Sales Practice

Run a bounded personalised outreach batch

Protect product time with a fixed research brief, manually checked messages, and a reply review before expansion.

Preparation
One setup block, scheduled research tasks, and a review after the batch.
Difficulty
Moderate
Task
Bound personalised outreach
Back to the Task: Bound personalised outreach

Before you start

Get what you need before you start

  • Choose one customer profile, one buyer problem hypothesis, and a stop date.
  • Complete the legal and privacy review for each recipient type and jurisdiction.

Steps

Work through the method

Use the listed inputs and tools. Check the evidence when you need to verify a step.

  1. Set the batch boundary

    Choose the account count, required research fields, allowed sources, message owner, review point, stop date, and maximum follow-up path.

    Why it matters: A fixed boundary protects building time and makes the experiment reviewable.

    Input
    The chosen profile, available founder time, and applicable outreach rules.
    Output
    A batch brief with its scope, owner, review date, and compliance checks.
    Tools in this stepHubSpot Sales Hub

    Evidence for this step

  2. Draft and check each message

    Use one sourced buyer signal and one relevant question. Check the source, sender identity, privacy information, opt-out route, and suppression status before enrolment.

    Why it matters: Per-contact review keeps sourced relevance and required controls visible.

    Input
    The batch brief, sourced account row, and suppression record.
    Output
    A checked message and permitted contact record for each recipient.
    Tools in this stepHubSpot Sales Hub

    Evidence for this step

  3. Pause and review the batch

    Complete each manual task, classify replies and objections against the original hypothesis, honour objections, and decide whether to revise, stop, or run another small batch.

    Why it matters: Replies provide evidence for revision while silence leaves several explanations unresolved.

    Input
    Sent records, replies, objections, bounces, and founder time used.
    Output
    A batch review with learning, suppressions, unresolved questions, and the next decision.
    Tools in this stepHubSpot Sales Hub

    Evidence for this step

Success checks

Check the result before you finish

  • The batch stayed inside its account, time, and follow-up boundary.
  • Every message received a source and compliance check.
  • Replies and objections changed an explicit assumption or next decision.

Failure modes

Watch for these problems

  • Research expands without a stop rule. Return to the required fields.
  • Automation sends an unchecked message. Require a manual task before enrolment or follow-up.
  • A non-response is counted as validation. Record it as unresolved.

Tools

Choose the tools you need

Sources

Read the sources behind this practice

Check what each source supports and where the advice has limits.