A sports foundation asked for seven features and I said no to one

Saying yes is easy. It's free on the day you say it.

You pay later. With interest.

A sports foundation wanted to move their fee collection onto PagoCRM. After a meeting, they came back with a list. Seven things they needed.

Export the season's fees to a spreadsheet. A tax-format export of those fees, because as a foundation they have to file it. PDF receipts for paid fees. Sending those receipts by email from the admin panel. Seeing player authorisations in each player's file. Letting coaches see those authorisations too.

And number three: creating clothing items, a shirt, a pair of shorts, and assigning them directly to a player.

I answered point by point. Six of them: not available today, planned for next season.

Number three: no.

A rewrite with a nice name

It wasn't a bad idea. We liked it. They weren't even the first club to ask for it.

But when our developers looked at it, they saw it wouldn't stay inside one feature. It meant changing other modules: exports, receipts, invoicing. Modules every other club relies on.

It's like asking for a new shelf and discovering you have to move the kitchen wall to fit it.

A request that looks like one feature but changes several modules isn't one feature. It's a rewrite with a nice name.

So I told them it was noted as interesting but not planned. And I didn't leave it at a bare no. I offered them a separate, simple way to sell clothing, the way other clubs already do it, at no cost to them.

Saying no to one feature is how you keep your promise on the other six.

The next day we spoke on the phone and agreed on what mattered most to them: the tax export. It would be working before January 2025, in time for them to file. The rest would arrive during the season. And since their season started on May 1st, they wouldn't get a single PagoCRM invoice before then.

Clear priorities. Clear dates. One honest no.

Every instinct said yes

Saying no to a club that's about to join is uncomfortable. Every instinct in a small agency says: say yes, figure it out later.

The trouble with "later" is that a change to invoicing doesn't only affect the club that asked for it. It affects every club that collects its fees through the platform. One club's favour becomes everyone's bug.

By saying no, I was accepting the risk that they'd walk away over one feature. I preferred that risk to the other one.

And I think the list helped. When you answer seven points one by one, a no stops sounding like "we can't be bothered". It sounds like someone actually read what you wrote.

PagoCRM is paid for by our services and by the clubs that trust it with their fees. There's no investor money to absorb a rewrite that breaks invoicing for everyone. Every hour of development has to make the product better for all clubs, not just for the one asking today.

That's the part of not having investors nobody puts on Instagram. You can't afford to say yes to everything. Which, it turns out, is a feature.

Six yeses showed them we were listening.

One no protected the product for everyone else.

P.S. The shirt can still be sold. It just doesn't get to move the kitchen wall.