Intake
Capture the facts that decide whether the opportunity deserves specialist review.
- Load profile
- Cooling type
- Facility status
Data Center Cooling RFQ
Follow up faster
Cooling RFQs stall when the team cannot see the project context, response owner, missing inputs, proposal status, and next buyer action. This page shows the AI System path we inspect before recommending a build.
Direct answer
A cooling RFQ needs one owner view
The useful system is simple: capture load profile, site readiness, facility constraint, buyer role, timeline, missing inputs, proposal owner, and next action in one place the team trusts.
Owner
Make the response owner, technical reviewer, partner dependency, and decision date visible.
- Response owner
- Technical reviewer
- Decision date
Follow-up
Track proposal status, missing buyer inputs, next action, and stale follow-up before the RFQ fades.
- Proposal status
- Missing inputs
- Next action
Checklist
What should be visible before engineering joins?
Specialist capacity is expensive. The handoff should include enough context for a useful review, not a discovery call that starts from zero.
Project facts
The opportunity record should show site, capacity, density, timeline, thermal constraint, and project stage.
- Site
- Capacity
- Project stage
Commercial facts
The team should know buyer role, procurement path, budget confidence, urgency, and expected decision process.
- Buyer role
- Procurement path
- Urgency
Follow-up facts
Every RFQ needs a next action, owner, due date, status reason, and a clear flag when buyer input is missing.
- Owner
- Due date
- Status reason
Related paths
Connect the RFQ page to the broader demand system
Cooling RFQs usually touch project readiness, specialist handoff, and power or commissioning dependencies. Link the pages so the buyer can self-diagnose before applying.
Project readiness
Use this when the RFQ is stuck because the project is not clearly funded, sited, timed, or owned.
- Readiness score
- Missing context
- Owner path
Specialist qualification
Use this when technical experts are joining too early or without the context they need.
- Escalation rules
- Handoff notes
- Capacity protection
Cooling plan
Use this when the RFQ problem is valuable enough to inspect inside the full AI System Plan.
- Plan path
- Build decision
- Next step
AI system fit
What AI can run here
For cooling rfq follow-up, 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