01
Messaging and structure
What the site needs to say, in what order. This is most of the work and it happens before any design.
Build
A website that earns its traffic.
Most business websites are a brochure that loads slowly. Yours should answer the question a visitor arrived with, make the next step obvious, and be something your own team can update without phoning anyone.
Why it matters
The short version.
A business website has one job on the first screen: make it obvious what you do and who it is for. Most fail at exactly that, because the people writing it are too close to the business to remember what a stranger does not know. The rest of the site is downstream of getting that sentence right.
Speed is a design decision rather than an engineering afterthought. A site that takes four seconds to become useful has already lost a share of its visitors before they read anything, and that share is highest on mobile connections — which is where most of your traffic is. We treat the performance budget as a constraint from the first layout, not a cleanup task.
Then there is the part that decides whether the site is still good in two years: whether your own team can update it. A site that requires a developer for a paragraph change quietly rots, because nobody wants to raise a ticket to fix a typo.
A site that needs a developer to change a paragraph quietly rots.
Is this you?
You probably need this if…
- Your site was built years ago and you avoid showing it to people
- Nobody on your team can change a paragraph without help
- It looks acceptable on desktop and falls apart on a phone
- Visitors arrive and leave without ever contacting you
What's involved
The actual work.
No two engagements are identical, but this is the shape of it.
02
Design and build
Every page and breakpoint, built to be genuinely fast rather than fast on a test rig.
03
A CMS your team will use
Content modelled around how your staff actually write, not around how developers store data.
04
Search and analytics groundwork
Structured data, sensible URLs, sitemap, and analytics that answers a real question.
What goes wrong
Mistakes worth
avoiding.
Named plainly, because most of them are easier to avoid than to undo.
-
Leading with the company, not the visitor
Nobody arrives wanting your founding story. They arrive with a problem and about eight seconds of patience for finding out whether you solve it.
-
A carousel on the homepage
People almost never see past the first slide, and the ones who do rarely interact. It is usually a way of avoiding a decision about what matters most.
-
Designing for the pitch, not the phone
The design gets approved on a large desktop monitor in a meeting. Most visitors will see it on a phone, one-handed, with something else demanding their attention.
How it runs
Start to finish.
Each phase ends in something you can open, click or read.
-
01
Discover
Who is arriving, what they need, and what you want them to do.
-
02
Design
Structure, then look, tested on real content.
-
03
Build
On a staging link you can watch as it comes together.
-
04
Launch
Migration, redirects and monitoring, then thirty days of refinement.
Deliverables
What you walk
away with.
Yours to keep, whatever happens next.
A fast, accessible, responsive site
A CMS with training and written notes
Source code and accounts in your name
Analytics and search console configured properly
Questions
Worth asking.
Anything else — email hello@haddon.software and a human replies the same business day.
Typically eight to twelve weeks from kickoff to live for a marketing site. The two things that slow it down are content and having more than one final decision-maker.
We write first drafts for every page and you edit — that is much faster than staring at a blank document, and waiting on copy is the single most common cause of a delayed launch.
Hosted on infrastructure you own, with Canadian data residency available. We set it up, document it, and hand over the keys.
Usually yes. We will recommend based on who maintains it after launch rather than on our own preference. If your team already knows a platform, that familiarity is worth a lot more than a marginally better technical choice.
Handled deliberately: we map every existing URL, set up redirects, keep the content that ranks, and monitor for four weeks afterwards. Traffic dips after a relaunch are almost always a redirect problem, which is a preventable one.
Related
You might also need…
Want to talk it through?
The first call is free, runs about thirty minutes, and you'll get a straight answer about whether we're the right fit — including when we're not.