Common questions about TaxRiskOS

TaxRiskOS is workflow software for the first hour after a client forwards an IRS notice. It captures the notice, computes the deadline, generates a notice-specific document checklist, surfaces escalation routing flags, keeps a timestamped audit trail, and produces a structured handoff packet for the licensed professional. It does not provide legal advice, tax advice, or IRS responses.

CPA firms, enrolled agents, tax attorneys, and any practitioner who handles the intake side of IRS notice matters. The workflow is designed for the practitioner or staff member who fields the first call or email when a client forwards a notice.

John Webb — solo founder based in Louisville, Kentucky. Accounting and finance graduate (University of Kentucky, Gatton College) and former KPMG audit associate. TaxRiskOS is pre-revenue and honestly says so.

It's a working prototype in the pre-revenue pilot phase. A synthetic-data demo is publicly available. The founding-firm pilot is open for practitioners who want to review the workflow and provide input.

Six workflow steps: (1) Notice intake — capture the notice type, date, and key facts. (2) Deadline capture — compute the response window from the notice date. (3) Document checklist — generate a notice-specific starter list of documents to request. (4) Escalation flags — surface routing labels for whether the matter needs partner review or counsel. (5) Audit trail — timestamp every step. (6) Handoff packet — produce a structured 11-section document for the licensed professional.

A structured document with 11 sections covering: notice summary, computed deadline, response window, document checklist, escalation flag and reason, intake notes, practitioner instructions, and a timestamped audit trail. It's formatted for easy attachment to any practice management tool, matter folder, or document management system.

A routing label — not a legal conclusion. The same notice always yields the same flag. The flag tells the intake practitioner whether the matter should stay with staff, go to a senior reviewer, or route to counsel before anything else happens. What to do with the flag is always the practitioner's decision.

Yes. Each notice type has its own typical response window, document checklist, and escalation logic. A CP2000 underreporter notice starts with a third-party data match; an LT11 final levy notice flags a hard collection-appeal deadline immediately; a criminal-investigation contact stops all intake and instructs the user to engage counsel.

No. TaxRiskOS provides workflow and decision-support outputs. It does not provide legal advice, tax advice, or representation. Practitioner judgment remains with the licensed professional. This boundary is enforced throughout the product and tested on every build.

TaxRiskOS does not: draft IRS responses or correspondence; communicate with the IRS on anyone's behalf; advise on the merits or strategy of a matter; make legal or tax determinations; draw conclusions from escalation flags; represent taxpayers in any capacity; or prepare tax returns.

Escalation flags are rule-based routing labels. The same notice type, with the same inputs, always produces the same flag — that's what makes them reliable. They tell the intake practitioner where a matter should go next in the workflow. They do not determine liability, determine the outcome of a matter, or substitute for a licensed professional's assessment.

Intake stops immediately. A hard stop panel appears with a single instruction: engage tax-controversy counsel before speaking with anyone or producing any documents. No workflow output is generated for that matter. This is not a configurable setting — it's a fixed rule.

The licensed professional — always. TaxRiskOS documents the intake process. The practitioner provides every piece of advice, drafts every response, and makes every strategy decision.

Rule-based in V1. The same notice, with the same inputs, always yields the same output — deadline, checklist, escalation flag. There is no language model in the V1 production decision path. The public demo uses synthetic data only.

Yes. TaxRiskOS is a web application — no installation required. The first-hour workflow runs in the browser; the engine that computes deadlines and flags runs server-side.

The public demo uses synthetic data only — no real client data is processed or stored in the demo. Data handling in the production version is being designed for the pilot phase. Pilot participants will receive a data-handling summary before use.

V1 delivers a structured export — a handoff packet formatted to attach to any practice management tool, matter folder, or document management system. Native integrations with Canopy, TaxDome, and Karbon are actively scoped for the roadmap. No timeline commitments.

No. TaxRiskOS handles the first-hour notice intake layer. Your practice management tool handles billing, ongoing matter management, client communication, and the rest of the practice. The two sit in different lanes — TaxRiskOS produces the intake packet; your PM tool carries the matter forward.

V1: structured text with 11 clearly labelled sections, formatted for easy copy/paste or file attachment. PDF export is on the V1 milestone list.

TaxRiskOS is in the pre-revenue pilot phase. Pricing isn't posted publicly because it's being shaped by the workflow and scope emerging from the founding-firm pilot. Apply on the pilot page to discuss terms.

The synthetic-data demo at /demo is freely available with no signup — it runs five synthetic IRS-notice cases through the full first-hour workflow. The full working prototype is available to founding-firm pilot participants.

No. TaxRiskOS is pre-revenue. No customer logos, no traction numbers, and no testimonials appear anywhere on this site because none exist yet.