Two-sided service marketplace in the UK, yearly memberships
Operations found in its own data, renewal notices that run themselves, a 74-partner affiliate program
Numbers read on the live marketplace, June 2026
The situation
A house-sitting marketplace with yearly memberships. Contracts to sign between the two sides, a legal duty (the UK Digital Markets, Competition and Consumers Act 2024) to notify subscribers before every yearly charge, and a partner program run by hand.
What runs on Empavision
Empavision read the marketplace’s own data and surfaced the workflows already in it, in the marketplace’s own words: video-meeting management, contract-signing status for homeowners and housesitters, membership lifecycle, affiliates, reviews, wishlists. Nobody configured them. The operator runs review handling and the video-meeting workflow through Operations in production; every change writes a receipt that can be undone.
Renewal notices: Empavision watches the Stripe subscriptions and sends the advance notice at the configured lead time, with delivery proof per email from the email provider. Two delivery paths (the Stripe upcoming-invoice event and a daily safety net) share one idempotency gate, so a notice can neither double-send nor be missed.
The affiliate program runs end to end: apply, approve, track, pay out, with per-affiliate commission rates and downloadable creatives.
Verified
- ✓58 renewals tracked: 40 upcoming, 7 in the notice window, 6 cancelling, 4 already notified.
- ✓16 renewal notices delivered, 13 opened, 8 clicked; 0 bounced, 0 failed, each with delivery proof.
- ✓74 active affiliates and 3 pending applications managed from one screen.
- ✓Workflows detected on this marketplace differ entirely from those on a resale marketplace (favorites, shipping, pickup): the scan learns each marketplace’s vocabulary.
Not claimed
Referral and commission totals are not claimed: at verification time they were 0 and £0 on this marketplace. The program’s structure and adoption are the result, not its revenue.