Product Roadmap
Complete

#65 — Guided onboarding blueprints by firm type

Opinionated setup blueprints for tax / CAS / advisory firms — 'guided configuration' that turns best practice into defaults instead of an implementation project (the market's #5 unmet need). Light in Phase 1; deepens into full migration tooling in Phase 5. Size: M. Source: product-roadmap.md §9.

4 Comments

Posting anonymously

claude-agent·12 days ago

Closed during the 2026-08-23 GitHub migration: shipped (PR #29, merged 5ccd6b3) — /staff/admin/blueprints with tax/CAS/advisory presets, additive + idempotent.

Posting anonymously

claude-agent·about 2 months ago

Merged into dev (new shared integration branch per 2026-07-09 operating model) at 5ccd6b3; combined tree re-verified on dev (typecheck/lint/boundaries clean, new unit tests pass, build green incl. both new routes, bundle gate green across 288 routes). Ships to master with the next release cut. Marking complete.

Posting anonymously

claude-agent·about 2 months ago

Agent A — code complete & verified; awaiting merge (PR #29).

What changed: /staff/admin/blueprints (new "Blueprints" admin sub-nav entry) with three firm-type presets — Tax & compliance (Tax module on; Filing status / Return types / Prior-year software / e-file fields; 1040/1120/1120S/1065/990/Extension/New-client tags), CAS/bookkeeping (Time tracking on; Accounting system / Close cadence / Payroll provider / Bank feeds fields; Bookkeeping/Payroll/Monthly-close/Cleanup/Sales-tax tags), Advisory/fractional CFO (Time tracking on; Engagement tier / Industry / Annual revenue / Board cadence fields; Advisory/CFO/Forecasting/Board-reporting tags). Apply is additive + idempotent (never disables/deletes beyond the explicit module settings; re-apply reports "already existed"); composition over existing command APIs (toggleModule / defineClientField / createClientTag) so every sub-write keeps its own authz + audit + events. No migration, no new tables.

User-visible: a new firm picks how it runs and gets a sensible module set + client fields + tag catalog in one click instead of an implementation project; safe to re-run or mix.

Files: apps/web/lib/blueprints.ts (+test), app/staff/admin/blueprints/{page,actions,blueprint-cards}, admin-subnav, e2e/admin-blueprints.spec.ts, dependency-cruiser allowlist, admin-config contract As-built, truth-table + roadmap rows.

Verification (branch agent-a/onboarding-blueprints, commit 9bc365e): blueprints.test.ts 4/4; e2e admin-blueprints.spec.ts 1/1 vs live dev stack (apply -> Tax module Enabled -> fields/tags present -> idempotent re-apply); typecheck/eslint/lint:boundaries clean; web build green (route /staff/admin/blueprints).

Remaining/limits: no firm-type picker on platform createFirm yet (follow-up); no service-catalog/workflow seeds until the engagements lane (#34, unmerged) lands — deliberately avoided touching that module and the tasks module (Agent B's #91). Status stays In Progress until Daniel merges https://github.com/Firmary/firmary-os/pull/29 — flipping to complete then.

Posting anonymously

claude-agent·about 2 months ago

Agent A claiming this until completion or block. Scope: Phase-1 light slice — firm-type blueprints (tax / CAS / advisory) applied at setup: opinionated module set, template packs, client custom-field + tag-catalog seeds per type, with an admin surface to pick/re-apply a blueprint. Not touching the tasks module (Agent B owns #91). Started: 2026-07-09 01:25 America/Chicago.

Posting anonymously