SAAS Reseller Agreement Template

In plain language: Grants the reseller a defined right — exclusive or non-exclusive — to market and sell the vendor's SaaS product within a stated territory or customer segment.

Common mistake: Failing to specify whether the appointment is exclusive or non-exclusive. Leaving this ambiguous allows the vendor to appoint competing resellers in the same territory — or gives the reseller grounds to claim exclusivity that was never intended.

In plain language: Sets the reseller's purchase price (as a percentage discount from list), the end-customer pricing floor, and any minimum annual revenue or seat commitment required to maintain active status.

Common mistake: Setting a minimum commit without defining what happens if the reseller misses it. Without a stated consequence — tier downgrade, conversion to non-exclusive, or termination right — the clause is unenforceable in practice.

In plain language: Defines whether the vendor provides co-marketing funds to the reseller, the approval process for using those funds, and the documentation required to receive reimbursement.

Common mistake: Making MDF available without requiring pre-approval of activities. Resellers spending discretionary MDF on unapproved channels — sponsorships, gifts, or unrelated advertising — create both financial and compliance exposure for the vendor.

In plain language: Governs how the reseller may use the vendor's name, logo, and product marks in marketing materials, and sets requirements for co-branding, trademark attribution, and prior approval of advertising.

Common mistake: No brand guideline reference or approval mechanism for marketing collateral. Resellers operating without guardrails frequently misrepresent features, make unsupported claims, or create materials that dilute the vendor's trademark rights.

In plain language: Determines who holds the contractual and billing relationship with end customers, who owns the customer data generated during use, and what happens to that data and those relationships if the reseller agreement terminates.

Common mistake: Leaving customer ownership silent. If the agreement does not specify who holds the end-customer relationship, both parties may claim it on termination — resulting in disputes, customer confusion, and potential data-portability claims under GDPR or CCPA.

In plain language: Defines the reseller's first-line support obligations, the escalation process for issues the reseller cannot resolve, and whether the vendor's uptime SLA flows through to end customers.

Common mistake: No escalation time threshold before the reseller can contact vendor support. Without a filter, vendor support teams are overwhelmed with tier-1 issues the reseller should handle, degrading response times for genuine escalations.

In plain language: Grants the reseller a limited right to demonstrate and resell the SaaS product while explicitly prohibiting reverse engineering, copying, or creating derivative works.

Common mistake: No express prohibition on reverse engineering in the reseller agreement itself. Even if the vendor's end-user terms of service include this restriction, the reseller — who may never click through an EULA — is not contractually bound by it without a separate clause.

In plain language: Requires both parties to protect non-public information — pricing, roadmaps, customer lists, and technical architecture — shared during the relationship, with standard carve-outs for publicly known information.

Common mistake: Omitting a survival period after termination. A confidentiality clause that expires with the agreement leaves sensitive information — customer lists, pricing tiers, product roadmaps — unprotected immediately after the relationship ends.

In plain language: Sets the initial contract duration, renewal mechanics (auto-renew or manual), notice periods for non-renewal, and termination triggers including cause, convenience, and insolvency.

Common mistake: Auto-renewal with no notice window or an unrealistically short notice period — 15 days or fewer. Resellers who miss the window are locked into another year; vendors who miss it cannot offboard a non-performing partner. Sixty days is the practical minimum for meaningful commercial planning.

In plain language: Specifies which jurisdiction's law governs, how disputes are resolved (arbitration, mediation, or litigation), and caps each party's financial exposure to the other — typically limited to fees paid in the prior 12 months.

Common mistake: No limitation of liability clause, or one that carves out so many categories — IP indemnification, confidentiality breaches, customer claims — that the cap effectively does not exist. Every carve-out should be deliberate and proportionate to the actual risk.

