Founder Notes · Published June 9, 2026
After We Learned to Say No
Declining the wrong work looks like a loss now and returns time to what matters later.
In year one we accepted everything. In year two we hesitated. In year three we said no for the first time. It was nerve-racking, and the following six months were the calmest the company had ever been.
Three kinds of projects we decline
Budget below half the cost. Not because it is small, but because such projects rarely fund acceptance or promotion either.
Build-first, sign-later. Verbal promises carry no weight the moment opinions diverge.
Work beyond the team's current ability. Taking it simply transfers delivery risk to the client.
What happened next
We spent the freed time improving existing clients' systems, and renewal went from sixty to ninety percent the following year.
The team stopped switching context constantly, spent longer on each project, and rework dropped noticeably.
Saying no is not rejecting clients. It is rejecting a way of working that would leave everyone unhappy.
← Previous post
Choosing Software After the SaaS Spring
Next post →
Making Code Review Work in a Small Team
Want to apply these ideas to your project?
We are happy to go deeper into implementation details, or to discuss the specific questions you are facing.
Start a conversation →