robinsamways.ca · Business Model
$ Two Projects Independently Invented the Same Pricing Shape
While designing a cross-project billing model meant to be shared in shape, not in runtime, an old, unbuilt idea from one project turned up describing a professional 'token bucket': buy 50 tokens for $20, spend one per claim. Structurally, that's identical to a separately-conceived idea from a second project — 'session packs' — a prepaid balance spent per use, arrived at with no connection to the first.
Neither project copied the other. Both independently converged on the same abstraction under different names, before this billing-model effort ever connected the two. It's the same shape of discovery as finding an already-converged tech stack by auditing real code instead of deciding on one from scratch — this time one level up, in the business model rather than the technology.
Project A's own idea (unbuilt, logged earlier): buy 50 tokens / $20, spend 1 per use
Project B's own idea (separately conceived): prepaid packs, spent per use
Same shape. Different names. Neither copied the other.The fix
The shared design ended up generalizing this convergence directly — a credit-pack pattern with a real consumption ledger, not just a decrementing counter, built to fit both projects' own already-independently-chosen shape rather than inventing a third abstraction neither had actually asked for.
Why this matters
A shared pattern validated by two independent teams already arriving at it is stronger evidence than a pattern designed once on a whiteboard and then imposed. This is the same 'golden path recognized after the fact, not planned top-down' story showing up a second time — in monetization design instead of technology choice — which is a signal it's a real pattern, not a coincidence.