Consulting Agreement with Sharing of Software Revenues Template

In plain language: Identifies the company and consultant as legal entities, states the purpose of the engagement, and records the date the agreement becomes binding.

Common mistake: Using a trade name instead of the registered legal entity name. Enforcement of IP assignment and revenue-share obligations becomes ambiguous if the contracting entity cannot be clearly identified.

In plain language: Defines precisely what the consultant will do — technical deliverables, advisory functions, sales activities — and excludes everything else.

Common mistake: Defining scope so broadly that any business activity of the consultant could be claimed as work product owned by the company — creating IP disputes long after the engagement ends.

In plain language: Sets the base consulting fee — hourly rate, project fee, or monthly retainer — payment schedule, and expense reimbursement policy.

Common mistake: Omitting an expense pre-approval threshold. Without one, the consultant can incur substantial costs the company is obligated to reimburse regardless of budget.

In plain language: Defines the exact percentage of software revenues owed to the consultant, the revenue base (gross or net), deductions permitted, payment frequency, and reporting obligations.

Common mistake: Failing to define 'net revenue' with an explicit, closed list of permitted deductions. Companies may otherwise deduct overhead, salaries, or marketing costs — eroding the consultant's share to near zero.

In plain language: Specifies how long the revenue share obligation lasts — by calendar duration, total cumulative payout, or number of product versions — and any cap on total amounts payable.

Common mistake: No defined end date or cap on the revenue share. An open-ended obligation can survive product pivots, acquisitions, and management changes — creating unexpected long-term liability for the company.

In plain language: Assigns all work product and new IP created under the engagement to the company, while carving out the consultant's background IP with a limited license grant to the company.

Common mistake: No background IP carve-out. Without it, consultants may be forced to assign pre-existing tools, frameworks, or libraries they use with other clients — making the clause overreaching and practically unworkable.

In plain language: Prohibits both parties from disclosing or using each other's confidential information — source code, roadmaps, revenue data, client lists — during and after the engagement.

Common mistake: A one-way confidentiality clause that only protects the company. Revenue data and client identities shared with the consultant are sensitive; consultants also disclose methodologies and pricing that warrant protection.

In plain language: Restricts each party from recruiting or soliciting the other's employees, contractors, and clients during the engagement and for a defined post-termination period.

Common mistake: Applying non-solicitation to clients with whom the consultant had no contact during the engagement. Courts may void an overbroad clause, eliminating even the reasonable restrictions.

In plain language: States the contract duration, termination rights for cause and convenience, notice period, and what happens to accrued and future revenue share upon termination.

Common mistake: Not specifying whether the revenue share survives termination. If silent, courts in some jurisdictions may treat accrued rights as vested — leaving the company paying revenue share on a product long after the consultant stopped contributing.

In plain language: Specifies the jurisdiction whose laws govern the contract, the dispute resolution mechanism (arbitration or litigation), and confirms the document supersedes all prior discussions.

Common mistake: Selecting a governing jurisdiction with no connection to either party's location. Some jurisdictions — particularly California — apply local law regardless of what the contract specifies, making a remote governing-law choice ineffective.

A consulting agreement with software revenue sharing is a legally binding contract that combines a standard consulting engagement with a provision entitling the consultant to a percentage of the software's commercial revenues. It defines the consulting scope, fees, the revenue share formula, IP ownership, and termination rights in a single document. Companies use it to attract senior consultants when upfront cash is limited, offering future upside instead of — or in addition to — standard fees.

The percentage is negotiated based on the consultant's contribution relative to total development cost, the risk they are taking by accepting deferred compensation, and the expected revenue trajectory. Typical ranges run from 2% to 15% of net revenues for consultants who contribute meaningfully to product development or go-to-market. Percentages above 20% are uncommon unless the consultant is effectively a co-founder contributing without salary.

Net revenue — gross revenue minus a defined list of deductions such as refunds, chargebacks, and payment processing fees — is the more common and fairer base. Gross revenue is simpler to calculate but can overstate the economic benefit to the company. Whichever base you choose, define it precisely with a closed list of deductions; leaving it open invites disputes about what costs can be subtracted.

Under a standard consulting agreement with revenue sharing, all work product created during the engagement is assigned to the company. The consultant typically retains ownership of background IP — tools, frameworks, and methods developed independently — and grants the company a license to use that IP as incorporated in the software. Without a clear IP clause, ownership defaults to the creator under copyright law in most jurisdictions.

The contract should explicitly address this. If silent, accrued revenue share obligations may transfer to the acquirer as a liability, and future obligations may survive under successor-in-interest principles in most jurisdictions. Common approaches include a lump-sum buyout of the revenue share right at acquisition, a cap triggered by a change-of-control event, or an explicit clause stating the revenue share terminates upon acquisition.

Yes. A consulting agreement engages an independent contractor — the consultant pays their own taxes, receives no benefits, and retains control over how they perform the work. An employment contract creates an employer-employee relationship with payroll tax obligations, statutory benefits, and termination protections. Offering revenue share does not change the classification; what matters legally is the degree of control the company exercises over the consultant's methods and schedule.

Yes, and for most companies it should be. A cumulative cap — for example, a maximum total payout of $[AMOUNT] — gives the company a defined maximum liability it can account for and value. A time-based cap (e.g., 24 months from first sale) is also common. Many agreements combine both: the share ends when the cap is reached or the period expires, whichever comes first.

For straightforward domestic engagements with a clear scope and a simple revenue-share formula, a high-quality template is a strong starting point. Legal review is strongly recommended when the revenue share obligation is material in dollar value, the consultant is contributing significant IP, either party operates in multiple jurisdictions, or the software has acquisition potential. A 1–2 hour review typically costs $300–$600 and can prevent disputes worth multiples of that cost.

Thirty days written notice for convenience termination is the most common standard for consulting agreements. Cause-based termination — misconduct, material breach, or IP misappropriation — typically allows immediate termination with written notice of the specific cause. The agreement should state explicitly whether accrued revenue share survives each type of termination and, if so, for how long.