Mirror Mirror · Free Webinar · Chapter 2

From Rental to Ownership

Your 90-day plan to stop renting your business.

Friday, May 8, 2026 · 10:00 AM MST

Brady Hugins · Witch Haven Grove LLC

Where we are in the series

Last week was the spine. Today is the whole road.

CHAPTER 1 (last week)

Unified Contact Profile. One row per person. The spine your whole stack hangs on.

CHAPTER 2 (today)

The 90-day plan to own your stack. Five layers. Three months. Not all at once.

If you missed last week: the spine is one row per person, stitched across every tool. That's the input. Today is what you build with it.

The rental trap

What you lose isn't a line item. It's iteration speed.

When the vendor's roadmap and yours diverge, you can't move. You wait. You file feature requests. You stop trying.

SQUARESPACE

Decides what your site can do.

MAILCHIMP

Decides who gets your list.

KAJABI

Decides how your course feels.

YOUR CRM

Decides what fields exist.

SCHEDULER

Decides how clients book.

Every monthly bill is also a vote you keep casting for someone else's roadmap.

What ownership unlocks

Four things you only get when the data is yours.

⚡ SPEED

Your iteration cycle becomes yours. Change the tool when you need to, not when the vendor releases it.

🔧 UTILITY

Fits your exact workflow. Not the average operator's. Yours. Every quirk a feature, not a workaround.

🛠 BUILD-YOUR-OWN

When the data is yours, every new feature is a Sunday afternoon, not a SaaS contract. Each tool compounds.

🛡 TOOL-NEUTRAL

No single point of failure. When one tool dies, you swap it. Backup reliability is the architecture, not a service.

Money matters but it's not the headline. Speed and shape are.

The five layers you're going to own

Today maps all five across 90 days.

1 · CONTACTS

UCP. One row per person.

2 · DATABASE

Where the row lives. Yours, not theirs.

3 · ENGINE

Workflows + automations. n8n, cron, Python.

4 · IDENTITY

Auth you control. Magic links over OAuth.

5 · BACKUPS + FRONT

Three locations daily. Static site. Your domain.

Five layers. Each one swappable. None of them held hostage.

The plan, at a glance

90 days. Three phases. Not all at once.

DAYS 1-30

Foundation — contacts + database. The hardest month.

DAYS 31-60

Middle — engine + identity. Wire what's already there.

DAYS 61-90

Lock — backups + front-end. The quietest month.

You don't migrate everything in week one. You sequence the layers so each month protects the last.

Days 1-30 · the foundation

Contacts and database. The hardest month.

WEEK 1: CONTACTS

UCP from chapter 1. Pick the spine (email). List your sources. Ship the stitch.

WEEKS 2-3: DATABASE

Pick the spine's home. Airtable for most operators. Your data, your fields, your schema.

WEEK 4: ONE QUERY

Build the first query you couldn't run before. Lifecycle by brand. Top customer LTV. Whatever was hiding.

WHAT YOU OWN BY DAY 30

A unified contact graph in a database you can move. A query nobody else can charge you to ask.

Roughly 20 hours of focused work over four weekends. The compound starts here.

Days 31-60 · the middle

Engine and identity. Wire what's already there.

WEEKS 5-6: ENGINE

n8n covers most automations. Cron + Python for the parts that matter. Workflows you can read in code.

WEEKS 7-8: IDENTITY

Auth you control. Magic links beat OAuth for ops surfaces. Your customers don't sign in through someone else's account.

THE PATTERN

Each automation reads from your database, writes to your database. Tools become interchangeable parts.

WHAT YOU OWN BY DAY 60

Workflows you can audit. Auth you control. The first private gated surface for paying customers.

Days 61-90 · the lock

Backups and front-end. The quietest month.

WEEKS 9-10: BACKUPS

Three locations rule. Daily encrypted snapshot to local + cloud + cold storage. Practice the restore.

WEEKS 11-12: FRONT-END

Static site. Your own domain. Everything cacheable; nothing held by a CMS rental.

THE LOCK

Now nothing is rented. Every layer can be swapped, backed up, restored. The vendor's roadmap is no longer your roadmap.

WHAT YOU OWN BY DAY 90

A stack you control end-to-end. A backup you've actually tested. A site you can move with one DNS swap.

Tool-neutral = backup-ready

When your tool dies, you don't fall.

If the data is yours and the schema is yours, the tool is just a pen. Three concrete swap paths most operators face:

Mailchimp → MailerLite

An export. An import. Your list is your list. The vendor never owned the relationship.

Airtable → Postgres

A nightly mirror you've already been writing. The cutover is reading from the new pipe instead of the old.

n8n → cron + Python

A focused rewrite of the workflows that matter. Not all of them. Just the ones tied to revenue.

The cost of switching is bounded because the data and the schema are yours.

Live demo

My stack is the proof.

Every widget you're about to see exists because the data is mine. None of these existed when I started.

// What I'll show you live (~5 min)
· 📊 Activity Feed — the last 24h across the whole stack
· 🎯 DS Funnel — today's webinar in 5 stages, real numbers
· 🔎 Customer 360 — type any email, see every brand touch
· The Airtable bases underneath each widget
· The cron jobs that keep them in sync

Switching to internal dashboard now.

What this looks like · local business

Cafe, boutique, studio. Days 1-30 in plain English.

RENTED TODAY

Loyalty card in Square, email in Mailchimp, reservations in OpenTable, booking site on Squarespace. Four bills. Four logins. Four roadmaps that aren't yours.

OWNED BY DAY 30

One Airtable base for customers + reservations. A static menu site you control. A payment processor that's a service, not a CMS. Three layers, all swappable.

The owner can change any one of those without changing the others. The regular gets a personal birthday email because the database knows their order history.

My own · multi-brand operator

8 brands. One stitched contact graph. Every brand reads from it.

WHAT IT WAS

Eight brands. Eight surfaces. Same person buying a tango ticket, a Venus reading, joining a webinar — looked like three strangers in three systems.

WHAT IT IS

Five Airtable bases. ~98 unified contacts. Six dashboard widgets. Each brand reads from the same graph; every new feature is a Sunday afternoon.

The pattern: one stitched graph; every brand's tooling reads from it; nothing rides on a single SaaS surviving.

Open the floor

Q&A

· Where in the 90 days are you stuck right now?

· Which tool decides FOR you, instead of with you?

· What's the swap path if your most expensive tool died tomorrow?

Three Paths Forward

Pick the one that fits your next 90 days.

$297 ONE-TIME

DS Course

Days 1-30 walked end-to-end. The hardest month, with a hand to hold. You finish the foundation.

$33/mo

Membership

Days 31-90 with weekly office hours. Bring your stitch script — we’ll review it live. Builder-buddy through the swap paths.

$800 APPLICATION

Custom Build

I compress 90 days to 14. Production-ready stack on your data, your tools, your domain. Application gated.

https://mirrormirror.roseinthegrove.com/consult/

"Speed isn’t a feature — it’s what you get back when nobody else’s roadmap can stop yours. In 90 days you can build the tool you actually need."

Recording lands at:

https://mirrormirror.roseinthegrove.com/ds/may-08/

Brady Hugins · Mirror Mirror · May 8, 2026