The Startup "Fitness Stages" Lesson, Read for a Growing CRE Shop

What does a startup's "fitness stages" framework actually teach a CRE operator?

A growing CRE shop should scale its systems the way a disciplined founder scales a team: match capability to the stage you're in, and keep new tools on a "propose, never commit" leash until they've earned trust. LumberFi CEO Shreesha Ramdas frames startup growth as distinct fitness stages. The operator's version is simpler — don't hand act-on-my-behalf power to a system before your process can survive its mistakes.

Shreesha Ramdas, CEO of construction-fintech firm LumberFi, recently laid out "the 5 stages of startup growth no one talks about" — fitness stages a company grows through, contrarian hiring moves, and a broader shift in how businesses use software. The framework was written for founders. But strip away the startup packaging and it answers a question every owner-operator, leasing principal, and asset manager is already asking: as my shop grows, what do I let my systems do on their own, and what still needs a human hand on it?

This piece reads that framework for a commercial real estate (CRE) operator — the developer, owner-operator, or brokerage principal running deal flow on spreadsheets and email — and translates "fitness stages" into a staging discipline for the tools you buy.

What are the "fitness stages," and what's the CRE equivalent?

Fitness stages describe a company maturing capability before it takes on load — you don't run a marathon in week one of training. For a CRE shop, the equivalent is your operating maturity: how reliably your leasing pipeline, rent roll, and broker updates hold together as headcount and deal volume climb. Each stage changes what you can safely automate.

A rough mapping for a leasing-and-asset-management shop:

• Stage 1 — One person, everything in their head. The founder-broker knows every deal. Spreadsheets and inbox work fine. Risk: it doesn't survive a second dealmaker.
• Stage 2 — A team, one shared tracker. The leasing tracker (the spreadsheet listing spaces, prospects, and stages) becomes the source of truth. Risk: broker updates arrive by text and email and never land in it.
• Stage 3 — A portfolio, real memory. Rent rolls, lease expirations, and LOIs (letters of intent — the non-binding term sheet before a lease) span properties. You now need a system of record, not a spreadsheet.
• Stage 4 — Multiple teams, standardized process. The question shifts from "where's the data" to "who's allowed to act on it."

The lesson: don't buy Stage 4 tooling to fix a Stage 2 problem, and don't run a Stage 4 portfolio on Stage 1 habits.

Which contrarian hiring move maps onto how you buy software?

Ramdas's contrarian hiring point — hire for the stage you're entering, not the one you're leaving, and don't over-hire capability you can't yet direct — maps cleanly onto software. Buying an autonomous system your process can't supervise is the tooling version of hiring a senior operator with no one to manage them. Capability you can't direct is risk, not leverage.

The parallel is exact:

• A great hire you can't onboard or oversee creates errors faster than value.
• A powerful system that acts on your rent roll without approval does the same — at machine speed.

The fix in both cases is governance, not restraint. You bring the capability in, but you stage what it's allowed to do. Vantrow's spine phrase is propose, never commit: the system drafts the broker follow-up, flags the lease expiring in 90 days, assembles the rent-roll update — and a human approves before anything is sent or committed, with everything landing on an audit trail.

What is the "AI shift" reshaping every business — and what should CRE do about it?

The shift Ramdas points to is that software is moving from tools you operate to systems that can act. For a CRE operator, the right response is not to stay on the sidelines and not to hand over the keys. It's to adopt systems that stage actions for approval. According to a Deloitte outlook widely cited in CRE, a large majority of real estate firms expect to increase technology investment — the question is control, not adoption.

Concretely, the shift changes three artifacts every shop already keeps:

• The leasing tracker stops being a passive list and starts proposing the next follow-up.
• The broker update — the "just toured Suite 300, they want a revised LOI" note lost in a text thread — gets captured and routed into the system instead of your memory.
• The rent roll gets watched for expirations and renewal windows so nobody discovers a rolled lease after the fact.

The through-line: adopt the capability, govern the action. A system that proposes and waits is safe to grow with. A system that commits on its own is a liability you scaled.

How does "propose, never commit" work in practice for a leasing team?

In practice, the desk does the drafting and a human does the sending. The system reads your captures — voice notes, broker texts, emails — stages a proposed action (a follow-up, a tracker update, an alert), and holds it for approval. Nothing leaves or changes the record without a person clicking approve, and every step is logged.

A typical loop:

1. A broker texts an update from a tour.
2. The system parses it and drafts a tracker entry plus a suggested next step.
3. The leasing lead reviews, edits, and approves — or discards.
4. The approved action lands on the record with a timestamp and author.

This is the difference between an assistant and an autopilot. For a growing shop, it means you can add volume without adding the risk that a wrong number or a premature email goes out under your name.

What are the alternatives — full automation, or staying on spreadsheets?

The two common alternatives both fail growing shops. Staying on spreadsheets caps you at Stage 2: updates get lost and expirations get missed. Handing an autonomous system full authority skips governance entirely and puts your rent roll and outbound at machine-speed risk. The governed middle — capture freely, propose actions, approve before commit — is the only option that scales with control.

Where each fits:

• Spreadsheets + inbox: fine for a solo operator; breaks the moment a second dealmaker or a portfolio arrives.
• Autonomous agents: attractive demo, wrong tool for anything touching a lease, a client, or a number you'd have to stand behind.
• Governed systems (propose, never commit): the operator's answer — capability with a human checkpoint and an audit trail.

FAQ

FAQ

(rendered below)