Why FigsFlow
Built by people who file against these deadlines.
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.
- No migration — documents stay in your own tenant
- Priced and scoped from rules you set
- Regional editions for the UK, US, Canada and Australia
- 01EnquiryOn the record
- 02Scope & priceYour own rules
- 03Engagement letterWhat was sold
- 04Work createdJobs & deadlines
- 05DeliveryReview logged
- 06BillingAs agreed
Documents written into your own cloud storage
Risk scored from coded rules, signed off by a person
Illustrative interface
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.
- 01
Onboarding is still manual
The same client details typed into a proposal, a letter, a checklist and a job list.
- 02
Nothing is joined up
Five subscriptions, five logins, and no single place that knows the whole client.
- 03
The process lives in people’s heads
It works until someone is on leave, leaves, or a new joiner has to guess.
- 04
You cannot see where the money goes
Which clients are worth the fee, and which are quietly funded by everyone else.
None of these is a software problem on its own. Together they are the reason a profitable job still feels like a scramble.
See how the pieces connect →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.
- 01
Enquiry
Captured against a client record, not a mailbox.
- 02
Scope & price
Priced from your own rules, not a gut feel.
- 03
Engagement letter
Reflects exactly what was sold.
- 04
Work created
Jobs and deadlines generated from the services signed.
- 05
Delivery
Records chased, reviews logged, evidence retained.
- 06
Billing
Billed 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
03 — The people behind it
Built inside a practising firm.
FigsFlow was built inside working practices, by people who had to run them — people who answer to the same deadlines, the same regulators and the same clients you do.
Every workflow in it started as somebody’s problem on a Tuesday.
Not a feature on a roadmap- Reporting
Partners
The numbers partners actually read — fees, margin and capacity as the work happens, not a year-end reconstruction.
- AML
Your compliance lead
Escalations routed to your MLRO, AML officer or equivalent. FigsFlow presents the evidence; a person signs it off.
- Microsoft 365
The team
Outlook, Teams and SharePoint — where the work is already discussed, not a sixth place to check.
04 — 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 compliance lead and hold the decision
- Track verification status against the registry and filing dates you set
- Keep an immutable, exportable audit trail of who did what, when
It does not
- Submit returns or periodic updates to any tax authority — your filing software does that
- Claim to be recognised filing software in any jurisdiction
- Make your practice compliant. Your regulatory 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
Regulatory detail differs by jurisdiction. Where a rule is local — registry dates, AML thresholds, filing deadlines — FigsFlow holds it as a setting you control, not an assumption baked into the product.
05 — 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.
Entra ID single sign-on
Your existing MFA and conditional access apply. No separate password to govern.
Outlook, not a copy of Outlook
Client threads sit on the client record without leaving the mailbox.
Teams where work is discussed
Job notifications land in the channel your team already watches.
A shorter due diligence review
If your IT governs identity and retention centrally, FigsFlow inherits it rather than asking for an exception.
06 — The platform
Everything a 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 stack it lives on, and the numbers partners actually read.
Win the work
- Proposals
- Pricing and quoting
- Engagement letters
- Onboarding suite
Run the work
- Jobs, tasks and deadlines
- Workflow templates
- Team and capacity
- Timesheets and billing
Compliance
- Risk assessment and scoring
- Statutory deadline tracking
- Verification and evidence trail
Work with clients
- Client portal
- Forms and requests
- Meetings and scheduling
- Client mobile app
Your stack
- Microsoft 365 and Outlook
- Documents in your SharePoint
- Google Workspace
- Payments, Zapier and the API
The numbers
- Proposal and letter insights
- Reporting and analytics
- Practice dashboard
07 — 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 practice year is not bespoke. Year ends, period staggers and registry 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 stack you already pay for. It will not file your returns, and it does not pretend to.
Questions
The questions firms actually ask.
Is FigsFlow recognised filing software?
No, and it does not claim to be. FigsFlow schedules and manages the workflow around your filing obligations — the recurring work, the records chasing, the review and the audit trail. The submission itself is made by your own tax or filing software.
Does it work in my country?
FigsFlow runs regional editions for the UK, US, Canada and Australia. The rules that differ by country — tax year, registry dates, AML thresholds, currency and letter templates — are settings you control rather than assumptions baked into the product. If you operate somewhere we do not yet have an edition, say so on the demo and we will tell you plainly what works today and what does not.
Does it replace Xero or QuickBooks?
No. FigsFlow runs the practice; your ledger software runs the books. It connects to your accounting stack rather than duplicating it.
Where do our client documents actually live?
In your own Microsoft tenant, in your SharePoint or OneDrive library, under your retention policy and access controls. FigsFlow does the filing, naming and syncing into the folder structure you already use. There is no migration and no second archive to search.
Will FigsFlow make our practice AML compliant?
No software can do that, and any that says otherwise is moving a liability you still carry. Your obligations under your own jurisdiction’s anti-money-laundering regulations remain yours. FigsFlow determines scope and risk score from coded rules, assembles the evidence, and routes escalations to your compliance lead — but a person makes the decision and signs it off.
Do we have to change how our team already works?
Less than you would expect. Sign-in happens through Entra ID with your existing MFA and conditional access. Mail stays in Outlook. Notifications land in the Teams channel your team already watches. Documents keep your existing folder and naming conventions.
Most of our growth is advisory, not compliance. Is this still relevant?
Arguably more so. Advisory work is quoted rather than repeated, so it needs scoping and pricing discipline, an engagement letter that matches what was sold, and budget-against-actual afterwards to see whether it paid. It also competes with compliance for the same senior people.
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 holding company, the missing records and the fee that crept. If FigsFlow cannot hold that one on one record, do not buy it.
- The trust
- The holding company
- The missing records
- The fee that crept
- One record, or don’t buy it
Screen-shared, using your services, your client mix and your deadlines. You will see where FigsFlow fits, and where it does not.