// FRAMEWORKS · INTERACTIVE

The four partner archetypes. Operated distinctly.

Most B2B SaaS partner programmes fail because they conflate the four archetypes. Each has different economics, different enablement, a different deal cycle, and a different reporting line. Conflating them produces noise. Operating them distinctly produces revenue.

Click any archetype to see how it actually runs. Generalised from a working partner playbook including time as Chief Growth Officer at Sapio Sciences. The frame is part of Ortent's wider guide to partner-led growth.

Click any archetype to see economics, enablement, deal cycle, owner, and the KPI that proves it is working
Highlight
// 01 · Reseller

Reselling partners

Customer-access leverage.

Sell the product to their customers on commission or margin. Typically global system integrators, regional resellers, and specialised industry firms. Best when the partner has buying-centre access the platform cannot easily reach directly.

Margin or commission Channel sales Partner-sourced ARR Buyer access
Owns Buying-centre access. The partner is already inside accounts the platform cannot reach directly, often through procurement, framework agreements, or industry-specific buying patterns.
Economics Margin or commission on closed-won ARR. Rates reward depth (deeper integration, multi-year deals, partner-led CS) over breadth.
Enablement Sales playbooks, demo certification, deal-registration discipline, comp-plan alignment between direct and partner.
Deal cycle Same shape as direct sales. Wins where the partner has the relationship and the platform has the product fit.
Owner inside SaaS Channel sales leader. Reports through CRO or CGO.
Headline KPI Partner-sourced ARR. Closed-won where the partner is the primary source. The number PE will look at in diligence.
Common pitfall Direct sales and partners chasing the same accounts with no deal-registration teeth. Direct wins because they are closer. The partner disengages because the economics feel rigged.
// Worked pattern

Regional reseller has a 15-year relationship with a buying centre that has rejected three direct approaches. Reseller introduces the platform under their own brand and existing framework agreement. Platform closes a £180K deal in 9 weeks that direct sales had not closed in 24 months. Channel sales own the relationship. Reseller earns 20% margin. Both sides clear on whose deal it is.

// 02 · Integrator

System integrator partners

Implementation leverage.

Implement and customise the platform, often owning the customer success and delivery layer. Best when implementation complexity is the gating factor for adoption.

Services + influence fee Partner success / delivery Time-to-value, attach Implementation-gated
Owns Implementation and customer success. The partner is the delivery layer. Configures, customises, runs the rollout, owns adoption.
Economics Services revenue billed by the partner, plus an influence fee or co-sell margin from the platform. Two revenue streams, two sides of the table to manage.
Enablement Technical training and certification. Reference implementation methodology. Joint solution architects. Customer-success playbooks the partner can actually run.
Deal cycle Slower than reselling. Gated by the partner's ability to scope, propose, and deliver the implementation. Watch for partners that pitch the deal but cannot resource the delivery.
Owner inside SaaS Partner success or delivery leader. Often reports through customer success or COO.
Headline KPI Time-to-value on partner-led implementations. Attach rate of partner-delivered services to net-new ARR.
Common pitfall The partner sees an SI opportunity, not a product opportunity. They sandbag the customer's roadmap to extend their own services. Joint customer-success governance is the only fix.
// Worked pattern

Mid-tier integrator with 40 certified consultants and three live customers on the platform. Implementation methodology is reference quality. Platform reduces direct-services headcount by routing 60% of net-new implementations through the partner. Time-to-value drops from 22 weeks to 14. Attach rate on services hits 70%. Partner success owner runs a monthly delivery review with both heads of customer success.

// 03 · ISV

ISVs

Capability-stack leverage.

Layer their software on top of the platform, producing combined offerings that neither party could deliver alone. Best when the platform's value compounds with adjacent capability, particularly AI.

