How I got my first client (before I felt ready)

There's a moment every tutorial carefully avoids: the one where a real person asks you to build a real thing for real money, and you have to answer before you feel qualified to. Mine came in 2021. I said yes, and I want to tell you what actually happened next — including the parts that went wrong — because the sanitized version of this story is why so many capable people never send an invoice.

Nobody was going to ask me

First, the part people get backwards. I didn't find my first client. I didn't cold-email anyone, didn't build a portfolio site, didn't post "open for work" anywhere. A business owner I already knew mentioned, in a completely ordinary conversation, that their website was embarrassing and the guy who made it had disappeared.

I heard that sentence and felt two things at once: I could probably do that and I am absolutely not qualified to do that. Both were true. I'd been building things at night for months — templates, YouTube tutorials, half-finished experiments. I was not a computer scientist. I had never shipped anything anyone depended on.

Here's what I've learned since, watching students go through the same moment: the first client is almost never found. They surface. They're already in your life — the gym owner, the cousin with a restaurant, the friend of a friend with a clinic — and they have a broken or missing website they think about with low-grade dread. The only thing that changes when you start building is that you begin to hear these sentences. They were always being said around you. You just weren't the person who could answer them yet.

So I answered. Something like: "I build websites. Want me to sort it?" No portfolio. No process. One true sentence — I did build websites, at midnight, badly — and one offer.

They said yes. That was the entire sales process. It usually is.

What went wrong (almost everything)

Now the parts the success stories skip.

I never wrote down what "done" meant. We agreed on "a new website" — verbally, enthusiastically, and with two completely different pictures in our heads. I thought five pages. They thought five pages, plus a gallery that was easy to update, plus "small changes whenever." The project had no edges, so it couldn't end. Weeks after launch I was still getting messages that started with "quick thing —".

I charged at the end, and I charged almost nothing. No deposit, because asking for money up front felt presumptuous for someone with no track record. So I carried the whole project on my own motivation, and when that dipped — week three, when the novelty was gone and the gallery plugin was fighting me — there was nothing holding the project up. The final number was small enough that I'm not going to type it here, because you'll be tempted to use it as a reference. Don't. It was a fraction of what the same site bills today, and the client would have paid several times more without blinking. I know because they later told me so.

Revisions had no boundary. "Can we try the logo bigger" is a fine request. The fourteenth "can we try" is a process failure — mine, not the client's. Clients aren't difficult; unbounded projects are.

The handoff was a mess. The domain was registered under the old developer's personal account. I'd never touched DNS. What should have been an hour of setup became a week of support tickets and forum threads at 1 a.m. Nobody warns you that the hard part of web development is rarely the website.

Every one of these mistakes had the same root: I treated the project as a favour I was lucky to get, instead of work being exchanged for money. The client, ironically, always treated it as the second thing. They were more professional about my work than I was.

What the invoice changed

And yet. The site shipped. It was fine — genuinely fine, not secretly terrible. The client was happy, their customers found them, and the embarrassing old site was gone.

Then I sent the invoice, and something disproportionate happened. The amount was almost irrelevant. What mattered was the category shift: I was now a person who had been paid to build a website. Singular, small, riddled with process errors — but real. The next conversation with the next potential client was different in kind, not degree, because "I build websites for clients" had stopped being aspiration and become description.

That's the uncomfortable truth of the title. Readiness didn't produce the work. The work produced the readiness. Every skill I actually rely on today — scoping, pricing, saying no, DNS — I learned because a live project forced me to, never from a tutorial in advance. Tutorials are rehearsal without a performance date. You can rehearse forever.

The work was real before the skills were complete. It took me years to fully accept that order. It's the entire premise of how I teach now.

What I'd charge today

The story ends in 2021, but the pricing mistake is timeless, so let's fix it properly — with numbers, because vague pricing advice is worthless.

The instinct to resist in 2026: "AI built most of it, so I should charge less." No. The client is not buying your hours or your tools — they're buying a finished, working website they didn't have to think about. That outcome had a market price before AI, and AI didn't lower it; it lowered your cost of delivering it. The margin between those two numbers is the entire point of learning this.

What I tell students, as a starting frame:

• First project ever: 800–1,500 in your local strong currency, 50% up front. Low enough that a small business says yes to an unproven person. High enough that both sides treat it as work. Never free — a free project teaches the client the work is worth nothing and teaches you to resent it.
• Projects two to five: 1,500–3,500 for a marketing site once you have shipped work to point at. Your proof, not your confidence, moves the number.
• After that: 3,000–8,000+ for sites with real moving parts — bookings, content the client edits, a backend. At this level you're pricing against the revenue the site produces, not against other freelancers.

And the two rules I broke, which cost more than any tool ever will: a deposit before work starts, always — it's not about cash flow, it's the moment the project becomes mutually real. And a one-page scope: pages, features, what's included, and the sentence "anything beyond this is quoted separately." That sentence, which costs nothing to write, is the difference between the fourteenth revision being a problem and being a line item.

If you're waiting to feel ready

You will not wake up ready. There's no final tutorial with an invoice at the end, no certificate that makes the first conversation comfortable. I felt like a fraud saying "I build websites" in 2021. The feeling was wrong about my potential but right about one thing: I hadn't done it yet. The only cure for that was doing it.

The mechanical version, if you want one: build one complete site this month — a real business type, invented client, full process, shipped to a live URL. Then listen for the sentence. Someone around you is saying "our website is embarrassing" right now. When you hear it, you say the one true sentence: "I build websites. Want me to sort it?"

Charge properly. Take the deposit. Write the scope. Everything I've built since — the studio, the process, this course — traces back to one underpriced, badly scoped, genuinely fine website in 2021, built by someone who was not ready.

You're not ready either. That was never the requirement.