Route product signups by fit and declared use

When to use it

A product signup with a declared business use starts this workflow. Keep access and onboarding separate from sales prioritization, then assign accounts using reliable company context. The intended output is an owned signup receipt with fit, usage facts and next action. A useful receipt names the accountable person and the next action; it should make the commercial decision easier to inspect.

This is an original GTMhub reference design. It explains how we would run the job, with tools selected for the company's existing stack. It is not presented as completed client delivery or measured commercial performance.

Inputs and decision boundaries

Confirm submitted company, product event, account associations and lifecycle rules. Keep the original source and observed date alongside each fact. Missing context stays unknown until it is resolved. Facts, interpretations and proposed actions should remain distinguishable in the handoff.

Your company brain holds the approved rules and proof; the live system holds current account state and ownership. Read both before making an operational change. Assign an exception owner before launch so an uncertain case has somewhere useful to go.

Run the job

1. Preserve the signup and onboarding state.
2. Resolve an existing company and relationship owner.
3. Assess company fit separately from product behavior.
4. Route sales-eligible accounts with the signup context and unknowns visible.

At the decision gate, ask: Does reliable evidence support a sales-relevant business account? If the answer is no: keep normal onboarding and request missing business context only when needed. Only the supported path proceeds to its output. A stopped job should preserve the reason and what would let an owner resolve it.

The output to inspect

Failure and recovery

The material failure to watch is this: a personal email is forced into a guessed employer or rejected automatically. Stop that path and preserve the underlying evidence. Repairing a field or a source is different from changing the commercial rule; record which decision was made.

If a connected system fails, keep the original request or event and expose its unresolved state. Retry only the incomplete action, with a stable event key where writes are involved. Do not let a retry create a second owner task or bypass a previous exclusion.

Test before making it live

Replay a supported case, an incomplete case and the failure described above. Where the job writes a record or creates a task, replay the same event twice and inspect the result. Check that the exception owner can understand the hold reason without reconstructing every step.

Judge the result

Track onboarding completion, owner latency and qualified sales conversations. Record the sample, dates and definitions before evaluating a change. Operational success shows that the job behaved as designed; commercial outcomes need their own mature evidence.

Return reviewed corrections to the company brain with the decision date and rule version. Keep the original observation available. The decision register records what changed and why, while the GTM brain guide explains how the job fits into one company system.