For CPAs, enrolled agents and bookkeepers

Keep your subscriptions. I build what they don’t do.

Your tax software prepares the return. Your practice tool tracks the jobs, and your portal holds the files. The work that falls between them still lands on your staff: the clients who never open the portal, the engagement letters nobody signed, and the calls in March asking where a return is. I build those pieces to fit beside what you already pay for.

Small CPA firms, enrolled agents and bookkeeping practices, from one person up to about 15.

Sample app, invented data · 10 second loopA client document checklist. Shown for an invented firm, Sample CPA firm, and an invented client, Jordan Avery. On the left is Jordan’s checklist, 2025 Tax documents, with 2 of 6 done: the W-2 and the 1099-INT are received. Jordan taps Upload on the 1098 and a phone photo goes up, so it shows Received and the count moves to 3 of 6. Jordan marks the childcare receipts Not applicable, and the count moves to 4 of 6. On the right, the staff list updates to 2 needed for Jordan, beside one client who is complete and one with 2 needed. The reminder log shows the last reminder listed only the two still missing, the property tax bill and the donation receipts, and that reminders stop when all 6 are in.
What firms run into

The portal holds the files. The chasing still lands on you.

A client says the documents went up, and the preparer’s side shows nothing. Preparers say it in their own words on public forums, and the trade press says the firms pulling ahead are the ones that connect their tools.

None of that means the software is bad. It’s built to do the returns and the books the same way for every firm. How you chase documents, sign up a client and answer the “is it done yet?” call is different in every office, and that’s the part I build.

Short quotes from public pages, as they read on November 7, 2026.

What I build

Six things your practice software leaves to you

Keep your subscriptions. I build what they don’t do. QuickBooks Online, Xero, Drake, UltraTax, Lacerte, TaxDome, Karbon, Canopy, SmartVault, Liscio or Financial Cents all stay where they are. Each of these is built to fit around them, and you can start with just one.

  • A document chase that files itself

    A request list per client for each tax year. Reminders by email and text list only what’s still missing, and they stop when it’s all in. The client snaps a photo of a W-2 on their phone, and it’s filed into the folder or system you already use.

  • An engagement letter tracker

    The year’s letters go out from your client list, and the unsigned ones get chased for you. A job stays marked do not start until its letter is signed, so nobody begins work without one.

  • A “where’s my return?” page

    Each client gets a page that shows where their return stands, fed from the job status in your practice tool. They see the stage, not your notes, and your phone rings less in March and April.

  • A monthly close pack

    For bookkeeping clients: one page from their QuickBooks Online or Xero data, in your firm’s branding, that an owner can read in a minute. The questions you still need answered are listed at the bottom.

  • One intake form for every system

    A new client fills in one form, and it creates them in your practice tool, your books platform and your portal at once. Nobody types the same name and address three times.

  • A Section 7216 consent tracker

    Which client signed which consent, for which recipient and purpose, and when it runs out. You’re reminded before one expires, not after.

Where most firms start

Paper Chase: the documents come to you

Your portal is fine. The trouble is the clients who never open it. Paper Chase is the part that goes after them, so nobody on your staff spends March sending reminders by hand.

Each client gets a list for the tax year, started from what you asked them for last year. They can upload each item from a phone or mark it not applicable. The reminders go out on a schedule by email, and by text to clients who agreed to texts. Each one lists only what’s still missing, and they stop on their own when the last item is in.

Every file goes into the folder or system you already use, named the way you name things. Your staff see one list of who’s done and who’s behind, without opening every client.

The best time to set it up is before the season, not in the middle of it.

Rules it’s built around

Your clients’ documents come with rules

Section 7216 consent. A tax preparer needs the taxpayer’s written consent before using or sharing their return information for most other purposes. The consent names who gets it, what for and which information. If it doesn’t say how long it lasts, it lasts one year from the day it was signed. That’s the date the consent tracker keeps for you.

