How Motion turned repeated GTM execution into a reusable operating system

Executive summary

Motion already had strong revenue momentum. The constraint was not strategy; it was execution speed.

Revenue teams needed to launch more campaigns, personalize outreach, test onboarding flows, and coordinate across systems without turning every initiative into a custom engineering project. The work focused on reusable systems that made repeated GTM execution faster, more reliable, and less dependent on manual coordination.

Where work was breaking

By the time the role shifted into GTM engineering, Motion already had a functioning revenue motion, but execution still depended on too much manual setup and cross-team follow-through:

• • outbound prospecting required significant manual research and setup
• • personalization existed, but it did not scale
• • onboarding and activation work needed tighter coordination
• • sales and marketing teams relied on engineering for one-off efforts

The teams could execute. The issue was that the coordination layer between systems, campaigns, and people was too manual to stay consistent at scale.

System built

Role: GTM engineering (full-funnel).

• • Partners: Head of Product, Head of Sales

The system focus areas were:

• • lead capture
• • onboarding and activation
• • personalized prospecting at scale

The mandate was simple: build the operating layer behind the work so revenue teams could launch and iterate without waiting on repeated one-off support.

Key initiatives included:

• • redesigned onboarding flows to improve education and time-to-value
• • experiments to validate onboarding and activation improvements
• • reusable workflows that reduced friction for repeated GTM motions
• • scalable, personalized outbound workflows
• • dynamically generated, personalized landing pages tied to outreach campaigns

The most impactful system combined:

1. 1. large-scale prospect insight gathering
2. 2. personalized outbound emails
3. 3. custom landing pages tailored to each prospect

This gave Motion a repeatable system for personalization instead of a workflow that depended on manual research and setup each time.

Constraints and edge cases

The challenge was not just building a campaign engine. The systems had to support rapid iteration across multiple teams without creating more engineering dependency, brittle one-off workflows, or hidden coordination work.

That meant treating commercial operations like real systems work: reusable foundations, clear launch paths, and enough structure that teams could keep running campaigns without rebuilding the process from scratch each time.

Operational outcome

The system changed how fast revenue teams could execute repeated work.

• • Sales and marketing could launch personalized outbound campaigns to 2,000+ prospects in hours, not weeks
• • What previously required 2–3 BDRs working for a month could now be done by the system
• • Landing pages and outbound campaigns could be generated as part of one coordinated workflow
• • Teams could test new GTM motions without rebuilding the process each time
• • Prospects reached demos faster because campaigns and landing pages were easier to launch and coordinate
• • Onboarding and activation improved through clearer, more repeatable education flows

The first outbound campaign using this system achieved the highest click-through rate Motion had seen within 24 hours of launch.

The result was a more reliable operating layer for outbound and onboarding, plus more confidence from internal teams to run new GTM experiments without the same coordination burden.

What this proves

The specific workflow was different, but the operating problem is familiar: teams had work they needed to repeat often, but the process depended on too much manual setup, one-off coordination, and internal follow-through. That is the same pattern that shows up when compliance service businesses manage recurring work, closeout, quoting, renewals, and billing across disconnected tools.

Why it matters for recurring service operators: repeated work breaks down when every launch, handoff, or follow-up depends on manual setup.