21 Branches

Hey, your AI results are about to get way better.

You are one bad prompt away from throwing your computer out the window. We help you refine your AI requests faster, so you spend less time rewording and more time getting things done.

1,308 writers applied for private beta
Get $100 in free credits across popular AI models when you sign up.
Join the beta to learn more.

One email when your seat opens. No newsletter. No marketing.

· Pick a demoSkip ahead
4 sections · scroll or click
01
See the doc as a tree
Eight branches off a PRD
02
How branching works
A diagram
03
Watch a branch run
Live demo · cover letter
04
Try a workflow
Run an agent
· Explore the branches

Stop wasting time on tedious work and
less time gambling on rewrites.

Import your artifact into the workbench. From there, spin up AI agents to explore every scenario in parallel and branch recursively. Each path they take generates a unique iteration, eliminating the cost of dead ends. Review the drafts, select the pristine version, and get to done.

checkout-v2.prd
7 branches · 2 sub-branches
ResearchLibrarianGhostwriterArchitectScribeForeman
main doc
v3
PRD: Mobile checkout v2
PRD: Mobile checkout v2
§1 · Background
We launched checkout v1 in Q3 and saw a 38% drop-off at the payment step on mobile. The flow asks for an email, then a card, then a billing address — three screens before the wallet sheet appears. Competitors lead with the wallet. This PRD proposes we do the same, with native fallback for users without a saved wallet, and a phased rollout to contain Android auth risk.
Research branch
+1
Competitor pricing scan
PRD: Mobile checkout v2
§1 · Background (+ market context)
We launched checkout v1 in Q3 and saw a 38% drop-off at the payment step on mobile. Stripe, Shopify, and Square all lead with wallet payment; peer CSAT lifts +14pt when wallet leads (11 sources).
Architect branch
~1
Lead with risk, then fix
PRD: Mobile checkout v2
§1 · Risk (was Background)
We launched checkout v1 in Q3 and saw a 38% drop-off at the payment step on mobile.Android auth drop-off is 11.4% — material; the resulting 38% mobile drop-off costs us $4.1M ARR. This PRD proposes a wallet-first flow with native fallback, phased to contain that risk.
Ghostwriter branch
~1
CFO-friendly version
PRD: Mobile checkout v2 (CFO draft)
§1 · TL;DR for finance
We launched checkout v1 in Q3 and saw a 38% drop-off at the payment step on mobile.Mobile checkout v1 costs us $4.1M/yr in drop-off. Wallet-first lifts conversion 11–14pt at peers; Android auth is the only material risk, contained by a phased rollout. Decision needed by Nov 14 for Q1.
Scribe branch
+1
Spec the API surface
checkout.session — API spec
§ NEW — endpoints (companion doc)
Three endpoints power the wallet-first flow: POST /v2/checkout/session returns a sessionId and wallet hints; GET /v2/checkout/session/:id returns status; POST /v2/checkout/session/:id/confirm finalizes. All paths are backwards-compatible with v1.
Foreman branch
⚑1
Audit the rewrite
Audit · architect branch
§ Findings on §1 rewrite
Risk framing preserved and numbers verified — but the architect's rewrite of §1 dropped two facts from the original Background paragraph (refund SLA and EU regs). Both queued for the Librarian sub-branch to recover.
Librarian branch
§1
Past risk language we used
Excerpt · Q2 launch memo
§4 — voice reference
From our Q2 platform memo: "We name the risk before the fix — every time." Declarative, single-clause, no hedging. Borrow this framing for the architect's §1 opener.
Librarian branch
§1
Refund SLA from old docs
Excerpt · checkout v1 PRD
§6 — refund policy
Recovered from checkout-v1.prd §6: "Refunds resolve within 5 business days, EU within 7," with the EU clause referencing PSD2 art. 74. Handing back to Foreman to patch the architect's §1.
Each branch is read-only until you promote it. Main doc unchanged. Steal a paragraph, promote one branch, or merge two.
I went from spending hours wrestling with AI assistants to getting what I needed in under a minute
Joseph · Beta Tester

We call it Death by a Thousand Prompts. It’s exhausting, it’s frustrating, and it completely defeats the purpose of using AI in the first place.

We fix the endless back-and-forth so you get more things done faster.

· Formats

Plugs into your stack.

Linear, Figma, GitHub, Notion, Slack. Lull reads from where the work lives and writes back in the right format — no migration, no lock-in.

Code
Any language
DOCX
export anytime
PDF
with footnotes
TXT
plain text & RTF
Markdown
send as a letter
EPUB
long-form ebook
HTML
publish to the web
JSON
every version, raw
· How branching works

The best version of your draft hasn't been written yet.

