The C Word: What Nobody Tells You About Working With a Web Studio

Communication. Everyone likes the idea of it, but often, it doesn't happen in practice. It's the thing that gets left out when things get busy. The thing that gets put off until "later". The thing that people say "we should do better at" but never actually do anything about. But it matters. A lot.

I've worked in companies where communication was an afterthought and companies where it was baked into everything. The difference is night and day. When it works, projects move. Great things get done. When it doesn't, things get missed, timelines slip and people get frustrated.

A web project has moving parts. Design decisions, content, technical choices, third-party integrations, timelines. No single person can hold all of that in their head. So you have to talk. Regularly. Clearly. And from both sides.

Here's what people don't realise: good communication doesn't just happen. Without conscious effort, it gets left out. It's the first thing to slip when things get busy. Sending that update, recording that walkthrough, flagging that blocker early; it all takes deliberate effort.

At Elevate North, this is a process we've built and refined over time. It didn't happen by accident. We made it a priority because we've experienced what happens when nobody does.

And that's not what we're about.

What we took from Agile

We're big on Agile at Elevate North. Not the corporate version with 47 meetings a week and a Jira board nobody looks at. The actual principles behind it.

The Agile Manifesto puts it simply:

• Individuals and interactions over processes and tools
• Working software over comprehensive documentation
• Customer collaboration over contract negotiation
• Responding to change over following a plan

Individuals and interactions over processes and tools:
that's the foundation. A project lives or dies on the people involved and how they talk to each other. No amount of fancy tooling fixes a breakdown in communication between real humans.

Customer collaboration over contract negotiation:
the best work happens when the client is part of the process, not just signing off on deliverables. It's a collaboration, not a transaction.

And responding to change over following a plan:
plans change. They always do. And that's fine. What matters is how quickly everyone knows about the change and what we're doing about it.

But in practice, for a web studio working with small and medium businesses, it really comes down to three things:

1. Communicate the plan clearly from the start. Everyone should know what's happening, when and why.
2. Keep regular updates flowing. We use Loom for this. Short video walkthroughs showing what's been built, what's coming next and any decisions that need making. We keep this weekly but it can be more or less often depending on the project.
3. Show the work early. Not when it's polished. Early. So you can see it, react to it and shape it while it's still easy to change.

That's it. No complicated framework. No Jira. Just good habits done consistently.

What you should expect from your developer

If you're hiring a web studio or a freelance developer, here's what good communication looks like from their side:

You should never have to chase for an update. If you're emailing asking "how's it going?" then something has already gone wrong. Updates should come to you. Regularly. Without asking.

You should be able to see the work in progress. Not just a final reveal at the end. You should be seeing builds early and often. We send Loom walkthroughs so you can watch in your own time, pause, rewind and come back with questions.

Technical decisions should be explained in plain English. If your developer can't explain why they've made a choice without drowning you in jargon, that's a red flag. You don't need to understand the code. You do need to understand the reasoning.

Timelines should be honest. If something is going to take longer than expected, you should hear about it before the deadline passes. Not after.

What your developer needs from you

This bit is just as important. It's also where most projects fall apart.

Communication is a two-way street. Full stop. The best developer in the world can't carry a project alone. When one side goes quiet, everything stalls. Projects where you're putting in the work, sending updates, asking for input and getting nothing back. It's exhausting. And it kills the work.

So if you're hiring someone to build something for you, here's your side of the deal:

Feedback, even rough feedback, is better than no feedback. "I'm not sure about this but I can't put my finger on why" is genuinely useful. "Looks great!" when it doesn't is not. Not got time to update? Just say "I will get back to you on this by the end of the week". Anything is better than silence.

Decisions need to happen. Not instantly. But within a reasonable window. When feedback or approvals sit in limbo, everything downstream gets pushed back. Your developer can't move forward without your input on certain things.

Content needs to arrive. Copy, images, brand assets. These things take time to gather and they're almost always the bottleneck. If your developer asks for content early, there's a reason. It's because the build literally depends on it.

Be honest about changes. Changed your mind about something? That's fine. Genuinely. It happens on every project. Just say it early so we can adjust the plan rather than discovering it three weeks in.

Why this matters

Our clients regularly tell us that our communication is one of the best things about working with us. Everything is clear. They know where things are at. They feel involved in the process rather than just waiting for a big reveal at the end.

That doesn't happen by accident. It happens because we've made it a priority. Short Loom updates. Early access to work in progress. Honest conversations about timelines and trade-offs.

The best projects we've worked on have one thing in common: both sides showed up. Both sides communicated. Both sides treated the project like a collaboration, not a hand-off. The worst ones? One side went quiet, and everything stalled.

When people communicate, projects move. Amazing things happen. Problems get solved before they become disasters. When that breaks down, everything suffers. We're great at a lot of things at Elevate North. But we can't read minds. Nobody can. So we make communication a non-negotiable part of how we work.

If that sounds like the kind of studio you'd want to work with, get in touch. We'd love to hear about your project.