Skip to content

POC success criteria templateRun a POC your buyer signs off.

A free Google Sheets workbook that takes every POC from kickoff to a signed readout, plus 70 measurable success criteria your buyer can accept before day one.

Free to use and share. No sign-up. Google Sheets opens it as a copy you own.

Success criteria

1 of 3 accepted by the buyer

  • SEC-01

    Users sign in through the buyer's identity provider ([Okta]) with SAML or OIDC single sign-on.

    AcceptedMust have
  • INT-01

    Two-way sync with [Salesforce] keeps [opportunities and contacts] current within [15] minutes.

    In reviewMust have
  • FUN-01

    A pilot user completes [primary workflow] end to end without vendor help in under [10] minutes.

    Not sentNice to have
The Success criteria tab, with the workbook's example rows.
Inside the POC workbook

Ten tabs, kickoff to signed readout.

Every tab answers a question that stalls POCs when nobody writes it down. The tabs run in the order a POC does.

  1. 01

    Start here

    How to use the workbook, the status key and a link to the criteria library.

  2. 02

    Overview

    The POC on one page: owners, milestones, objectives, scope and the next step you agree before day one. Progress counts fill in as you work.

  3. 03

    Stakeholders

    Everyone who influences the decision on both sides, what they care about and whether they can sign.

  4. 04

    Users

    Everyone who logs in, with access and training confirmed before testing starts.

  5. 05

    Success criteria

    Each criterion with its use case, how it's measured, priority, tester and the buyer's acceptance, plus status and evidence.

  6. 06

    Plan

    A mutual action plan with 15 starter tasks, each with an owner, a due date and its dependencies.

  7. 07

    Environment and access

    The 14 access, security and legal items that stall POCs, cleared in week one.

  8. 08

    Issues and gaps

    Every blocker and product gap, tied to a criterion, with an owner and a written answer.

  9. 09

    Weekly check-ins

    One row per check-in: progress against criteria, blockers, decisions and next steps.

  10. 10

    Readout and sign-off

    Met or not met for every criterion, the decision and sign-off from both sides.

Write criteria that get signed

A POC without accepted criteria has no finish line.

The buyer keeps testing, new requirements show up in week three and the decision slips a quarter. Criteria your buyer accepts in writing before day one turn the POC into a test you can win, and the readout into a decision.

Weak

The CRM integration works well.

Signable

Two-way sync with Salesforce keeps opportunities and contacts current within 15 minutes, checked on 20 test records.

  • Specific

    It names the workflow, system or data it covers.

  • Measurable

    It has a number, a time limit or a clear pass or fail.

  • Tied to discovery

    It maps to a use case the buyer told you matters.

  • Owned

    Someone on the buyer's side tests it and confirms the result.

  • Accepted in writing

    The buyer agrees to the exact wording before the POC starts.

How to use the template

Accepted criteria before kickoff, in five steps.

  1. Step 1

    Pick your criteria

    Choose the criteria from the library that map to your buyer's objectives. Keep the list tight enough that everyone tracks every one.

  2. Step 2

    Fill in the brackets

    Replace everything in [brackets] with the buyer's systems, numbers and dates.

  3. Step 3

    Set the priority

    Mark each criterion must have or nice to have, so the readout has a clear bar.

  4. Step 4

    Paste them into the workbook

    Copy each ID and its wording into the Success criteria tab, and name a tester on the buyer's side.

  5. Step 5

    Get them accepted

    Send them to your champion for acceptance before kickoff. Change one later, and it goes back for acceptance.

The Success Criteria Library

70 POC success criteria, ready to copy.

Ten categories, each criterion with an ID you can paste into the workbook and the evidence to collect. Replace the [bracketed] text with your buyer's details.

