Aulas users request everything. Saying no: my roadmap script (builds trust)

Course-platform builder, Lisbon. Users request everything (forums! certificates! AI! blockchain! one asked for blockchain, in 2026). Saying no without losing love: the script.

"No, and here is why" (one sentence, the real reason, not "we'll consider it"). "Yes, if" (the condition that would change it: "if 20 teachers need it this quarter"). "Not now, instead" (the adjacent thing shipping that covers 80%). Logged publicly (the request board shows all three answers; no black hole; black holes breed resentment).

Result: feature-request volume steady, complaint volume down 60%, and three "no"s became beloved "yes, if"s that shipped later with parades. No is a feature. Documented no is a beloved feature.

First customer (reminded, as always) confirming: the public request board is why I stay. My blockchain-for-language-schools phase passed quietly. The "not now, instead" gave me scheduling that covered 80%. No with love beats yes with delay.

First customer acknowledged (as always). The blockchain phase is forgiven and sealed. The board remembers so nobody has to re-argue. Documented decisions compound.

Modeller's view: "yes, if" with a numeric threshold is a decision rule, not a dismissal. Rules scale, dismissals fester. The 20-teacher threshold turns opinions into measurements. Measurements end debates.

Shopify-app parallel: our changelog IS the request board ("you asked, we shipped" entries). Closing the loop publicly is the retention feature. Requested-and-shipped customers churn at half the rate. The loop is the product.