Green
Clear buyer role, real project, relevant need, known timeline, budget confidence, owner assigned, and next action set.
- Real project
- Owner assigned
- Next action
Readiness Scorecard
Score readiness
A readiness scorecard helps the team decide whether an inquiry should move to sales review, specialist handoff, proposal follow-up, later follow-up, or disqualification.
Direct answer
A readiness scorecard should guide routing
Score buyer role, project stage, site status, timeline, budget confidence, technical match, missing info, and next action before the inquiry reaches expensive specialist capacity.
Yellow
Promising opportunity, but missing site, specs, capacity, timeline, authority, or budget context.
- Promising
- Missing context
- Clarify first
Red
Research-only, weak fit, no owner, no timeline, unclear need, or low-value request.
- Research-only
- Weak fit
- No owner
Score fields
Score only what changes the next action
A lightweight score is easier to use than a perfect score nobody updates.
Fit
Need, category, geography, buyer role, technical match, and project stage.
- Need
- Role
- Stage
Readiness
Site, capacity, timeline, budget confidence, procurement path, and required inputs.
- Site
- Timeline
- Inputs
Movement
Owner, next action, due date, specialist trigger, stale reason, and follow-up path.
- Owner
- Due date
- Follow-up path
Related paths
Use the score to route the work
A scorecard is only useful when it changes the owner, the follow-up, or the decision to involve specialists.
Inquiry routing
Use this when readiness score should decide the first owner.
- Route
- Owner
- Next step
Specialist qualification
Use this when the score should protect specialists from low-readiness work.
- Gate
- Handoff
- Escalation
Project readiness intake
Use this when the intake needs better fields before scoring can work.
- Fields
- Context
- Readiness
AI system fit
What AI can run here
For project readiness scorecard, 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