Get in Touch
About Us Insights Newsroom Gallery Why AtomicNorth Get in Touch

Salesforce
Managed Services

Salesforce ships three seasonal releases a year whether or not you are ready for them. Between those, the backlog of small changes grows faster than any one admin can absorb, and the org slowly becomes something nobody fully understands.

Run, change and release, by the same team, against one backlog.

ReleasesThree a year

Spring, Summer and Winter, tested against your org in a sandbox before they land.

Covered24×7×365

Shift handover crosses time zones, so overnight is a working shift rather than a pager.

BacklogOne queue

Incidents, changes and enhancements prioritised together instead of competing.

ReportingMonthly

Volumes, release impact, org health and technical debt, with owners and dates.

What is included

Running the org, and changing it

A managed service that only keeps the lights on leaves the backlog growing. The change half is the point.

Administration

Users, permissions, data quality, reports and dashboards, sandbox refreshes and the steady stream of small requests that otherwise queue behind the important work.

Joiners, movers and leavers run to a documented process with an audit trail, which is also what an access review asks for.

The routine handled without it becoming anyone's afternoon.

Release management

Each seasonal release reviewed against your org, tested in a sandbox ahead of the window, and anything affected fixed before it reaches production.

Release notes are read against what you actually have configured, not forwarded in full to somebody who has to work it out.

A release that arrives as a non-event.

Backlog delivery

A standing allocation of change each month, sized from your real history, so enhancements ship on a cadence instead of waiting for a project.

Most Salesforce frustration is not incidents. It is a list of small changes that never reaches the top of anyone's day.

The small things actually shipping.

Org health

Technical debt tracked deliberately: overlapping automation, unused fields, stale permission sets, API consumption and limits, with a plan rather than a list.

Debt that is only measured at audit time is debt that gets paid at the worst moment.

A position you can state, not guess.

Incident support

Incidents worked to agreed response and resolution targets, with a recurring problem opened as a problem record rather than appearing again next month.

An incident that recurs is a defect in the service, not a line item.

Causes closed, not just tickets.

Security and access

Permission and sharing reviewed on a cycle, least privilege maintained rather than restored, and findings reported with a remediation owner and a date.

Permission debt becomes visible the moment an audit or an AI feature starts surfacing records somebody should never have seen.

An access model that stays explainable.

Transition: the first sixty days

WeeksOne to TwoInventory

What is actually in the org: objects, automation, integrations, permission sets, installed packages, API consumers and the things nobody has opened in two years.

Most orgs surface at least one surprise here. Finding it in week one is the point of the exercise.

You receive:

An org register and a debt list

Every customisation with an owner and a status, plus technical debt ranked by what it would cost you on the day it matters.

This is yours whether or not the engagement continues.

WeeksThree to FourInstrument

Monitoring and alerting on the parts that fail quietly: integrations, scheduled jobs, API consumption, data quality rules and the sandbox refresh cycle.

A failed overnight job that nobody is told about is discovered by a user, usually the one who can least afford it.

You receive:

Alerting with an owner on each

What is watched, what the threshold is, who is told and what they do about it, written down rather than carried in somebody's head.

Thresholds come with the reasoning behind them.

WeeksFive to EightTransition

Support moves across in a planned order, with the outgoing admin or partner shadowed rather than switched off, and run books written by the people receiving the work.

Nothing transfers until its run book has been executed once under supervision.

You receive:

Run books and a live queue

Documented procedures for the recurring work, an escalation matrix with names, and a backlog you can see into at any time.

The queue is visible to your team, not just ours.

WeekNine OnwardRun

Steady state: incidents to target, the monthly change allocation shipping, seasonal releases tested ahead of the window, debt worked down on a plan.

Improvement is part of the service rather than a separate proposal.

You receive:

A monthly service review

Volumes, target attainment, what shipped, release impact, org health and the remediation plan for whatever slipped.

Written to be read by your board, not by us.

01
Coverage

What is watched, and what happens next

Response targets are the standard commitment. Regulated orgs and fixed trading peaks are quoted separately.

Salesforce Managed Services: coverage, area, what is watched, first action, response target
AreaWhat is watchedFirst actionResponse target
IntegrationsInterface failures, retries, reconciliation, API headroomFailure triaged, replayed or escalated to the far end15 min, P1
Scheduled jobsBatch, scheduled Flow and Apex, data exportsJob rerun, root cause opened as a problem record30 min, P2
Seasonal releaseRelease notes against your configuration, sandbox testAffected items fixed before the production windowAhead of the window
User accessPermission changes, access requests, review cycleRequest fulfilled to process, exception escalated4 hrs, P3
Data qualityDuplicate rules, validation failures, required-field gapsException report to the data ownerWeekly
Org limitsAPI consumption, storage, governor headroomReported with headroom before it becomes an outageMonthly, sooner on trend
Commercials

Priced on the org, not on the ticket count

Quoted against the inventory taken in week one: users, customisation, integrations and release cadence. A fixed monthly fee covers run, release and a standing allocation of change.

There is no charge for incident volume. A month with more incidents costs the same as a quiet one, which is the only arrangement that leaves us on the same side of the problem as you.

Talk to an expert
  • In the monthly feeAdministration, incident handling, release testing, org health reporting, the standing change allocation and the service review.
  • Quoted separatelyNew cloud rollouts, major integrations, migrations, and programmes of work that change the shape of the org rather than keeping it running.
  • Never chargedIncident volume, out-of-hours calls inside the covered scope, and the org register, run books and documentation you take with you if you leave.

Scope and targets are set after discovery, against the org as it stands.

Questions we get asked

Before you send an RFP

Can you work alongside our in-house admin?

That is the common arrangement. The internal admin usually keeps the business relationship and the decisions; we take the volume, the release testing and the overnight cover. The split is written down explicitly so nothing falls between the two.

What happens at a seasonal release?

The release notes are read against what you actually have configured rather than forwarded whole. Anything affected is tested in a sandbox ahead of the production window and fixed before it lands. The aim is that the release is a non-event.

How is change handled against a fixed fee?

The fee includes a standing allocation of change, sized in week one from your real history. Work beyond it is estimated and approved before it starts, and anything that changes the shape of the org is a project and quoted separately.

What do we keep if we leave?

Everything. The org register, run books, documentation, monitoring configuration and ticket history are yours throughout, not handed over at exit. Being replaceable is part of how the service is designed.

Send us theorg.

However much of it nobody can explain. The first conversation is a scoping call, and the week-one inventory is yours whether or not you appoint us.

Get in touch +91-120-4849200