Starting signal
A serious buyer asks about capacity, timeline, site readiness, integration, or proposal plan, but the request arrives with incomplete context.
- Buyer role
- Project stage
- Requested outcome
Proof Asset
Trace one inquiry
A useful plan does not start with a software wishlist. It follows one serious inquiry until the team can see the buyer, project context, handoff risk, next action, and whether a sprint is worth planning.
Direct answer
A plan teardown follows one real inquiry
The teardown is anonymized, but the operating path is concrete: what arrived, what was missing, who needed context, what the CRM failed to show, and what decision the plan supported.
Missing context
The plan checks whether sales can capture the facts before founders, engineers, estimators, or channel owners spend time.
- Site facts
- Timeline
- Constraints
Decision point
The team leaves with a recommendation: build the AI system now, gather more proof, continue later follow-up, or close the loop.
- Build
- Wait
- Close out
Teardown path
Follow the inquiry until the next action is obvious
A teardown should make the sales motion easier to operate, not more complicated. The output is a shorter path to owner, risk, follow-up, and decision.
Capture
Record buyer role, facility or project type, capacity, site status, timeline, budget confidence, and technical constraints.
- Role
- Capacity
- Constraint
Route
Decide whether sales, estimating, engineering, leadership, channel team, or later follow-up should own the next step.
- Owner
- Escalation
- Handoff notes
Review
Surface proposal status, missing buyer inputs, stale follow-up, channel dependencies, and the next action in the weekly view.
- Status
- Risk
- Next action
Build decision
Only build when the gap is visible and valuable
The teardown protects the team from premature automation. If the inquiry path is rare or low-value, the recommendation should be simple process cleanup instead of a sprint.
Ready to build
The problem repeats, the opportunity value is meaningful, the internal owner is clear, and the CRM can support the workflow.
- Repeatable
- Valuable
- Owned
Needs more proof
The market is real, but volume, handoff quality, proposal movement, or CRM trust needs more evidence before a build.
- More data
- Cleaner fields
- Recheck later
Wait
The inquiry path is too early, too rare, too low-value, or blocked by missing ownership.
- Missing owner
- Low value
- Too early
Related paths
Use the teardown with the proof layer
These pages help a buyer compare the teardown against benchmarks, stage-map requirements, and the commercial plan page.
Benchmarks
Compare the inquiry path against response, qualification, handoff, proposal movement, and visibility gaps.
- Response
- Qualification
- Movement
CRM stage map
See how one messy inquiry path should become clearer stages, owners, and next actions.
- Stage
- Owner
- Action
Pipeline dashboard
See which fields the teardown should make visible in the weekly operating view.
- Owner
- Risk
- Action
AI infrastructure plan
Apply when the inquiry path is valuable enough for a full Technical AI System Plan.
- Plan
- Build decision
- Next step
AI system fit
What AI can run here
For plan teardown, the useful AI system is not a generic chatbot. It is an operating layer that reads project or buyer context, prepares the next owner action, flags missing information, and keeps follow-up visible. The team still owns technical judgment, pricing, plan, proposal language, and customer commitments.
Inputs to bring
Bring the source material already used to judge the opportunity: CRM fields, RFQs, forms, call notes, proposal status, files, source pages, buyer role, owner, due date, and missing facts.
- CRM and forms
- RFQ or proposal context
- Owner and due date
Useful AI work
AI can summarize inquiries, classify readiness, draft missing-info requests, prepare handoff notes, update operating views, and surface stale follow-up before opportunities drift.
- Summaries
- Readiness classification
- Follow-up prep
Human gate
A person approves technical fit, engineering assumptions, pricing, legal terms, customer promises, sensitive language, and whether the opportunity deserves specialist time.
- Technical approval
- Pricing and plan
- Customer promise
Next pages
Keep the diagnosis connected
Technical buyers often need more than one page before they trust the recommendation. These links connect the specific problem to the larger AI System Plan path.
Technical AI Systems
Use the hub when the team needs the full view of project context, specialist handoff, proposal follow-up, and pipeline visibility.
- Hub
- Use cases
- Technical fit
Run the scorecard
Use the AI Infrastructure Scorecard when the page points to a repeatable project context or qualified-demand problem.
- Inputs
- Build decision
- Next step
Conversion Skills
Use Conversion Skills to see the public method behind prompts, tools, review gates, handoffs, and repeatable AI work.
- Skills
- Tools
- Review
Next step
Find the gap first
Start with the repeated work, the source material, and the business result. Then choose strategy, an agent, or a custom AI system.
Choose the AI path