The AI-native firm

How to Build a Firm OS

How you get everyone, from the front desk to the partner, using AI on real work the same way: fast, consistent, and on the safe side of the rules.

1

The Architecture Block

One shared firm workspace. Every service line is a folder. Every engagement type is an activity inside it. Every activity has a skill file that loads the right context, your standards, your voice, and its guardrail, for whoever runs it.

One partner's best workflow stops living in their head and becomes the firm's default.

📁 tax📁 bookkeeping📁 advisory📁 attest📁 payroll📁 admin📁 +more
📁 Firm-OS (workspace root)
📁 firm — voice, standards, the data rule
📁 onboarding — new-client intake
📁 tax (service line)
📁 1040-prep (engagement type)
📄 return-review-skill.md
→ loads context + guardrail into Claude
📁 bookkeeping
📄 monthly-close-skill.md
📁 advisory
2

The 3 Layers of Implementation

Layer 1

Start with the ontology

Before any tool, map your work: service line → engagement type → task. Then color-code each task: what stays human judgment (the review, the signature) versus what AI drafts. The OS is built from that map, not the other way around.

TAX1040draft organizerreview & sign

Layer 2

Build the skill files

One skill per task. Not a generic prompt, an opinionated guide that reflects how your firm does that work: your engagement-letter voice, your workpaper format, your modified-cash-basis defaults. Your best preparer's workflow becomes everyone's starting point.

1 person's best workflow → the firm default

Layer 3

Deliver it in-flow

Surface the right skill where the work already happens: the engagement folder, your practice-management software, the close checklist, the email draft. Even the friction of a separate window kills adoption.

the skill meets staff where they already work

The layer underneath everything

Every skill ships with its data rule baked in

This is what a firm OS adds that a generic one can't: each skill carries its own guardrail. The rule turns on your account tier, personal accounts anonymize; Team/Enterprise is permissible with your §7216 basis, and either way you keep SSNs and EINs out and the licensed professional reviews, decides, and signs. The safe path is the default path because it's built into the skill.

🪜 Where to start: you don't build the whole OS on day one. Stand up one person's setup first (a profile + a single skill, that's Workshop 1), prove it on one engagement type, then promote the winners into the shared firm workspace.

“A personal setup makes you faster. A firm OS makes your whole practice faster, and keeps everyone on the same safe path.”

Adapted from news.aakashg.com/p/company-os-jz for the AI Lab for Accountants.