How I Price Fixed-Scope Freelance Projects Without Losing Money
Learn how to price fixed-scope freelance projects profitably. Real formulas, common mistakes, and exact rates I charge now.
- Freelance & Client Work
- how to price fixed scope freelance projects
I quoted a 40-hour website rebuild for 120,000 LKR in 2019. I thought I was being careful. I had a time estimate. I had a scope document. Then the client asked for a color change, a layout shift, and 'just one more integration' - and suddenly I was at 68 hours, earning 1,765 LKR per hour instead of 3,000. I learned that day that how to price fixed scope freelance projects is not the same as how to price hourly work. A fixed price is a bet, and I was betting with bad odds.
That year cost me. I burned out. I started charging differently. Now when I get a project brief, I don't just multiply hours by my day rate and call it done. I use a three-layer model that accounts for scope creep, my actual execution speed, and the friction of client communication. I've watched indie devs across Asia charging 500 rupees an hour for work that should cost 5,000 - not because they're slow, but because they never learned to separate estimation from pricing.
How I Used to Price Fixed-Scope Freelance Projects (And Why I Failed)
Most freelancers start the same way. You estimate how many hours a project will take (let's say 30 hours), you pick an hourly rate (let's say 2,500 LKR), you multiply them together and tell the client 75,000 LKR. Done, right? No. This math assumes you will never be interrupted, the client will never ask for revisions, the technology will work exactly as you assumed, and scope will stay locked. In my experience, that happens maybe 2 out of every 10 projects.
The real problem is that fixed-price contracts transfer risk from the client to you. They have no incentive to keep scope tight or feedback fast. You have every incentive to either bid so high that you never win, or bid so low that you work for free. I spent my first two years choosing option two. I'd bid 60,000 LKR on a project that took 50 hours because I was terrified the client would hire someone cheaper. Then scope would expand by 15 hours and I'd eat the entire overage. That's not being generous. That's being bad at business.
The Three-Layer Pricing Model I Use Now
Today I price fixed-scope work by stacking three separate calculations. First is the honest estimate: how long will this actually take, given my current speed and the client's tech stack? For a Laravel API with Vue frontend and 8 database tables, I estimate 45 hours because I've built that exact shape 12 times. I write that down. Second is the scope creep multiplier: I multiply that estimate by 1.3 if the client is a first-time hire (they ask for more revisions), or 1.15 if they're a repeat (they know how to brief clearly). So that 45 hours becomes 58.5 hours. Third is my real floor rate: what's the minimum I'll earn per hour after taxes and expenses? Today that's 3,500 LKR because I need to cover power, internet, laptop maintenance, and the 3 months a year I'm not billing.
Using that framework: 58.5 hours times 3,500 LKR equals 204,750 LKR. I'd quote 205,000 LKR, maybe 210,000 if the client is geographically awkward (they're in a 9-hour timezone difference, we'll need lots of async handoff). That price now has a real safety margin. If scope bloats 10 percent or a technology surprise adds 5 hours, I still hit my floor. If everything goes smooth and I finish in 42 hours instead of 45, I just made 5,000 LKR bonus - and I'm still profitable at the contract rate.
Building a Buffer Into How to Price Fixed Scope Freelance Projects
The multiplier is where most freelancers fail to add buffer. They estimate 30 hours and quote 30 hours-worth of money. They're treating the quote like an hourly gig, not a fixed contract. I spent 18 months doing that before I realized it was mathematically impossible to be profitable that way. The 1.3x multiplier for first-time clients isn't greed - it's acknowledgment of reality. First-time clients typically make 2 to 4 revision rounds (I've tracked this across 28 projects). Second-time clients average 1 revision round. That difference is real time, and you have to price for it.
Where does the buffer go? Revision time, of course - maybe 40 percent of it. Technical dead-ends and rework (I estimated wrong about how Django's ORM handles that edge case, now I need 4 extra hours to refactor) - maybe 20 percent. Waiting for the client to reply to questions - maybe 15 percent. Slack and Loom video explanations instead of documentation - maybe 15 percent. Miscellaneous (their designer gave me an Figma file that's useless, I have to build layout from screenshots, the Google Workspace integration docs are wrong). Maybe 10 percent. That's your 1.3x buffer, roughly distributed.
When to Walk Away From a Quote
Not every project is worth taking at your floor rate, even with a buffer. I walk away from projects if the client shows red flags that suggest scope will explode beyond my multiplier. The top signals: they have no written spec (they want to 'figure it out as we go'), they're unclear on budget (they ask what you charge, then negotiate down 40 percent), they have a history of projects (I ask, and they've hired 4 developers in 18 months and fired 3). Two weeks ago I passed on a 4-month contract at 2.8M LKR because the client had hired 3 developers for the same project and fired all of them. That's not a scope problem. That's a client problem.
I also walk away if the multiplier doesn't close the gap. A client wants a WordPress theme built on a tech stack I've never used (Statamic). My estimate is 60 hours, but I've never shipped with that technology - so I should be using a 1.5x or 1.6x multiplier (higher risk of unknown unknowns). That's 90 to 96 hours of work. If they'll only pay for 70 hours, the contract is upside-down. I'd rather spend 20 hours on my own product or bid on projects I know I can execute in half the estimated time.
The Contract Language That Protects Your Rate
Getting the price right is only half the battle. You need contract language that defines scope so tight that the client can't expand it without you charging more. I include three clauses: first, a detailed scope of work with deliverables listed line by line (3 API endpoints, 5 Vue components, database schema with these 12 tables, this exact authentication flow). Second, a revision clause (unlimited revisions on the deliverables listed above, beyond this scope is out of scope and billed hourly at 6,000 LKR). Third, a change order process (if you want anything added or significantly modified, we document it, I estimate the hours, and we agree on the new price before I start).
The magic is that last clause. It lets you say yes to scope creep without eating it. Client asks for a new report feature that wasn't in the original spec. You estimate 8 hours, tell them it's 28,000 LKR extra, and they either green-light it or they don't. You don't do it anyway hoping they'll be grateful. I've used this exact language on 15 projects in the last 18 months and never had a client push back - because they can see the original scope and they can see exactly what the addition costs. It's fair. It protects both of you.
Start this week: take your last three fixed-price quotes and reverse-engineer your own multiplier. How long did they actually take, divided by your estimate? If it's above 1.1x, you're underestimating. If your average across projects is above 1.25x, your floor rate is too low. You can't fix old work, but you can fix the next bid. Write down your real floor rate in LKR, rupees, or whatever your currency is. Then take your next estimate and multiply it by 1.25, at minimum. That one change will add 200,000 to 500,000 to your annual income. I'd know - it added 380,000 to mine.