> ## Documentation Index
> Fetch the complete documentation index at: https://docs.screenpipe.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Plan a Screenpipe enterprise pilot with a measurable result

> Start with one workflow, a small participating group, and one agreed output.

Start with one workflow, a small participating group, and one agreed output. A pilot should establish capture coverage, output accuracy, operational effort, and useful value before expanding deployment.

## Start here

Choose a workflow owner and reviewer. Agree on participating devices, recording boundaries, data destinations, duration, support contact, and the current commercial terms with your Screenpipe contact.

## Copy this prompt

Use this in Screenpipe chat or an assistant with the required connections. Replace the brackets with your details. If the assistant lacks access, provide a reviewed excerpt; a prompt alone does not connect it to your history.

```text theme={null}
Draft a pilot plan for [workflow] with [participants] over [dates].
Define one output, its reviewer, baseline process, success criteria, capture
coverage checks, privacy boundaries, setup owner, support path, and end date.
Separate measured outcomes from targets. Include setup and review effort.
List unknown deployment, plan, retention, and security requirements for
confirmation. Do not assume a feature or allowance is included in our account.
```

## Check the result

Run the complete path on one device before enrolling the rest. Review a normal example and an exception, then compare measured effort and usefulness against the agreed baseline.

<AccordionGroup>
  <Accordion title="See a worked example" id="worked-example">
    | Dimension   | Example pilot criterion                                       |
    | ----------- | ------------------------------------------------------------- |
    | Coverage    | Each agreed test session is findable on its recording device. |
    | Output      | Reviewer can follow one SOP and recognize its exception.      |
    | Reliability | Missing input creates an explicit no-data outcome.            |
    | Effort      | Setup, review, and correction time are recorded.              |
    | Decision    | Expand, revise, or stop based on reviewed evidence.           |
  </Accordion>

  <Accordion title="Go deeper: setup choices and edge cases" id="details">
    Separate recording-only participation from AI report generation when estimating usage. Ask who runs AI tasks, how often, and which account or provider bears that usage. Do not infer current pricing from an older call or another customer’s contract.

    Give participants a useful output and a clear way to raise recording concerns. A technically successful installation does not establish that people trust or use the workflow. End with a documented decision and owners for remaining issues.
  </Accordion>
</AccordionGroup>

## Continue

[Enterprise device coverage](/enterprise-device-coverage) · [enterprise security review](/enterprise-security-review) · [automation prioritization](/automation-prioritization)