The operating system for well operations.
One record for a job, from the first estimate to the settled invoice. Planning, the workshop, the crew offshore and finance all read the same one, and nothing is re-keyed at a handover.
One record
Every job. Every tool. Every hour.
The estimate, the tool string, the shipment, the run log and the invoice line are one object at different ages. The time a planner loses goes on reconciling spreadsheets, chasing certificate dates and rebuilding a tool string somebody already built. Wellplanner removes the reconciliation, because there is nothing to reconcile.
Figures describe the system, not customer results.
Built with the people who run the work.
The model behind Wellplanner comes from a decade of running plug and abandonment, intervention and completion campaigns on the Norwegian shelf. It is built with the operators who do that work, and it is shaped by what they say it gets wrong.
- Domain
- Built on well service operations, not project theory
- Deployment
- Multi-tenant SaaS, one product identity for every company
- Data
- Full export and a documented API. No lock-in clause
- Offshore
- A rig app designed for gloves, darkness and no signal
One system, from the base to the wellhead.
Planning, workshop, logistics, offshore execution and invoicing are four views of the same job. No guesswork about what shipped, what is downhole, or what has been billed.
Book a demoBuilt for the whole operation.
Wellplanner covers the operational and commercial lifecycle of a well service company, in one multi-tenant platform. Each company runs its own regions, currencies, product lines and rates.
Questions we get asked.
If yours is not here, ask it directly. You will get an answer from someone who has read the model, not a form response.
We already have an ERP. Why do we need Wellplanner?
An ERP models purchase orders, stock and ledgers. It does not model a tool string, a crew certificate that expires before mobilisation, or a run record attached to a physical serial. Wellplanner sits beside the ERP and feeds it. The two integrate rather than compete.
Is Wellplanner only for offshore work?
No. The model covers well service work wherever it happens. Terminology is configurable per company, so a wireline operator working entirely onshore does not read offshore language throughout the product.
How long does implementation take?
The first job is built with you in week one. One rig runs live by week five, base and workshop by week ten, and finance closes the loop in the following quarter. You are not asked to migrate everything before anything works.
Is our data safe, and is it separated from other companies?
Wellplanner is multi-tenant with hard isolation. No user reads across companies, and every record carries its company identifier at the database level rather than in application logic.
Can we export our data?
Yes. Full export and a documented API from day one. There is no lock-in clause, and leaving is as easy as joining. We would rather you stay because the product works.
Does it work when the rig has no connection?
Not yet. The rig app shows the connection state, and an entry lands on the job record the moment it is saved. A queue that holds entries while the link is down and sends them in order when it returns is in development.
Can we configure it for how our company works?
Regions, currencies, product lines, job numbering, contract fields, unit system and terminology are all yours to set. The visual identity is not configurable - every company sees the same Wellplanner, so support and training carry across.
Do you integrate with our existing systems?
Connectors are per company and off by default. Tell us which systems matter and we will scope the integration before you commit to anything.
What happens to our data if you are acquired?
Nordworks AS is Norwegian and independently owned. If that changed, your position would not: the record is yours, an administrator can take all of it whenever they like, and there is no lock-in clause for anyone to renegotiate.