At exit, we are the best in the world at two things. A lead generating machine that fills our buildings, and operations that run like SpaceX. I already own the first. The second is not an operations philosophy, and it is not an operations problem. It is a software problem, and I have already started solving it.
Building got cheap
AI is the reason. A small team now builds tools that used to take a department and a year. We build them 100 percent to our use cases, not the generic version every competitor can buy. Off the shelf and outside agencies get you 80 percent of the way and no further. They are never embedded enough to know what we actually need, and they will not push past the brief, because keeping us as a client is the job, not chasing our edge. The question is no longer buy or do without. We build, we own the last 20 percent, and we build cheap.
One demand engine and one build engine
Lead generating machine
The demand engine I run today. It fills buildings on a predictable timeline, not a sign in the window and a wait.
Operations like SpaceX
A stack of build problems. These are just what Joseph asked for recently. There is much more I am already building and can build.
One small build capability the whole company can call. I stay anchored in growth. The build reaches everywhere else as a shared service.
What the demand engine actually does
Most operators run three to five of these. We run all eight, and we built them.
Per-building local SEO
Every building ranks where its tenants actually search, not buried under a corporate domain.
AI search optimization
We surface inside AI Overviews, where a growing share of those searches now end up.
Tenant-voice content
Built from what tenants actually say, refreshed on its own, not guessed at once a year.
Signal monitoring
47 sources watched for the moment a business needs space. A move, an expansion, a lease running out.
Outbound prospecting
We reach those businesses first, by name, before they ever run the search.
AI inbound response
Every inbound answered in seconds, because speed to lead decides whether the tour happens.
Lifecycle automation
Tour, follow up, waitlist. Every stage runs itself.
On-site leasing tooling
The close captured and instrumented at the building, not lost on a clipboard.
Every lead flows into one system that scores it and routes it to the right closer in real time. That is the part off-the-shelf cannot sell you.
This is not a slide. It is in production.
Real software, used every day, on real infrastructure. Hagen has supported the backbone. I have been trailblazing the build. We did this on the side of our desks. Picture it done with intent. Everything below is gated behind our SSO, so these are screenshots, each linked to the live tool.
Screenshot slot. Drop the image in /public and set imageSrc. The card links out to the live tool.
Screenshot slot. Drop the image in /public and set imageSrc. The card links out to the live tool.
Screenshot slot. Drop the image in /public and set imageSrc. The card links out to the live tool.
Screenshot slot. Drop the image in /public and set imageSrc. The card links out to the live tool.
Screenshot slot. Drop the image in /public and set imageSrc. The card links out to the live tool.
Data Backbone + Sync
HubSpot, Aircall, Stripe, and Rent Manager flowing into one Supabase source of truth, hourly.
When building gets cheap, judgment gets scarce
The scarce thing stops being the build. It becomes knowing what to build, why, and how far to push. That takes one person holding the whole picture at once. The real estate, the people we sell to, our internal stakeholders and what each of them actually needs, and the data underneath all of it. I hold that in context when I decide what to build. Engineers do not have it. Most people who have it cannot build, or will not push.
I push into our own intuitions and explore the data for edges, because that is my natural inclination, not a job description. The acquisitions tool I am building is that instinct in action. Nobody handed me a spec. I am building it to chase a hunch through the data. Off-the-shelf gives every operator the same 80 percent. Curious, custom building is how we find the 20 percent nobody else has.
The time argument still holds underneath all of it. Even if I were not the best person, I am better than the best person starting today, because any hire spends a year learning what I already carry. The bottleneck in the AI era is the person who can translate need into build and has the drive to push past the obvious. That is the seat I already sit in.
Marketing does not skip a beat. The team is built for it.
This only works if the day-to-day keeps running without me in the weeds. It will, because every hire moves the person above them up a level.
Marketing Ops Manager
Takes the operational load I carry myself today. The execution and coordination I shovel comes off my plate entirely.
Growth, under Zak
Zak gets someone to share the load, so every channel gets the attention it deserves and the team can move faster.
RevOps support, under Hagen
Hagen comes off hands on keyboard for routine data and ops work. He moves up to architecting the systems.
Every layer rises a rung. The new hires execute, Zak and Hagen lead, and I am freed to build. This is how they grow, not just how I get my time back.
The window is now
From August to January there is little active lease-up. It is a reset, not a lead-up, and that quiet stretch is when we finish onboarding the bench and stand up the build at almost no cost to momentum.
By then Charlotte, Alexandria, Fort Lauderdale, and Bladensburg are full or all but full, with Phoenix and Denver close behind. Only Norcross launches in January, while Plano and Park Hill push toward the finish line. That is the quiet stretch.
A small, reversible bet
What I am not asking for
- To become a tech company. We are not one, and pretending is how good operators waste money.
- To leave revenue. I stay anchored in growth, where the value is.
- A giant team to manage. One or two strong engineers, not an org chart.
What I am asking for
- One or two strong engineers. The hungry, mid-career builder who wants to ship, under me and Hagen, on the stack we already run.
- A real budget for tokens and tooling, plus consultants and agencies where they earn their keep.
- The mandate to be the build engine for both pillars.
How it rolls out
Prototyping
What I am already doing, on the side of my desk, with no engineering team. The tools on this page are the proof.
The mandate to build
A clear mandate so the company knows this is mine to run, plus the first strong engineer. Support, not permission battles.
Earned function by function. Acquisitions is already a natural fit and working well. Operations is next, with Joseph. Finance and construction follow once the portfolio of wins makes the case for itself.
Where partners fit
This does not replace Outcome Labs. I own the function internally as the executive accountable for it, and I can leverage Outcome Labs or any other partner as a vendor underneath that.
My title does not need to change today. As the build proves out, phase by phase, the title can catch up to what I am already doing. This is a growth and strategy seat, not a CTO chair. Right now I am asking for one or two builders and a mandate, so the thing you said we need to be at exit, we actually start becoming.