Plan your pilot

One field. Four weeks. License fees only when the metrics move.

Our implementation team scopes your systems, well count and operating metric in one call. The pilot runs on one field’s data, read-only, DataHub included, live in four weeks, with a first read against your signed baseline. Fit-for-purpose. Plug-and-play.

See Your Wells RankedView a Sample 6 AM Plan, no form →

Straight talk on how the pilot is priced

There is no price on this page, on purpose.

A number without your scope would be a guess. What a pilot involves turns on three things we cannot see from here:

  • How many wells are in the field you pick
  • Which systems of record we read from
  • Which modules the pilot runs

Our implementation team scopes all three in one call and puts the plan in writing. The offer itself does not need a number:

The Impact Guarantee. License fees only when the metrics move.

  1. 01

    You pick the metric.

    Cash flow per BOE, OPEX per well, drive miles: the number you already run the field on. The baseline and how it is measured go in writing before week one.

  2. 02

    The 4-week pilot measures it.

    One field, on your data, read-only against your systems of record, measured against the baseline you signed.

  3. 03

    License fees start only if it moves.

    If the number does not move, you walk away. No license fee, no kill fee.

Adoption gates come first, and they are ours to hit, not yours.

A tool the field does not use has no effectiveness to measure. We measure usage and uptime before we ask you to measure anything. Then the number is judged against the baseline you signed before week one, and if it did not move, we say so and you keep the baseline work.

The 4-week pilot

Week 0

The scoping call. You pick the metric. The baseline and how it is measured go in writing.

  1. Week 1Connect read-only to your systems

    Deliverable: Credentials your IT team issues. Data flowing, verified by your team.

  2. Week 2Configure and rank

    Deliverable: Flags tuned to your wells. A ranked plan generated every morning.

  3. Weeks 3 to 4The ranked plan in the field

    Deliverable: Pilot crews run on the ranked plan from week three, all live by week four. Their corrections feed the next ranking.

  4. Week 4Measure the metric you picked

    Deliverable: A first read of your metric against the baseline you signed.

The 4-week pilot, one field, on your data. License fees only when the metrics move.

The pilot plan

What the plan covers, in writing.

A pilot should not be a leap of faith. Before anything is stood up, our implementation team writes the plan down: scope, data, integration, schedule, and the guarantee.

01

A scoping call

Our implementation team walks your operation with you: well count, basins, systems of record, crew structure, and the operating metric you want to move. You leave the call with a written pilot plan.

02

One field's data

The pilot runs on a single field or asset group you pick. Big enough to prove the number, small enough that nobody has to bet the company to see it.

03

Read-only integration

DataHub connects to your SCADA, production accounting, and CMMS read-only. Your systems of record stay authoritative. No rip-and-replace, no data entry.

04

The schedule and the guarantee

The 4-week pilot and the Impact Guarantee terms, both set out above.

Are your best people working on your most valuable work today?

That is the question the pilot answers, on your wells, against your baseline.

We name the metric before week one. We charge when it moves.

How the Impact Guarantee works ↑

The catalog

Eight modules. Your pilot starts with the one that maps to your sharpest pain.

Every module runs on the same backbone: the most sophisticated prioritization engine in the field, fed by DataHub. The scoping call picks the module, the field, and the metric; our implementation team scopes the engagement to your well count and systems. The pilot itself is four weeks on one field, and license fees wait for the metric.

DataHubIncluded

WorkSync DataHub

The integration backbone. Pre-built connectors to your ERP, SCADA, production accounting, and historian: the systems your team already runs. Included with any WellOPS or FlowSync module. Sold standalone too.

Module deep-dive →
WellOPS

Field Data Capture

Gauge sheets, JSAs, hazard observations, equipment inspections, environmental readings. Voice-enabled, offline-capable, one-tap completion. The form fills itself; the field team member confirms what is true.

Module deep-dive →
WellOPS

Field Work Management

Permits, lone-worker check-ins, MOCs, hot work, lockout/tagout, incident investigations, compliance audits. Every job has an owner. Every permit has a clock. Every lone worker has a check-in.

Module deep-dive →
WellOPS

Work Engine

Ranked daily work plan in every truck cab by 6 AM, scored on cash-flow impact and risk. Includes Opportunity Scoring. The brain that decides what your field does today.

Module deep-dive →
WellOPS

Route Optimizer

The most profitable drive day, re-solved when something changes. Not the shortest route. Multi-stop optimization with crew qualifications, priority, geography, and time windows. 35% fewer miles driven, measured across 5,000+ wells in live deployments.

Module deep-dive →
FlowSync

Model Builder

Build the model from PDFs, P&IDs, datasheets, GIS layers, and as-builts you already have. Automatically. The hydraulic model that took weeks of an engineer's time and was six months stale, now minutes of verification and current.

Module deep-dive →
FlowSync

Flow Simulator

Steady-state and transient hydraulic simulation, on live data. Liquids and gas, gathering, transmission, distribution. Interoperates with and feeds the hydraulic simulators your engineers already trust, or runs alongside them. Customer's choice.

Module deep-dive →
FlowSync

Process Simulator

Process simulation for gas processing, dehydration, sweetening, compression, separation, and small-facility design. Full-scale simulation for the everyday work that does not need a full-scale license. Sized for the work that fills your day, not the once-a-decade greenfield.

Module deep-dive →
WellOPS Control Panel from the production build: live activity feed, field map, ranked critical queue, production and deferred-volume panels, and crew tracker
WellOPS Control Room, production build: what the modules above look like running. Product capture. Map and identifying detail generalized for confidentiality.

