Hybrid motions

Most founders start pure: either product-led, sales-led, or partner-led. They defend the purity because it is simple. One motion, one org, one set of incentives. Then the market teaches them that no market is actually pure. Healthcare is partner-led, but there is a sales-led tail of large hospital systems. SaaS is PLG, but enterprise customers demand dedicated support and compliance reviews. Developer tools are community-led, but the largest companies want an account manager.

By year two or three, most successful GTM operations run hybrid. The purity they once defended is gone. They have two or three motions running in parallel, each optimized for a different segment. The ones that thrive have made hybrid explicit: they name which motion owns each segment, they specify where handoffs happen, and they build organizational structure to prevent the conflicts that destroy hybrid architecture. The ones that collapse built hybrid by accident and never clarified who owns what.

This is the difference between deliberate hybrid and accidental hybrid. The first is operationally sound. The second is organizational chaos.

Why no market is pure

Start with first principles. A motion must satisfy one core constraint: CAC payback must fit the economics of the buyer.

A product-led motion works when CAC is <$500 and you can prove value in 30 days. The buyer onboards themselves. The product is the salesperson.

A sales-led motion works when ACV is >$50k and you can spend 3-6 months on a single deal. You hire salespeople whose fully-loaded cost ($300-500k/year per AE) can be justified by deal size and close rate.

A partner-led motion works when your go-to-market requires deep technical or industry integration that partners already own. You cannot build it faster than you can partner with those who already have it.

The moment your market has accounts with >3x ACV spread—some at $5k, some at $150k—you cannot serve all of them with one motion. Low-ACV accounts cannot support a sales-led motion’s CAC. High-ACV accounts chafe under PLG’s self-serve friction. You have two markets under one roof.

The same applies to buyer complexity. If some accounts close in 2 weeks (bottom-up adoption, no committee) and others take 6 months (procurement, legal, board approval), one motion cannot serve both. Add distinct buyer types—some buy through procurement, some through DevOps, some through the CTO—and the answer is clear: you need multiple motions.

This is not a failure. This is economics. Your market is big enough that it spans multiple buying patterns, and serving it requires different GTMs.

The diagnostic: when is hybrid necessary vs. when is it motion confusion?

Ask yourself four questions. Your answers tell you whether you need hybrid or whether you are confusing motion indecision with hybrid strategy.

First: what is the ACV spread?

Calculate the ACV of your top 10% of customers, your median customer, and your bottom 10%. If the top 10% is >3x the median, you have two economic tiers. A motion optimized for one will not work for the other.

Example: you sell infrastructure software.

• Bottom 10%: $5k ACV. These are small teams at startups. They self-serve, use free trials, upgrade when they hit a usage limit.
• Median: $20k ACV. Mid-market teams. They need a sales conversation and some technical integration.
• Top 10%: $200k ACV. Enterprise. They demand procurement review, compliance validation, and a dedicated account manager.

The bottom and top tiers are 40x apart. One motion cannot serve both. You need at least two: PLG for small teams, SLG for enterprise.

If your spread is <2x (everyone clusters around $20-30k), you have one market and one motion. Do not invent hybrid. Hybrid is not sophisticated. Pure and executed well is.

Second: what is the buyer complexity spread?

Plot your deals on two axes: days to close (x) and number of people in the decision committee (y).

• Quick deals: 2-4 weeks, 1-2 people. These are bottom-up buys. One engineer decides.
• Medium deals: 4-8 weeks, 3-5 people. A team decides.
• Long deals: 12+ weeks, 7+ people (CTO, VP Eng, Security, Finance, Legal). Procurement-driven.

If you have quick deals and long deals, you have two different motions. A sales motion that works for procurement-driven deals (needs compliance docs, contract negotiation, executive sponsorship) does not work for bottom-up deals (need technical credibility, developer community, free tier). One motion will dominate and starve the other.

If all your deals cluster in the 4-8 week range with similar committee sizes, you have one buying motion. Run it hard. Do not invent parallel motions.

Third: do different segments respond to different entry points?

This is a behavioral question. Where do your different customer segments first encounter you?

