Your fund’s back office
Operator works on the investors, books, documents and deals your team already runs the fund from, and nothing changes until you approve it.
Why Operator
Fund admin by spreadsheet
An administrator works from its own copy of your fund, so every request means waiting for a spreadsheet, checking it against your records and chasing what’s missing outside the system you run the fund on.
Operator works on your record directly. It looks things up, proposes the exact changes, applies what you approve, then checks the result.
Fund admin today
- 1Email the administrator
- 2Wait for a spreadsheet
- 3Re-key it into your tools
- 4Chase what’s missing
- 5Reconcile it by hand
With Operator
- 1Ask for the outcome
- 2Operator reads your record
- 3Review the exact change
- 4Approve it
- 5Operator applies and checks it
How it works
Three ways to use Operator
The app, the terminal and your own agent reach the same Operator, with the same rights and approvals, and every change lands on your fund’s record.
- AppAsk in Infra OneChat, or press Run as job
- CLIoperator runFrom your shell, scripts or CI
- MCPYour own agentAny MCP client, under your login
- Changes land on your recordInvestors, books, documents and deals
- Plans that keep runningSteps that wait on dates and sign-offs
- Every step on fileWho asked, who approved, what changed
Live demo
Quarter close from a terminal
Watch the quarter close get created and released from a terminal, then run in the app as each step finishes.
Q3 close · Larkspur Fund II
plan 4f2a91 · from q3-close.yaml
- Held
Collect portfolio valuations
- Held
Reconcile bank to ledger
- JBHeld
Sign off valuations
Valuations signed off
- Held
Post fees and accruals
- Held
Draft capital account statements
- Held
Send LP statements
Not before 15 Oct
- MEHeld
GP sign-off
You approve every change
Operator looks before it acts, shows you exactly what it wants to change, and checks the result after it lands.
Plans that run for weeks
Write the quarter as one plan, with steps for Operator and your team in order and the waits between them.
Operator in fifteen seconds
Operator and your team
Six short films on working with Operator, where every go-ahead belongs to the person who owns it.
CLI & MCP
Use Operator from your terminal
Install the CLI, log in once in the browser and run Operator from your shell, scripts or CI, or give your agent the same commands.
# Start a job and follow it
$operator run "Chase LPs missing a W-8BEN" --watch
# Create a plan, held until you release it
$operator plan create --file q3-close.yaml
# Release it with a budget
$operator plan release 4f2a91 --spend-budget-cents 20000
# See what needs you
$operator jobs --status waiting
# Find the right tool
$operator tools search "capital call"
- runStart a job
- jobs_listWhat’s running and what needs you
- plan_createDraft a held plan
- plan_releaseRelease it with a budget
- gate_setTick a sign-off
- tools_searchFind the right tool
Install with npx @allocator-one/operator · add it to any MCP client with operator mcp
Every tool
402 tools for Operator
Operator can use every tool on your fund, from CRM search to capital calls and data-room publishing, with the rights each has in the app and your approval on every write.
- CRM108
46 reads · 62 writescrm.party.search
- Funds & capital69
55 reads · 14 writesfunds.capital_call.draft
- Portfolio & reporting62
59 reads · 3 writesportfolio.performance.read
- Dealflow & network46
40 reads · 6 writesdealflow.selection_case.get
- Communications & events43
30 reads · 13 writescommunications.email.send
- Platform & people29
18 reads · 11 writesplatform.team.list
- Hiring26
15 reads · 11 writeshiring.candidate_list.search
- Ledger & expenses10
9 reads · 1 writeledger.book.review
- Documents & data rooms9
8 reads · 1 writedocuments.dataroom.publish
402 tools in all
Reads Writes, each approvedOperator’s limits and controls
Operator works for a person in your organization, with that person’s rights, inside budgets your admins set.
- The rights of the person asking
- Operator acts for the person who asked, or who released the plan, and checks their access again at every step. Guests can’t start jobs.
- Exact approval for every write
- An approval covers one exact set of changes. If anything in it changes, the approval no longer applies and Operator asks again.
- Each change read back after it’s applied
- Each change is read back from the record after it’s applied. A partial or unknown outcome is shown as exactly that.
- Monthly and per-plan budgets
- Admins set a monthly budget for the organization, and each plan carries its own. Operator stops starting work when either runs out.
- Stop any job or plan
- Hold a plan, cancel a job, or switch Operator off for your organization. Approvals never carry over to new work.
- Each job’s data stays in one organization
- Every job, plan and result belongs to one organization. What Operator reads stays in the job’s room, out of search and out of other organizations.
More on Operator
Four views of Operator
Each page covers one part of how Operator works.
Plans
Plans across Operator and your team
Chains of work that run for days or weeks, across Operator and your team, with the waits between them.
See plansApprovals
Every write waits for your approval
Every write waits for an exact approval, and every change is checked after it lands.
See approvalsTools
402 tools across your fund
Operator can use every tool on your record, from CRM search to capital calls.
See the toolsCLI & MCP
Operator in your terminal, CI or agent
Run Operator from your shell, your scripts and your CI, or hand it to your own agent over MCP.
See the CLI
Works with
Products that run on the same login and record.
Common questions
No. Reading is automatic; writing isn’t. Every change waits for approval from you or someone you’ve delegated to, and only that exact change goes through.
No. Everything works in the app, and the CLI and the MCP server are there for teams who want to script Operator or drive it from their own agents.
Any agent that speaks MCP. Add Operator’s MCP server and your agent gets the same commands as the CLI, under your login and your rights.
Every job and plan shows an estimate before it starts, and runs inside the budget you give it and your organization’s monthly cap.
Operator retries it with what went wrong in hand, up to the plan’s retry budget. If it still fails, that branch stops, the owner is notified, and independent steps carry on.
Hand Operator your back office
Operator does the work on your fund’s record, and nothing changes until you approve it.