Skip to main content

Engine for technical B2B · Proof Asset

Inspect readiness first.

A readiness intake example should show what is missing before the handoff.

Technical system map for Inspect readiness first.

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.

  • Project facts

    Capture the facts that decide whether the request is ready to move: stage, site, capacity, timeline, and constraint.

    • Stage
    • Site
    • Capacity
  • 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 scope

    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

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
    Open
  • CRM stage map

    Use this when readiness needs to drive cleaner stage movement and exit criteria.

    • Stage
    • Criteria
    • Action
    Open
  • Proposal workflow

    Use this when missing readiness context keeps slowing proposal movement after send.

    • Owner
    • Risk
    • Action
    Open

Next step

Test a short intake on real inquiries.

We turn your own inquiries into a short readiness intake and show which questions would have saved a handoff.