SaaS Operator Guide

Guide 03 / Run Outbound

Run one focused outreach test and read the replies honestly

A test has a start, an end, a message, and a rule for what the replies mean. This guide covers sending, following up, interpreting what comes back, and handing a real conversation to discovery.

The shape of a bounded test

Fix four things before the first send: the list, the message, the window and the review date. Then do not change them mid-test. If you edit the message on day three, you no longer have an experiment; you have a mood. When something is plainly broken, such as a dead link, fix it and write down that you did.

Keep the volume modest enough that you can personalize and follow up properly. A test you can finish is worth more than a campaign you abandon. Founder-run routines have an obvious cost, which is time, and an obvious benefit, which is that every reply lands in front of the person who can act on it. A Reddit r/SaaS thread on technical founders and sales reports technical founders describing missed follow-ups, delayed demos and unclear targeting. Those are anecdotes, not representative evidence, but they point at a design requirement: put follow-ups and demo scheduling in the plan, with dates, so they cannot slip silently.

Write the message

A first message needs to do three jobs in a few sentences: show you know the recipient’s situation, name the problem in their language, and make one small ask. The situation line should reference the trigger you recorded. If you cannot write that line truthfully, the contact does not belong in the test.

Keep the ask small enough to answer in a sentence. “Is this something your team handles by hand?” is easier to answer than a request for thirty minutes. The tradeoff is that small asks produce lighter signals, so you will read replies more carefully.

Avoid claims you cannot support. Do not promise results, quote averages from other customers as if universal, or imply endorsements. If you cite something, cite it plainly.

Plan the follow-up

Decide in advance how many follow-ups you will send and how far apart. A common structure is one initial message and one or two short follow-ups that add a new angle rather than repeating the first. Each follow-up should be answerable by itself. Then stop. A contact who has not replied after your planned sequence goes into the “no signal” pile, not into an endless nurture loop.

Record every send with a date and the version of the message. Without that, you cannot say later which variable mattered.

Read the replies without flattering yourself

As a practical classification method, sort responses into a small number of categories, and record the category beside the reply. This is not a validated buying-intent score:

  • Describes the problem. The recipient describes current handling or a recent episode. Useful reported detail, not proof they will buy.
  • Wrong person. Points you to a colleague. Check the referral before updating the buyer map.
  • Not now. Gives a reason tied to timing or budget. Note the reason without assuming a future purchase.
  • Not a problem. Says it does not happen. Evidence against this account-level hypothesis; do not argue.
  • Polite interest with no detail. An expression of interest, not demonstrated behavior.
  • Silence. Ambiguous by nature.

One reading error to guard against is treating enthusiasm as demonstrated behavior. “Sounds interesting” does not describe a past action. Kurt Bostelaar, “How to capture customer jobs, pains & gains that aren’t subjective,” Strategyzer, July 25, 2016 recommends asking about past behavior rather than opinions. Our practical adaptation is to request a recent episode and distinguish a person's report from something you have observed directly. Neither proves buying intent, prevalence across the market, or eventual revenue.

Discovery and handoff

When someone agrees to talk, the job changes from testing a message to learning how this company buys. Treat the first call as discovery, not a pitch. Your objectives are to confirm the problem exists in their words, find out who else is involved, and learn what would have to be true for them to act.

Questions that serve those objectives: What happened the last time this came up? Who else was involved? What did you try? What would have to happen internally for a change to be approved? Who would need to see this before money moves?

For this routine, a handoff means moving a conversation to an agreed next stage, such as a demo, trial or written proposal. Record the possible champion, budget owner as far as known, stated problem, open questions and agreed next action. Name an owner and ask for a date; if timing is not agreed, explicitly write pending rather than inventing a commitment. A scheduled demo is not a sale.

Be explicit about what you do not yet know. Unknown budget owner, unknown timeline and unknown process are all legitimate entries. Writing them down turns them into the agenda for the next call.

Review and decide

On the review date, open your decision rule and apply it. Count replies by pile, list the exact phrases recipients used, and note anything you changed mid-test. Then choose one of three outcomes: continue with the same segment and message, change exactly one variable, or drop the segment. Resist choosing a fourth option, which is to keep going without deciding.

The result of one test is not a verdict on your business. It is one dated entry in your log. Keep entries short, and keep the next experiment as small as this one.

Open the worksheetBack to the buyer map

Sources for this guide