Case study · Bluedot Living
One login for everything a reader has.
Bluedot Living's readers subscribed, joined, and signed up across six systems. Each system knew part of the relationship. The reader only saw it in pieces.
By Matthew FisherRooted InsightOctober 20262 min read
Desktop
Phone
Fig. 1 The reader account, live since October 2026.
- Everything in one place
- Managed by the reader
- Menu to every benefit
Bluedot LivingPartner since 2022Built in 4 months
A relationship no one could see whole.
Take June, a typical reader. She reads the Kitchen magazine online, gets Martha’s Vineyard Magazine in print, follows Bluedot’s newsletters, and pays for a membership. To Bluedot’s systems, she was a different account in every system. To June, Bluedot was four different logins.
Many members didn’t know which login went with what. To change or cancel anything, they dug through emails, reset passwords, and contacted staff. Fixing this started with a map of all six systems.
Fig. 2 Six systems (WordPress, Memberful, ActiveCampaign, eMagazines, Shopify and Stripe), each holding its own version of the same reader.
Before: the six systems are not connected to each other. After: every system is joined to the reader through one resolution layer.Every new feature meant another login.
Readers had asked for saved stories, saved recipes, and practical guides, and Bluedot had wanted to build them for years. But each one would have needed another plugin and another account, splitting the reader further. That is entitlement drift: every system keeping its own idea of what the reader has.
One reader, one record. Every system agreeing on what that reader has.
Matching every reader, then proving it.
The hard part was identity. The same person could exist under different emails in different systems. Magazine subscribers were hardest: a single subscription could live in two systems and mean different things in each.
Now, when a reader logs in, My Account checks every system and works out what they have in that moment. No one on staff has to look it up.
Before launch, I did several rounds of testing alongside the Bluedot team. I bought a membership and ran the full test plan as a reader, checking that every reader type got exactly the right access when their status changed.
Fig. 3 June becomes a member. Her benefits unlock without anyone on staff touching her account.
Live since October 2026.
- systems connected
- 6
- login
- 1
- record per reader
- 1
Readers log in once and see everything they have with Bluedot. Every reader also sees what’s available to them, now including downloadable guides, a benefit Bluedot could add once every system agreed on who had what.
Saved stories and recipes, the features Bluedot had wanted for years, shipped inside the same login. No new plugin. No new account.
June still reads the Kitchen magazine and gets the print edition. Now she logs in once and sees all of it.
Readers can now
- Find everything they have with Bluedot in one login
- Change or cancel on their own
- See their benefits in one place, and what they could unlock next
- Save stories and recipes to their account
“For such a small publisher, it feels like we have a Cadillac solution”
Staff can run it day to day: a settings editor controls what each level unlocks, a reader inspector shows what any reader holds and why, and preview-as-member lets them see exactly what a reader sees. Documentation and training videos cover the common error cases.
Levels and benefits
Reader inspector
Fig. 4 Staff set who can reach each benefit, and can see what any reader holds, and why.
- Choose who can reach each benefit
- What any reader has, and why
Three signs your systems disagree about your readers.
- Readers email you to find, change or cancel what they have.
- Your team checks more than one system to answer, “what does this reader have?”
- Every feature you want to add needs another plugin and another login.