Why Experience Matters More Than Project Size

A bigger project number on a pitch deck reads as more institutional, more credible, somehow safer. It usually isn't. Scale adds stakeholders, longer timelines, more regulatory exposure, and more coordination points where something can go wrong — complexity tends to grow faster than whatever protection came with the size. What actually predicts whether a deal performs isn't its size. It's whether the people running it have done this enough times, in enough different conditions, to know where it goes wrong before it does.

Thirty Years, Not One Big Deal

RC Thornton, who leads construction and development at Assemble Capital, is the clearest case for this. Thirty-plus years in Los Angeles residential development, more than 50 homes personally delivered, and multiple neighborhood-record sales at closing along the way — including 7123 Macapa Dr, the most expensive sale in Outpost Estates at the time it closed. None of that came from any single large project. It came from doing the same disciplined work, deal after deal, long enough to know exactly where things go wrong.

That distinction is worth sitting with. A sponsor who has closed one $50 million project has one data point. A sponsor who has closed fifty homes across three decades has fifty data points about what actually happens when a permit gets delayed, a subcontractor underperforms, or a comparable sale doesn't hold up the way underwriting assumed. Repetition, not scale, is what builds that kind of pattern recognition — and pattern recognition is what lets a team catch a problem in month three instead of discovering it in month eighteen.

Execution Risk Doesn't Care How Big the Deal Is

Smaller projects fail from poor planning. Larger ones fail just as easily when execution discipline breaks down — the cost overruns, entitlement surprises, and sequencing errors that sink a deal don't disappear because the project got bigger, and in some ways they compound faster because there are more moving parts to keep aligned. A track record across varied conditions — different cycles, different regulatory environments, different construction challenges — reveals something project size alone can't: how a team actually makes decisions when circumstances aren't cooperating. That's precisely when outcomes get decided, and it's not visible in a project's square footage.

What Experience Actually Changes: The Underwriting Itself

The clearest place experience shows up isn't in a bio. It's in what a deal is underwritten against. The acquisition criteria here explicitly rule out dependence on appreciation as a business plan: every deal is underwritten to today's closed comparable sales, not to where the market might go. A deal that only works if prices rise a certain amount by a certain date is a bet on the future. A deal that already works against today's comps, with appreciation as upside rather than a requirement, is something else entirely — and that distinction is exactly the kind of judgment call that comes from having underwritten enough deals to have watched appreciation-dependent ones fail before.

Size doesn't teach that lesson. Getting it wrong once, or watching someone else get it wrong, does.

Investing on Comps, Not on Hope

The comps discipline is really a specific case of a broader habit that experienced teams develop and inexperienced ones often skip: relying on what can be controlled — basis, leverage, execution — over what can only be predicted, like where rates or sentiment go next. A deal that needs a specific market movement to work is a prediction wearing an underwriting model. A deal that already pencils against today's numbers, with upside sitting on top rather than baked into the base case, is a different kind of bet altogether — one where being wrong about the market's next move doesn't automatically mean being wrong about the investment. That's not a size question. It's a discipline question, and discipline is exactly what repetition across market cycles teaches that a single ambitious project cannot.

Bigger Isn't Safer — It's Just Bigger

None of this is an argument against large projects on principle. It's an argument against treating size as a proxy for competence. A large deal with an inexperienced team concentrates risk; a smaller deal matched to a team's actual operational strengths tends to have fewer variables and clearer paths to execution, which is often the more conservative choice even when it looks less impressive on paper. Experience is what lets a sponsor recognize which scope actually fits their capability, rather than defaulting to whatever looks most ambitious.

Headline numbers — total project cost, unit count, projected IRR — are easy to compare and easy to be impressed by. They also don't say much about whether the team behind them has been tested by anything harder than a spreadsheet. The more useful question is how that team has actually behaved across a career's worth of deals, not how large the deal in front of you happens to be.

This article is for general informational and educational purposes only. It is not, and should not be relied upon as, investment, legal, tax, or accounting advice, and it is not a recommendation or endorsement of any strategy or investment. Consult your own financial, tax, and legal advisors before making any investment decision. See our full Risk Disclosures for additional information.