The FTC Safeguards Rule. The FTC names tax preparation firms among the businesses the rule covers. It asks for a written information security program and for oversight of the service providers who handle client data. An event that exposes 500 or more people has to be reported to the FTC within 30 days.

Your state’s breach law. Every state has one, with its own deadlines. In Florida, under s. 501.171, a service provider has to tell the business within 10 days of a breach, and the business has to tell the people affected within 30 days.

None of this is new to you. What I can do is build so it’s easier to keep: client files stay in your firm’s accounts, every action goes in a log, and you get in writing how your system is set up.

From Treas. Reg. 301.7216-3, the FTC’s guide FTC Safeguards Rule: What Your Business Needs to Know and the 2025 Florida Statutes, s. 501.171, read on November 7, 2026. This is a summary, not the whole text. I’m not a lawyer or a tax advisor, and this isn’t legal or tax advice, so check what applies to your firm with your own counsel.

One person

You get me, not a ticket queue

Every firm runs a little differently, and it’s easier to build the right thing after seeing how your front desk, your preparers and your bookkeepers actually work. I do that over a screen share, wherever you are, and if the job needs hands on site, I’ll travel to you for a few days.

When you call, you get me. The same person who builds it is the one who fixes it, in April too.

How working with me remotely goes →

Who builds it

From 2012 to 2026 I ran the eBay side of AllOEMRims and built the system behind it.

AllOEMRims closed in 2026. The back office I built for it cataloged more than 26,500 items and tracked more than 22,000 orders, with an order ledger and profit and loss that showed where every dollar came from and where it went. A close pack is the same job for a bookkeeping client: what came in, what went out and what’s still open.

An AllOEMRims eBay listing photo: a silver multi-spoke OEM alloy wheel standing on the bright blue backdrop.
A real AllOEMRims listing photo.
14 yrssince 2012
$3.5M+in sales
22,000+orders
130,000photos

Sales and order figures from the business’s own records.

If you advise owner-run businesses

Know a client buried in their back office?

I also build for auto recyclers, online sellers, boatyards and property managers. If a client of yours is drowning in a back office, feel free to pass my name along. I’ll take good care of them.

How it starts

Two easy ways in

A free map of your setup

Tell me what you run, how many clients you chase each season, and what keeps going wrong. It’s nine short questions. Within a few days I will send back a plain-English map: what your software already covers, what I’d build beside it, and roughly what that’s worth to you.

  • Free
  • In writing
  • No call
  • No password

If you want help after that, each stage is a fixed price, agreed up front, and everything is set up in accounts in your firm’s name.

Technical · advancedUnder the hoodFor the technical folks: how it connects, what it’s built with, and how it’s kept safe.

I’d rather you know exactly what you’re getting. This is how a firm’s system is set up, in plain technical terms. Where something is how my own back office works today, I say so. I don’t hold a security certification like SOC 2, and I won’t tell you anything is unhackable. What I can tell you is that these basics are always there.

How it connects

  • Your tax, practice, portal and books software (Drake, UltraTax, Lacerte, TaxDome, Karbon, Canopy, SmartVault, Liscio, Financial Cents, QuickBooks Online, Xero) through the exports or reports it already makes, or through API access you or your vendor grant. Nothing reads its database without your written OK.
  • Each client gets their own link and sees only their own checklist, their own letters and their own status.
  • Texts to clients go out from an account in your firm’s name, only to clients who agreed to get them, and a reply of STOP ends them.
  • Uploaded documents stay in your install only until they’re filed into the folder or system you already use.
  • New data is picked up each time a new export comes in, or as often as your software’s access allows.

What it’s built with

  • Python, with FastAPI and SQLite, for the services and the back office.
  • JavaScript and TypeScript for the screens and for Cloudflare Workers. Next.js for websites, this one included.
  • Cloudflare for sign-in (Access), the encrypted connection to your server and hosting websites (Pages). Resend sends the email.
  • The same stack my own back office runs on today.

