Starting a run
New pitch takes a company name, a bare domain, or both, plus optionally a point of contact, the partnership motion to argue for, and the value angle to lead with (the last two come from your workspace's own brief). Before anything else, the studio works out who the company actually is from its own website — it opens the site, reads what they sell and to whom, and rules out same-named businesses. The pitch is then researched, scored and drafted against that settled identity.
While it runs
A run takes minutes and shows six named stages: understand, research, score, draft, people, check — with what each stage is actually doing ("2 searches · 9 sources read"). There is no percentage bar on purpose: research is one stage of six, and a long read would sit at 17% looking dead.
You can leave. The worker runs in the background; Running lists every run in flight with Watch to drop back in. A run nothing has been heard from in twenty minutes is marked stopped and offers Dismiss; a run still working offers Stop (confirmed — it kills real work). There is no pause.
Everybody reads every run; your own are yours to manage. Stopping, archiving or deleting a run somebody else started — or calling off their batch — needs the owner or admin role in the workspace. Reading it never does. (The roles are in Workspace settings.)
Beast Mode — a whole list at once
The foot of the New pitch form: upload a CSV or paste one company per line (Company name, website — the website optional) and Run batch → queues every row through the same pipeline. Up to 100 companies per batch, three running at once, each landing in the Library like any other pitch. The CSV is parsed in your browser and never uploaded.
Reading the result
A pitch reads as a sequence: Summary → Fit thesis → Signals (for and against, each rated by recency and recurrence) → Deliverables (deck, one-pager, cold email, proposal — each block copyable and pencil-editable) → Decision-makers → Lookalikes → Next steps. If it is coral, you can click it.
- Blank decision-maker names are deliberate. A name appears only when a credible source supports it; blanks are left for your own enrichment rather than filled with guesses.
- Bracketed placeholders in drafts mark what could not be verified — filling them in is your job, and they are listed together so none is missed.
- Find more under the researched lists queues more research in the background — an empty box is a valid instruction ("look again").
- Compliance findings: the studio reads its own draft back and reports anything that broke a rule (banned terms, numbers without provenance) next to the work. What to do about them is your call.
- What the studio read to know who this is, at the foot of the Summary, lists every page the studio opened with what it learned there, and every same-named company it checked and ruled out with the reason why. It is open — you do not have to go looking for it. If a company you have never heard of is missing from the ruled-out list and its facts are in the profile instead, that is the thing to catch before you send anything.
- The highlighted sentences in a draft were written for this company. Above each deliverable a line counts them — "6 of 21 sentences were written for Delvinia" — and the sentences themselves are marked where you read them. A sentence counts when it names something the run established about the target: its name, brand, legal entity or domain, one of the decision-makers the research named, where it is or how big it is. Its industry does not count, because B2B SaaS describes the target and everyone it competes with. Unmarked is not wrong — your own proof and your own offer belong in the draft and are not about the reader. The one to act on is a draft that names nobody: the studio says so in red, and it means the draft reads as something you could send to anyone. On a shared link the recipient sees the count and the highlighting, and never that judgement.
- From your own workspace, on the Summary, says what this run had of yours to read: how many recorded outcomes and how many saved edits went into the draft. Everything else came from your brief and the live web. A run that found no outcomes says so, and offers the door to record one — that is the loop that makes a later run better than this one.
Editing, and what it teaches
The pencil on any deliverable block edits it in place. Saved edits become brand-voice examples for future runs — tone and structure only, never facts, and facts never cross companies. Editing is the highest-leverage thing a team does in the studio.
Since 23 Aug 2026 a run chooses those examples for the company it is working on rather than simply taking the three most recent: the ones whose subject looks most like this target, with at least one example of each deliverable the run has to write. So a workspace with fifty saved edits draws on all fifty, a few at a time, instead of on whichever three were saved last.
A run also carries what your team recorded in Outcomes — what actually won and lost, in their words. The waiting line says so while the run works: "Brief loaded, with 4 of your edits as voice references and what you recorded about 6 companies." It shapes the judgment, never the copy — a company from your own outcomes record appearing in a deliverable is flagged by the compliance check like a banned word is.
Ask the studio
The last tab of a finished pitch is a conversation about it — where a claim came from, how to open the first call, what to say when the predicted objection lands. It answers only from that pitch and your brief, and never changes the pitch. Each member has their own conversation per pitch; it survives reloads.
Print / PDF
Ctrl/Cmd-P, or the Print / PDF button on a pitch or a share, prints the deliverable styled with your workspace's own stylesheet — Save as PDF in the same dialog is the PDF export.