Firm AI Ops Show us a process

Services

The whole offer, on one page.

The monthly managed service is what most firms buy and the only line with a published price. Everything else is scoped and quoted in writing before it starts: that is the rule for anything outside the monthly service.

  1. Monthly, published price Managed automation service Recurring finance work automated across the systems you already use, then operated, monitored and improved month after month.
  2. Scoped and quoted AI governance and policy A written record of which AI tools your firm allows, what may be put into them, and who signed that off.
  3. Scoped, then monthly Automation takeover The automations nobody maintains, inventoried and either retired or repaired, then monitored with a named owner.
  4. Scoped and quoted Private AI environments Model hosting inside infrastructure your firm owns, with client identifiers stripped before anything reaches an outside model.
  5. Scoped and quoted Firm knowledge assistant An internal assistant over your procedures and past work that answers with the document it drew from.
  6. Monthly, alongside a tier Team enablement A firm specific library of prompts and templates, delivered as recorded walkthroughs rather than workshop days.

Monthly, published price

Managed automation service

The one line of work with a number on it. What separates the tiers is how much is actively operated and in progress at once.

Maintain

$1,000 / month

Keep existing automations healthy.

  • Monitoring, fixes and failure handling
  • Integration and credential maintenance
  • Updates when a connected system changes
  • Documentation kept current
  • A written monthly operating summary
  • No significant new automation build work

Managed Automation

$3,000 / month

Operate what is live and keep improving the next most valuable process.

  • Everything in Maintain
  • Active operation of the workflows already live
  • Exception handling and failure review
  • One meaningful automation priority in progress at a time
  • Regular review of what to automate or improve next
  • A walkthrough when something materially changes

Embedded

$6,000 / month

For teams with several processes moving at once.

  • Everything in Managed Automation
  • Multiple automation priorities in progress at once
  • More complex cross system workflows
  • Priority handling for operational issues
  • A regular roadmap and prioritisation review with your finance or operations lead
  • Month to month, no minimum
  • Pause or stop any month
  • 10% off an annual prepayment
  • Work larger than about a month is scoped and quoted separately

You keep every map, runbook, prompt and recording produced. Access needed is scoped to each workflow and named before it is granted.

Scoped and quoted

AI governance and policy

A written record of which AI tools your firm allows, what may be put into them, and who signed that off.

Staff are already putting client work into AI tools. The review inventories what is actually in use, sets out which classes of data may and may not leave the firm, and produces the policy and approved tool register that govern it. Registers are rechecked on a cycle afterwards, so the document still describes what is running rather than what was true the quarter it was written.

You keep The written policy, the data classes and the approved tool register. Access needed None. Built from what your staff report and what you send.

  • An inventory of the AI tools already in use across the firm
  • Data classes: what may leave the firm and what may not
  • The written policy and the approved tool register
  • Registers rechecked and permissions reread on a cycle
  • A written note of what changed each cycle

Scoped, then monthly

Automation takeover

The automations nobody maintains, inventoried and either retired or repaired, then monitored with a named owner.

Most firms have a graveyard: flows and half configured rules built by someone who has left, which nobody reviews and nobody notices when they stop. The takeover inventories what exists, says in writing what is broken, redundant or unwatched, retires what should not be running, and puts the rest under monitoring with a runbook and a named owner. A screenshot of the dashboard is enough to start.

You keep The inventory, plus a runbook for everything that stays. Access needed None to start. A screenshot of the dashboard is enough.

  • An inventory of everything currently running
  • What is broken, redundant or unwatched, stated in writing
  • Retirement of what should not be running at all
  • A runbook and a named owner for everything that stays
  • Second opinion: a written read on a proposal, a tool or another provider's quote

Scoped and quoted

Private AI environments

Model hosting inside infrastructure your firm owns, with client identifiers stripped before anything reaches an outside model.

Every workflow names where its models run before it is built. Most firms should stay on business grade model services configured for the firm; some carry obligations that do not allow it. Either way the routing rules are written into the workflow map: which identifiers are stripped before anything leaves, and which client's records a given piece of work is allowed to reach.

You keep The environment, its access list, its runbook and the routing rules. Access needed An account your firm creates. We hold only what you grant.

  • Deployment into a cloud account your firm owns and pays for directly
  • Keys, access list and bill held by your firm, revocable any day
  • Client identifiers stripped before anything reaches an outside model
  • Each client's records scoped to that client's work
  • A runbook for the environment and the routing rules in every workflow map

Scoped and quoted

Firm knowledge assistant

An internal assistant over your procedures and past work that answers with the document it drew from.

Built over the folders on an access list your firm approves, and no others. Every answer names the document behind it, so a person can check the source rather than take the answer on trust, and permissions mirror who may already see each source rather than flattening the firm into one audience.

You keep The assistant, its source register and its permissions map. Access needed Read access to the named folders on the access list.

  • Answers that cite the document they were drawn from
  • A source register naming every folder it reads
  • Permissions mirroring who may already see each source
  • Nothing outside the named folders is connected

Monthly, alongside a tier

Team enablement

A firm specific library of prompts and templates, delivered as recorded walkthroughs rather than workshop days.

Built on the tools your policy already names, so nothing here contradicts the register. Recorded rather than run live, because a walkthrough watched at double speed on a Tuesday evening reaches more of a firm than a workshop day half of it cannot attend.

You keep The library and the recordings. Access needed None. Built on the tools your policy already names.

  • A prompt and template library written against your own work
  • Recorded walkthroughs rather than scheduled workshop days
  • Built only on tools the approved tool register already names
  • Added to as the register and the workflows change

Not sure which line of work you need?

Show us one process. The written teardown will tell you what it would take, and whether it is worth doing at all.

Show us a process