When you’re a website developer, you’re constantly balancing four sometimes conflicting priorities:

  • The website visitor experience

  • The client’s needs (and their ability to update the site)

  • Security and future-proofing

  • Other developers who may take on the site later

Juggling all these is both challenging and rewarding — but when they clash, it can get stressful fast.

The Process Should Be Collaborative

Getting a website from idea to launch should feel like a partnership, not a tug-of-war. Your developer genuinely wants the same thing you do — a website you're happy with that works brilliantly.

Here’s how you can help make the process smooth, collaborative, and even enjoyable — and get a website that may exceed your expectations.

Be Really, Really Clear

You’re not being pedantic. Websites, like any complex project, can go in a hundred directions.
Help your developer by breaking your brief down into headings, bullet points, and clear tasks. It makes tracking progress easier for everyone.

And remember — development isn’t always linear. Sometimes an idea won’t work, or a better one will come along. That’s part of the creative process. As long as there’s shared clarity on the overall goal, it’s all good.

When Things Go Wrong (Because Sometimes They Do)

No website is immune to glitches. From minor bugs to the dreaded white screen of death, things happen.

Believe me — if it’s stressful for you, it’s ten times worse for your developer. We want to fix it quickly. It’s not just about your satisfaction, but our reputation too.

And no, we’re definitely not "down the pub" ignoring it.

Report Issues Early — And Give Detail

Don’t wait. The sooner you flag a problem, the easier it is to trace and fix.
When you do, include:

  • What happened

  • When you noticed it

  • What you were doing when it happened

 Screenshots Are Gold

Please don’t send a photo of your laptop screen taken with your phone!
Use your device’s screenshot tool so we can see exactly what you see.

Here’s how:

  • Mac: Shift + Command + 3

  • Windows: Windows + PrtScn

  • iPhone/Android: Use the side + volume buttons

And don’t forget to include the URL (web address) in your screenshot — it can be key to solving the issue.

Always Double-Check Fixes

If your developer says an issue is fixed — check it.
Not because you shouldn’t trust them, but because it avoids misunderstandings. Sometimes it’s not the issue they thought it was, or it hasn’t been fixed quite how you expected.

A good developer will check their work — but a second pair of eyes always helps.

What Really Counts as “Urgent”?

"Urgent" means:

  • Your website is down

  • Your email is down

  • A critical function (like taking payments) isn’t working

It doesn’t mean:

  • A colour is wrong

  • A heading font looks odd

These things matter — but if everything is urgent, nothing is.

When developers see “URGENT” in the subject line, our adrenaline spikes. So please save it for real emergencies.

We Haven’t Vanished (Or Gone Down the Pub)

A good developer will update you regularly.
But sometimes progress is slow, or they’re deeply focused. It’s fine to check in — just be patient.

Trying to hurry a developer with emotional pressure doesn’t make them work faster. In fact, it’s likely to make them more prone to mistakes.

Calm doesn’t mean careless. Often, it means we’ve learned to manage stress so we can stay logical and solve problems for you.

Final Thoughts

Web development is a craft that works best when there’s trust, clarity, and mutual respect.
Help your developer help you — and you’ll both end up with something you’re proud of.