When I talk to CEOs who run product shops, especially dev-led companies, I often hear the same frustration. They struggle to bring in work that truly moves the needle. They end up relying on small projects that barely cover costs, never mind deliver meaningful profit.
Naturally, the conversation turns to lead generation, inbound funnels, outbound sales and positioning. Yet the focus is often misplaced. The simplest and most effective way I know to attract more and better work is this: do good work.
Why they don’t get the big projects
The reason these companies often miss out on significant opportunities is painfully simple: they don’t produce good work.
Yes, they ship. They deliver something. But what’s shipped is usually a watered-down version of what was promised, padded with excuses about constraints, and polished just enough to get it out the door. When you look past the visuals and the charm of the sales team, there’s little to celebrate.
This happens because of mis-steps during production, poor prioritisation, and a defensive culture that values output over outcome. Instead of delivering success stories that can be proudly marketed, they are left with compromises.
The imbalance inside the team
The root problem is how these teams are weighted. Too often, the COO and CTO dominate discussions, while design and business strategy are sidelined. User experience is treated as lip service, bundled with UI as a checkbox rather than a leadership function.
Business thinking is reduced to project management and billing, not to challenging the client’s model, path to profit, or market fit. Conversations get intellectualised to sound clever, but they rarely tackle the fundamentals: realistic budgets, pragmatic timelines, and whether an MVP can prove market demand before more money is sunk.
Notice that I’m not talking about frameworks, stacks, or architecture. I’m talking about products that people actually want and businesses that can actually make money.
Where it goes wrong
I’ve seen founders and corporations alike sink significant resources into projects no one wanted. Stakeholders become so convinced of their idea that dissent is silenced. When the project fails, they blame resourcing instead of asking if the product should have existed in the first place.
Meanwhile, dev shops perpetuate the churn by accepting projects with limited information, focusing on building what they can rather than what the client needs. They ignore design and business disciplines that could have made the product viable.
This isn’t just naïve. It’s unethical.
What good looks like
The companies that stand out take a different approach:
- Invest in a well-rounded team that balances design, tech, and business.
- Refuse to overpromise or hide capability gaps.
- Push for outcomes, not just output.
- Build products that clients can proudly share, that the industry talks about, and that their teams are motivated by.
Doing good work creates a ripple effect. Clients become advocates. Projects become case studies. Teams become proud ambassadors. The company culture thrives, and more opportunities follow.
I would rather go broke delivering on a project than protect my margin by putting out something half baked.
If your rallying cry is progress over perfection, ask yourself this: do you really believe you inspire anyone with that? Do you think clients with real budgets and serious ambitions want to hand over their money to a team that advertises compromise as a value?
No amount of repositioning or trend-chasing will achieve what consistent, excellent work does.
The responsibility
If clients are not coming to you, it isn’t the economy, or the market, or the latest technology shift. It’s you.
As a CEO, you have a responsibility to build a business that delivers what it promises. That means more than shipping. It means creating outcomes that clients value and products that prove themselves in the market.
Do that, and you’ll never worry about where the next big project comes from.