Project facts
Capture the facts that decide whether the request is ready to move: stage, site, capacity, timeline, and constraint.
- Stage
- Site
- Capacity
Proof Asset
Inspect readiness first
A readiness intake example should show what is missing before the handoff. The useful version is short, practical, and tied to the next action your team can actually take.
Direct answer
A readiness intake should make the handoff obvious
The intake should show project stage, site status, capacity, timeline, buyer role, budget confidence, missing inputs, internal owner, and the next action before a proposal or specialist review begins.
Buyer facts
Capture who the contact is, who decides, how procurement works, and whether budget has been discussed.
- Role
- Decision path
- Budget
Action facts
Capture what is missing, who owns the next step, when it is due, and what happens if the buyer does not respond.
- Missing input
- Owner
- Due date
Intake example
Keep the example small enough to use
The plan checks whether these fields exist, whether the team trusts them, and whether they change how an inquiry moves.
Stage
Research, vendor comparison, RFQ, design, procurement, expansion, replacement, or live issue.
- Current stage
- Project type
- Urgency
Site and plan
Site status, geography, capacity, facility type, known constraints, and required documentation.
- Site status
- Scope
- Constraints
Commercial path
Buyer role, budget confidence, procurement path, partner dependency, decision group, and timing.
- Buyer role
- Budget confidence
- Timing
Next action
Internal owner, missing input, response date, review need, escalation trigger, and outcome after follow-up.
- Owner
- Review
- Outcome
Review view
The weekly review should show the exceptions
A readiness example becomes useful when it helps the team see which opportunities are ready, which need missing facts, and which should wait.
Ready
The project has enough context for proposal work, specialist review, or a clear commercial next step.
- Clear stage
- Clear owner
- Clear action
Missing facts
The project may be serious, but site, capacity, buyer role, budget, timing, or documentation is still missing.
- Site
- Budget
- Timing
Wait
The opportunity should stay visible, but the next move is education, later follow-up, or a clean close of the loop.
- Educate
- Follow up later
- Close loop
Related paths
Connect intake to the rest of the system
Readiness intake works best when it connects to CRM stages, proposal workflow, and a weekly pipeline view.
Project readiness guide
Use this when you need the broader readiness page before reviewing an example.
- Stage
- Site
- Owner
CRM stage map
Use this when readiness needs to drive cleaner stage movement and exit criteria.
- Stage
- Criteria
- Action
Proposal workflow
Use this when missing readiness context keeps slowing proposal movement after send.
- Owner
- Risk
- Action
AI system fit
What AI can run here
For readiness intake example, 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