Copy the library as a Google Doc
Business outcomes (OUT, 7)Prove the value your champion will take to the economic buyer.
  • OUT-01

    Time spent on [process] drops from [baseline] to [target] for the pilot group over [X] weeks.

    Evidence: Baseline and pilot time logs

  • OUT-02

    The pilot team runs [X] real [transactions, cases or projects] through the solution, using test data only for setup.

    Evidence: Record counts from the solution

  • OUT-03

    The champion can present a business case to [economic buyer] with baseline and pilot results side by side.

    Evidence: Business case reviewed by the champion

  • OUT-04

    At least [X]% of pilot users rate the new process better than the current one.

    Evidence: End-of-POC survey

  • OUT-05

    The solution replaces [tool or spreadsheet] for the pilot workflow, with no parallel tracking by week [X].

    Evidence: Champion confirms the old tool is retired for the pilot

  • OUT-06

    Projected annual savings or revenue impact, calculated from POC data, reaches at least [$X].

    Evidence: ROI model built on pilot data

  • OUT-07

    The economic buyer attends the readout and confirms the results support a decision.

    Evidence: Readout attendance and decision notes

Core workflows (FUN, 8)Prove the product does the job users are buying it for.
  • FUN-01

    A pilot user completes [primary workflow] end to end without vendor help in under [X] minutes.

    Evidence: Timed run by [X] users

  • FUN-02

    The solution handles [scenario from discovery] using the buyer's own data.

    Evidence: Live run with buyer data

  • FUN-03

    [X] of [Y] must-have requirements are met through configuration, with no custom code.

    Evidence: Requirements checklist signed by the evaluator

  • FUN-04

    Approvals follow the buyer's routing rules, including [exception case], with no manual workaround.

    Evidence: [X] test approvals routed correctly

  • FUN-05

    Users find any [record type] by [fields] in under [X] seconds.

    Evidence: Timed searches across [X] records

  • FUN-06

    The solution handles [edge case, such as multiple currencies, business units or regions] correctly in [X] of [X] test runs.

    Evidence: Test log with results

  • FUN-07

    Bulk actions (update, assign, close) work on [X] records at once.

    Evidence: Bulk test on [X] records

  • FUN-08

    Notifications reach the right people in [email, Slack or Teams] within [X] minutes of the trigger.

    Evidence: Timestamps on [X] test events

Integrations and data (INT, 9)Prove it fits the buyer's systems without breaking them.
  • INT-01

    Two-way sync with [system] keeps [objects] current within [X] minutes.

    Evidence: Changes on [X] records checked in both directions

  • INT-02

    The buyer's admin connects [system] in under [X] hours using the vendor's documentation.

    Evidence: Admin completes setup, time logged

  • INT-03

    Historical data from [system] ([X] records, [X] years) imports with [X]% field accuracy.

    Evidence: Sample of [X] records compared to the source

  • INT-04

    Field mapping covers all [X] required fields, including custom fields [list].

    Evidence: Mapping sheet approved by the data owner

  • INT-05

    Data entered in the solution reaches [downstream system or BI tool] within [X] minutes.

    Evidence: Timestamps on [X] test records

  • INT-06

    The buyer's developer makes a working API call for [operation] within [X] hours using the public documentation.

    Evidence: Developer confirms a working call

  • INT-07

    A failed sync appears in the admin log within [X] minutes, with a clear error and a way to retry.

    Evidence: Deliberate failure test

  • INT-08

    The buyer can export all of its data in [CSV, API or other format] without vendor involvement.

    Evidence: Full export completed by the buyer's admin

  • INT-09

    Webhooks or events for [events] reach [system] in [X] of [X] tests.

    Evidence: Event delivery log

