How to Get Your First Paying Customer: Ask Early, Ask Directly
You get your first paying customer by asking, not by waiting for a pricing page to convert someone. Pick the few users who came back more than once, tell them what the product will cost, and ask for payment in a conversation. Take the money in the simplest way you can, even a hand-made invoice, and count asks and answers instead of sales. A clear no teaches you more than silence.
Why is the first payment a different job from the first user?
A free user spends attention. A paying customer spends money and takes a risk on you, so the evidence you need is different. People say yes to free things for many reasons that have nothing to do with value: curiosity, politeness, boredom. Paying removes all of those reasons at once, which is exactly why it is the better test.
It also changes who matters. The person who enjoys your product is not always the person who can approve a purchase. For a tool used by one person at work, ask who signs off the spending. For a consumer app, ask whether the user would pay out of their own pocket. If you cannot name the buyer, that is the first thing to find out, and a short call with two or three users will answer it.
Which users should you ask first?
Not everyone. Start from behaviour, because what people did is more honest than what they said. Compare each candidate against the signals below.
| Likely to pay | Probably not yet |
|---|---|
| Came back on more than one separate day | Signed up, used it once, never returned |
| Asked what it will cost, or whether a feature is coming, without prompting | Said it looks great but never asked a question |
| Used it for a real task with their own data | Only tried the sample data |
| Sent it to a colleague or asked how to add one | Described it as interesting |
| Has a budget or a deadline attached to the problem | Treats it as a someday project |
A handful of people in the left column is enough to start. Resist the urge to ask the whole list at once, because you want to learn from each conversation and change what you say in the next one.
What price do you say out loud?
Say a real price, attached to a real period, in the first sentence of the ask. “It is free for now, pay what you want” turns the conversation into charity, and you learn nothing about demand. A price also tells the customer you expect the product to be worth it.
- Anchor on the cost of the problem. If the product saves two hours of a job someone is paid to do, price against that job, not against what it cost you to build.
- Look at what they pay now. The spreadsheet, the freelancer or the rival tool they use today sets a reference. Ask what it costs them and be near it, or explain why you are different.
- Offer one option. Three tiers invite a debate about tiers. For the first customer, one plan and one price is easier to say yes to.
- Say what happens if they stop. A plain refund promise or a month-to-month arrangement lowers the risk of being first.
The guide on how to price a micro SaaS goes further into pricing models. For wording on a page later, see the pricing page copy template.
How do you take the money without building billing?
Do not build checkout yet. Send a payment link from whichever payment provider you will use anyway, or an invoice, and switch the account on by hand when it is paid. It is not scalable, and that is fine for the first customer. You are buying certainty that somebody will pay, not building a business process.
Before you charge, find out how tax and invoicing rules apply to a seller in your country selling to a buyer in theirs. They differ by place and by kind of product, and we cannot tell you your answer. A short read of your provider’s guidance, or an hour with an accountant, is cheap compared with fixing it afterwards.
What does the ask itself look like?
Short, specific and easy to decline. Edit the template to match the person and send it after a call or a message exchange, not cold.
Hi [name], you have used [product] on [number] different days now, and your last session was [what they did]. I would like to turn this into something you pay for, so it stays around and keeps improving. The price I am proposing is [price] per [period], and you can stop whenever you like. If that works, I will send an invoice today and make sure your account carries on exactly as it is. If it does not, I would really like to hear why, since that helps me more than a polite yes.
The last sentence matters. It makes a no easy to give and gives you the reason, which is usually a price, a missing feature or the wrong buyer. Each of those leads to a different next step.
Which numbers tell you it is working?
Track asks, answers and reasons. Count how many people you asked, how many said yes, how many said no and why, and how many days passed between the first ask and the first payment. Do not track revenue yet; one customer is a fact, not a trend. If you ask ten well-chosen people and none will pay at any price, treat that as information about the product or the audience, and go back to talking to users before you build more.
When someone does pay, ask whether they would write two sentences about what they use it for. The testimonial request template is built for that. If you have not yet found users to ask, start with the first 100 users playbook, and when you are ready to be found in public, you can launch your product on the board with no account and no queue. The guide to making money from an app lays out the models you might move to next, and the ideas board is a good place to see what problems builders say people would pay to solve.
Frequently asked questions
Should I charge before my product is finished?
You can, if you are honest about what exists today. A customer who pays for an early version knows the rough edges and the plan. Be explicit about what is not built, give a way out, and keep the promise small. Charging early is a stronger test of demand than any amount of free feedback.
What if nobody will pay?
Ask the people who said no why, and write down their exact words. A no tied to price means you should test another price. A no tied to a missing feature means you should build that feature or confirm it is the real blocker. A no from the wrong buyer means you should change who you ask.
Do I need a pricing page before the first customer?
No. A pricing page is useful once strangers arrive on their own and need to decide without you. Your first customer comes from a conversation, so a clear message and a payment link are enough. Build the page after you have heard what people say when you tell them the price.
Is a pre-order the same as a paying customer?
It is a weaker signal, because the product is not in use yet, but it still costs the buyer money, which makes it far stronger than a waitlist sign-up. Treat a pre-order as a promise to keep: deliver on the date you gave, or refund it without argument.
Written by Post your build ideas with AI assistance and edited for this site. Where a page names another product, the facts came from that product’s own pages on the date shown above; terms change, so check them before you rely on them. About the publisher.