This page may contain partner links that earn us compensation.
A partner page explains who your program is for, what partners receive, and how to apply. This guide compares 15 examples and the lessons B2B SaaS teams can adapt for affiliate, referral, and channel programs.
These examples cover different business models. Use the comparison to find a relevant pattern, rather than copying a program whose audience or delivery requirements differ from yours.
How this guide was reviewed: We compared the linked public program pages for audience clarity, program options, benefits, and application paths on October 4, 2026. The lessons below are editorial recommendations, not measured conversion results. Screenshots are retained from earlier versions and may differ from the current pages; use each source link for current program details.
1. PartnerStack: separate routes for different partner jobs
What the page communicates: The page explains four ways to partner: promoting links, referring clients, delivering services, and building integrations. Each path has its own next step.
What to adapt: Use short audience descriptions so a publisher and an implementation consultant can find the right offer without guessing.
Watch out for: Only show program tracks your team can actually support. More choices are not automatically better.
What the page communicates: Crossbeam separates API integration partners from service firms that help customers implement and use the platform. It also links to its partner marketplace.
What to adapt: Describe what partners will do, then explain the customer problem they help solve.
Watch out for: An ecosystem directory serves buyers as well as applicants. Keep those journeys distinct.
What the page communicates: Kiflo places its affiliate, referral, and solution options together, with requirements and rewards for each. It also describes a partner directory listing.
What to adapt: Help applicants assess fit before they fill in a form. Make certification or delivery requirements visible.
Watch out for: Specific reward terms need an owner and a review process so they stay accurate.
What the page communicates: Gorgias describes an agency offer through service opportunities, training, co-marketing, revenue share, lead sharing, and dedicated support. A separate link lets visitors submit a lead.
What to adapt: Explain the support behind the commission: onboarding, enablement, and access to your team.
Watch out for: Promise only the support your operating model can consistently deliver.
What the page communicates: The linked Commerce partner portal provides a login for existing partners and an application route for newcomers. Agency and technology options have separate information links.
What to adapt: Give current partners an obvious login, while keeping recruitment information visible to new visitors.
Watch out for: A portal-first page may be less suitable as the main destination for a cold recruitment campaign.
What the page communicates: HubSpot presents five program routes with short audience descriptions. It also separates finding a service provider from becoming a partner.
What to adapt: Use plain-language eligibility descriptions. A content publisher should not need to read a solutions-partner pitch to find the affiliate route.
Watch out for: Multiple programs need separate detail pages and clear ownership; one generic form can create routing problems.
What the page communicates: Mixpanel groups its options into solutions and resellers, integrations, referrals, and startup partners. Signup and partner login are distinct actions.
What to adapt: Make each pathway understandable before asking visitors to enter a partner platform.
Watch out for: Broad categories still need qualification criteria and clear expectations on the next page.
What the page communicates: Klaviyo distinguishes becoming a partner, finding a partner, and accessing the partner portal. Its page also provides navigation to program paths, resources, and success stories.
What to adapt: Separate the needs of applicants, customers looking for help, and existing partners.
Watch out for: Long ecosystem pages benefit from section navigation, but a focused affiliate landing page may need fewer sections.
What the page communicates: Chili Piper describes three tracks and their responsibilities, then offers an application form that asks for partner type. The form explains the expected follow-up.
What to adapt: Tell applicants what they will contribute and what happens after submitting their details.
Watch out for: Do not copy another company’s response-time promise unless your team can meet it.
What the page communicates: Smith.ai provides distinct partnership actions, including referral affiliate, technology, and wholesale options. It also offers a contact route for visitors who are unsure.
What to adapt: Give uncertain applicants a helpful next step instead of forcing a choice they do not understand.
Watch out for: A general inquiry route still needs internal qualification and follow-up ownership.
What the page communicates: ShipBob describes co-marketing, partner management support, and revenue opportunities alongside a partner application link and a named customer testimonial.
What to adapt: Explain how the relationship will work after approval, including the support available to partners.
Watch out for: Benefits from a logistics ecosystem will not map directly to every SaaS affiliate program. Adapt them to your own offer.
What the page communicates: impact.com separates several partner audiences and explains different ways to refer or collaborate. The page includes program actions and attributed testimonials.
What to adapt: Use a route that matches how the visitor will introduce customers, deliver services, or build technology.
Watch out for: Headline earning claims need current terms and substantiation. Avoid copying a maximum payout as a typical outcome.
What the page communicates: The LiveChat partner site separates sharing referral links, delivering customer solutions, and building apps. It includes both registration and partner login.
What to adapt: Explain whether a partner promotes your product, implements it, or builds on it. Those are different commitments.
Watch out for: A shared registration flow should preserve the applicant’s chosen program type.
What the page communicates: Sprout Social presents referral, agency, and reseller options with different benefits and application or contact actions. Its reseller description identifies a public-sector audience.
What to adapt: State who the program is for as clearly as what the program offers.
Watch out for: Avoid describing every relationship as an affiliate program; service and reseller obligations differ.
A useful partner page helps the right people decide whether to apply. Review these elements before adding more visual decoration.
A clear audience. Name the publishers, consultants, agencies, or technology companies you want to work with. Explain any eligibility requirements.
A specific offer. Describe the customer problem, the partner’s role, and the value they receive. Publish current commission and payment terms where appropriate.
The right program routes. Distinguish affiliate promotion from referral partnerships, service delivery, reselling, and integrations.
Credible evidence. Use approved partner logos, attributed testimonials, and case studies that describe what actually happened. Do not imply that a logo proves revenue performance.
Operational support. Explain onboarding, training, sales materials, reporting, and who partners can contact.
One clear next step. Label the action accurately: apply, register, or contact the team. Collect enough information to assess fit without asking for details you will not use.
A follow-up process. Assign an owner to applications and explain what happens next. If a partner management platform handles registration, test the handoff.
How is an affiliate page different from a general partner page?
An affiliate page usually focuses on people who promote a product to an audience and receive compensation for qualifying activity. It should explain audience fit, tracking, approved promotion methods, commission terms, and payment conditions.
A general partner page may also serve agencies, resellers, and integration builders. Those relationships can involve implementation, support, certification, or technical requirements. Give each audience a clear route when the commitments differ.
How should you measure a partner page?
Start with qualified applications and partner activation, not raw form submissions alone. Track the share of visitors who apply, the share of applicants who fit your criteria, and how many approved partners go on to generate qualifying activity.
Review applications by source and partner type. If signups increase while qualification falls, clarify the audience and offer before increasing promotion. Evaluate revenue using your attribution rules and sales cycle; a page redesign alone does not prove incremental revenue.
Choose a pattern, then test it
Start with the example closest to your partner model. Borrow its clearest audience explanation, program route, or application step, then adapt it to your actual offer. A useful page sets expectations that your team can deliver after approval.
Nick Cotter is the founder and principal consultant at Growann. He brings 10+ years of experience in B2B SaaS marketing and helps teams build and improve affiliate and partner programs.