Most services firms do not die from a lack of clients. They die slowly from work that looks busy and pays poorly. The calendar is full, the team is stretched, and at the end of the quarter there is less cash than anyone expected. When I trace that back, the root cause is almost always pricing: rates set by guesswork, discounts given to win deals, and scope that grows while the invoice stays the same.
I learned this the hard way. As a partner, I helped grow a software consulting company from about $6M to $60M in under three years, and later I founded a fully remote consultancy. Growth only worked when pricing was deliberate. When it was not, we simply did more work for the same money. If you are trying to figure out how to price software development services, here is the approach I would use today.
Start From Cost, Then Climb to Value
Before you can price well, you need to know what an hour of delivery actually costs you. Not just salary, but the fully loaded number: benefits, tools, management time, recruiting, bench time between projects, and the hours nobody bills, like internal meetings and estimates for deals you lose.
Take total delivery cost for a role and divide it by realistic billable hours, not theoretical ones. A developer who is available 2,000 hours a year might bill 1,400 to 1,600 once you account for holidays, ramp-up, and gaps. That loaded cost is your floor. Anything below it is a donation.
Then decide your target gross margin. Many healthy services firms aim somewhere in the 40 to 50 percent range on delivery. If your loaded cost is 50 dollars an hour and you want 45 percent margin, your rate needs to be around 91 dollars, not 60.
Cost sets the floor. Value sets the ceiling. A team that ships a payment integration that unlocks a new revenue line is worth more than a team that closes tickets, even if the hours are similar. Price within that band, closer to value the more specialized and proven you are.
Pick a Pricing Model That Matches the Risk
There is no single correct model. There is a correct model for each kind of work.
Time and materials fits discovery, evolving products and long engagements where scope will change. It protects you from estimation risk, but clients carry the uncertainty, so you need trust and transparent reporting.
Fixed price fits well-defined work with clear acceptance criteria. It can earn better margins when you estimate well, and it can destroy margin when you do not. Only fix the price when you have fixed the scope in writing.
Retainers or dedicated teams fit ongoing product work. They give the client predictable capacity and give you predictable revenue. Price them on the team, not on hours, and review the composition every quarter.
Value-based or outcome pricing fits work where the business result is measurable and you control enough of the delivery to influence it. It is powerful, but only use it when both sides agree on how the result is measured.
The mistake I see most often is using fixed price for vague work to win the deal. That is not a pricing model. It is a bet you will probably lose.
Protect Margin Inside the Engagement
Signing at a good rate is half the job. Margin leaks out during delivery.
Write scope as outcomes plus boundaries. Say what is included, and just as clearly what is not. "Integrations with third party systems not listed above are out of scope" saves more arguments than any clever clause.
Make change easy to price. Agree up front on how change requests work: who approves them, how they are estimated, and how they hit the invoice. Clients do not mind paying for change. They mind surprises.
Watch staffing mix. A project priced for a blend of senior and mid-level engineers quietly loses margin when it ends up all senior because nobody else was free. Track planned mix against actual mix every month.
Measure utilization and realization separately. Utilization tells you how busy people are. Realization tells you how much of that time you actually got paid for. A firm can be 90 percent utilized and still lose money if write-offs pile up.
Review margin by project, monthly. Not at the end. By the time a project closes, the loss is already locked in.
Avoid the Discounting Trap
Discounting feels like a small favor to win a deal. In practice it resets the client's sense of your value, and it rarely comes back up. A 15 percent discount on a project with 40 percent margin does not cost you 15 percent of profit. It costs you closer to 37 percent of it.
When a client pushes on price, trade, do not cave. Reduce scope, extend the timeline, swap a senior role for a mid-level one with more oversight, or ask for a longer commitment in exchange for a better rate. Each of those gives the client something real while protecting the economics.
If you do discount, make it visible and temporary. Show the full rate on the proposal, show the discount as a line item, and tie it to something specific, like a pilot phase. That way the conversation about returning to full price is already set up.
And be willing to walk away. Some clients only buy on price. They will leave the moment someone cheaper appears, usually after demanding the most attention. Losing those deals is part of a healthy pipeline.
Raise Rates Without Losing Good Clients
Clients who value your work expect rates to move over time. What upsets them is a surprise.
Review rates once a year. Give existing clients 60 to 90 days of notice, explain the reason in plain language, and apply increases at renewal or on new work rather than mid-project. Pair the conversation with a short recap of what you delivered. Good clients rarely leave over a fair, well-explained increase. They leave when quality slips or communication goes quiet.
New clients should always start at your current rate. Grandfathering old rates into new relationships is how a firm ends up with a price list nobody remembers agreeing to.
What Good Pricing Looks Like
A well-priced services firm is not the most expensive option in the room. It is the one that knows its numbers. It can tell you its loaded cost per role, its target margin, which projects are making money this month and which are not. It picks a pricing model to fit the work, writes scope that holds, and treats discounts as trades.
Clients stay with firms like that because the relationship feels stable. There are fewer surprise invoices, fewer tense scope fights, and a team that is not burned out from underpriced work. Making money and keeping clients are not competing goals. Good pricing is how you get both.
If you are working through rates, margins or pricing models for your services firm and want an experienced view, visit https://tdzpro.com.
Ashkan Rajaee is the founder of TDZ Pro. He has helped scale a software consulting company as a partner and founded and grew a fully remote software consultancy.
Top comments (0)