Security and compliance (SEC, 10)Clear the security review early, before it stalls the decision.
  • SEC-01

    Users sign in through the buyer's identity provider ([Okta, Entra ID or Google]) with SAML or OIDC single sign-on.

    Evidence: Admin and [X] users sign in through SSO

  • SEC-02

    Adding or removing a user in [identity provider or SCIM] takes effect in the solution within [X] minutes.

    Evidence: Provisioning and deprovisioning test

  • SEC-03

    Role-based permissions restrict [sensitive data] to [roles].

    Evidence: Test with one user in each role

  • SEC-04

    The vendor provides a current SOC 2 Type II report or ISO 27001 certificate.

    Evidence: Report reviewed by the security team

  • SEC-05

    The vendor completes the buyer's security questionnaire by [date].

    Evidence: Completed questionnaire

  • SEC-06

    Data is encrypted in transit (TLS 1.2 or higher) and at rest.

    Evidence: Vendor documentation reviewed by security

  • SEC-07

    Customer data is stored in [region], and the vendor lists its subprocessors.

    Evidence: Data residency statement and subprocessor list

  • SEC-08

    Audit logs record [logins, permission changes, exports and deletions] with the user and time, and admins can export them.

    Evidence: Sample audit log export

  • SEC-09

    Retention and deletion settings meet the buyer's policy, including deletion of POC data if the buyer doesn't proceed.

    Evidence: Policy comparison signed off by security

  • SEC-10

    The buyer's security team signs off by [date] with no open high-severity findings.

    Evidence: Security sign-off in writing

Administration (ADM, 6)Prove the buyer's team can run it without you.
  • ADM-01

    The buyer's admin adds a user, assigns a role and removes access without contacting the vendor.

    Evidence: Admin completes all three tasks

  • ADM-02

    The buyer's admin changes [workflow, field or form] without code in under [X] minutes.

    Evidence: Timed configuration change

  • ADM-03

    Changes can be tested in a sandbox before they reach production.

    Evidence: Sandbox change promoted to production

  • ADM-04

    Fields, picklists and labels match the buyer's own terms for [objects].

    Evidence: Configured screens reviewed by users

  • ADM-05

    Admins can see who changed which setting and when.

    Evidence: Configuration history

  • ADM-06

    The solution supports [X] teams or business units with separate settings and shared reporting.

    Evidence: Two units configured and reported on

Performance and reliability (PRF, 6)Prove it holds up at the buyer's scale and on the buyer's network.
  • PRF-01

    Key pages load in under [X] seconds with [X] users working at once on the buyer's network.

    Evidence: Load timings from [X] locations

  • PRF-02

    The solution handles the buyer's projected volume of [X records or transactions per day] with no errors.

    Evidence: Load test results

  • PRF-03

    The vendor commits to at least [99.9]% uptime with service credits and publishes its status history.

    Evidence: Contract SLA and public status page

  • PRF-04

    [Workflows] work on [iOS and Android] for field users.

    Evidence: [X] field users test on their devices

  • PRF-05

    The solution works through the buyer's firewall, proxy and VPN with documented allowlisting only.

    Evidence: Access test from the corporate network

  • PRF-06

    The vendor documents backup and recovery targets of [X] hours or better.

    Evidence: Recovery objectives in writing

Usability and adoption (USR, 6)Prove people will actually use it.
  • USR-01

    [X]% of pilot users log in at least [X] times a week during the POC.

    Evidence: Usage report

  • USR-02

    New users complete [core task] on their own after a [X]-minute training session.

    Evidence: Observed task completion

  • USR-03

    Pilot users rate ease of use at least [X] out of 5.

    Evidence: End-of-POC survey

  • USR-04

    The solution meets [WCAG 2.1 AA] accessibility.

    Evidence: Vendor VPAT or the buyer's own testing

  • USR-05

    The interface is available in [languages] for [regions].

    Evidence: Users test in each language

  • USR-06

    In-app help answers [X] of [X] common pilot questions without a support ticket.

    Evidence: Question log

