Administration, release management, monitoring and enhancements from one named team of admins, Apex and LWC developers and integration engineers, on a monthly retainer sized to your backlog.
Most Salesforce orgs do not need a full-time team. They need reliable hours every week, somebody who can read Apex when a Flow is not enough, and a release process that does not break Friday afternoons.
Users, permission sets, layouts, Flows, reports, dashboards, data fixes and duplicate rules. The daily work, done quickly and logged.
Sandbox strategy, source-driven deployments, test coverage kept healthy, release notes per window. See Apex and LWC.
Scheduled job failures, integration errors, API and storage limits, login anomalies, Apex exceptions. Routed to a person with context, not a mailbox.
Small builds inside the retainer: a new object, an LWC component, an integration tweak, an Agentforce topic. Larger work is scoped as a project.
Two lanes, one queue. Urgent issues bypass the sprint; everything else ships in a planned window with notes. Alerts from monitoring enter the same intake as human requests, so nothing is handled off the books.
Pick by the volume and complexity of change, not by headcount. Every tier has a named lead engineer and a monthly report. Pricing follows the hours band and coverage window; ask for a quote.
For stable orgs with light change and an in-house admin who needs backup.
For orgs with custom code, a few integrations and a steady stream of requests.
For multi-cloud orgs, live AI features and teams that ship every week.
A retainer stays predictable only if the boundary is explicit. Out-of-scope work is still ours to do; it is estimated and scheduled as a project so the monthly band is not silently consumed.
| Area | In the retainer | Scoped separately |
|---|---|---|
| Configuration | Flows, layouts, permissions, reports, validation rules | New cloud roll-outs, re-implementation |
| Code | Bug fixes, small components, test coverage upkeep | Multi-sprint custom builds |
| Integrations | Monitoring, retries, mapping changes | New integrations with new systems |
| Data | Duplicate rules, data fixes, small imports | Full migrations and org merges |
| AI features | Agentforce topics, prompt tuning, evaluation runs | New AI use cases from the AI roadmap |
| Users | How-to answers, admin questions, refresher sessions | Full end-user training programmes |
Week one: read-only access, metadata export, a list of every integration, scheduled job and the person who owns it.
A compressed health check across debt, security, performance and adoption. The score is what we report against.
We import your request list, agree severities, pick release windows and the monthly report format.
Written procedures for releases, incidents, user onboarding and each integration we now watch. Yours to keep.
From week three or four: triage within a working day, releases on cadence, monthly report with hours and burn-down.
Retainers end, and they should end cleanly. When you hire an in-house admin or bring the platform back into your own engineering team, we hand over in 30–60 days. You get the runbooks, the release pipeline, a named owner for every integration, and paired sessions with your new people until they are comfortable.
Everything we built lives in your org and your repository, not ours. There is no proprietary tooling in the path, so a different partner could pick it up tomorrow. Commercial terms, notice periods and how retainers compare with fixed-scope projects are set out under engagement models. The most common questions are answered in our FAQ.
The baseline every retainer starts from: debt, security, performance, adoption.
ReadThe release pipeline and coding standards we run your org on.
ReadHow we keep AI features measured, cheap and safe once they are live.
ReadRetainer, fixed scope or team extension: which fits which kind of work.
ReadPricing, process, time zones and how we start.
ReadImplementation, clouds, AI, development, integrations and support.
BrowseDay-to-day administration, release management with a sandbox pipeline, monitoring of jobs, integrations and limits, and small enhancements inside a monthly hours band. Larger builds, new clouds and full migrations are scoped separately so the retainer stays predictable.
Every request gets a severity at triage. P1 (users blocked, data at risk) and P2 (a team degraded) go to the hotfix lane. P3 and P4 go to the sprint backlog and ship in the next release window. You see the queue and can reorder it; we tell you when a reorder pushes a date.
Yes, and it is the most common set-up. Your admin keeps the user-facing work and the business relationships; we take releases, code, integrations and the backlog they never reach. Runbooks are shared so either side can cover the other.
Tiers can move up or down at a month boundary with notice, and unused hours are reported rather than hidden. When you take the platform in house we hand over in 30–60 days. See engagement models for how retainers are structured.
On the Extended tier, yes: topic and prompt changes, evaluation runs against a fixed test set, cost tracking and incident handling. For external LLM services we apply the same practice described under LLMOps and monitoring.
Our teams sit in the UK, Australia, India, Sweden and South Korea, so extended coverage across 18+ time zones is practical on the Extended tier. We agree the actual window and the response targets in writing rather than promising a blanket 24/7.
Tell us about your systems, your data and your constraints. We reply within one business day with a straight answer and a suggested next step.