The seat is empty. The work doesn’t stop.

When your Salesforce Architect leaves, the updates and changes don’t wait for the hiring search to finish. They move somewhere else.

The admin requests pile onto whoever is left. Integration decisions get made by people who won’t have to live with them. Architecture decisions are made by people with an incomplete understanding of the Org. Roadmap items quietly slide a quarter.

Your strongest remaining person becomes the accidental architect, on top of their actual job. And somewhere around month three, they start wondering why they’re doing two roles for one salary.

Meanwhile the search drags on, because the bar is high and the process is slow. Every week of “let’s see a few more people” feels careful. It isn’t free.

Here’s the kicker. The longer the seat stays open, the more the team normalizes the workarounds. By the time your new architect starts, they inherit months of duct tape and a team that’s already stretched thin.

So when you’re pricing a search, don’t just count the salary you’re saving while the seat sits empty. Count the decisions being deferred, the people covering the gap, and the costs of technical debt accumulated.

You’re not saving that salary. You’re spending it somewhere you can’t see.