SaaS Tips by Sapna | Tip No. 13 – Pilots

Your customer may want to run a pilot of your SaaS application for a limited term. And your customer will likely expect to fully negotiate your SaaS agreement since it will be used in production. This may not be worth your time for a short-term contract. Consider having a separate pilot agreement for your SaaS, keeping in mind the limited reach of a pilot and your customer’s concerns.

Alternatively, you may want to have your customer commit to a full-term unless the pilot failed some clear, objective criteria. This would increase the chance that your SaaS term would be extended beyond the pilot.

A pilot, like a proof of concept, is a limited roll-out of the SaaS system with the aim of testing its capabilities. But there are important differences between a pilot and a POC.

  • A pilot is a limited roll-out of the SaaS system in a live, production environment. This isn’t run in a sand-box or test environment. It is set up in the production environment and it connects to other live systems in your eco-sphere.
  • Data used is not test data and is not masked. This is live, production data that can potentially include confidential information and personal information
  • You will most likely have to pay the subscription fee for the period of the pilot.

The negotiation strategy for a pilot can be a little tricky. Since this is only a “test”, you may be pressured to not do a full dive into the agreement. But since this is a production application, you need to consider the warranties, security obligations, and risk allocation.

You may be tempted to negotiate a less-than-ideal agreement for the pilot given the limited production reach with the condition that the SaaS is not expanded into full production until a full agreement is negotiated. This can work, but you will need business buy-in. Nothing is more frustrating for the business than to have a successful pilot and then have to wait until a production roll-out until the full agreement is negotiated.

The learn more from the customer’s perspective and to join in the conversation, check out my LinkedIn post.

About the Author

More Articles

About the Author

Leave a Reply

Your email address will not be published. Required fields are marked *

Related Articles

SaaS Tips by Sapna | Tip No. 14 – Subcontractors

Your SaaS supplier will almost always subcontract part of the services to a third party so the SaaS

SaaS Tips by Sapna | Tip No. 12 – Proof of Concept

Before engaging a new SaaS system into your company, you will almost always start with a proof of

SaaS Tips by Sapna | Tip No. 11 – Open-Source and Third-Party Software

If the SaaS system includes open-source software, your SaaS contract should contain the appropriate provisions to ensure the

SaaS Tips by Sapna | Tip No. 10 – EULAs

This tip covers when and how to include and negotiate a EULA in a SaaS Agreement.

Most Recent

The Contracts Queen’s Guide to Creating a Practical Contract Playbook

Contract playbooks can be used to improve relationships, empower stakeholders, speed up the contracting process, and save time

Acceptance Terms in SaaS Agreements

Acceptance is an important commercial concept to understand as it pertains to implementation services in SaaS agreements.

Nine Financial Terms Every SaaS Negotiator Should Know

By having a strong grasp of finance aspects of SaaS agreements, you are helping the business win new

Elevating Your GC Brand: 3 Contract-Centric Strategies

A strong GC brand doesn't just bring more influence, compensation, and respect; it also opens doors to the

Subscribe to Contract Nerds weekly newsletter

* indicates required
Professional Role
Generic filters