How we think about the work

A straightforward guide to websites, hosting and business tools

If you're paying someone to build or look after a website, you should understand what they're doing. This page covers the basics we think are worth knowing before a project starts.

What makes a website useful?

A useful website answers the questions people already have. What do you do? Where do you work? How can they contact you? Design matters, but getting those answers in the right place comes first.

For a service business, that often means a home page, a page for each main service, examples of work and a clear contact route. Then we deal with speed, accessibility and the technical details.

Why hosting needs maintenance

Hosting isn't something you switch on and forget. Domains expire, certificates renew, software needs updates and contact forms can quietly stop sending. Regular checks catch a lot of avoidable problems.

We can check DNS, SSL, backups, uptime and email routing, then tell you what needs doing in plain English.

When custom software is worth it

Custom software can make sense when a repeated admin job is taking too much time or several systems don't quite work together. The aim isn't to build a huge platform. It's to fix a specific problem.

That might be a quote tracker, a simple customer portal or an internal screen that puts the information your team needs in one place.

Build process

How a project normally runs

We start by agreeing what the project needs to do and who it's for. That saves both of us from polishing a feature nobody actually needs.

First conversation: what you need, who will use it and what you already have.
Plan: the pages or workflow, the information involved and anything it needs to connect to.
Build: we make it, test it and keep you updated as the useful parts come together.
Launch: we handle the final checks, domain changes, backups and handover notes.
Afterwards: you can take it from there or ask us to keep looking after it.

Website checklist before launch

Every public page has original text that helps a visitor make a decision.
Contact routes are visible, tested and supported by a privacy policy.
Images have descriptive alternative text and are compressed sensibly.
404, legal, sitemap and important utility pages do not look unfinished.
Analytics and cookie messaging are documented so visitors know what is collected.

Content that tends to perform better

Good content sounds like the business behind it. It answers specific questions and gives people enough information to decide whether to get in touch.

We're still building up our own library of project notes and guides. We'd rather publish useful detail as we have it than pad the site with generic articles just to make it look busy.