It is easy to describe a firm by what it does. It is more revealing to describe it by what it refuses. Saying no to work has a cost, the work itself, and a benefit that is less visible: every engagement declined is attention and discipline preserved for the engagements taken. Here is the work we turn down, and the reasoning behind each.
Work where the problem is not actually software
Some businesses arrive wanting a system to fix something a system cannot fix. The real problem is an undecided process, an unresolved disagreement between departments, or an unwillingness to change how work is done. Software built on top of that does not resolve it; it encodes it, expensively, and the dissatisfaction returns wearing a new face. When we can see that the genuine blocker is a decision the business has not made, the honest move is to say so, rather than to take the engagement and deliver a system that was set up to disappoint.
Work for a business not ready to operate the system
A capable system needs an owner, a change discipline, and a habit of maintenance. A business that wants the system but not the operating commitment is buying something it cannot keep. We have written before that an implementation is the start of operation, not the end of a project. When a prospective client is clear that they want the project to end at go-live and nothing to follow, we are not the right firm, because we know how that story goes and we do not want to be the ones who wrote its first chapter.
Work where we are asked to skip the parts that make it work
Sometimes the engagement is real but the client wants to remove the things that make it succeed: no time for the audit, no budget for testing, no knowledge transfer, no stabilisation, just build the features and leave. We would rather decline that than accept it, because accepting it means signing up to deliver something we already know will fail, and being the name attached to the failure. A discount on the method is not a discount. It is a different, worse product.
Work outside what we are genuinely good at
And sometimes the work is simply not ours. It needs a platform we do not specialise in, or a domain where another firm would serve the client better. The temptation to take it anyway is real; revenue is revenue. But a firm that takes work it is not the right firm for produces a mediocre outcome and a client who should have been sent elsewhere. Naming the limit is better for everyone, including us.
Why this protects the clients we take
Turning work down is not principle for its own sake. A firm has a finite amount of attention, judgment, and senior capacity. Every engagement that was a bad fit, or was set up to fail, or was outside our strength, would have consumed that finite capacity and drawn it away from the clients we are genuinely serving. Saying no is how the clients we say yes to get a firm that is not overstretched, not distracted, and not quietly resentful of a project it should never have signed.
The position, in one line
What a firm declines is a description of what it takes seriously. We turn down work that is not really a software problem, work for businesses not ready to operate a system, work stripped of the parts that make it succeed, and work outside our strength, because doing so is what keeps us good for the work that is right.