In 2019, before designing a single Vulpine Creations product, I wrote the sales page.
Not a rough draft. The real page. The headline, the problem statement, the product description, the pricing, the call to action. I wrote it as if the product existed, as if it were ready to ship, as if the only thing between the customer and the product was a click.
The product did not exist. But writing the page forced me to answer every question the customer would ask — before I built anything.
What does this product do? Who is it for? Why is it better than alternatives? What does it cost? What does the customer get? When do they get it?
If I could not answer these questions clearly on a sales page, I could not answer them clearly in product design. The page was not marketing. It was a mirror for my own thinking.
The Paradox
The paradox is this: the sales page is supposed to sell a finished product. Writing it before the product is finished seems backwards. But the act of writing the page before building clarifies what needs to be built.
Most founders build first and sell second. They design features, then figure out how to describe them. They set a price, then figure out how to justify it. They create a product, then figure out who it is for.
The sales-page-first approach reverses this. It forces you to start with the customer’s perspective — what they want, what they fear, what they need to hear — and then build a product that matches.
This reversal eliminates a common and expensive failure mode: building a product that you cannot explain. If the sales page is confusing, the product concept is confusing. And a confusing product concept produces a confusing product, no matter how well it is built.
What Writing the Page Reveals
The sales page exposes four types of confusion that building alone cannot.
Audience confusion. When you write the problem statement, you must decide who the customer is. Not vaguely — specifically. If you find yourself writing “this is for anyone who…” you have not chosen a customer. Go back to the profile.
Value confusion. When you write the solution section, you must articulate what the product does for the customer. Not what it is. What it does for them. If you cannot describe the outcome in two sentences, the value proposition needs work.
Pricing confusion. When you write the price, you must commit to a number. Many founders avoid pricing decisions until launch day. Writing the page forces the decision early, which forces the pricing research that should happen before you build.
Scope confusion. When you list what is included, you define version one. This list becomes your specification. Everything on the page is in the product. Everything not on the page is out. The page draws the boundary that prevents scope creep.
The Process
Here is how to write a sales page before you have a product.
Step 1: Write the problem (30 minutes). Pull from your customer interviews. Describe the problem in the customer’s words. Be specific. Be vivid. If the problem section does not make a reader nod and think “that is exactly my situation,” rewrite it.
Step 2: Write the solution (30 minutes). Describe the outcome the product delivers. Not features — outcomes. “You will know exactly where every euro went, without manual tracking, in less than five minutes per week.”
Step 3: Write the proof (20 minutes). If you have testimonials from your interview subjects who said “I would pay for that,” use them (with permission). If not, use your own expertise: “Built by someone who spent 20 years helping businesses get their finances right.”
Step 4: Write the offer (20 minutes). Price, what is included, what is not included, guarantee, timeline. This is the commercial heart of the page and the hardest section to write, because it requires committing to specifics.
Step 5: Write the headline (10 minutes — write this last). The headline is the distillation of everything else. Write it after the body is done, because you need to know the full page before you can summarize it in one line.
Total time: about two hours. You now have a sales page that doubles as a product specification, a pricing commitment, and a validation tool.
Using the Page for Validation
The sales page you just wrote is also a landing page test. Put it online. Replace the “Buy Now” button with an email signup: “Join the waiting list — launching soon.”
Drive traffic. Measure signups. If the page converts well, the product concept is validated. If it does not, the concept needs refinement — and you discover this before building anything.
Better yet, add a real price and a real “Pre-order” button. Sell before you build. If people pre-order based on the sales page alone, you have the strongest possible validation signal.
The page that started as a thinking tool becomes a validation tool becomes a sales tool. One document, three functions, zero product development required.
The Feedback Loop
Share the page with five people from your target market. Not for validation — for clarity testing.
“Can you tell me, after reading this page, what the product does, who it is for, and what it costs?”
If they can answer all three questions correctly, the page is clear. If they cannot, the parts they get wrong are the parts that need rewriting — and redesigning, because if the page is confusing, the product concept behind it is confusing.
This feedback loop produces better product decisions than any brainstorming session. You are testing the clarity of your concept through the lens of the customer’s experience, using the sales page as the medium.
The Page as North Star
Once the page is written, print it. Pin it above your desk. Every product decision should be checked against it.
“Does this feature appear on the sales page?” If not, it is not in version one. “Does this design choice match the page’s positioning?” If the page promises simplicity and the product is complex, something is misaligned. “Would this change make the sales page stronger or weaker?” If it would not make the page stronger, question whether it makes the product stronger.
The sales page is your promise to the customer. The product is the fulfillment of that promise. Building the promise first ensures the product is built to deliver it.
All great things start terrible. Your sales page will be version one of the page, just as your product will be version one of the product. Both will improve through iteration. But starting with the page — starting with clarity about what you are offering and why — produces a first product that is more focused, more marketable, and more likely to sell.
Write the page. Then build the product the page describes. The sequence feels backwards. The results are forward.
