Skip to main content
SUWANVARA LAWFIRM
Suwanvara Law Firm Co., Ltd.
SUWANVARA LAWFIRM
SUWANVARA LAWFIRM
Suwanvara Law Firm Co., Ltd.
Business Law

Trial or Pilot Before Buying: What a Proof-of-Concept (PoC) Agreement Should Say in Thailand

What a PoC or pilot agreement should fix in writing: scope, pass criteria, duration, who pays for what, test data, ownership and confidentiality of results, and what happens at the end, plus how to stop a trial turning into unpaid full use.

Suwanvara Law Firm— Business Law TeamNovember 21, 202615 min read
Trial or Pilot Before Buying: What a Proof-of-Concept (PoC) Agreement Should Say in Thailand

The core answer

A PoC (proof of concept) or pilot agreement has one job: to stop the trial turning into something nobody intended, such as an implied purchase, a licence for live use, or open-ended work done without payment. A good agreement fixes six things: what is tested and when it passes, how long it runs, who bears which cost, what data is used, who owns the results and any work created, and how the trial ends in a purchase, an extension or a walk-away.

The usual problem is not a badly written clause but a missing one. The buyer assumes it could use the system in the meantime, the vendor assumes the customer agreed to buy once the trial ended, and neither knows when test data must be returned or deleted. This page covers the PoC agreement itself. Designing a business trial, subscription pricing and software development contracts have their own pages (see Further reading).

Who should read which part

Your positionSections to read
Not signed yetSections 1 to 6 to draft scope, criteria, costs, data and ownership, and section 9 as the pre-signing checklist
Signed and runningSection 2 to check that criteria and end date match what is happening, section 4 to check data is used within scope, and section 7 to prepare the exit options
Already in disputeSections 7 and 8 on whether the trial is being treated as a purchase, and section 5 on who holds rights in results and work, then send documents to a lawyer using the section 9 checklist

1. How does a PoC differ from a purchase or a licence?

A PoC shows that a technology or solution works in the customer's environment against agreed criteria. A pilot is usually slightly larger: real use in a limited area such as one branch or one department. The label matters less than the wording. A court or the parties will read intention from the text and from what both sides did, and Civil and Commercial Code section 368 provides that contracts are interpreted according to the intention in good faith, having regard to custom.

PointPoC or pilotPurchase or licence
PurposeShow it works to agreed criteriaContinuing live use
DurationShort, fixed end dateContract term
Scope of useLimited: few users, sample dataFull, as agreed
Obliges purchase?No, unless statedYes, as agreed
Warranty and liabilityUsually narrow; system is a trial systemAs in the main contract

State in the first paragraph that the trial is not an order, is not a licence for live use and does not oblige either party to enter a main contract. If you do want a specific commitment, for example the vendor holds a price if the customer buys within a set time, write it as a separate clause with its conditions.

2. What scope and pass criteria should be agreed?

Scope and pass criteria are the core of the agreement, because they decide at the end whether the trial succeeded. Agree them in writing before starting, not after seeing the results.

  • What is tested: which functions, modules or processes, and what is out of scope
  • Environment: whose system (vendor, customer or cloud) and who looks after connections
  • Users and test data: how many, which department, which data set
  • Pass criteria: measurable indicators, target values, how measured and the data set used
  • Decision maker: who says pass or fail, and within how many days of the end, in writing
  • Customer inputs: data, access, test staff, by what dates, and how time is counted if the customer is late
  • Scope changes: agreed in writing before the work is done
Risky wordingClearer wording
The system works wellThe system reads the 200 agreed sample invoices and extracts the data correctly at no less than the rate set in the annex
The customer is satisfiedTest users complete all 10 scenarios on the test list within the set time
It responds quicklyAverage response time does not exceed the stated value in the stated test window, measured from system logs

The figures above are examples of drafting only. Actual values depend on the system and the business. If a criterion cannot be measured by the end of the trial, agree the method before starting or drop it.

3. How long, and who pays for what?

