Aisle  ·  strategy one-pager  ·  2026-07-17

The moat isn't
the list.

A wedding directory has no defensibility — a couple finds a vendor's name, Googles it, books direct, and the platform is bypassed. The defensible business owns the couple's planning workflow and the transaction — the vendor list is just bait. Here's the model, the SA reality, and the pilot.

The 30-second problem · disintermediation

“I went onto Pink Book, got the vendor's name, searched Google, found them direct. Why would a couple stay on our site — and why would a vendor pay for a lead they'd have gotten anyway?”

This is lead leakage, and it's what kills every directory. Phone books lost to Google for the same reason. You can't stop the Google search — and gating the vendor's name just makes couples bounce off your site entirely. The fix isn't hiding the vendor. It's making the on-platform path better than going direct.

The model

Own both sides. Charge one.

Free planning tools keep the couple's whole wedding on-platform. Qualified, attributed leads plus business tools make vendors pay. The directory sits in the middle as customer acquisition — never the product.

The couple

Free · the traffic engine

  • Free wedding website (they share your URL with 150 guests)
  • Guest list + RSVP tracking
  • Budget tracker + checklist
  • All vendor chats in one inbox

Lock-in: their entire wedding lives here. Leaving = starting over.

Qualified lead →
Aisle
← Attribution + tools

The vendor

Pays · the customer

  • Real leads with intent: date, budget, style
  • Proof the booking came from you (attribution)
  • Instant-response + quote tools
  • Calendar, contract, deposit — their back office

Lock-in: you're their software, not their ad.

Anti-leakage levers, ranked

What actually stops the bypass

Evidence is blunt: gating contact is the weakest lever and vendors resent it (Thumbtack sells the same gated lead to five pros). Value beats friction — every strong lever makes leaving cost something.

Couple's whole wedding lives in your free tools
Website + guest list + budget. The real moat — build first.
Strongest
On-platform booking + deposit / payment
The Airbnb move: trust + protection, not friction. Phase 2 (Peach/PayFast).
Strongest
Qualified, attributed leads (+ instant response)
Why vendors keep paying. 81% of couples are frustrated by slow replies.
Strong
In-platform messaging + quotes
Conversation history lives here. Cheap to build, real stickiness.
Strong
Review-gating tied to verified bookings
Couples complete the booking on-platform to unlock the review vendors want.
Medium
Gating vendor contact details
Pure friction. Overdo it and couples leave. Lead quality matters far more.
Weakest

The South Africa reality

Validated model, unclaimed wedge

What's true on the groundWhat it means for you
Happly & Plan My Wedding Africa already run planning-tool-first in SAModel works locally — but you're not first. Need a sharp wedge, not "another Happly."
Pink Book (incumbent) hides pricing behind sales; no public rate cardWhole market is opaque — transparent pricing is a differentiator.
Wedding Venue Guide = R65/mo race-to-the-bottom listingsDon't compete on cheap listings. That floor is a trap.
SA lead costs: Google Ads R800–2,000, cold email R300–900, Meta R50–350 /leadYour pricing anchor. A qualified wedding lead at R150–400 undercuts Google and stays credible to small vendors.
Market $1.4B → $2.4B by 2035; payment rails: PayFast, Yoco, Ozow, PeachRoom to build; Peach handles the marketplace split-payment / deposit model for phase 2.
R150–400
Your qualified-lead target price
R800–2,000
What a vendor pays Google Ads per lead
81%
of couples frustrated by slow vendor replies — your opening

Guardrail

POPIA shapes how you use the vendor data

⚠ Electronic outreach is the risk zone

The Information Regulator's Dec 2024 guidance: email, SMS, and (per their view) phone calls for marketing need opt-in consent or an existing relationship. POPIA covers businesses too, and a first enforcement notice has already been issued. Scraping vendors and cold-emailing all of them is exactly the exposure. This shapes how you use the list — it doesn't kill it.

  • Prefer phone / a vendor's own public "contact us" form / social DM over bulk email.
  • Every message identifies the sender and carries a clear, working opt-out.
  • Maintain a do-not-contact list and honour it.
  • Frame as a B2B partnership offer, not a marketing blast.

The pilot — prove one loop

Don't boil the ocean

A directory scales breadth; a defensible business proves a loop. Get one enquiry → attributed booking working before anything else.

Build the couple wedge first

Free wedding website + guest list + budget. That's the traffic and the lock-in — not the vendor list.

Pick one category, one region

E.g. Cape Town venues or photographers. Recruit ~10 vendors from the Pink Book list (POPIA-safe outreach).

Wire the loop

Couple enquires in-platform → vendor responds in-platform → booking is attributed to Aisle.

Get one vendor to say the words

“I got a real booking from you.” That sentence is your proof of business. No amount of directory scale substitutes for it.

Then charge, then scale

Pay-per-qualified-lead (R150–400) or a light monthly. Add on-platform deposits as the phase-2 anti-leak lever.

The one-liner

Kill the word "directory."

Aisle is a couple's planning app with vendors attached, monetised by selling vendors qualified, attributed leads and the tools to run their business. The directory is bait; the moat is the couple's data and the on-platform transaction. Proving the directory-only version worthless in 30 seconds is the most useful thing that could have happened this early.

Own the couple. Own the transaction. Sell the vendor a booking — never a listing.