Inside Mewayz · Decisions

Was wir
said no to.

M
The Mewayz team
On the modules we won't build
March 28, 2026 · 6 min read

It's easy to describe a product by its roadmap — the things it's going to build. We think you learn more about a platform from its refusals. Saying yes is the default in software; every customer request, every competitor feature, every shiny idea pulls toward yes. The character of a product is mostly in the no's. So here, plainly, are some things we've said no to, and the principle behind each one.

No to charging for the exit.

We said no to gating the API, no to charging for exports, no to making cancellation a phone call. Every one of those would make money, and every one is a bet against our own product — a wager that we can retain you through friction instead of merit. We'd rather be forced to earn the next month. The exit stays free, on every plan, forever. That's a no we'll never revisit.

You can read a company's confidence in its product by how hard it makes leaving. We made leaving easy on purpose.

No to per-seat pricing.

We said no to the most lucrative pricing model in B2B software because it taxes the thing we most want our customers to do: grow and hire. Per-seat would improve our numbers and quietly punish our customers for adding people. The flat fee costs us net-dollar-retention we watch with a wince every quarter — and we keep saying no, because a customer rationing logins is a customer we've failed.

No to modules we can't do justice.

We get asked for deep, specialized capabilities — full-blown EHR, complex multi-entity tax consolidation, heavy industrial MRP. We say no to most of them, not because we couldn't ship something, but because we couldn't ship something good enough to deserve being someone's system of record for that job. A mediocre module that pretends to be sufficient is worse than an honest gap and a clean API to a specialist.

the no's
Where a platform's real character lives

No to dark patterns, even small ones.

No to pre-checked upsell boxes, no to the fake-urgency countdown, no to the “are you sure?” guilt screen engineered to make cancellation feel like a moral failing, no to silent price increases buried in a renewal. Each of these is a tiny, proven revenue lever. Each is also a small lie, and small lies compound into the thing customers can smell even when they can't name it. We said no to the whole category.

Why the no's matter
Every refusal above costs us money in the short run — that's what makes them real. A principle you only hold when it's free isn't a principle; it's a preference. The no's that cost something are the ones worth telling you about, because they're the ones you can actually rely on us to keep.

We'll keep shipping modules — that's the yes. But we wanted the no's on the record too, because they're the load-bearing part of who we are. A platform that will build anything and charge any way it can isn't a platform with character. It's a platform with a sales target. We'd rather be known for what we refused.

— Das Mewayz-Team
March 28, 2026 · 6 min read · From mewayz.com/blog
Diesen Essay teilen

Built on
Prinzipien.

Kostenlos starten — keine Karte erforderlich →
150+ modules — and a list of the ones we won't build