---
title: "Proof of Value"
canonical_url: "https://flowfuse.com/handbook/sales/meetings/pov/"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

## Proof of Value

A Proof of Value (PoV) is the stage where FlowFuse and the prospective customer
jointly prove that FlowFuse solves the specific problem uncovered during
[Discovery](https://flowfuse.com/handbook/sales/meetings/discovery/) and shown in the
[Demo](https://flowfuse.com/handbook/sales/meetings/demo/). Unlike a generic "kick the tyres" trial,
a PoV is scoped in the [Solution](https://flowfuse.com/handbook/sales/meetings/solution/) stage — the
apps that will solve the use case, the success criteria they are judged against,
and the plan are all agreed before it starts — and it ends in a clear decision.

## Where a PoV fits in the sales process

A PoV is **stage 4 — Validate** of the sales process: the technical heart of the
Evaluation phase, jointly owned by the **AE and SE**. It provides technical
evidence that strengthens the forecast by proving FlowFuse solves the agreed
problem. Deals can qualify for the forecast from Stage 3 when they meet the
[Forecast Deal criteria](https://flowfuse.com/handbook/sales/forecast-review/#forecast-deals).
A **completed installation**
and **technical validation** against the agreed criteria are the exit signals that
carry the deal out of Validate toward Commit.

It runs in three arcs — the same three that shape the [Process](#process) below
and the workbook's **Plan** tab:

<table>
<thead>
  <tr>
    <th>
      Arc
    </th>
    
    <th>
      Sales stage
    </th>
    
    <th>
      What happens
    </th>
  </tr>
</thead>

<tbody>
  <tr>
    <td>
      <strong>
        Pre-PoV
      </strong>
    </td>
    
    <td>
      <a href="/handbook/sales/meetings/solution/">
        Solution
      </a>
      
       (stage 3)
    </td>
    
    <td>
      The gates are produced — use case and value understood, apps and success criteria defined, plan agreed, FlowFuse available (see the <a href="#pre-pov-checklist">
        Pre-PoV checklist
      </a>
      
      ). A PoV should not start until they are.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        PoV
      </strong>
    </td>
    
    <td>
      Validate (stage 4)
    </td>
    
    <td>
      Prove each scoping criterion. Completed installation and technical validation are the exit criteria.
    </td>
  </tr>
  
  <tr>
    <td>
      <strong>
        Post-PoV
      </strong>
    </td>
    
    <td>
      Moving to Commit (stage 5) and Closing
    </td>
    
    <td>
      A successful PoV feeds the business case, Economic Buyer alignment and paper process that carry the deal to close.
    </td>
  </tr>
</tbody>
</table>

A PoV is run from the **PoV Workbook** — the single
document that spans the whole engagement — using the shared
[definitions](https://flowfuse.com/handbook/sales/pov-workbook/#definitions) defined there. This page
covers the PoV stage itself: [where it fits](#where-a-pov-fits-in-the-sales-process)
in the sales process, and the [process](#process) of running one.

## Process

A PoV moves through a small number of phases, all tracked in the workbook's
**Plan** tab: **pre-PoV gates** clear, then **kickoff** (agree the plan and
success criteria, and schedule every check-in and the wrap-up), **install**,
**execute** (prove each scoping criterion in turn), and **wrap-up** (sign-off
against the criteria). The commercial follow-on lives in the **Post-PoV** section
of the same plan.

### Pre-PoV checklist

Before a PoV starts, five things must be true. The first four are the output of
the [Solution](https://flowfuse.com/handbook/sales/meetings/solution/) stage (stage 3) — they are
produced there, not during the PoV — and the fifth is getting access. They are
also the gates tracked in the workbook's **Plan** tab. Starting a PoV before they
are met is the most common way one stalls.

1. **The use case and its business impact are understood.** [Discovery](https://flowfuse.com/handbook/sales/meetings/discovery/) has established the pain and what solving it is worth to the customer.
2. **The apps are defined.** The app or apps that will solve the use case are identified and follow FlowFuse's app delivery methods, so the PoV showcases FlowFuse as an app-building platform — not a test of Node-RED.
3. **Success criteria are well defined.** Each criterion has a concrete, agreed pass signal, so "success" is not open to interpretation when the PoV ends.
4. **The plan is agreed with the customer.** Tasks, owners and dates are agreed jointly, not just internally.
5. **FlowFuse is available to test.** The customer has either installed FlowFuse (self-hosted) or signed up for a Cloud trial — set up as the [FlowFuse Trial Environment](https://flowfuse.com/handbook/sales/flowfuse-trial-environment/) during the Solution stage.

### PoV meetings

Every PoV meeting is scheduled up front, at the kickoff, so the cadence is agreed
and the wrap-up is already on the calendar before any testing begins.

- **Kickoff** — the customer formally agrees to the PoV, the plan and success criteria are confirmed, and every subsequent meeting (the check-ins and the wrap-up) is scheduled. For a self-hosted PoV, this is where the customer receives the [trial license key](#generating-a-license) to install on their own server.
- **Check-ins** — a regular cadence agreed at kickoff. Each check-in reviews progress against the scoping criteria and clears blockers; open items are tracked in the workbook's **Questions** tab between calls.
- **Wrap-up / feedback meeting** — a final session, also booked at kickoff, to review the PoV against its success criteria, capture the customer's feedback, and agree the next step toward Commit.

### Licensing

Getting the customer a running FlowFuse — the
[FlowFuse Trial Environment](https://flowfuse.com/handbook/sales/flowfuse-trial-environment/), a Cloud
trial or a self-hosted install — is set up in the Solution stage. The licensing
tasks the SE performs during the PoV live here. A **license key applies only to
self-hosting**; a Cloud trial never needs one.

A Cloud trial starts on Edge by default, and a platform Administrator can change it to
another package. If a combined trial (eg Hub+Edge) is required, an Administrator can modify the team limits on the Team Settings page to unlock specific features for the team.

Self-hosted can trial any combination of packages based on what the license is configured to enable.

Sales issues trials are recommended to have both Hub and Edge enabled to ensure a client has all required capabilities for a successful PoC phase.

#### Generating a license

- Generate one by [filling out this form](https://energetic-sanderling-4472.flowfuse.cloud/dashboard/license).
- Trial license expiry date should be set for 30 days, even in cases where longer than 30 days may be warranted.
- Tick the packages the customer is evaluating: Hub, Edge or Fleet. At least one is required, and the choice decides which features the key unlocks.
- Include 10 users, 10 teams, and 10 Node-RED instances on the Enterprise Tier.
- Certified nodes are separate from the package. Request them with a [certified nodes request](https://github.com/FlowFuse/CloudProject/issues/new?template=certified-nodes-request.yml) on CloudProject, for a self-hosted or a Cloud customer.

All generated licenses are added [to this sheet](https://docs.google.com/spreadsheets/d/1wM_o8IWjjkwi-WMRueKfS-lrmkQYzV83xm4BIzZNAO0) automatically.

#### Extending a trial

- **Cloud** — use the 'Extend Trial' button on the Team Settings page (platform Administrators only). Without admin access, raise a [CloudProject change request](https://flowfuse.com/handbook/operations/change/#flowfuse-cloud-change-control) with details.
- **Self-hosted** — issue a new license key with a later expiry. Trial extensions need to be approved by management.

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
