For audit firms · built and running
Audit software an inspector can follow.
Automate the fieldwork without asking anyone to trust a black box. Every conclusion traces to the clause behind it — and the trace is stored, not reconstructed.
Three minutes, one real engagement
Watch it work.
Not a storyboard and not a mock-up. Every screen below is the running platform, recorded on a complete engagement — findings ranked, a conclusion traced to its clause, materiality recomputing live, a review gate passed, and an opinion signed and sealed.
The problem isn't capability. It's defensibility.
Audit AI can already find the anomalies. What it usually cannot do is tell you why, in terms a regulator accepts. A tool whose conclusions nobody can trace back to a standard shifts risk onto the person who signs — which is exactly why adoption stalls in the firms that would benefit most.
One-button trace
The path an inspector asks for is a first-class object, not something reconstructed under deadline.
What that buys you
Six properties that follow from one decision: never produce a conclusion the auditor cannot defend.
Every conclusion cites its clause
Findings link to the specific standards paragraph behind them, and the chain from finding to clause is one click — not a citation pasted in afterwards. The link is a stored relationship, so it survives archive and staff turnover.
outputs enter on the model's authority
Every one is accepted, edited or rejected by a named human. The file records both the proposal and the judgment.
to reperform a control
Controls compile to deterministic logic and run over the full population, issuing a signed certificate — not a sampled conclusion.
Late data doesn't silently rewrite your file
When new data arrives — as it always does — only the artifacts it actually affects are flagged stale. The rest of your concluded work stays intact. That is the difference between software that respects a concluded file and software that quietly overwrites one.
Multi-jurisdiction from the start
US PCAOB and SEC frameworks alongside international ISA, IFRS and IESBA, and MENA regulators including DFSA — in one corpus, not separate products.
Your methodology, versioned
Firms author their own workpaper and field universes. An engagement pins to a version, so a mid-engagement change can never mutate a concluded file.
This is the actual product. Unstaged.
A real capture from the running system on a complete fixture engagement — 244 findings ranked by risk, the exposure quantified, and the five gates across the top. No mockups anywhere on this site.
A standards corpus, not a PDF library
Clauses are addressable objects that findings, risks and procedures link to directly. That is what makes the trace above possible rather than aspirational.
Clauses in the corpus, by framework
11,683 in total, across 19 frameworks. Counted from the live corpus on 2026-08-09 with test fixtures excluded, not estimated.
View as table
| Framework | Clauses |
|---|---|
| ISA — International Standards on Auditing | 6,463 |
| IFRS | 1,766 |
| PCAOB Auditing Standards | 1,445 |
| IESBA Code of Ethics | 1,424 |
| Other frameworks combined | 274 |
| Quality control / quality management | 111 |
| DFSA | 102 |
| SEC Regulation S-X | 98 |
| Total | 11,683 |
Where it deliberately stops
Some judgments are legally reserved to a person. Advertising limits is unusual; for this buyer it is the entire credibility argument.
| Area | What the software does | What stays with you |
|---|---|---|
| Findings | Detects, evidences, cites the clause | Accepting, editing or rejecting every one |
| Independence | Screens and surfaces what it found | The partner attests — the tool never asserts permissibility |
| The opinion | Assembles the supporting file | Entirely yours. It is a judgment, not an output |
Five gates. Five recorded judgments.
No gate advances on the model's authority. Each one is a named person's decision, snapshotted against the exact data state it was made on.
- 1IntakeGL · documents · ERP
- 2Detection & riskfindings routed for review
- 3File buildpinned methodology version
- 4Evidence & provingsigned control certificate
- 5Completionarchive · inspection pack
What we are looking for
Built and running. Now we want it stress-tested.
If you are an audit firm willing to run a real engagement on it and tell us where it falls short, that is precisely the conversation we want.