The register your advice files have never had.
GOAT Work sits alongside the planning software your firm already runs. It takes the work around the advice — meeting prep, file notes, documents, the reviews quietly falling due — and puts it in one place every adviser and paraplanner can read at a glance.
| Client | Contact | Review due | State |
|---|---|---|---|
Margaret Okonjo Pension phase — check minimum drawdown |
m.okonjo@example.com |
12 Jun 2026 46 days ago |
Overdue |
Daniel & Priya Whitlock Insurance review deferred once |
dwhitlock@example.com |
14 Aug 2026 in 17 days |
Due soon |
Tomas Berger SMSF — accountant copied on advice |
t.berger@example.com |
03 Feb 2027 in 6 months |
Current |
Ayesha Rahman Redundancy strategy signed 09 Jul |
a.rahman@example.com |
21 Mar 2027 in 8 months |
Current |
The stripe down the left of a row is the review state. Nobody has to read a date to see where the book stands.
Three things, done properly.
Reviews surface themselves
Every client file carries its next review date, and the register colours itself against it. The dashboard opens on what is overdue rather than on a chart of how busy you have been.
File notes that count
A note records what was discussed, what was advised and why — then cannot be edited or deleted by anyone, including whoever wrote it. That is the only version worth having when someone asks two years later.
Documents that stay put
Files sit in private storage, filed against a client. Opening one mints a link that dies two minutes later, so a URL left in a chat thread stops being a hole in a client file.
This is version 0.1.
It is a foundation, deliberately. Client records, documents, file notes, sign-in and an audit trail all work. The advice production itself — drafting a Statement of Advice from the file — is the next piece of work, and it is being built on top of this rather than alongside it.
Not a replacement
Your modelling, product research and lodgement stay where they are. This improves the work that surrounds them, which is where the hours actually go.
Your data, your database
Everything lives in your own Supabase project, under your account, with access rules enforced by the database rather than by the app. No client information is stored on the device you are reading this on.
Built to be handed over
No build step, no bundler, no framework churn. The folder that runs is the folder you deploy, which is what keeps a small product maintainable for years rather than months.
Start with one client file.
Create an account, add a client, write the first note. That is the whole of getting started.
Create an account