Revenue and demand workflow control surface
← All workflows

Revenue and demand

Lead intake and qualification

Turn an inbound request into a qualified next action before useful context is lost.

Trigger

A prospect submits a form, sends a message, books a call, or is referred.

Outcome

A confirmed next step, a clear decline, or an exception routed to the right owner.

Related operating model

Lead intake and qualification

  1. 01

    Capture

    Record the request, source, consent, and the minimum context needed without forcing a long form.

  2. 02

    Qualify

    Check fit, urgency, scope, decision owner, and information gaps against explicit rules.

  3. 03

    Route

    Assign one next action: reply, discovery, advisory, nurture, decline, or human review.

  4. 04

    Close the loop

    Confirm the action happened and retain the reason when a request is paused or declined.

Useful when

Requests are frequent enough that response quality, speed, or follow-up depends on memory and manual coordination.

Do not use this model when

There is no defined offer, owner, or minimum information needed to make a decision.

Controls that keep the workflow usable

A reliable system names its owner, retains the context needed for a decision, gives exceptions a visible path, and leaves a record of what happened.

  • A single record for source, context, owner, and current state.
  • A human route for ambiguous, sensitive, or high-value requests.
  • A visible follow-up deadline instead of an untracked inbox promise.