Best Practice: Quotes, Projects & the Product Catalogue
A quote is a risk-allocation decision wearing a price tag. Whether a line bills Fixed Fee or Time & Materials isn't really a billing-mechanics choice. It decides who absorbs the cost if the work runs long: the client, on a T&M line, or the business, on a fixed one. Get that allocation wrong often enough and it shows up as margin quietly bleeding out of jobs that looked profitable on the quote.
Getting it right starts well before a quote is drafted, with how the product catalogue is built, and it doesn't stop at "won". A quote that wins has to hand off cleanly into tickets or projects, time entries, and eventually an invoice, without anyone having to re-decide what was already agreed. This guide covers that whole chain: the catalogue as the foundation, structuring a quote's tasks, what Fixed Fee and T&M actually commit you to, and how a won quote's labour lines carry their pricing all the way through to the invoice.
The catalogue is the foundation everything else resolves from
Every quote line, every ad-hoc product and every recurring charge ultimately points back to a catalogue item. Get the catalogue wrong and that error reproduces itself on every quote built from it, not just the first one.
Separate what's being sold from how it's priced. An item's category (hardware, software licence, managed service and so on) says what it is. Its billing type (one-off, recurring monthly, recurring annual) says how it charges. Keeping those as two independent choices, rather than baking pricing logic into the product name, is what lets the same catalogue serve both a quote and an ad-hoc ticket sale without duplication.
Labour doesn't live in the catalogue as a priced product. There's nothing to hardcode, because a labour line's rate is resolved per line at the point it's used. A labour line points at a labour role (plus any location or time modifier), and the rate comes from the billing agreement the quote was built against, falling back to the standard rates. Products are for things you sell; labour roles are for time you sell.
Category discipline pays off at the accounting end, not just on the quote. A two-level category hierarchy resolves to an account code (item override, then sub-category, then top-level category), so the catalogue is doing double duty as pricing structure and as the bridge into whatever accounting platform the invoice ultimately posts to. A catalogue built without that in mind usually means someone re-coding invoices by hand later.
Name items the way an engineer would say them out loud, not the way a spreadsheet column header would. The catalogue gets searched under time pressure, mid-quote or mid-ticket. A name that matches how the team actually talks about the product beats a precise but unfamiliar SKU every time.
A quote is rarely one billing model all the way through
It's tempting to treat Fixed Fee vs. T&M as a decision made once, for the whole quote. Real jobs don't usually sort that cleanly. A server migration might have a well-scoped cutover phase worth quoting Fixed, bolted onto a "troubleshoot whatever comes up during the two weeks after" phase that's genuinely open-ended and belongs on T&M. Forcing the whole quote onto one model means either padding the fixed price to cover the unknown part, or putting the well-defined part on T&M and leaving money on the table.
The fix is structural, not a compromise: break the quote into multiple tasks, and set the billing mode per task, not per quote. A well-scoped chunk of work goes in as Fixed; the open-ended part goes in as T&M; both sit on the same quote, priced from the same agreement, sent and won as one document. The client sees one coherent proposal, and the business carries exactly the risk it chose to carry, task by task, rather than all-or-nothing across the whole job.
What each model actually commits you to
T&M bills actual hours worked, at the resolved rate. The client pays for exactly what happened, no more and no less, which means the client is the one exposed if the job runs longer than expected. This is the right call wherever genuine ambiguity exists: diagnosis before the fault is understood, a migration with an unknown number of edge cases, anything where quoting a number up front would mean guessing. There's no padding needed to absorb the unknown, because the unknown is priced as it happens rather than estimated in advance.
Fixed bills the quoted hours at the quoted rate, locked, regardless of actual hours. The business is the one carrying the risk here: run under the estimate and the margin improves; run over, and that's absorbed, not passed on. That trade only makes sense when the scope is genuinely well understood, a task the team has done enough times to estimate confidently, not a first-of-its-kind job dressed up as fixed because the client asked for price certainty. A fixed price never recovers from scope that creeps in without a change order. If the job's shape changes mid-stream, that's a new line or a new quote, not quietly absorbed labour on the existing one.
Set the model by where genuine uncertainty actually lives, not by habit or by what's easiest to explain to the client. A team that defaults to Fixed for everything is quietly taking on open-ended risk it never priced for; a team that defaults to T&M for everything is handing every client an unpredictable bill even on work that's perfectly well understood. Both defaults cost money, just in different directions.
What "won" actually hands off
The moment a quote is won, the decisions made while drafting it need to carry forward intact. An engineer picking up the resulting ticket shouldn't have to re-derive what was quoted from the PDF.
A won quote seeds labour lines as tasks (on the ticket, or on the project) with one task per quote line, carrying that line's billing mode with it. It also seeds products onto the ticket: one-off items land ready to invoice, and anything recurring is seeded ready to be placed on a billing agreement, because recurring charges can't go live without one. Nothing quoted gets silently dropped between winning and the work starting.
The quote's billing agreement travels with it too. A quote references an agreement the same way a ticket does, defaulted to the client's own default agreement, with an explicit "no agreement, standard rates" option when that's genuinely the right call rather than an oversight. Labour lines price from whichever agreement the quote was built against, and changing that agreement while the quote is still a draft re-prices every labour line against it. Once the quote is sent or won, prices freeze: a later rate-card or agreement change never reaches back to rewrite what the client already agreed to pay.
How a logged entry finds out what it bills
An engineer logging time against quoted work doesn't pick Fixed or T&M themselves, and doesn't need to know which the task was quoted as. That decision was already made when the quote was built, and the system carries it forward automatically.
Time entries come in two modes. Standard resolves its rate the normal way: a labour role, priced through whatever agreement the ticket carries. In Quoted Work mode the engineer picks the specific task, and the task governs everything else about how that entry bills.
| Task was quoted as | What a Quoted Work entry does |
|---|---|
| T&M | Bills at the resolved rate for the actual time worked, like any standard entry. |
| Fixed | Lands on a non-billable "Quoted Work" placeholder. It's tracked and visible for internal purposes, but doesn't create a separate invoice line, because the client already agreed a locked amount for the task. |
That resolution isn't frozen onto the task at creation. It's looked up every time an entry is logged, by following the task back to its quote line and the labour role chosen there, and falling through to the placeholder only if nothing in that chain resolves. The labour selection genuinely lives on the quote line, not copied onto the task, so there's exactly one place that decision is recorded.
Travel follows its own rule, independent of how the underlying task bills. Onsite travel against a task-governed entry prices against that task's labour role regardless of whether the task itself is Fixed or T&M. A fixed-fee job doesn't absorb travel for free just because the labour portion is locked. Travel and labour are deliberately two separate pricing decisions on the same entry, not one inherited from the other.
Where this goes wrong in practice
Picking a billing mode before scope is actually clear. A fixed price quoted under schedule pressure, before anyone's genuinely confident in the estimate, is the single most common way a job loses money quietly. It never shows up as one bad invoice, just as margin that was never really there.
Letting scope creep absorb into a fixed task without a change order. The work changed, but because asking for more money mid-job felt awkward, it got done anyway, on the clock that was supposed to be locked. That's not a billing-system failure; it's a conversation that didn't happen at the right moment.
Forgetting that changing a draft quote's agreement re-prices every labour line on it. Switching agreements mid-draft to fix one line can silently move every other labour line on the quote too. It's worth a full read-through before sending, not just a glance at the line that was actually being edited.
Treating travel as automatically included in a fixed task. It isn't, by design. A locked labour price doesn't imply free travel, and assuming otherwise is a quiet, recurring undercharge rather than a one-off mistake.
Letting the catalogue drift out of sync with how the team actually talks about a job. A catalogue nobody trusts to have the right item gets worked around, with ad-hoc free-text lines or a product added from memory instead of selected. That is exactly the inconsistency category discipline and account-code resolution were meant to prevent in the first place.
Pre-flight checklist for quotes, the catalogue and labour billing
- [ ] Catalogue items separate category (what it is) from billing type (how it charges)
- [ ] Labour quoted from labour roles, not duplicated as priced catalogue products
- [ ] Category hierarchy mapped through to real account codes, not left to resolve by accident
- [ ] Catalogue names match how the team actually talks about the product
- [ ] Each quote task's billing mode set by where the real uncertainty sits, not by habit
- [ ] Fixed Fee reserved for scope the team has estimated with genuine confidence before, not a first-of-its-kind job
- [ ] A quote free to mix Fixed and T&M tasks within the same document, not forced onto one model
- [ ] Scope changes on a fixed task go through a change order, not silently absorbed labour
- [ ] The quote's billing agreement confirmed before send, since changing it on a draft re-prices every labour line
- [ ] One-off and recurring products from a won quote both land correctly, with recurring items placed on an agreement before they can go live
- [ ] Engineers log time via Quoted Work against the task, never guessing at a rate themselves
- [ ] Travel on a quoted task confirmed to price independently of the task's own billing mode
- [ ] Prices confirmed frozen at send/win, so a later rate or agreement change never rewrites what was already quoted