Reactivate a founder's network with a useful reason

When to use it

A founder identifies a known contact or a genuine reconnection opportunity starts this workflow. Choose relevant existing relationships and a timely resource instead of sending one pitch to every connection. The intended output is a reviewed personal reconnection queue with next-action notes. 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 relationship notes, current role, company fit and approved resources. 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. Verify the current role and what the relationship actually is.
2. Match a useful resource to a plausible current problem.
3. Check active deals and other owner conversations.
4. Draft a personal note for founder review and individual sending.

At the decision gate, ask: Does this note have a credible relationship and useful reason? If the answer is no: hold it or choose a lighter public interaction. 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: an exported connection list is described as a book of warm buyers. 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 responses, useful introductions and qualified 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.