Three levels, one system
What an operator can do at each level — and the exact machinery behind it. Level one gets you funded and gets you a door. Level two fills the calendar of the door you got. Level three makes the demand yours instead of the platforms'.
What you can do at each level
Every level ships with every GoHighLevel capability switched on — CRM, calendars, funnels, email, SMS, automations, AI, reputation. Nothing is throttled and doors are never counted. What changes is what's already built inside for you.
- Two audiences tracked separately: landlords and investors
- Every property and every potential funder in one place, with the numbers you actually need to decide
- Capture pages and vetting forms so you stop chasing people by text message
- Follow-up that runs on its own until you get a yes or a no
- The full guest journey, from first inquiry to the review
- Pre-arrival, in-stay and post-stay sequences that go out whether or not you remember
- A review engine that turns finished stays into ratings
- A monthly owner report that keeps your landlord calm and re-signing
- Direct-booking demand: your own channel, your own offers, your own list
- Repeat and win-back campaigns built on stay history, not guesswork
- Corporate and group accounts — recruiters, insurance housing, travel nurses, crews, teams
- Attribution: which campaign produced which booking, and what it cost
The one-line version. Level one produces a funded door. Level two produces booked nights. Level three produces a guest list you own — and the second booking is the cheapest one you will ever make.
Seven stages, three audiences
A short-term rental business has three outputs: investors (the money), landlords (the doors) and guests (the revenue). Each one moves through the same seven stages. Pipelines, contact fields, tags, forms, funnels and automations exist to move a person one stage to the right — that is the only job any of them has. Twenty-one cells; the level you're on decides how many are already built for you.
| 1 · Awareness | 2 · Discovery | 3 · Evaluation | 4 · Commitment | 5 · Delivery | 6 · Follow-through | 7 · Advocacy | |
|---|---|---|---|---|---|---|---|
| Investors | L1Capital list building | L1Deal one-pager request | L1Vetting & check size | L1Commitment tracked | L2Deal updates | L2Returns reporting | L3Re-invest & intros |
| Landlords | L1Owner outreach | L1Property intake | L1Walkthrough & numbers | L1LOI / lease signed | L2Onboarding & performance | L2Monthly owner report | L3Referred doors |
| Guests | L3Owned-channel demand | L2Inquiry captured | L2Questions & quote | L2Booking | L2The stay | L2Thank-you & review | L3Repeat, corporate, referral |
Read the rows, not the columns. A beginner has no guests yet — their whole world is the top two rows, stages one to four. That is why level one contains no guest machinery at all: it would be dead weight. The moment a door is signed, the guest row switches on. Level three is the two ends of the board — owning the demand that starts a stay, and harvesting the stay into the next one.
What is actually built, level by level
Named assets, as of this document. live is built and verified in the master accounts; building is scoped and in progress this week.
Level one — Fund Your First
| Component | What ships | State |
|---|---|---|
| Pipelines | Landlord Acquisition (7 stages) · Investor / Capital (7 stages) | live |
| Contact records | 23 landlord/investor fields — property address, unit type, doors, rent ask, LOI status, owner motivation, investor check size, accreditation, target return, source | live |
| Segmentation | 12 tags — audience, stage and status markers for both audiences | live |
| Calendar | Property walkthrough · Capital call (owner and investor appointments, not guest check-ins) | live |
| Forms | Property submission · Investor interest & vetting | live |
| Funnel | Doorway capture — a landlord page and an investor page you can send traffic to on day one | building |
| Automations | Landlord intake · Landlord follow-up sequence · LOI nudge · Investor intake & vetting · Investor nurture · Commitment follow-through | live |
Level two — Fill Your Nights (adds)
| Component | What ships | State |
|---|---|---|
| Pipeline | Guest Journey — the seven guest stages | live |
| Automations (13) | Inquiry intake · Booking mirror · Pre-arrival ops · In-stay care · Registration form · Post-stay thank-you · Review flywheel · Monthly owner report · Returning-guest invite · Anniversary offer · Win-back · Direct-inquiry fast reply · Party guest check-in | live |
| Forms | Direct inquiry · Guest registration · Party guest check-in | live |
| Calendar | Owner call | live |
| Email library | 10 written guest emails covering inquiry, pre-arrival, in-stay, thank-you, review request and win-back | live |
| Contact records | +51 guest and stay fields · +53 tags · 27 account values (property, rates, house rules, links) | live |
Level three — Book Them Twice (adds)
| Component | What ships | State |
|---|---|---|
| Pipelines | Direct Demand Engine (awareness → repeat/advocacy) · Corporate & Group Accounts (awareness → proposal/RFP → contract → renewal) | live |
| Contact records | 22 marketing and lifetime-value fields — source, campaign, ad id, offer segment, stays to date, lifetime nights, lifetime revenue, repeat flag, review left and rating, referral source, referrals given, corporate account, role, rooms needed, contract value, direct-booking opt-in | live |
| Segmentation | 10 marketing tags — channel, campaign and lifecycle markers | live |
| Funnels | Direct-booking offer page · Guest-list opt-in · Corporate housing enquiry | building |
| Automations | Owned-channel lead capture · Offer campaign engine · Repeat-stay invitation on stay history · Win-back by season · Referral request · Corporate RFP intake and proposal follow-up · Attribution roll-up | live |
How the three kits are maintained
One build account per layer, not per tier. Each layer is edited in exactly one place and stacks additively, so a customer can start at any level, upgrade to any level, and keep everything they customised — an upgrade only adds what was missing.
| Rule | Why |
|---|---|
| Edit only in the layer account | A fix made in an assembly or a client account is lost at the next release |
| Layers are additive — never delete or rename | Guarantees an upgrade cannot damage a customer's existing setup; retire an asset by unpublishing it |
| One layer version per release | Keeps it obvious which layer version a client is carrying |
| Record layers on the account | Each client stores which layers they hold, so the upgrade delta is never guessed |
| Upgrade = load the delta snapshot | Adds what's missing; a push-update would overwrite their customisations |
Counts as built
Read live from the master accounts on 16 Sep 2026. Customers should never be sold on these numbers — they are the maintenance surface, not the benefit.
| Component | Level 1 | Level 2 | Level 3 |
|---|---|---|---|
| Automations | 6 | 13 | 20 |
| Pipelines | 2 | 3 | 5 |
| Contact fields | 23 | 74 | 96 |
| Tags | 12 | 65 | 75 |
| Forms | 2 | 3 | 3 |
| Email templates | 0 | 10 | 10 |
| Calendars | 2 | 2 | 2 |
| Funnels | 0 (1 building) | 0 | 0 (3 building) |
Level counts are cumulative: level two includes level one, level three includes both. Pipeline counts exclude the default marketing pipeline every account is created with.