Promise risk
This is one result from the Are You Undercharging Clients? calculator, and it is the inverted one. Most profiles here describe carrying more than you charge for. This one describes charging for calm you cannot reliably deliver. The subsidy runs backward: the buyer is funding a promise, and the promise is thin.
What this profile means
Your price and packaging signal managed relief. The offer is visible, the number is premium, the customer believes someone dependable is watching. But the staffing answer you gave the calculator says the coverage is thin or hangs on one person. That combination is not undercharging. It is overpromising with an invoice attached.
The uncomfortable framing: on paper this account looks great. High price, high margin, grateful customer. The margin exists because a cost that should exist does not. The rotation you have not hired, the backup you have not arranged, the redundancy you have not built. You are booking the profit of a managed service while running the cost structure of a tool.
Why promises are judged at the worst moment
A response promise is invisible for months and then evaluated in a single hour. Nobody grades your SLA on a calm Tuesday. They grade it during the outage, at 2 a.m., when the one person who can fix things is on a plane. Support operators have a phrase for this: a one-hour response commitment with no on-call rotation is a target, not a plan. Slow first response during a real incident is among the most common reasons a vendor gets put up for replacement.
This is why the failure compounds unfairly. A hundred quiet months buy you nothing. One bad incident, judged against a premium price, converts a happy reference customer into a churn story with a paper trail.
Why founders land here
Usually not through dishonesty. The tier got sold before the team got hired, on the reasonable theory that revenue funds staffing. Or the founder was the coverage, back when three customers made that survivable, and customer twenty arrived without anyone rewriting the promise. The common thread is that the offer scaled and the operating model did not, and there was never a day when the gap announced itself.
There is also a human cost hiding in this profile: the one tired person. Coverage that depends on a single individual is not just a business risk. It is a resignation letter in progress, and the promise dies the day they do quit.
The move: narrow it or staff it
There are exactly two honest exits, and both beat waiting for the incident.
- Narrow the promise. Move the boundary to what your current team can keep on its worst week: business-hours response, defined severity levels, self-serve paths for the rest. Buyers forgive a modest promise kept far more than a grand promise missed, and a written boundary protects you at exactly the moment a vague one destroys you.
- Staff the promise. If the premium positioning is the strategy, fund it for real: a rotation, a paid backstop, an escalation contract. Price it in, since the price was supposed to be covering it anyway.
The test for which one to pick: write down the response commitment your team could honor during a week when one person is sick and another is on vacation. If that sentence looks nothing like your contract, the contract is fiction, and you get to choose which document to fix.
Boundaries
Do not read this profile as permission to hide the operational work you do perform. Once the coverage is real, the visibility playbook in Custody priced is how you defend the premium. And if you narrow the promise substantially, rerun the calculator: you may discover you have drifted toward Capability mode, which is a legitimate place to stand as long as the price says so.