Why FigsFlow · United Kingdom
Built by people who file against these dates.
One record from first enquiry to payment. The proposal becomes the engagement letter, the engagement letter creates the work, and the work is what you bill — not five tools doing one job badly.
G2 reviews
Google reviews
Verified reviews
Trustpilot reviews
- Your tenantDocuments are written into your own SharePoint. No migration, no second archive.
- DeterministicAML scope and risk scored from coded rules. A person still signs it off.
- One recordScope, letter, work and fee reconcile against each other, not from memory.
Trusted by the best
01 — The actual problem
Practices rarely lose time to complexity.
They lose it to the seams between tools. Scope agreed in one place, the letter signed in another, the work planned in a third, and the fee reconciled from memory at year end.
Onboarding is still manual
The same client details typed into a proposal, a letter, a checklist and a job list.
Read more → 02Nothing’s joined up
Five subscriptions, five logins, and no single place that knows the whole client.
Read more → 03The process lives in people’s heads
It works until someone is on leave, leaves, or a new joiner has to guess.
Read more → 04You can’t see where the money goes
Which clients are worth the fee, and which are quietly funded by everyone else.
Read more →02 — The difference
One unbroken line, from enquiry to payment.
Each step inherits from the one before it. Nothing is re-keyed, and nothing is agreed in one system then delivered against a different version of itself.
- 01EnquiryCaptured against a client record, not a mailbox.
- 02Scope & pricePriced from your own rules, not a gut feel.
- 03Engagement letterReflects exactly what was sold.
- 04Work createdJobs and deadlines generated from the services signed.
- 05DeliveryRecords chased, reviews logged, evidence retained.
- 06BillingBilled against what was agreed and what it cost.
The engagement letter creates the work, and the work is what you bill. That is the whole argument.
Inside a working practiceEvery workflow in it started as somebody’s problem on a Tuesday.
How FigsFlow was builtThe people behind it
Built inside a practising UK firm.
FigsFlow was built inside working practices, by people who had to run them — people who file against these dates, not a script.
- PartnersReporting
The numbers partners actually read, not a year-end reconstruction.
- Your MLROAML
Escalations routed to them. FigsFlow presents the evidence; a person signs it off.
- The teamMicrosoft 365
Outlook, Teams and SharePoint — where the work is already discussed.
03 — Being precise
What FigsFlow does, and what it does not.
Compliance software that overstates itself is worse than none, because it moves a liability you still carry. So, plainly:
It does
- Schedule recurring obligations as work, per client
- Chase records and documents before a period closes
- Determine AML scope and risk score deterministically, from coded rules
- Route escalations to your MLRO and hold the decision
- Track verification status against confirmation statement dates
- Keep an immutable, exportable audit trail of who did what, when
It does not
- Submit quarterly updates or returns to HMRC — your filing software does that
- Claim to be HMRC-recognised compatible software
- Make your practice compliant. The MLR 2017 obligations remain yours
- Make the risk decision. It presents the evidence; a person signs it off
- Replace your professional judgement on scope or engagement terms
- Become another place your client files live
04 — Microsoft, properly
Your documents stay in your SharePoint.
FigsFlow writes into your own tenant, under your retention policy, with your access controls. The files are still there in Explorer on Monday morning — because they never left.
How the integration works →- Entra ID single sign-onYour existing MFA and conditional access apply. No separate password to govern.
- Outlook, not a copy of OutlookClient threads sit on the client record without leaving the mailbox.
- Teams where the work is discussedJob notifications land in the channel your team already watches.
- A shorter due diligence reviewIf your IT governs identity and retention centrally, FigsFlow inherits it rather than asking for an exception.
05 — The platform
Everything a UK practice runs on. One record underneath.
Six groups, one client record — the sale, the compliance work, the jobs, the client’s side of it, the Microsoft stack it lives on, and the numbers partners actually read.
04Work with clients
06The numbers
06 — Honestly compared
Why not just add another tool?
Sometimes you should. Here is where each option genuinely wins, and where it stops.
A point solution
Best when one step hurts and the rest is fine.
You keep the seams. The proposal still does not know what the job list is doing, and the fee still gets reconciled by hand.
Generic project software
Best when your work is genuinely bespoke and has no statutory calendar.
A UK practice year is not bespoke. Year ends, staggers and confirmation dates have to be first-class objects, not tasks somebody remembers to create.
FigsFlow
Best when the handoffs are the problem, not any single step.
One record end to end, sitting on the Microsoft stack you already pay for. It will not file your returns, and it does not pretend to.
The questions we get asked
Is FigsFlow HMRC-recognised software for filing?
Does it replace Xero or QuickBooks?
Where do our client documents actually live?
Will FigsFlow make our practice AML compliant?
Do we have to change how our team already works?
Most of our growth is advisory, not compliance. Is this still relevant?
The invitation
Bring your messiest client to the demo.
Thirty minutes with someone who has filed against these dates, not a script. Bring the client with the trust, the SPV, the missing records and the fee that crept. If FigsFlow cannot hold that one on one record, do not buy it.