Every civilization organized itself around a contained fire.

c. 400,000 BCE — the first kept fire

First, we gathered around it.

c. 1200 BCE — the forge: fire, directed

Then we put it to work.

c. 700 BCE — the hearth: fire, given walls

Then we built the walls around it.

The fire was never the point. The structure around it was.

Hearth Advisory builds that structure for oilfield, service, and fintech companies still running critical workflows by hand.

The situation

Critical workflows still run by hand.

Not because anyone chose it. The system was built for a smaller company, the person who understood it left, and the workaround became the process. These are the artifacts we find competent teams still moving by hand, every month, on a deadline.

Credit memos

Written from scratch, every time

An analyst pulls financials, re-types the same spreads, and rebuilds a memo that looks like the last forty. The judgment takes an hour. The assembly takes a day.

Field tickets

Keyed in twice, sometimes three times

Written in the field, photographed, emailed, re-entered into the billing system. Every hop is a place a number can change without anyone noticing.

JIB

Reconciled against a PDF

Joint interest billing arrives as statements that do not match the ledger. Someone opens both, scrolls, and marks the differences by eye before the close.

Approval chains

Waiting on one person's inbox

Limits, exceptions, releases — real decisions that need a human. But the queue lives in email, so nobody can see what is stuck or how long it has been stuck.

The method

Map it, modernize it, keep people in it.

01

Map the workflow

We sit with the people doing the work and trace one process end to end — every hand-off, every re-key, every wait. Nothing is proposed until the map is right.

02

Modernize the loop

We take the steps that are assembly — gathering, formatting, re-keying, checking — and build the tooling that does them reliably, inside the systems you already trust.

03

Keep humans in it

Judgment stays with your analysts. Every automated step lands in front of a person who can see what was done, why, and how to override it. Your team, faster and surer.

What an audit surfaces

Three findings, written plainly.

An audit ends in a short document: where the time goes, what can be modernized in ninety days, and what should be left alone. The examples below illustrate the format — not client results.

Example only

The memo is 80% assembly

Of the average credit memo, most of the elapsed time is gathering and formatting. The analytical section is written last, tired, and quickly.

Example only

The same number is entered four times

A field ticket quantity travels from paper to photo to email to the billing system. Each re-entry is unverified, and the mismatch is found at invoicing.

Example only

Nobody can see the queue

Approvals sit in individual inboxes. There is no shared view of what is waiting, who owns it, or how long it has been there — so escalation is a guess.

Who we are

A small practice, run by someone who has done the work.

Hearth Advisory is a credit and operations practice in Houston. The background is portfolio risk — writing the memos, chasing the exceptions, closing the month — which is why the work starts with the workflow and not with the technology.

We are not selling a platform. We modernize one workflow at a time, with the people who run it, and we leave when it holds without us.

Start here

The AI Modernization Audit.

Two weeks. One workflow, mapped end to end. You get the map, a ninety-day modernization plan, and a plain answer about what is worth doing. If the answer is “less than you think,” we will say so.

Book an audit Or write plainly about the workflow that keeps you up at month end.