Where it runs and who owns it

  • Each firm gets its own install. It isn’t shared with any other firm.
  • It runs on a small cloud server in your name, with me as the admin, and its backups go to storage in your name too.
  • Your data lives in your install. My own back office doesn’t keep a copy, and I don’t sell or share your data.
  • It keeps only what the job needs. None of these jobs needs a client’s bank login, so it’s never asked for.

How it’s kept safe

  • Staff sign in through Cloudflare's single sign-on, so you decide who gets in and can take anyone's access away at any time.
  • Keys get only the access they need. If your software ever hands back less access than the job needs, it stops making changes and tells me.
  • Passwords and keys never live in the code. They sit in a locked down file on the server, and the key to your software is encrypted there and never leaves it.
  • Everything travels over HTTPS. Webhooks from outside services are checked against their signature before anything in them is used, and anything public has rate limits.
  • Every change it makes goes into an audit log the app has no way to edit or delete. In my own back office, a price change is a new entry and the old one is kept.
  • New features start in dry run, so you see what it would do before it does it. A kill switch stops all changes at once. It never moves money, it never files anything with the IRS, and nothing goes out to a client until your staff have turned it on.

How changes are made

  • My own back office runs over 3,000 automated tests on every change, once on my machine and again on the server. Nothing ships unless both pass. Your system gets its own suite, run the same way.
  • A backup is taken before any database change.
  • Every release is versioned and can be rolled back.
  • A health check runs after each update, and monitoring keeps checking it every 5 minutes after that.
  • Updates are remote. A fix never needs a trip to your office.

What you get at the end

  • A runbook for your system and a one page guide for your staff, plus a short training session.
  • The audit log, so you can see every change it ever made.
  • Admin access to everything, in accounts in your name.

Straight answers

Do I have to give up TaxDome, Karbon or my client portal?

No. Your tax software, your practice tool, your portal and your clients’ books all stay. Keep your subscriptions. I build what they don’t do, and if one of them already does the job, I’ll tell you that instead.

Which systems can it work with?

The usual ones are Drake, UltraTax and Lacerte for tax, TaxDome, Karbon, Canopy and Financial Cents for the practice, SmartVault and Liscio for documents, and QuickBooks Online and Xero for the books. Each one is reached through the exports and reports it already makes, or through API access you or your vendor approve. Before anything is built, I check that each one gives what the job needs. If one doesn’t, I’ll tell you up front.

Our clients upload tax documents. What about Section 7216?

Those documents are the kind of information Section 7216 protects, so the system is built to keep them inside your firm: an install in your firm’s name, files going into the folder you already use, and nothing sent anywhere you didn’t set up. The consent tracker can keep a record of which client signed which consent and when it runs out. I’m not a lawyer or a tax advisor, so what your consents need to say is a question for your own counsel.

Does this fit with our FTC Safeguards Rule program?

The rule asks your firm to oversee its service providers, and I would be one of them. So before any work starts, you get a plain written summary of how your system is set up, who can reach what, and how a problem gets reported to you, to keep with your program. Florida law also asks a service provider to tell you within 10 days if a breach happens, and I’ll put that in writing too.

Do my clients need to download an app?

No. They get a link by email or text and open it in the browser on their phone or computer. A client sees only their own checklist and their own status.

Can it text my clients?

Yes, from an account in your firm’s name, and only to clients who agreed to get texts. A reply of STOP ends them. Email works for everyone else.

What does it cost?

Each stage is a fixed price, agreed up front before any work starts. Every firm is set up differently, so there’s no price list. The map is free.

Are you affiliated with any of the companies on this page?

No. I’m not affiliated with Intuit, Xero, Drake, Thomson Reuters, TaxDome, Karbon, Canopy, SmartVault, Liscio or Financial Cents. I build beside what they make, with the access you give me.

Who are you?

Justin Zagar, and it’s just me. From 2012 to 2026 I ran the eBay side of AllOEMRims, an OEM wheel business, and built the system behind it, including an order ledger with profit and loss that showed where every dollar came from and went. Now I build the same kind of system for other businesses.