Kyndling

// The Collection · concept: what happens after the match

The Collection Concept 2026

Dating apps stop at the match. Kyndling picks up from there, turning both partners’ swiped preferences into planned, bookable dates, for couples on date 1 and couples in year 10.

The problem

The original pitch opens with one question: dating apps are cool, but what happens next? The apps end at the match; everything after (finding something both people will enjoy, booking it, timing it) is friction. Kyndling’s promise is the whole date pre-arranged, so all you worry about is what to wear.

What it does

The documented concept: each partner builds a preference profile by swiping activity cards: pastimes, dining venues, cuisines, outdoor adventures, local attractions, gift ideas. Kyndling cross-references both profiles and proposes dates you’d both enjoy, availability-aware and payable up front: transport, dinner, tickets in one go. Matched partners become each other’s flames, with a flame symbol showing how much they have in common; a relationship timeline and journal keep the history, and a “rekyndle” theme points the same machinery at established couples who’ve stopped planning dates. Phase-2 ideas on the worksheet: double dates with other Kyndling couples, venue partnerships, sponsored swipe cards.

Where it stands

Concept stage. I’ll say that plainly. What exists: full product documentation dating to 2021 (an app overview plus a phased feature worksheet), a worked revenue model (free base app, a premium couples subscription, venue listing fees), and the kyndling.app domain, secured with a holding page up. What doesn’t exist yet: code. The repo is a planning repo; the build is scoped and costed in the studio’s investor docs; those figures live in the data room, not on a marketing page.

Outcome

The strategic angle is one backend, two TAMs: Kyndling is planned to share its activity database with PlayDay, the live family day-planner, so one infrastructure investment serves families and couples. Go-to-market is UAE-first, then GCC; comparables (Paired, Lasting, Couple) are relationship-content apps, none activity-booking focused or GCC-native. Part of The Collection, at the “prove cheaply” step of build once, prove cheaply, graduate what works.

Links: kyndling.app, domain secured, holding page only.