How Much Does a Month of Delay Cost a Self-Storage Development?
A data center stat sent me down a rabbit hole into what a self-storage development delay really costs — modeled with two AI models, real Austin street rates, and a monthly DCF. The answer should change how developers think about time.
While my daughter was playing on the floor with a ladybug toy, I was reading an article in The Economist about data center development, when something struck me:
So, I wanted to look at self-storage projects and try to understand how a self-storage development delay impacts overall returns. And can the same claim be made in self-storage?
I fired up the TractIQ AI Connector in Claude and posed this question to Opus 4.7 and Fable 5 to compare differences in the analysis, then re-ran everything with real street rates in Austin, TX (where I'm based).
As a quick aside, my aim is not to use AI to write my posts, and to be transparent about when AI is used. It is an incredible time to be in data, technology, and self-storage, and my aim is to explore questions I wouldn't historically have been able to in 1 hour, and provide interesting takeaways for self-storage investors, developers, brokers, and operators in the process.
And with that, here are the results:
What does a self-storage development delay actually cost?
Check out the assumptions in the footnote of the chart above for this sample $10MM project, and the results are interesting…both from what it means for developers, and each AI model.
Off the bat, it looks like developers lose ~50 basis points off the IRR for every month delayed, and $65k of Net Present Value from the project.
We all know developers are motivated to expedite the permitting and construction progress, but these findings put that in stark terms.
What's also interesting is that if you take these claims at face value, it drastically increases the value of a development site that's already approved, versus one that you'd have to go through a process.
A 12-month head start on a project has a ~$780K value impact on a $10MM project. I'd be curious to hear from developers on how they think about this, and what it means for quantifying land value differences between approved and raw land sites.
Why did the two AI models disagree?
I find it interesting that Fable had starker findings than Opus 4.7. So I asked it why, and here is the response, verbatim:
Fable 5 explains the gap
- Why they differ: The models did the same math on a different deal. The prompt left one thing open — what to do with the perm loan — and Fable assumed a cash-out refi at stabilization while Opus left the equity in until sale. Fable's version has a higher return, and higher-return deals lose more IRR per month of delay. On everything the prompt pinned down, the models agreed within ~5%.
- What it means for analysts: When two models disagree, it's now for the same reason two analysts disagree: an open assumption, not bad math. The question isn't “which model is right” — it's “did I specify the deal tightly enough.”
I find this to be fascinating, that Fable took the prompt and added in a decision-point that I never specified, but could make sense for many developers depending on the terms of the construction loan.
This highlights the need to be extremely clear in your prompting, and to recognize that each new AI model continues to evolve in ways that may be unexpected.
What is a self-storage development delay worth in rents?
Now, to the second part of the overall question: how do we compare these findings to a decline in rents?
For this round, I anchored the model to real data: TractIQ's trailing-12-month average street rates across 117+ Austin facilities per unit type, blended across a typical unit mix. The deal is hypothetical but the rents are real.
Per the above analysis in Austin using Fable 5, a 1-month delay is equivalent to cutting rents 0.8% on the entire building, forever. Stretch it to 9 months, and the delay costs 91% of the project's lifetime operating expenses.
Read that again.
This finding doesn't just support the Carnegie Endowment's data-center analysis. It's arguably more striking in storage, because the storage operating budget is tiny relative to the capital at risk. In a data center, delay competes with the electricity bill. In storage, delay competes with everything.
And one more Austin-specific finding worth sitting with: at current Austin rents, the model says a project has about 15 months of slack before delay alone turns it NPV negative. In a market where entitlement fights routinely run past a year, that is not a rounding error.
Discipline is the whole game
Before TractIQ and publicly committing to exit the self-storage investment business, I developed 120,000 NRSF of self-storage across 4 projects. There are so many challenges that come with every project, which I can get into in later posts. But in this case, it demonstrates that the development yield on cost must be significantly larger than outright acquisitions.
Not only will you have higher cost of capital, stress, and risk, but it's so rare to find a hyperlocal market starved for self-storage in 2026 (although there may be a few listed in TractIQ right now).
So, if you're a developer, continue to be disciplined, and constantly confirm a project is truly worth the effort, since even a short self-storage development delay could have a huge impact on your performance.
Maybe more importantly, was this article worth the effort?
I think so, since it was fun, data and AI filled, and highlights interesting takeaways for developers.
Will I keep writing things like these?
Only time will tell. But in my case, a 1-month delay in posts shouldn't impact me too much.
The full delay model, free
- What it is: the complete monthly DCF behind this article. All eight delay scenarios side by side, the TractIQ Austin T12 rate table with editable unit-mix weights, every assumption in standard blue-input convention, and every formula auditable.
- How to get it: comment “DELAY” on the LinkedIn post for this issue, or reach out through tractiq.com, and we'll send it over. Swap in your own market's rates and the whole analysis re-runs.