Reporting and analytics (RPT, 6)Prove leaders get numbers they trust.
  • RPT-01

    The [executive or team] dashboard shows [metrics] within [X]% of the buyer's source of truth.

    Evidence: Side-by-side comparison

  • RPT-02

    A business user builds a new report on [question] without help in under [X] minutes.

    Evidence: Timed report build

  • RPT-03

    Reports filter by [team, region, segment and date] and respect each viewer's permissions.

    Evidence: Test with two different roles

  • RPT-04

    Scheduled reports arrive by [email or Slack] on [cadence].

    Evidence: Reports received on schedule

  • RPT-05

    Reports reflect changes within [X] minutes.

    Evidence: Timestamped change test

  • RPT-06

    The buyer can reproduce [KPI] and gets the same result as its current method.

    Evidence: KPI calculations compared

AI and automation (AI, 6)Prove the AI is accurate, controlled and approved.
  • AI-01

    Reviewers rate AI-generated [summaries, fields or drafts] accurate in at least [X] of [X] samples from real data.

    Evidence: Scored sample set

  • AI-02

    A person reviews AI output before it changes a record or reaches a customer.

    Evidence: Workflow walkthrough

  • AI-03

    Customer data isn't used to train the vendor's or any third party's AI models.

    Evidence: Contract or DPA language

  • AI-04

    AI runs on a provider the buyer's AI policy approves, including the option to use the buyer's own account.

    Evidence: Provider settings checked against policy

  • AI-05

    Admins can turn AI features off for the whole organization.

    Evidence: Admin turns AI off and back on

  • AI-06

    Automations triggered by [event] run correctly in [X] of [X] tests and are logged.

    Evidence: Automation run log

Support and partnership (SUP, 6)Prove the vendor shows up after the contract is signed.
  • SUP-01

    The vendor answers POC support requests within [X] business hours.

    Evidence: Ticket timestamps

  • SUP-02

    A named technical lead attends every weekly check-in and owns open issues.

    Evidence: Check-in attendance

  • SUP-03

    The vendor delivers a rollout plan with timeline, roles and effort by [date].

    Evidence: Implementation plan

  • SUP-04

    Every product gap found in the POC gets a written answer: a workaround, a roadmap date or no plan.

    Evidence: Gap log with responses

  • SUP-05

    The vendor provides [X] reference customers in [industry or company size] by [date].

    Evidence: Reference calls completed

  • SUP-06

    Total cost over [X] years, including implementation, training and support, is documented and within [budget].

    Evidence: Cost breakdown approved by finance

From spreadsheet to Deal Room

Put your buyer inside the POC with you.

The workbook gets every POC started right. The PresalesIQ Technical Deal Room gives each engagement a branded room where your buyer accepts each criterion exactly as written, signs off every stage and works the mutual action plan with your team. Every agreement is recorded with who and when.

POC success criteria questions, answered

What is a POC success criteria template?

A ready-made structure for writing and tracking the tests a proof of concept must pass. Each criterion states what will be proven, how it's measured, who tests it and whether the buyer has accepted it, so the readout ends in a decision.

What should POC success criteria include?

Each one should name a specific workflow, system or data set; have a number, time limit or clear pass or fail; map to a use case from discovery; have a tester on the buyer's side; and carry the buyer's written acceptance of the exact wording before the POC starts.

Is the POC workbook free?

Yes. The POC workbook and the Success Criteria Library are free to use and share, with no sign-up. Open the workbook link and Google Sheets makes a copy you own.

Who should accept POC success criteria?

Your champion accepts each criterion as written before kickoff, and a named tester on the buyer's side confirms each result. If a criterion changes after it's accepted, it goes back to the buyer for acceptance again.

Can my buyer accept success criteria online instead of in a spreadsheet?

Yes. In the PresalesIQ Technical Deal Room, buyers sign in with an invite link and a one-time email code, accept each criterion as written and sign off each POC stage, with every agreement recorded with who and when.

Every POC, signed off on the record.

See how PresalesIQ runs POCs from success criteria to readout, with your buyer in the room. Thirty minutes is all it takes.