THE GRAPH SERIES / Search. Structure. Content.Meet your intelligence stack
Appearance Circadian
Choose your theme

Circadian: Light 6 AM–6 PM. Dark 6–10 PM and 2–6 AM. Agentic 10 PM–2 AM. Motion settings always take priority.

Field notes / Agentic operations

Managed agent operations or in-house automation: compare who carries the failure

Both models can produce the same workflow on launch day. They diverge over the following year: interfaces change, credentials expire, prompts drift, and the person who built the automation gets busy or leaves. The comparison that matters is operational: who watches, who repairs, and who can show the record when a run goes wrong.

YOUR NEXT STEPCHOOSE A GOAL
What would be useful next?

The short answer

Both models launch the same workflow. They diverge over the year that follows: who notices the silent failure, who holds the authority model, and who can produce the record of what ran. Compare the models on operation, not on the demo…

  1. 01 / Establish the context
  2. 02 / Review the right fit
  3. 03 / Take the next step

Your choice stays on this page. No click or selection tracking.

01

The short answer

Build in-house when the workflow embodies your team's judgment, changes often, and someone is genuinely assigned to operate it. Choose managed operations when the workflow is stable and repetitive, when its failure would be silent and expensive, or when operating it well is not the work your team exists to do.

Either way, two assets must remain yours: the authority model (what the system may do, what needs approval, what it must never do) and the run record. A model you cannot state and a history you cannot read are the real risks; the build location is secondary.

02

Decision criteria

  • How many workflows are there, and how often does each one change?
  • If a workflow failed silently tonight, who would notice, and when?
  • Where does the authority model live: a document, a system setting, or one person's memory?
  • What record could you show a client, an auditor, or yourself in six months?
  • Is operating automation a core skill of this team, or a means to an end?
  • What does a day of this workflow not running actually cost?
03

Side by side

Launch day looks the same. These rows are the year that follows.
DimensionIn-house automationManaged agent operations
BuildYour team designs and buildsBuilt with you; operated by the provider
MonitoringYour responsibility, and often nobody's assigned jobThe operator's standing job, with agreed reporting
The 2 a.m. failureFound when someone notices, often by its effectsFound by observability; handled under agreed rules
Authority and approvalsAs good as your team's documentation disciplineDefined in the operating agreement and enforced in the system
Knowledge riskConcentrated in whoever built itHeld by the operator, against records you can inspect
Cost shapeStaff time plus tooling; spiky around incidentsPredictable operating fee; incidents are the operator's problem
04

Tradeoffs that decide it

In-house wins on control and learning: the team that operates its own automation understands its business more deeply, and can change a workflow the same day the need appears. Managed operations win on continuity: the workflow does not depend on one person's memory, calendar, or continued employment, and its record is kept by someone whose job is keeping it.

The deciding question is what the workflow is. If it differentiates the business, own it and staff it properly. If it is infrastructure the business relies on, treat reliability as the feature, and be honest about whether the team will still be watching it in month nine.

Workflow observability services
05

Operating the agent after the build

The build is the easy half. An agent that works on the day it ships still needs someone to watch it, and that watching is the durable cost. The question is not whether the agent can do the task. The question is who notices when it does the task badly, who can change what it does, and who is responsible when it acts on bad input.

Observability is the first requirement, and it is a record, not a dashboard. For every run, keep the inputs, the actions taken, the outcomes, and the exceptions, written so a person can read them later. The run log is how a team learns whether the agent is improving or drifting, and it is the evidence that supports a decision to expand what the agent is allowed to do. An agent without a run log is an agent nobody can defend.

Human review is the second requirement. Some actions need a person before they happen — anything that spends money, contacts a customer, or changes a public record. Some actions need a person after they happen — a sample of routine runs, reviewed on a schedule, so the team sees the quality of the work rather than only the exceptions. The review points are set when the agent is designed, not added after the first mistake.

The operating cost is the sum of the runs, the review time, and the exceptions. A managed operation carries that cost as a service: the provider watches the runs, handles the exceptions, and reports the outcomes. An in-house operation carries it as staff time. Either way, the cost exists, and the decision is about who carries it — not whether it can be avoided.

The review points are also the off switch. When the run log shows a pattern of bad actions, the team that can see the log can also stop the agent, narrow what it is allowed to do, and restore the previous process while the cause is found. An agent that cannot be stopped is not an agent. It is a liability.

06

Common questions

Do we lose control with managed operations?

Control is the authority model: what may run, what needs approval, what never runs. If that is not explicit, you do not have control in either model; if it is, managed operation executes your model rather than replacing it.

What should stay in-house?

Workflows that embody your judgment and change weekly. Hand over the stable, repetitive ones first; they benefit most from being watched and least from being rebuilt.

What record should exist either way?

For every run: inputs, actions taken, outcomes, and exceptions, written so a person can read them later, and kept with the business rather than only inside a tool.

Accessibility & reading

Adjust this site to your needs. Preferences stay on this device. Your browser’s zoom and assistive technology continue to work.

Reading text size

100%

100%, 112%, 125%, or 150%. You can also use your browser’s zoom.

Reading preferences

Motion and attention

Your device’s reduced-motion setting takes priority.

Need another way to access something?

Tell HGM the page, the task, the barrier, and your preferred format or way to communicate. You do not need to share medical details or create an account.

No analytics, retargeting, advertising pixels, tracking identifiers, or sale of visitor data. These controls use local device storage only.

These optional controls support access. They do not replace accessible page design or an individualized accommodation process.

Find your next step.

Marketing Intelligence Infrastructure | Holistic Growth MarketingCompany & ecosystemAbout HGM | Holistic Growth MarketingCompany & ecosystemCompany Profile | Holistic Growth MarketingCompany & ecosystemServices | Holistic Growth MarketingCompany & ecosystemGraph Series | Holistic Growth MarketingGraph SeriesSchemaGraph | Holistic Growth MarketingGraph SeriesSearchGraph | Holistic Growth MarketingGraph SeriesCopyGraph | Holistic Growth MarketingGraph SeriesSearch Intel OS | Holistic Growth MarketingCompany & ecosystemPlatform Architecture | Holistic Growth MarketingCompany & ecosystemMarketing Intelligence Infrastructure | Holistic Growth MarketingCompany & ecosystemData Governance | Holistic Growth MarketingCompany & ecosystemDeployment Architecture | Holistic Growth MarketingCompany & ecosystemCustomer-Controlled Data Infrastructure | Holistic Growth MarketingCompany & ecosystemCRM Integrations | Holistic Growth MarketingCompany & ecosystemIntelligence CRM | Holistic Growth MarketingCompany & ecosystemPricing and Engagements | Holistic Growth MarketingCompany & ecosystemGraph Series Subscriptions | Holistic Growth MarketingCompany & ecosystem