Stage
Know whether the buyer is researching, comparing vendors, responding to an RFQ, designing, procuring, expanding, or fixing a live constraint.
- Research
- RFQ/RFP
- Procurement
AI Infrastructure Readiness
Qualify project readiness
AI infrastructure demand gets expensive when every inquiry sounds urgent but the project context is incomplete. A readiness intake separates real projects from early research before specialist capacity is spent.
Direct answer
Readiness is the filter before the handoff
A useful project context intake captures project stage, site status, capacity, timeline, buyer role, budget confidence, procurement path, constraints, and next action before the opportunity moves to a specialist.
Site
Capture geography, site control, facility status, drawings/specs, and any dependency that changes feasibility.
- Geography
- Site control
- Specs
Owner
Identify whether the contact can move the project or is gathering information for another buyer, EPC, developer, or team.
- Buyer role
- Decision path
- Next owner
Readiness fields
The CRM should reflect the real project path
Do not overload the team with fields nobody trusts. Use the few fields that decide routing, urgency, follow-up, and whether the project deserves specialist review.
Project context
Stage, use case, capacity, timeline, site readiness, geography, and known technical constraints.
- Stage
- Capacity
- Constraints
Commercial context
Buyer role, budget confidence, procurement path, partner dependency, urgency, and expected next step.
- Buyer role
- Budget confidence
- Procurement
Follow-up context
Internal owner, missing info, next action, due date, stale reason, and escalation trigger.
- Owner
- Due date
- Escalation trigger
Related paths
Use the right page for the breakdown
Project readiness usually appears with RFQ follow-up, specialist handoff, or category-specific qualification problems.
Cooling RFQ follow-up
Use this when cooling inquiries are real but response owner, missing inputs, and proposal next step are hard to see.
- RFQ owner
- Proposal status
- Missing inputs
Specialist qualification
Use this when the project may be real but specialists are being pulled in before the right facts are captured.
- Handoff filter
- Escalation rules
- Context packet
AI infrastructure demand
Use this as the parent page when the team needs the full demand system view.
- Intake
- Handoff
- Pipeline view
Readiness intake example
Use this proof asset when the team needs a small example of the fields that should be visible before handoff.
- Stage
- Site
- Action
AI system fit
What AI can run here
For project readiness intake, 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