The first time a client signs up for hosting and support, they often ask, “What does the support hour each month do?” The honest answer is: most months, very little. That's the goal. We've designed the service so that you don't need it, and when you do, you reach a human who already knows your site. We call that “quiet support,” and it took us a while to figure out why it matters.
Loud support is the default
Most agency-style support arrangements look like this: there's a ticket system. You log in, fill out a form, wait. A tier-one person responds asking for more info. You respond. A tier-two person responds with a workaround. You ask if they can actually fix it. There's a back-and-forth. Three days later something happens. You forget what you were trying to do in the first place.
This is loud support. It's noisy, it churns, and it makes everything take five times as long as it should. Worst of all, it teaches the customer not to ask for help even when they need it — because asking is more painful than living with the problem.
What quiet support looks like
One number to call
You text or email Alex. He answers. He's already in your account, on your site, looking at the same screen you are. No tier system. No queue. No “let me check with our team.” The team is him and a small group he trusts, and they all already know your build.
The hour is for what only we can do
The hour of support included each month is for work that requires us specifically — code changes, integration updates, security patches, that-thing-on-page-three that needs to look different. It is not for re-explaining your site to a new tech every six months because the agency rotates staff.
Most months, nothing is wrong
Because the underlying build is custom-coded, kept lean, and hosted on an infrastructure that just works, most months there is genuinely nothing to do. When that happens, we don't manufacture work to fill the hour. We let it sit. The hour rolls over up to a small cap so you can use it when you actually need it.
We watch even when you don't ask
Quiet support is also us looking at things on your behalf. Did a Lighthouse score drop after we shipped that change? We notice. Did a directory listing go stale? We push a correction. Did an SSL renewal need a nudge? Done before you'd have noticed. The thing about quiet is it depends on someone actually paying attention. That someone is us.
Why it's a feature
Loud support is profitable for the support provider. The more tickets, the more touchpoints, the more “hours billed.” Quiet support is profitable only if the work upstream is good — if the code, the hosting, the integrations are solid enough that nothing breaks much. We made the bet to build quietly so the support could stay quiet.
The signal of good support is that you forget you have it.
When you should expect us to be loud
There are moments when quiet support gets loud, and you should expect them:
- A real incident. If something breaks, we're on it inside the hour and we communicate proactively until it's resolved.
- A scheduled change. When we're pushing something non-trivial, you'll hear from us beforehand and get a brief afterward.
- An upstream provider problem. Domain registrar, payment processor, third-party API. If something they do affects you, we tell you.
Outside those, silence is the right state. If you ever feel like you don't know what's going on with your site for too long, ask. We'll send a status. But usually, nothing is news, because nothing has changed, because nothing broke.
The honest version
Support is the part of the relationship most clients never think about during the sales process and most regret eight months later. Pick the kind you want now. Quiet, in our experience, is the one that doesn't make you regret it.
