We've got a small SaaS product and I'm starting to feel like we're building a different product for every customer.

One wants custom reports. Another wants more integrations. Someone else asked for a feature that a competitor has, and now my co-founder thinks we should probably have it too.

The annoying part is none of these requests are stupid. They all make sense on their own.

But we're a small team. If we keep saying yes to everything, when do we actually get to improve the product we're supposed to be building?

How do you decide which requests to ignore? Do you wait until several customers ask for the same thing, or do you sometimes build something for one customer if they're paying enough?

Also, has anyone said no to a feature request and regretted it later? Feel like there's probably a balance here that I haven't figured out yet. Can I get some advice?

Stop calling them feature requests and start treating them as sales conversations.

Will this help you win more customers, keep the ones you have, or charge more? If the answer is no to all three, why are you building it?

Not every customer needs to be your customer forever.

This is part of why keeping your product focused matters. There's a useful read on building an MVP and figuring out what actually needs to be built first.

15 hours ago, Noah Lindqvist said:

We've got a small SaaS product and I'm starting to feel like we're building a different product for every customer.

One wants custom reports. Another wants more integrations. Someone else asked for a feature that a competitor has, and now my co-founder thinks we should probably have it too.

The annoying part is none of these requests are stupid. They all make sense on their own.

But we're a small team. If we keep saying yes to everything, when do we actually get to improve the product we're supposed to be building?

How do you decide which requests to ignore? Do you wait until several customers ask for the same thing, or do you sometimes build something for one customer if they're paying enough?

Also, has anyone said no to a feature request and regretted it later? Feel like there's probably a balance here that I haven't figured out yet. Can I get some advice?

Okay but what if you're still early and only have like 5 customers? 😂

Feels a bit risky to ignore requests when you don't have enough users to know what's actually important yet.