Hacker News new | ask | show | jobs
by tresni 1236 days ago
The problem is that it's very chicken and egg. You want to build enough flexibility into the system to support the next step you are looking to take while not introducing so much complexity that you end up not doing the things that deliver value to the customer.

That said, I've been in the situation where there were 50+ "billing plans" and who knows how many custom plans in order to support some lighthouse customers... It was not a fun experience and the move to an entitlements system was painful. If you start from the idea of entitlements/feature flags/etc separate from the billing logic, you can save yourself a ton of heartache later.

1 comments

That is exactly my experience, but we stopped it before it became a problem. We only had 5 plans and we didn't do too many "custom plans" until we had the system in place.

Once it was in place, we moved everyone into normal, supported situations.