Offering a POC (proof of concept) is a common commercial strategy for SaaS vendors. It allows you to convince a prospect through demonstration, without requiring a firm commitment upfront. This trial phase is often decisive in winning the deal. But for it to be genuinely beneficial, it must be properly structured from a legal perspective.

POC vs trial period: two different approaches

Some vendors use a standard SaaS agreement with an initial free or discounted period. If the customer does not terminate at the end of that period, the agreement continues automatically. This is a trial period, embedded within the main contract.

A standalone POC works differently. It is time-limited, with no automatic renewal, and does not yet commit the parties to a long-term commercial relationship. It is a separate arrangement that requires its own contractual framework.

Why use a dedicated POC agreement?

A POC does not serve the same purpose as a standard SaaS agreement. Its objective is evaluation, not commercial exploitation. The functional scope is typically restricted. The customer does not benefit from the same level of service or the same commitments. The contract should reflect this.

A standard SaaS agreement imposes significant obligations on the vendor: availability, support, maintenance, security. These commitments are inappropriate for a test phase. A dedicated POC agreement allows the vendor to limit the scope of its commitments and reduce its legal exposure. For a comparison with testing without any contract, see my article on the risks of testing a SaaS without a contractual framework.

Key provisions for an effective POC agreement

The following points should be addressed in any POC agreement:

1. Short duration with no automatic renewal

A POC is a limited phase, typically lasting 15 to 60 days. It should expire automatically unless the parties expressly agree to proceed further. This avoids any ambiguity regarding an implied commitment.

2. Restricted scope of use

The customer should only have access to the features necessary to evaluate the solution. The agreement may provide for:

  • A limited or partial version of the platform.
  • Access restrictions (number of users, modules tested, etc.).
  • A prohibition on misuse or reverse engineering of the solution.

This limits technical, competitive and contractual risk.

3. No heavy-duty obligations

By default, the vendor should not owe any guarantee of availability, support or security during a POC. If any such services are provided on an exceptional basis, they should be specifically identified.

4. DPA requirements, even during a POC

If the POC involves the processing of real personal data, a Data Processing Agreement (DPA) is mandatory under Article 28 of the GDPR. The DPA may be lighter than the one used for a production contract, but it cannot be omitted entirely. The absence of a DPA during a POC exposes both parties to a compliance risk.

5. Obligation of means only

The agreement should exclude any obligation of result. The vendor does not guarantee the success of the test — only that it will provide the means necessary to carry it out.

6. Reinforced liability limitations

A POC is not a production contract. It is therefore appropriate to limit the vendor’s liability significantly: low cap, broad exclusions, no compensation for indirect losses. The objective is to protect the vendor during a phase where the commercial commitment is minimal.

7. Specific financial terms

A POC is often offered free of charge or at preferential rates. If any fees apply (setup, customisation, training), they should be clearly defined. The agreement should also make clear that these fees do not predetermine the pricing of any future subscription.

The POC agreement as a foundation for the commercial relationship

A well-drafted POC agreement demonstrates to the prospect that the vendor is structured and professional. It establishes the ground rules from the outset, while avoiding premature commitment to a long-term arrangement.

If the POC is successful, it serves as a springboard to a standard SaaS agreement. If it is not, it protects the vendor’s interests and prevents scope creep (extended access, unauthorised reuse, etc.).

Conclusion

The test phase is a decisive moment for winning the customer. But it does not justify operating without protection. A lightweight but well-constructed POC agreement is sufficient to secure both parties. If you need a template adapted to your business, book a call.

Other posts


Blog image
SaaS Exit Fees Under the Data Act: What You Can Challenge

The Data Act limits what SaaS vendors can charge when you switch providers. Permitted fees, prohibited charges, and the 2027 deadline explained.

Blog image
How to Terminate a SaaS Agreement Under the Data Act: Practical Guide

Stuck in a SaaS contract your company no longer needs? The EU Data Act gives you a legal right to switch providers. Eligibility, process, and pitfalls.

Let's build together to grow your business