Performance Based Contract Template

In plain language: Identifies both parties as legal entities, defines the services or work being performed, and states that compensation is contingent on measurable outcomes.

Common mistake: Describing services too broadly in the body and relying on a vague schedule. If the scope is ambiguous, disagreements over which activities count toward a KPI arise immediately after the first measurement period.

In plain language: Lists each KPI by name, defines it precisely, establishes the baseline value measured before work begins, and states the target value and the measurement period.

Common mistake: Setting targets without documenting the baseline at contract execution. If baseline data is added later, one party will dispute the starting point when it determines the size of the variable payment.

In plain language: Specifies exactly how each KPI will be measured — which system or tool generates the data, who has access, how often data is pulled, and which party's records control in a dispute.

Common mistake: Naming a platform without specifying which report or metric definition within that platform. Platforms like Salesforce or HubSpot have multiple ways to calculate 'revenue' — the contract must pin down the exact report and any applied filters.

In plain language: Defines the formula that converts KPI results into dollar amounts, states any caps or floors on variable pay, and sets the date by which payment must be made after each measurement period closes.

Common mistake: Omitting a payment cap. Without a ceiling, a single anomalous result — a one-time enterprise contract that skews MRR — can generate a payment far larger than either party anticipated, damaging the relationship.

In plain language: Requires the client to provide KPI data on a defined schedule, gives the contractor the right to audit supporting records, and establishes how discrepancies trigger review.

Common mistake: Giving the contractor audit rights without a frequency limit or cost-allocation rule. Unlimited audit rights create operational burden for the client and become a harassment tool in contentious engagements.

In plain language: Defines what portion of a KPI result is attributable to the contractor's work and excludes external factors — market downturns, client pricing changes, or unrelated campaigns — from the calculation.

Common mistake: Omitting an attribution clause entirely, then discovering mid-engagement that a pricing change the client made independently drove most of the measured improvement. Clear exclusions prevent disputes that neither party can resolve objectively.

In plain language: Sets the threshold below which underperformance is formally triggered, the remediation period and required corrective steps, and the financial consequences if the deficiency is not cured.

Common mistake: Triggering termination after a single missed period without a remediation window. One underperforming month is often attributable to seasonal variation or a data anomaly — skipping remediation creates resentment and invites litigation.

In plain language: Protects the client's KPI data, revenue figures, and customer information shared with the contractor for measurement purposes, and restricts the contractor from using that data for any purpose other than performing under this agreement.

Common mistake: Using a generic NDA clause that does not specifically address KPI and financial data shared for measurement. Revenue and customer data is typically more sensitive than general business information — name it explicitly.

In plain language: States the initial contract term, renewal conditions, each party's termination rights, and how in-progress measurement periods are handled when the contract ends.

Common mistake: No provision for how to treat a measurement period that is open when the contract terminates. Without it, the contractor may argue they are owed a full period's fee for a partial period of work.

In plain language: Creates a specific mechanism for resolving disputes about KPI calculations — escalation to senior management first, then an independent expert, before arbitration or litigation is available.

Common mistake: Routing measurement disputes through general commercial arbitration from the start. Measurement disputes are technical, not legal — an independent data expert resolves them faster and at a fraction of the cost of a commercial arbitrator.

A performance-based contract is a legally binding agreement that ties all or part of a service provider's compensation to the achievement of specific, measurable outcomes — such as revenue growth, cost savings, uptime percentages, or conversion rates — rather than paying a fixed fee for time or deliverables. The contract defines the KPIs, baseline values, payment formula, measurement methodology, and what happens when targets are missed.

Performance-based contracts work well for marketing and growth agencies billing on revenue share, management consultants charging a percentage of documented savings, technology vendors guaranteeing SLA metrics, sales contractors paid by commission, and any vendor relationship where the client's priority is measurable outcomes rather than hours spent. They are less appropriate for creative or research work where outputs are subjective or outcomes are influenced heavily by factors outside the contractor's control.

Each KPI should be defined with a one-sentence description of what is measured, the exact calculation method, the data source, the unit of measurement, the baseline value at contract execution, the target value, and the measurement period. Definitions precise enough for a neutral accountant to calculate without additional context are generally enforceable; vague terms like "improved performance" are not.

A payment formula converts a KPI result into a specific dollar amount. Common structures include a fixed percentage of the measured improvement above baseline, a tiered rate that increases as performance exceeds different thresholds, or a flat bonus triggered when a binary target is met. Every formula should include a performance threshold below which no variable pay is earned and a per-period cap above which no additional payment accrues, regardless of overperformance.

A well-drafted performance-based contract includes a tiered dispute resolution mechanism specific to measurement disagreements. The first step is escalation to senior representatives from each party. If unresolved, the dispute goes to a neutral independent expert — typically an accountant or data analyst — whose determination is binding. General commercial arbitration should be reserved for disputes the expert mechanism cannot resolve, as it is far more expensive and time-consuming.

A performance-based contract is generally enforceable when properly executed, provided the KPIs are objectively measurable, the payment formula is unambiguous, and the measurement methodology is specified in enough detail to be applied without additional negotiation. Courts and arbitrators in the US, Canada, the UK, and the EU have consistently upheld outcome-based payment structures when the metrics and formula meet the definiteness standard required for contract enforcement.

Attribution is the contractual rule that determines what portion of a KPI movement is caused by the contractor's work versus external factors such as market trends, client pricing changes, or seasonal patterns. Without an attribution clause, contractors can claim fees for improvements they did not drive, and clients can withhold fees for shortfalls caused by their own decisions. Clear exclusions for identifiable external factors are the most practical way to manage attribution risk.

For straightforward domestic engagements with simple KPIs and a standard payment formula, a high-quality template is usually sufficient. Legal review is strongly recommended when the engagement involves large variable payments, complex attribution rules, cross-border performance measurement, regulated industries, or KPIs tied to sensitive financial data. A 2–3 hour template review typically costs $400–$800 and is cost-effective for any engagement where annual variable fees could exceed $50,000.

Baseline data should be exported from the agreed measurement platform on or before the contract's effective date, attached to the contract as a signed exhibit, and initialed by both parties. If the measurement platform is not yet operational, the contract's effective date should be delayed until it is. Agreeing to determine baselines later is the single most common cause of disputes in performance-based engagements.