What to charge a client for a snapshot install

The question comes in almost the same words every time. I bought a snapshot — what do I charge to install it? And the honest answer is that the question has the shape of the problem in it, because nobody is buying an install.

Your client is buying the fact that the phone gets answered at nine at night. You are quoting for that. The install is how it arrives, in the same way a van is how a plumber arrives.

Stop pricing the artefact

There is a reason this trips people up. A snapshot has an acquisition cost you can see, and a visible cost invites cost-plus thinking. So agencies take what they paid, multiply it by something that feels brave, and quote that.

It undersells the work by an order of magnitude, and worse, it teaches the client that the thing they are buying is a file. Files get compared to other files. Systems that answer the phone do not.

Price against the client’s own number

Every vertical has one figure the owner already tracks and already argues about. Find it in the first call and anchor everything to it.

Once that number is on the table, your quote stops being an expense and becomes a subtraction from a loss they already carry. That is the whole move.

The two-line structure that works

One-off install fees create a cliff: the money arrives, the work continues, and by month four you are supporting an account you are no longer being paid for. Retainer-only pricing creates a different problem — the setup work is real and front-loaded and you are financing it.

1. A setup fee that covers the build week honestly. Configuration, domains, sender authentication, number provisioning, calendar wiring, the copy pass and the walkthrough. This should be a number you would be content to do the work for twice.
2. A monthly figure that covers access, usage and the fact that somebody keeps it alive. Structure it in visible parts — platform, managed system, growth work — so that a client under pressure downgrades rather than cancels.

An illustrative quote — rebuild it with your inputs

This is an assumption set, not a result. Nothing below reports a real customer’s outcome; every figure is an input you should replace.

Assume a six-van home services company. Assume they take a hundred and twenty inbound calls a month and, by their own estimate, miss around a fifth of them during working hours. Assume their average job is worth several hundred dollars and roughly one in three enquiries converts. Multiply those three assumptions together and you get the monthly value of the calls that currently go nowhere. In most versions of this arithmetic that figure is four digits, and the owner has never written it down.

Against that figure, a setup fee in the low four figures and a monthly retainer that sits comfortably below the recovered value is not a negotiation. It is a subtraction. Write the sum on the call, with their numbers, and let them check it.

What the setup fee has to cover

Be specific in the proposal, because a number without a scope is a number that gets negotiated. A realistic install week includes the account foundations, sender authentication and carrier registration, calendar and pipeline ownership, a copy pass so the sequences sound like the client’s business, and a walkthrough that leaves somebody at the client able to use it.

The QA sweep matters more than any of it, and it is the part most often skipped under time pressure. Our fourteen-point snapshot import checklist is the version we run before a client ever logs in, and it is worth pricing the hours for explicitly rather than absorbing them.

Three pricing mistakes worth naming

• Quoting per asset. Counting workflows and funnels invites the client to count them too, and to ask why they need the eleventh.
• Discounting the setup to win the retainer. The client learns that your prices move, and every subsequent conversation starts from that lesson.
• One undifferentiated monthly number. When budgets tighten, an undifferentiated retainer is a single yes-or-no decision, and you will not enjoy how it gets answered.

Where your margin actually comes from

It is not the markup on the snapshot. It is the fact that the second install of the same system takes a fraction of the first, and the tenth takes less again — as long as the system is genuinely identical each time. That is the entire economic argument for buying a rebrandable white-label snapshot rather than assembling one per client, and it is why our pricing is a one-off per vertical with unlimited installs inside your own agency rather than a fee per client.

Price the first install as though it were bespoke, because for you it very nearly is. Price the tenth the same way, because for the client it is.

How to present the number

A price is a piece of writing, and the same figure lands differently depending on what surrounds it. Four things consistently help.

1. Put the client’s own arithmetic above the price, not below it. They should read the cost of the problem before they read the cost of the fix, and the arithmetic should use numbers they gave you on the call.
2. Show three options, not one. A single number invites a yes or a no; three invite a choice. The middle one should be the one you want, and the top one should exist mainly to make it look sensible.
3. Separate the setup from the monthly visually, and name what each buys. A client who understands they are paying for a build week and then for somebody keeping it alive rarely argues about either.
4. State the delivery commitment in the same breath as the price. A date is worth more than another paragraph of features, because it is the only part of the proposal that can be checked.

What does not help is a feature list. The client cannot evaluate whether a long list of automations is a lot, and asking them to try invites them to count.

When to walk away from the quote

Two situations are worth naming, because in both of them the right price is no price.

The first is a business whose problem is not lead handling. If they are losing customers because the service is poor or the pricing is wrong, a system that answers the phone faster will deliver more people to the same disappointment, and you will be blamed for it. Say so, and say it before the proposal.

The second is a business with no capacity. Recovering forty missed calls a month is worth nothing to a company that cannot service them, and a booking system that fills a calendar nobody can staff produces cancellations rather than revenue. That client needs a different conversation first, and the fact that you had it is what makes them a client later.

The short version

Charge a setup fee that respects the build week and a monthly that respects the babysitting, and anchor both to the number your client already loses sleep over. The snapshot’s price is your cost of goods. It has no business appearing in the quote.