Duration: state exact start and end dates, not "until finished", and make trial rights end automatically on the end date. If an extension is needed, use a short letter signed by both sides with the new end date and the reason.

Costs: a PoC is not always unpaid, although many are run at no charge to the customer. In some the vendor charges nothing for the trial, in some the customer pays set-up or team time, and in others the trial fee is credited against the price if the customer buys. What matters is writing down who bears each item.

ItemQuestion the contract must answer
Vendor team timeVendor bears it, hourly, or fixed within the scope
Infrastructure and cloudWho pays and is there a cap
Travel and equipmentWho pays and is prior approval needed
Out-of-scope workHow it is charged and whether it needs agreement first
Crediting trial fees against the priceWhether credited and until when
TaxInvoices and VAT on anything charged: have an accountant or auditor check

If the vendor charges nothing, say the trial is provided at no charge only for the stated scope and period, and that use beyond them is not included. That prevents the assumption that no charge at first means no charge later. Pricing models and subscription terms are in SaaS pricing models and subscription contracts.

4. Test data: what to do if it includes personal data

If the trial uses data that identifies people, such as names, phone numbers, customer histories or employee data, Thailand's personal data protection law is engaged. The following is a plain-words overview; details should be checked on the PDPC website (pdpc.or.th) and with an adviser for the actual case.

  1. Use real data only as far as needed. If synthetic data or data with names and identifiers removed will do, choose that first. De-identified data that can still be traced back to a person may remain personal data.
  2. The customer needs a lawful basis and must tell the data subjects what the data is used for. Giving data collected for one purpose to an outside party to test a system may go beyond what was originally notified, so check first.
  3. The tester is usually a processor for the customer. A data processing agreement should say the data is used only on the customer's instructions, kept secure, reported if there is a breach, and deleted or returned at the end.
  4. Sensitive data such as health data should be avoided in a trial. If it must be used, a stricter legal basis needs checking.
  5. Sending data abroad, for example to a cloud or development team overseas, needs the cross-border transfer rules checked first.
  6. Customer data must not be used to train models or improve the vendor's product unless the customer clearly permits it in writing.

Data that is not personal but is confidential to the customer, such as price formulas or supplier lists, also needs limits on use in the contract. The wider PDPA programme is in the PDPA compliance checklist.

5. Who holds rights in test results and work created during the trial, and what stays confidential?

Four groups of things usually arise during a trial. Each should have a clear owner.

ItemSuggested approach
Vendor's existing system, software and technologyStays with the vendor. The customer gets a trial right only: no decompiling, copying or showing to the vendor's competitors
Customer's data and documentsStay with the customer. Vendor uses them only for the trial
New work created during the trial, such as connectors, scripts and configurationChoose one: vendor keeps rights and lets the customer use them if it buys, or assigns to the customer, or joint use
Reports and test resultsSay which side may use them externally, for example as a reference or in publicity

New work is the point usually not thought of at signing. For work the vendor develops specially, rights as a general rule begin with the creator and move or are licensed only by clear agreement. Say which rights are assigned and which are only licensed, and how the work may be used if the customer does not buy. Who owns code and how it is delivered is in software development contracts and source code. Protection of formulas, methods and internal information as trade secrets is in patents, petty patents and trade secrets.

Confidentiality: put a confidentiality clause in the PoC itself or attach an existing NDA covering what each side sees during the trial: system architecture, results, prices and customer data. State how long confidentiality lasts after the end and the usual exceptions, such as information already public or disclosure required by law or an authority. Poor results are confidential too. If this is not written, one side may speak about them publicly.

Competition point: if the buyer is trialling several vendors, agree that the buyer will not show one vendor's results or what it saw to another.

6. How does a trial become unpaid full deployment?

This is mainly a vendor risk, but buyers carry a different one: being told they agreed to buy. Four causes are common.

  1. No real end date. The system stays on after the deadline and staff use it day to day.
  2. Scope creeps. Ten users become a hundred, sample data becomes all real data, with no written change.
  3. Pass criteria are vague. One side says it passed and moves on, the other says it did not and wants fixes without further payment.
  4. Messages and conduct mix. An email saying "let's start live use" or opening a live account can be cited as evidence of a move to purchase.

