SaaS Partnership Agreement:
Essential Clauses & Template

A SaaS partnership agreement is a contract between two or more software companies that defines how they'll collaborate to deliver value to customers. Unlike a customer agreement (where one party buys access to software) or a reseller agreement (where one party simply redistributes another's product), a partnership is bidirectional and collaborative.

Common SaaS Partnership Types

1. Technology Integration Partnership

Both companies' platforms integrate via API to provide a combined solution. Example: A CRM integrates with an email marketing platform. Revenue typically flows from each company's existing customers; no direct payment between partners.

2. Revenue Share Partnership

One partner refers customers to the other and receives a percentage of revenue. Example: A consulting firm refers clients to a SaaS product and earns 20% of subscription fees for the first year.

3. White-Label Partnership

One company licenses its SaaS platform to another, which rebrands it as their own product. Example: A payment processor licenses fraud detection software and sells it under their own brand.

4. Reseller Partnership

One company grants another permission to resell its SaaS product, typically with a commission or markup. This is distinct from white-label because the original brand remains visible.

5. Co-Marketing Partnership

Both companies promote each other's products through joint webinars, case studies, or content. No direct revenue share; value comes from lead generation and brand association.

6. API Partnership

One company provides API access to its platform, and the other builds features on top of it. Payment structure varies: per-call fees, revenue share, or flat licensing fee.

Why You Can't Use a Generic Partnership Agreement

Most generic partnership templates are written for brick-and-mortar businesses or professional services firms. They don't address:

• API ownership and versioning: Who controls API updates? What notice is required before deprecating an endpoint?
• Data flow and privacy compliance: When customer data passes between platforms, who's the controller vs. processor under GDPR/CCPA?
• Uptime dependencies: If Partner A's downtime causes Partner B to breach its SLA with end customers, who bears the liability?
• IP in the integration layer: Custom API connectors, middleware, and joint features require explicit ownership rules.

Clause 1: Partnership Scope and Purpose

This section defines what you're actually doing together. It should specify:

• The type of partnership (integration, revenue share, white-label, etc.)
• The specific products or services covered by the agreement
• Geographic territory (worldwide, US-only, specific regions)
• Exclusivity (is this an exclusive partnership, or can both parties have similar deals with competitors?)

Clause 2: Revenue Share and Payment Terms

If money changes hands between partners, specify:

