What one GoHighLevel client actually costs you to deliver

Ask an agency owner what a client is worth and you get a precise figure. Ask what a client costs and you get a pause, then the platform fee, then a shrug. The pause is where the margin goes.

Delivered cost is not complicated. It is five lines, and four of them are easy.

The five lines

1. Platform share. The sub-account’s portion of your fixed monthly platform cost. This is a division problem and it improves every time you sign somebody.
2. Usage. Calls, texts, emails, AI minutes. Variable, driven by the client’s own success, and billed to you first.
3. Build labour, amortised. The setup week, divided across the months you expect to keep the client. A build that took thirty hours against a two-year expected life is a real monthly number, not a one-off.
4. Support and maintenance. The minutes per month somebody spends inside that account — broken steps, deliverability drift, the request that arrives on a Friday.
5. Account management. Reporting, the review call, the internal ten minutes preparing for it, and the follow-up nobody logs.

Lines one and two arrive as invoices, so everybody counts them. Lines three, four and five are hours, so almost nobody does — which is why the shrug happens.

The line that is always missing

It is line five, and it is missing because it does not feel like delivery. Preparing for a review call, answering a question in a chat thread, chasing a client for the asset you needed three weeks ago — none of it is billable, all of it is real, and it scales with client count rather than with revenue.

An illustrative ledger — put your own numbers in

What follows is an assumption set, not a measured result from any customer. Its purpose is to show which line dominates, not to tell you what your business looks like.

Assume a fixed monthly platform cost spread across twelve clients. Assume moderate messaging and call volume rebilled at a stated multiple, so usage is roughly margin-neutral. Assume a thirty-hour build amortised over eighteen months. Assume forty minutes a month of maintenance and a further hour a month of account management, both valued at whatever your own hour is genuinely worth rather than at what you pay a contractor.

Write those five lines out and two things become obvious immediately.

• The hours lines — three, four and five together — dominate the invoice lines by a wide margin. The platform fee everybody worries about is usually the smallest number on the page.
• The ratio is worse for small clients than for large ones, because maintenance and account management barely scale down. A quiet client is not a cheap client.

What this changes about pricing

Three decisions fall out of the ledger, and none of them is "raise the price".

Set a floor and hold it

Once you know delivered cost, you know the retainer below which a client is a hobby. Most agencies find they are carrying two or three accounts under that line, kept out of loyalty or optimism. Fixing those two accounts is usually worth more than winning a new one.

Make the build identical

Line three falls when the build stops being bespoke, and line four falls with it, because identical accounts fail in identical ways and the fix is already written down. That is the practical argument for standardising on one rebrandable snapshot per vertical rather than assembling each client from parts.

Convert hours into a fixed line

Lines three, four and five are variable, unpredictable and made of your own week. They are the ones worth converting into a known monthly figure — which is precisely what a white-label fulfilment retainer does, and why the comparison that matters is against your delivered cost rather than against a contractor’s hourly rate. If you would rather see the plan structures side by side first, they are all on the pricing page.

The number that predicts whether you can grow

Divide your total delivery hours by your client count. That is hours per client per month, and it is the single most useful figure in an agency’s operations.

Multiply it by the client count you want next year. If the answer exceeds the hours you and your team actually have, you do not have a sales problem — you have a delivery ceiling, and no amount of new business will get you through it. It will simply arrive and then leave again.

What the client is paying for, in their terms

None of this ledger belongs in a proposal. Your client does not care that maintenance is forty minutes; they care that a stranger who calls their business after hours gets a conversation and a booked slot rather than voicemail, that the person who booked gets reminded twice before the appointment, that somebody who does not turn up gets called back within the hour, and that the ones who did turn up get asked for a review.

The ledger is for you. It tells you whether you can afford to keep the promise you just made.

Three costs that only appear in year two

The five-line ledger is a monthly view, and it misses three things that accumulate annually. Each of them is invisible in month three and obvious in month eighteen.

• Replacement cost. Every departing client has to be replaced before you grow at all, and the acquisition cost of the replacement belongs somewhere. An agency with a twelve-month average tenure is running a treadmill it has not priced.
• Platform drift rework. The underlying platform changes. Something that worked last year behaves differently this year, and somebody has to go through every live account and fix it. This is real, recurring, and almost never in anybody’s model — and it scales with client count and with how different your accounts are from each other.
• Knowledge concentration. If one person can complete an install and nobody else can, you are carrying an unpriced risk that converts into a very large cost on the day they resign. Documentation is not overhead; it is the premium on that policy.

The second one is the strongest practical argument for standardising. Twenty identical accounts are one fix applied twenty times. Twenty bespoke accounts are twenty investigations, and the investigation is the expensive part.

What to do with the ledger once you have it

Do not put it in a proposal and do not show it to a client. Use it for exactly three decisions.

1. Which accounts to reprice at renewal, because they sit under your floor.
2. Which vertical to build the next standard system for, because delivered cost falls fastest where you have the most accounts.
3. Whether the next capacity you add should be hired or rented, which is a question about how volatile the hours line is rather than how large it is.

The short version

Five lines, two of which arrive as invoices and three of which arrive as your week. Count all five, set a floor underneath them, and then attack the hours rather than the invoices — because the invoices were never the problem.