A design partner is an early customer who helps you build the product. A channel partner is a third party who sells, implements, or recommends a product you have already built. Same word, two different businesses, at two different stages, under two different contracts. Confusing them is the most expensive mistake in early-stage partnerships, so this page answers both questions.
The short version. If you are pre-product-market-fit, or your first ten customers are not yet repeatable, you want design partners, and the next section is the one to read. If your direct motion already works and you are trying to reach a geography, vertical, or procurement layer you cannot economically cover, you want a channel program, and the rest of the page is how to build one that survives year one.
Signed partner agreements are not a revenue metric. That is the mistake sitting underneath most stalled channel programs, so it goes first. Forrester's channel forecast for the decade had the average program growing its partner count roughly tenfold in five years, with about 80% of those new partners nontransacting: referral agents, affiliates, advocates, alliances, partners who recommend but never sell (Forrester, What I See Coming For The Channel). That is the shape of a healthy modern ecosystem, not a broken one. It is also why a count of signatures answers none of the questions a board is actually asking.
When we are asked to audit a partner program, the agreement count is the last number we ask for. The first two are how many partners logged an opportunity in the last 90 days, and whether finance has paid every approved commission on schedule. Those two separate a live program from a folder of contracts faster than anything else on the list.
The pattern underneath the stalled ones is familiar. A founder reads about how HubSpot, Atlassian, or Snowflake built channel businesses worth hundreds of millions, then assumes the same motion will work at $5M ARR with one part-time partner manager and a Notion page. It almost never does.
I've spent the last ten years building RevOps systems for B2B SaaS teams, currently as Founding GTM Engineer at Peec AI. Channel partner programs are one of the most over-pitched and under-built parts of a modern GTM stack. When they work, they are incredible. The CAC is lower, the deals are larger, and the retention is better. When they fail, which is most of the time, they soak up a partner manager's salary, a slice of your engineering roadmap for a PRM, and a year and a half of leadership attention.
This is the guide to read before a board approves the program, not in the year after.
What a design partner program is, and what 30 days can actually produce
A design partner program recruits a small set of early customers to shape the product before it ships, in exchange for early access, influence over the roadmap, and preferential pricing. It is a product instrument that happens to produce some revenue. A channel program is a distribution instrument that produces no product insight at all. If someone has handed you a revenue target 30 days out and you are still finding the shape of the product, the design partner program is the one that can move inside that window.
The structure the people who run these converge on:
Cohort size: three to fifteen. Most founders should start with three to five closely matched companies inside one buyer persona, with enough variation in the workflow that cross-partner pattern matching tells you what is universal and what is one company's habit (Koji, Garuda).
One page, not a 30-page MSA. The working agreement names the scope (what you are building and, more usefully, what you are not), the cadence (a 30 to 60 minute call weekly or biweekly plus async feedback on prototypes inside a stated number of days), and the compensation.
Charge something. Free access lowers friction and buys you a partner who never shows up. A small, heavily discounted pilot fee is the cleanest demand test there is: a company that will not pay a fraction of list for early access to a solution does not have the problem badly enough to build a business on. Sierra ran its design partner program on the hard setting, asking partners to pay, commit real time, and co-build, and converted all of them into customers (First Round Review).
Roadmap influence, not veto. Partners vote on quarterly priorities. You keep the final call, and you say so in writing before the first call.
Write the exit ramp in. A specific date or trigger where design partner status converts to a paid contract, with the discount stated up front: usually 30 to 50% off list for the first 12 to 24 months, sometimes locked longer in exchange for references and case studies, occasionally equity warrants for genuine co-creators (SaaStr).
The 30-day revenue target, honestly
Thirty days is enough to sign design partners and collect pilot fees. It is not enough to book annual contracts from partners who have not yet seen the product work, and it is not enough to book a single dollar of channel revenue.
What a disciplined 30 days produces: three to five signed design partner agreements inside one persona, a pilot fee or usage credit invoiced against each one, a written conversion date and discount per partner, and a first round of feedback that changes the roadmap. That is a real number and it is defensible in a board update.
What it does not produce: channel-sourced revenue. Partner programs take roughly 6 to 12 months to produce meaningful revenue and 12 to 18 months is common, and the average partner takes 6 to 12 months to become fully productive without structured onboarding (New Breed, Magentrix). Anyone promising channel revenue inside a quarter is selling a different program from the one that works.
If the 30-day target is fixed, negotiate what counts rather than whether it is possible. Signed agreements with a collected fee and a stated conversion date are a defensible metric at this stage. Logos signed with no money and no date are the metric that kills programs, and the rest of this page is largely about why.
Design partners buy you a product. Channel partners buy you distribution. Neither buys you the other.
Running a design partner program to hit a revenue number produces a product you can sell. Running a channel program before the product is repeatable produces a roster of signed agreements and no revenue, which is the failure this page opens with.
Everything below is the channel side. If you are still at the design partner stage, the piece on moving from founder-led sales to the first AE hire is the next one on the path.
What a channel partner program actually is
A channel partner program is a system for getting third parties to sell, implement, or recommend your product to their customers. The third party gets revenue share, margin, or co-marketing. You get a sales motion you do not have to staff directly.
The three real types you will run into:
- Referral partners. They send you a name. You close the deal. They get 10 to 20% of year one ARR for one or two years.
- Reseller partners. They sign the contract with the end customer and resell your product. They get a margin, often 20 to 40%.
- Solution partners or SI partners. They implement, configure, and support your product for the customer. They get implementation fees plus sometimes a referral fee.
These three programs look similar on a one-pager. They are completely different businesses to run. A referral program is mostly marketing and a Stripe integration. A reseller program is a finance, legal, and tax problem. An SI partner program is essentially a second product team that supports humans instead of code.
Most companies launch all three at once. Then they wonder why nothing works.
A partner program is a sales motion, not a marketing campaign.
If you would not staff this as a real sales channel with quota, comp, and pipeline reviews, do not launch it. A page on your website with a contact form is not a partner program.
When you should not build a channel partner program
I will start here because most teams need to hear this first.
Do not build a partner program if any of the following is true:
You are below $3M ARR with a sub-30 person company. Your direct motion is not yet proven. Adding a second motion that is harder and slower to debug will just confuse your data. Fix direct first.
You do not have a clear ICP. Partners need a sharp pitch about who they should sell you to. If your team cannot answer this question in one sentence, partners will not either. They will pitch your product to everyone and close no one. Fix that first, with a data-driven ICP rather than a persona doc nobody opens.
You do not have written sales collateral. Battle cards, demo recordings, pricing one-pagers, security overviews, a simple ROI model. If your own AEs are still passing tribal knowledge, your partners will be guessing.
Your product is hard to demo. If it takes a senior CSM 90 minutes to show value, a partner rep doing 12 demos a week of 8 different vendors will not bother. They will sell whatever takes them 20 minutes to pitch.
You do not have a deals desk or pricing discipline. Partners will discount harder than you would. If you do not have a published price book and an approval workflow, you will end up with 60% net revenue while the partner pockets 40% of a deal you priced for 90% margin.
In my experience, fewer than half of the B2B SaaS companies that ask me about partner programs actually clear this bar. The honest answer for the other half is "fix the direct motion first."
When a partner program does make sense
The signal is not ARR. The signal is geography, vertical, or persona that you cannot economically reach with direct sales.
A few patterns that actually justify a channel motion:
Your direct AEs cover North America well, but you keep getting inbound from EMEA or APAC that you cannot close because of timezone, language, or compliance. A regional partner there can cover that gap in 60 days versus the year it would take you to hire and ramp a local AE.
You sell into a regulated vertical where buyers prefer to work with someone they already know. Local government, healthcare networks, mid-market manufacturing, regional banks. A SI who already has the relationship will close a deal faster than a cold AE.
Your product needs configuration that your CS team will not scale to deliver. If every new logo eats two weeks of engineering or success hours, an SI partner who can do that work is unblocking your roadmap.
You sell to a persona who buys at the bottom of a procurement layer that always wants a partner of record. Public sector is the canonical example. So is anything involving a GSA schedule or a master services agreement with a large IT services firm.
If none of those four patterns fit, your partner program is probably a vanity project.
Indirect and partner-transacted revenue rose from 21% to 31% of total B2B software revenue inside a single year on ICONIQ's data, with direct sales falling from 73% to 57% over the same period (Partner Insight on the ICONIQ numbers). Mature partner programs contribute around 28% of company revenue and correlate with roughly 2x revenue growth, and partner-involved deals run about 32% larger than direct-only deals (Forrester's state of B2B partner ecosystems research, Continu's 2026 partner enablement roundup).
The 38% number is not the ceiling, and this page used to say it was
An earlier version of this page put the long term channel ceiling at 38% of revenue for mature SaaS and hung it on Forrester. The figure I can actually source is 28%, which is what Forrester reports mature programs contribute on average, and the ecosystem-wide figure is 31% of B2B software revenue transacted through partners. Partner-sourced share also varies about 3x by industry, roughly 24% in SaaS against 58% in services-led businesses, so a single ceiling number is the wrong shape of answer anyway. If you are building the board case, use your own segment's number, not the highest one you can find.
How to structure the program
Once you have decided to actually build one, the structure decisions matter more than the marketing.
Pick one partner type and ignore the other two
For the first 12 to 18 months, run one program. Referral, reseller, or SI. Mixing them at the start is the single biggest reason early programs collapse. Different partner types have different motions, different paperwork, different tooling, and different quota structures.
If you are not sure which to pick, default to referral. It is the simplest legally, the fastest to revenue, and gives you the data you need to design tiers later.
Tier the program on contribution, not logos
Most partner programs tier on the wrong thing. They sort partners by company size, geography, or how shiny the logo is. Then they wonder why their gold tier partner with the famous name does no business.
Tier on what the partner produces. A simple version:
Bronze: signed agreement, completed onboarding. Gets access to the partner portal and 15% referral fee.
Silver: closed at least two deals or sourced $50K ARR in the trailing twelve months. Gets dedicated partner manager, MDF, and 20% referral fee.
Gold: closed at least six deals or sourced $250K ARR. Gets co-selling support, deal registration with protection, and 25% referral fee plus margin opportunities.
You can adjust the numbers for your ACV. The principle stands. Tier on outcomes, not on logo prestige.
Solve deal registration before the first contract is signed
Deal registration is the part of partner ops that breaks programs. It is the system that says "this partner brought this opportunity, so they get credit and protection if it closes." Without it, partners stop sourcing because they think the direct team will steal their deals. Direct AEs stop cooperating because they think partners are claiming credit they did not earn.
In HubSpot, deal registration looks like this: a custom object called Partner Deal Registration. Each registration is created from a form on the partner portal. It has fields for partner company, partner contact, end customer, deal value estimate, and a 90-day validity window. A workflow auto-creates a HubSpot deal record, associates the partner company, and routes notifications to both the partner manager and the AE in that territory.
The hard part is enforcement. We typically write the rules into the partner agreement itself. If a registered deal closes within the validity window, the partner gets paid. If the same deal comes inbound through marketing during that window, the partner still gets paid. If a different partner registers the same end customer for the same product in the same 90 days, the first registration wins.
Then you have to actually pay it out. The programs I have audited that died quietly usually died here: finance stopped processing partner payouts for a quarter or two, partners stopped working their pipeline, and nobody connected the two until the program was already dead. That is a pattern from engagements rather than a published benchmark, so weigh it as such, but it is the failure I have watched most often.
What goes in a SaaS channel partner agreement
The agreement is the program. Everything else is enablement on top of it, and every failure mode further down this page traces back to a term somebody left out. Ten things it has to name:
- Partner type and appointment. Reseller, referral, distributor, or agent, named explicitly. A reseller contracts with the end customer and takes a margin. A referral partner introduces and you contract and bill. These are different tax, revenue recognition, and liability positions, and one agreement should not try to cover both.
- Territory or vertical, and whether it is exclusive. Exclusivity granted casually in month one is the clause that blocks the territory you want to sell into directly in year two. Overlapping territories are the clause that starts fights between partners and your own AEs.
- Deal registration. The mechanics belong in the agreement, not only in the portal: what gets registered, the validity window, what happens when the same end customer is registered twice, and what happens when a registered deal arrives through marketing during the window.
- Pricing, discount floor, and margin. A published price book and the lowest price the partner may quote without approval. Without it you discover your net revenue after the partner has already committed the discount.
- Commission, trigger, and payment terms. The rate, what event triggers payment (booking, invoice, or cash collected), and the number of days after that event. Referral fees commonly run 5 to 20% of first-year value, sometimes for two years (Referral Rock, ContractsCounsel).
- Who owns the customer. The relationship, the contract, the renewal, and the data. This is the question you do not want to be resolving during a renewal negotiation (Sirion).
- Data protection roles. If customer personal data moves between you and the partner, GDPR and CCPA want a written data processing agreement naming controller and processor, subprocessor consent, breach notification timelines, and data subject rights (Terms.law).
- Brand and marketing use. What the partner may call themselves, which logos they may use, and what needs approval before it goes out.
- Performance targets and tier movement. The number that has to be produced to stay in a tier, and the process for moving down as well as up.
- Termination, transition, and survival. The triggers, the notice period, what happens to in-flight deals and to end customers the partner is servicing, and which obligations (confidentiality, non-solicit, data handling) survive the end of the agreement (Traverse Legal, GLS Startup Law).
The most common startup version of this is a template pulled off the internet, signed, and never read again until something goes wrong. The failure listed further down this page, where a company discovered it had granted territory exclusivity it needed back, is that story. Have a lawyer who has seen a SaaS partner agreement before read it, and have whoever owns pricing approvals and the deal desk read the discount floor specifically.
A design partner agreement is the opposite document: one page, scope and cadence and conversion date, no territory, no margin, no registration. If you find yourself drafting territory language for a design partner, you are building the wrong program for your stage.
The tooling stack you actually need
Partner program tooling has its own industry. PartnerStack, Impartner, ZINFI, Allbound, Crossbeam, Reveal. Each pitches itself as essential. For the first 18 months you do not need any of them.
Here is the minimum viable partner ops stack I would ship at Series A to Series C:
The total spend on this stack at the Series A stage is usually under $1500 a month. Compare that to the $40K to $80K a year a PRM vendor will quote you for the same outcomes plus features you will not use.
Once you cross 50 partners actively producing pipeline, the math changes. At that point, a real PRM with automated payouts, training tracking, and tiered portals is worth the spend. Before then, it is premature optimization that delays your time to revenue.
If you want a deeper look at how we wire up the underlying HubSpot workflows for deal registration, attribution, and partner notifications, we have written that up separately.
Partner onboarding that does not get forgotten
The other place programs die quietly is partner onboarding. Companies sign a partner, get them through legal, send a welcome email with three Loom links, and then never speak to them again. Three months later the partner has done nothing. The partner manager says the partner is not engaged. The partner says they had no idea what to do.
Both are right.
The structure that has worked for us looks a lot like the 30/60/90 plan we use for new AEs.
In the first 30 days, the partner gets a kickoff call, two product walkthroughs, a written sales playbook, and a co-built target account list of 20 to 50 accounts you both think are good fit. The partner manager runs weekly office hours. The output of the first 30 days is at least one registered deal, even if it is small.
In days 31 to 60, the partner gets co-pitch support on at least two live calls. You let your AE run the second half of the demo at first. By the end of the second deal, the partner runs the demo and your AE supports. This is the slowest and most expensive part of partner onboarding. It is also the part that nobody does, which is why partner programs do not work.
In days 61 to 90, the partner runs deals end to end with your team as a backstop for technical questions. The partner manager moves from weekly to biweekly. By day 90 the partner either has live opportunities and a clear path to producing, or they do not. If they do not, you have learned something cheap, and you can stop investing in that partner without burning the relationship.
Most partner programs fail at month four, not month one.
The honeymoon period of any new partnership covers the first 90 days. After that, both sides forget. Whoever owns partner ops on your team has to design for sustained engagement, not just the launch.
How to comp the partner manager
I see this wrong almost every time. Companies hire a partner manager and put them on the same comp plan as an AE. Then they wonder why the partner manager spends all their time chasing their own deals instead of building the channel.
A partner manager's comp should be 60 to 70% partner-sourced or partner-influenced revenue, 20 to 30% activation metrics (number of partners producing pipeline above a threshold), and 10 to 20% qualitative (program development, content, training assets shipped).
The activation component is the one most companies skip. It is the only thing that protects you against the "two partners doing 90% of the volume" trap, which is where almost every early-stage partner program ends up. You want a partner manager whose paycheck depends on diversifying revenue across the partner base, not on babysitting the one happy SI who came in through their personal network.
For comp math basics on building this kind of role-specific plan, we have a longer piece on sales compensation plans that walks through the structure.
The numbers you should actually track
Most partner program dashboards are noise. Logos signed, MQLs, partner-attended webinar registrations. None of this tells you whether the program is working.
The four metrics that actually matter:
Partner-sourced ARR. Revenue from deals the partner brought to you that you would not have found otherwise. Track quarterly. Should grow quarter over quarter after month nine.
Active partner count. Number of partners who have submitted at least one deal registration in the trailing 90 days. If this number is flat or declining, your program is dying regardless of what total partner count looks like.
Partner-sourced ACV vs direct ACV. If partner deals are smaller than direct deals, you are selling the wrong kind of partner program for your ICP. Partner deals should generally be the same size or larger.
Partner-sourced win rate vs direct win rate. Partner-sourced deals should close at a higher rate than direct, because the partner has prequalified them. If they close at a lower rate, you have a deal quality problem and need to retrain your partners.
If you want to push further into partner influence rather than just partner sourcing, account-based marketing work overlaps heavily here, and the same attribution rigor applies.
If partner-sourced ARR is not at least 10% of new ARR by month 18, the program is not working. Either kill it or rebuild the structure from scratch. That threshold is my own working rule from audits rather than a published benchmark, and it sits well below the 24% partner-sourced share reported for SaaS generally, which is the point: it is a floor for survival, not a target.
The most common failure modes
A short list, drawn from programs we have audited or rebuilt:
The program was launched without sales leadership buy-in. AEs viewed partners as competition. Deals were quietly de-registered. The partner manager became an internal advocate for partners against the rest of the company, which is not a winnable job.
The partner agreement was written by a lawyer who had never seen a SaaS partner agreement. Three months later the company discovered they had given partners exclusivity in territories the company actually wanted to sell into directly.
There was no deal protection. Partners stopped sourcing because three of their early deals were closed by the direct team without payout. By the time the company fixed the policy, the partners had moved on.
The MDF was a slush fund. Partners ran webinars nobody attended, generated zero pipeline, and the partner manager could not prove the spend was working. Marketing finance pulled the budget. The program lost its only growth lever.
The wrong KPIs were tracked. Leadership cared about logos signed because the partner manager could control that number. Pipeline did not show up. The board lost faith. The program was killed two quarters too early.
Most of these have the same root cause. The company treated the partner program as a marketing initiative or a side project rather than as a sales channel that requires the same rigor, comp design, ops support, and executive attention as the direct team.
When to invest in a real PRM and partner team
The signal that you are ready to spend serious money on partner tooling and team is simple. Partner-sourced ARR has been at least 15% of new ARR for two consecutive quarters, and you have at least 10 active partners producing pipeline. At that point a real PRM, a head of partnerships, and a partner enablement person all start to pay back inside 12 months.
Before that, every dollar you spend on partner tooling is replacing dollars you could spend on direct sales, where you actually know the unit economics. The math almost always favors direct until the partner channel proves itself.
This is the same logic we apply to any new GTM motion. Prove the unit economics in a stripped-down version. Then invest in infrastructure once the motion works. We see far too many programs build the infrastructure first and then try to backfill the motion.
Trying to figure out if a partner program is right for your stage?
We have audited and rebuilt partner programs at companies between Series Seed and Series C. Book a 30-minute call and we will tell you honestly whether this is the right time to invest, and what to fix first if it is not.
Book an auditFAQ
What is the difference between a design partner and a channel partner?
A design partner is an early customer who co-builds the product with you, in exchange for early access, roadmap influence, and preferential pricing. A channel partner is a third party who sells, implements, or recommends a product you have already built, in exchange for a referral fee or margin. Design partners help you find the product. Channel partners help you distribute it. The agreements look nothing alike: a design partner agreement is one page covering scope, cadence, and the conversion date, while a channel agreement covers territory, margin, deal registration, data protection, and termination.
Can a partner program hit a revenue target 30 days out?
A design partner program can, if you count the right thing. Thirty days is enough to sign three to five design partners inside one persona and invoice a discounted pilot fee against each, and charging even a small fee is the cleanest test of whether the problem is real. A channel program cannot. Published ramp data puts meaningful partner revenue at 6 to 12 months, with 12 to 18 months common, and individual partners take 6 to 12 months to become productive without structured onboarding. If a 30-day number is fixed, agree in advance that signed agreements with a collected fee and a stated conversion date are what counts.
What should a SaaS channel partner agreement include?
Partner type and appointment, territory or vertical and whether it is exclusive, deal registration mechanics with a validity window, the price book and discount floor, the commission rate and what event triggers payment, who owns the customer relationship and data, a data processing agreement naming controller and processor roles, brand and marketing use, performance targets tied to tier movement, and termination triggers with a transition plan and the clauses that survive. The two most expensive omissions in practice are casual exclusivity and unclear customer ownership.
How much revenue should a partner program contribute?
For mature B2B SaaS companies, the long term target is 25 to 40% of new ARR from partners. In year one, anything above 5% is a real signal. In year two, you want to be at 15% or higher. If you are below 10% by the end of year two, the program is probably not going to work in its current shape.
How long does it take to see real revenue from a partner program?
Published ramp data puts meaningful revenue at 6 to 12 months, and 12 to 18 months is common. The first 90 days is partner recruitment and legal paperwork. The next 90 days is onboarding and first deal cycles. After that you start seeing closed revenue from the early cohort. Anyone promising you partner revenue in quarter one is selling you a different program than the one that actually works. Time to first deal is the signal worth watching inside that window: partners who close early stay active, and partners still at zero after six months mostly churn.
What is the difference between partner-sourced and partner-influenced revenue?
Partner-sourced means the deal would not exist without the partner. They identified the account, made the introduction, and the deal got registered. Partner-influenced means the partner was involved at some stage of an existing opportunity, often providing implementation services or a recommendation. Most companies pay full referral fees on sourced and a reduced rate (or nothing) on influenced. Decide your policy before you sign your first partner agreement.
Do we need a partner portal on day one?
No. A shared Notion or Google Drive folder with collateral, demo videos, and a Typeform for deal registration will get you through the first 10 partners. Build the portal when you cross 15 to 20 active partners or when your top tier partners explicitly ask for it. Until then, the portal is procrastination.
Should we sign every partner that asks?
No. The same way you qualify prospects, you qualify partners. The minimum bar is: do they have direct access to a buyer in your ICP, do they have at least one rep who can run a discovery call without your help, and do they have a real reason to push your product specifically. If they fail any of these three, the partnership will not produce revenue regardless of how shiny the logo is. The most expensive partners are the ones who sign agreements and then do nothing, because they still cost you onboarding time and they take up a slot in your tier system.
A note on the numbers. The benchmarks on this page were taken from search result extracts of the reports linked above rather than from a direct read of each publisher's page, so treat them as reported rather than verified first hand. Where sources disagree, as they do on partner-sourced revenue share by industry, the page says so. Confirm anything headed for a board deck at the source.