5 Things I Wish Clients Knew Before Their Project Started
Managing web and software projects is, genuinely, one of the most rewarding things you can do in a digital agency. You get to take something from a blank page to a live, working product that real people use every day. It is brilliant.
It also teaches you a lot. About technology, about process, and about human nature.
There are a handful of things I wish every client knew before we kicked off. Not because it makes our lives easier (though it does help), but because knowing these things will genuinely make your project better. Faster, smoother, and with far fewer of those "ah, we forgot to mention..." moments.
Here they are:
1. A tight brief is the best investment you will make
We love ambition. Bring us big ideas, bold visions, and high expectations. What we find harder to work with is lack of clarity.
"We want something clean and modern" is a starting point, not a brief. Without clear goals, defined users, and an honest picture of what success looks like, a project spends the first few weeks finding its feet instead of moving forward. Every clarification email, every "just to confirm" call, and every revision that could have been avoided adds time. And time has a cost.
The businesses that get the most from their investment with us are the ones that arrive prepared. You know your business and your users better than anyone. Help us understand both, and we will build something that truly works for them.
2. Your internal approval process is part of the timeline
We plan everything. Design sprints, development phases, QA, UAT, go-live. What we cannot plan for is how long it takes for feedback to land on our end.
If your sign-off process involves multiple departments, senior stakeholders with packed diaries, or a legal review, that is completely fine. We have delivered projects in exactly those environments. The key is knowing about it upfront so we can build it into the plan rather than discovering it mid-sprint.
Tell us how your business works and we will work with it. The projects that run smoothest are the ones where the approval chain is agreed before anyone writes a line of code.
3. Content is rarely as ready as it feels
This one comes up on almost every project. Not because clients are unprepared, but because content is genuinely hard to get right, and it always takes longer than expected.
Copy, images, product descriptions, team bios, updated policy pages, old assets that need replacing. It all needs to exist before a website can go live and pulling it together whilst a build is in progress is a significant undertaking.
If content is a risk area for your project, say so early. We can plan around it, phase the build, or bring in copywriting support where it helps. What does not work is discovering in the final weeks that key pages are still waiting on text.
4. Consolidated feedback moves projects forward
We welcome feedback. It is how good work becomes great work. What can slow a project down is feedback that arrives in multiple emails from multiple people, sometimes with conflicting views, across a two-week window.
The most effective approach is straightforward: one point of contact, one consolidated round of feedback, with a clear list of changes. It respects everyone's time and keeps momentum going in the right direction.
If your team has opinions on the work (and they will), that is a good thing. Channel them through one person who has the authority to make decisions. It makes for a cleaner process and a better result.
5. Changing direction early is fine. Changing it late is expensive
Requirements evolve. Businesses shift. Someone sees a competitor's website and has a new idea. This is all part of the process, and we are used to it.
The earlier a change comes, the easier it is to absorb. A new direction in week two is a conversation. The same change in week eight affects timelines, budgets, and the scope of work already completed. It does not have to be a problem, but it does need to be managed properly.
If something is changing on your side, tell us as soon as you know. We will find the best way to handle it, whether that means adjusting the current phase or planning a follow-on sprint. What matters is that we are working with the right information at the right time.
The best projects are partnerships
The clients, we do our best work with, are not necessarily the ones with the largest budgets or the clearest briefs (though both help). They are the ones who treat the project as a shared endeavour. Who communicate openly, respond promptly, and trust us to do what we do best.
That dynamic is what turns a good project into something both sides are genuinely proud of.
If you are planning a new web or software project and want to talk it through before you brief anyone, we are happy to have that conversation. No commitment, no jargon, just an honest chat about what you are trying to achieve.