CodelessOps · Services
A knowledge base for your finance team.
Built from your own documents, in weeks. Every answer cited to the exact cell it lives in, and you sign off when it passes 25 questions your own team wrote.
Finance teams spend close to half their time finding and re-validating information that already exists in their own files. And when the person who knew leaves, the knowledge leaves with them. Big tech companies fix this with in-house engineering teams. I'm the version of that team you can actually hire.
01 · What you can expect
Fourteen things your team gets. All of them built, none of them roadmap.
Answers you can take to the pack
- Ask in plain English, get the figure with its exact source: the workbook, the sheet, the cell. Not "see attached file".
- Every citation quotes your document word for word, so checking an answer takes seconds, not a search.
- A verification pass you can run on any answer: each citation graded against its source, the way you'd tie out a junior's work.
- Version sense built in: FINAL beats draft, v3 beats v2, the reissued report beats the one it replaced. Ask about an old version and it still knows where it is.
- When your documents don't contain the answer, it says so. No guessing, no figures smuggled in from adjacent periods.
- Numbers trace to a source cell or to a calculation it shows. A figure it can't support doesn't get stated.
Your documents, as they are
- One searchable store for the whole record: board packs, management accounts, policies, contracts, filings, forecasts. Scanned PDFs included.
- No re-platforming and no behaviour change. Your files stay your files; the knowledge base reads them where your team already keeps them.
- It finds things whether or not you use the same words the document did. Paste an account code or a standard and the exact match wins; ask "why did margin dip" and it finds the narrative that never says those words.
Beyond a search box
- Your team's notes live alongside the documents and come back in the same answers: why a treatment was chosen, what the auditor accepted, what to watch. The judgment stays when the person who wrote it moves on.
- Recurring work becomes a skill it runs the same way every month: the variance commentary, the close checklist, a covenant check. Same citation discipline as any answer.
- Multi-document questions get worked properly: "reconcile what the last four board packs said about runway" is a research job, and it does the legwork with the evidence attached.
Yours, provably
- A 25-question control your own team writes, rerun on demand. It graded the build before you accepted it, and it re-grades the system every month as new documents land.
- Your instance is yours alone, and if you want it inside your own infrastructure, that's an option. No data shared across clients, ever.
I wrote up the full architecture, organ by organ: The anatomy of a financial knowledge base.
02 · Financial, not generic
A generic knowledge base answers. A financial one proves.
Engineering teams have shown how to build company knowledge bases, and the retrieval science is genuinely good. But finance answers get filed, so a financial knowledge base needs organs the generic ones skip.
| A generic knowledge base | A financial knowledge base |
|---|---|
| Answers with a link to a file | Answers with the figure and the cell it lives in |
| Citations as decoration | Citations checked in a separate pass, like a tie-out |
| The newest file wins, maybe | FINAL beats draft, the reissue beats the original |
| Guesses when it's unsure | Says "your documents don't say", and is tested on it |
| "Trust us" | A rerunnable control: 25 questions, graded in front of you |
03 · The acceptance test
You don't take my word for it. You examine it.
Before anything is built, your team writes 25 questions it already knows the answers to: the real ones your auditors, your board and your new starters actually ask. That set becomes the acceptance test. The build is done when the system passes it, graded in front of you, and the same 25 questions re-run every month as new documents land, so you always know it still works.
The method is public. I published a version of this exam as theBoard Pack Test: 34 documents, 25 questions, answer key and grader included. Raw frontier models score 66 to 71 of the 81 machine-checkable points on it. The engine this service is built on scores 81. The gap was never intelligence. It was proof.
04 · Who it's for
Teams whose knowledge lives in a drive and a few heads.
CFOs, FDs and controllers of SMEs and scale-ups, especially at the moments complexity jumps: a new hire joining the finance team, a raise, a first audit, the month the "just ask Sarah" person hands in notice. If your team could write 25 questions it already knows the answers to in an afternoon, you're ready for this.
05 · How it's built
Weeks, not quarters. Then it's kept honest monthly.
01
The corpus
Your real drive, scoped and loaded: packs, accounts, policies, filings, contracts. What stays out gets documented too.
02
The exam
The 25 questions built with your team, and the system tuned until it passes them in front of you.
03
The handover
Notes and skills set up, team trained, run-book delivered. Then monthly: new documents in, the control re-run, a report you can read in a minute.
Where this sits among the other doors: if you just want your existing Claude or ChatGPT licence set up safely, that'sthe Audited AI Close. If one specific process is eating your month end, that'scustom automation. The knowledge base is for when the problem is finding and proving what you already know. The engine underneath isGrounded, my own platform — you can watch it work before we ever touch your files.
06 · Next step
Start with the exam, not the build.
A discovery call costs you thirty minutes. If it makes sense, the first piece of work is small and self-contained: we write your 25 questions and grade whatever AI your team uses today against them. You keep the question set either way, whoever you end up buying from.