Most indie founders do not have a positioning problem. They have a rewrite problem. The homepage gets torn apart every Tuesday because a friend said the hero felt vague, a cold DM went unanswered, or ChatGPT suggested a punchier headline. Three weeks later you have twelve hero drafts, zero clarity, and a site that still sounds like a category page.
A one-page positioning brief fixes that. It is not a brand book. It is a single page you fill in one afternoon so the homepage has something solid to obey. When the brief is done, rewriting copy becomes translation—not invention under panic.
This guide is for solo founders and tiny indie/AI SaaS teams who keep polishing the landing page before they can say, in one breath, who it is for and why it wins. If you are already collecting thin but honest proof for that page, pair this with how to write social proof for an indie launch when you have almost no users—positioning tells the story; proof makes strangers believe it.
What a one-page positioning brief actually is
Think of it as the contract between you and your homepage. One page, eight blocks, written in plain language you would say on a call. No mission statements. No "empowering creators." No feature laundry lists pretending to be strategy.
The brief answers five questions a visitor is silently asking:
Is this for someone like me?
What painful job does it do?
Why is this better than the messy workaround I already use?
What should I believe after reading the hero?
What is the next concrete step?
If you cannot answer those on paper, no amount of gradient hero art will save the page. And if pricing still feels like guesswork after the brief, that is a signal too—see how to price your first SaaS when you have almost no data once the who/what/why is locked.
Homepage rewrites without a brief are therapy. Homepage rewrites with a brief are shipping.
The one-page template (copy this into a doc)
Open a blank Notion page, Google Doc, or Markdown file. Title it with the product name and today's date. Fill every block in bullets. Aim for ugly clarity over pretty prose.
1. Product in one sentence
[Product] helps [specific person] [do specific job] so they can [measurable or felt outcome], without [the painful workaround].
2. Primary customer (ICP)
Role / company shape / stage. One primary. Secondary audiences go in a "not yet" footnote—not in the hero.
3. Job to be done
When [situation], I want to [progress], so I can [outcome]. Write it in the customer's words, not yours.
4. Status quo & switching cost
What they use today (spreadsheet, ChatGPT tabs, agency, competitor, doing nothing). Why switching feels annoying.
5. Differentiator that a stranger can verify
One claim you can defend in a demo or screenshot. Not "AI-powered." Something like "imports your Notion docs and drafts the first outbound email in under two minutes."
6. Reasons to believe
3–5 proof points: a metric, a quote, a before/after, a constraint you designed around. Thin is fine if honest.
7. Objection you must answer above the fold
The one worry that kills signups ("Will this train on my data?", "Is this just ChatGPT with a UI?", "Do I need a designer?").
8. Primary CTA + success moment
The button label and the first win after signup. If the CTA and the first win do not match, the page is lying.
That is the whole page. If a block takes more than six lines, you are writing a manifesto. Cut it.
How to fill the brief in one afternoon
Block three hours. Phone on Do Not Disturb. No Figma until the doc is done.
Hour 1 — Mine real language
Pull five sources before you invent copy:
Last 10 sales or discovery call notes (or Discord/Slack DMs if that is your "sales")
Support tickets or "where did you get stuck?" replies
Rejected outreach—what people said when they said no
Competitor homepage heroes (steal the structure of clarity, not the adjectives)
Your own onboarding: what you type when you demo the product live
Highlight phrases customers repeated. Those become the job-to-be-done and objection blocks. If your best distribution asset is still a repo, remember your GitHub README may already be doing more sales than your landing page—mine README questions the same way.
Hour 2 — Force tradeoffs
Write two ICPs that feel tempting. Delete one. Positioning dies when the hero tries to please "indie hackers, agencies, and enterprises."
Write three differentiators. Keep the one a skeptical friend could check in five minutes. Kill "all-in-one," "seamless," and "next-gen" on sight.
For AI products, be ruthless: if the differentiator is the model, you do not have a differentiator. Prefer workflow, data, evaluation, speed-to-first-output, or a constraint your buyer already lives with (compliance, brand voice, offline, team roles).
Hour 3 — Stress-test out loud
Read the one-sentence product line to someone who is not invested in your startup. Ask only: "Who is this for, and what do they get?" If they invent a third audience you never wrote, the sentence is mush.
Then write the anti-position: one sentence for who this is not for. Put it at the bottom of the brief. It keeps you honest when you are tempted to widen the hero "just for this launch."
Worked example: indie AI SaaS (meeting notes → CRM follow-ups)
Imagine a solo-built tool that turns messy meeting notes into CRM follow-up tasks for B2B founders who hate Salesforce hygiene.
Product in one sentence: NotePipe helps solo B2B founders turn messy call notes into CRM tasks and follow-up emails in under three minutes, without rebuilding their pipeline in Notion every Sunday.
ICP: Solo or 2-person B2B SaaS founders doing their own sales calls, already using HubSpot free or a spreadsheet CRM, closing under ~15 deals/month.
Job: When I finish a sales call, I want the next steps captured where I will actually see them, so I do not ghost warm leads because I was "busy shipping."
Status quo: Apple Notes + a half-updated HubSpot deal + a guilt spiral. Switching cost: fear of another AI tool that invents action items.
Differentiator: Pastes into your existing HubSpot fields and drafts the email in your tone from the last five messages—no new CRM.
Reasons to believe: "Cut my post-call admin from 25 minutes to 4" (beta quote); works offline on the transcript paste; never auto-sends email.
Objection above the fold: "Does this send email or write to my CRM without me?" Answer in the hero subhead: you approve every task and every draft.
CTA + first win: CTA "Paste a transcript." First win: one approved HubSpot task + one draft email in the first session.
That brief already dictates the homepage. You are no longer hunting for clever headlines. You are mapping blocks.
Turn the brief into homepage sections
Here is the boring, effective mapping. Stick to it for v1.
Hero headline ← Product in one sentence (tighten; keep the ICP noun)
Hero subhead ← Job to be done + objection answer
Primary CTA ← Same verb as the first win
Logo/proof strip or quote ← Reasons to believe (even one specific quote beats five fake logos)
"How it works" 3 steps ← Differentiator broken into a path the ICP recognizes
Comparison / vs status quo ← Status quo & switching cost (table or two columns)
FAQ (3–5) ← Objections you heard in Hour 1
Final CTA ← Repeat the first-win promise, not a new fantasy feature
What you cut: the feature grid with twelve icons, the "trusted by innovators" empty row, and the paragraph about your founding story above the fold. Story can live lower or on /about. The homepage's job is recognition and a clear next step.
Copy patterns that survive contact with reality
Weak: "AI-powered productivity for modern teams."
From the brief: "Turn sales call notes into HubSpot tasks before you close the Zoom tab."
Weak: "Save time with automation."
From the brief: "Approve the follow-up in under three minutes—nothing sends without you."
Weak: "Built for founders."
From the brief: "For solo B2B founders who still run their own demos."
Specific nouns beat category adjectives. Every time.
A 90-minute homepage rewrite from the brief
Once the doc is solid, do not open five tools. Open the page and the brief side by side.
Replace the hero with the one-sentence product line. Subhead = job + objection. CTA = first-win verb. Ship it ugly if needed.
Delete anything that contradicts the ICP. If the brief says solo founders, remove "for enterprise GTM teams" badges you added for vibes.
Rewrite How it works as three steps that end at the first win—not at "enjoy insights."
Add one proof block from Reasons to believe. One defended number or one named quote. Stop there if that is all you have.
Write the FAQ from objections, not from SEO keyword lists.
Read the page out loud once. If you hear yourself hedging ("kind of," "and also," "for anyone who"), go back to the brief and cut the extra audience.
Then leave it alone for a week. Collect replies, call notes, and signup reasons. Update the brief first; only then touch the homepage. That habit alone ends the rewrite treadmill.
Common failure modes (and the fix)
The brief is a slogan farm. If every block is a tagline, you skipped Hour 1. Go back to call notes.
Two ICPs in the hero. Split into two landing pages later if you must. One homepage cannot marry "hobby indie hackers" and "Series A ops leads."
Differentiator only you care about. "Our proprietary pipeline" is not verifiable. "Exports a CSV your bookkeeper can open" is.
CTA promises a different product than the first win. "Start free trial" that lands on an empty dashboard with no sample data is a positioning leak. Align the button with the success moment in block 8.
You rewrite weekly because Twitter said so. Change the brief when evidence changes—new ICP interviews, a pattern in churn reasons, a competitor move that actually steals deals. Random aesthetic feedback is not evidence.
Keep the brief alive without bureaucracy
Pin the doc in your project folder. When you change pricing, ICP, or the core job, edit the brief the same day. Review it for fifteen minutes every Monday before you touch growth experiments.
Share it with anyone who writes public copy: future you, a contractor, a friend editing the launch post. If they cannot draft a hero from the brief alone, the brief is incomplete—not their fault.
Optional stress test: paste the eight blocks into a new chat and ask, "What homepage sections does this imply?" If the model invents a sixth audience, your brief still has mush. Tighten the nouns.
Ship the brief, then ship the page
You do not need a strategy offsite. You need one honest page that tells the homepage what job it has. Fill the template this afternoon. Stress-test the one-sentence line with a human. Map blocks to sections. Rewrite the hero once. Then go talk to users instead of rearranging gradients.
Positioning is not a vibe. It is a decision you write down so your homepage stops arguing with itself.
