Apparatus 202 — Power Tools

The Skills Are There. The Infrastructure Isn't.

202 takes a team that already prompts well and gives it the infrastructure to compound. Skills anyone can run, internal data connected, and workflows that belong to the firm - not just the people who figured them out.

The Problem

Your team learned to prompt. That learning is still stuck in individuals.

Good prompts still live in browser history, at a higher skill level. When someone figures out a great approach to a recurring task, it's theirs - not the firm's. Individual fluency is real. Firm fluency isn't.

Files in Drive, client notes, data in your CRM - AI can work with all of it. Most firms prompt against nothing but generic training data because nobody set up the connection. The information exists. The integration doesn't.

The work from the last engagement taught your team something. That knowledge didn't become a Skill, a template, or a documented workflow. The next engagement starts from scratch. Good outcomes stay unrepeatable.

The training worked. The missing piece is the infrastructure that makes what individuals learn accumulate into something the whole firm owns.

Why Apparatus

We built this because 101 wasn't enough.

Getting teams to prompt reliably is the foundation - and 101 solves that well. But the firms that actually pull ahead are the ones that turn individual skills into shared infrastructure. Skills libraries. Data connections. Documented workflows that survive when someone changes roles.

We work with consultancies, law firms, and advisory practices that have already done the training. We built 202 for the next problem: making what they learned stick at the firm level.

What to Expect

Three shifts that move fluency from individuals to the firm.

01

Turn prompts into Skills your whole firm can run.

A Skill is a reusable unit - more structured than a prompt, designed to produce consistent output for a specific task type. Instead of a working prompt buried in someone's conversation history, you get something any team member can run on the same kind of work.

02

Connect AI to your firm's actual information.

MCP connectors let your AI environment read your Google Drive, your Notion workspace, your CRM. AI that can see your client files and internal data produces better output than AI working from memory alone. This is the difference between a generic tool and one that knows your firm.

03

Document workflows as assets, not tribal knowledge.

The best way your team does the work gets written down in a format anyone can follow - and that custom tooling can later build on. What used to live in one person's head becomes something the whole firm owns and can hand to a new hire on day one.

Get Started

Book a 30-minute call.

We'll ask about where your team is after 101, what your current infrastructure looks like, and walk you through what a 202 engagement typically covers for a firm at your stage.

Why Now

Individual AI fluency is no longer a differentiator.

Firms that did nothing in 2024 are training their teams now. The fluency gap is closing. The infrastructure gap - who has working data connections, whose Skills library is growing, whose workflows are documented and transferable - is what separates firms that compound from firms that stay flat. That gap is forming now, and it gets harder to close the longer it exists.

The Other Side

What one person knows, the firm knows.

A Skill one person builds is a Skill everyone can run. What used to live in a browser tab becomes a reusable tool any team member can use on the same kind of work.

Your client files and internal data inform AI output - not just generic training data. AI that knows your firm produces better work than AI that doesn't.

New hires get a working AI setup on day one. The Skills library is there. The workflows are documented. The ramp is weeks, not months.

Your best workflows belong to the firm, not to whoever figured them out. When someone leaves, the institutional knowledge stays.

The path

101

Foundations

Prompt fluency, shared standards, and a seeded prompt library. The prerequisite for everything that follows.

Learn about 101 →

303

Custom Development

Proprietary tools built on top of the infrastructure 202 establishes. New services to offer. Engagements to win because nobody else is set up to deliver them.

Learn about 303 →

Ready to turn what your team knows into something that lasts?

30 minutes to find out where to start.

Book a Call →