Kindred's next move isn't more homes. It's more trips.
The setup
Kindred has built the hard part: a trusted, verified network where everyone hosts their own home, so everyone has skin in the game. That trust layer is the moat — it's why this isn't Airbnb, and it's why the supply is worth something a stranger can't replicate.
But most of the story around home-swapping is aspirational and infrequent: the month in Lisbon, the two-week swap to Barcelona. Beautiful, and rare. Twice a year, if that.
The overlooked angle: the same trust network that powers a once-a-year international trip could power a once-a-month regional one — and frequency is where the business actually compounds.
The real constraint isn't awareness. It's local liquidity.
The thing standing between Kindred and frequency isn't that people haven't heard of it. It's that in any given market, the pool is often too thin to get matched. You can see it in the reviews: travelers requesting multiple stays in a major city and getting zero acceptances — not because the homes aren't there, but because supply and demand aren't dense in the same place at the same time.
That's a cold-start density problem, and it's the single most important variable for any exchange network. You don't solve it network-wide. You solve it one dense node at a time — the way every marketplace that ever worked did it.
The hypothesis
Reposition the use case — not the brand — from "aspirational international travel" to "a network you use close to home, often, and internationally as the step beyond."
Three rungs on the ladder:
Regional (lead here). NYC member leaves for a weekend upstate — which frees their apartment — while the upstate member comes into the city. Genuinely bidirectional supply. This is the strongest wedge because the supply and demand occasions are naturally matched.
Intra-city (harder, test second). "Skip the hour drive home — stay near the thing." Real demand, but a thinner supply story, because the member staying local hasn't freed up their own home. Worth testing precisely because it's non-obvious whether it works.
International (the existing story). Already the hero use case. Leave it as the horizon, not the entry point.
Why this grows the business, in their terms: frequency isn't just "more transactions." The Passport pays off at roughly two-plus trips a year, so driving trip frequency is how you convert an occasional user into recurring, higher-margin subscription revenue. More rungs on the ladder = more reasons to travel = more Passport conversions.
The positioning shift
Not a rebrand. A sharpening. Access over ownership. Community over commodity. A network of like-minded people you exchange with — starting with where you live, not just where you dream of going.
This isn't a leap for Kindred; it's an acceleration of something they're already leaning into (identity-based Circles are the early signal). The pitch lands better as "here's how to pour fuel on a direction you've already chosen" than "here's a repositioning."
The experiment
A localized, occasion-anchored densification test in one market — NYC — built to spike both sides of the marketplace in one geo, in one time window.
Pick the occasion. Identify a near-term NYC event/moment where people either (a) want to stay nearby (intra-city) or (b) want to escape it (regional). The event is the wedge that concentrates intent.
Top of funnel — creative that stops the scroll. Lead with performance-social: UGC on TikTok and Reels (real members, real homes that speak directly to the event), plus static and motion units for paid social feeds. Cut the creative to both sides of the market — traveler angle and host angle — so a single occasion campaign is recruiting supply and demand at once. Start with organic posts. Take the top-performing organic posts and turn them into paid-social ads.
Two-sided funnel — not just demand. This is the part most campaigns get wrong. A traveler-only funnel spikes demand and can make liquidity worse.
Demand track: event landing page for travelers — regional ("get out of the city, go upstate") and intra-city ("skip the drive, stay close").
Supply track: event landing page for hosts in the target geo — "your place is empty that weekend anyway; turn it into a trip." Recruit supply in the same nodes, at the same time.
Email flows tailored to each track and each rung, moving people from interest → listing (supply) or interest → first booking (demand).
What we're actually measuring — CAC is the headline, but it's not the point. The point is whether we can manufacture local density:
Up Next
The move I'd make: run this in NYC, read the match rate, and let the data decide whether it’s repeatable.
