Hire a Salesforce administrator when your org is stable, your needs are mostly day-to-day configuration, and one person can realistically cover them. Choose managed services when you regularly need skills one person does not have, such as development, integration, architecture or release planning, or when losing a single admin would leave you stuck. Many companies do both: an internal admin for daily requests, and a managed services partner for everything else.
What a Salesforce administrator actually covers
A good Salesforce admin keeps the org running and useful: adding users and managing permissions, building fields, page layouts, reports and dashboards, maintaining Flows, handling data imports and cleanup, and answering the steady stream of "how do I" questions. An admin who sits inside the business also builds relationships and context that no outside team can fully replicate.
What a single admin usually cannot cover is everything else a growing org needs: Apex and Lightning Web Component development, integration with ERP and marketing systems, data architecture, security reviews, testing each Salesforce release, and planning larger projects like a new cloud or an AI agent. Those skills exist, but rarely in one person.
What Salesforce managed services include
Salesforce managed services is an ongoing arrangement in which a consulting partner runs and improves your org, drawing on whichever specialist each task needs. A typical scope includes:
- Administration: users, permissions, layouts, fields, reports and dashboards.
- Enhancements: new automation, objects and processes, prioritized with you.
- Development: Apex, Lightning Web Components and integration fixes.
- Release management: reviewing each Salesforce release against your org and testing in a sandbox.
- Data quality: duplicate rules, validation and cleanup jobs.
- Technical debt: retiring unused fields, old workflow rules and overlapping automation over time.
Side by side
| In-house Salesforce admin | Managed services team | |
|---|---|---|
| Skills | One person’s skill set, usually administration and Flow | Admins, developers, architects and integration specialists as needed |
| Coverage | Gaps during vacation, illness or turnover | Continuity if an individual consultant changes |
| Business context | Deep and daily | Built over time; strongest with a named lead |
| Best for | Stable orgs with mostly configuration needs | Growing orgs, multiple clouds, integrations, AI or a backlog |
| Cost model | Salary and benefits, plus training | An agreed monthly scope, separate from project work |
Signs one admin is no longer enough
- Requests sit in a backlog for weeks because the admin is busy firefighting.
- You keep hiring contractors for one-off development or integration work.
- Salesforce releases surprise you; users find the changes first.
- The admin is also doing another job, such as sales operations or IT support.
- Nobody else understands how key automation works.
What to do if your org is already messy
Most managed services relationships start with an org that has history: overlapping automation from several admins, unused fields and reports nobody trusts. The sensible first step is a health check that ranks problems by risk and effort. After that, urgent fixes come first and technical debt is retired steadily alongside new work, rather than pausing everything for a rebuild.
We have seen this pattern repeatedly. A manufacturer whose org had been overcomplicated by several admins streamlined it and integrated NetSuite, and went from zero Salesforce usage to all 99 reps active within 30 days. A demand-generation firm restored reliable Salesforce and Pardot sync across 145,000+ prospects, and a medical-device company removed 970+ invalid records to get its marketing platform working again.
Which skills does each model cover?
An internal admin handles configuration and daily support well, while specialist skills usually need a partner or extra hires. The table shows where each model tends to be strong.
| Skill | In-house admin | Managed services | Hybrid |
|---|---|---|---|
| Administration | Strong, with daily business context | Covered, with context that grows over time | Admin leads; partner covers absences |
| Development (Apex, Lightning Web Components) | Rarely | Developers assigned as work requires | Partner builds; admin reviews the result with users |
| Architecture | Rarely | Available for design reviews and larger changes | Partner designs, with the admin's input on process |
| Integration | Usually limited to simple connectors | Middleware, error handling and monitoring | Partner owns it; admin watches for error alerts |
| Release management | Often informal or skipped | Planned review and sandbox testing for each release | Partner tests; admin tells users what changes |
How do you run a hybrid model without confusion?
Write down who owns each type of request and give users one place to raise it. Most hybrid problems come from overlap and unclear ownership, not from missing skills.
- Make the internal admin the front door for all requests, routing work to the partner when needed.
- Agree which work the admin does alone, which the partner does, and which needs both.
- Keep one backlog both sides can see, ranked by a business owner rather than by the loudest voice.
- Send every change, from either side, through the same sandbox and deployment path.
- Maintain a single set of documentation, updated as part of each change.
- Hold a short regular review where the admin and the partner lead go through the backlog together.
What should the first 90 days of managed services include?
The first 90 days should build shared knowledge of the org, remove the most urgent risks and set a working rhythm. New features matter less than getting those foundations right.
| Period | Focus | Done when |
|---|---|---|
| First month | Access, health check, documentation review and urgent fixes | Risks are ranked and the partner can change the org safely |
| Second month | Request intake, backlog ranking and a first batch of technical debt | Users know where requests go and see them closed |
| Third month | A release review, a first enhancement delivered and a scope review | Both sides agree whether the scope fits real demand |
What questions help you choose between the two?
Answer a few questions about your own org before comparing costs. The answers usually point clearly to one model or to the hybrid.
- Which requests from recent months could our admin not complete alone?
- How many clouds, packages and integrations must someone understand to support us?
- Is a major project coming, such as adding Service Cloud or launching Agentforce?
- Who checks our admin's changes before they reach production today?
- Could we keep working if our admin were unexpectedly out for a while?
- Do we expect Salesforce to change often, or mostly to stay as it is?