• Some come through the product (free trial, open source, community).
• Some come through sales (SDR outreach, event, referral).
• Some come through partners (integrations, resellers, technology partners).
• Some come through channels (affiliate, marketplace, app store).

If all segments come through the same entry point, you have one motion with different segments. You do not need parallel motions; you need better segmentation within one motion.

If different segments have different entry points and respond to different pitches, you have motion diversity. The product-led segment is not convinced by a sales conversation. The sales-led segment is not convinced by a free trial. The partner-led segment does not want direct contact; they want to work through their partner. You need multiple motions because the segments are optimized for different channels.

Fourth: does a single motion cannibalizes or conflicts with another?

This is the killer question. Run two motions and ask: does running motion A prevent motion B from working?

Example: Slack in its early years. They had a bottom-up product-led motion (teams discover Slack, adopt it, expand usage, then procurement deals with approval when it mattered). They also had a top-down sales motion for large enterprises (direct sales, compliance, procurement, annual contracts). Did one cannibalize the other?

No, because the market split cleanly:

• Bottom-up works for companies <2,000 people where engineering teams have freedom to adopt.
• Top-down works for enterprises >10,000 people where procurement controls tools.

The two motions reinforced each other. Bottom-up adoption created proof of value. When procurement finally engaged, the decision was easier because Slack was already embedded.

Contrast this with a company running sales and product-led with no segmentation. Salespeople chase every lead, even the small ones that are better served by PLG. The sales team eats the PLG CAC but cannot close small deals at the required price. PLG gets starved of resources because sales is chasing low-ACV leads that do not close. Motions cannibalize.

If running motion B prevents motion A from succeeding, you have motion confusion, not hybrid. Pick one and execute it.

Founder mistakes: how hybrid fails

There are three ways founders build hybrid, and two of them are mistakes.

Mistake 1: Hybrid by accident

The founder did not decide to build hybrid. It happened. The business grew. Different sales reps discovered different approaches. Some sold upmarket with long cycles. Some worked with resellers. Some customers came through free trials and upgraded. The founder looked at the data and said “we are hybrid” without ever asking “should we be?”

The result: no handoff rules, no clear ownership, no organizational structure to support it. Sales and product fight over leads. Partnership and sales both claim they can serve enterprise. Customer success gets confused about which motion owns onboarding. Operations cannot forecast because different motions have different sales cycles.

The fix for accidental hybrid is to retrofit structure: define which motion owns which segment, specify handoffs, and separate incentives.

Mistake 2: Hybrid as cover for motion indecision

The founder is unsure which motion will work, so they say “we will run both.” They invest in a sales team and a product-led funnel simultaneously. They run a community and a partner program with no segmentation between them. Six months later, neither motion has enough resources to succeed.

This is not hybrid. This is hedging bets on weak conviction. Hybrid requires belief that each motion serves a distinct segment. If you are hedging because you do not know which motion works, pick the one with the strongest early signal and commit.

Mistake 3: Undefined handoffs

This is the most common failure. The founder decides on hybrid, names which motion owns which segment, but never specifies when handoff happens or what the criteria are.

Real example: a B2B SaaS company running PLG and SLG. Their rule: “PLG owns accounts <$50k ACV. SLG owns >$50k.” Makes sense. But what is ACV at handoff? Is it potential ACV (what we think they could pay) or actual ACV (what they have paid to date)? Do you calculate ACV at first deal or based on annual projection?

Now a mid-market account with one $10k deal and potential for $80k/year appears. Does PLG own it because they are currently below $50k? Or does Sales own it because they will exceed $50k at renewal?

Without clarity, sales reps claim the account because the upside is big. The product-led team thinks they own it because the account signed up without sales. The account gets two different sales processes, two different contracts, and two different customer success managers. The experience is fractured.

The fix: define handoff criteria with specificity. “An account enters SLG when (1) they sign a contract for >$50k ACV or (2) they trigger SLG entry criteria (custom integrations, procurement involvement, contract negotiation). Once in SLG, they stay in SLG for the relationship, even if ACV dips below $50k at renewal.”

