Roopairs founder explains how they shifted from building features in isolation to a disciplined approach: new features get settings in a central module, which forces conversations about billing and pricing. This workflow naturally connects product development to monetization.
Chapters
So I think that if you are building kind of your initial product out, your first feature, like what are you gonna build out the feature, you're gonna build the notifications that go with it and you're gonna build, you know, the permissioning that goes with it. Like any new feature has a list of extra things like that you add that are part of that build, you know what I mean? And I think that we would always just build the feature, the feature, the feature, and then we'd be like, oh shit, we gotta add notifications, we gotta add permit, like, it was just always after the fact. We didn't really have that proper like format of how to build new features from top to bottom. Um, and so one of those things is right. If it's a new feature, you also add its, the feature settings to the settings module. So I think that having a settings area of course would then encourage you to put your billing stuff in there. And then you kind of go down the rabbit hole of like, okay, well, what's, what are our packaging? What's our, what's our pricing? And that's always changing.