Know how your finance work really gets done. Then change it with proof.
We watch the work your people already do, turn it into a process map where every step points back to what was said or seen, and price the future state you choose. Your board gets numbers it can audit, not a consultant’s estimate.
1 · Observe
See how work actually happens
A recorded working session becomes a process map in minutes. Below is the real output from an accounts payable walkthrough: move through the recording and watch each step appear the moment someone describes it.
Transcript
Vendor Invoice Processing 9 of 12 steps found
- 1A vendor invoice arrives in Outlook, usually as a PDF attachment from the supplier
- 2I download the invoice to my desktop so I can read the PO number off it
- 3Then I open NetSuite and go to the purchase order list
- 4I search for the purchase order using the number printed on the invoice
- 5I check the receipt information to confirm the goods were actually received
- 6I open Excel, our matching tracker, and paste the PO, receipt and invoice amounts
- 7I compare the three amounts. If they match within the tolerance I move on; if not it is an exception
- 8When there is an exception I message Purchasing on Teams and ask them to confirm the price or quantity
- 9Then I wait for their answer, which can take anywhere from an hour to two days
2 · Decide
Choose your future state, priced
Every process can be run several ways. You compare complete options side by side, each with the controls it would need, and each priced from your own observed volumes and rates during the engagement.
IllustrativeThree ways to run the same accounts payable process
Lean
Remove, simplify and standardize the work first. Little or no new technology.
What changes
- Stop downloading invoices to the desktop to read the purchase order number.
- Replace the side spreadsheet with one agreed matching tolerance, written into policy.
Controls it needs
- Policy change record
- Updated standard operating procedure
- Process owner sign-off
AI-assisted
AI does the reading and proposes the answer on judgment steps. Your people accept or correct it.
What changes
- AI reads each invoice and proposes the three-way match, citing where each figure came from.
- Your specialist reviews the proposal instead of keying it.
Controls it needs
- A person accepts every AI proposal
- Evaluation gates before any model change
- Pinned model versions
- Uncited claims flagged
- Drift review
Agent-owned
An AI agent runs the routine path end to end. People decide at approvals and exceptions.
What changes
- An agent matches, chases Purchasing on mismatches and routes approvals.
- Your team sees only exceptions and approvals above the threshold.
Controls it needs
- Written policies the agent cannot exceed
- Every system change staged through a controlled write-back
- Approval chains with thresholds and separation of duties
- A kill switch
- A tamper-evident audit trail
Illustrative. Options and controls are shown for the sample accounts payable process. We show no savings figure here because every number we give you is calculated from your own observed volumes and rates, and traces back to that evidence.
3 · Prove
Every number traces to evidence
Each step carries a coloured rail that says how we know it: seen on screen, or said by the person doing the work. Focus or hover a rail to open the evidence behind it. Nothing in the map is taken on trust.
Vendor Invoice Processing · review, read-only
- Observed
- Reported
- Measured
- Inferred
- Modeled / assumed
- Corrected
- Unknown
- 1A vendor invoice arrives in Outlook, usually as a PDF attachment from the supplierOutlook
- 2I download the invoice to my desktop so I can read the PO number off itOutlook
- 3Then I open NetSuite and go to the purchase order listNetSuite
- 4I search for the purchase order using the number printed on the invoiceNetSuite
- 5I check the receipt information to confirm the goods were actually receivedNetSuite
- 6I open Excel, our matching tracker, and paste the PO, receipt and invoice amountsExcel
- 7I compare the three amounts. If they match within the tolerance I move on; if not it is an exceptionExcel
- 8When there is an exception I message Purchasing on Teams and ask them to confirm the price or quantityMicrosoft Teams
- 9Then I wait for their answer, which can take anywhere from an hour to two daysMicrosoft Teams
- 10Once they reply I return to NetSuiteNetSuite
- 11I enter the invoice against the purchase order with the agreed amountsNetSuite
- 12Finally I route it for approval to my manager; anything over five thousand dollars needs her sign-off before it postsNetSuite
How it works
Capture
Your team records ordinary working sessions or shares existing call transcripts. Consent is recorded per session and sensitive details are redacted before anything is analysed.
Map
We turn the recordings into a step-by-step process, each step tied to the moment it was said or shown.
Validate
Your process owner reviews the map, corrects anything we got wrong and approves it. Every correction is kept.
Decide
You compare priced future-state options with the controls each needs, and choose. The choice and its evidence form the business case.
Security and governance, in plain language
Your data is walled off
Every query is fenced to your company at the database layer (row-level security), not only in application code.
Nothing happens off the record
Every view of evidence, every approval and every change is written to an audit trail that is chained so it cannot be quietly edited after the fact.
Your data stays where you say
Pin your workspace to a region. Analysis that would send data outside it is refused, not just logged.
Advisors only with your permission
Our advisors can open your workspace only when you grant access to a named person, for a set period. You can see every grant and every look, and end it at any time.
Who it is for
CFO
A business case your audit committee can check
Every saving is tied to observed work and shows its assumptions, so you can defend it line by line.
COO
Where the time really goes
See waits, hand-offs and rework as they happen today, and how each future option changes cycle time and capacity.
CIO
Change without new technical debt
Know which systems each option touches, where an integration beats a bot, and what controls come with it.
Process owner
Your process, described accurately
Review and correct the map yourself. Nothing is approved without you, and your corrections are kept as evidence.
Questions finance leaders ask
What do we need to provide to start?
A process owner, a few recorded working sessions or meeting transcripts, and an hour for review. No system integration is needed to begin.
Do you record our staff without their knowledge?
No. Every session is captured with consent that is recorded alongside it, and sensitive details are redacted before anything is analysed.
Where does our data go?
It stays in your workspace, in the region you choose. Sensitive details are redacted before analysis, and the evidence can only be viewed through short-lived links that are themselves logged.
How do you arrive at the savings figures?
From your own observed volumes, times and rates. Each figure shows the evidence and assumptions behind it, and where evidence is missing we say so rather than guess.
Can our auditors rely on it?
Every step, correction and approval is recorded in a tamper-evident trail, and the validated process can be exported as a documented procedure with its evidence.
What happens in a walkthrough?
A short session with one of our advisors, using a sample process or one of yours, to see whether it fits your priorities. There is no obligation.
See your own process, evidenced
Bring one process that matters to you. We will show you what the evidence looks like and how a priced decision follows from it.