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 Revenue 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 audit
Use this when the RFQ problem is valuable enough to inspect inside the full Revenue Audit.
- Audit path
- Build case
- Next step
Next step
Start with the audit.
If there is a measurable revenue problem worth fixing, the Revenue Audit shows whether a Revenue System Sprint is the right next move.
Apply for a Revenue Audit