wowprompt

Proof of concept success plan agreed with a B2B buyer

Writes a short proof of concept plan for a business software or service trial: the buyer's problem, measurable success criteria agreed in advance, scope, timeline, responsibilities on both sides and what happens if the criteria are met. Use it before agreeing to a free trial or pilot for an enterprise deal so it ends in a decision, not a drift.

A one-page POC plan with three to five measurable success criteria, scope in and out, a week-by-week timeline, owners on both sides and the agreed decision step
The output this prompt produced, unedited.

The prompt

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

  1. Objective in two sentences, in the buyer's words.
  2. | Success criterion | Baseline today | Target | How it is measured | Who measures |, three to five rows.
  3. Scope: in scope and out of scope, as two lists.
  4. Week-by-week timeline with setup, test, review and decision dates.
  5. Responsibilities: what the vendor provides, what the buyer provides, such as data, access and a named contact.
  6. Decision step: who decides, on what date, and what happens if the criteria are met, partly met or missed.
  7. 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.
proof of conceptpoc success criteriaenterprise sales trialb2b pilot plansales evaluationdeal closing

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity