Flat rate pricing: quote one price, and price in the overrun

Flat rate pricing means charging one fixed price for a defined job or plan, whatever it ends up costing you to deliver. Use flat rate pricing when you can write down exactly what the price buys and you have delivered something like it before; then add a buffer for the overrun, because your own estimate will almost certainly run short.

Guides such as HubSpot's show the formula (hours times rate, plus materials) and move on. The hard number in a flat price is the hours, and the research on how people estimate their own work says the first guess is low.

1. Choose a flat rate when the buyer is paying for an outcome

A flat price sells a result. The buyer knows the cost before they say yes, and you keep any hours you save by working faster. HubSpot's guide gives the classic example: a designer who charges $400 for a logo, whether it takes one hour or 20 (HubSpot).

That trade suits buyers who have to get a number approved. A founder with a fixed budget, or a manager asking finance for a purchase order, would rather sign for $6,000 than for "$150 an hour, probably 40 hours." Hourly billing puts the overrun risk on the buyer. A flat rate moves it to you, and you should charge for carrying it.

It fits poorly in three situations, so check for them first:

The work is exploratory and nobody can say when it is finished ("help us figure out our pricing").
The buyer controls most of the inputs, such as how fast they send data or how many people must approve a draft.
You have never done this kind of job, so you have nothing to estimate from.

For those, bill by the hour (see what consultants charge per hour). If the client insists on a fixed number, sell a short paid discovery phase first and quote the flat price for the work that follows it.

2. Assume your estimate is short, because almost everyone's is

Psychologists call this the planning fallacy: people predict that their own tasks will take less time than they do, even when they know similar tasks ran late before. In a 1994 study by Buehler, Griffin and Ross, 37 students estimated how long their senior theses would take. The average prediction was 33.9 days. The average actual time was 55.5 days, and only about 30% finished by the date they predicted (Wikipedia summary of the study).

The detail worth remembering: the students' average "worst case" estimate was 48.6 days. The real average ran about a week past their worst case. If you price a flat project on your worst case, you may still be short.

Professional projects show the same pattern. Bent Flyvbjerg and Alexander Budzier analyzed 1,471 IT projects and found an average cost overrun of 27%. One project in six was what they called a black swan, with an average cost overrun of 200% and a schedule overrun of almost 70% (Flyvbjerg and Budzier, 2011). Your logo is not an enterprise software rollout, but the direction of the error is the same, and the long tail is the part that hurts a flat-rate seller.

Short version: estimate from what similar past jobs actually took, not from how long this one feels like it should take.

3. Build the price from past jobs, a buffer and your hourly floor

Here is a made-up example to show the arithmetic. Dana is a freelance analyst who builds competitor pricing teardowns for SaaS startups. Each one ends with a spreadsheet and a 20-minute readout call. A new client asks for a flat quote.

Start from past jobs. Dana has done four teardowns. Her time logs show 22, 26, 31 and 35 hours. The average is about 29 hours. Her gut said 20, which is the planning fallacy at work.
Pick a planning number above the average. She plans for 35 hours, the length of her slowest job. Using the slowest real job, rather than the average, is a simple way to cover the jobs that go long.
Multiply by the hourly rate you would accept. At $150 an hour, 35 hours is $5,250. This is her floor: below it, she would rather bill hourly.
Add a price for carrying the risk. Dana adds 15%, about $790, because she is promising a fixed cost and the client is not. The quote rounds to $6,000.

The 15% is Dana's choice, not a market standard. The point is that it exists and has a reason. If her logs had shown a wider spread (say 15 to 60 hours), she would raise it, or she would decide the job is too unpredictable for a flat price.

If Dana's work gets faster with practice, her effective hourly rate rises while the client's price stays the same. That is the reward for carrying the risk, and it is fair.

For the minimum price under any quote, cost plus pricing covers how to count your costs. For the ceiling, value-based pricing shows how to work out what the result is worth to the buyer. A flat rate set from your hours is the floor; if the client's numbers say the work is worth far more, price closer to that.

4. Write the scope as a list of deliverables, with a price for extras

A flat price is only as safe as the description of what it buys. HubSpot lists scope creep first among the drawbacks of flat rates: the job grows and the price does not (HubSpot).

Write the scope so a stranger could tell when the job is done:

Name each deliverable and its format ("one spreadsheet comparing eight named competitors, one 20-minute readout call").
Say how many rounds of changes are included, as a number.
Say what the client must supply, and by when.
Put a fixed price on each kind of extra work outside the list.

The last line matters most. Without a stated price for extras, every "small" request turns into a negotiation, and you will usually lose it, because arguing over $300 feels petty when the client has already paid $6,000. With a price written in advance, saying "happy to, that is an extra $400" is just reading the contract back.

If you need a template, our guides to a consulting proposal and a consulting agreement show where the scope and change terms go.

5. In software, a flat plan works while heavy users cost you little

A flat-rate SaaS plan is one price for access, however much a customer uses it. Basecamp is the well-known example. Its Pro Unlimited plan costs $199 a month billed annually, or $329 billed monthly, with unlimited users and no per-user fees; the company describes it as one fixed, capped price (Basecamp pricing).

The model works when an extra user or an extra project costs the seller almost nothing to serve. It breaks when heavy users drive real costs. Zuora's glossary names the two problems: heavy users pay less than the value they get, which caps expansion revenue, and one price can be too high for small customers and too low for large ones. It also warns that a pure flat rate becomes a constraint once a product adds usage-heavy features such as APIs, data or AI inference (Zuora).

Basecamp itself shows the usual fix. Its smaller plans are also flat, but they cap projects, storage and users, which is really a set of tiered prices (Basecamp pricing). Zuora describes that path as common: start with one flat plan, then add tiers or usage-based charges as the business grows (Zuora).

Use a single flat plan if you can name the cost of your heaviest likely customer and it still leaves a margin. If your costs grow with every API call or model query, read usage-based pricing first. If you are still deciding between monthly and annual billing, see subscription pricing.

6. Test the number with someone who has bought or sold this exact job

Your time logs tell you what a job costs you. They do not tell you what buyers expect to pay. The quickest check is a short conversation with someone on the other side: a person who has bought this kind of work, or a seller who has quoted it many times.

Ask them two questions:

"What did you last pay for a job like this, and was it a flat price or hourly?"
"What made the final bill different from the quote?"

The second question finds the overrun you have not seen yet. A buyer might tell you their last vendor charged for every extra stakeholder interview, which tells you where your own scope needs a line.

If you do not know anyone who fits, you can reach specific people through Instant Expert, such as pricing strategy consultants or fractional CFOs. You set what they receive for a short call or a written answer, Instant Expert's fee is added on top, and you pay only if someone books or answers.

Quote from your slowest real job, then add a price for the risk

Pull up the time logs for your last three jobs of this type, take the slowest one, multiply by your hourly rate and add a margin for carrying the overrun. Write the deliverables and the price for extras into the quote before you send it.