A SaaS reseller agreement is a legally binding contract between a software vendor and an authorized third party — the reseller — that governs how the reseller may market, sell, and support the vendor's subscription product to end customers. It defines the reseller's pricing and margin, territory rights, branding obligations, customer ownership, support responsibilities, and the term of the relationship. Without one, either party can walk away at any time with no obligations, and disputes over customer ownership and data rights have no contractual resolution.

A referral agreement compensates a partner with a commission for introducing a prospect to the vendor; the vendor closes the deal, invoices the customer, and owns the relationship. A reseller agreement authorizes the partner to transact directly — issuing quotes, collecting payment, and holding the customer contract. Resellers take on more commercial risk and responsibility but typically earn higher margins than referral commissions. Choosing the wrong model creates channel conflict and unclear customer ownership.

Non-exclusive appointments are standard for most channel programs because they allow the vendor to work with multiple resellers in the same territory simultaneously. Exclusive appointments are appropriate when a reseller is making a significant investment — dedicated headcount, co-marketing spend, or deep product integration — that justifies protection from vendor competition in their territory. Any exclusivity grant should be tied to a minimum annual revenue commit that the reseller must maintain to retain the exclusive status.

Ownership depends on how the agreement is structured. In a two-tier model, the reseller transacts with the end customer and is the customer of record — the vendor has no direct contractual relationship with the end user. In an agent or referral model, the vendor retains the end-customer relationship. The reseller agreement must state clearly who holds the billing relationship, who owns the customer data, and what happens to both on termination — courts will not assume an answer that the contract left open.

Reseller margins in SaaS channel programs typically range from 15% to 40% off list price depending on the product's price point, the reseller's value add, and whether the reseller handles first-line support. High-touch value-added resellers who perform implementation and support often negotiate 30–40% margins. Referral-style resellers who simply transact typically receive 15–20%. Whatever the margin, the agreement should include a floor price below which the reseller cannot sell to prevent undercutting the vendor's direct channel.

The agreement should define a wind-down process: a transition period — typically 60–90 days — during which existing subscriptions continue to be serviced, followed by either a vendor-directed migration of active accounts or a formal handoff protocol. Without this, end customers risk service disruption, and the vendor may lose accounts simply because the transition was disorganized. Customer data portability obligations under GDPR and CCPA add additional complexity if the reseller has been acting as a data processor.

Yes, if the vendor or any end customer is in the European Union or UK. Under GDPR, if the vendor processes personal data on behalf of the reseller's end customers, the vendor is acting as a data processor and the reseller may be acting as a data controller — requiring a Data Processing Agreement. If the vendor transacts directly with end customers and the reseller merely facilitates the sale, the data relationship is different but still requires documentation. Ignoring GDPR in the reseller agreement creates regulatory exposure for both parties.

Market development funds are a budget the vendor allocates to the reseller to co-fund demand generation, events, content creation, or sales enablement activities. MDF is typically activity-based — the reseller proposes a campaign, the vendor approves it, and the vendor reimburses eligible expenses upon receipt of documentation. MDF clauses should specify the annual budget, approval process, reimbursement timeline, and whether unused funds expire. Poorly structured MDF programs are frequently abused or create accounting disputes between the parties.

For straightforward non-exclusive reseller appointments with a single domestic partner, a high-quality template reviewed by your counsel is typically sufficient. Engage a technology transactions lawyer when appointing an exclusive reseller in a major market, when the partner handles significant customer data with GDPR or CCPA implications, when equity or acquisition scenarios are contemplated, or when the deal involves cross-border territories with differing competition law requirements. A 2–4 hour template review typically costs $600–$1,200 and is worthwhile for any appointment generating over $100K in ARR.

The agreement should specify the consequence explicitly — common options are automatic conversion from exclusive to non-exclusive status, a reduction in the reseller's margin tier, or a vendor right to terminate with 30 days' notice. Without a stated consequence, the minimum commit clause is effectively unenforceable because there is no contractual remedy the vendor can exercise. The reseller's failure to meet a commit with no stated consequence may be treated by courts as a waived condition rather than a breach.