Built for field pace
Most frac simulators are study tools: you book a week, a specialist, and a compute queue. That work matters — and we do it. But the decision that actually changes a job happens while the crew is still on the pad, and nothing on the market is shaped for that hour. The fast lane is.
The loop, on one screen
Five steps, each on a single key. Enter takes the next action, so a re-solve is a keystroke rather than a tour of the application.
- 1Inputs
Load the case or nudge the handful of parameters that change on site.
clicks 6 → 2
- 2QC
Clear the ingest QC verdict for this revision before spending solver time.
clicks 5 → 1
- 3Run
Solve the current revision — one key, no dialogs.
clicks 3 → 1
- 4Review
Read the deltas against the last accepted run.
clicks 4 → 1
- 5Iterate
Queue a tweak and re-solve without rebuilding the case.
clicks 6 → 1
Count the clicks yourself
A classic multi-page loop costs 24 clicks per iteration; the fast lane costs 6 — 18 of them removed outright, step by step in the table above. This counts interface actions only — not solver time, which depends on your case.
Classic loop
144 clicks
Fast lane
36 clicks
Saved
108 clicks · 75%
A real pad, on the clock
4 wells, 50 stages each, 80 bpm at 2000 lb/ft — the same planning arithmetic the free calculator runs, not a slide. Change any of it there and these numbers move with you.
Stages on the pad
200
Pumping per stage
136.3 min
Stage cycle
181.3 min
Stages per day
6.6
Pumping days
30.2
Water on the pad
2,095,238 bbl
Proppant
80.0 MMlb
Perf friction
647 psi
Limited entry
Held at this rate
The window you get: 45.0 minutes between stages
On that pad the pumps run 136.3 minutes and the full cycle is 181.3 minutes, leaving 45.0 minutes of wireline, pump-down and plug work. That is the whole decision window — and you are sharing it. At 6 iterations:
Classic loop · 144 clicks
7.2 min · 16% of the window
Fast lane · 36 clicks
1.8 min · 4% of the window
Iterations the window allows (interface time only)
37 classic → 149 fast lane
Interface time handed back
5.4 min
Interface minutes assume 3 seconds per action. That is a stated assumption, not something we measured on your crew — the click counts underneath it come from the shipped workflow. Solver time is separate and depends on your case.
Why it is fast
One screen, five keys
Inputs, QC, run, review, iterate all live on one page. Keys 1–5 jump between them and Enter takes the next action, so a re-solve never means re-navigating the app.
QC clearance carries forward
Clearing ingest QC once holds across parameter tweaks on the same revision. You do not re-certify the same data every time you nudge a rate.
Pre-flight estimate before you spend solver time
The study designer estimates the cost of a run before it starts, so you find out a configuration is out of budget while you can still change it.
Tweaks you actually reach for at the pad
A fixed list of 8 on-site changes — rate, proppant loading, viscosity, stage length, cluster count, closure stress, leakoff — queued and re-solved without rebuilding the case.
Glove mode
Larger targets and reduced motion for a tablet in a truck, remembered per engineer.
Free diagnostics, no login
Paste shut-in pressure or step-down plateaus and get a pre-closure regime call and perf/near-wellbore split in the browser.
The tweaks the lane offers
No form hunting. These are queued, applied and re-solved against the same case:
Fast is not the same as loose
Speed here comes from removing interface work, not from skipping physics or hiding doubt. The same rules apply in the fast lane as everywhere else: an estimate is labelled an estimate, a run that did not converge shows no number, and every export carries its caveats inside the file.