You're offline — showing the last version we saved.
Tech stack · Works with FYI

The FYI stack

FYI is a document and process system built for accounting practices: client documents, email and workflow automations in one place, filed against the client. A practice that runs FYI has decided that the document is the unit of work and that filing should be automatic. The stack around it should feed that filing system, not compete with it.

Updated 3 September 2026, reviewed annually. By Trent McLaren.

14 tools listed, grouped by what each one is for

Ledger & accounting that works with FYI

2 ledger and accounting tools · all ledger and accounting tools

Payments & billing that works with FYI

1 payments and billing tool · all payments and billing tools

Reporting & dashboards that works with FYI

2 reporting and dashboards tools · all reporting and dashboards tools

Practice management that works with FYI

2 practice management tools · all practice management tools

Document management that works with FYI

2 document management tools · all document management tools

Proposals & engagement that works with FYI

2 proposals and engagement tools · all proposals and engagement tools

Signing & verification that works with FYI

4 document signing and verification tools · all document signing and verification tools

Marketing & client growth that works with FYI

1 marketing and client growth tool · all marketing and client growth tools

1 corporate and legal tool · all corporate and legal tools

Guide

Building a practice around FYI

What FYI is the record of

In an FYI practice, FYI is the record of what was sent, received and signed: the engagement letter, the authority, the financial statements, the email that changed the scope. Every other tool should either produce documents that file into it or read client details from it. A signing tool that returns the executed letter into the client's FYI cabinet is respecting the record; one that keeps signed documents in its own portal is building a second archive.

What to add first

The practice-management or job system FYI reads client and job data from, because FYI's automations key off jobs and client status. Then signing and identity, because the executed documents are FYI's reason to exist. Then the ledger and tax tools whose outputs (statements, returns, workpapers) need filing. Collection tools that gather documents from clients earn their place next, since a document requested through them can land in FYI already filed. Meeting assistants last, once the client record is trusted.

The grid on this page lists the directory tools that state an FYI integration, grouped by category.

Automations and the risk of silence

FYI's automations are the value and the hazard: a well-built automation files, notifies and moves a job without anyone touching it, and a badly built one does the wrong thing silently for a quarter. Firms that run FYI well name an owner for each automation, log what it did, and review the log monthly. Tools added to the stack should be checked for whether they trigger FYI automations as intended, or bypass them.

What FYI does not do

It is not a ledger, a tax engine, a proposal tool or a signing platform, and it is not the job-capacity view a practice-management system gives. It connects to those. The order above is the order in which the connections pay back.

Pricing and the document count

FYI is priced per user per month; the tools around it vary between per user, per client and per document. A signing tool priced per envelope and a collection tool priced per request scale with the firm's volume, not its headcount, which suits a practice growing its client base faster than its team. The directory records what each vendor publishes; it does not tell a firm what to charge.

Common questions

FYI integrations, answered

What software integrates with FYI?
The grid on this page lists every directory tool that states an FYI integration: practice systems, signing and identity tools, ledgers and tax tools, collection tools and assistants. Counts change as vendors and firms add integrations.
What should a firm connect to FYI first?
The system FYI reads jobs and clients from, then signing and identity, then the ledger and tax tools whose outputs need filing, then document collection, then meeting assistants.
How does a firm keep FYI automations safe?
Name an owner per automation, keep the log, review it monthly, and check that any new tool triggers the automations it should rather than bypassing them.
Is this a comparison of FYI against other document systems?
No. The Firm does not publish comparison content between tools. This guide is about the stack around FYI for firms that already run it.
Does The Firm charge vendors to be listed?
No. Listing is free and claiming a listing is free. Paid placement is labelled as such, and every outbound link to a vendor carries a sponsored attribute. Paying never changes how a tool is described.
Other integrations
Browse by category
Get your free seat →

AI in Practice Summit returns. What worked, what's next: two days on what AI actually did for firms this year, and where it goes in 2027. 11–12 November 2026, virtual and free.