Consumption state across five systems

Inside Out sell nine member benefits as one membership: events, awards, training, articles, guides, recordings, perks, a job board and a forum. They ran across WooCommerce, Discourse, an events calendar, a job board and WordPress. Nowhere showed a member the whole set.

I designed single sign-on across all five, which replaced an external forum platform on the way through.

Most of the difficulty was in the seams. At every handover I had to decide what a member sees, and separately what a non-member sees on a locked item, because those are different failures. A member hitting a login wall inside their own membership raises a support ticket. A non-member hitting a dead end is a lost sale.

Then consumption state. Every card carries its own: Listen now, Watch now, then Watched with a progress dot. One stored field per member per item, cheap to design and expensive to deliver, because it has to survive all five systems to mean anything. Get it wrong in one integration and the state is not missing, it is wrong.

Without it a hub of forty items looks the same on the fortieth visit as the first, and the renewal invoice arrives with no record of what the member got.

Single sign-on shipped. There is a named founder quote and no engagement figures.