The fastest way to determine what a business actually needs before starting an AI implementation isn't a long scoping call — it's five questions. Answer them honestly and it becomes clear whether a business needs a full system build, an extension of existing tools, or just a strategy conversation to figure out where to start.
The 5 Implementation Readiness Questions
1 — Can you describe your current process in writing, without gaps?
Not the ideal version — the actual current version. What happens when a lead comes in? Who touches it? What decisions get made? Where does it go next? If this can be written out clearly, with no "it depends" gaps that can't be explained, the process is ready to automate. If the honest answer is "it depends on who sees it" or "we kind of figure it out each time," that's not a barrier to starting — it just means documentation comes first.
Clear process → ready to build. Murky process → documentation phase first, then build. Both are fine starting points. Only one leads straight to a system build in week one.
2 — Do you already have a CRM, or are you starting from zero?
This one question determines the shape of an engagement more than almost anything else:
- Starting from zero (spreadsheets, email only, no real pipeline tracking) — the foundation gets built first.
- Have a CRM that's not working (a platform nobody uses, poorly configured, no automation) — the new system gets built on top of what exists.
- Have a CRM that is working but want to add lead gen, site visitor tracking, reporting, and automation end-to-end — that's a broader, full-flow build.
Existing infrastructure determines build type. There's no "right" answer — just an honest one that shapes where to start.
3 — What's the one thing that, if automated, would have the biggest impact on your revenue or your time?
Not the most interesting thing to automate. Not the easiest. The highest impact. For most businesses it's one of four: lead follow-up, client onboarding, scheduling, or reporting. The answer to this question becomes the primary success metric for the build — the number both sides are accountable to after the system goes live.
This answer becomes the headline of the build spec. Everything gets oriented around moving this one metric. If there's no clear answer yet, that's a sign to start with a diagnostic conversation rather than a build.
4 — Is there someone on your team who will own the system after it's built?
This is the question most businesses don't ask — and then wonder six months later why the system degraded. Every implemented system needs an owner. Not a technical administrator — just a person accountable for checking that it's working, flagging when something seems off, and being the point of contact if anything needs adjustment. In a solo practice, that's the owner. In a team, it's whoever manages operations. The system doesn't maintain itself, but with good documentation and the right setup, it takes less than 30 minutes a week to keep healthy.
A named owner means the system has a future. No owner means it degrades silently.
5 — What does success look like in 30 days, in a number you can measure?
Not "things feel more organized" — a number. Lead response time under a specific hour count. Follow-up completion rate above a specific percentage. Onboarding time cut from days to hours. Client complaints about a specific process: zero. Writing this number down before the build starts, then checking it at 30 days post-launch, is what tells you whether the investment paid off.
A defined success metric means real accountability on both sides. It also means knowing, 30 days from go-live, whether the investment paid off — rather than guessing.
How to Read Your Score
A scoping conversation can be short, focused, and productive, and a build can typically start within a couple of weeks of that call.
Worth surfacing the missing answers before committing to a build — rushing this step is exactly how systems end up half-scoped and under-adopted.
That's not a problem — it's the right starting point. A short diagnostic conversation, free and about ten minutes, will surface clear answers to all five questions before anything gets built.
Not sure how you'd score on these five? A free Jordan session is built to surface the answers before you talk to anyone about implementation — describe what's most manual and repetitive about your week, and go from there.