A two-person design shop and a four-hundred-person engineering firm can quote the same project and arrive at numbers that are not in the same universe. The usual explanation is brand, or overhead, or nerve. The more boring explanation is that one of them has machinery and the other has a feeling. The big firm's number went through a rate card, a cost floor, a scope document and at least one person whose job includes refusing to discount. The small shop's number went through a drive home.
Worth saying plainly: most of that machinery is unnecessary at small scale. But three pieces of it are doing real work, and they are the three pieces that stop a business from underselling. It helps to know where they came from.
The hourly rate started as an accounting device, not a price
The billable hour was not invented to tell clients what work was worth. It came out of cost accounting, and out of government contracting in particular, where an agency buying engineering or research services needed a defensible way to reimburse a contractor who could not quote a fixed price for something nobody had built yet. The answer was cost plus a margin. To make that auditable, firms had to know what an hour of a given person's time cost them: salary, payroll taxes, benefits, and then a share of rent, insurance, software, admin staff and everyone who does not bill.
That share became the overhead multiplier. A firm figures out that for every dollar of direct salary it spends, it spends roughly another one and a half or two dollars keeping the lights on and the person employed. Multiply the hourly salary cost by that figure and you have break-even. Add profit and you have a rate. The Bureau of Labor Statistics tracks wages and employer costs across industries, which is part of why the inputs to that calculation are arguable rather than mysterious.
The second input is utilization. Nobody bills forty hours in a forty-hour week. A large firm assumes something like sixty to seventy-five percent of paid hours are billable, depending on the role, and prices accordingly. This is the step small operators skip almost universally. If you work fifty hours a week and bill twenty-five of them, your rate has to carry the other twenty-five. Quoting a number based on what you would like to earn per hour, times the hours you plan to work, produces a business that is busy and broke.
What the rate card is actually for
Large providers publish internal rate cards: a grid of roles and the hourly rate for each, sometimes with a separate column for government, nonprofit or long-term clients. The card is a pricing tool, but its more important function is institutional. It means a project manager in one office cannot quietly undercut a project manager in another, and it means the number a client hears is the same number regardless of who answers the phone.
Underneath the card sits a floor. The floor is the rate below which the firm declines the work, and it is usually set somewhere above break-even rather than at it. Crucially, the floor is enforced by someone who is not the person in the room with the client. Discount authority lives one or two levels up. A principal can approve ten percent; anything deeper goes to a committee or a managing partner.
That structure looks like bureaucracy and partly is. But strip it down and it is solving a specific human problem: the person who wants the job most is the worst person to decide what it costs. Separating the two is the entire mechanism. A solo operator can reproduce it by making the discount decision the day before the conversation rather than during it, in writing, with a number attached.
The change order, and why big providers rarely eat scope
The place small businesses lose money is almost never the headline rate. It is the work that gets added after the price is agreed. A client asks for one more revision, one more room, one more report. The request is small, the relationship is good, and saying yes costs nothing visible.
Large providers handle this with a scope statement and a change order process, and they handle it unsentimentally because an unbilled hour on a hundred-person project is a line item somebody has to explain. The scope statement says what is included and, just as usefully, what is not: number of revisions, number of site visits, what happens if the client's materials arrive late, who pays for a redesign triggered by a decision reversed at week six.
The small version is not a contract annex. It is three or four lines in the proposal under a heading that says what the price covers, followed by a sentence saying that work outside it is quoted separately before it starts. The sentence is not aggressive. It is the thing that lets you say yes to the extra room and send an invoice for it, instead of saying yes and resenting it.
The simplest version that still works
Most of what a large provider does with pricing is scaffolding for coordination across many people. You do not need the scaffolding. You need what it was holding up.
- A break-even number you have actually calculated. Annual costs including your own pay, divided by the hours you can realistically bill, not the hours you work. Recalculate it once a year.
- A floor, decided in advance. One number, written down, with a note on what circumstances would justify going below it. Review it when a quarter ends, not when a client pushes back.
- A scope line in every proposal. What is included, what triggers a new quote.
Three items. That is the whole system, and it fits on an index card. If someone is selling you pricing software before you have those three, they are selling you the scaffolding without the building.
The honest limit here is that none of this tells you what the market will pay. No multiplier produces that number, and large firms do not know it either; they find it by quoting and losing some. What the machinery does is make sure that when you lose a job on price, you lost it on purpose, and that the ones you win are worth having won.