Deployment
$12.5k fixed
OS instance, supervised agent, and 3 working workflows: one read suite plus two approved write workflows.
First cohort · max five firms
Paid design partners for the PI firm agent OS.
Early partners get FirmOps deployed as a working system: read-only visibility first, supervised write actions next, founder attention, roadmap influence, and pricing nobody sees again.
Good fit for the first cohort
- PI or high-volume contingency practice with 3–50 staff
- Clio as the practice-management system for the pilot phase
- Owner/operator personally involved in the rollout
- Willing to be referenceable after results, with anonymization negotiable
- No direct-market conflict without Conduit review and written sign-off
Pilot terms
Paid pilots only. Free pilots are not demand signal.
The first cohort is priced to fund productization while keeping the scope tight enough for founder-led delivery and fast proof.
Run fee
$2k/mo
Hosting, supervision, model costs, monthly tuning, and design-partner pricing grandfathered into the platform phase.
Term
90-day pilot
Month-to-month after the pilot. Generic FirmOps IP stays with FirmOps; firm-specific data stays yours.
What the pilot proves
If three firms pay for bespoke deployments, the next roadmap gate is the multi-tenant refactor: tenant config, credential routing, and onboarding instead of hand-maintained instances.
Three-workflow scope
A narrow deployment that proves the operating system.
The pilot is not an open-ended automation backlog. It is one read suite plus two supervised write workflows that show the agent can connect firm systems, explain its work, and wait for approval.
Read suite
Owner command center
Ask cross-system questions like dormant matters, unsigned retainers, unassigned tasks, treatment-stage bottlenecks, or intake follow-up gaps.
Supervised write #1
Intake → matter handoff
Turn qualified intake data into an approval-ready matter-opening package with tasks, notes, and source links before anything is pushed.
Supervised write #2
Client-update drafts
Draft status updates from Clio, email, phone, document, and task context, then wait for human approval before any external message goes out.
Delivery sequence
Read before write. Approval before external action.
FirmOps earns trust the same way the demo does: answer first, cite sources, draft only after the owner sees value, and require a human approval gate before anything touches a client, court, provider, or system of record.
Week 1
Read-only first
Connect approved firm systems and prove the agent can answer operating questions with source-linked evidence and zero write risk.
Week 2
Workflow mapping
Choose the two supervised write workflows that generalize beyond one firm and define the approval rules before implementation.
Week 3
Supervised writes
Ship approval-gated actions: drafts, tasks, notes, or matter setup move only after a designated human confirms the proposed action.
Days 30–90
Tune toward platform
Measure usage, remove brittle firm-specific assumptions, and extract tenant-config patterns that make the next deployment faster.
Who should apply
Best fit: owner-led PI firms on Clio.
The first cohort is deliberately narrow because the goal is product equity, not consulting cashflow. Every deployment should make the next one more repeatable.
Watch the demo before the fit callNot a fit yet
- You want a one-off custom feature that no other PI firm would need
- You need a non-Clio adapter before the first cohort has proven demand
- You want a free pilot or a generic consulting project instead of a productized operating system
- You expect unsupervised external actions before the approval model has earned trust
Cohort gate
If the demo looks like the firm you want to run, take the 15-minute fit call.
The call is a live walkthrough and qualification check for the paid design-partner cohort. No publishing, outreach, or implementation commitment happens without an explicit next-step agreement.