Practical protections:

  • Make trial rights end automatically on the end date, without notice.
  • Close the account or set it to read-only on the actual end date. Do not let use continue out of courtesy.
  • State that use after the end date is not agreement to buy, and that buying requires a signed main contract or purchase order first.
  • Attach the list of permitted users and scope as an annex, and widen it only by signed letter.
  • If the customer wants to carry on during negotiation, sign an extension letter stating it is a continued trial and not a purchase.
  • Approve changes through the agreed channel, not informal messages.

Who may sign for a company and internal approvals are in contract review and approval in a company without a legal department. If one side starts using the system as if it had bought, the other should say in writing quickly that it is still a trial.

7. What happens at the end: buy, extend or walk away?

A good agreement sets three routes in advance and says who must do what within how many days.

RouteWhat to write in advance
BuyBuyer's written notice within how many days of the report; how long the vendor holds key terms (if agreed); crediting of trial fees; which main contract applies; moving configuration and data into the live system
ExtendHow many times; a letter signed by both sides each time; whether criteria or scope change
Walk awayDelete or return customer data, close access, return or destroy confidential material, vendor stops using customer data, written confirmation within how many days, and how long confidentiality continues

If the parties part: where the agreement or the law gives a right to rescind, rescission is made by notice to the other party, and once a party has rescinded each must restore the other to the former position, under Civil and Commercial Code sections 386 and 391. In practice write more detail than the law: what is returned, how deletion is done and who issues the confirmation, because once data sits in cloud storage or backups, restoring the former position is not simple.

Caution: ending a PoC for failing the criteria should follow the written terms, with a report and an end within the agreed time, not by going silent.

8. Hypothetical example: a software company trials a document-reading system for a manufacturer

This is a hypothetical example for explanation only, not a real case. All figures are illustrative.

Assumed facts: Company A makes software that reads invoices automatically. Company B is a manufacturer interested in it. They agree a six-week trial at no charge, with five test users in the accounts department.

When nothing was written: B sends a full year of real invoices containing employee names and supplier data into the system. After six weeks the users grow to twenty and process live work. A's sales team does not object because it hopes B will buy. Three months later A sends a quotation. B replies that it has been using the system and never agreed to pay. Neither is sure whether the data must be deleted or who owns the customisation A built for B.

When it was written:

  • Scope: 300 sample invoices with personal names removed, and five users
  • Pass criteria: core data read correctly at no less than the rate in the annex, decided by B's accounts manager within seven days of the end
  • Duration: six weeks, rights lapse automatically on the stated date, account closed that day
  • Costs: A bears team time, B bears the cost of connecting to its own system, and if B buys A credits the agreed portion against the price
  • Data: de-identified data, A acts as processor on B's instructions, no model training
  • Rights: A's software stays with A, the data stays with B, the connector built specially stays with A and B may keep using it if it buys
  • Ending: B tells A in writing within 14 days whether to buy, extend or end. If it ends, A deletes the data and confirms in writing within 30 days. Confidentiality lasts two years

The result is that even if B does not buy, both sides know what happens next, and A does not end up working for a customer who keeps using the system without a contract.

9. Checklist before signing a PoC agreement

  • States clearly that this is a trial, not an order or a licence for full use
  • Sets scope, users, environment and what is out of scope
  • Pass criteria are measurable, with the method, the data used and the decision maker
  • Start date, end date and an extension mechanism that needs a signed letter
  • Each cost allocated to a party, plus crediting of trial fees against the price
  • Knows whether the data includes personal data, has a lawful basis, and has a data processing agreement if needed
  • Customer data may not be used beyond the trial, including for model training
  • Separates rights in existing assets, data, new work and test reports
  • Confidentiality clause with duration and exceptions
  • Exit steps for buy, extend or walk away, with dates
  • Method for deleting or returning data and a written confirmation
  • Signatory has authority, and the permitted user list is an annex
  • Emails and meeting notes confirming it is still a trial are kept

