Care plan (AMC)

A care plan is the ongoing operations agreement that starts once a system is in production. It defines what is monitored, how quickly incidents are acknowledged and resolved, what routine work is included, such as security patches, dependency upgrades, model and prompt updates, and how much engineering time is reserved for small changes. Eazyware's Care Plans run at Essential $1,000, Standard $2,500 and Enterprise $5,250 and above per month, with cover, response times and included hours increasing across tiers.

For AI systems a care plan has to cover things a traditional AMC did not: evaluation runs after provider model updates, prompt regression checks, inference cost review, and handling model deprecations when a provider retires a version. Without these, an AI feature quietly degrades even though no code changed.

A care plan is not a development contract. New features and large changes are scoped separately. It is also not the same as hypercare, the intensive first weeks after go-live, which is usually included in the delivery programme and hands over into the care plan.

• CTO / Head of Engineering: guarantees someone is watching production and patching it, without pulling the internal team off roadmap work.
• CFO: converts unpredictable emergency spend into a fixed monthly line that can be budgeted for the year.
• Operations head: gives a single escalation path with agreed response times when something breaks during business hours.
• Product manager: reserved hours allow small improvements to ship monthly rather than waiting for a project budget.

Care plans exist because software does not stay working on its own. Dependencies get vulnerabilities, cloud providers change APIs, traffic patterns shift and, for AI systems, model providers update or retire models. Without an agreement, these arrive as emergencies handled by whoever is available, at whatever rate. A care plan makes maintenance deliberate: scheduled patching, monitored alerts, evals re-run on change, and a known person to call. The trade-off is a fixed cost in quiet months. For a system the business depends on, that cost is almost always lower than the first unplanned outage or the security incident that a missed patch would have prevented.

• A SaaS company keeping its in-app copilot on a Standard plan so that provider model updates are evaluated before they reach customers.
• An NBFC with an Enterprise plan covering 24x7 monitoring of its KYC extraction pipeline and quarterly security patching evidence for auditors.
• A hospital network maintaining its voice agent under a plan that includes monthly call-quality review and telephony vendor updates.
• A retailer on an Essential plan for a personalisation engine that needs dependency updates and occasional model retraining.
• A university keeping a modernised ERP patched and supported through the academic year with reserved hours for regulatory report changes.

Eazyware programAn Eazyware programme rather than a skill: a tiered monthly agreement delivered through Maintenance & Support. Tiers and inclusions are listed on the pricing page, with AI-specific cover such as eval re-runs and deprecation handling built in.

Eazyware service that covers it: Software Maintenance & Support. Starting prices are on the pricing page.