How to get your first MRR
A step-by-step path from a rough idea to your first paying subscriber, with what to do in each week and the mistakes that cost first-time founders months.
Your first MRR is the first recurring payment from someone who is not a friend, a relative or a colleague doing you a favor. It is usually a small number, often less than a dinner out, and it matters more than any number that comes after it because it is the first proof that a stranger will keep paying for what you made.
This guide is the order we would follow if we were starting from zero today. It assumes you have an idea, or a rough area you care about, and no product yet.
1. Pick a problem you can reach this week
The best first idea is rarely the biggest one. It is the one where you can name ten people with the problem and talk to five of them before Friday. If you need a marketing budget just to meet your first potential customer, the idea will stall long before it earns anything.
Good starting points are problems you have had yourself, problems your current job is full of, and communities where you already spend time. A bookkeeper who has watched clients lose receipts for years starts with an advantage over someone who read that receipt apps are a big market.
2. Talk to people before you build
Before writing a line of code or opening a no-code builder, have ten to fifteen conversations with people who match the customer you have in mind. You are not pitching. You want to hear how they handle the problem today, what it costs them, and whether they have already tried to fix it.
The questions you ask decide whether you get facts or compliments, so they deserve their own guide: customer interview questions for your first business.
The strongest signal from these calls is a workaround. Someone who keeps a messy spreadsheet, pays a freelancer or loses two hours every Monday to the problem is already spending something on it, which means they might spend money on a better option.
3. Write the offer in one sentence, with a price
Once you have heard the same problem described several times, write down what you will sell in one sentence: who it is for, what they get, and what it costs. For example: “Freelance designers get their unpaid invoices chased automatically for $12 a month.”
Put a price on it from the start. A free beta tells you who likes free things, and turning those users into paying customers later is much harder than charging the right people from the first day. Pricing your first version too low is the more common mistake, because a low price attracts people who are not sure they have the problem.
4. Ask for money before the product is finished
Go back to the people who described the problem most clearly and ask them to pay, or put down a deposit, for the first version. A simple page with the offer and a payment link is enough. Some will say no, and that is useful information too.
One pre-sale is worth more than a hundred waitlist signups, because paying costs something and signing up costs nothing. Our guide on validating a business idea explains how to set the bar before you start, so the result does not get reinterpreted afterwards.
5. Build the smallest version that delivers the result
Your first customers are paying for an outcome, not for features. The first version should deliver that outcome, even if part of it happens by hand behind the scenes. If the promise is “invoices chased automatically”, sending the reminders yourself from a template for the first five customers is a legitimate way to start.
Paul Graham describes this in his essay “Do Things That Don’t Scale”: early on, the manual work is how you learn what the product should do. Automate a step once you have done it often enough to know exactly what it involves.
6. Get the first ten customers one at a time
The first ten customers almost never come from a launch post. They come from people you talked to, introductions those people make, and communities where your customers already ask for help. Each one is found, contacted and converted individually.
We cover where they come from and how to reach them without spamming anyone in how to find your first 10 customers.
7. Count your MRR correctly
MRR only includes recurring revenue, converted to a monthly amount. An annual plan at $120 adds $10 of MRR, not $120. One-time fees, setup charges and free trials do not count. Counting this way from the first customer keeps you honest about whether the business is growing. The full method, with examples, is in what is MRR.
An example six-week plan
This is an illustration of the order above, not a promise of how long it takes. Some ideas move faster, and plenty of good ones take longer.
| Week | Focus | Done when |
|---|---|---|
| 1 | Choose a reachable problem and list people who have it | A list of at least 20 names or places to find them |
| 2 | Customer conversations | 10 to 15 calls, notes written the same day |
| 3 | Offer and price | A one-sentence offer and a payment link |
| 4 | Pre-sale | Clear yes or no answers from the people you spoke to |
| 5 | Smallest working version | Paying customers receive the promised result, even if partly manual |
| 6 | Next customers, one by one | A tracked list of conversations and outcomes |
Mistakes that cost first-time founders months
- Building for months before talking to anyone. The longer the build, the harder it becomes to accept what customers say.
- Counting friends as customers. They pay to support you, which tells you nothing about strangers.
- Treating signups as revenue. A waitlist measures curiosity, while a payment measures demand.
- Changing the idea every week. If you switch before ten conversations, you never collect enough evidence to judge any of them.
- Waiting for a launch. Your first customers will come from direct conversations long before any launch day matters.