ResourcesWhite paper
Who looks afterSalesforce once it is live
The build gets the budget, the board's attention and a launch date. What comes after decides whether it was worth it. This paper weighs the four ways organizations look after Salesforce, when each makes sense, and how to run whichever you choose so the system keeps up with the work.
In short
- A live system is an operating capability, not a finished project. Budget and staff it like one.
- Ownership always stays inside. The work can sit inside, outside or both.
- Judge each model on coverage, depth, continuity, key-person risk and the management time it takes.
- Choose a combination on purpose rather than inherit one.
- Whatever you choose, run it the same way: one route for requests, priorities from the business, visible time, a quarterly review.
- Keep admin access and every account in your own name.
ForAnyone who runs or relies on SalesforceTime to readAbout 25 minutesUse itAt go-live, at budget time, or when an admin resigns
- What Salesforce needs after go-live
- What happens when nobody owns it
- Four ways to look after it
- When outside support makes sense
- When it does not
- Running any model well
- The decision matrix
- The first 90 days of support
Rather talk it through?
A 30-minute conversation about your systems and what's getting in the way. You leave knowing what would help.