How we plan

The AI System Plan is a structured submission. The form asks for the seven facts we need to write back with the named gap. It is free because the no is a real outcome we want to deliver fast.

The seven facts we collect

1. Annual revenue band. Sets the realistic ceiling for what fixing the gap is worth.
2. Implementation budget. Tells us whether a Sprint is even in range.
3. The operating outcome. The result the client wants the system to improve: booked meetings, cleaner client updates, faster reporting, better follow-up, or fewer manual handoffs.
4. Urgency. The named timeline. 30 days, 60 days, this quarter.
5. Current CRM and lead volume. Tells us the operational reality.
6. Free-form workflow note. The client describes the repeated work in their own words.
7. Assessment responses. Ten short questions on workflow orchestration, measurable movement measurement, attribution fidelity.

How we read it

A human reviewer reads every submission. Not an AI summarizer, not a templated response. The qualification engine scores the submission against four dimensions: potential value, urgency, operational build decision, and decision-maker access. The score produces a next step.

• Plan review. The AI System Build is a clean fit. We send the named gap, likely build path, and review link in one email.
• Follow-up. A real gap exists, but urgency, budget, CRM maturity, or lead volume needs sharper definition before a Sprint is the obvious move. We send the named gap and a short recommendation for what to tighten first.
• Wait for now. Either the gap is too small to justify the Sprint cost, the timeline is misaligned, or the plan reveals the real problem is upstream of AI systems work. We say so, name the better-fit option, and end the conversation honestly.

The 24-hour rule

Every plan gets a response within one business day. No exceptions. The respondent is a named human, not the company. The brand-voice rule we apply to ourselves: the response email has a number, a named gap, and a next action. If we cannot find a number, we ask one clarifying question instead of guessing.

What the plan is not

It is not a generic AI build decision assessment. It is not a checklist. It is not a sales call disguised as discovery. It is a written diagnosis from a human reviewer who is looking for the workflow, source material, owner, review loop, and business result.

Why this scales

Reading plans is one of the most useful hours in the company. Every plan teaches us where the gaps cluster, which verticals are under-served, which automations need to ship next. The plan funnel is also the recruiting funnel for new client work. Bad plans are not noise, they are signal about market gaps we have not addressed.