2019: The talent they couldn't find
Rich Keeler runs software engineering at Extra Space Storage. In 2019 his constraint was the one every technical leader knows by heart: the local market would not produce the senior engineers he needed, at the speed he needed them.
His words, not ours:
“We didn't have the ability to find that kind of talent locally and scale up that quickly.”
That constraint is where most nearshore stories start. The first cohort was five developers. What makes this story worth reading is what happened next, and how long it kept happening.
The shortlist where everyone was hirable
Ask Rich what stood out and he starts with the part most clients expect to be the painful part.
“One of the things that has been helpful for us is the hiring process.”
Here is what that process looks like from the client's chair. We source. We vet with senior humans, not keyword filters. The client interviews a short list and picks. Jeff Scott, SVP Technology, describes what landed on his calendar:
“They were able to do a lot of the legwork for us, to vet and find highly qualified candidates. So it was kind of like shooting fish in a barrel. You know, we had 5-6 developers, and all 5 to 6 were hirable. It was more about who you want to work with the most.”
Read that again. The decision was never “who clears the bar.” Everyone cleared the bar. The decision was “who do we most want to work with.” That is what vetting is supposed to buy you: not a stack of resumes, a choice.
Five to thirty
“We have been using SMASH at Extra Space Storage since 2019. I think we hired five developers at that point. I think we are at the point now where we have 30.”
Nobody grows an embedded team sixfold on inertia. A staffing relationship that is not working gets trimmed quietly, one seat at a time, at every renewal. This one moved in the other direction for seven years, with the client holding full information the entire way. In year one you are evaluating a vendor. By year seven the question has changed: what should we build next, and who do we add to build it.
5 → 30
Developers, first cohort to today.
It's really one team
Every staffing company claims integration. Here is what the client says after seven years of it:
“Part of the success story here is how well our teams have worked together. It's really one team.”
And the engineering view of the same seven years:
“Our experience working with SMASH has been pretty seamless. SMASH has been a strong partner and has allowed us to build software and solutions that we couldn't have done on our own because we didn't have the ability to find that kind of talent locally and scale up that quickly.”
Notice what Rich is measuring. Not savings. Software that would not otherwise exist. That is the whole argument for the model in one sentence: the point of an embedded team is not a lower invoice, it is shipping the roadmap you could not staff.
“Not outsourcing. An extension of your team.” is our line. “It's really one team” is the client's version of it, seven years in. Different location. Same team.