Enterprise SaaS deals rarely start with a signed subscription agreement. They start with a pilot — a limited deployment that gives the prospect organization a chance to evaluate your product in their environment before committing to a full contract. What most early-stage SaaS companies do not realize is that this pilot period creates significant legal exposure if it is not governed by a proper agreement.
A SaaS pilot or proof of concept (POC) agreement is not a courtesy document. It is the legal framework that determines who owns what gets built during the trial, what happens to your prospect’s data, whether your software’s limitations create liability, and whether the pilot converts automatically to a paid arrangement or requires a new signature.
1. Why a Verbal or Email-Based Pilot Creates Real Risk
Many SaaS founders treat enterprise pilots as informal relationships — a handshake deal or a thread of emails confirming the scope. The problem is that when something goes wrong during an unformal pilot (a data issue, a software failure, a dispute about what was agreed), you have no documented terms to fall back on.
More importantly, the prospect organization’s legal team will often try to impose their standard vendor terms on the relationship — terms written to benefit the customer, not the SaaS provider. If you do not have your own pilot agreement, you end up negotiating from the customer’s paper. A purpose-built SaaS pilot agreement puts you in a better negotiating position and protects your core commercial and IP interests from day one of the evaluation.
2. Defining Scope and Duration
The pilot agreement needs to define exactly what is being tested, by whom, over what period, and on what terms. Scope creep is common in enterprise pilots: a limited deployment agreed in January becomes a company-wide rollout by March, all under the “pilot” label that was never meant to cover that scale.
Your agreement should specify:
- The exact features or modules included in the pilot
- The number of authorized users or seats
- The technical environment (production, staging, or sandbox)
- The pilot duration, including a specific start and end date
- Whether the pilot can be extended and under what conditions
Without a defined scope, a prospect organization can argue that expanded use during the pilot was authorized — and that your failure to object converted the expansion into an implied license. That argument can cost you a paid deal that should have converted to a full subscription.
3. Intellectual Property During the Pilot
This is the clause that SaaS companies most frequently get wrong in pilot agreements. When an enterprise prospect evaluates your software in a live environment, several IP questions arise that your agreement must answer.
Feedback and Improvements
Enterprise prospects frequently provide detailed feedback during pilots — bug reports, feature requests, workflow suggestions. Some of that feedback, if implemented, becomes part of your product. Your pilot agreement should include a feedback IP clause making clear that all feedback, suggestions, and improvements contributed by the prospect during the pilot are assigned to your company or licensed to you on a perpetual, royalty-free basis. Without this clause, the prospect could later argue they have a co-ownership claim over features that started as their feedback.
Customization and Integrations
If your team performs any customization or builds integrations during the pilot, the agreement should specify who owns that work. Custom work built on your platform typically should remain your property as part of the platform. If customization is specific to the prospect and has no broader application, the ownership question is more nuanced and should be negotiated explicitly.
This intersects with broader IP assignment practices: if contractors or consultants are doing the customization work during the pilot, your IP assignment agreements for startups need to be in place to ensure all that work flows to your company and not to the individuals performing it.
4. Confidentiality and NDA Terms
A pilot involves sharing sensitive information in both directions. The prospect shares their technical environment details, business processes, internal data, and evaluation criteria. You share your product roadmap, pricing structure, proprietary algorithms, and potentially unreleased features.
Your pilot agreement should include mutual confidentiality obligations — or reference a separate NDA that was signed before the pilot began. The confidentiality scope should cover: the software itself, the terms of the pilot arrangement (including pricing), and any non-public business information shared during the evaluation.
Standard enterprise pilot NDAs for tech companies need to address specific issues like residual information clauses (does knowledge retained in unaided memory remain subject to NDA?), the return or destruction of confidential materials at pilot end, and how long the confidentiality obligation survives termination. If you do not have a template NDA for tech company pilots, review what an NDA for tech companies should include before you run your next enterprise evaluation.
5. Data Handling and Security During the Pilot
Enterprise prospects will frequently push their personal data or business-critical data into your platform during a pilot, even when you ask them not to. Your pilot agreement needs to address this reality.
The agreement should specify: what categories of data the prospect is permitted to load into the pilot environment, what your security standards and certifications apply during the pilot, how data is handled at pilot termination (deletion timeline, export options), and what your data breach notification obligations are during the pilot period.
If the prospect is a regulated entity — a healthcare company, a financial institution, an education platform — they may have specific compliance requirements (HIPAA, GLBA, FERPA) that affect what they can share with you during a pilot and what security controls you must maintain. These requirements should be negotiated before the pilot begins, not discovered midway through.
Understanding what a SaaS agreement covers is the starting point for structuring how your pilot agreement interacts with your eventual subscription terms.
6. Pricing, Conversion, and What Happens at Pilot End
One of the most commercially important clauses in any SaaS pilot agreement is the conversion mechanism. What happens when the pilot ends?
Your agreement should specify:
- Whether the prospect must take any affirmative action to convert (sign a new agreement, issue a purchase order) or whether inaction results in automatic conversion to a paid subscription
- Whether the pilot pricing carries any promotional rate and what the post-pilot pricing will be
- Whether the prospect has any exclusivity or preferred pricing for converting within a specific window
- What happens if the pilot ends without conversion: data deletion, access termination, any notice requirements
Automatic conversion clauses require careful drafting to be enforceable — particularly for agreements with California-based enterprise customers, where the state’s Automatic Renewal Law applies to subscription arrangements and requires clear advance disclosure of auto-renewal terms.
7. Limitation of Liability During the Pilot
During a pilot, your software is running in a customer’s environment and may be integrated with their systems. A bug or outage during the pilot can cause real operational disruption for the prospect — but a pilot is an evaluation relationship, not a production deployment with contractual SLAs.
Your pilot agreement should limit your liability during the evaluation period. A well-drafted limitation clause will: cap your aggregate liability at a nominal amount (often the fees paid, which during a free pilot may be zero), exclude liability for indirect or consequential damages, and clarify that the software is being provided “as is” during the pilot without the warranties that will apply under the full subscription agreement.
Prospects may push back on these limitations, particularly if they are loading production-level data into the pilot environment. That pushback is itself a signal that the pilot has moved beyond evaluation scope — and a reason to convert to a paid agreement with appropriate protections before proceeding.
If you are running enterprise SaaS pilots and want an agreement that protects your IP, data, and commercial interests, connect with why every SaaS business needs a SaaS agreement lawyer — and what that counsel actually handles.
Frequently Asked Questions
Is a free pilot still a legal contract?
Yes. A pilot agreement is a binding contract regardless of whether money changes hands. The consideration in a free pilot is typically the mutual obligations: the vendor provides access to software, and the prospect provides feedback, agrees to usage restrictions, and accepts the confidentiality and IP terms. A signed pilot agreement is enforceable even at zero cost.
Can I use my standard subscription agreement for a pilot?
You can, but it typically creates the wrong commercial dynamic. A full subscription agreement implies committed usage, pricing, and SLA obligations that may not apply during an evaluation. A dedicated pilot agreement scoped to the evaluation period is cleaner and gives both parties clarity about what the relationship is and what it is not.
What should happen to customer data at the end of a pilot that does not convert?
Your pilot agreement should specify a data deletion timeline — typically within 30 days of pilot termination — and give the prospect an option to export their data before deletion. This should mirror your standard subscription agreement’s data handling terms to avoid creating inconsistent obligations if the prospect converts.
Does a SaaS pilot agreement need to be reviewed by a lawyer?
For material enterprise evaluations, yes. Enterprise prospects will often have their own legal teams review your pilot agreement and push for changes. Having a technology lawyer draft your pilot agreement ensures you are not giving up rights you cannot recover — particularly on IP, data, and liability clauses.
How do I protect proprietary features I show during a pilot from being copied?
Your confidentiality clause covers what the prospect learns about your product during the pilot. Additionally, the feedback IP clause ensures that any improvements or suggestions derived from seeing your proprietary features stay with your company. For features that are genuinely novel, consider whether patent protection is warranted before running broad enterprise evaluations.
Lock Down Your Enterprise Pilots Before They Lock You Out
A poorly structured pilot can cost you the IP you built, the data you trusted to a prospect, and the commercial terms you thought you were negotiating toward. The time to fix a pilot agreement is before the evaluation starts — not when the prospect’s legal team sends back a redlined version designed to protect their interests at yours.
Hansen Tong at TOSLawyer.com advises SaaS companies on pilot agreements, subscription contracts, and the full range of technology agreements that support enterprise sales. Contact us to get a pilot agreement that works for your business.