Fynn GloverCo-Founder & CEO, Schematic · Co-founder & CEO of Schematic | Runtime monetization infrastructure for SaaS & AI companies

David Bartolomucci, founder & CPO of YC-Backed Roopairs, on the importance of entitlements

14 Jan 2025 · 1 min

Watch on YouTube

1:18

In this interview, David Bartolomucci, founder and CPO of YC‑backed Roopairs, explains the company’s product strategy in the B2B software space. He contrasts two market extremes: legacy on‑premise systems that are inflexible and modern, one‑size‑fits‑all SaaS tools that are overly generic. Roopairs aims to occupy the middle ground by offering a modular platform that lets customers pick only the functionalities they need—such as billing, entitlements, permissioning, job management, invoicing, and price‑book management—rather than forcing a monolithic suite. He notes that the company’s modest $1 million funding limits its ability to build everything at once, so it focuses on building a flexible, extensible core that can be expanded over time as customers adopt additional modules. The discussion highlights the strategic importance of entitlements and permissioning as the foundation for this modularity and the challenges of scaling product development with limited capital.

Chapters

— There are so many companies in our space that are running on really old legacy software. It's limited in its workflows, limited in its capabilities, is still on-prem, and just needs a facelift. And that's kind of like what we're building. And then there's this other group of software which is very modern, but it's super general and like it's a one-size-fits-all. So you kind of have those two sides of the coin. And we think that we can kind of be the player that bridges it together. But it's going to take time because we never really raised that much money. We only raised close to $1 million. And, you know, we're not building a Chrome extension. We have— and that's why, you know, billing and entitlements and permissioning is so important for us is because we really have a system that is— that needs to become modular where you have this, you know, I want job management and I want invoicing, but I don't need purchasing, but I also want price book management. There's just a lot of different layers to it because each company has specific needs. Like they may come into the sales call, the demo with their problem being purchasing. But if we have a product where they just get everything, you know, that's not what they want. They just want a portion of the value. And then we can, you know, extend the value, additional value to them over time because it's hard for a company to just full stop and just learn 10 different modules all at once, you know.