What automations cost after they're built

The build is only one part of an automation's cost. The ongoing work appears when a provider changes an API or pricing model, an EHR updates an interface, or an internal scheduling rule changes without the workflow being updated.

Automations are not set-it-and-forget-it. They're more like cars, they need maintenance, and the maintenance cost depends on how complex the system is and how frequently your business changes.

Third-party changes are a recurring risk. Services update APIs, deprecate endpoints, change authentication flows, or alter payloads. The frequency depends on the stack, but without monitoring even a small change can cause a workflow to fail silently or produce the wrong result.

Volume can expose new edge cases. For example, an automation that works at 20 records a day may hit rate limits or concurrency constraints as usage grows. A sudden lead spike can expose assumptions that were reasonable at the original volume but were never tested at the new one.

Business process changes matter too. Your practice adds a new insurance payer. Your real estate team hires agents who specialize in a new area. Your financial firm starts offering a new service. The automation doesn't know about any of this unless someone updates it.

OrchestriAI currently offers ongoing maintenance at $500 per month across workflow automation, AI agent systems, and MCP server development. The exact work depends on the system: monitoring and mapping changes for deterministic workflows, evaluation and output-quality checks for agentic systems, or tool, permission, and authentication updates for MCP servers. Ad-hoc work is scoped separately when a retainer is not the right fit.

I include 30 days of post-launch support with every project. During that window, issues get fixed at no additional cost. After that, you have three options:

1. 1Monthly retainer, I monitor the system and handle fixes proactively. This suits business-critical automations where downtime costs real money.
2. 2Ad-hoc support, You call when something breaks, I fix it. Cheaper month-to-month but you're reactive instead of proactive.
3. 3In-house handoff, I document everything and train your team (or your IT person) to maintain it. This suits technically capable teams that want full ownership.

Clients can start with a retainer and move to ad-hoc support or an in-house handoff once the system, ownership, and support needs are clear.

Prefer documented, versioned APIs and review each provider's deprecation policy. Self-hosting a tool such as n8n can give you more control over update timing, but it also makes infrastructure maintenance your responsibility. Build monitoring into the workflow instead of waiting for a person to notice a failure.

Maintenance stays more manageable when error handling, logging, alerting, and documentation are part of the original build instead of being added after the first outage.