Fill in these first
- Your product or service: [e.g. invoice automation software]
- Buyer company type and team: [e.g. a logistics company, finance team of 12]
- Problem the buyer wants solved: [from discovery notes]
- What they will test: [e.g. processing 500 supplier invoices from two branches]
- Length of the trial: [e.g. four weeks]
- Buyer contacts by role: [e.g. finance controller, IT lead, CFO as approver]
- Commercial terms if successful: [e.g. annual plan placeholder, or to be agreed]
Task
Write a proof of concept plan both sides can sign off in one meeting.
Output format
- Objective in two sentences, in the buyer's words.
- | Success criterion | Baseline today | Target | How it is measured | Who measures |, three to five rows.
- Scope: in scope and out of scope, as two lists.
- Week-by-week timeline with setup, test, review and decision dates.
- Responsibilities: what the vendor provides, what the buyer provides, such as data, access and a named contact.
- Decision step: who decides, on what date, and what happens if the criteria are met, partly met or missed.
- Risks that could stall the trial and how each will be handled.
Example criterion
"Invoices processed without manual correction: baseline 0 percent, target 80 percent, measured from the trial system report, checked by the finance controller."
Rules
- Every criterion must be a number or a yes or no; no "users are happy".
- Keep scope small enough to finish in the time given.
- Do not promise results the inputs cannot support.






