AI & Human
TryPipeline is one founder and the software he's built. The software does the reading and the checking, and nothing reaches you until he's been through it himself.
What the software does
- Reads your filed return, in ESMA's format or the FCA's own RegData format, and the files behind it: Excel workbooks or CSV exports, laid out however your administrator lays them out.
- Tells you plainly when it can't read a file, and what to send instead. It never guesses figures from a PDF, a scan or an email.
- Rebuilds the return from those files and compares it with what you filed, field by field.
- Points every difference at the cell it came from.
- Logs every run with a fingerprint of each file it used, so any result can be run again and checked.
What a person does
- Agrees what's in scope with you, and signs the NDA and data processing agreement.
- Goes through every finding against your files before the report is sent.
- Talks you through the results and answers for them.
- Tells you straight what the check can't see.
Where we use AI
- Drafting and reviewing code
- Writing tests, and test funds with mistakes planted in them
- Reading the rules and guidance
- Every change checked against every test before it's used
- Your files are read and compared by written rules
- Anything the files don't settle becomes a question for you
- A person goes through every finding
- You decide what to correct or refile
Every day, for writing and testing our code and for keeping up with the rules. The check itself doesn't use AI to make judgements. It runs on fixed rules, so the same files give the same answer every time, and every answer goes back to a cell in your files.
When it gets something wrong
Before a new version goes anywhere near a client's files, we test it on made-up funds built by a separate AI agent that never saw our code. The first time we did that, it fell over. We wrote down what happened before fixing anything, and we do that every time.
Every version of the software and every test run goes into a log where each entry carries the hash of the one before. Each report and deletion certificate we send prints its entry's hash, so if the log were ever rewritten, your copy would no longer match. The standard each version must meet and the latest hash are on How we test.
Why one person can do this now
A firm doing this work would normally need a small team, with developers, someone who knows the rules inside out, people to run the checks and someone to look after clients. All of that ends up in the fee.
That's changed. One person with the right software can now do the building and the checking, and spend their own time on the calls and the judgement. We think a lot of specialist firms will be built this way over the next few years, with very few people and a lot of software behind them.
What it means for you
- You deal with the person who built the check.
- We're cheap to run, so we can charge less.
- Every check follows a written method and every run is logged, so nothing lives only in one person's head.
- We only take on as many firms as we can do properly, and we'll tell you the timings before we start.