Spin up a branch for each premise. Each is a full alternate, written by an agent. Read it. Ask the author why. Steal a paragraph. Promote the winner. The main doc is always yours.

· Main

Your draft.

The only doc you author. Edit freely. Steal from any branch. When a branch wins, it becomes the new main.

v3 · saved
spin up
promote
Aggressive· by Skeptic

Cuts the warm-up. Gets to the ask in two sentences.

OPEN ↗
CFO-first· by Architect

Leads with cost, risk, and the call to action.

OPEN ↗
Plain English· by Editor

No jargon. A smart reader who has never seen this gets it.

OPEN ↗
Spin up

Pick angles. Agents write full alternates in parallel.

Read · Ask

Open any branch. Ask its author why it made a choice.

Steal

Pull a paragraph from a branch into main with one keystroke.

Promote

Pick a winner. It becomes the new main. Old main is archived.

· Watch a branch run

One cover letter.
Three full alternates.

Spin up three branches with three different premises. Each agent writes a complete alternate draft — not a comment, not a suggestion. Read them side by side. Pick a winner. The main doc only changes when you say so.

cover-letter_to-stripe.md
Letter · 1 page · 287 words · main · saved 4m ago
Branches · writing in parallel
branch
Aggressive
“Cut the warm-up. Get to the ask in two sentences.”
branch
CFO-first
“Lead with cost, risk, and the call to action.”
branch
Plain English
“No jargon. A smart reader who's never seen this gets it.”
Compare · pick a branch
Spin up branches to see three full alternates written in parallel. Pick a winner — your main doc only changes when you say so.
· Try a workflow

Different agents for different docs. Watch it in action!

Maren_Holst_resume_v3.docx
Resume · 2 pages · last edit Tuesday
  1. Reading the document
    —
  2. Studying your voice
    —
  3. Tightening impact bullets
    —
  4. Suggesting a single opener
    —
  5. Awaiting your approval
    —
Edits
11
Time
18s
Auto-applied
0
Run the recipe to see results.
Resumes · in the wild
№ 01 / 04

turned into 3.2× more callbacks at

OpenAIGooglexAITikTokMicrosoftAmazonMetaRobloxSalesforceUberDoorDash
— plus startups backed bya16z·General Catalyst·Sequoia·Accel·Lightspeed
Beta cohort callback rate: 18% → 57%
verified

21 Branches is not affiliated with or endorsed by any company or publication listed.

· Three primitives

Compose. Steer.
Orchestrate.

· Compose

Build the workflows your team actually runs.

Chain agents into reusable loops — research, drafting, QA, release. Save them, fork them, share them across the team.

· Orchestrate

Run six workstreams in parallel on one doc.

Agents read, draft, restructure, and review at the same time. Findings come back ranked by confidence. Nothing ships without your sign-off.

· Steer

Every revision reversible. Every call yours.

Full audit chain on every change. Roll back any agent, any step, any decision — down to the keystroke.

· Workflow library

Eleven workflows
ship in the box.

Each is a reusable workflow — a chain of agents, a doc shape, a set of outcomes. Fork any of them. Teams in beta help us pick the next batch.

See the full library
Product
Draft a PRD
Reads the brief, the research, and the last three sprints. Returns a revision and one open question.
Engineering
Design a system
Reads the PRD and the surrounding code. Returns boundaries, data shape, sequence — and the failure mode you should worry about first.
Engineering
Refresh stale docs
Walks the diff between what the docs claim and what the code does. Flags every line that has quietly become a lie.
Engineering
Write a runbook
Reads the alert, the dashboards, the last three incidents. Returns the steps, in order, that the on-call will actually follow at 3am.
Student
Lit review
Drop in 12 papers. 21 Branches surfaces contested claims and drafts the synthesis with citations.
Student
Final paper
Outline-first canvas. Citations auto-resolve. Margin asks the questions your professor will.
Research
Customer research
Synthesizes interview transcripts into themes, quotes, and the questions you didn't ask.
Engineering
Spec a feature
From a one-line idea to acceptance criteria, edge cases, and a Linear-ready ticket.
QA
QA a release
Reads the diff, the spec, and the changelog. Flags drift between what was promised and what shipped.
Personal
Letter draft
A clean format for the harder kind of email. No subject line yet.
Notes
Half-formed idea
A scratch page that never asks you to commit.
Editing
Compare two drafts
See what changed in plain English. Roll back to any version.
Speaking
Talk outline
Stage notes, slide cues, and a script in one calm document.
Personal
A short note on…
The classic 21 Branches format. Title first, paragraphs next, no pressure.

Bring a doc.
We'll bring the calm.

Free for the duration of the beta. No credit card. No marketing emails. Just a quiet seat at the table when one opens up.