Operators
An Operator owns the outcome. A Mission tells it what done means.
An Operator is a persistent AI worker. Give it a Mission — a business outcome that needs to keep getting done — and it carries the work across the systems and people involved, asks when judgment is needed and verifies the result.
What an Operator owns
One worker. One outcome. Everything needed to carry it responsibly.
The Mission defines the outcome. The Operator holds the context, trigger, rules, systems, controls, exceptions and proof needed to keep carrying it.
Operator = the worker. Mission = the outcome it owns.
- ObjectiveWhat outcome are we trying to achieve?
- Every confirmed customer reaches a genuinely ready onboarding state.
- ContextWhat does Ordmere need to know about the business?
- What was sold, who owns the customer, the target date and the approved onboarding requirements.
- TriggerWhen should the Mission run?
- Whenever a new customer is confirmed.
- RulesWhat business logic matters?
- Routine coordination can proceed. Scope or committed-date changes require approval.
- SystemsWhich systems does it touch — with what access?
- Email, Customer Records, Shared Files and Team Tasks — only the data this Operator needs.
- ControlsWhat happens automatically, and what needs a person?
- Routine onboarding moves automatically. Scope, timing or consequential customer commitments ask first.
- CompletionWhat evidence proves it succeeded?
- Every required item is complete, owned or explicitly accepted as an exception — and the customer is genuinely ready.
- ExceptionsWhat happens when work can't finish?
- Missing inputs, conflicts, blocked dependencies and system failures stay open until resolved or explicitly accepted.
Good Operator Missions
Where an Operator earns its keep.
A strong Operator Mission
- Happens repeatedly — hourly, weekly, or whenever something arrives
- Crosses systems, people or time
- Has a real finish line, not just a response
- Depends on rules, and has exceptions
- Sometimes needs a person to approve
- Needs proof that it actually got done
Probably not an Operator Mission
- One app already does the whole job, start to finish
- A one-off question with no ongoing state
- “Automate everything in the company”
- Moving money without anyone's approval
Ordmere will tell you when a single platform already does the job well.
Mission Maps
Every Mission has its own shape.
No shared template with the nouns swapped. Ordmere draws each Mission's lifecycle from what it has to achieve — so you can see where systems take part, where your team steps in and what “done” means.
Customer Onboarding Operator
Whenever a new customer is confirmed · Owner: Customer Operations
01Start
New customer confirmed
- Pick up what was sold, who owns the relationship and the target start date
Systems: Customer Records
02Understand
What was promised is assembled
- Read the relevant messages, scope and customer requirements
Systems: EmailShared Files
03Plan
Owners, milestones and deadlines created
- Turn the commitment into an owned onboarding plan
Systems: Team Tasks
04Coordinate
Missing inputs and dependencies kept moving
- Request what is missing, follow owners and keep the plan current
Systems: EmailTeam Tasks
- Anything that changes scope, timing or commitment waits for the right person
05Resolve
Blockers stay open until resolved
- Retry safe failures, reroute blocked work and preserve the full state
- Unclear or consequential exceptions arrive with the evidence and a recommended next step
06Ready
Customer and internal teams are ready
- Confirm the required setup, handoffs and customer communication
Systems: Customer RecordsEmail
07Verify
Onboarding is actually complete
- Every required item is complete, owned or explicitly accepted as an exception
- No dependency is left without an owner
- Customer records, tasks and communication agree on the outcome
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
The customer has not supplied something required
- The missing item gets an owner and deadline
- Independent work keeps moving
What was sold conflicts with the onboarding plan
- The conflicting evidence is assembled
- Nothing consequential changes until approved
A dependency puts the target start date at risk
- The risk is surfaced before the deadline
- A recovery plan stays tracked until resolved
The same task or request already exists
- Existing work is reused
- A duplicate is never created
A connected business system is temporarily unavailable
- State is preserved and safe work continues
- The blocked step is retried and never assumed complete
Research, qualify and record target accounts
Every week · Owner: Sales
01Discover
Companies that may fit
- Find companies that may fit
Systems: Public web
02Research
Decision-makers and evidence
- Identify the right decision-makers and the evidence
03Qualify
Checked against your ICP
- Check each against your ICP
- Contacts Ordmere isn't sure about go to Sales
04Record
Prospects in HubSpot
- Add qualified prospects to HubSpot
Systems: HubSpot
05Prepare
Outreach ready for Sales approval
- Draft outreach for each prospect
Systems: Gmail
- Every outreach draft is approved by Sales before it's sent
06Verify
Verified next action for each prospect
- 25 qualified prospects recorded in HubSpot, each with its evidence
- Each has outreach ready for Sales
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
Company doesn't match your ICP
- Recorded as not a fit, with the reason
- Not added to HubSpot
Decision-maker can't be confirmed
- Held for review with the evidence found
- Nothing drafted until it's confirmed
Company already in HubSpot
- The existing record is enriched, never duplicated
Not enough public evidence
- Kept as a candidate, not recorded
- Retried next run
Watch traffic and conversion, and follow incidents to resolution
Every hour · Owner: Operations
01Observe
Website traffic and conversion read hourly
- Read website traffic and conversion hourly
Systems: GA4
02Compare
Against the normal range
- Compare with the normal range
03Detect
Material change classified
- Decide whether the change is material
04Escalate
Operations alerted
- Alert Operations in Slack
Systems: Slack
- Operations owns every incident until it's resolved
05Resolve
Resolved or handed off
- Follow the incident until it's resolved in Linear
- Each incident is resolved or explicitly handed off
- Every run is checked, including runs with a missing source
Systems: Linear
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
A data source can't be read
- Reported as a gap, never as all clear
- Retried next run
Signals disagree
- Flagged to Operations with both readings
Incident has no owner
- Escalated along the escalation path
- Kept open until someone takes it
Alert couldn't be delivered
- Retried, then sent another way
- Kept open until acknowledged
Reconcile supplier invoices against purchase orders
Every week · Owner: Finance
01Receive
Supplier invoice received
- Detect new supplier invoices
- From email · Gmail
Systems: Gmail
02Match
Invoice and purchase order
- Read each invoice and its supporting files in Google Drive
- Find the matching purchase order in NetSuite
Systems: NetSuiteGoogle Drive
03Evaluate
Match, mismatch or above $1,000
- Compare supplier, PO number and amount
- Apply the $1,000 review threshold
- Invoices above $1,000 go to Finance for review
- Mismatches go to Finance to resolve
04Record & route
Result recorded, exceptions routed
- Record the result in NetSuite
- Route mismatches to Finance
- Send invoices above $1,000 to Finance
Systems: NetSuite
- Reconciliations above $25,000 need CFO sign-off before Ordmere records them
05Verify
Verified reconciliation
- Every invoice received this week ends matched, in review, or open with a reason
- Each recorded result is confirmed in NetSuite
When work can't finish
Nothing is dropped. Unfinished work stays open until it's resolved.
No matching purchase order
- Kept open — never marked reconciled
- Missing purchase order requested from Finance
- Reconciliation resumes when it arrives
Invoice and purchase order disagree
- Differences recorded with the evidence
- Finance resolves the discrepancy
- Re-checked, then completed
NetSuite can't be reached
- Nothing is marked complete
- Retried on the next run
- You're told if it keeps failing
Mission vs. automation
Automation performs steps. An Operator owns the outcome.
Automation tools are excellent when you know the exact trigger and steps. An Operator starts from the outcome, works through changing context and exceptions, and keeps going after the first step fires.
Fast and reliable — when the happy path is the whole job.
When X happens, the Operator:
- Understands what happened
- Checks the relevant context
- Works out what state the work is in
- Applies your rules
- Takes the actions it's allowed to
- Asks for approval when required
- Checks the outcome actually happened
- Handles exceptions
- Recovers when it can
- Escalates when it should
- Records the evidence
- Continues until the outcome is complete
Already using Zapier, Make or n8n? Keep them for the deterministic steps they are good at. Operators are for the responsibility around those steps.
When the work changes
When the work changes, the Operator adapts with you.
Tell Ordmere in plain language. It shows exactly what changes in the Mission, systems and controls before anything takes effect.
New access is never added silently, and rules you set are never relaxed without you.
“Keep the target start date, but ask me before anything changes what we promised the customer.”
- Target start date stays unchanged
- New rule: commitment changes ask first
- Access unchanged — nothing new requested
Completion
The Operator is done when the outcome is verified.
Not when an action ran. The Mission defines what must be true, and the Operator checks that business state before calling anything complete.
Revenue
Research, qualify and record target accounts
Complete when
- 25 qualified prospects recorded in HubSpot, each with its evidence
- Each has outreach ready for Sales
Operations
Watch traffic and conversion, and follow incidents to resolution
Complete when
- Each incident is resolved or explicitly handed off
- Every run is checked, including runs with a missing source
Reconciliation
Reconcile supplier invoices against purchase orders
Complete when
- Every invoice received this week ends matched, in review, or open with a reason
- Each recorded result is confirmed in NetSuite
Know the pain, not the Mission yet?
That's normal. Start with what your team keeps chasing and Ordmere helps turn it into a Mission.
What outcome should an Ordmere Operator carry for you?
Start with one outcome. Build from there.