Sales owner
Owns qualified discovery when buyer role, need, and next step are clear enough to move.
- Qualified discovery
- Buyer role
- Next step
Inquiry Routing
High-value technical inquiries need a routing rule before the team spends expert capacity. The goal is simple: send the right work to the right owner with the right next action.
Direct answer
Route by buyer role, project stage, urgency, fit, missing context, potential value, technical complexity, and next action. The route should decide owner before a specialist is invited.
Owns qualified discovery when buyer role, need, and next step are clear enough to move.
Joins only when the opportunity has context and a technical question worth answering.
Handles research-only, incomplete, early-stage, or low-readiness contacts without wasting expert capacity.
Routing table
The routing rule should be simple enough to run daily and strict enough to protect the team.
Clear buyer, relevant need, real timeline, known project context, and a next-step reason.
Qualified opportunity with a technical blocker, proposal risk, implementation question, or decision requirement.
Early research, missing context, unclear authority, weak fit, or no immediate decision path.
Related paths
Buyer role, readiness score, and proposal workflow should all support the routing rule.
Use this when the first routing signal should be who the buyer is.
Use this when routing should depend on red, yellow, or green readiness.
Use this when routing breaks later in proposal follow-up.
Next step
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