Motion

Operational context

Motion is an established B2B SaaS company doing eight figures in revenue. Later in the company's growth, the need shifted from product building to commercial operations: the revenue teams needed better systems to move faster without adding equivalent headcount.

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 to scale efficiently.

Where work was breaking

By the time the role shifted into GTM engineering, Motion already had a functioning revenue motion, but execution was too dependent on manual effort:

• • 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 problem was not whether the teams could execute. The problem was that the operating layer between systems, campaigns, and people was too manual to support the company's growth ambitions.

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: use systems work to unlock revenue team throughput, not just ship product features.

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 allowed Motion to deliver relevance at scale without increasing sales or marketing headcount.

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, more coordination overhead, or brittle one-off workflows.

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

Operational outcome

The impact was immediate and measurable.

• • 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 and with higher intent
• • Onboarding and activation improved due to clearer value delivery

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

Both revenue and activation improved, and teams gained confidence to request and run more ambitious GTM experiments.

What this proves

We can build systems that let commercial teams move with leverage instead of manual effort. For ops-heavy service businesses, the transferable lesson is the same: when the coordination layer is too manual, growth gets capped long before demand does.

Result: Revenue teams moved faster, ran higher-leverage experiments, and reached prospects with less coordination overhead.