Common misunderstandings

  • "It is just a trial, no contract needed." Not necessarily so. The less is written, the more the parties can disagree about what is already binding. A trial involving customer data, confidential information and development work should be documented.
  • "If someone has used the system, they agreed to buy." It should not be so where the agreement says it is a trial. But if the wording is unclear and full use continues without the vendor objecting, the other side may argue conduct, so close access on schedule.
  • "No charge this time means no conditions are needed." Not charging does not remove customer data, confidentiality or rights in work. The conditions are the same.
  • "Results automatically belong to whoever paid, or whoever did the work." There is no fixed rule on who owns results and work created during a trial. It depends on the contract and the nature of the work, so write it down.
  • "Data with names removed is definitely not personal data." If it can still be linked to a person using other data, caution is still needed. Check before giving testers access.
  • "If the customer does not buy, the vendor can keep the data to improve its product." Not unless the customer permits it in writing, and the personal data protection law may not allow use beyond the purpose notified.

Limits of this guide: this page does not cover a full software development contract, subscription pricing or an internal business-model trial, each of which has its own page. The answer can change where the trial involves sensitive data, cross-border transfers, public-sector customers or products that need a specific licence. Information as at 21 November 2026.

Further reading

A good PoC agreement tells both sides in advance what is tested, when it passes, who pays what, who owns the data and results, and what happens at the end, so the trial finishes as a purchase, an extension or a clean exit and never as continued use with no contract.

We draft and review trial and pilot agreements for technology vendors and for buyers, including the data, confidentiality and ownership terms. We are not a technical adviser or system auditor, not an accountant or tax adviser, and cannot promise the outcome of a negotiation or of the test results. Fees depend on the stage of the matter and the work needed. Send us your documents first and we will give you the scope of work and fees in writing before we start. Call +66 92 254 2045 or send us the details. See also contracts and documents and intellectual property.


This guide is published by Suwanvara Law Firm — a Khon Kaen law firm established in 1986. General information only, not legal advice on a specific matter.

Frequently asked questions

How does a PoC agreement differ from a purchase or licence?+

A PoC lets one party try a system within limited scope and time to see whether it meets agreed criteria. It is not an order and not a full licence. The agreement should say expressly that the trial does not oblige either side to buy or sell and gives no right to use the system in live operations.

How should PoC pass criteria be written?+

As things that can be measured and repeated, for example the system correctly processes an agreed sample data set at an agreed accuracy, or responds within an agreed time. Say who decides and which data set is used. Words such as works well or satisfied are poor criteria because each side reads them differently.

What if the customer keeps using the trial after it ends without paying?+

Set a clear end date, make trial rights lapse automatically on that date without notice, close the account or access on that date, and state that continued use is not an agreement to buy. The vendor should actually switch access off, because letting use continue without objection can let the other side argue that an agreement arose from conduct.

Can real customer data containing personal data be used for testing?+

Yes, but there must be a lawful basis and the data subjects must be told the purpose under the personal data protection law. The tester is usually a processor acting for the customer, so a data processing agreement is advisable, data should be limited to what is needed, and de-identified or synthetic data is preferable where possible.

Who owns test results and work developed during a PoC?+

It depends on the contract. If the contract is silent, disputes arise over whether results, prototype code or customisations belong to the vendor, the customer or both. Separate each side's existing assets, newly created work, the customer's data and the test report, including who may use the report.

What must happen to data and deliverables if the customer does not buy?+

The agreement should require the tester to delete or return customer data, close access, return or destroy confidential material and confirm this in writing within an agreed number of days. Confidentiality should continue for an agreed period after the trial ends.

Lawyer-client handshake symbolizing trust at Suwanvara Law Firm

Ready to hear your story

Get an initial consultation with one of our experienced attorneys.