The fastest path to proving the retention loop is two high-recurrence, low-ticket services in a single dense cluster. This page is the plan: the verticals, why they're first, how we sequence the rest, and what's in (and out of) the MVP.
Both are high-recurrence, low-ticket (HRLT) services — ~₡30,000 (≈$60) a visit, repeating every week or two. We deliberately ignore the high-ticket one-off jobs at launch: they pay more per job but teach us nothing about the loop that makes this a platform rather than a directory. HRLT gives us frequent, forgiving, observable transactions to learn from fast.
Recurrence is the whole thesis. A roof replacement is a once-a-decade lead; a lawn is a relationship. Frequent jobs mean we see the retention loop work (or fail) in weeks, not years — and the low ticket means a bad early experience costs a customer ₡30,000, not ₡3 million.
Both are exterior — the customer rarely needs to be home, which removes the hardest scheduling friction. Both have a clear, repeatable scope that's easy to estimate from photos. And both reward route density: a gardener or detailer wants stops clustered, not scattered.
Two concrete walk-throughs — one per vertical — from first request to a standing schedule.
✓ Happy path
✓ Happy path
We launch in a single tight cluster and saturate it before expanding. Density does three things at once: it makes a pro's route efficient (the difference between a viable wage and a waste of a morning), it creates visible word-of-mouth on the same streets, and it lets a handful of vetted pros cover all the demand we can generate.
🇨🇷 Lindora Village (Lindora / Santa Ana, Costa Rica) — a specific affluent, dense condo, the pilot building.
Next: a single Kelowna neighbourhood (the current demo market), same playbook.
The wedge: a building's resident base is an instant pre-clustered roster.
Which market is first is still an open call — and it changes the payments stack. See Decisions.
Goal: enough recurring customers on enough adjacent streets that a pro can build a full route without leaving the zone. Only once a cluster is dense and self-sustaining do we open the next one — same playbook, copy-pasted.
Services sort into three tiers by recurrence and ticket size. We start where recurrence is highest, then layer in medium-recurrence work to the same customers, and only later chase the high-ticket one-offs — by then we own the home relationship and can win those jobs without paying for the lead.
Gardening · car wash. Later: veggie/produce delivery, grill & BBQ cleaning. Frequent, forgiving, route-dense — the jobs that teach us the loop.
Fumigation · gutter cleaning · window cleaning · light plumbing. We already have the home and the trust — these become reminders on the home profile, not new customer acquisition.
A/C maintenance · appliance repair · hydro-washing · landscaping · small remodels. The high-margin jobs — captured through a home we already serve, so we don't compete on lead-gen for them.
The trust rule holds across every vertical — no completed, paid job → no fee — but gardening and car wash have their own failure modes. How we handle the common ones:
| What goes wrong | How we handle it | Platform |
|---|---|---|
| Pro no-shows for a scheduled visit | Customer flags / system detects no completion. We re-route to a backup pro in the same cluster; reputation hit on the no-show. | Nothing |
| Locked gate / no water or power (back garden, mobile wash) | Pro does what's accessible or reschedules; the blocker is saved to the home record so it never repeats. No charge if not done. | Nothing |
| Scope bigger than expected (overgrown lot, heavily soiled car) | Pro requests a revised amount before starting; the customer approves in-app, or it stays at the estimate. | Fee on agreed |
| Quality dispute (patchy mow, missed spots) | Satisfaction guarantee, funded by the customer fee: a free re-do by the same pro, or a refund. The pattern is tracked against the pro. | Reversed |
| "Just pay me cash next time" — leakage (the #1 risk here) | Set-and-forget scheduling, payment protection, and the pro's booked-revenue dashboard make in-app the easy path. Off-platform = no auto-rebook, no protection, no reputation. | Nothing |
| Customer skips a visit (vacation, rain, already mowed) | One tap — "skip this visit" — in My Home; no charge; the cadence resumes next cycle. | Nothing |
| Seasonal pause (winter — no mowing) | The plan auto-pauses; we nudge both sides to resume in spring so the relationship survives the gap. | Paused |
A proposed line for the first release. Everything "in" supports running the two verticals in one cluster end-to-end; everything "out" waits until the loop is proven. This is a starting point for the partner discussion, not a locked spec.