WorkSync Services · The method
What an engagement actually looks like.
Four phases, from the number to a program your team runs without us.This page is the part most firms leave to the proposal: what we do, what your people do, and what exists at the end of each phase that did not exist before it.
For the person who has to staff this alongside their day job
The four phases
- 01Assess2 to 4 weeks, fixed fee
- 02DesignCo-built with your team
- 03Stand UpSprint delivery
- 04Run and TransferYours to run
Priced to scope · no gate
Why it is shaped this way
One continuous path from the number to the program you own.
- Nothing waits for the end
- The Assess phase produces a number you keep whether or not you carry on.
- Value in the first sprint
- Stand Up is sprint delivery, so the operation feels it before go-live rather than after it.
- The last phase is a handover
- Not a renewal. The runbook behind it is a deliverable, and your team has already used it.
Phase by phase
Who does what, and what lands at the end.
2 to 4 weeks, fixed fee
Assess
Quantify the prize in dollars against your own data. You get the number whether or not you hire us for the rest.
Co-built with your team
Design
The reference model and the operating design, built with the people who will run it.
Sprint delivery
Stand Up
Value in the first sprint, not at the end of the program.
Yours to run
Run and Transfer
You own the program. Where our software carries the work, license fees can be tied to agreed performance metrics, on terms set in the proposal.
What WorkSync does
- Read the operation as it actually runs, with the people who run it. Not an org chart and not a benchmark.
- Quantify the prize in dollars on your own data, for the one objective you picked.
- Write the roadmap: the sequence, the owners and the measure.
What your team does
- Name one asset group and the objective you are judged on this year.
- Give us read access to the data you already collect for it.
- Put the people who choose the work in a room with us for a few hours.
What lands at the end
- The current-state read, in your terms.
- The number: the prize in dollars, on your own data.
- The roadmap, yours to take into a budget conversation whether or not you carry on.
What WorkSync does
- Build the reference model the program runs on.
- Draft the framework: charter, objectives, KPIs and RACI.
- Design the operating rhythm around the people who will own it, not around us.
What your team does
- Name an owner for each objective, and hold them to it.
- Decide the one standard per function where today there are two.
- Send the people who will run the program, not a liaison.
What lands at the end
- The framework: charter, objectives, KPIs, RACI.
- The reference model, documented and yours.
- An operating design with a named owner against every part of it.
What WorkSync does
- Wire the data flows to the systems you already own.
- Build the dashboards and the workflows: the measure reported monthly, and the rhythm that keeps it honest.
- Add a point solution only where software improves the operating model.
What your team does
- Run the rhythm from the first sprint, not from the go-live.
- Work the list in the field, and tell us where it is wrong.
- Hold the before-and-after measurement to the baseline you agreed.
What lands at the end
- Data flows, wired to the systems you already own.
- Dashboards and workflows in use, not in a demo.
- Before-and-after measurement on one metric, agreed before it started.
What WorkSync does
- Hand over the runbook and the documentation behind every part of it.
- Train the people who will run it after we leave.
- Stay only where our software carries the work.
What your team does
- Own the program, the model and the measure.
- Run the rhythm without us in the room.
- Keep the reference model current as the asset changes.
What lands at the end
- The program, running, with your name on it.
- The handover runbook, and a team that has already used it.
- A capability that does not leave when we do.

Built underneath
Five things get built, whatever the objective is.
- 01FrameworkCharter, objectives, KPIs, RACI.
- 02Reference modelThe model the program runs on.
- 03Data flowsWired to the systems you already own.
- 04Dashboards and workflowsThe measure reported monthly, and the rhythm that keeps it honest.
- 05Point solutionsSoftware only where it improves the operating model.
How the program ends
You own the program. That is the end state, not a courtesy.
Where our software carries the work, license fees can be tied to agreed performance metrics, on terms set in the proposal.
Service, and software
Which half is people, and which half is a product.
The service. People, and what they leave behind.
- The framework: charter, objectives, KPIs, RACI.
- The reference model the program runs on.
- The operating rhythm, and the supervisors who run it.
- The data flows, wired to the systems you already own.
- The handover runbook, and the team trained on it.
The software. Only where it improves the operating model.
- WellOPS ranks and routes the daily work, and captures it in the field.
- FlowSync builds and keeps the hydraulic and network models.
- DataHub is the integration toolkit. It is not sold separately, and the program never depends on it.
Most of what we have delivered runs on systems you already own. A program that needs our software to work is a program we have designed badly.
The limits
What we do not do, said before you ask.
We do not replace your stack
We do not issue stamped engineering
We do not promise an uplift we have not measured
We do not sell you the platform and leave
The practice, page by page
- OperationsField operationsEfficiency, downtime and artificial lift: the work the crews do every day, chosen by what it is worth.
- Engineering and SafetySafety programA safety management system the field owns: hazards assessed with the crew, competency per task, leading indicators.
- Engineering and SafetyLeak detection and integrityLeak detection and integrity management designed around the instrumentation you have, with the evidence trail built in.
- Engineering and SafetyEngineering capacityRecurring engineering deliverables drafted from your own data, so the engineer reviews and issues instead of gathering.
- Technology, Data and AIOperational dataThe integration inventory, one canonical model, governed tables in your own cloud, and the runbook to own them.
How it starts
One asset group, and the objective you are judged on.
The Assess phase puts a dollar figure on it in two to four weeks, for a fixed fee. You keep the number either way, and the roadmap with it.