Motion

Operational context

Motion is an established B2B SaaS company doing eight figures in revenue. Later in the company's growth, part of the need shifted from product building to commercial operations: the revenue teams needed better systems so repeated work did not depend on one-off engineering effort.

The work here was not about pretending Motion was a field-service business. It was about solving an adjacent operations problem: high-volume, cross-functional coordination that was too manual and too fragmented to stay reliable as volume increased.

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 product-led growth mechanics
• • introduction of self-serve plans to reduce friction
• • 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
• • 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

Motion is not in the same industry Reppable serves today, but the systems lesson transfers directly. When work keeps stalling between teams, tools, and follow-through steps, the fix is often the coordination layer behind the workflow, not more manual effort on top.

Transferable lesson: even outside field service, the same systems principle applies when work stalls between teams, tools, and repeated follow-through.