Every job, every deadline, every owner — visible
Your tax software files the return. Your ledger keeps the books. FigsFlow runs everything in between — every job broken into the right tasks, every statutory deadline assigned to a real owner, every review tracked from first draft to partner sign-off. Nothing depends on a spreadsheet, a sticky note, or someone remembering to ask.
See how a job actually moves through your firm
Click through a real job — from the day it is created to the day it is filed — and see exactly where FigsFlow keeps a task from slipping through.
The job exists before anyone opens their inbox
The client accepts the proposal. FigsFlow creates the job on the same client record, generates the task list from your service template, and assigns an owner — with no re-entry and no second system.
Every task has a name against it, not a team
Tasks and sub-tasks carry their own owner and due date. A parent task cannot be closed while a sub-task underneath it is still open, so a job is never reported complete on the strength of the top-level box.
Work that is not ready cannot be marked done
The review task depends on the reconciliation. Until that clears, the reviewer can open it and prepare, but cannot complete it. The moment the dependency clears, the assigned person is notified that the task is ready — nobody has to check.
The review leaves a record, not just a tick
The preparer cannot submit until every checklist item is checked, and the reviewer completes their own checklist before approving. If the work is not error-free, the reviewer classifies the error and their notes create a correction task automatically.
Next year is already on the calendar
The job closes and the recurrence carries it forward. Next year's job appears on schedule whether or not this one finished on time, and the full history of when every job was created, completed and filed stays on the client record.
You should not have to ask whether the CT600 review is actually done
It is Thursday, the filing deadline is Monday, and the managing partner still does not know whether the balance sheet review is finished, sitting in someone's inbox, or already signed off with nobody updating the tracker.
“I sent that over for review on Tuesday.”
“I never got it. I thought it was still with the preparer.”
“Complete.” Last edited two weeks ago, by someone on leave.
Three people, three different answers, and an engagement letter that said this would be done a fortnight ago. That is not a staffing problem. It is a visibility problem — the same one every growing practice hits the moment the work stops fitting inside one person's head.
One record, from the signed engagement letter to the filed return
A job does not start with a blank task list. When a client accepts a proposal, FigsFlow creates the job automatically — no re-entry, no second system. Every task, deadline and review then lives on the same client record your team already uses for time tracking, capacity planning and firm-wide reporting.
The client signs. This is the only moment anyone types anything.
The job appears on the client record with its task list already built.
Start a timer on a task and the hours reach the timesheet with no manual entry.
The same record feeds capacity planning and firm-wide reporting.
Break every job down until nothing can be missed
Every job can be broken into tasks and sub-tasks, down to the level your review process needs. A parent task cannot be marked complete while any sub-task remains open. Tasks are generated from your firm's service templates, or added by authorised team members when something changes — with a note explaining why.
“Done” actually means done.
The parent stays open because one sub-task is open. Nobody can close it early, and nobody has to notice.
Staff can open blocked work and prepare. They cannot mark it complete before the work it depends on is done.
Keep every job moving in the right order
Some work has to happen before something else can start. FigsFlow makes those dependencies explicit and blocks the dependent task automatically, rather than sending a reminder and hoping.
As soon as the dependency clears, the assigned person is notified that the task is ready.
Make every checklist a hard gate
Attach a checklist to any task and FigsFlow makes completion mandatory. The preparer cannot submit the task for review until every item is checked, and the reviewer must complete their own checklist review before approval.
Nothing moves forward until the checklist is complete.
Turn every review into a quality record
Reviewers confirm whether work is error-free. If it is not, they classify the error by type, severity and affected area, and their notes automatically create a correction task for the original preparer. Serious errors escalate on their own.
The task closes and the next stage of the job unblocks.
A correction task is created for the preparer, carrying the reviewer's notes.
Serious errors are raised without anyone having to decide to raise them.
Every review becomes a record your firm can learn from — not just a sign-off.
Set recurring work once. Never rebuild it again.
Set the recurrence once — annual, quarterly, monthly, or whatever the engagement requires — and FigsFlow creates each job on schedule. A late or unfinished job never holds up the next one. Statutory dates behave the same way, and you can see how they are handled on the HMRC deadlines page.
Twelve months of upcoming work at a glance, with a complete history of when every job was created, completed and filed.
Built for practices that have outgrown spreadsheets and shared inboxes
FigsFlow is not a tracker bolted onto a spreadsheet. It is accounting workflow software built to move the work forward on its own — it does not just track the work, it moves the work forward.
Built to fit how your practice actually runs
Whatever size practice you run, this is accounting workflow software built around how the work actually moves.
Everything a small team needs to run jobs on schedule — nothing it does not.
See the platform →Standardise how jobs run before headcount makes inconsistency expensive.
See the platform →Jobs, tasks and reviews run inside your own Microsoft tenant, under your IT team's existing policy.
Documents in your SharePoint →Works inside the stack you already run
FigsFlow's job and workflow data lives alongside the tools your practice already uses day to day.
Entra ID single sign-on, Outlook, Teams, SharePoint and Microsoft Graph.
The ledger stays where it is. Billing runs through it.
Collection rails you choose, not ones you are locked into.
For practices that do not run on Microsoft 365.
Company data and filing dates pulled onto the client record.
API and webhooks where a direct connection is not the answer.
Built inside working practices, not in a lab
FigsFlow was built inside two working practices — the workflows came from partners running real deadlines, not from a product roadmap. Every module started as something a firm needed on a Tuesday.
Founding-customer programme
We are taking on a small group of UK firms this quarter — a direct line to the product team, your workflows shaped into the template library, and pricing locked for as long as you stay.
Ask about the founding group →What a firm of one pays, and what is live in the UK today
Priced per user, per month — for a firm of one, that is a single seat.
No implementation fee, no onboarding package to buy, no minimum seat count. See FigsFlow plans and tiers →
Accurate as of 01/09/2026 · United Kingdom. Ask on a demo call for anything not listed.
Everything a job connects to
Jobs and tasks are one piece of FigsFlow — here is what they connect to.
The scope on the signed letter is the scope the job is built from.
See engagement letters →Statutory dates as first-class objects, not tasks somebody remembers to create.
See HMRC deadlines →Ready to see every job run like this?
Every job you run through FigsFlow feeds straight into your firm's workflow templates and time and billing — so the next job starts faster, and every hour worked is already accounted for.