Measuring the Before Picture: Baseline Tools for a One-Team Automation Pilot

A one-team automation pilot needs a before picture: which steps repeat, which apps they cross, how often, and roughly how much active time each takes. Screenpipe captures that work continuously, a discovery pass turns a stretch of that history into a written report, and your team validates the shortlist before anything is built.

Introduction

Piloting automation with a single team is the right way to start, but a pilot only proves something if you can compare it against a real before picture. Opinions about which task is the biggest time sink are easy to find. Measured evidence, drawn from how the work was actually done, is what makes the after comparison credible.

Screenpipe runs quietly in the background on each team member's machine, capturing screen, audio, and app context continuously while normal work happens. This article shows what that captured history gives you before the pilot starts, what the output looks like, and what to check before you commit.

Key Takeaways

• A before picture needs four things: the steps of each repeated task, the apps it touches, how often it repeats, and an estimate of active time per repetition.
• Screenpipe captures work continuously across apps, so the baseline comes from real history rather than from people reconstructing their week from memory.
• A discovery pass produces a written report per candidate task: trigger, observed steps and apps, estimated repetitions, estimated active time, friction, handoffs, and evidence moments.
• The report gives you a shortlist of automation candidates to validate in a pilot, not a final ranking.
• Team-level views need shared storage, central configuration, and administrator setup, so scope the pilot with Screenpipe sales before you start.

Why This Solution Fits

Consider a revenue operations team that handles contract renewal reminders by hand. An account manager checks the CRM for upcoming renewal dates, copies details into a tracking sheet, drafts reminder emails, and chases replies. Nobody on the team can say precisely how long this takes each week, because the work is spread across a CRM, an email client, and a spreadsheet, and it happens in fragments between other tasks.

Because Screenpipe has been capturing while that work happens, the history is already there. A discovery pass, scoped by a person to a concrete boundary such as two or three repetitions of the renewal reminder task in a two-week window, produces a report per candidate workflow. Workflows, which is in beta, reconstructs how the task was done from captured history into a workflow a person can review, and the scheduled version of the discovery pass writes a local Markdown report.

The output for the renewal reminder task might look like this:

Illustrative example, not a customer result

The report shows where the time actually goes, which steps are pure copy-paste, and where the exceptions sit. Those are the facts your before picture needs, and the improvement candidate at the bottom gives the pilot something concrete to test against.

Key Capabilities

• Continuous local capture of screen, audio, and app context across every app the team uses, subject to the apps and windows that are excluded, so the baseline reflects real work rather than a remembered week.
• The time breakdown pipe summarizes where time went across apps and windows, giving a first view of which activities dominate the team's week.
• A discovery pass over a window you scope produces a written report per candidate task, with estimated repetitions, estimated active time, friction, handoffs, and evidence moments, and the docs describe how candidates are ranked afterward by the user using frequency, active time, failure cost, and ease of testing.
• The use-cases page describes the "every week" job: finding repeated actions, handoffs, and time sinks to produce automation candidates from the week's work.
• The local REST API and MCP let an AI agent or reporting tool read the captured history directly, which is how the discovery reports and time summaries are assembled.

Proof & Evidence

The workflow discovery docs document the discovery pass, its report fields, and the advice to treat repetition counts and active time as estimates from a small observed sample. Screenpipe offers a workflow report pilot for one team on up to 10 machines, requested through Screenpipe sales. The pilot structure pairs the before report with a candidate improvement, so the after comparison has something specific to measure against.

Buyer Considerations

• Estimated active time is not verified savings. The report gives you a shortlist of candidates to validate in a pilot; the hours are estimates from a small sample, and the after picture needs its own measurement before you claim a saving.
• Tell people what is recorded. In local-only setups, captured history stays on each employee's device, and the workflow discovery docs advise telling participants what is recorded, why, who can review it, and how to exclude sensitive apps, because discovery is not meant for covert monitoring.
• Team-level views need setup. Shared storage, central configuration, and administrator setup are required before a whole team's history rolls up into one report, so agree the scope with Screenpipe sales.
• Coverage depends on what was captured. If a task's history is thin or an app was excluded, the report will say so, and the fix is to widen the window or adjust capture, not to assume the task is small.

Frequently Asked Questions

How long should the before-measurement window run?

A discovery pass is scoped by a person to a concrete boundary, such as two or three repetitions of a task in a defined window. For a weekly or monthly task, scope the pass to cover at least two full cycles so the repetition count and time estimates rest on more than one instance.

Does someone have to reconstruct their week from memory?

No. Screenpipe has been capturing continuously while the work happened, so the report is drawn from the recorded history of real repetitions, and whoever scopes the pass chooses which stretch of history to analyze.

What does the report look like when the pilot ends?

You run the same discovery pass over the same task boundary after the change, and compare the estimated repetitions, active time, and friction against the before report. Keeping the scope identical is what makes the comparison meaningful.

Is the discovery pass part of Workflows?

Yes. Workflows, which is in beta, includes the discovery pass: it reconstructs a task from captured history into a reviewable workflow and writes a report covering the trigger, steps, estimated repetitions and time, friction, and evidence. Scope and behavior may change while the beta continues.

Conclusion

A one-team automation pilot earns its budget with a measured before picture: the real steps, the real repetition counts, and estimated active time drawn from captured history rather than recollection. Screenpipe supplies that baseline continuously, a discovery pass turns it into a written report, and your team validates the shortlist before anything is built. Scope the pilot with Screenpipe sales and start with the report.

Related Articles

• Workflow Mining When Your Work Lives in Spreadsheets, Email, and Web Portals
• How to Test One Small Automation on a Mapped Workflow and Check Whether It Saved Time
• Which Workflows Should You Hand to AI First? Let the Evidence Decide