Salesforce AMS: what managed services include and when they pay off

The choice is not about the hourly rate, it is about how your requests arrive: continuously, or one project at a time.

Support: answering user questions, fixing permission issues, helping with reports and dashboards.

Corrective maintenance: investigating and fixing bugs in configuration, automations and code.

Small enhancements: new fields, page layout changes, validation rules, Flow adjustments, small report and dashboard work. The boundary between a small enhancement and a project is usually defined in hours: anything under a set threshold is covered by the plan, anything larger is quoted separately.

Platform hygiene: reviewing release updates, monitoring storage and API limits, cleaning up unused metadata, keeping documentation current.

A service level agreement defines how fast the provider reacts to each type of request. A typical structure: blocking issues acknowledged within a few business hours and worked on immediately; standard requests acknowledged within one business day and scheduled; enhancements planned within the monthly hours. What matters is that the SLA is written, measurable and reported, not that it is aggressive.

Most plans are a monthly fee for a bundle of hours, with a lower effective hourly rate than one-off work because the provider can plan capacity. Good plans let unused hours roll over to the next month and allow the bundle to be resized with short notice. Watch for minimum terms longer than three months and for plans that charge full price for hours you did not use.

You have more than a couple of requests per month and are tired of asking for a quote each time.

You have no internal admin, or your admin is part-time and overloaded.

You want a known monthly cost for budgeting.

You need someone who already knows your org when something breaks, instead of onboarding a new provider under pressure.

When it does not: if you have a single well-defined project and no recurring needs, a fixed-price quote is simpler and costs less overall. An AMS plan buys reserved capacity and a guaranteed response time, not a discount on the hourly rate.

Most AMS enquiries do not come from companies with nobody: they come from companies that have a provider and are unhappy with it. The handover scares people more than it costs, because it looks as if the org will be left uncovered in the middle. In practice it is not, if the order is this one.

First the inventory, with read-only access: active automations, Apex classes and triggers, Flows, integrations and service users, scheduled jobs, profiles and permissions. It tells you what is being taken over, and nobody can block it: these are your org's metadata.

Then the list of keys. Integration users and their credentials, connected apps, certificates and their expiry dates, the code repository if one exists, documentation, access to sandbox environments. This is where a handover actually stalls: ask for that list in writing before you send the termination notice, not after.

Then the dates. End of the current contract, notice period, tickets still open and who closes them. A month of overlap costs a fraction of an outage and takes the hurry out of it for all three parties.

Finally the first month: normal requests get worked while what the inventory found gets fixed in parallel. Anyone who takes over and tells you straight away that everything is fine has not looked.

Cloud Atelier AMS plans start at €370 per month with eight hours included, a response within one business day, unused hours rolling over for three months and a three-month initial term. Larger bundles are available and can be adjusted monthly. Describe your org and you get a proposed size within one business day.