Outreach

This is the email we actually send.

No vague intro calls. We name the trigger, map the opportunity to the six activations, and ask for a working session with decisions and outputs. Below is the template, word for word.

The template

Six GTM activations, one email.

Subject options we rotate:

subject lines
[Company] GTM activation plan - six workflows, one operating system A contract path to make [Company]'s GTM motion AI-enabled Turning [buyer trigger] into a 90-day GTM activation
the email
Hi [First name], Following up on [specific conversation or trigger], I mapped the opportunity into six practical GTM activations I have built or operated at enterprise scale: 1. Inbound Automation Engine 2. Outbound Automation Engine 3. Pre-Call Intelligence 4. Post-Call Follow-Up 5. Workflow Execution Reporting 6. Daily GTM Executive Reporting Each activation combines a defined workflow, the right agent or skill set, human review controls, and measurable operating evidence. The aim is not to add another disconnected tool. It is to create one governed system that connects [CRM], [engagement tools], [meeting data], and leadership reporting. I recommend we start with a 60-90 minute activation workshop. We would select the first production workflow, confirm system owners and data access, define the pilot group, and agree on acceptance criteria. From there I can deliver a controlled 90-day activation, followed by optimization and team transfer. Would [option 1] or [option 2] work for the workshop? Best, Patrick

Outreach with rules.

The same discipline we install for clients governs our own pipeline.

R-01

Name the trigger first

Every email opens with the specific conversation or signal that prompted it. No generic compliments, no "hope you're well" filler.

R-02

Six activations, fixed

The offer never changes shape per prospect - only the examples get tailored to the buyer's stack. Consistency is the proof.

R-03

Ask for a working session

Not an intro call - a session with named participants, a duration, decisions to make, and outputs to produce.

R-04

Promise evidence, not pipeline

We never promise revenue. We promise observable workflow outputs, controls, and operating ownership - in writing, before we build.

Reply to the email.

Tell us your trigger - the CRM, the bottleneck, the quarter you're trying to save. We'll map it to the six activations and propose two workshop times.