How to leave a five-tool practice stack without losing the month

Search demand for how to leave a five-tool practice stack is a polite way of saying the firm already runs a close in five places and is tired of arguing about which number is true. I write the impolite version because the polite version never lands opening WIP.

Sevak Girard here. I built Ficary to post the obvious and hold leftovers. I said the growth-engine line on the record in Accounting Today, July 2025. The desk version is simpler: automate the obvious, hold the leftover. A five-tool pile is leftover by construction.

A plain definition

Leaving a five-tool practice stack means you name every system that currently holds clients, work, time, bills, or files, you pick an as-of date, and you land opening WIP and AR that a signer can inspect. If you cannot point at the pile, you defined a mood. Moods do not survive review.

Five is a typical count, not a badge. Some firms will tell you three. Some will admit ten once you sit with the ops lead. CRM, time, billing, tax workflow, portal, spend, bank, and a dashboard tool is a normal Wednesday. The number that matters is not how many logos hang in the sidebar. The number is how many as-of stories you are running.

Open data migration for practice software if the leftover is opening numbers. Open what to export before you switch if the leftover is the file you still cannot name. Open opening WIP when you switch systems if someone suggested starting at zero. Money page: practice software. Early access is a conversation: request early access.

Where firms hide the pile

They hide it in “we already have a CRM.” They hide it in a dashboard that looks like a close. They hide it in a time app that never posts. They hide it in a portal nobody opens. They hide it in a tax workflow that will not speak to WIP. The hide is the bug.

A partner will say the stack is under control because everyone has a login. Control is not a login. Control is one leftover list with a reason, an owner, and a date. If unbilled work lives in one product, aging lives in a second, and the invoice lives in a third, you do not have a practice. You have a relay race.

I watch firms add a sixth tool to “connect” the five. That is how the pile grows. A connector is not a close. A dashboard that reads five exports is not as-of money. If August is not closed, a pretty visual is not the product.

Inventory before you promise a date

Write the stack on one page. Not a vendor bake-off. A job list.

1. Where do clients live, including prospects who are not billed yet.
2. Where does work live, including jobs that have time and no letter.
3. Where does time live, including the date it was incurred.
4. Where does unbilled money live, and whether that date survives an export.
5. Where does AR live, and whether it ties to the same clients.
6. Where do files and requests live.
7. What is leftover — the bank, payroll, spend, or a report someone still pastes into slides.

If a row has no export, write “cannot export” and a recovery: named report, API, or omit that room this week. Do not invent a File menu. I have seen cutovers die on a project surface that the seller swore existed.

Clients first, then work, then time. That order is not taste. Work without clients is an orphan. Time without work is a pile of hours with no job to age. Opening WIP that hits current-period revenue is how you lie to yourselves in month one.

What to keep, what to leftover, what to refuse

Keep the jobs the pile was pretending to do: clients, work, time, leftover inbox, a posted ledger, a letter that gates money. Leftover the custom columns that do not have a room yet — they become fields, not a second schema. Refuse mail import. Refuse staff logins from a user table. Email and calendar reconnect from the suite you already pay for. A CRM user is a name on a time row, not an IdP.

Refuse starting at zero. Refuse importing ten years of noise to look complete. Refuse a dashboard as the definition of done. The proof is one job you can open, one invoice you can send, or one report that matches the books on a named date.

If the firm also runs owner books for clients, that is the same product on a different tenant, not a sixth practice tool. The close still has to tie. See CAS technology stack if the leftover is client accounting wearing a practice costume.

The metric

Count of systems named versus rooms landed this week is the number I want on a Monday. Then opening WIP tied out versus rows imported. Same as-of as AR. Not a composite score. Not a smile. If you cannot read both numbers without a meeting, the pile is still in charge.

Staff the leftover by type. If the same two people recode every import skip, you have heroes. Heroes leave. The inbox should route: missing client, missing job, missing date, custom column, count mismatch. A human commits. Software proposes.