Building a freelancing playbook for web developers — would love your feedback

The hardest part is usually pricing confidently before you have proof of results. Advice that stuck: quote against the client's outcome, not your hours. Good luck with the guide.

One thing I’d add is turning the first project into recurring work. Maintenance, SEO, analytics, and small improvements can be more valuable than constantly hunting for new clients.

You're reaching into the sales/marketing side and finding it daunting, welcome to consulting haha. You'll find that you're selling yourself almost as much as selling your work, and the networking and relationships formed from a solid portfolio will start opening doors. The trick is to manage expectations on both sides, have ironclad communication, and strive to over-deliver while meeting requirements and timelines. And as another commenter noted, scope creep is the silent killer of project deliverables.

The hardest part of freelancing for devs isn't the stack but the transition from being a builder to a consultant. Instead of just teaching how to get clients, I'd suggest focusing on how to audit a potential client's business pain so the dev can sell 'outcomes' rather than 'hours'. Most developers fail here because they try to sell a website when the client is actually looking for an increase in leads or operational efficiency. If your guide can help them map technical tasks directly to client revenue, it will be much more valuable than typical outreach templates.

Answering your three questions directly since you asked:

Hardest part starting out: figuring out which clients to say no to. Early on, the instinct is to take everything because every project feels like validation. But a bad-fit client costs you three to four times the revenue in time, energy, and opportunity cost. I had no framework for disqualifying early, which meant I learned who the wrong clients were by working with them. That's expensive.

Advice that actually helped: reframing the discovery call as a mutual evaluation, not a pitch. Most developers go in trying to convince the client to hire them. The better posture is: I'm deciding if this is a project I want to take. That shift changes how you ask questions, how you respond to low-ball offers, and how confident you sound — which, counterintuitively, makes clients more likely to hire you.

Myth people still believe: being fully booked means you're doing well. Full utilization with low rates and high-maintenance clients is one of the worst positions in freelancing. It looks like success and feels like a ceiling.

One thing that might be missing from your list: a section on minimum viable client criteria. Before positioning, pricing, or proposals, a developer needs a clear definition of which clients are worth pursuing and which aren't — and the discipline to stick to it when cash flow is tight. That filter makes everything else in your list work better.

One thing worth checking against your chapter list: in the freelancer threads I've been reading (research project, mostly Reddit), the complaint that keeps repeating isn't "I can't find clients" — it's what happens after the contract is signed. Scope creep specifically. The same story over and over: price agreed, then "small" additions pile up mid-project, and the dev either eats the extra work or has an awkward fight they never priced in. The people writing those posts mostly had clients. What they didn't have was a script for the moment the client says "can you also just…".

So if your proposals & contracts chapter has an actual word-for-word way to handle mid-project additions (a change-order template, when to say it, how to price it), that alone would separate it from the generic advice you're describing. Most guides cover how to win the deal and go silent on how to defend it.

Is that something you're covering already?

Solid initiative. One thing I'd add from my own freelance experience: pricing transparency early in the sales process saves a ton of back-and-forth. I run a full sales process for ERP/SaaS missions and the biggest time-sink is always scope creep before pricing is locked.

The categories you named are exactly right, and I'd add a third gap: almost nobody writes about what happens after you land the client. Positioning and pricing get you the first project. What actually builds repeat business is boring stuff, following up at the right moment, remembering what you promised in the discovery call, not letting a proposal go cold because you got busy on delivery. Most freelancers I've talked to lose more revenue to forgetting than to bad pricing. Curious what you're planning to cover on the "building repeat business" side, is it more about the relationship habits, or more about systems/tools for staying on top of it?

I think what you're creating is awesome. I just built an app for freelancers that quietly handles your books while you actually get some sleep...lol! It's like having your own accountant for just $20 a month
I would be happy to share your stuff if you wouldn't mind sharing mine. 😉

I think the distinction between knowing how to build and knowing how to consistently get clients is really important. ~

A lot of developers learn the technical side first and only later realize how much of freelancing is communication and positioning.

I appreciate how it sheds light on the not-so-glamorous aspects, like pricing, discovery calls, proposals, and getting repeat business - these areas often have the biggest gaps that need to be addressed.

I've come to realize that tips on finding clients can be really specific to each person's situation. What might work great for someone with a lot of connections can be pretty much useless for someone who's just starting out with no network at all. It's like they're in two different worlds, and what helps one person might not even apply to the other.

The idea of making the guide practical rather than another collection of generic advice makes sense. I’d be especially interested in the parts around turning a first project into repeat work.

One layer this list understates: professional delivery isn't just "do good work," it's the paperwork trail around the work. Talking to freelancers while building Alisio, an invoicing app for people who bill clients across borders, the complaint that comes up unprompted, more than pricing anxiety, is that clients quietly downgrade trust after messy invoicing: wrong currency, inconsistent numbering, a PDF that looks improvised. Nobody churns a freelancer over that alone, but it's the tiebreaker when a client decides whether to send the next project your way or shop around. Positioning gets you the first job. The boring operational stuff, contracts, invoices, how you close out an engagement, is what gets you asked back without having to sell yourself again. Worth a section of its own, not folded into "professional delivery" as an afterthought.

The hardest part is usually pricing confidently before you have proof of results. Advice that stuck: quote against the client's outcome, not your hours. Good luck with the guide.

You already have a fairly clear thesis about why developers struggle with freelancing.

Before structuring the playbook around it, how much of that came from recurring patterns you've seen across other developers versus your own experience and observations?