How to bill a client: Summary & key takeaways
A margin decision, not paperwork: How to bill a client profitably is decided long before the invoice, in how you capture time and price work.
The Bill-to-Profit Ladder: Climb four rungs in order (Capture, Model, Invoice, Collect); fixing them out of sequence is how teams leak revenue.
Capture comes first: Un-logged billable hours are simply unbilled revenue, and they are the single biggest source of margin leakage in client delivery.
The model sets your ceiling: Hourly, fixed-fee, and retainer billing carry very different margin and predictability profiles, so choose the model on purpose.
AI is breaking hourly billing: As AI compresses delivery hours, teams billing purely by the hour quietly bill themselves out of margin.
Most guides on how to bill a client stop at the invoice: pick Net 30, send a tidy PDF, chase the late payers. That is the paperwork, not the billing. Billing a client profitably is a commercial decision you make long before the invoice goes out, and getting it wrong drains margin every single month.
This guide reframes billing as a four-rung climb from work done to margin banked. Expect real numbers and the moves that actually shift the outcome.
I wrote it for professional services teams, agencies, consulting firms, and IT services. In that world billing is multi-project and multi-rate, and the leak shows up in salaries, not pocket change.
What "billing a client" actually means (and why the invoice matters least)
I still see billing treated as a synonym for invoicing, and that one mix-up is where the money quietly goes. The invoice is the receipt at the end of a decision you already made. The decision was how you priced and captured the work in the first place.
Billing a client is the process of requesting payment for completed work. You issue an invoice that lists the services delivered, the amount owed, and the payment terms.
That is the textbook definition. The profitable version is different: it is the whole chain from logging a billable hour to banking the margin on it.
A few terms sit inside that chain, so let me define them cleanly:
Billable hours: the hours you can charge a client for delivering their work.
Billable utilisation: the percentage of a person's available hours spent on billable work.
Payment terms: the agreed window for payment, such as due on receipt, Net 15, or Net 30.
Retainer: a recurring fixed fee a client pays for ongoing work each cycle.
Get those four right and the invoice becomes trivial. Get them wrong and no invoice template will save you. For the fuller commercial picture, our guide to professional services billing goes deeper on the models and metrics. It pairs well with managing client expectations around money.
The other thing to settle before any work starts is the contract. A written agreement or statement of work sets the rate, the scope, the billing model, and the payment terms in one place both sides signed. That is not legal theatre.
It is the reference you point to when scope drifts or a payment stalls, and it removes most billing disputes before they start. I would never begin billable work on a handshake, because the ambiguity always costs the delivery team, not the client.
The Bill-to-Profit Ladder: fix the invoice last, lose margin
I keep seeing services teams scramble at the bottom of the process. People polish the invoice and automate the reminders, then wonder why margin still slips. They are working the ladder upside down.
So I use a simple model I call the Bill-to-Profit Ladder. It has four rungs, and you climb them in order: Capture, Model, Invoice, Collect. The higher-leverage rungs sit at the bottom, and when you get Capture and Model right, Invoice and Collect almost take care of themselves.
Rung
The order matters because each rung feeds the next. Accurate capture makes the model defensible, the right model makes the invoice correct, and a correct invoice makes collection painless. Skip a rung and you patch the symptom while the cause keeps costing you.
Most teams climb this ladder backwards, and the reason is worth knowing. Invoice and Collect are the visible rungs, the ones with obvious tools and templates, so they get the attention.
Capture and Model are quieter and earlier, so they get skipped. That is exactly why the money leaks there: the highest-leverage rungs are the ones nobody is watching. Fix the bottom two and the top two stop being a fight.
Capture (rung 1): you can't bill for the hours you never logged
Before I joined Teamwork.com, I lost more margin to un-logged time than to any late payer. A designer would spend 40 minutes on a client call, forget to log it, and that revenue vanished. Multiply that across a team and a month, and the leak is enormous.
Capture is the first rung because everything downstream depends on it. If an hour is not logged, it does not exist to your invoice, your margin report, or your utilisation figure. It becomes free work you did not choose to give away.
The distinction that matters here is billable versus non-billable time. Billable time is the client-facing delivery work you can charge for.
Non-billable time covers internal admin, business development, and rework you absorb. Both are real, but only one pays the bills, so see the split clearly before you bill.
Billable utilisation is the metric that exposes the leak, and you can calculate it simply:
A healthy target for most services teams sits around 75% to 85%. The industry is drifting the wrong way, though, which tells you how common this leak really is.
Key insight: Billable utilisation fell to a record-low 66.4% in 2025, well below the 75% optimal threshold, according to the Deltek-sponsored SPI 2026 Professional Services Maturity Benchmark.
Here is what that looks like in money. Say a 10-person delivery team each carries 30 billable hours a week at an average $125 rate. If everyone under-logs just three hours a week, that is 30 hours lost. At $125, that is $3,750 a week, or roughly $195,000 a year, invisible.
The fix is to capture time and cost as delivery happens, not from memory on a Friday. One of the reasons we built real-time time tracking at Teamwork.com is that reconstructed timesheets always under-count.
To start with a clean habit, the client work time tracking template gives you a consistent format. Use it to log billable and non-billable hours from day one. Costs count here too, not just hours. A client's project usually carries pass-through expenses like software licences, contractor fees, or travel.
If those land in a general expense pile instead of against the client, you either eat them or bill them late. So capture the cost the moment it happens, tagged to the client, the same way you capture the hour. The habit is what makes this rung hold. Logging time weekly relies on memory, and memory rounds down.
Logging as you go, ideally with a running timer, captures the small stuff. It catches the 20-minute call and the 15-minute revision that quietly add up to your missing margin.
Model (rung 2): pick the billing model before you pick the invoice
What I've noticed is that most teams never actually choose a billing model. They inherit hourly billing because it feels safe, then blame the invoice when margin disappears. The model is the rung that sets your profit ceiling, so it deserves a real decision.
A billing model is the structure you use to price client work: hourly, fixed-fee, retainer, or value-based. Each one trades predictability against margin risk differently. Here is how they compare.
Billing model
This is where AI changes the math, and it is the part competitors skip. When AI compresses delivery hours, hourly billing punishes your own efficiency. Every hour AI saves comes off your revenue, not your cost base.
Take a website build scoped at 40 hours at $150, so $6,000. Your team uses AI and finishes in 25 hours. Bill hourly and you invoice $3,750. Price it fixed-fee at $6,000 and you keep the $2,250 your efficiency earned. Same work, same client, a $2,250 swing from the model alone.
Value-based billing is the direction this pressure pushes you. Instead of charging for time, you price against the outcome the work creates, such as a revenue lift or a cost saved.
It is harder to scope and defend, so it suits high-impact work where you can point to a measurable result. The reason it holds up as AI cuts hours is simple. The client pays for the result, so shaving delivery time grows your margin instead of shrinking your invoice.
Retainers are the predictability lever most agencies actually want, since they turn variable months into steady recurring revenue. For the setup detail, use the retainer agreement template and decide whether a retainer is right for each account. To run one without bleeding margin, the retainer project template tracks monthly hour budgets so scope creep has nowhere to hide. For the wider pricing picture, our breakdown of agency pricing models covers each option in depth.
Clients feel this shift too, which raises the stakes on model choice. In our own research, 66% of senior leaders told us clients are now more demanding but less willing to pay for the same work. Billing by the hour into that pressure is a losing position.
Invoice (rung 3): the paperwork that finally becomes trivial
In my experience, a slow or wrong invoice is almost always a symptom of a broken rung below it. When capture is accurate and the model is set, the invoice is just a clean read-out of what already happened. When they are not, the invoice becomes a negotiation.
A strong client invoice includes a unique invoice number, issue and due dates, and both your details and the client's. Add itemised services with rates, the total owed, accepted payment methods, and any PO or reference number. Missing fields, especially a PO number, are a leading cause of payment delays. So the goal is a complete invoice sent the moment work or a milestone is done.
Payment terms are the other lever you set on the invoice, and they matter more than people expect. They are the agreed window a client has to pay, such as due on receipt, Net 7, Net 14, or Net 30.
I use shorter terms for new clients until they prove reliable, then extend to Net 30 for established relationships with formal finance cycles. Always state the exact due date, not vague language, so there is nothing to interpret.
Speed matters as much as accuracy. Prompt invoicing shortens your cash-flow gap, and delayed invoicing is one of the most common self-inflicted causes of late payment. A simple central record helps here, which is why the invoice tracker template keeps every invoice and its payment status in one view.
Match the invoice cadence to the model, too. Fixed-fee work often bills in milestones, such as a deposit up front and the balance on delivery. Retainers bill on the same date each cycle.
Time-and-materials work bills on a regular schedule against logged hours. Getting the cadence right keeps cash arriving predictably instead of in unpredictable lumps.
Pro tip: Reconcile logged hours against the budget before you send anything. Teamwork.com's budgeting and profitability view compares actuals to the budget in real time, so you catch under-billing before the invoice leaves, not after the client queries it.
For hourly work, the invoice is only as honest as your capture. Track every billable hour against the project, apply the agreed rate, then itemise the hours and rate line by line. If the hours are logged accurately, the invoice defends itself.
Collect (rung 4): chasing late payers is a symptom, not the disease
What I keep seeing across Teamwork.com customers is that collection problems rarely start at collection. They start three rungs down, with vague terms and incomplete invoices that give clients a reason to stall. Fix the cause and the chase mostly disappears.
The cost of getting this rung wrong is real and well documented. 56% of US small businesses are owed money from unpaid invoices, averaging $17,500 per business, and nearly half have invoices more than 30 days overdue, according to the Intuit QuickBooks 2025 Small Business Late Payments Report.
Most late payments trace back to the same handful of causes. The usual suspects: missing invoice details, vague payment terms, invoices sent to the wrong contact, and internal approval delays. Clear terms, complete invoices, and prompt follow-up remove nearly all of them before they happen.
The reason this rung matters so much is cash flow, not just principle. Money owed is money you cannot pay salaries or reinvest with, and a stack of 30-day-overdue invoices can strain an otherwise healthy business. A firm that captures accurately, prices deliberately, and invoices promptly rarely lands in that position, because it has already removed the friction that stalls payment.
When a payment does slip, I keep the first nudge factual and warm. I reference the agreed terms, restate the invoice number and amount, and make paying easy. A missed payment is often an honest oversight or a cash-flow wobble, so I assume good faith first, then escalate politely if it continues.
My light-touch sequence looks like this, and it resolves most cases before things get tense:
A friendly reminder the day after the due date, restating the invoice number and amount.
A direct check-in a week later, asking if anything is blocking approval on their side.
A firmer note referencing the contract terms if it reaches two weeks overdue.
For the harder cases, we have a full escalation playbook. Our guide on how to get clients to pay on time walks through each step in more detail.
How to bill a client without the four costly mistakes
The mistakes I see cost teams the most are not dramatic. Nobody forgets to send an invoice entirely.
Instead, small habits compound into a slow, invisible margin leak that only shows up in the quarterly numbers. Here are the four I would fix first.
Billing from memory instead of real time: Time logged from recollection always rounds down, and the short calls and quick fixes vanish with their revenue.
Defaulting to hourly because it feels safe: Hourly is easy to explain, yet it caps your upside and quietly punishes your own efficiency.
Treating the invoice as the start of billing: By then the profit is already set, so you manage the receipt, not the margin.
Letting retainers quietly overservice: A retainer only stays profitable while you protect the hour cap, and steady overdelivery turns a healthy account into a loss.
That last one deserves numbers, because it hides so well. Take a $5,000 monthly retainer scoped at 40 hours, with a blended cost of $95 an hour.
Deliver 55 hours instead, and you have given away 15 hours, or about $1,425 of cost, every month you overservice. Across a year, that is roughly $17,000 of margin gone on a single account nobody flagged.
I would rather catch that overservicing in week two than in the annual review. Real-time budget visibility is the difference between a small mid-month adjustment and a write-off you only spot a year later. Top-performing firms use automation to hold revenue leakage below 3%, according to Deltek's SPI KPI analysis.
How the agentic PSA ties capture, model, and margin together
)
Teamwork.com is the agentic PSA that connects projects, resources, and financials in one platform. That is how you climb all four rungs of the Bill-to-Profit Ladder without stitching tools together.
Generic project tools track the work but cannot manage the money, so margin leaks where the systems meet. Traditional PSAs manage the money, but teams resist using them, so the data going in is unreliable and the numbers are too.
Companies using professional services automation report 11% higher resource utilisation and 25% greater profit margins. That is according to Deltek's professional services trends analysis of SPI Research data. Here is how that plays out across the ladder.
See margin before you invoice, not after. I have found the biggest mindset shift is watching margin move as work happens. Teamwork.com's budgeting and profitability tools track fixed-fee, time-and-materials, and retainer budgets against real cost in real time. You see the margin on a project while you can still act on it, so a low-margin account gets flagged early instead of surfacing as a nasty surprise at invoice time.
Run retainers without overservicing them away. Retainers only stay profitable if you protect the hour budget every month. Retainer management tracks billable hours and remaining scope against each client's monthly cap, so a generous team does not quietly deliver a fixed fee's worth of extra work for free. I have watched a healthy retainer turn unprofitable in a quarter purely from unmanaged scope creep.
Let AI flag the leak before it costs you. TeamworkAI reads your own delivery data, so the AI Utilization Summary surfaces under-logged time and the AI Forecaster flags margin risk while you can still fix it. Because it works from your real actuals, it does what generic AI cannot: tell you where this client's margin is slipping this week.
)
When SugarCRM unified projects, time tracking, and billing in Teamwork.com, they hit near-perfect invoicing accuracy. They credited less than $20K on more than $10M in annual invoicing.
That is the Capture rung paying off at the Invoice rung: accurate time in means accurate invoices out. Across our customer base, teams improve billable utilisation by around 21.8% on average within 12 months, which is the leak on Rung 1 closing.
The job
Connect the rungs in one platform and billing stops being admin you dread and becomes the margin lever it should be.
)
)
)
)
)
)
)
)
)