• Percentage split or flat fee structure
• How revenue is measured (gross vs. net, before or after refunds/chargebacks)
• Payment frequency (monthly, quarterly)
• Currency and payment method
• Audit rights (can one partner inspect the other's books to verify revenue calculations?)

Clause 3: Intellectual Property Ownership

This is where most SaaS partnerships fall apart. You need explicit rules for:

• Pre-existing IP: Each party retains ownership of IP they brought into the partnership.
• Independently developed IP: IP created by one party during the partnership term remains that party's property.
• Jointly developed IP: For features, integrations, or tools created collaboratively, specify either (a) joint ownership with cross-licenses, or (b) assignment to one party with a perpetual license to the other.
• Derivative works: If one party modifies the other's IP (e.g., customizing a white-label product), who owns the modifications?

Clause 4: Confidentiality and Data Protection

SaaS partnerships involve sharing sensitive information: API keys, infrastructure details, customer lists, pricing models. You need:

• Definition of what constitutes "Confidential Information"
• Obligations to protect confidential information (industry-standard security measures)
• Permitted disclosures (to employees, contractors, subprocessors on a need-to-know basis)
• Survival period (2-5 years post-termination for general business info; perpetual for trade secrets)

Data Processing Addendum (DPA): If either party processes personal data on behalf of the other, or if customer data flows between platforms, you need a GDPR/CCPA-compliant DPA that specifies:

• Roles (controller vs. processor)
• Permitted data uses
• Subprocessor consent and notification requirements
• Breach notification timelines (typically 72 hours under GDPR)
• Data subject rights (access, deletion, portability)

Clause 5: Service Level Agreement (SLA)

If one party's uptime affects the other's ability to serve customers, you need an SLA that covers:

• Uptime commitment: 99.9% is standard for SaaS (43 minutes of downtime per month). 99.99% is enterprise-grade (4.3 minutes per month).
• Measurement methodology: How is uptime calculated? Does scheduled maintenance count against the SLA?
• Remedies: Service credits (not liquidated damages) are the standard remedy for SLA breaches. Example: 10% credit for 99.5-99.9% uptime, 25% credit for 95-99.5%, 50% credit below 95%.
• Exclusions: Downtime caused by the other party's misuse, third-party failures (AWS, Google Cloud), or force majeure events doesn't count against the SLA.

Clause 6: Term, Renewal, and Termination

Specify the initial term (1-3 years is typical), renewal mechanism, and termination rights:

• Auto-renewal: Recommended for partnerships where customers depend on the integration. Example: "Initial term of 2 years, then automatic 1-year renewals unless either party gives 90 days' notice of non-renewal."
• Termination for convenience: 60-90 days' notice is standard. Shorter notice (30 days) works for low-integration partnerships like co-marketing deals.
• Termination for breach: Material breach with 30-day cure period. Define what constitutes a "material breach" (e.g., SLA failures, payment defaults, IP infringement).
• Termination for insolvency: Either party can terminate immediately if the other files for bankruptcy or becomes insolvent.

Post-termination obligations:

• Wind-down period for existing customers (30-90 days to migrate customers off the platform)
• Return or destruction of confidential information
• Survival of certain provisions (confidentiality, IP ownership, indemnification, limitation of liability)

Clause 7: Non-Compete and Non-Solicitation

Whether to include a non-compete depends on the partnership type:

• White-label and exclusive distribution deals: Non-compete is standard and typically enforceable. Example: "During the term and for 12 months after termination, Partner shall not offer a competing fraud detection product in the same geographic territory."
• Technology integrations and co-marketing: Non-competes are rare and often unenforceable (unreasonable restraint of trade). Focus on non-solicitation instead.

Non-solicitation: Prevents each party from poaching the other's employees or customers. Typical duration: 12-24 months post-termination. Scope should be narrow—don't prohibit hiring any employee; prohibit soliciting employees who worked on the partnership.

Clause 8: Dispute Resolution and Governing Law

Specify how disputes will be resolved and which state's laws apply:

• Governing law: Choose the state where the economically dominant partner is headquartered, or Delaware for predictable business-friendly contract law. Avoid states with no connection to either party.
• Arbitration vs. litigation: I generally recommend arbitration (AAA or JAMS) for SaaS partnerships because it's faster, private, and both parties are sophisticated commercial entities. Exception: If you anticipate needing injunctive relief (e.g., to stop IP theft), litigation may be better because arbitrators can't grant preliminary injunctions in most jurisdictions.
• Hybrid approach: "The parties agree to first attempt resolution through mediation. If mediation fails within 30 days, disputes will be resolved through binding arbitration under AAA Commercial Arbitration Rules."

Revenue splits should reflect contribution asymmetry. Here's what I typically recommend based on partnership type:

Technology Integration (No Direct Revenue Share)

Most tech integration partnerships don't involve direct payment between partners. Both companies benefit from increased customer value and retention. Revenue model:

• Each company charges its own customers directly
• No revenue share between partners
• Potential for joint customer referrals with standard affiliate commissions (10-20%)

White-Label Partnership

The underlying technology provider typically receives 60-80% of revenue because they built and maintain the core product. The white-label partner receives 20-40% for distribution, customer acquisition, and support.

Alternative model: Flat licensing fee instead of revenue share. Example: Distributor pays $50,000/year for white-label rights, then keeps 100% of customer revenue. This shifts risk to the distributor (they must hit a revenue threshold to break even) but gives them more upside.

Reseller Partnership

Standard reseller commissions: 20-30% for transactional sales, 10-20% for recurring SaaS subscriptions. Higher commissions (up to 40%) for enterprise deals that require significant sales effort.

Watch out for: Whether the commission applies to the full contract value or only the first year. Enterprise SaaS companies often pay commissions only on Year 1 revenue to avoid perpetual commission obligations.

API Partnership (Usage-Based Pricing)

API providers typically charge per-call fees or tiered pricing based on volume:

• Per-call pricing: $0.001 - $0.01 per API call, depending on complexity
• Tiered pricing: $500/month for up to 100,000 calls, $1,500/month for up to 500,000 calls, custom enterprise pricing above that
• Revenue share: 5-15% of transaction value if the API enables revenue-generating activity (e.g., payment processing API takes 2.9% + $0.30 per transaction)

Co-Marketing Partnership (No Direct Revenue Share)

No money changes hands. Value comes from lead generation, brand association, and content distribution. Measure success through:

• Number of qualified leads generated
• Conversion rate from partnership-sourced leads
• Customer lifetime value (LTV) of partnership customers vs. other channels

How to Handle Discounts and Promotions

Your revenue share formula must account for discounting. Options:

1. Commission on actual revenue collected: If you offer a 50% discount, your partner's commission gets calculated on the discounted price. This is fair but reduces partner incentives to close deals with heavy discounts.
2. Commission on list price, with discount limits: Partner earns commission on full list price, but discounts above 20% require your approval. This protects you from partners giving away your product.
3. Tiered commissions based on discount level: 30% commission on full-price sales, 20% commission on sales with 10-25% discount, 10% commission on sales with 25%+ discount. This incentivizes partners to sell at full price.

I've seen partnerships collapse over IP ownership disputes. Here are the most common pitfalls and how to avoid them:

Pitfall 1: Ambiguous Joint IP Ownership

You and your partner build a custom integration. Who owns it?

Pitfall 2: Derivative Works Without Clear Ownership

In white-label partnerships, the distributor often customizes the underlying product (adding features, changing UI, integrating with third-party tools). Who owns these modifications?

Pitfall 3: No IP Audit Rights

If your partner is using your IP beyond the scope of the license, how do you find out?

Pitfall 4: No IP Escrow for Critical Dependencies

If you're building your product on top of a partner's API or white-labeling their technology, what happens if they go bankrupt or get acquired?

Pitfall 5: Trademark and Brand Usage Without Guidelines

Your partner wants to use your logo in their marketing. What are the rules?

Pitfall 6: No IP Indemnification

If your partner's technology infringes a third party's patent or copyright, and you get sued because you're distributing it, who defends the lawsuit?

The indemnifying party (technology provider) should have the right to control the defense and settlement of IP claims. The indemnified party (distributor) shouldn't settle claims without the provider's consent, because settlements can include admissions that affect the provider's other customers.

The terms "partnership" and "reseller" are often used interchangeably, but they're legally distinct and require different contract structures.

Use a Reseller Agreement When:

• One-directional value flow: You're simply granting permission for another company to resell your SaaS product. They don't contribute technology, IP, or infrastructure.
• No integration required: The reseller is selling your product as-is, not integrating it with their own platform.
• Transactional relationship: The reseller brings customers, you fulfill the service. There's no ongoing collaboration beyond order processing and commission payments.
• Commission-based compensation: Reseller earns a percentage of sales or a per-seat fee. No revenue sharing based on joint value creation.

Use a Partnership Agreement When:

• Bidirectional value creation: Both parties contribute something valuable—technology, distribution, IP, customer base, or infrastructure.
• Technical integration: The companies' platforms integrate via API, and customers see a unified experience.
• Joint product development: You're building new features together or white-labeling one party's technology for distribution by the other.
• Revenue sharing based on joint value: Revenue splits reflect each party's contribution to customer acquisition, product development, and ongoing support.
• Shared risk: Both parties invest resources (engineering time, marketing budget, customer support) with uncertain ROI.

Key Legal Differences

Provision	Reseller Agreement	Partnership Agreement
IP Ownership	Provider retains all IP; reseller gets no license beyond selling	Each party retains pre-existing IP; joint IP addressed explicitly
Revenue Model	Fixed commission or markup on sales	Revenue share based on contribution; may vary by customer type or feature usage
Customer Relationship	Provider owns customer; reseller is just the sales channel	May be shared or assigned to one party; both parties may interact with customers
Support Obligations	Provider handles all support; reseller refers support requests to provider	Support may be split by technical area or customer tier
SLA	Provider's standard SLA applies; reseller has no SLA obligations	Both parties may have SLA obligations (uptime, integration reliability, API response time)
Non-Compete	Rare; reseller can typically sell competing products	Common in white-label and exclusive partnerships
Exclusivity	Rarely exclusive; provider uses multiple resellers	May be exclusive in a specific territory or vertical

Hybrid Structures: When You Need Both

Some relationships start as reseller deals and evolve into partnerships as integration deepens. Example:

When this happens, execute a new partnership agreement and explicitly state that it supersedes the prior reseller agreement. Avoid trying to amend the reseller agreement to cover partnership terms—you'll end up with a Frankenstein document that doesn't fit either model cleanly.

What's the difference between a SaaS partnership agreement and a reseller agreement?

A partnership agreement is bidirectional and collaborative—both parties contribute resources, IP, or distribution. A reseller agreement is unidirectional: one party grants the other permission to resell their SaaS product for a commission or markup. Partnerships involve shared risk and reward; reseller relationships are transactional.

How should revenue splits be structured in a SaaS partnership?

Revenue splits depend on contribution asymmetry. For technology integration partnerships where both sides provide equal value, 50/50 is standard. For white-label or reseller models, the party owning the underlying technology typically receives 60-80%, while the distributor gets 20-40%. API partnerships often use tiered pricing where the API provider takes a per-call fee or percentage of transaction value.

Who owns IP created during a SaaS partnership?

Default rule: each party retains ownership of their pre-existing IP and any new IP they independently develop. Joint IP (created collaboratively) should be addressed explicitly—either joint ownership with cross-licenses, or assignment to one party with a license back to the other. Never leave this ambiguous.

Should I include a non-compete clause in my SaaS partnership agreement?

It depends on the partnership type. For white-label and exclusive distribution deals, a non-compete (limited to the partnership's scope and territory) is standard. For technology integrations and co-marketing partnerships, non-competes are rare and often unenforceable. If you include one, limit it to 12-24 months post-termination and define the restricted activities narrowly.

Do I need a Data Processing Addendum (DPA) in my SaaS partnership agreement?

Yes, if either party processes personal data on behalf of the other or if your customers' data flows between both platforms. GDPR, CCPA, and other privacy laws require written data processing agreements that specify roles (controller vs. processor), data handling obligations, subprocessor consent, breach notification timelines, and data subject rights. Don't skip this.

What's a typical termination notice period for SaaS partnerships?

60-90 days is standard for convenience termination. 30 days is common for breach-based termination with a cure period. Shorter notice periods (30 days for convenience) work for low-integration partnerships like affiliate or co-marketing deals. Longer periods (90+ days) are appropriate for deep technical integrations where customers rely on the partnership.

Should I use arbitration or litigation for dispute resolution in SaaS partnerships?

I generally recommend arbitration (AAA or JAMS) for SaaS partnerships because it's faster, private, and both parties are typically sophisticated commercial entities. Litigation makes sense if you anticipate needing injunctive relief (e.g., to stop IP theft) or if the partnership involves complex multi-jurisdictional issues. A hybrid approach—mediation first, then arbitration—often works best.

What governing law should I choose for a SaaS partnership agreement?

Choose the state where the economically dominant party is headquartered, or Delaware if you want predictable, business-friendly contract law. California is common for tech partnerships but has employee-protective rules that can complicate non-solicitation clauses. Avoid choosing a state with no connection to either party—courts may ignore it.

How long should the confidentiality obligations survive termination?

2-3 years post-termination is standard for general business confidential information. 5 years or perpetual protection is appropriate for trade secrets, source code, and customer lists. SaaS partnerships often involve API keys, infrastructure details, and customer usage data—these should have longer survival periods.

Do I need an SLA in my SaaS partnership agreement?

Yes, if uptime/performance of one party's platform affects the other's business. SLAs should specify uptime commitments (e.g., 99.9%), measurement methodology, scheduled maintenance windows, and remedies for breaches (service credits, not liquidated damages). If you're white-labeling or reselling another company's SaaS, the SLA protects you from liability to your end customers when your partner's platform goes down.

Can I auto-renew a SaaS partnership agreement?

Yes, auto-renewal is common and recommended for SaaS partnerships to avoid disruption. Typical structure: initial term of 1-3 years, then automatic 1-year renewals unless either party gives notice of non-renewal (60-90 days before the end of the then-current term). Make sure the notice requirements are clear and include a mechanism for either party to opt out without penalty.