The four rules of hybrid operations

If hybrid is necessary (you have cleared the diagnostic), run it with these four rules. Each one prevents a specific type of failure.

Rule 1: Name which motion owns each segment

Do not say “we are hybrid.” Say “we run three motions: PLG owns accounts with <$50k ACV, self-serve discovery, and <2-week buying cycle. SLG owns accounts >$50k ACV or with procurement involvement. Partner owns geographic expansion in APAC.” Each motion is assigned to a segment. No overlap. No ambiguity.

Segments can be defined by:

• ACV (threshold for handoff between motions)
• Buying complexity (solo buyer vs. committee)
• Buyer type (engineer vs. procurement vs. executive)
• Geography (North America PLG, Europe SLG, APAC partner)
• Product use case (self-serve for use case A, sales-led for use case B)
• Company size (startups PLG, mid-market SLG, enterprise SLG+)

The taxonomy does not matter. Clarity does. Every account should fall into exactly one segment. No gray zones.

Rule 2: Define handoff criteria and SLAs

A handoff is a moment when one motion passes an account to another. The moment must be specified by behavior, not judgment.

Bad handoff rule: “When an account is ready, we hand to sales.”

Good handoff rule: “An account triggers SLG handoff when: (a) they have used the product >20 hours in 30 days (product engagement signal), OR (b) they have requested integrations or custom features (scope signal), OR (c) they have entered a procurement process (organizational signal). At handoff, SLG owns the relationship. Handoff SLA: Sales must contact within 2 business days.”

The criteria must be observable. If you can measure it in the CRM or product telemetry, you can automate it. Define the SLA too: how fast does the receiving motion respond? What is the onboarding process? Does the first motion introduce the second, or does it happen invisibly?

Bad SLA: “Sales will follow up when it makes sense.”

Good SLA: “Product-led will hand to Sales via a warm introduction email. Sales will schedule an intake call within 2 business days. Product-led will observe the first 30 days of the relationship, then exit.”

Rule 3: Separate compensation incentives

This rule is non-negotiable. If two motions can make money on the same deal, someone will game the system.

Example failure: PLG CSM and sales rep both have commission on the expansion deal. The CSM wants the account to expand organically (product-driven). The sales rep wants to claim the expansion (credit it to a sales motion they initiated). Both claim credit. One gets commission, one does not. Conflict. Deal moves slowly while they fight.

Fix: separate compensation by motion and segment.

• PLG comp: based on free-to-paid conversions, activation rates, and retention. Not tied to expansion deals.
• SLG comp: based on new logo, expansion deals, and ACV. Not tied to PLG metrics.
• Partner comp: based on partner-generated pipeline, not on account outcome (partner risk, not partner responsibility).

If an account moves from PLG to SLG, the PLG team gets credit for acquisition. The SLG team gets credit for expansion. Both get paid. No conflict. The incentives align with what each motion owns.

Rule 4: Separate teams and reporting structures

This rule prevents hybrid from becoming a matrix mess. Each motion needs a leader, a team, and a clear reporting line.

Bad structure: one VP Sales manages both PLG and SLG. They have separate teams but the same leader, the same budget, the same cadence. The VP has to optimize both at once. During crunch, resources shift. PLG loses its people to a large enterprise deal. PLG metrics suffer.

Good structure:

• PLG owns acquisition, product marketing, community. Reports to Chief Product Officer.
• SLG owns sales, enterprise customer success, major account management. Reports to Chief Revenue Officer.
• Partner owns channel, ecosystem, integration strategy. Reports to Chief Business Officer.

Each motion has its own leader. Each motion has its own budget. Each motion has its own cadence (PLG is bi-weekly product cycles; SLG is monthly forecast cycles; Partner is quarterly planning cycles). The motions synchronize at the top through the executive team, not through a matrix reporting structure.

Shared infrastructure exists: CRM, analytics, finance, legal, HR. But the motions themselves are separate. This prevents the constant resource trades that drain both.

The conflict matrix: what goes wrong and how to prevent it

Here are the conflicts that emerge in hybrid GTM, and how to prevent them.

