A 12-person dev shop I talked to last year had a rule: whoever wrote the proposal picked the number. Sometimes it was the founder, sometimes the PM who'd just come off a brutal client, sometimes an account exec who wanted to win badly. The prices swung by 40 percent for similar scopes of work, and nobody could explain why. That's not a pricing strategy, it's a mood ring. If your proposals are priced by whoever happens to be holding the pen, you are almost certainly underpricing some of them, and you probably don't know which ones.
In this guide
Start from what the work actually costs you Price the risk, not just the hours How you present the number matters as much as the number Discounting without training clients to expect it Frequently asked questions
Start From What the Work Actually Costs You
Most underpriced proposals share one root cause: the estimate was built on a rate card instead of on the actual cost of the people who will do the work. If your senior developer bills at $150 an hour but their fully-loaded cost, salary, benefits, tools, PM overhead, is closer to $90, and a proposal gets built assuming a junior can do the same work at $95 an hour, the math looks fine on paper and falls apart in week three when the junior needs twice the hours or the senior has to step in anyway.
Before you price anything, know three numbers cold: the fully-loaded hourly cost of each role you're staffing, your target utilization for that role over the engagement (not 100 percent, nobody bills 40 hours a week for a month straight), and the actual hours similar work has taken on your last three to five projects, not the hours you originally scoped. That last number is the one most firms don't have, because it lives in old timesheets nobody goes back and reads. This is exactly the gap a connected system closes: when time tracking and project data sit in the same place you build proposals, you can pull "what did the last five projects like this one actually take" in minutes instead of guessing. Autovella's features page covers how time, projects, and CRM data stay linked so that estimating a new deal isn't a cold start every time.
Once you have real hours and real cost, multiply. Don't average across roles and hope it nets out, price each role's hours separately, then sum. A proposal that blends a $60/hr designer and a $140/hr architect into one "blended rate" of $95 will look attractive and then quietly bleed margin the moment the mix of work shifts even slightly toward architecture, which it always does once scope conversations start.
How You Present the Number Matters as Much as the Number
A $48,000 proposal with one line item, "Website redesign, $48,000," reads as arbitrary even if the math behind it was rigorous. Break it into phases (discovery, design, build, launch) with hours and outcomes attached to each. Clients don't push back harder on bigger numbers, they push back harder on numbers they can't see the logic in. A breakdown gives them something concrete to negotiate against other than the total, "can we cut the third design round" is a much easier conversation than "can you just lower this."
This is also where fixed pricing usually beats hourly for anything with a defined scope. Hourly estimates invite clients to negotiate the rate, which is the one number that protects your margin on every future project too. Fixed milestone pricing lets the conversation happen at the scope level instead, where you have more room to trade, cut a deliverable, adjust a timeline, without ever touching the rate you charge everyone else. If you're building proposals inside a CRM that's disconnected from delivery, this gets harder, because you lose the feedback loop between what you quoted and what it actually took to deliver. A CRM built for project-based billing keeps that loop closed, so this quarter's proposals get smarter using last quarter's actual delivery data instead of the same spreadsheet formula everyone's been reusing since 2022.
One more thing worth saying plainly: a lower price rarely wins you a better client. It wins you a client who now expects every future ask to be priced the same way. If a $60,000 project gets discounted to $45,000 to close it, the next scope addition gets negotiated against that $45,000 baseline forever, not against what the work is worth.
Discounting Without Training Clients to Expect It
Discounts aren't the enemy, undisciplined discounts are. If you're going to move off your number, move on scope, timeline, or payment terms first, and only touch the rate as a last resort with a clear reason attached (a multi-year commitment, a case study you genuinely need, a slow month you're trying to fill). Every discount should have a reason a colleague could repeat back to a client without flinching. "We knocked 15 percent off because it's a 12-month retainer paid quarterly in advance" is defensible. "We knocked 15 percent off because they asked" is a policy that will eat your margin one client at a time.
Track what you actually discount and why, even if it's just a note on the deal record. After a couple of quarters you'll usually find a pattern, maybe every proposal from one salesperson gets discounted 20 percent, or every deal in a certain industry does. That pattern is data you can act on, either by pricing that segment differently from the start or by having a direct conversation about what's driving the discount habit. You can see how deal-level notes, quotes, and win/loss data connect in the pricing overview, which is worth a look if your team is currently tracking this in someone's head instead of a system.
See how your quotes, delivery hours, and margin connect
Get a live walkthrough of how Autovella links CRM deal data to real project hours so your next proposal is priced on facts, not memory.
Frequently asked
For most agencies and consulting firms, 45 to 55 percent gross margin on the direct delivery cost is a reasonable target before accounting for sales and overhead. If your real fully-loaded margin lands under 35 percent once you subtract PM time, rework, and tools, the proposal was probably priced too close to raw cost and left no room for the unplanned hours every project generates.
Price the internal math by the hour, always, so you know your true cost basis. Present the client price as a fixed fee or milestone-based number whenever the scope is well-defined, since fixed pricing protects your margin from scope creep and is easier for a client to approve than an open hourly estimate.
Show the breakdown behind the number instead of just defending the total. Walk through the roles involved, the hours per phase, and what happens to timeline or scope if the budget has to come down. Clients rarely argue with a well-reasoned breakdown; they argue with a number that looks like it was picked out of thin air.