SAAS OUTREACH GUIDE
From a signal to a relevant next step.
A reasoning framework for your outreach, illustrated with fictional SaaS examples. This is not a click-by-click app setup guide.
1. Start with what actually changed
Read the source and identify the account, the event, and when it happened. Separate the observation from your interpretation. A hiring announcement gives you evidence of hiring; it does not tell you that a company is shopping for software.
2. Apply your seller lens
Write down the accounts and roles you serve, what your product does, and the claims you can substantiate. Ask why this particular event relates to your offer. If the connection is weak, reconsider the outreach instead of stretching the signal.
3. Choose a relevant recipient
Look for a role connected to the topic and review the person/account match. Treat role relevance as a hypothesis. Do not turn a job title into a claim that someone owns budget, requested outreach, or has authority to buy.
4. Carry the context into each step
Keep the microsequence short and coherent. Open with an accurate reference to the event, connect it to an approved product capability, and ask a proportionate question. Follow-ups should build on that reasoning without inventing urgency or repeating a generic pitch.
5. Review before taking action
Recheck the source, account, recipient, and approved claims across the whole sequence. Edit language that overstates the evidence. Confirm the channel is supported and the message is appropriate before using the draft. The marketing demonstration stops at review and sends nothing.
Follow the connected workflow.
Explore the interactive product story and see how evidence stays attached to a seller-reviewed draft.