CASE STUDY GROWTHMULTI-CHANNEL2019 TO PRESENT

Anatomy of a 10× Growth Engine

I joined as the first marketing hire in 2019. Revenue grew 10x and the footprint grew from 10 facilities to 38. This is the shape of the engine that did it: not channels run side by side, but systems wired to feed each other.

Role
First marketing hire, Oct 2019 to present
Channels
Paid, SEO & organic, lifecycle, PR, data
Scope
38 facilities, US & Canada
Status
In production; core systems run unattended
10×
Revenue growth across the tenure
1038
Facilities, each its own local market to fill
149K
Organic sessions a year after the full site rebrand (GA4)

The Problem

ReadySpaces rents flexible warehouse space. It is a physical business: real buildings, local demand, occupancy that moves every week. When I joined in October 2019 as the company’s first marketing hire, there were 10 facilities and roughly a tenth of today’s revenue. There was no marketing function to inherit. No tracking, no lifecycle program, no organic presence worth the name.

The growth plan made the problem sharper. Every new facility opens at low occupancy in a market where nobody has heard of you, and it needs demand immediately. Do that 28 more times, across two countries, and the standard playbook fails. You cannot hand-manage 38 local campaigns, 38 sets of ad copy, and 38 occupancy curves by hand. The usual answer is a big department. Ours stayed small: I started alone, then added a social media and content manager, a dev agency with two developers and a designer, and freelance videographers and photographers. A small team plus partners, with systems doing the scaling.

The Engine

The engine was built in a deliberate order, and the order is the whole story. Paid ran as a channel from early on, but the systems were built warehouse-first, and the sequence took two years to perfect.

The data layer came first. I built a PostgreSQL warehouse that reconciles occupancy, leads, revenue, and spend nightly. It has no users and no UI, and it is the most important thing on this page, because everything that came after needed data it could trust. It turned every later idea from a proposal into a query.

The ad budget algorithm came next. The Google Ads budget engine reads the warehouse and reallocates spend nightly toward facilities with room to sell. Occupancy moves; budgets follow the next morning; nobody attends a meeting about it.

Then the ad asset builder. Each market’s ad copy regenerates from live pricing, unit sizes, and availability, so 38 sets of creative stay current without anyone rewriting them.

SEO and organic compounded underneath. A full site rebrand, treated as a content and architecture rebuild rather than a coat of paint, grew organic through the migration rather than losing it, and the system built on that foundation now runs around 149,000 organic sessions a year (GA4). Paid taught us which pages and queries mattered; organic made them free.

Lifecycle closed the loop. Email cadences read from the warehouse, so a lead nurture knows whether the facility it is selling actually has space.

Channels do not compound. Channels connected through one trustworthy data layer compound.

What Compounded

Seven years in, the engine mostly runs without me. Budgets rebalance nightly. Ad copy regenerates from live pricing and inventory. Lifecycle programs adjust to occupancy on their own. Reporting is a query, not a project.

That freed the human hours for work that only a person can do. I personally pitched and landed TechCrunch, RENX, GlobeSt, CRE Daily, and Bisnow; an agency handled the earliest placements, the LA Times and The Real Deal, while I learned the craft. And in 2025 the engine got its biggest test: launching WareCRE, a new marketplace brand, on top of the same warehouse, the same organic muscle, and the same distribution. A launch that would once have taken a department took a system.

The revenue line reads 10× across the tenure. The truer summary is that the second half of that growth cost far less effort than the first, because by then the engine was doing the pushing.

01

Build the warehouse first, because everything else needs trustworthy data. The real order was data layer, then budget algorithm, then ad asset builder, and it took two years to perfect. Paid ran as a channel throughout, but automating budgets or creative on top of data you cannot trust just automates mistakes. Every system that scaled was built warehouse-first.

02

A rebrand is an SEO project wearing a design brief. The rebrand grew organic instead of losing it because I treated it as an information architecture and content rebuild first and a visual refresh second. Sites that only change their look keep their old traffic. Ours changed what it was about, and the system built on that foundation now runs around 149,000 organic sessions a year.

03

Keep the team small by making the systems large. Thirty-eight local markets cannot be hand-managed by a tiny team, so the only real decision was which jobs to automate first. Budgets, ad copy, lifecycle triggers, and reporting all run unattended now. Headcount went to the work only a person can do.

Code samples are simplified from production systems. Performance figures are queried from the warehouse or indexed to protect confidential data; demo inputs are illustrative.

WareCRE: Launching a Marketplace from Zero →

The newest system built on the engine: a B2B industrial real estate marketplace, named, branded, and launched in April 2025.