TaxEase

TaxEase does not prepare your return.

That belongs at the top. Tax software usually means a calculator with a wizard in front of it, and this is a different kind of product entirely.

What it manages is the work around the filing.

Most of the effort inside a practice is not arithmetic. It is a request that arrived without the document it needed. A file waiting on a signature. A client writing for the third time to ask where things stand.

None of that is visible to the person waiting, which is exactly why they keep asking.

The constraint is the same one every product on this site is built to. No paid service in the critical path, no server that has to be kept alive, nothing whose price can move underneath a practice that budgets a year in advance.

Documents make that harder than it sounds.

A file somebody uploaded about their income is not a file that should be casually copied across three vendors, so the fewer places it lives the fewer places it can leak. React 19 and TypeScript on the web, Firebase behind it, Capacitor packaging the same codebase for Android.

The request is the unit.

It is raised, tracked and worked by somebody on the staff side, and both parties look at one record instead of at their own copies of it.

Documents attach to the request rather than to an inbox thread, which is the difference between evidence somebody can find in a year and correspondence somebody has to remember to go searching for.

Status changes in real time. The person waiting watches it happen.

That removes the email that was only ever asking a database a question, and it removes the reply that had to be written by hand.

Communication happens inside the file, so the conversation and the paperwork stay in the same place and stay together when somebody else picks the file up.

The admin side is for staff. It is a working surface rather than a reporting one, because the person moving a stack of files this week needs a queue they can act on.

Android comes from the same codebase, since a client chasing a document is rarely sitting at a desk.

The costs are worth stating plainly.

A status field is only ever as honest as the person who moves it. Software can make the current state visible and it cannot make anybody update it, so the real job is to make updating cheaper than answering the email would have been.

Documents are the sensitive part, and they are also the part people will email anyway.

A system is only as private as the least convenient path through it. Convenience is a security property here rather than a nicety, and that is not how it is usually budgeted.

A shared inbox is easier to start with. By the third month it is worse, and by then the history of a file lives in somebody's mailbox rather than in the file.

There is no iOS build. There is no Apple Developer account behind this work, so the web and Android are the two surfaces it reaches.

Nothing here is tax advice and nothing here computes what you owe. It moves the requests, the documents and the answer to the question everybody keeps asking, which is the part that was quietly costing both sides their week.