FirmOps Design-Partner FAQ

FirmOps is an agent operating system for law firms. It connects the stack a PI firm already runs on—Clio first, plus email, phones, documents, e-sign, accounting, and reporting—so the owner can ask cross-system questions and approve supervised work from one operating layer.

The product is the operating system and agent layer. Early design-partner deployments include founder attention and per-firm configuration, but the goal is product equity, not selling fractional-COO hours. Every deployment should extract more of the repeatable system into the platform.

Because the cold-email visitor needs to see the product, not be offered a free audit. The demo shows the real workflow: ask the firm a question, get an answer across systems, then move into supervised work with approval gates.

PI or high-volume contingency firms with roughly 3-50 staff, Clio as practice management, and an owner/operator who personally wants the system. The first cohort is capped at five paid design partners.

A firm is a bad fit if it wants a free pilot, wants one custom feature that will not generalize, lacks owner/operator buy-in, or runs a non-Clio stack that would turn the pilot into adapter engineering before the core product has enough proof.

Yes. Referenceable proof is part of the trade, with anonymization negotiable. The whole point is to prove the system in real firms, with real staff and real workflows, while building the platform.

The first design-partner cohort is Clio-first so early deployments stay focused and repeatable. The architecture is stack-aware, but Filevine, MyCase, and other adapters are roadmap decisions ranked by real pilot demand—not promises made before the first cohort proves the offer.

The agent OS is designed to connect practice management, email, phones/SMS, e-sign, documents, accounting, job schedulers, and reporting stores. Week 1 emphasizes read-only visibility across those systems before any supervised write workflow is enabled.

The demo path shows the product: ask a cross-system question, inspect stale matters, draft updates, prepare tasks, or support intake-to-matter steps. Write actions are configured as drafts, queues, or approval-gated actions rather than blind automations.

Plan on weeks, not days. A per-firm instance for a Clio-stack firm is expected to take roughly 2-3 weeks of configuration and extraction work in the early design-partner phase.

Read before write. Week 1 is about connecting the stack so the agent can answer useful cross-system questions with zero operational risk. Supervised writes come after trust is earned and approval rules are explicit.

The pilot includes one read-suite plus two supervised-write workflows. Examples include matter-dormancy digests, intake-to-matter preparation, client-update drafts, task routing, or other workflows that generalize beyond one firm.

No. FirmOps is approval-gated and human-in-the-loop. The system can surface work, draft actions, and route exceptions, but attorney judgment and firm-owner control stay with the firm.

The first phase is read-only, which creates fast value without writing back to practice-management or client systems. Writes are added only after the firm approves rules, permissions, and workflows.

Before pilot #1, the engagement agreement needs the usual pass on generic IP ownership, confidentiality and data handling, no-UPL scope language, market conflict policy, and any entity or brand structure decisions.

The current design-partner offer is $12.5k fixed for deployment, with a $10k floor, plus a $2k/month run fee, with a $1.5k floor, for hosting, supervision, model costs, and monthly tuning.

A per-firm agent OS instance, a read-suite that gives the owner cross-system visibility, and two supervised write workflows such as matter-dormancy digests, intake-to-matter support, or client-update drafts.

The pilot is structured as 90 days, month-to-month after that. Design partners get early pricing and roadmap influence; FirmOps keeps the generic product IP and improvements.