Request a demo
Custom solutions · built to your constraints

The engines are standard.
The solution is yours.

Every basin has its own fiscal terms, its own reservoir physics, its own exploration logic. The suite ships with sensible defaults — and a customization layer where your requirements and constraints become the workflow: your presets, your sensitivities, your risking criteria, wired in and handed over.

I need a custom solution See the engagements
01 · Base engine

Start from the suite

Imagio → Conversio → Præsagio → Punctio → Maturatio → Estimatio. Proven engines with clean hand-offs — nothing is built from zero.

02 · Your constraints

State what the defaults miss

The fiscal decree that isn't a textbook PSC. The reservoir that holds two fluids. The play where amplitude, not structure, ranks the portfolio.

03 · Custom build

We wire it into the engine

New presets, new physics, new sensitivities — implemented in the engine itself, verified against your reference cases, and handed over so your team runs it without us.

Three customizations that shipped
illustrative — fiscal waterfall and farm-in split, no real terms shown
EstimatioAngola offshoreFiscal engine customization

An economics engine that speaks Angolan fiscal terms

Off the shelf
Estimatio runs a monthly PSC ledger — cost oil, profit oil, tax, decommissioning — with generic term structures.
The constraint
Angola offshore is not one fiscal regime but several, and the client's real question wasn't NPV — it was what a block is still worth today, and what a defensible farm-in offer looks like.
What we built
The engine was extended into the client's own valuation instrument: domain presets, profit-oil mechanics and a bespoke remaining-value sensitivity, sitting on a financing layer.
Delivered customizations
  • Four fiscal-term presets for the Angolan offshore domain, switchable per project — one click from marginal-field to deepwater terms.
  • Profit-oil sharing sensitivity — the sharing mechanism itself as a driver, swept across slabs to show where the contractor take breaks.
  • Custom remaining-value & farm-in sensitivity — rolling remaining NPV from any as-of date, converted into a farm-in offer range under working-interest and carry structures.
  • Financial engine — loans, offtaker prepayment and equity dilution run against the fiscal ledger, so the entry structure is priced, not assumed.
Base · Estimatio · fed by Maturatio profiles
See the Angola engagement →
illustrative — gas cap, oil rim and aquifer, no real field shown
MaturatioMalaysia bid roundReservoir physics customization

Forecasting reservoirs that hold two fluids at once

Off the shelf
Maturatio's tank material-balance simulator runs a field of one fluid — oil with aquifer support, or gas down to plant intake — month by month to licence end.
The constraint
The bid-round blocks don't read that cleanly: gas fields carrying an oil rim, oil fields under a gas cap. Bidding on single-fluid forecasts means mispricing every one of them.
What we built
A dual-fluid formulation of the same tank engine, so one forecast carries both fluids and their coupling — cap expansion pushing on the rim, rim wells competing with gas blow-down, contacts moving consistently with pressure.
Delivered customizations
  • Gas-with-oil-rim mode — thin-rim producers phased against gas-cap drive, with the rim's window shrinking as the cap expands.
  • Oil-with-gas-cap mode — cap energy as drive and as constraint: blow-down timing traded against oil recovery in the same run.
  • Pressure-consistent contact movement for both contacts at once, so the forecast honours one material balance rather than two half-truths.
  • Bid-round tempo — every concept still hands off to Estimatio's monthly ledger, so dual-fluid physics reaches the bid economics unchanged.
Base · Maturatio · hands off to Estimatio
See the Malaysia engagement →
illustrative — stacked sands and amplitude patches, no real prospect shown
PræsagioAndaman SeaExploration logic customization

When structure isn't the story, the workflow changes

Off the shelf
Præsagio's exhaustive sweep finds every structural closure a surface can hold, seals it at its exact spill, and ranks unrisked volumes.
The constraint
In the Andaman biogenic gas play, the classical structure-first workflow isn't the most effective lens: the prospectivity lives in what the amplitudes say, how the sands stack, and how far each body extends.
What we built
A play-specific portfolio builder on the same engine: closures are still found exhaustively, but the portfolio is driven by trap-type classification, amplitude evidence, stacking and sand-body extent rather than structural relief alone.
Delivered customizations
  • Trap-type classification — structural, stratigraphic pinch-out and combination traps tagged per prospect, so unlike traps aren't ranked on one axis.
  • Seismic amplitude anomaly as a driver — anomaly presence and conformance feed the ranking and the risking, not a footnote.
  • Stacked-reservoir handling — vertically stacked prospects grouped where one location tests several, with shared-lattice bookkeeping.
  • Sand-body extent limits — trap outlines clipped to mapped body extents, so volumes honour the geology, not just the contour.
Base · Præsagio · risking in Punctio
See the Andaman engagement →
The customization surface

What tends to get tailored.

Anything with a default has a customization path. These are the levers clients reach for most.

Estimatio

Fiscal terms & presets

PSCs, concessions, decrees and increments encoded as switchable presets, with your reporting conventions on the ledger.

Estimatio

Bespoke sensitivities

Beyond tornados: the sensitivity your decision actually turns on — remaining value, farm-in range, sharing mechanics — built as a first-class analysis.

Maturatio

Reservoir physics

Fluid systems, drive mechanisms, facility constraints and abandonment chains matched to how your reservoirs actually behave.

Præsagio · Punctio

Exploration & risking logic

Play-specific portfolio drivers and editable POS matrices, so the ranking encodes your basin's evidence — not a generic checklist.

Conversio

Depth-conversion methodology

Your preferred velocity modelling — one-point, V₀+K, instantaneous, TDR — set as the house method with your QC displays.

Suite-wide

Deployment & integration

On-premises installs, database locations, volumetrics reporting templates, units and naming — the suite fitted to your environment, not the other way round.

Tell me the constraint. That's the brief.

I need a custom solution Request a demo