Replace this page
with your product promise.
Use this starter to shape your positioning before you build more features.
Replace the headline, proof, offer, and calls to action with your own message.
Aim for one sentence a buyer understands in 5 seconds: who it's for, what changes, and what friction you remove.
Example: "Automate vendor onboarding for small HR teams—without spreadsheets and follow-ups."
One promise.
One customer.
One measurable change.
Keep it simple enough that a buyer can repeat it after one read.
Why this is structured
Most products don't fail because the idea is bad.
They fail because the message is unclear—and the build gets bigger anyway.
This page forces clarity before you spend more time or money.
THE COST OF STAYING MANUAL
Name the expensive problem you remove.
What breaks, slows down, or leaks money if nothing changes?
Write it like your customer would say it.
Time lost on ___
Money lost on ___
Risk created by ___
Common objection: "We tried before and it didn't stick."
Closing tip: name the cost before you pitch the fix.
THE SIMPLE PROMISE
What changes—and how it works.
Sentence 1: the measurable change.
Sentence 2: the simple mechanism (no jargon).
One recurring bottleneck removed
One manual step automated
One reliability promise
One clear 'why now'
Proof ideas:
- Hours saved per week
- Fewer mistakes / fewer support tickets
- One before/after metric you can show
Before vs. After (keep it measurable)
Pick 3 metrics your customer actually cares about.
Use real customer language. If you don't have customers yet, use the words you hear in sales calls.
Who this is for (and who it isn't)
Specific sells.
Write so the right people self-select—and everyone else leaves fast.
Best fit:
- They have this problem weekly.
- They already pay (in time or money) to handle it.
- They want a simple workflow, not more complexity.
- They can decide without a committee.
What they get
List what's included—no fantasy.
Price it to the cost you remove.
- A structured page: problem → proof → audience → offer
- Reusable UI blocks (hero, grid, pricing, FAQ)
- Fill-in prompts so you don't guess
- A clean baseline you can iterate safely
Technical Deep DiveSee the execution checklist
Execution System Map
Core capability
- Define one recurring problem this removes.
- Name the trigger that starts this workflow.
- State one measurable outcome.
User flow
- Map the first 3 steps a user takes.
- Call out one friction you eliminate.
- Add one reliability promise.
Value model
- Describe how value is delivered each cycle.
- Tie pricing to time saved or risk reduced.
- List what is included by default.
Operations
- Set an onboarding expectation in plain terms.
- State what needs ongoing attention.
- Define support response boundaries.
Growth loop
- Name your first acquisition channel.
- Show the conversion checkpoint sequence.
- Pick one feedback metric to review weekly.
Integrations
- List the tools your buyer already uses.
- Define import and migration boundaries.
- Identify one automation to add later.
One promise, one method, one proof.
Next step
If you can fill this page clearly, you're ready to build.
If you can't, fix the message before you write more code.