What '48-hour setup' should actually mean when you buy AI for your agency

Setup claims are where AI vendors hide the most

Agency owners have been through this movie before, because martech invented it: the platform that was 'up and running in a day' and then spent a quarter half-configured, generating logins nobody used while the subscription billed. AI tools inherited the same vocabulary with a straighter face. 'Live in minutes' is usually true in the narrowest sense — an account exists, a dashboard renders — and false in every sense you're paying for, because nothing is connected to your actual work yet.

The gap persists because 'setup' is doing two different jobs in the sentence. For the vendor, setup means provisioning: your tenant exists, the trial clock started. For you, setup means the thing is doing the job you bought it for — which requires your tools connected, your context loaded, your team knowing what to click, and at least one real piece of work flowing through the system end to end. Vendors quote the first clock and let you assume it measures the second.

For an agency the stakes of that gap are concrete: you're buying AI precisely because your senior people have no slack. A tool that arrives 'live' but needs three weeks of your evenings to become useful didn't cost $999 a month — it cost the evenings, and probably a stalled rollout, because the fourth time onboarding slips down the priority list it never comes back up. So before comparing any two vendors' setup claims, force both onto the same question: what exactly is true at the end of your number?

'Done' means the first real approved move

Here's the definition worth holding every vendor to, ours included: setup is done when your team approves the first real action, built from your real data, executed in your real tools. Not a demo record. Not a sandbox draft. A follow-up to an actual lead, a recap of an actual meeting, a nudge on an actual overdue invoice — drafted by the system, reviewed by a person on your team, approved, and sent. That moment is the product working. Everything before it is preparation.

The definition is deliberately strict because each word closes a loophole. 'Real data' rules out the seeded demo that always looks great. 'Your real tools' rules out the parallel sandbox you'd have to migrate out of. 'Approved by your team' rules out the vendor clicking the button for you — if your people can't operate the approval queue, you don't have a working system, you have a vendor demo running on your account. First approved move is the smallest milestone that proves the whole loop: connection, context, draft, judgment, execution.

It also sets the right expectation for what setup is not. One approved action doesn't mean the system knows your voice yet, or that every workflow is wired — that maturing takes weeks of normal use, and any vendor who claims otherwise is overpromising. But the difference between 'first real move on day two' and 'still configuring in week five' is the difference between momentum and a stalled rollout. Define done at the first approved move, and the rest compounds from there.

Honest clock mechanics: business hours and pauses

Once 'done' is defined, interrogate the clock. First: business hours or wall-clock? A 48-hour promise on a wall clock means a Friday-evening kickoff is due Sunday — which either means the vendor staffs weekends (ask) or the promise quietly fails every Friday signup. A 48-business-hour clock is the honest version: it measures working time, so a Friday kickoff lands mid-week instead of pretending the weekend doesn't exist. Vaguer is not better here; a vendor precise about the clock is telling you they've actually run it.

Second: what pauses it? Real onboarding has a dependency the vendor doesn't control — you. Someone on your team has to connect the CRM, grant the OAuth scopes, answer 'which pipeline matters most.' An honest promise pauses the clock while the ball is in your court and says so up front; a dishonest one either eats the delay silently (and misses, teaching you the promise was decorative) or blames you retroactively. The pause rule cuts both ways, note — it also tells you your own homework determines whether the fast path stays fast.

Third: what's the remedy when they miss? A promise without a consequence is a mood. It doesn't need to be dramatic — a meaningful service credit is a perfectly good answer — but it needs to be written, automatic-ish, and not contingent on you arguing. The remedy question is really a confidence question: a vendor who has hit their number a hundred times will happily price the miss, and one who won't put anything behind the claim has told you their own base rate.

How Kirality's version works, stated plainly

Since this is our checklist, here's our answer to it. Kirality's 48-Hour Setup is a program promise on the done-for-you plans: from kickoff, your tools connected and the operator's first real drafted work waiting in your approval queue within 48 business hours. Business hours, explicitly — a Friday kickoff doesn't owe you a Sunday miracle — and the clock pauses when we're waiting on you, credentials being the usual example. 'Done' is the definition above: real work from your real stack, staged for your team's approval.

If we miss the window for a reason on our side, your next month carries a one-time service credit. That's the remedy in writing, and the reasoning is exactly the confidence argument: pricing the miss keeps us honest about the promise. What the promise is not: a claim that the system has learned your agency's voice in two days, or that every workflow you'll eventually run is live by Wednesday. It's the first-approved-move milestone, hit fast, so the compounding starts immediately instead of after a stalled quarter.

And if you'd rather not have anyone set it up for you, that path exists too: the self-serve Starter tier at $239 a month, where you bring your own AI key, connect your own tools, and go at whatever pace suits you. The setup promise is a service commitment on the plans where setup is our job. On the plan where it's yours, the honest statement is simply that the same first-approved-move definition of done is worth holding yourself to.

The questions to email every vendor

Paste these five into your next evaluation thread and judge the replies on plainness. One: at the end of your quoted setup time, what specific thing will be true — and is 'my team approved a real action in our real tools' part of it? Two: is the clock wall-time or business hours? Three: what pauses it, and how do I see the pause happening? Four: what exactly do you need from us in the first day, listed, so we can have it ready? Five: what happens if you miss — in writing?

The answers matter less than their shape. A vendor who has actually onboarded businesses like yours answers in specifics, fast, because the questions map to a process they run every week. Deflection has a recognizable sound: 'every business is different,' 'our success team will scope that on a call,' 'typically customers see value quickly.' Those are all ways of saying the number in the headline was marketing, not operations.

One last calibration: fast setup is evidence of operational seriousness, not a guarantee of fit. A vendor can hit 48 hours and still be the wrong product for how your agency runs — which is what the demo, the pricing math, and the approval-model questions are for. But a vendor who can't tell you what 'done' means has answered the fit question too, just not the way they intended. Buy from people who define their promises tightly enough to fail them; those are the promises that were ever real.