Subscription billing

A premium dating platform, built end-to-end and running in production.
Dear Jane came to us with a market thesis for a premium adult dating platform and a set of references — no product yet.
- Client
- Dear Jane
- Year
- 2025
- Scope
- Product · Brand · Frontend · Backend · Payments · Ops
- Role
- Engineering & product studio of record
- Team
- 3 engineers + 1 designer
- Duration
- 6 months
Context, approach, and the decisions that mattered.
The brief was not a landing page and not an MVP, but a real international service (English) that could take a first-time visitor all the way to a paid subscription and a running conversation, on its own domain, from day one. We took the whole engagement: product design, brand, frontend, backend, integrations, deploy, and post-launch operation. The first week was scope — a written product spec, the state machine for the user journey (arrive → sign up → build profile → discover → match → message → subscribe), the integration shortlist, and the trade-offs we asked the founders to make before we wrote production code. From there we ran a six-month build with weekly demos on real branches and merges to main from week two. Onboarding was designed as a funnel with metrics on every screen, not a form. Billing, entitlements, and partner payouts were built against Stripe with the same rigor we use on marketplaces. AI generation entered production, not the pitch deck: promo videos, ad creatives, dynamic banners and avatars, all running in campaigns and on-site. By launch, the client's team was operating the platform themselves through the admin and CMS we shipped, while we continued to run monitoring, updates, and paid acquisition.
- 01
One team, one contract, one delivery
Product, brand, engineering, content, video and marketing sat inside a single team. There was no design agency to hand off to, no separate copy vendor, no external shop for the AI creative work — one owner from spec to live users. That is why the deadlines held and why the details did not fall between briefs.
- 02
Real monetisation, not a fake button
Subscription is wired end-to-end: Stripe as the billing spine, entitlements enforced on the server, tier changes handled by webhooks with an idempotent replay path, and a partner payout pipeline for referrers. The full flow — landing → onboarding → paywall → paid content — was instrumented and A/B tested before we pointed acquisition at it.
- 03
AI in production, not in the deck
Promo videos, ad creatives, dynamic banners and profile-adjacent visuals were generated with AI and shipped into real campaigns and the live site. We built the pipeline that turns scripts into on-brand video and formats, and the queue that keeps the ad account fed without a manual operator.
- 04
Tools the client's team can actually operate
The admin panel manages users, content, tiers, partners and analytics. The CMS lets non-engineers edit copy and content without a deploy. Runbooks cover the incidents that statistically hit a dating platform in its first 90 days — payment failures, account abuse, subscription lifecycle edge cases — with a detection and recovery path for each.
A small spread from the engagement.
The numbers we agreed to ship against.
Handover to client team
Creative in production
Have a project that looks like this?
Send a short brief — we'll reply with concrete next steps. New engagements are limited each quarter.