Paid diagnostic · Results in 14 days

Route Economics Diagnostic

We connect to your data, analyze your routes by cash-flow impact, and hand you the gap and the fix. Fixed scope, agreed in the planning call, no surprises.

See your route economics

The full platform

Both products on one backbone.

WellOPS plus FlowSync plus DataHub plus Willie and Taylor embedded. Most operators land with one module and expand as the metric proves out. Scope the mix with our implementation team.

Talk to Our Team

ROI Calculator

What could WorkSync deliver on your data?

Three inputs, one order-of-magnitude estimate. Put in your numbers and the calculator applies the deployment benchmarks noted below them.

Your operation

Calculation assumes $55 oil. Benchmarks are deployment figures from the multi-basin reference (a top 25 private producer, Western Anadarko + Permian + Wyoming): 10% optimizable production × 15% capture, and a 35% drive-mile reduction at the same production coverage.

Expected annual impact

Free cash flow uplift
$4.5M
per year (at $55 oil)
Drive miles saved
42 / pumper / day
Show Me My Number →

Onboarding walkthrough

See Your Wells Ranked

Prove value on one module. Four weeks to stand up (integrate week one, configure week two, crews live by week four), under the Impact Guarantee: license fees only when the metrics move. Name and work email; the scoping call collects the rest. This same form reaches our implementation team if you would rather start with a conversation than a pilot plan.

The team will reach out within 1 business day and sets a 30-minute working session on your stack.

SOC 2 Type II in progress, report targeted Oct 30, 2026.

Your details go to the implementation team only; no third-party sharing.

Before you commit

See the pilot in context: by basin, by alternative, by module.

By basin

The math in your basin

By alternative

Compare the approaches

By module

Module deep-dives

Before you ask

Frequently asked

What does a pilot plan cover?
Five things, in writing: the scoping call where we map your systems and pick the operating metric, the single field or asset group the pilot runs on, the read-only DataHub integration plan, the 4-week stand-up schedule to crews live, and the Impact Guarantee terms: license fees only when the metrics move.
What is the Impact Guarantee?
License fees only when the metrics move. We agree the baseline and the measurement in week zero, stand up on the stack you already own for four weeks, then take a first read of the number you anchored on at week four (cash flow, OPEX, drive time, study turnaround, whatever you pick). If it moves, we keep going. If it does not, you walk away, no kill fee. Open offer for qualified operators.
How do we justify this internally?
Build the case from a method rather than a projection. First, you and your controller pick one operating metric and write it down before anything is connected: cash flow per BOE, operating cost per well, drive miles, or TRIR. Second, run your own well count, crew count, and drive times through the route economics calculator on this site, which puts a dollar figure on a day of your field capacity using your inputs rather than ours. Third, run the four-week pilot on one field against that single agreed metric, with the baseline set in week zero, so the business case is measured on your wells. The Impact Guarantee carries the commercial risk while that happens: license fees only when the metrics move. What reaches your approver is your own baseline and your own delta, which is the only version of the number that survives a finance review.
Run the route economics calculator on your numbers →
What training does the field need before the first shift?
The app is built for a truck cab at 6 AM in gloves: one screen at a time, offline capable, and it syncs when signal returns. A field team member opens it to a day that is already assembled and already in order, so the first shift is the training. Capture happens at the wellhead, by voice or in a couple of taps, rather than at shift end, and Willie walks a person through a JSA by voice. Every stop carries the reason it is ranked where it is, and any stop can be resequenced or skipped in one tap with a reason code, which keeps local knowledge in charge of the day. The rollout is gated rather than dated: flags tune against the field's own judgment first, and the ranked plan goes into a truck when the crews agree the ranking is right. The measure that matters is whether the plan survives contact with the field, and establishing that on your own crews is what the four weeks are for.
See what the field app asks for →
What does WorkSync cost?
We scope every engagement to your well count, your systems, and the modules you actually need, in a pilot-planning conversation with our implementation team. The DataHub is included with any WellOPS or FlowSync module. The Impact Guarantee applies either way: license fees only when the metrics move, so the four weeks on one field carry our risk, not your budget.
How is the DataHub included?
The DataHub is the integration backbone. It comes with any WellOPS or FlowSync module, and it can also run on its own for operators who want a clean operations data layer first. We make money on the modules that ride on it, so the more we make the backbone work for you, the more likely you are to add modules.
Can I pilot one module without the others?
Yes, and most operators should. Pick the module that maps to your sharpest pain. Run it for four weeks on one field under the Impact Guarantee. Add modules when value proves out.
How fast can we deploy?
The stand-up is four weeks: we connect read-only in week one, configure and rank in week two, and put the ranked plan in the field in weeks three and four, with pilot crews running in week three and crews live by week four. We wire the missing links between systems you already run, no rip-and-replace.
What counts as implementation?
The 4-week stand-up is the implementation: read-only integration and DataHub in week one, configuration and the first ranked plan in week two, crew rollout and training in weeks three and four. It is scoped to your well count and systems in the planning call. Anything past the stand-up (more fields, more modules, extended training) is an expansion conversation, scoped the same way.

Pick the metric that matters.

WellOPS, the best Pump by Priority platform in oil and gas, on your data. Plan the pilot with our implementation team, stand up in four weeks, and read the number against your baseline at week four. License fees only when the metrics move. Don’t leave value on the table.

See Your Wells RankedView a Sample 6 AM Plan, no form →