Vertical ICP Segmentation for Cold Email: Research Worksheet

Vertical segmentation is useful when it changes the business problem, buyer role, proof, or routing. It is not useful when it merely swaps an industry label into a generic template. Start with evidence-backed signals, define exclusions, map the workflow, and stop when the evidence is too thin to justify a separate track.

Build the segment

Name the proposed vertical and write the reason it deserves its own hypothesis. Collect public evidence such as a recurring workflow, role pattern, terminology, technology signal, or procurement constraint. Record source and date. Avoid stereotypes about how an industry “usually” operates.

Define inclusion and exclusion rules before building the list. An inclusion rule might require a public role or service signal. An exclusion rule might remove companies without the relevant workflow, locations outside the operating area, or records lacking an identifiable business owner. Map the role who feels the problem, the role who evaluates, and the role who approves.

Set a stop rule: if the team cannot verify enough consistent signals or cannot explain why the message differs, do not create a new vertical track. Use the reply-rate measurement guide only after the segment definition and denominator are fixed.

Google’s sender guidance stresses authentication, opt-out, and reputation practices for delivery [1]. Segmentation does not override those fundamentals. RepMail can help keep event and suppression data visible, while your team owns the segment definition and evidence.

Make the segment falsifiable

Create a track only when evidence predicts a different problem, buyer, proof standard, message, or route. Write: organizations with signal X may face workflow Y, and role Z can validate it. Define inclusion, exclusion, source, freshness, and stop threshold. Changing only an industry noun is not a new segment.

Classify replies as qualified, neutral, wrong person, negative, and opt-out; opens do not prove fit. Compare with cold email reply-rate measurement and use Google sender guidelines only as receiver context. Merge back when routing and offer are not materially different.

Related resources

Use the adjacent workflow and then review the next operational guide to keep this decision connected to the wider RepMail resource graph.

References

[1] https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business "FTC CAN-SPAM Act: A Compliance Guide for Business" [2] https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/electronic-and-telephone-marketing/electronic-mail-marketing/ "ICO Electronic Mail Marketing" [3] https://support.google.com/mail/answer/81126?hl=en-GB "Google Email Sender Guidelines"