Price consistently, without discounting by instinct
Set your fees once — fixed, hourly, per unit, banded, or calculated from the client’s own numbers — and apply them the same way on every quote, every renewal and every partner’s Tuesday afternoon.
Set a price. Watch it lock in.
Pick a pricing method, move the inputs, and watch the fee recalculate. This is the same engine your practice would run — change an input and every figure below it moves with it.
A flat agreed fee for the engagement, whatever the transaction count.
Nothing here is generated. Change an input and the same rule recalculates — the rule itself only changes when your practice changes it.
Illustrative rates · fictional client · your practice sets its own
Same service, different fee, and nobody’s checking
Two partners quote near-identical bookkeeping engagements three weeks apart — same transaction volume, same two entities — and the fees don’t match. Neither is wrong. Neither is working from a shared number.
Monthly bookkeeping, around 240 transactions, two entities. Priced from memory of the last one like it.
Monthly bookkeeping, around 250 transactions, two entities. Priced from a different memory, on a different Tuesday.
Do you fee the same?
See how this gets fixed →The same number, from quote to invoice
Your price isn’t typed into a proposal, a pipeline record and an engagement letter — it is computed once here, and every document downstream displays it. When the client signs, that same number becomes the invoice.
Your rate card runs. This is the only place the figure is decided.
The engagement value updates itself. Nobody keys it in a second time.
Same fee, same scope, same wording — assembled, not retyped.
Signature raises the bill. No re-entry, no rounding drift.
One pricing engine. Every pricing model.
Price any service your way — fixed, hourly, per unit, by price band, by volume, on a graduated scale, as a percentage, or with a formula built from the client’s own numbers. Each rule is written in plain English, so your team can see exactly how a price was reached.
One agreed fee for the engagement, however the work moves.
A rate per hour, by grade or by service, applied the same way each time.
A rate per transaction, entity, employee or return — whatever the work counts in.
A single fee for everything inside a range, stepping at the boundary.
The unit rate itself falls as the count rises, across the whole quantity.
Tax-band style — each slice priced at its own rate, then totalled.
A percentage of a figure the client already has, such as turnover or payroll.
Your own expression, built from the client’s numbers and your own inputs.
No guesswork. FigsFlow applies the same pricing rules every time. AI can explain how a price was reached, but it never decides what the price should be.
Build offers clients can compare and adjust
Create one offer with side-by-side tiers and optional extras. Use fixed prices, or calculate each tier from the client’s own numbers so the top tier lands at the right figure for that client rather than the same figure for everyone.
- Monthly bookkeeping
- Bank reconciliation
- Quarterly VAT return
- Payroll
- Quarterly advisory call
- Everything in Essential
- Payroll, up to 12 employees
- Statutory accounts and CT600
- Quarterly advisory call
- Cash-flow forecasting
- Everything in Complete
- Cash-flow forecasting
- Monthly advisory call
- Named partner contact
- Priority filing window
Illustrative tier fees for a fictional client. These are the figures your practice sets from its own rate cards — each tier can be a fixed price or a calculation.
Protect your pricing before a discount goes too far
Set a minimum fee floor for discounts and surcharges, so FigsFlow warns your team before a price falls below the limit — not after the client has seen it.
Need an exception? Role-based permissions control who can override a calculated price, and every override is logged.
The warning arrives before the client does
The floor is checked as the discount is typed, inside the quote — not at review, not at invoice, and not in a conversation with a client who has already been told a number.
Role-based permission, set once. Anyone without it sees the block rather than a silent success.
The calculated price, the price sent, who authorised the gap and when. It lands on the audit trail rather than in somebody’s memory.
Change your pricing once. Update every engagement that needs it.
Apply an increase or a decrease across the engagements priced from a rate card, instead of editing clients one at a time in January.
Move a rate card and every engagement priced from it moves with it. You choose which engagements are in scope before anything applies.
Set an uplift once and it applies at renewal — no annual round of individually edited fees, and no client quietly left on 2023 prices.
When pricing changes after signature, the original stays intact — the change becomes a separate signed variation rather than a silent edit to a document the client already agreed.
The pricing engine behind every quote you send
Every quote your practice sends — on a call, over email, embedded on your site — comes from the same engine, using the same rules. Nothing retyped, nothing reinvented for whoever happens to be in the room.
One number, computed once, inherited by every document downstream.
An interactive quote the client explores themselves, embedded on your own site.
An accurate quote delivered in the room, during the actual conversation.
Pricing knowledge that lives in the system, available to a new joiner from day one.
Built for practices your size — whichever size that is
One person, every role — including the one who sets prices. Set a fee once and stop re-deriving it between client calls.
No implementation project and no operations hire — set fees once and the whole team quotes the same way from day one.
Standardise pricing before headcount outpaces it. Rate cards and approval limits keep every new joiner inside the same guardrails.
Every partner, every office, one set of pricing rules — permissioned overrides and a trail your IT team will sign off on.
Pricing connects to the tools you already bill and collect with
An invoice raises the moment a client signs, synced both ways, so the fee that was agreed is the fee that gets billed.
The client pays from the quote or the portal, by card or Direct Debit. You choose the rail; we don’t lock you into one.
Stays exactly where it is. FigsFlow prices and runs the engagement around your filing software rather than inside it.
What FigsFlow itself costs, and what’s live in the UK today
FigsFlow is licensed per user — for a sole practitioner that is a single seat. Current UK plan prices are on the pricing page rather than here, so this page can’t go out of date.
No implementation fee, no onboarding package to buy, no minimum seat count.
| Capability | United Kingdom |
|---|---|
| Pricing, quoting, proposals and engagement letters | Live |
| Eight pricing methods and rate cards | Live |
| Fee floors, permissioned overrides and the override log | Live |
| Client due diligence and AMLIdentity verification, screening and risk assessment. | Live |
| Companies House and Irish CRO lookup | Live |
| Xero, QuickBooks Online, Stripe, GoCardless | Live |
| Native invoicingBilling runs through Xero or QuickBooks Online today. | Roadmap |
| Submitting MTD quarterly updatesStays with MTD-compatible software on HMRC’s list. | Not available |
| Filing to Companies HouseStatutory filing stays with WebFiling or your filing software. | Not available |
| Tax and filing software integrationsNothing to announce. | Roadmap |
Availability shown for the United Kingdom as at 01/09/2026. Ask on a demo call for anything not listed.
Pricing doesn’t work alone — here’s what sits either side of it
Where the fee sits in the sequence — between the due diligence that gates the letter and the jobs that start on signature.
The signed agreement that fixes the fee. The letter displays the calculated number rather than a retyped one.
Where an override lands — the calculated figure, the figure sent, who authorised it and when.
Pricing software for accountants, answered plainly
What pricing methods does it support?
Fixed fees, hourly rates, per-unit pricing, price bands, volume rates, graduated (tax-band-style) rates, percentage-of-a-figure pricing, and formula pricing tied to a client’s own numbers. All eight are defined in plain English inside one engine, so the rule behind any quote is readable rather than buried in a spreadsheet.
Does FigsFlow decide what to charge a client?
No. Every price is calculated by rules your practice sets. AI can explain how a number was reached; it never generates or approves one. Overriding a calculated price requires role-based permission and is logged against the client record.
Can we stop people discounting below a certain point?
Yes. Set a fee floor on the rate card and the check happens as the discount is entered. Below the floor, the quote is blocked until someone with override permission authorises it, and the authorisation is recorded with the calculated figure alongside the figure sent.
What happens when we put our prices up?
Move the rate card and every engagement priced from it moves with it, with you choosing which engagements are in scope first. A renewal uplift can be set once and applied automatically at each renewal rather than edited client by client.
What if the fee changes after the letter is signed?
The signed document is not edited. The change is issued as a separate signed variation, and the original stays readable exactly as the client agreed it — which is what a file review or a fee dispute actually asks to see.
Does it replace Xero or QuickBooks?
No. FigsFlow integrates with Xero and QuickBooks Online rather than replacing either. It sits alongside your bookkeeping software and handles how you price, quote and take clients on, raising the invoice into your ledger when the client signs.
Set the price once. Let everything downstream inherit it.
Bring a client you have quoted twice and never quite explained the difference on. We will build the rate card live and show you what it would have produced both times.
All fees, rates and tier prices on this page are illustrative examples for a fictional client, shown to demonstrate how the pricing engine works. They are not FigsFlow’s own prices and are not a quotation. Capability statements checked on 01/09/2026 and should be re-verified before release.