How to Price Custom Software Work Without Underselling or Losing the Deal
- Fixed-price projects create an adversarial relationship: the client wants maximum scope, the agency wants minimum effort. Both lose. Fixed price works only when scope is genuinely fixed and change risk is low — almost never true for integration projects.
- Time-and-materials is transparent but creates anxiety for clients who cannot predict final cost. The solution: T&M with a budget ceiling and monthly scope reviews.
- Value-based pricing — charging a percentage of the value the software creates, not the cost to build it — is the highest-margin model and the most client-aligned. It requires the confidence to sell it and the client relationship to support it.
- The most common pricing mistake: undercharging for complexity, overcharging for simplicity. Clients remember both and neither builds long-term trust.
Pricing custom software is one of those problems where there is no formula — only frameworks, judgment, and pattern recognition built from watching many projects succeed and fail. Most agencies start with hourly rate times estimated hours, learn that estimates are wrong half the time, and spend years evolving toward something more nuanced. Here is the evolution compressed.
Why Fixed Price Creates the Wrong Incentives
When a client buys a fixed-price integration project, they are incentivised to add scope (“while you’re in there, can you also…”) because there is no marginal cost to them for each addition until the contract fights start. The agency, having fixed the price, is incentivised to cut scope and deliver minimum viable. Both parties are optimising for their own interest, not the outcome. This is why fixed-price projects have change order disputes — the model builds conflict in.
The T&M Ceiling Model
Time and materials with a budget ceiling addresses the client’s concern (I won’t get a surprise invoice for double my budget) while preserving the agency’s ability to scope honestly. The ceiling is not a cap on quality — it is a trigger for scope conversation. When the project approaches 80% of the ceiling, both parties review: is the remaining work necessary? If yes, extend the ceiling with shared agreement. If no, cut scope together. This model creates aligned incentives.
Value-Based Pricing in Practice
If a custom NetSuite integration automates a workflow that currently costs a client £8,000/month in manual processing staff time, and the integration pays back in 4 months, the value created is roughly £80,000 in year one. Charging £15,000 for the integration (which took 6 weeks at a standard rate) is leaving significant money on the table. A value-based price might be £35,000–£45,000 — still a 2x payback in year one for the client, but a significantly better margin for the agency. Value-based pricing requires the confidence to present the ROI case, and the client relationship to make it credible.
References
- ProfitWell — Value-Based PricingProfitWell (Paddle) — value-based pricing methodology for software and services businesses.
- Bain — T&M vs Fixed PriceBain & Company — analysis of time-and-materials vs fixed-price contracts and client alignment.
- Thoughtbot — Pricing Consulting ProjectsThoughtbot — practical pricing guide from an established software consultancy’s experience.
Leave a Reply