Joint revenue share Product & alliances Joint-customer ARR Adjacent compounds
Owns Adjacent capability that compounds the platform. Increasingly an AI layer. Their software extends the platform's value into a use case the platform alone cannot serve.
Economics Joint revenue share on combined deals. Pricing of the integrated offer agreed at MSA level. Renewal economics designed at the same time as new-business.
Enablement API depth. Joint roadmap with quarterly review. Joint solution engineering. Co-developed reference architectures the joint sales motion can demo.
Deal cycle Faster on attach to existing platform deals. Slower on net-new co-sell, because both companies' sales teams need to be lit up in parallel.
Owner inside SaaS Product and alliances. Cross-functional ownership between CPO and CGO, because the relationship is part technical and part commercial.
Headline KPI Joint-customer ARR. Attach rate of the ISV product on net-new platform deals.
Common pitfall Slide-deck partnership. MOU exists, press release exists, joint roadmap exists. Pipeline does not. Without committed BDR resource on both sides, the relationship dies after the launch quarter.
// Worked pattern

Mid-stage AI ISV with a vertical model that complements the platform's workflow. Joint MSA agreed in 11 weeks. Joint roadmap reviewed quarterly. Each side commits one named BDR. Within two quarters the attach rate on net-new platform deals reaches 35% and joint deals close 22% faster than platform-only. The MSA is the structural commitment that makes the rest possible.

// 04 · Instrument or platform vendor

Instrument or platform vendors

Workflow-bundle leverage.

Bundle the SaaS with hardware, instrument, or platform deals. Best in life sciences and healthtech, where the platform sits inside a wider workflow the customer is already buying.

Bundle pricing or attach Strategic alliances Bundled-deal ACV Workflow already has hardware
Owns The hardware or instrument footprint. The customer is buying the instrument or platform anyway. The SaaS rides the bundle into the workflow already being procured.
Economics Bundle pricing negotiated per deal, or a standing attach fee inside the vendor's price book. Long renewal cycle tied to the instrument lifecycle.
Enablement Workflow fit study. Joint reference design. Co-developed onboarding so the SaaS is alive on the instrument from day one. Field-service team training.
Deal cycle Tied to the instrument or platform purchase cycle. Often quarterly or annual buying windows. Strategic alliance manager works the vendor's planning cadence, not the platform's quarterly rhythm.
Owner inside SaaS Strategic alliances leader. Reports through CGO or CEO depending on alliance criticality.
Headline KPI Bundled-deal ACV. Attach rate of the SaaS to net-new instrument or platform sales by the vendor.
Common pitfall Treating the vendor like a reseller. The economics, deal cycle, and procurement reality are different. A reseller comp model applied to a vendor relationship produces a strategic alliance that under-performs and a vendor that disengages.
// Worked pattern

Established lab instrument vendor includes the SaaS in the standard bundle for its next-generation instrument. Joint reference design developed over four months. Field-service team trained alongside instrument engineers. The vendor sells the bundle through its existing global channel. Platform gains 60+ new logos in 12 months at zero direct-sales CAC, but with a longer onboarding tail managed jointly.

// The central rule
"In B2B SaaS the right answer is rarely all four at once. It is usually the two archetypes most likely to compound for the specific business, built properly, before the other two are added."

Picking two and operating them distinctly beats announcing four and operating none. The selection criteria are simple. Where is the gating risk to growth (buyer access, implementation complexity, adjacent capability gap, or workflow ownership)? Which two of the four directly relieve that risk? Build those two. Add the others when the first two are working.

Side by side

Reseller Integrator ISV Instrument
OwnsBuying-centre accessImplementation & CSAdjacent capability (often AI)Hardware / instrument footprint
EconomicsMargin or commissionServices revenue + influence feeJoint revenue shareBundle pricing or attach
EnablementSales playbooks, demo certsTechnical training, methodologyAPI depth, joint roadmapWorkflow fit, joint reference design
Deal cycleSame as directSlower, implementation-gatedFaster on attach, slower on co-sellTied to instrument purchase cycle
Best whenYou can't reach the buyer aloneImplementation is the gating riskAdjacent value compounds yoursWorkflow already includes hardware
Owner inside SaaSChannel salesPartner success / deliveryProduct & alliancesStrategic alliances
Headline KPIPartner-sourced ARRTime-to-value, attach rateJoint-customer ARR, attachBundled-deal ACV, attach

