The payment structure you put in an SOW is one of the highest-leverage decisions in the contract. It determines your cash flow exposure, your leverage if the relationship deteriorates, and how much of your margin survives client behavior you could not predict at signing time.
Most IT consulting firms default to whatever the client's procurement template expects — usually net 30 monthly billing for T&M work, or milestone payments for fixed-price. The decision rarely gets deliberate analysis. It should.
Here is how the three primary payment structures actually perform across the risk dimensions that matter for delivery teams.
The Three Structures
Net 30 Monthly Billing (Time & Materials)
T&M is typically the lower-cost option for the client — and the reason is risk. With T&M, the client carries the delivery risk. They pay for hours worked regardless of whether the outcome meets expectations. The delivery organization provides the effort; the client owns the result.
You invoice at the end of each billing period for hours worked plus approved expenses. Payment is due net 30 from invoice date.
Where it protects you: Monthly invoicing limits your maximum cash flow exposure to roughly one billing period of work. If the client stops paying, you know within 30 to 45 days and can act. Disputes are usually about specific timesheets, not the entire engagement.
Where it exposes you: Net 30 with a slow-paying enterprise client becomes net 60 or net 75 in practice. Without a work suspension right for overdue invoices, you may keep working while invoices age. Without a not-to-exceed clause, clients who receive a larger invoice than expected will dispute the excess — even if every hour is documented.
Milestone-Based Billing (Fixed Price)
Fixed-fee flips the risk. The client is buying an outcome, and the delivery organization owns the risk of getting there. Fixed-fee engagements are priced higher than equivalent T&M work for a reason: the contingency baked into the price is not padding — it is the cost of guaranteeing an outcome and absorbing the unknowns that only surface once work is underway. There are always some. When clients negotiate fixed-fee prices down to T&M levels, they are asking the delivery org to own the risk without being compensated for it.
We covered the structural risks of milestone billing in depth in Part 1 of this series — the short version is that milestone billing creates a client-controlled payment gate that can delay or block payment regardless of how much work you have done.
Where it protects you: Fixed-price forces scope clarity that benefits both sides — you both have to agree on what "done" means before signing. That clarity, if actually achieved in the SOW, reduces disputes at delivery time.
Where it exposes you: Vague acceptance criteria, no review window, and no deemed-acceptance clause turn milestone billing into open-ended unpaid work. Back-loading payments to the final milestone is the highest-risk configuration in IT consulting — it gives the client maximum leverage at the moment they are most likely to use it.
Retainer Billing
The client pays a fixed monthly fee for a defined scope of advisory, support, or capacity. Work performed within that scope is covered by the retainer. Work outside it triggers a change order or separate SOW.
Where it protects you: Retainer billing is the most predictable and lowest-friction payment structure for ongoing engagements. Payment happens on a schedule regardless of deliverable status. There are no milestone disputes because the payment trigger is time, not completion. Cash flow is highly predictable.
Where it exposes you: Scope creep is the core risk. Clients on retainer often treat the arrangement as access-to-team rather than access-to-defined-scope. Without a clear retainer scope definition and a change-order process for out-of-retainer requests, the retainer gets diluted — you are delivering more than you are billing for and the math slowly breaks.
At a Glance
| Structure | Cash Flow Risk | Dispute Risk | Client Leverage | Best For |
|---|---|---|---|---|
| Net 30 T&M | Medium | Low–Med | Medium | Ongoing work, variable scope |
| Milestone | High | High | High | Discrete deliverables, clear criteria |
| Retainer | Low | Low | Low | Advisory, ongoing support, trusted relationships |
A Hybrid Approach That Addresses Most of These Risks
A hybrid structure can solve a lot of the exposure that comes with any single model: a kickoff payment at signing, monthly T&M billing for ongoing work, and milestone payments tied to major phase completions — with each milestone protected by explicit acceptance criteria, a review window, and deemed-acceptance language.
The kickoff payment validates the client's procurement process before you commit resources. Monthly billing caps your cash flow exposure. Milestone payments at phase gates align incentives around delivery quality without making final payment a hostage.
This structure requires more negotiation than accepting a client's standard terms — multiple SOW revisions, procurement involvement, and stakeholder alignment on both sides. That overhead is only worth absorbing on engagements of significant contract value. A reasonable threshold is $250K or more. Below that, the negotiation cost often outweighs the protection gained.
The Structural Question to Ask Before You Sign
For any payment structure, ask: If this client becomes difficult in month three, does this payment structure give them more leverage or less?
Milestone payments with vague acceptance criteria: more leverage. Net 30 with no suspension right: more leverage. Monthly retainer with clear scope and automatic renewal: less leverage.
You cannot always negotiate your preferred structure. But you should know what you are accepting and build the other contractual protections — suspension rights, deemed acceptance, dispute carve-outs — around whatever structure the engagement requires.
SOWaudit reviews your SOW's payment structure and flags the specific clauses — missing suspension rights, vague acceptance criteria, back-loaded milestones — that create cash flow exposure before the project starts.
Run a Free SOW Audit →