What My First Paying Customer Taught Me About Launching

I started building GetWaitly in April. I launched in July. And then, for weeks, almost nothing happened.

A handful of signups. Some page views. No revenue. I refreshed the dashboard more times than I'd like to admit, hoping a number would move.

Then, on September 1, I got my first paying customer.

This is the honest story of the gap between "launched" and "first customer" — what actually moved the needle, and what a single user taught me that no launch checklist could.

The gap nobody warns you about

There's a lot of content about how to launch. There's much less about the strange, quiet period after you launch and before anyone pays you. Launch day itself was fine. The hard part was the silence that followed.

I'd read that "launch is not a moment, it's a process." What I didn't internalize is that the process is mostly waiting, iterating, and — if you're lucky — talking to the one person who shows up and tells you what's broken.

That person, for me, was Bachir.

How my first customer actually found me

I assumed my first customer would come from Twitter, or a community, or someone I'd been building in public with.

I was wrong. Bachir found GetWaitly by searching "waitlist creator" on Google.

He tried a few other tools first. He chose GetWaitly because, in his words, it felt "the most responsive and authentic" out of everything he tried — and because of the reviews about customer service, which he says he can now confirm.

That's a strange and useful lesson for a crowded category. In a sea of similar waitlist tools, the thing that won him over wasn't the longest feature list or the cheapest price. It was how the product made him feel: responsive, real, made by a person.

If you're building in a space where everyone has the same features (a form, referrals, emails), your differentiation may not be a feature at all. It may be how quickly you answer, how openly you communicate, and whether your product feels like it was made by someone who cares.

The ten days that followed

Getting a user is not the same as keeping one. Bachir did something most early users never bother to do: he tested everything, and he told me exactly what broke.

Over about ten days, he reported a steady stream of issues. Each one was a real bug that would have quietly cost other users:

• Profile links redirected to an error page. A share link for a profile pointed somewhere broken. He caught it, reported it, and I fixed it that first day.
• Welcome and confirmation emails weren't sending. This was the big one. New subscribers weren't getting their emails, which is fatal for a product whose whole job is emailing a waitlist. It took several rounds of back-and-forth to pin down the root cause. He kept testing after each fix, and eventually the emails landed.
• Broadcast replies carried the wrong address. He noticed that replying to a broadcast used the custom email address. That wasn't intentional — a good catch that became a fix.
• Email variables and the "Send test" button failed. The test button wasn't using the From/Reply-To you'd set on the broadcast, and the real delivery path had a queueing bug that could hide failures. Both fixed — and now the error message tells you the specific reason instead of failing silently.

Here's the part worth sitting with: I wouldn't have found most of these on my own, and I definitely wouldn't have found them as fast.

Early users who care will test your product harder than you ever will. They use it in ways you didn't imagine, from devices you didn't consider, with the patience to try something three times until it works. Your job is to make it easy for them to tell you what's broken — and to fix it visibly and quickly.

What made him actually pay

Bachir upgraded because of the welcome and broadcast emails — features that were on the paid plan. He'd been trying to get them working, we fixed the delivery issues, and the value became real.

That's the sequence that matters, and getting it wrong is expensive: make the paid feature work flawlessly before you put it behind a paywall. Every day a paid feature is subtly broken is a day a would-be customer walks away thinking the product doesn't work. Fixing the boring infrastructure — deliverability, queueing, reply-to headers — is not glamorous. It's the difference between a free user and a paying one.

What I'd tell another founder

A few things I now believe more strongly than I did in April:

Support speed is a moat. In a crowded category, being the founder who replies in hours — and ships a fix the same day — is a genuine advantage. It's also the easiest thing for a solo founder to offer that a funded competitor can't fake.

Your first users are co-builders, not testers. Bachir wasn't just using the product. He was shaping it. The bugs he found, the features he asked for, the praise he gave — that's the raw material of a better product. Treat the first ten users like collaborators and they'll act like it.

One user's request is a signal, not a roadmap. Bachir asked for conditionals in waitlist forms and translated pages. Those are real, useful ideas — and they go on a list, not straight to the top of the queue. n=1 tells you something might matter. n=10 tells you it does.

The launch isn't the milestone. The first paying customer is. Launch day is something you can plan. The first customer is something you earn, one fixed bug and one honest reply at a time.

Where this leaves me

I have a long way to go. A handful of users, a first paying customer, and a product that's better today than it was a month ago because one person took the time to tell me what was broken.

If you're in the quiet gap between launching and your first customer: keep going. Answer the person who emails you. Fix the bug they found. Make the paid thing work before you charge for it.

The first customer doesn't come from a launch. It comes from paying attention.

Bachir — thank you for testing everything, reporting the bugs, and sticking with it. This post exists because you took the time.

Ready to start collecting signups? Create your free waitlist in 5 minutes — no credit card required.

Related guides

• How to Get Your First 100 Users as a Solo Founder — the channels that actually bring early users, and why a waitlist compounds
• Launch Day Playbook: How to Convert Your Waitlist into Paying Customers — what to do on launch day and in the two weeks after
• Why Most Pre-Launch Campaigns Fail (And How to Fix Yours) — the failure modes that keep products from ever finding a customer
• The Solo Founder's Pre-Launch Playbook — the 30-day sequence that gets you to launch ready
• Best Waitlist Tools for Solo Founders in 2026 — how GetWaitly compares to the alternatives Bachir considered