From transactional to symbiotic.

The structural shift in 2026 partner programmes is from transactional to symbiotic relationships, because partner AI capability is maturing fast. In a transactional model the partner refers, the platform pays a commission, and the relationship is sustained one deal at a time. In a symbiotic, co-growth model the partner and the platform grow each other's capability and footprint. As the partner's AI matures, the platform becomes a higher-value attach point. As the platform's customer base grows, the partner gains a larger surface to deploy against. Both sides are rewarded for the long arc, not the individual deal.

Three structural commitments make the co-growth model real.

  1. Joint roadmap. Both sides commit a portion of their roadmap to the integration and review it on a defined cadence, usually quarterly.
  2. Co-investment in pipeline. The partner contributes a named BDR or solution architect. The platform contributes leads or marketing budget. Both sides have skin in the joint motion.
  3. Long-arc economics. Margin, commission, and tier qualification reward depth not breadth. A partner who closes ten deals over two years earns more than a partner who closes one a quarter for two years.

This is the model PE operating partners should test for in any B2B SaaS asset that claims to have an AI partner strategy. The transactional version is the same channel programme repackaged with new logos. The co-growth version is the lever that actually compounds.

// Take it with you

Whitepaper and Claude prompt

Two artefacts to run this with your board or your CRO. The whitepaper explains the four archetypes and the twelve-marker audit. The Claude prompt runs the diagnostic conversationally, marker by marker, and returns a scored assessment plus a rebuild recommendation at the end.

// Whitepaper · PDF

Four Partner Programmes, One Slide

The framework in twenty-five pages. Twelve markers across three components, four archetypes, three cross-industry worked examples, and the before-and-after of a rebuild from twelve partners to two.

Download PDF→
// Claude prompt · Interactive

The Partner Architecture Diagnostic, run live

Paste the prompt into a Claude project. Twelve markers, one at a time, A or B. Hedges pushed back. Component scores and rebuild recommendation at the end. Eight minutes to run.

Copy the prompt→

FAQs

What is the Partner Architecture Visualiser?

An interactive visualiser of the four partner archetypes that actually move ARR in B2B SaaS: referral, co-sell, ISV and alliance. Each archetype card shows the economics, enablement, deal cycle, owner inside the SaaS company and the KPI it moves. Free, browser-based, no email captured.

Who is the visualiser for?

CROs, CGOs and PE operating partners scoping a partner programme or auditing one that is not producing. Also useful for boards trying to understand why a programme with four archetypes lumped into "the channel" is underperforming. The visualiser makes it hard to keep confusing them.

What are the four partner archetypes?

Referral partners introduce and take a fee. Co-sell partners run joint pipeline and joint account planning. ISVs integrate your product into theirs. Alliance partners (system integrators and instrument or platform vendors) sell your product as part of a larger solution. Each archetype has different economics, enablement, deal cycle, owner and KPI.

How does this differ from a channel programme?

A channel programme is one archetype, usually reselling. Partner-led growth spans all four archetypes. Running all four as if they were one channel programme (same enablement, same deal-reg, same margin, same owner) is the single most common reason partner revenue underperforms.

Do I need to give an email address?

No. The visualiser is free and browser-based. There is no signup, no lead form and no gate. The whitepaper and Claude prompt that accompany the tool are also free and require no email.

Is there a scoring version of the tool?

Yes. The Partner Architecture Diagnostic prompt scores a programme against twelve markers in three components (Ownership and Reporting, Enablement and Compensation, Board-Facing Signals) and returns a level verdict plus the single component to fix next. Same voice as the whitepaper.

What do I do with the result?

Two things. Pick the one or two archetypes that fit the business, not all four. Then match owner, enablement, deal-reg, margin and KPI to the archetype, not to a generic "channel" template. Running the scored diagnostic tells you which of the twelve markers is the actual gap.

// GET IN TOUCH

Clarity when it counts.

For a board, advisory or fractional engagement, or a working call on the next stage, email directly. Thirty minutes is usually enough to test fit.

Book a 30-minute intro call