Stop running your JVs on spreadsheets, email and post-it notes.

Beryl reads and remembers every agreement, connects it to your data, and recommends your next action — the variance to challenge, the notice you owe, the cash call you're about to miss — before anyone thinks to ask.

Become a design partnerSee how it works

Illustrative — not live client data

Beryl is a commercial control tower: continuous monitoring of every joint-venture obligation against your live financial and production data.

Today's commercial reality.

Your agreements are spread across Egnyte, SharePoint, a shared drive — and three people's heads.
Daily reports and data arrive by email, from different operators, in different formats. Simple questions don't have simple answers.
You inherited a stack of agreements from an acquisition and nobody's had time to read half of them.
A 5% interest is the same work as a 45% one — same cash calls, same JV audits, same obligations.
Somewhere there's a side letter nobody remembers signing.
Costs are running over, and the notice you owe your partners still hasn't gone out.
One person knows how this asset really works commercially. They're on leave.
The audit window closes in months, and you get one shot at it.

Your JOA isn't a document you file. It's the control system for the asset — you've just never been able to run it.

Extract. Monitor. Respond.

Extract

Every obligation, structured.

Read once, held forever.

Every clause, deadline and threshold pulled out of your JOAs, CTIAs and TPAs, with clause references attached. A 300-page binder becomes structured data you can act on.

Monitor

Checked against what's actually happening.

Continuously, not once a year.

Every obligation, cash call and AFE reconciled against your live financial and production data — the variance surfaces the day it appears, not at year-end close.

Respond

The response, drafted and ready.

You decide. Beryl does the drafting.

Notices, breach challenges and sole-risk elections drafted and cited to the clause that governs them — reviewed by a person before anything is sent.

From clause to challenge.

Take a hypothetical operator, Ardmore Energy. Here is one clause, followed from agreement to action.

Step 01 · Extract

Beryl reads the agreement.

Not a summary — a structured read. Every party, deadline, threshold and obligation lifted out with its clause reference still attached.

Joint Operating Agreement · Section 12Page 214 of 387

12.3 — The Operator shall, within thirty (30) days of the end of each Quarter, deliver to each Non-Operator a statement of the Joint Account, and any variance exceeding five per cent (5%) of the approved AFE shall be separately identified in such statement.

Step 02 · The ontology

The words become things.

“The Operator” becomes a company holding 45%. “The approved AFE” becomes a number in SAP. This mapping — contract language bound to the real entities in your business — is the part that makes everything after it possible.

Step 03 · Monitor

Checked against the systems that hold the truth.

Budget and committed spend from SAP. Production from EnergySys. The cash call itself, sitting in someone's inbox. The deadline in the calendar. Beryl joins them and does the arithmetic the clause implies.

SAP · costSynced
AFE-1847-14 budget£480,000
Committed to date£512,340
Variance+£32,3406.7%
EnergySys · productionLive
Brae North · Q3412 kboe
Your entitlement76.2 kboe
Inbox
Ardmore · Cash call CC-091209:41
Ardmore · Q3 Joint Account stmtMon
Calendar
Challenge window closes12 days
Audit window closes41 days
Step 04 · Ask

Ask in plain English — including from Claude.

Beryl exposes your commercial estate to the assistant your team already uses. Ask Claude the question; Beryl supplies the answer, with the clause and the ledger entry behind it.

Claude · connected to Beryl
Is the Brae North cash call within the AFE?

No. CC-0912 is £512,340 against an approved AFE of £480,000 — a variance of £32,340, or 6.7%.

Clause 12.3 requires any variance above 5% to be separately identified. It wasn't. Your 18.5% share is £5,983.

↳ JOA cl. 12.3 · SAP AFE-1847-14 · CC-0912
Step 05 · Respond

Beryl drafts. Your team decides.

The challenge is written, cited and ready to send. Nothing leaves the building without a person approving it — and either way, the decision is logged to the audit trail.

Reconciliation · Brae NorthLive
⚠ Break detected£32k overCash call £512k vs. AFE £480k · clause 12.3
one click — no manual

Why you can't just put your agreements in Claude.

Ask Claude what clause 12.3 requires and it will tell you, accurately, and you should be doing that. Ask whether you've been overcharged and it cannot know: the answer isn't in the document.

You'll still get an answer. On a £2M invoice, a confident figure tracing back to no clause and no cost line is worse than none. Beryl connects the clauses to reality:

The clause saysWhich means, for you
“the Operator”Ardmore Energy — a party, holding 45%
“each Quarter”Q3 2026, closing 30 September
“the approved AFE”AFE-1847-14 — £480,000, in SAP
“exceeding five per cent (5%)”A £24,000 threshold — already crossed
“each Non-Operator”Three parties; your share is 18.5%

Resolution

The agreement's terms have to be bound to real entities, numbers and dates inside your systems. That mapping is the ontology — the unique layer that Beryl brings.

Cross-agreement

A JOA clause interacts with a CTIA, and with a side letter signed three years later. One document in a context window doesn't know the others exist.

Continuity

This isn't a question you ask once. It's a check that runs every day, against data that changes every day, and raises its hand without being asked.

Your data never leaves your environment.

Beryl deploys inside your own cloud environment, alongside the systems it reads — no copies, no uploads, no training on your data.

LayerWhat it does
Agentic workflowsExtract, validate, reconcile, track and generate — running continuously in the background, whether or not anyone is watching.
IntelligenceAsk Beryl anything about your portfolio in plain English — “which cash calls are overdue?”
Human-in-the-loopEvery flag is reviewed and approved by a person, with a full audit trail. Beryl proposes; you decide.
ConnectorsSnowflake · Databricks · SAP · EnergySys · OSIsoft PI · AVEVA · SharePoint
DeploymentRuns inside your own cloud — AWS · Azure · Google Cloud— natively alongside your data platform. Cloud-agnostic by design.
Co-founder · CEO

Niall Rowantree

Eleven years at TotalEnergies across commercial, joint ventures and digital — running North Sea JV interests, then building the UK data and analytics function from scratch. He has been the one answering for a missed obligation, and the one asked to build the system that should have caught it.

LinkedIn ↗
Co-founder · CTO

Pedro Santos

A decade in data and AI across the energy sector and the Bank of England. He has led data science teams inside a North Sea operator and built the production knowledge graphs and ontologies that Beryl now runs on.

LinkedIn ↗

We're taking on a handful of design partners.

Not customers — partners. You bring the assets and the agreements; we build the tool around your reality. First movers set the roadmap.

Email us

Based in Aberdeen · Working across the UK Continental Shelf