Digital projects usually go wrong before development starts, in the gap between what the business needs and what the developers think they’ve been asked to build. Closing that gap takes a partner who learns how the business makes money, which deadlines can move and who makes the decisions, before the brief turns into code.
If you run a business, you may have lived through one of these projects. It began with confidence and polished wireframes, then slowed, drifted or ended in difficult conversations three months later. The cost is more than money: lost momentum, wasted effort inside the business, and the feeling of having been here before.
This article looks at what derails projects, why technical skill is only part of the answer, and how to choose a partner who shapes a build around how your business works.
The alignment problem
Three Circles. One Truth.
The Gap
Clarity
Drag the rings to align
The work before the brief
Most briefs arrive tidy, with goals, features and timelines. What’s missing is the context that gives those goals meaning: internal politics, seasonal pressure, sales targets, a bad experience with a former supplier, an acquisition on the way, a marketing manager who already has too much to do.
If your partner doesn’t know this, the build rests on assumptions. A commercially minded partner will slow the first weeks down to learn:
- How your business makes money today
- The internal blockers that slow execution
- Where your operational costs come from
- Which deadlines can move and which can’t
- Who inside your organisation will shape decisions
Technology is rarely the problem
Businesses are often told their problems come down to tools: a new CMS, a rebuilt checkout, a different platform. Those may be right, but they’re rarely the first problem worth solving. What usually sits underneath:
- Work is prioritised without considering commercial value
- Nobody questions features that exist out of habit
- Nobody’s clear what launch needs and what can wait
- Everyone expects it perfect first time, so decisions drag
- The project is planned around deliverables rather than results
When these problems exist, the platform doesn’t matter. Shopify, WordPress, Laravel or a bespoke system can all produce a site that’s technically sound and does nothing for the business. A strong partner moves the conversation from what you want to build to which numbers it should move.
A partner who defends your priorities
Good developers build what you ask for. A good partner also defends your priorities when that’s uncomfortable.
They help you avoid the common traps:
- Too much too soon: the urge to launch everything at once, rather than a focused first version
- Hidden complexity: small requests that carry heavy running or maintenance costs
- Internal optimism: expecting sign-offs to be instant, designers to be free and content to write itself
- Misplaced confidence in quick wins: features that sound simple but need complex architecture
A commercially aware partner will challenge the brief early, map every decision to a business outcome, and stop you drifting into scope that offers little return.
Three overlapping circles
Picture three overlapping circles:
- What you want
- What the organisation can support
- What will make or save the business money
Many projects only explore the first, and the other two decide whether it works. A partner with technical and commercial sense will question all three, and make sure the overlap is big enough for a project that’s achievable, stable and profitable.
Large teams and small ones
Larger agencies bring process, depth across departments and account managers. That suits projects that need many specialists at once. The trade-off can be longer decision chains, higher minimum project sizes and team changes partway through.
Many managing directors assume they need scale, when what the project needs is focus: someone who knows the business well enough to make the daily decisions well. A smaller partner works close to the business, because they have to. They connect marketing, sales, operations and finance, because each one affects the build.
How to judge a partner before you sign anything
The questions they ask tell you most of what you need to know.
Look for someone who wants to understand:
- How you make money, as well as the requirements
- The cost of time for your internal team
- The commercial risk of not launching on time
- The three things that slow your staff down most
- Where previous projects broke and why
Be wary of anyone more excited about tools, frameworks or animations than about your numbers. A technical partner who thinks commercially talks about conversion, support costs, how fast content gets published, and a calmer marketing team.
What changes with the right partner
Things get clear early. Decisions get easier, the scope gets smaller and the stakeholders agree. The mood moves from hoping it works to knowing it’s under control.
The right partner keeps things simple. They turn a business problem into a clear technical plan, speak honestly about cost and value, and build what matters first.
Working with me
I build on Shopify, WordPress and Laravel, and write bespoke software where none of them fits.
Further reading
If you’re choosing a platform for your next project, these go further:
- When to rebuild vs refactor your website: how to tell when refactoring has become denial
- Choosing the right technical partner: a companion piece on finding the right fit
- Shopify theme performance and Liquid optimisation: what makes a Shopify store fast and easy to maintain
- WordPress caching strategies: building WordPress sites that hold up under traffic
- Advanced Eloquent relationships in Laravel: for teams building data-heavy applications
Published , updated .
Part 3 of The Long Game.