How to organize a hybrid GTM

There are three valid structures, depending on your scale and motion maturity.

Structure 1: Separate P&L by motion (for >$10M ARR)

Each motion is a business unit with its own P&L, leader, and team. They share infrastructure (CRM, legal, finance) but operate independently.

CEO
├── Chief Product Officer
│   └── VP Product-Led GTM
│       ├── Product team (activation focus)
│       ├── Growth team (conversion focus)
│       └── Community manager
├── Chief Revenue Officer
│   └── VP Sales (enterprise)
│       ├── Sales team (enterprise AEs)
│       ├── Sales development (enterprise SDRs)
│       └── Customer success (enterprise)
└── Chief Business Officer
    └── VP Partnerships
        ├── Channel team
        ├── Integration team
        └── Partner success

Each leader has their own budget, hiring plan, and goals. They sync with each other quarterly. The CEO arbitrates conflicts. This scales well once each motion is big enough to justify its own team.

Structure 2: Shared sales org with specialized segments (for $1-10M ARR)

One sales leader manages multiple motions, but with clear segment ownership. This works when the company is too small for separate P&Ls but large enough to need dedicated teams per segment.

CEO
├── VP Sales & Growth
│   ├── Mid-market Sales Lead
│   │   ├── 3 mid-market AEs
│   │   └── 2 SDRs
│   ├── Enterprise Sales Lead
│   │   ├── 2 enterprise AEs
│   │   └── 1 solution engineer
│   ├── Growth/Expansion Lead
│   │   ├── Product-led onboarding
│   │   └── Expansion specialist
│   └── Partnership Lead
│       ├── 1 channel manager
│       └── 1 partner engineer
└── VP Product

This works if the VP Sales understands each motion’s economics and can operate by segment without constant trade-offs. It breaks down if the VP defaults to “sales-first” and starves the other motions.

Structure 3: Single team, explicit segmentation (for <$1M ARR)

The company is too small for multiple teams. One team, but they segment their work explicitly and follow the four rules: name segments, define handoffs, separate comp, and measure by motion.

CEO
├── VP Sales/Growth
│   ├── 1 AE (enterprise)
│   ├── 1 Growth marketer (PLG)
│   ├── 1 Partner manager
│   └── All three report to the same VP but operate by segment
└── VP Product

This requires discipline. Without it, they collapse into “we will just sell to anyone.” But if the VP can hold the lines—“we are not chasing that $10k deal, it belongs in PLG”—it works fine until the business grows.

Common mistakes in hybrid organization

Mistake: matrix reporting

Two leaders fight for the same person’s time. The person tries to serve both. Both leaders feel like they are under-resourced. In reality, the person is under-focused.

Fix: single reporting line per person. If two motions need someone, hire two people.

Mistake: “we will decide on handoff once we have enough data”

Handoffs are undefined. Teams make ad-hoc decisions. Account ownership is ambiguous. Leads get lost in the cracks.

Fix: define handoffs before you have the scale to make it obvious. Better to be wrong early and fix it than to let ambiguity become a habit.

Mistake: heroic translation between motions

One person (usually a COO or VP Sales) translates between PLG, SLG, and partners. When they leave, the organization breaks.

Fix: make the translation rules explicit. Write them down. Automate what you can. Put them in the CRM. Make them independent of any one person.

Mistake: one incentive structure for all motions

Everyone is paid on new logo or ACV. PLG CSMs, SLG AEs, partners, all the same. This incentivizes the wrong behavior. PLG CSMs should be incentivized to keep churn low and activation high, not to close new deals.

Fix: tiered compensation by motion and role. PLG comp is different from SLG comp is different from partner comp.

The teaser: from hybrid selection to hybrid execution

Naming which motion owns each segment is step one. Executing on that choice is step two. Once you have motions defined, the next question is: how do they move accounts through the funnel? What does the path look like from awareness to advocacy when you are running multiple motions in parallel?

That is the foundation of funnel design (C4), where the bowtie takes shape across hybrid architecture. Different motions, same customer journey, one definition of success.