← Back

Guide · Published November 14, 2026 · Reviewed November 14, 2026 · Ingenious AI team · Not legal advice

← All guides

ADMT Notice Kit Pricing: Free, Pro ($49), and Team ($99) Compared

The short answer: The kit's plans, as stated on the pricing page and in the kit's own site data: Free — $0: Colorado, one decision type, core record log. Pro — $49 per month: all three states (Colorado, California, Connecticut), explanation builder, human-review queue, exports. Team — $99 per month: multi-seat review queue, all states. The right tier is a function of three variables — how many states, how many decision types, how many reviewers — and this guide maps the common operator shapes in this series onto them, so the choice can be made from your register rather than from a feature list.

Check your duties and dates — free Build your first notice — free

What do the plans gate? Per the kit's stated plan data: geography and decision-type breadth (Free is Colorado-only, one decision type), the building tools (the explanation builder arrives with Pro), the review machinery's seats (Team is the multi-seat queue), and exports (Pro and up). The core record log — the hash-chained per-decision record — is in every tier, including Free, because the record is the product's centre at every scale.

The Free shape: one state, one decision, real record

Free fits the operator this series meets repeatedly: a single-state (Colorado) business with one decision type — the small landlord screening tenants, the single-site employer hiring, the solo lender. What it includes is the genuine core: notices generated from your profile for that decision type, and the core record log that keeps them chained with the decisions. What it does not include is equally clear: other states, other decision types, the explanation builder, the staffed queue, exports.

Evaluate Free as an operating tier, not a trial: if your register honestly says Colorado-only and one decision type for the foreseeable year, Free is a complete configuration for the notice-and-record core, with the explanation workflow run from the generated document shapes the guides describe. The moment a second state or decision type becomes real — not hypothetical — the tier question reopens.

The Pro shape: three states, the builder, the queue, exports

Pro is the tier the multi-state examples in this series implicitly run on: all three states with their divergent duties (Colorado's clock, California's opt-out and access set, Connecticut's notice pair and profiling events) in one record; the explanation builder producing adverse-outcome documents from case facts; the review queue for the human-review duties; and exports for the producible record.

The trigger facts for Pro are concrete: any California or Connecticut duty set; any need to produce case exports (for access answers assembled from the record, internal sampling, or an examiner); any review volume beyond an occasional case handled by hand. Most operators who run the January 2027 checklist to completion land here, because the checklist's phases assume the builder, the queue, and the export as working parts.

Worked example: Three operators from this series

Example — fictional business, real duty structure. The tier logic applied to three businesses from these guides, using their register facts:

The Team shape: seats for a real rota

Team adds the multi-seat review queue — several reviewers working one queue with the rota, deputies, and per-reviewer records the queue guide prescribes. The trigger is organisational, not volumetric: the moment review is a rota rather than a person — two or more reviewers plus a deputy, across sites or shifts — the seats are what make the queue's records honest (who reviewed, with what authority, changing what).

Team also fits the staffing and platform shapes: agencies running reviews for several client workflows, multi-site employers whose reviewers sit in different locations. If your review step today is a shared inbox, Team is priced against the cost of the inbox's failures — unowned cases, unlogged outcomes, the token-review pattern that flourishes where no individual reviewer is identifiable in the record.

What no tier changes: the duties and the boundaries

Plans change tooling breadth, never the duties: a Free operator owes Colorado exactly what a Team operator owes Colorado. Plans also do not change the product's stated boundaries at any tier — the kit is a templates and records tool, not legal advice; it does not judge whether decisions were fair; regimes outside its data (the GDPR, per the checker's pointer) remain outside it at $0, $49, and $99 alike.

Payment and fulfilment facts belong to the pricing page itself, which is the authority this guide defers to for current terms. This guide's job is the fit analysis: states, decision types, seats. Run it off your register — count the states with live duty sets, the decision types in production, and the reviewers on the rota — and the tier reads off the counts.

Choosing, upgrading, and the cost of the alternative

Start where your shape fits today, with the upgrade triggers written down: a second state entering the register, a second decision type going live, a second reviewer joining the rota. Starting one tier low with named triggers is better planning than starting high 'for growth' — the triggers, being register facts, announce themselves.

Finally, price the alternative honestly, as the spreadsheet guide does: staff time per generated document, daily clock-watching, reconstruction hours when a case is questioned, and the risk position of an editable record. For a one-state, one-decision operator the spreadsheet-plus-Free comparison is genuinely close; for a three-state operator with a review rota, the arithmetic is not. The pricing page has the current terms; the free generator has the artefact to evaluate before any of it.

  1. Count from your register: states with live duty sets, decision types in production, reviewers on the rota — the tier reads off the counts
  2. Free fits Colorado-only, one decision type, core record needs — treat it as an operating tier, with written upgrade triggers
  3. Pro is triggered by any second state, the explanation builder, the review queue, or case exports becoming real work
  4. Team is triggered by review becoming a rota — multiple identifiable reviewers whose records must show who decided
  5. Re-run the fit at every register change, and confirm current terms on the pricing page before acting on this guide

Sources, as carried in the kit's own data: the duty summaries in app/rules.py and the checker data in app/checker_data.py, verified against primary or authoritative sources on October 28, 2026. Run the free duties checker for your jurisdiction, decision type, and the tool's role, and compare the kit's plans for the record, builder, and review queue. More from Ingenious AI is on the hub.

Build your first notice — free

Related guides

See all ADMT guides for the full set.

Frequently asked questions

What does the Free plan include?

Colorado coverage, one decision type, and the core record log, per the kit's pricing data. It is an operating tier for a single-state, single-decision operator, not a time-limited trial.

What does Pro add for $49 per month?

All three states (Colorado, California, Connecticut), the explanation builder, the human-review queue, and exports.

What does Team add for $99 per month?

The multi-seat review queue across all states — several reviewers working one queue, which fits rotas, multi-site employers, and agencies running reviews for multiple workflows.

Do the plans change what duties we owe?

No. Duties come from the states and your use, not from the plan. Plans change tooling breadth: geography, decision types, builder and export features, and queue seats.

Where is the authoritative pricing?

The pricing page. This guide maps operator shapes to the plan structure stated in the kit's site data; current terms, billing, and fulfilment are the pricing page's to state.

Build your first notice — free