Are you still taking new managed-hosting clients?

Yes — but capacity is intentionally limited. The honest answer to "can you take us on right now?" depends on how many sites we are already running and where we are in the operations cycle. Here is how it works for managed-hosting new clients, and how to find out where you stand.

Why we cap capacity

Most agencies hide their capacity constraints. They sell, sell, sell, and then the delivery quality suffers. We do not. The reason is structural: we are a small operation with one operator deeply involved in every project. That is a feature of how we deliver — one point of contact, no handoffs, fast turnarounds — and it imposes a real limit on how many sites can be running simultaneously without quality slipping.

The arithmetic is not complicated. There is a number of active client sites we can run well, and once we hit that number, taking on one more means dropping the ball somewhere. We would rather tell a new client they have to wait three weeks than tell an existing client their security patch slipped because we were too busy onboarding.

What "limited" actually means in practice

The constraint is on new onboardings per month, not on total clients. Operations of an existing site is mostly automated — backups, monitoring, updates, performance reports run on schedule and require minimal hands-on time. The hands-on work concentrates in two phases: the build (when you sign on) and changes (when you ask for them). Both are bounded by available hours.

In practical numbers, we onboard up to three new clients in a typical month, sometimes four if the builds are simple. Beyond that we add to a waitlist for the following month rather than overcommit.

How onboarding works when there's a slot

When there is open capacity, the timeline from "I'd like to sign up" to "site is live" is short:

1. Day 0: You send a request through the form. You hear back within 24 hours with either "yes, we can start this week" or "we have a queue — expected start week of X."
2. Day 1–2: Quote is issued. You review and accept.
3. Day 3–5: Onboarding call. We collect access, branding, content, and any third-party integrations.
4. Day 6–14: Build phase. Starter typically lands in week one, Standard in week two, Shop usually around weeks two to three.
5. Day 14–21: Final review, your sign-off, launch. First billing month starts from launch day, not from day zero.

The waitlist — what it is and is not

If we are at capacity, the waitlist is the alternative. It is not a vague "we'll get back to you whenever". It works like this:

Position transparency. When you go on the waitlist, we tell you your position and our best estimate of when a slot opens up. Two weeks, four weeks, six weeks — whatever it is, you get a real number.

No deposit, no obligation. Being on the waitlist costs nothing. You are not committing to anything until you formally accept the quote when your slot opens.

First-come, first-served, with one exception. Existing clients adding a second site jump the queue. New clients are sequenced in the order they joined the list.

You can leave the list at any time. If you decide to go elsewhere, a single email removes you. We will not pester.

How to position yourself to start sooner

If you are flexible, there are a couple of small things that can move you up the queue:

• Have your content ready. Logo, brand colours, copy, product list. The single largest cause of delayed builds is waiting on content from the client.
• Be clear about scope on first contact. "I need a five-page brochure site" is easier to slot than "we want a site, eventually with a shop, plus a member area maybe".
• Be open to Standard. Most Starter builds turn into Standard within a year anyway. Starting on Standard occasionally moves the slot forward because the build is more predictable.

The flip side: when we say no

We will turn down work in two situations. First, when the scope clearly does not fit what we do — large-scale custom development, enterprise integrations, complex multi-vendor procurements. We will tell you up front and, where possible, recommend someone who handles that kind of work. Second, when we are already at capacity and adding even a waitlist position would mean the wait is unreasonably long. In that case we say so directly rather than string you along.