FAQ
Questions, answered plainly.
Understand the value, the controls and the next step—from your first Mission to ongoing work.
General
What is Ordmere?
Ordmere is a platform for persistent AI Operators. Each Operator carries one Mission — a recurring business outcome with explicit context, controls and a definition of done.
You describe what needs to happen. Ordmere helps define the Mission, understands the context, identifies the systems and access it needs, and works within the controls you set. It's designed to keep the state of the work over time and surface exceptions when a person is needed.
Is Ordmere an AI agent?
Yes, of a specific kind. An Operator is a persistent AI worker with one Mission.
You don't assemble or manage a team of agents. You give an Operator an outcome, set its boundaries, and govern the work in Mission Control.
Is Ordmere a chatbot?
No. Conversation is one way to tell Ordmere what you want. The product itself is an operating layer for recurring work.
A chatbot answers. An Operator keeps the Mission moving.
Is Ordmere an automation builder like Zapier, Make or n8n?
Those tools are excellent when you know exactly which trigger, steps and integrations to connect.
Ordmere starts somewhere else: the business outcome. It works out the rules, context, systems, permissions, approvals, completion criteria and exceptions with you. You never build a node graph — and you can keep your existing automations for the steps they do well.
Why wouldn't I just build an AI agent myself?
You can. The difficult part usually comes after the demo:
- How does it authenticate, and what is it allowed to do?
- How does it remember the state of ongoing work?
- What happens when data is missing, or two systems disagree?
- When should it ask for approval?
- How are duplicate actions prevented?
- How do you know the result actually completed?
- What happens after an API failure — and who maintains it when things change?
Define the supported scope, permissions and completion criteria in your Mission agreement.
Missions
What exactly is a Mission?
A Mission is a defined, recurring business outcome Ordmere is responsible for operating.
It includes the objective, the context it needs, when it runs, the business rules, the systems and capabilities it uses, its control boundaries, what counts as complete and what happens when work can't finish.
What makes something a good Mission?
Missions are most useful when work:
- happens repeatedly
- crosses systems
- depends on rules
- needs follow-up or can become overdue
- has exceptions
- sometimes needs approval
- needs evidence that it's complete
What isn't a good Mission?
If one application already completes the whole job cleanly and reliably, adding Ordmere may add little. Ordmere checks this when you describe a Mission and will tell you.
Ordmere is strongest in the gaps between systems, people and decisions.
Do I need to know exactly what I want Ordmere to automate?
No. Many people know the pain before they know the solution. You can start by describing:
- something repetitive
- something people constantly chase
- a process that falls through the cracks
- a recurring report
- systems somebody keeps checking
- a responsibility you wish somebody reliably owned
Ordmere helps shape that into a Mission with you.
Can Ordmere suggest Missions?
The intended experience would identify recurring cross-system work from approved company context and explain why it might make a useful Mission.
Today, the site and setup offer starting points you complete in your own words.
Can a Mission change over time?
Yes. You can change a Mission in plain language during setup, and Ordmere shows exactly what changed in its definition, systems and controls.
The design requires deliberate and visible changes to rules, permissions and completion criteria.
Getting started
How long does setup take?
It depends on the Mission. A narrowly defined Mission may take a few minutes to describe and shape; a complex one may need more company context, systems or approval boundaries.
The goal isn't to complete setup for its own sake. It's the first useful result, as quickly as is responsible.
Why doesn't Ordmere use a normal setup wizard?
Because businesses aren't identical. A giant questionnaire either asks irrelevant questions or misses the important ones.
Ordmere asks for the next piece of context only when it changes the Mission — and skips anything it already knows.
Will I have to explain my company every time?
No. Company context you add — your website, a policy document, how your teams work — carries over to your next Mission, so it starts from what Ordmere already understands.
Ordmere asks when something is missing or ambiguous, not because every Mission starts from zero.
What is the supervised first run?
Before a Mission runs routinely, Ordmere is designed to run it once under supervision. You inspect what it found, what it understood and decided, what it would do, the evidence and whether completion was reached — and correct anything before trusting it with recurring work.
Define the supported scope, permissions and completion criteria in your Mission agreement.
Controls & approvals
Can Ordmere take actions without asking me?
Only within the permissions and controls set for that Mission. Each action is set to happen automatically, to ask first, or never to happen.
Financial and destructive actions are never offered as automatic, and if no rule allows an action, it doesn't happen.
Can I require approval before an email or external message is sent?
Yes. External messages ask first by default in Work with approval, and some Missions never request permission to send at all — Ordmere drafts, and a person sends or approves.
Needs You is designed to bring the draft, evidence and approval decision together.
Can I limit how much Ordmere can spend?
Define explicit limits in your Mission agreement: items per run, messages per day, retries and amount thresholds that need approval.
The principle: financial autonomy always has visible boundaries.
What happens when Ordmere doesn't know what to do?
It shouldn't bluff. If information is missing, a rule conflicts, permissions are insufficient or the situation is beyond the Mission's allowed autonomy, Ordmere is designed to stop that action and surface it as a Needs You decision.
You can already see this in setup: conflicting instructions become a decision for you, never a silent choice.
What is Needs You?
Needs You is designed to bring together decisions that need a person: what happened, why Ordmere stopped, what it recommends, the evidence and what's needed from you.
Instead of monitoring everything Ordmere does, you handle only what needs judgement, approval or information.
Completion & reliability
How does Ordmere know a Mission is complete?
Every Mission defines explicit completion criteria when it's set up — for example, “every qualifying order appears exactly once and matches its current state.”
At run time, Ordmere is designed to verify that business state rather than call work finished because an action was attempted.
What happens if an integration fails?
The Mission is designed to keep its state. Depending on the failure and the Mission's controls, Ordmere retries where that's safe, waits, or surfaces the exception for a person.
Every Mission already defines what happens when a system is unavailable. A transient failure should never make ongoing work vanish.
What happens if two systems disagree?
That's exactly the cross-system exception Ordmere is built for. A Mission can set which source is authoritative, which differences are acceptable and when to escalate.
When a discrepancy can't safely be resolved automatically, Ordmere is designed to surface it with the evidence from both sides.
Does Ordmere keep a history?
Mission History is designed to record meaningful activity — actions, decisions, approvals, exceptions, recovery and outcomes — so you can see what happened and why.
In setup today, every change to a Mission's definition, systems and controls is already tracked and shown.
Integrations
What can Ordmere connect to?
Ordmere is designed to work with the systems Missions depend on: email, files, collaboration, CRM, ecommerce, finance, support, analytics, spreadsheets, projects and custom APIs.
Explore the software and source examples on the Integrations page. Your Mission agreement defines the supported systems, access and permissions; choosing a demonstration does not connect an account.
Do I need to connect every system I use?
No. A Mission requests only the systems and capabilities it needs to finish — and tells you which ones are optional.
Why does Ordmere need access to my accounts?
Only because a Mission needs to read information or take an approved action inside a system.
Each requested capability comes with its reason (“Read new orders — to find orders over $500”), alongside what Ordmere doesn't need.
Can I disconnect an integration?
Yes. A connection can be removed once no Mission depends on it, and removing a Mission removes only that Mission's access.
If disconnecting would stop an active Mission, Ordmere tells you what's affected first.
Security & trust
Can Ordmere access everything in a connected system?
No. Connection doesn't mean unrestricted autonomy. Ordmere separates the organization connection, each Mission's access, action controls and approval policy.
A Mission is granted only the capabilities it needs, on the narrowest resource it can justify — one spreadsheet, one channel.
Does Ordmere hide what the AI is doing?
No. You should always be able to see the meaningful actions Ordmere took and the state of the Mission.
Explainability means the rule, the evidence and the result — operational accountability, not a transcript of a model's private reasoning.
What happens with sensitive actions?
Sensitive or consequential actions sit behind approval boundaries. You decide where Ordmere can act on its own and where a person must authorize — and the Mission's own approval rules can't be quietly relaxed.
Will Ordmere ever make a decision it isn't allowed to make?
Mission controls exist to prevent it. The absence of a rule is a denial: when an action falls outside the Mission's boundary, Ordmere fails closed rather than expanding its own authority.
New access is never added silently either — any expansion is shown for your review.
Does Ordmere store my passwords or tokens?
The website demonstrations use simulated connections and do not request account credentials. Your Mission agreement defines supported authorization methods and credential handling before access is granted.
AI & models
Which AI model does Ordmere use?
You don't have to choose a model to create a Mission. Ordmere's job is to use the right underlying capabilities for the work.
The Mission stays the stable thing you manage, even as the AI ecosystem underneath it changes.
What does BYOK mean?
Bring Your Own Key: using your own provider credentials for certain underlying AI or API services, so external usage is billed to your provider account directly.
Your agreement confirms provider support and data-handling requirements before activation.
Do I have to BYOK?
No. What matters is transparency: you should know what external usage applies before you activate a Mission.
Pricing
What does Ordmere cost?
Starter $99/month with 1 Mission; Growth $199/month with 3 Missions; Enterprise by custom quote. Vault Essentials is included. Eligible plans can add active Missions for +$49/month.
Your Mission agreement confirms supported scope, usage and access before activation. Where supported, a first supervised proof lets you evaluate the work before choosing ongoing operation.
What's included in the $99?
Starter includes 1 active Mission and Vault Essentials. Growth includes 3 active Missions and a larger allowance. Both are designed to bring recurring work, knowledge, evidence and approval boundaries into one responsibility.
You pay for the responsibility. No per-seat platform fees or per-task platform pricing. Agree your outcome, supported systems, operating limits and approval rules before activation.
Do I need to pay extra for Vault?
Vault Essentials is included with Starter and Growth. There is no separately priced Vault add-on in the current plan catalog.
Advanced cross-document answers and knowledge monitoring require confirmed scope and support before use. Any external processing costs are agreed separately; essential security, permissions and original document access are not premium features.
What counts as an additional Mission?
Starter includes 1 Mission; Growth includes 3. Each additional scoped recurring responsibility is +$49/month on eligible plans.
One Mission can span several systems and steps. A new Mission means another agreed recurring responsibility, rather than another task or conversation.
Is the first Mission free? Is this a 14-day trial?
The proof is free; ongoing operation isn't. Your first Mission is proven under supervision with a $0 Ordmere platform fee, for up to 14 calendar days from the first supervised proof run.
It's a proof window, not a software trial. The clock doesn't start when you sign up, describe the Mission or connect a system — only when Ordmere starts the supervised proof run.
The proof can end sooner: when the agreed outcome is verified, if the Mission falls outside the agreed scope, if the access or information it needs isn't available, or if continuing would exceed the agreed safety or usage limits. It isn't meant to run as a live production process.
Define the supported scope, permissions and completion criteria in your Mission agreement.
When do I start paying — and what happens after the proof?
Choose Starter $99/month for 1 Mission or Growth $199/month for 3. Your subscription begins only after scope, supported capabilities and usage are agreed and you explicitly activate.
Describing a Mission or requesting a plan does not start a subscription. Where supported, agree a supervised proof before ongoing operation.
Why is the proof free?
Because you shouldn't pay for a promise that has only been configured. Ordmere should show useful work before asking you to rely on it.
What if Ordmere can't prove the Mission?
Then don't activate it. You pay for Missions you choose to keep running, not for trying. If a Mission isn't supportable, Ordmere says so rather than stretching the proof.
Can I run several free proofs?
There’s one free proof per company or organization, for one Mission, unless we agree otherwise. Starter is $99/month, Growth is $199/month, with optional additional Missions as needed.
Are AI, API or provider costs included?
External AI models, APIs and data providers can have separate costs. Your platform fee covers your agreed Mission scope; provider usage is disclosed separately.
Where supported, expected usage and approved limits are part of the agreement before work begins. Paid top-ups require your approval.
Will Ordmere spend money without limits?
No. Define financial limits in your Mission agreement. Consequential financial actions require approval.
Can I stop a Mission?
Yes. You decide whether a Mission stays active.
What about complex or high-volume Missions?
Enterprise deployments receive custom proposals based on verified requirements. Tell us about the work when you describe the Mission, and we'll agree the right plan with you.
Business impact
Is Ordmere supposed to replace employees?
That isn't the goal. Ordmere takes ownership of recurring operational work that consumes attention unnecessarily.
Often that means someone who spends their day checking, chasing and moving information can spend it on work that needs judgement, relationships or expertise.
What should I automate first?
Not the most ambitious process in the company. Start with something recurring, measurable, annoying and bounded — useful enough that you'll notice when it disappears.
Give Ordmere one real responsibility. Let it earn another.
What's the easiest way to understand Ordmere?
Give it something your business repeatedly has to remember. Then watch what happens.
Still wondering?
Give it something your business repeatedly has to remember. Then watch what happens.