Sell before you build: pre-selling without the bullshit

In short — Pre-selling means selling a digital product before you build it, to validate demand with real money rather than opinions. It’s the only method that protects a solopreneur from the classic scenario: six months of coding, zero customers.

---

You have an idea. It feels solid. You switch into build mode: Git repo, tech stack, design system, landing page. Three months later, you launch. Five people visit the page. Two sign up for the newsletter. Zero sales.

That’s not a lack of talent. It’s a sequencing problem. You built before you sold — when the only way to know if someone will pay for your product is to ask them to pay, before the product exists.

Pre-selling isn’t a growth hacker technique. It’s a survival discipline for a solo studio.

Why most solopreneurs build in the wrong order

The default developer logic is: “I build something good, people will buy it.” That’s wrong. And it’s especially dangerous when you’re solo, because there’s no team to absorb the cost of a flop. Every week of wasted build time is a week of lost revenue and energy burned on a bad bet.

There’s a structural reason for this inverted order: code is comfortable. Coding is controlled. You know what you’re doing. Selling before you have a product exposes you to immediate rejection. It’s uncomfortable, so you put it off.

The problem is that the discomfort of rejection on day 3 is infinitely less costly than the collapse on day 90 after you’ve built everything.

The other reason is the confusion between interest and demand. People say “great idea” to be polite. They say “I’d be interested” because it’s true — in a hypothetical world where the product is perfect and free. Money doesn’t lie. When someone pulls out their credit card for something that doesn’t exist yet, that’s a real signal. Everything else is noise.

According to CB Insights data on startup failure reasons, “no market need” comes in first place (42% of cases). For a solopreneur with no safety net, that number isn’t an abstract statistic — it’s the daily risk. Pre-selling is the only way to test the market before committing the real cost: your time.

The three forms of pre-selling — and when to use each

There are three distinct formats. They don’t measure the same thing and they don’t apply to the same situations.

1. The waitlist (weak signal, zero cost)

You publish a minimal page describing the problem you’re solving, the solution you’re considering, and a sign-up form. No payment.

This is useful very early on, when you don’t yet have conviction about the shape of the product. A list of 200 sign-ups in two weeks tells you the topic is interesting. But “interesting” isn’t “buying.” Count on a list-to-purchase conversion rate of 3 to 8% in the best case. So 200 sign-ups = 6 to 16 potential buyers. That’s a signal, not a validation.

Use the waitlist to: test a messaging angle, build a starter audience, prepare a paid beta.

2. The paid beta (medium signal, real commitment)

You ask for a reduced payment — typically 30 to 60% of the final price — in exchange for early access and an active role in shaping the product. Paid beta testers aren’t guinea pigs; they’re co-builders.

This is the most useful format for a solo digital product. You collect cash that funds the build. You have real users from day one. And you build exactly what they need, not what you imagined.

The paid beta works particularly well for SaaS, tools, and premium courses. It assumes you can deliver a partial but functional version within an announced timeframe (4 to 8 weeks maximum — beyond that, trust erodes).

3. The pre-order (strong signal, maximum commitment)

You sell the final product at its real price (or with a 20 to 30% launch discount) before it’s delivered. You set a public delivery date. You collect money now.

This is the most reliable signal, and the hardest to get without an audience or social proof. Pre-orders work when you already have a relationship with your target — a newsletter, a community, a content history — or when the product is a natural follow-on to something you’ve already sold.

Quick reference for choosing:

Format	Signal	Money collected	Best context
Waitlist	Weak	No	Very early idea, no audience
Paid beta	Medium	Yes (partial)	SaaS, tool, course — nascent audience
Pre-order	Strong	Yes (full)	Existing audience, clear product

How to build a minimal sales page in 48 hours

A presale page isn’t a startup landing page with animations and testimonials. It’s an honest document that answers four questions in order.

Question 1: What is the exact problem? Describe it in your target’s words, not your developer words. If you’re targeting freelancers who waste time chasing clients, write: “You’re sending the same follow-up email for the third time this week.” Not: “Optimise your client follow-up workflow.”

Question 2: What transformation are you promising? Not features. Life after. “In 30 days, your follow-ups go out automatically and you never think about them again.”

Question 3: Why you, why now? Your legitimacy on the subject. One sentence is enough. No false modesty, no inflated self-promotion. A concrete fact: “I spent 18 months automating my own client management as a freelance dev.”

