Skip to content
BTW

Use cases

Built for one artist. Ready for the whole production.

BTW gives every AI generation a searchable home. Start alone, keep the tools you already use and bring collaborators into the same record when the job grows.

01 Freelance AI artists

Your best work should not live inside someone else's tool history.

The situation

A client comes back for last season's look. The prompt is in one account, the reference in another and the approved export is somewhere in a project folder.

What changes

The asset, the recipe it was made with, its references and its versions stay in one record. Open it, answer the client and pick the iteration back up without unpaid detective work.

Start on the free plan. Move to Freelancer when active client work grows.

Start free
Asset · Prompt
A BTW asset detail view: the prompt that was used, with a recipe block naming tool Midjourney, model Midjourney v6, seed 744120815 and aspect ratio 4:5.
One asset, six months later: the prompt and the settings it ran with are still on it.
  1. Tool, model, seed, aspect
  • The prompt, tool, model, seed and aspect ratio stay on the shot
  • Copy a recipe you already used straight into the next job
  • Hand over the final with its record attached

02 Teams and studios

One production should have one shared memory.

The situation

Three artists touch a shot, feedback lands in chat and the director only sees the final export. When the next change arrives, nobody has the complete context.

What changes

Versions, decisions and recipes sit together in one workspace. A new teammate sees what happened, and a producer can answer without chasing the person who ran the generation.

Team includes five seats and scales self-serve up to ten.

See team pricing
Workflow · Versions
The BTW workflow canvas: three connected versions of one shot, marked hold, killed and final.
Iterations of one shot, each carrying the call that was made on it.
  1. The version that shipped
  • Iterations stay linked in the order they were made
  • Every version is marked: on hold, killed or final
  • Client review and handover keep the context attached

03 Agencies

The record stays with the agency, not with whoever held the login.

The situation

Work crosses internal teams, freelancers and production partners. The client asks the agency how an asset was made, even when the generation happened elsewhere.

What changes

Every account works to the same shape of record, with projects and roles kept separate. The agency holds the history it needs for delivery, reuse and the questions that follow.

More than ten seats, or a rollout of your own? We will plan it with you.

Talk to us
Library · References
The BTW library, references tab: a folder rail with named folders and counts, a rights status filter, and reference cards each marked clear, unclear or risky.
The shared reference shelf, with a rights status on every item on it.
  • One shape of record for every contributor
  • Each reference carries a rights status: clear, unclear or risky
  • One answer you can reuse for handover and procurement questions

Start

Start with the workflow you have today.

Your first project takes about two minutes. The free plan needs no credit card, and nobody has to change AI tools.