Finance and accounting decision

Keeper Tax

Building a usable deduction-tracker and receipt workflow is realistic for a small team, but reproducing Keeper's patented deduction-tracking, IRS e-file authorization, and human-reviewed full-service filing is not practical to replace; keep paying for full-service features unless you only need a DIY tracker.

Visit website
You pay

$16.58/mo

$199/yr

Read off the official pricing page.

You’d pay instead

$100one-off80 h to build

$150/mo12 h/mo upkeep

On cash alone, building overtakes the subscription at 10 seats.

No open-source build does this yet

Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.

What a replacement has to do

  • Track deductible transactions, attach receipts, and export deductions for tax filing

What it still won’t have

  • IRS authorized e-file provider status
  • Keeper's patented deduction-tracking IP and any proprietary models
  • Human tax pro review, 1:1 consultations, and audit protection
  • Guaranteed accuracy and full-service filing (state+federal, complex forms)
  • Year-round support and multi-year filing/amendments

What remains hard

  • Proprietary modelsSave thousands in taxes with Keeper's patented deduction tracking - recommended by accountants and trusted by tens of thousands of self-employed americans.
  • Compliance and regulationIRS authorized e-File Provider
Read the build prompt

First-year cost

Keep paying

Paying is—cheaper in year one.

On cash alone, building overtakes the subscription at 10 seats.

Paid seatsseats

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal deduction-tracking web app using React frontend, Node/Express backend, Postgres DB, and AWS hosting. Core features in scope: (1) Plaid integration to read transactions; (2) transaction classifier (rule-based + small ML model) that tags likely deductible items; (3) receipt upload endpoint with OCR (Tesseract or cloud OCR) and storage in S3; (4) dashboard to review/edit tagged deductions and export CSV of deductions; (5) user auth (JWT) and a Stripe subscription for payments. Out of scope: IRS e-filing, providing certified tax pro review, audit protection, multi-state/form filing. Include basic error handling, logging, unit tests for core logic (classification, upload, export), and a README with deployment steps.
How we checked3 sources · 2/3 runs agreed · evidence score 20

How the score was reached

  • Pay verdict base20
  • 3 cited sources+3
  • Price verified on pricing page+3
  • Hard moats found in the evidence-6
  • Evidence score20

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

✓ Price read off the page! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 2 moats quoted from the page