Question 4: What exactly are people buying? Price, delivery date, what’s included, what isn’t yet. Transparency about current limitations builds trust — it doesn’t destroy it.

The message script for your first 20 sales

If you don’t have an audience, the first 20 sales don’t come from a web page. They come from direct conversations. Here’s the structure of a message that works, to send to existing contacts or in relevant communities:

“I’m building [product name], a tool for [specific problem]. Before writing any code, I’m looking for 10 people who deal with this problem and want early beta access at [reduced price]. If that’s you, or if you know someone it fits, reply directly.”

This message is short. It’s honest about the fact that the product doesn’t exist yet. It creates real scarcity (10 spots). And it asks for a simple action: reply.

Tools for a page in 48 hours

You don’t need a complex stack. The fastest options:

• Carrd or public Notion: a static page in under an hour.
• Gumroad or Lemon Squeezy: built-in payments, zero code, 5 to 10% commission.
• Stripe + form: if you want to own the data, a Stripe payment link + a Typeform is enough.

The goal is to have a URL to share within 48 hours. Not a perfect page. A page that exists and lets people pay.

If you want an outside perspective on what your page actually communicates — message clarity, conversion friction — that’s exactly what the SEK audit addresses.

What threshold triggers the real build — and how AI accelerates the test phase

This is the question everyone dodges, because the answer forces you to commit.

The minimum threshold in real money:

• Price between €29 and €79: 10 pre-orders or paid betas before you start coding.
• Price between €80 and €199: 5 pre-orders is enough.
• Price above €200: 3 confirmed customers with payment collected.

These thresholds aren’t arbitrary. They represent a sufficient signal that the risk of building is reasonable — not zero, but reasonable. Below that, you’re betting on noise.

What AI actually changes in the validation phase

AI doesn’t validate for you. It can’t tell you whether people will pay. But it drastically cuts the time between idea and test.

Concretely, as a solo operator in 2026, here’s what AI accelerates:

• Writing the presale page: a solid prompt about your target problem and your solution produces a first draft in 10 minutes. You go from “blank page” to “something to edit” in a fraction of the usual time.
• Finding target communities: asking an agent to list active subreddits, LinkedIn groups, and Discord servers on your target topic — with size and engagement criteria — takes 5 minutes instead of 2 hours of browsing.
• Analysing responses: when you get replies to your prospecting messages, an agent can help you identify patterns in the objections. “Too expensive,” “not the right time,” “I don’t understand what it does” — each type of objection calls for a different response.
• A/B testing messages: generating 5 variants of a prospecting message, testing them on different channels, measuring response rates — AI produces the variants, you analyse the results.

What AI doesn’t do: it doesn’t go into communities on your behalf with your voice and your credibility. It doesn’t build the trust relationship that turns a stranger into an early buyer. Pre-selling remains a human act, because it rests on trust — and trust can’t be delegated to an agent.

For more on the numbers that shape the solo economy in 2026, the solopreneur & AI statistics 2026 piece compiles the authoritative sources on the rise of the one-person business.

What pre-selling reveals that building never does

There’s a secondary benefit of pre-selling that rarely gets mentioned: it forces you to clarify your positioning before you have any code to show.

When you try to sell something that doesn’t exist, you have to answer the hard questions immediately. “What’s the difference from [competitor]?” “Why that price?” “What happens if it doesn’t work as expected?”

If you get those questions on day 3 (during the presale), they cost you a conversation. If you get them on day 90 (after the build), they cost you a pivot or an abandonment.

Pre-selling is also a motivation filter. If you can’t bring yourself to send the prospecting message, publish the page, ask for money for something that doesn’t exist yet — that’s information about you and your level of conviction in the idea. Not a judgement. A data point.

Solopreneurs who manage to last don’t build less. They build better, because they know in advance that what they’re building has a chance of being paid for. That’s the competitive advantage of a disciplined solo studio over a team iterating in the dark.

If you’re stuck on the technical side — how to set up the page, connect payments, automate the beta-tester onboarding sequence — /unstuck/ is designed to unblock exactly that kind of situation in a single session.

---

Sébastien de Bollivier has been a freelance dev since 2008 and builds solo from La Réunion. If you’re looking for someone to help you frame the technical side of a launch or validate a stack before you build: sebastiendebollivier.com.

Got an idea to ship? A website, a SaaS, an AI automation — built with you.

Talk about your project