Land, geology, production, people, spend and deals — one system, one set of numbers. Ask it out loud and it answers from your own data. Here is everything it does, organized by the person who needs it.
Nobody in the patch is short of data.
They are short of one place where it agrees with itself.
Land is in a spreadsheet. Geology is on an engineer's laptop. Production is in one vendor's system, accounting in another, and the reporting lines exist only in somebody's head. Every question that crosses two of those becomes a two-day project.
Which leases expire before a rig can get there. Which wells cost more to run than they bring in. Which county is worth renewing as a block. They are all answerable — but only by a system holding land, geology, production and cost at the same time.
You are not replacing any of this.
Nobody rips out their reserves database to try a new tool. The question is what WELLFORCE reads, what it writes, and what it honestly does not touch yet — so here is the whole list, including the rows that are not finished. The status on the right is what the code can back today, not a roadmap.
wf_alarm has zero rows: the formula is live and has never seen a real alarm..mdb, .accdb and SQL Server ariesadmin.* directly, in the operator’s own browser — the database never uploads. The Arps maths reproduces what ARIES itself printed to within 0.0035% on four published cases. The parse is proven on four real Access files; what is not proven is a real operator’s ARIES database, because the development fixture is a shape WELLFORCE built.wf_crew_post marks a message as an instruction; the feed shows what is still unacknowledged.“Be nice to just put info in once.”
“So many alarms, kinda like crying wolf, and the guys kinda ignore most of them.”
“No accountability or paper trails… I said to do xyz.”
A workover foreman, 10 September 2026Two of the eight rows above are working today. Six carry a caveat, and two of those say “not built” outright. That is on purpose. Every integration on this page that has not met a real operator’s data is labelled as such, because the first time it fails is going to be in front of you either way — and you should hear it from us first.
100+ capabilities. Built and shipping.
Every capability below is built and deployed. Some are in daily use; some are waiting on their first operator. Each one is explained in full further down the page — and we will tell you which is which.
Ask out loud. He answers, then acts.
See the entire company at a glance.
Know what actually lands in the bank.
Never lose a lease to the calendar.
The curve, beside the cost and the clock.
Numbers that arrive already tied to the well.
Built for one bar of signal and dirty hands.
Open the data room without losing control of it.
Whose data it is, and who can reach it.
The machinery underneath all of it.
“Operated only, nothing over thirty million, Eagle Ford or Permian, at least five hundred a day, and I care more about contiguous acreage than price.”
Said once, out loud. It saves to the company profile, supersedes the previous box with a record of who set it, and every recommendation in WELLFORCE screens against it until somebody changes it. The leaning becomes a weight, not a filter — which is the difference between narrowing your list and emptying it.
He doesn’t just tell you. He does it.
Every other assistant in this industry reads you a summary. DERRICK answers from your live numbers, reasons over them like an operator, and then drives the application on your behalf — and asks before he commits anything.
Not a chat log — nobody reads those. He keeps the four things still true next month: what you decided and the reasoning behind it, what somebody committed to and by when, how you like to be dealt with, and the durable facts about the operation that live nowhere else in the data.
Three properties are what make that worth trusting. A new decision about a subject retires the previous one, so a call you reversed never sits in his head arguing with the one you made. A commitment goes quiet once it is a fortnight past due, because a task from two weeks ago is noise, not memory. And every fact keeps the words it came from — you can challenge it. An assistant that remembers things it cannot justify is worse than one that forgets.
He raises it unprompted when it bears on now: the lease you told him to rig up on is inside forty days, the numbers have moved against a call you made, someone's commitment comes due Friday. And you can open everything he remembers, read it line by line, and delete any of it.
Rig up before the primary term rather than renew — the county bonus is climbing faster than the day rate.
“we are not paying that bonus twice”
Walk the Webb 12 location with the construction superintendent before the pad order goes in.
“I’ll get out there Friday”
Wants the dollar figure first and the reasoning after it. No menus of options.
He reasons over a live snapshot of your company — production, cash, wells, people, leases, deals, calendar. He never invents a figure. If something isn’t tracked he says so plainly and offers to start tracking it.
Not a phone’s robot. Say “Hey WELLFORCE, what’s going on?” as one sentence, hands full, and he answers aloud.
Many crews work in Spanish. He replies in whichever you spoke, and translates any note or message between the two on request.
Quick status questions run on the fast model; strategy, land and portfolio questions shift up to the deeper one automatically. You never pick a model.
Seven jobs. One set of numbers.
You get thirty seconds between meetings. The question is never "what happened" — it is "what needs me today, and what is it worth."
The thirty-second landing. A north-star number for your industry, then production, cash flow, land at risk and open opportunity — each tile opening into the detail behind it. Built to be read standing up.
The whole company on one page, industry-aware: an operator sees BOE/d, netback and lease risk; a service company sees utilization and backlog; a supplier sees fill rate and cash conversion cycle.
Tap the orb and your briefing is read aloud — production, cash, the flagged opportunity, the top deal signal — composed live from your data. Or ask him anything: "what's bleeding money?" He answers from the snapshot, never from a guess.
Every morning, ranked by dollars at stake, printable and mailable. The one-pager you would have asked an analyst for.
One cross-side feed of what changed while you slept — new permits nearby, assets listed, crews freed up, needs posted against your fleet.
Say it once — "nothing over thirty million, operated only, Eagle Ford and Permian, and I care more about contiguous acreage than price" — and it becomes the standing filter behind every screen. Hard requirements filter; preferences weight. It saves to the company profile with who set it and when, and a new one supersedes rather than overwrites, so any screen can be traced to the rule it ran under. Your VP of business development screens against your current box, not last quarter's.
One screen that reads your box back in plain English — "under $30M, operated, over 500 BOE/d" — and shows only what clears it. The rest of the market stops competing for your attention.
Live rig and A&D activity on a rotating globe, scored for fit against your position. The screen you leave up on the wall.
Gross production is not money. You care about what actually lands in the bank per barrel, what a decision does to it, and which wells are quietly eating the difference.
The "it all connects" layer: from wellhead volume through price differential, severance tax, operating cost and working interest down to field cash per BOE. Every well, every month, with the arithmetic visible.
Wells whose operating cost exceeds their revenue, surfaced with the annual dollar figure attached rather than buried in a variance report. Shut-in, workover or divest — with the number in front of you.
Drilling cost built up by depth, spud days and day rate, so an authorization for expenditure is modeled before it is signed, not reconciled after.
Instant asset appraisal on a discounted cash flow — decline rate, netback, oil cut and NRI over the life of the well. PV and EUR appear in the well popup itself.
Model a purchase or a divestiture against the existing portfolio and see projected impact on production, cash flow and margin before anyone signs a letter of intent.
Who gets paid what, when one party operates and the others do not — grounded in COPAS joint-interest billing and farmout promote structures.
A lease that expires is not a filing problem, it is a development-value problem. The job is knowing which ones, how long you have, and what walking away costs.
Every lease ranked by days to expiration, with held-by-production status, the continuous-development clause that governs it, and the development value at risk if it lapses. Critical leases first, in days, not in a spreadsheet tab.
Risk rolled up across the whole position: total acres, total dollars at risk, critical count, and county clusters — because renewing six leases in one county as a block earns better bonus terms than renewing them one at a time. Weighs renewal cost against development value, lease by lease.
Flags the leases where a competitor's top-lease offer is already circling, and the spud-or-lose-it clauses where the clock is the real counterparty.
Leases, wells and jobs on an actual map inside WELLFORCE — no new tab, no export to a desktop GIS. Ask DERRICK to "show me the land" and the map comes up.
State by state: the regulator, the permit forms, completion and production report deadlines, and plugging rules — Texas RRC, New Mexico OCD, Oklahoma OCC, Louisiana SONRIS. Operational guidance where the deadline actually lives.
He doesn't read you a report — he works the position. Ranks counties by critical count, then by dollars at risk. Weighs renewal cost against development value lease by lease. Tells you what to renew first, what to negotiate as a block — six leases in one county earn better bonus terms than six one-offs — and what to let go. Calls out the spud-or-lose-it clauses where the clock is the real counterparty, and the leases with a top-lease offer already circling. Then puts the map, the portfolio view or the Regulatory Compass on screen, and drafts the message to the operator if you ask him to.
Your curves already exist. What you rarely get is the curve sitting next to the lease clock and the operating cost — which is where the decision actually lives.
Hyperbolic decline on the real parameters — Qi, Di, b — carried through to EUR and to a discounted cash flow, so a type curve becomes a dollar figure instead of a chart.
Formation-level performance across your wells and the offsets around them, so a new location is judged against what the rock has actually done nearby.
Completion and frac parameters held with the well, alongside its production history — the two halves of the question usually kept in different files.
CSV import with a keyed join: land binds by lease, geology binds by API. Bring in an RRC or FracFocus export and it lands on the right well instead of in a new orphan table.
Import from the tools you already run — API, Formation, Qi, Di, b, EUR, WI, NRI, PriceDiff, Opex, Capex, SevTax. NPV and EUR then appear in every well popup.
Permits and activity around your acreage, updated as a daily habit rather than a quarterly pull — the early signal that somebody is drilling toward you.
Your month-end is somebody else's data-entry backlog. Everything here exists to make the numbers arrive already tied to the well, the owner and the AFE.
Joint-interest billing grounded in COPAS accounting procedure and farmout promote structures — so non-op partners get billed on the basis everyone agreed to.
Working interest and net revenue interest held on the well and editable in place, feeding valuation, netback and revenue distribution from a single number instead of three copies of it.
Import and track AFE_No, CostCenter, Vendor, InvoiceAmt, GLCode, Owner, NetRevenue, JIB — spend tied to the authorization it was committed against.
Severance tax and price differentials carried in the netback calculation, so field cash per BOE is the real number and not a gross-revenue proxy.
Photograph a paper invoice, a coding note or a field ticket and WELLFORCE proposes the record — routed to the right well or person, with the words on the page quoted beside every field. Nothing is written until you confirm it.
DSO, DIO and DPO surfaced as one cycle number, so trapped working capital is a metric on the board rather than a discovery in the audit.
Anything that needs a laptop, a signal, or twenty minutes at the end of a shift does not get done. This half of the product is judged on one bar of service and a dirty screen.
Sticky notes, legal pads, hand-drawn org charts, gauge sheets, business cards. Photograph it and WELLFORCE reads it, matches names against the real roster instead of creating near-duplicates, and proposes the records. Every field cites the words it came from; nothing lands without a tap.
No signal on the lease road is the normal case, not the edge case. Captures queue on the device under a generated id and upload when the truck gets back in range — the id makes retry idempotent, so a flaky connection cannot file the same page twice. And the app now opens with no bars at all: install it to the home screen once where there is service, and it launches on a lease road with nothing, holding the last work it saw.
A pumper's readings used to live on the pumper's phone and the superintendent's notes on his laptop, and neither could see the other. Every reading, note, incident and report from every device now converges into one company record — append-only, so two people gauging the same well keeps both observations rather than one silently overwriting the other. What DERRICK reasons over is the record the crew is actually writing.
The Field screen opens on the shift, not a menu: the wells on today's route, which are gauged, which are still due, which are reported down. The sheet takes oil, water, gas, tubing and casing pressure and hours run, stamps where and when, and posts whether or not there is a signal.
A well-control kill sheet that steps drillpipe pressure down from initial to final circulating across the strokes from surface to bit. Kill mud weight from shut-in drillpipe pressure and true vertical depth. Hydrostatic pressure, and the mud weight needed to hold a target. Annular and pipe volume, pump output per stroke, equivalent circulating density, buoyed string weight. Lock the drawer to a well and depth and mud weight fill themselves from the record. It follows you across screens, so you never lose your inputs to go look something up.
Submit from the field, route to the person who has to sign off, and keep an inbox of what is awaiting your review — with an incident path for well-control and safety events that reaches leadership immediately.
What is on the shelf, what is on order, and an AI recommendation on what to stock before the next failure rather than after it.
The recipient list builds itself from your org chart: Everyone, My team (everyone reporting under you, at any depth), each department, every role at once — all pumpers, all superintendents — and each location. Or search and tick individuals. Say it to DERRICK instead and he writes it in your voice, reads it back, and waits for your yes before it goes.
Many crews work in Spanish. Messages, notes and DERRICK himself all work in either, and translate between them on request — not a setting buried in a menu, just the language you spoke.
Deals die on trust. A seller will not open reserves and geology to a stranger, and a buyer will not spend weeks on a package they cannot verify. The data room is the product.
Nothing opens until a confidentiality agreement is signed electronically. The signature record captures identity, timestamp, IP and a hash of the exact agreement text — an ESIGN/UETA record, not a checkbox.
Sensitive folders — reserves, geology — are watermarked with the viewer's own identity and served view-only. Every open is logged to an audit trail the seller can read.
Wells, non-op interests, acreage, midstream, saltwater disposal, minerals, yards and rigs — listed where buyers already are, with a fit score against each buyer's position.
One click drafts the teaser, the executive summary and the confidential information memorandum from the package data — the week of document work that usually delays a launch.
Deal density by county across every segment, so you can see where transactions are actually clearing before you price yours.
Deals, service companies and people are scored the same way: your hard requirements filter the list, then your preferences weight what survives. Every result carries why it ranked, what to watch, and the trade-off you are accepting — because the cheapest and the closest are almost never the same vendor, and a list that hides which is which is worse than no list at all. Distances are real miles between real towns.
Every transaction in one command center from indication through close, with a capital layer connecting buyers to acquisition financing and verification badges establishing who is real.
The rest of the machine.
Most of these appear inside the screens above rather than as destinations you navigate to.
Your numbers are yours, and the system can prove it.
The second question every operator asks is where their data lives and who can reach it. These are the answers, in the order they get asked.
Which company you are is resolved from your authenticated session against a membership record — never from anything the browser claims. There is no value a person can edit on their own device that puts them inside somebody else's operation.
Every record — production, notes, readings, incidents, buy box, and everything DERRICK remembers — is scoped to the company that wrote it, on the server, on every request. Not a filter in the interface. A wall underneath it.
Nothing in an A&D room is visible until a confidentiality agreement is signed electronically, with identity, timestamp, IP and a hash of the exact agreement text captured — an ESIGN/UETA record, not a tick box.
Reserves and geology are watermarked with the viewer's own identity and served view-only, and every open is written to an audit trail the seller can read.
What it refuses to do.
DERRICK answers from your snapshot or says plainly that something isn't tracked and offers to start tracking it. SNAP proposes records, quotes the words on the page behind every field, and leaves a field blank rather than guess — because a blank is recoverable and a fabricated pressure reading is not.
Messages are read back and confirmed before they go. Photographed records show exactly what will change and where before anything is written. One extra tap — and the difference between a demo and a system people still trust in six months.
WELLFORCE is in private preview with a small number of design partners. Bring a well list and a lease schedule and it will be running on your data, not a demo set, inside a day.