Salesforce Admin on Demand
A certified admin inside your team for a fixed number of hours a month: users, dashboards, small automations and release readiness every Salesforce cycle.
01
The problem
Why people call us about this.
A
Your accidental admin is a sales ops manager doing this in the evenings.
B
Requests sit in an inbox until the person asking gives up.
C
Seasonal releases arrive and nobody has checked what breaks.
02
What’s covered
The Salesforce we actually configure.
The same named admin every month, working your backlog. Hours are used within the month, never billed in six-minute increments, and nothing is outsourced further.
03
How it runs
Five phases, and what you see at the end of each.
01 · Week 1
Inventory
What exists, who owns it, and which system is really the source of truth. Almost always surfaces something nobody knew was live.
A written map
02 · Weeks 2–3
Contract
The design in writing, with each decision and its reversal cost named. This is where we argue with the brief — before money is spent.
A signed scope
03 · Middle
Build
Built against the contract and reviewed against it. You see working software every two weeks, in your own sandbox.
Fortnightly demos
04 · Late
Prove
Volume testing at twice expected load, deliberate failure injection, and a replay run with your team watching.
A test evidence pack
05 · Final week
Hand over
Runbook, monitoring, escalation path and a named owner on your side — then a month watching it together before we step back.
Runbook and owner
04
First call
Thirty minutes. Three answers.
You speak to a certified architect, not a sales engineer. No deck, no discovery fee, and no obligation to go further — you leave the call with three things whether you hire us or not.
Whether this is even the right line
About a third of the time it is not, and we say so. Usually the ask is custom development when the real problem sits in the data model underneath.
A shape and a range
Roughly how long, roughly how many people, and the band it falls in. The firm number follows discovery about two weeks later, and it holds.
The two risks we would flag
The things most likely to blow the timeline on a project like yours — named on the call, before anyone has signed anything.
Book it for this week.
Pick a slot directly in the calendar — most questions get answered inside the thirty minutes.
05
FAQ
Asked on nearly every call.
How many hours do we need?
Most teams settle between twenty and forty a month. We start with a health check and recommend a band, rather than selling you the largest one and hoping you do not notice.
Do unused hours roll over?
Not at this size. Rollover starts at 140 hours a month, which is managed-services territory — below that a carried-over handful of hours just moves an argument about capacity into the following month. We do not bill in six-minute increments and we do not invent work to burn a balance at month end.
Is it the same person every month?
Yes, named. If they are on leave you get a named cover who has already worked in your org, not whoever is free that week.
What is not included?
Custom development beyond small automations, integration work, and anything needing architecture design. Those move to the relevant line and are quoted separately rather than eating your hours.
Other lines