A Salesforce admin for your investor team: hire, freelancer or retainer?

Signs the admin gap is costing you

You don't need a full-time admin because you're on Salesforce. You need some admin time when changes start piling up. These are the signs I see most:

• Changes wait weeks. A new lead source, a new market, a new field for the acquisitions team. Nobody owns it, so it sits.
• Automations fail and nobody knows. A missed-call alert stops firing after someone edits a flow, and you find out when a seller says nobody called back.
• The dashboard and the bank account disagree. Cost per contract looks fine in Salesforce, but the money doesn't feel that way.
• Your ops lead is the admin by accident. They know the most about the CRM, so every request lands on them on top of their real job.
• Zapier is doing a lot of the heavy lifting. Every Zap is a thing that can break quietly, and the bill keeps growing.
• You're about to grow. New reps, a new market, a new dialer. Every one of those is a set of CRM changes.

If two or three of those sound familiar, the gap is already costing you deals. The question is how to cover it.

What an admin actually does in an investor org

In a home-buying company the work is mostly the same few things, every month:

For a longer list of real requests from one acquisitions team, see 50+ real Salesforce requests from an acquisitions team.

Three ways to cover it

Honest version: if you're under 10 people and nothing changes month to month, you probably don't need any of these. Fix the setup once and leave it. If you're past 40 or 50 people with several markets, a full-time admin starts to make sense, and a retainer can bridge until you find the right one.

What to put on a retainer

A retainer only works if both sides know what "covered" means. This is what I'd put in writing, whoever you hire:

1. A request queue. One place where requests go, with a status. Not WhatsApp messages to one person.
2. A monthly check of the automations. Flows, Zaps and integrations that should have fired, checked against what actually happened.
3. A monthly report. What was asked, what was done, what's next, and anything that looks wrong in the data.
4. Documentation as you go. Every change gets one line: what, why, who asked. The next admin will thank you.
5. Response times you can plan around. Something broken that stops leads gets looked at the same day. A new report can wait for the next slot.
6. Training for new hires. A short walkthrough for every new rep, so they don't end up working out of a spreadsheet.
7. No long contract. If it isn't worth it, you should be able to stop.

That's how I run Ongoing Support & Development. It's a monthly retainer with no long-term contract.

If you hire someone full time

Good. Hire for your process as much as for Salesforce skill: write the job post around how a lead moves through your business, ask scenario questions about missed calls, duplicates and cost per contract instead of certification trivia, and give your top two candidates a short paid test. A few things that save pain:

• Ask them to walk you through how they'd track a lead from a mailer number to a closed assignment. If they can't picture it, they'll learn on your org.
• Give them read-only access to a sandbox during the interview and ask what they'd fix first. You'll learn more in 20 minutes than from the CV.
• Get the org documented before the handover, not after. If the person who built it is still around, pay them for a week of write-up.
• Check that one person isn't the only system administrator. Two people with full access, always.

Hiring well takes time, and Salesforce doesn't wait. A retainer admin can keep things running, handle the handover and get the org documented, so your new hire starts with a clean desk. If your admin has already left, start with the two-week handover plan.

A job post you can copy

Most Salesforce admin job posts are a list of Salesforce features. Write yours around your business instead, and the right people will recognize themselves in it. Replace the parts in brackets.

That last question does a lot of the screening for you. People who've run a sales org answer it in terms of records, tasks and reports. People who haven't talk about the phone system.

Put a pay range in the post. Several US states and cities now require one, and it stops you interviewing people you can't afford.

Ten interview questions any owner can ask

You don't need to know Salesforce to run a good interview. Ask about your own business and listen for whether the answer is about records, rules and reports, or about vague promises. I run the Salesforce for a home-buying company in Ohio, so these are the things I'd want my own replacement to know.

Ask four or five of these in a first interview. Save the rest for the finalists, along with the test below.

A paid test for your top two candidates

Ask each finalist to sign up for a free Salesforce Developer Edition org and spend two to three paid hours on this:

1. Add a field to leads called "Last call result" with the values Answered, No answer and Wrong number.
2. When it's set to No answer, create a callback task for the lead owner due in 15 minutes, and send the owner a notification.
3. Build a report of open leads with no activity in the last 48 hours.
4. Write half a page: what they built, what they'd test before going live, and what could go wrong.

Then have them walk you through it on a call. The write-up tells you more than the build. Anyone can follow a tutorial to make a flow. The candidates worth hiring bring up the edge cases on their own: what happens after hours, what if the lead has no owner, what if the rep is out sick, how to avoid creating three callback tasks for the same lead.

Pay for the test. It's a few hundred dollars, it's fair to the candidate, and it gets you real work instead of a performance.

Last step: have each finalist spend 20 minutes with your ops lead and one acquisitions rep. Those are the people they'll work with every day, and the rep will tell you quickly whether the candidate listens.

What do Salesforce certifications tell you?

The Administrator certification tells you someone studied how Salesforce works and passed an exam. That's worth something. It doesn't tell you whether they've kept a busy org running, handled a broken integration at 8 a.m. or said no to an owner. I hold the Administrator and Platform App Builder certifications myself, and I'd still rather hire someone who can walk me through a real org they've run than someone with more badges.

Treat certifications as a tie-breaker, and the scenario questions and the test as the real interview.

What does a Salesforce admin cost in 2026?

Salesforce Ben pulled together three US salary sources in August 2026. All figures are base salary in US dollars.

Add benefits, payroll taxes, equipment and the weeks it takes to hire, and you have the real cost. For many 10 to 50 person investor teams, that number is the reason they use a part-time admin or a retainer instead, at least until the workload proves itself.

Where the person is based matters less than two things: how many of your working hours they overlap with, and whether they've seen a home-buying pipeline before. I work from Cairo during US business hours, so I'm not neutral on the first point. The second is the one I'd weigh more.

Red flags in candidates

• Wants to rebuild everything in the first month.
• Has never used a sandbox, or thinks testing in production is fine "for small changes".
• Can't explain a past change without jargon.
• No habit of writing down what they changed.
• Answers every scenario with "we'd buy an app for that".
• Talks about Salesforce features but never asks how your business works.

What should their first 30 days look like?

Agree on this before they start, so they don't spend a month building things nobody asked for.

The Deal Leak Score is a good week-one starting point, and the handover plan lists everything that can be running under the previous admin's name.

Questions

Sources

Salary figures checked in October 2026. The interview questions come from my own screening kit, written from running the Salesforce for a home-buying company in Ohio.

1. Salesforce Ben: The State of Salesforce Salaries in 2026 (Henry Martin, August 12, 2026). US data from Mason Frank, Stott and May and the Salesforce Ben survey