Skip to main content

Compare

TaxOrch versus building it yourself

Sometimes you should build it. What an estimate misses is not the rates — it is provenance, the point-in-time resolver, and the evaluation harness.

What this compares

An approach, not a product.

No product is named here, because a statement about a named competitor needs a public source rendered on the page — and without one it is hearsay published as fact, which also ages into a lie the moment they ship a release.

The dimensions

Where each one actually differs.

  • The rates

    Building it in-house
    The easy part, and the part the estimate is based on.
    TaxOrch
    Bracket, allowance and rate datasets for forty-five countries, each carrying its source, law-as-of date and explicit assumptions.

    Deterministic calculators for 8 jurisdictions and parameter datasets for 45.

  • Which year's rules apply

    Building it in-house
    The part that gets discovered late. Every answer is a point-in-time answer, and a system that does not model that answers the wrong year silently.
    TaxOrch
    Point-in-time resolution gating retrieval and the bracket resolver, with the law-as-of date on every answer.

    A 2023 question is answered with 2023 law.

  • Knowing it still works

    Building it in-house
    A second project the first one depends on. Without golden cases you discover a broken bracket when a customer does.
    TaxOrch
    Golden cases across ten release-gate categories, with abstention cases first-class and a gate that exits non-zero.

    Every golden case is classified as answered-correct, answered-wrong, escalated or clarified — and an answer that shipped wrong is a P0.

  • Keeping it current

    Building it in-house
    Permanent. The build is a project; the maintenance is a standing team, and that is the cost usually left out.
    TaxOrch
    Included, and visible: sources carry an update cadence and stale ones block release freshness.

  • Control

    Building it in-house
    Total. Your schema, your priorities, no vendor between you and a change.
    TaxOrch
    Self-hostable with around 151 routes, which is close but not the same thing.
    Where building it in-house wins: Real. If the shape of the problem is genuinely yours, building it is the right answer and no vendor page should tell you otherwise.

    Approximately 151 API routes.

Building it in-house suits you if

  • A single jurisdiction, a single tax type, and rates that change once a year
  • A team with tax expertise in-house and time to keep it current
  • Requirements so specific that a general product would be adapted more than used

TaxOrch suits you if

  • More than one jurisdiction, where the maintenance compounds
  • Teams whose product is something else and who do not want a permanent tax team
  • Anywhere the answer needs provenance a customer can check
The honest part

Do not buy this if any of these is true.

A comparison page with no such section is an advertisement, and a reader discounts everything else on it accordingly. This one is required by the data model, so it cannot be quietly dropped when somebody is editing for length.

  • One jurisdiction, one tax type, rates that move annually — that is a build, not a purchase
  • You already have tax expertise in-house and the maintenance is not a burden
  • Your requirements are specific enough that you would spend more adapting this than writing it
Check the working

Everything here is meant to be verifiable.

The coverage matrix, the evaluation results and the answer contract are all published, including what they do not cover. Read them before you talk to anybody.

Bring the question you expect it to get wrong.

TaxOrch provides decision support, not professional tax advice. Exact results apply only within declared coverage. TaxOrch does not file returns or execute payments. Review all outputs before filing.