Development is what happens after the layout is agreed: the code, the forms, the hosting, the parts nobody sees until they break. Done right, it is invisible. Done badly, it is every problem you will have for the next three years.
Website development is the engineering: turning a design into a site that loads fast, works everywhere, and keeps working. Markup and styles, forms that reliably reach you, hosting and DNS, the structure search engines read, and the accessibility that decides whether a chunk of your visitors can use the site at all.
It sits next to two neighbours. Web design decides what gets built and why. Website redesign handles the case where a site already exists and the rankings attached to it must survive the move. Development is the middle: the actual building.
None of this is visible on a screenshot, which is exactly why it gets skipped. Here is what is under a site that holds up.
Real headings in a real order, buttons that are buttons, links that are links, images with alt text that describes the image. This is not pedantry. It is the same structure a screen reader uses to navigate and a search engine uses to understand the page. A wall of styled divs looks identical to a sighted visitor and is useless to both.
Speed is a build decision, not a plugin. It comes from not shipping what you do not need: images sized and served in modern formats, fonts that do not block the first paint, scripts that are not there because nobody was sure what they did. Bolting an optimisation tool onto a bloated build is treating the symptom. That is why speed work so often turns into a build conversation.
A contact form is the only revenue-critical thing on most small business sites, and it is the least tested. Submitting it in a browser once proves nothing about whether the mail lands. Delivery depends on the sending domain being authenticated: SPF, DKIM and DMARC configured properly. Without that, your enquiries go to spam and you find out when a customer asks why you ignored them.
A surprising number of small business sites are hosted somewhere nobody can identify, on an account registered to a developer who moved on. Knowing where your site lives, who owns the domain, and where DNS is answered is not an advanced topic. It is the difference between a ten minute fix and a two week recovery. See Cloudflare management for how we usually set this up.
Keyboard navigation, real contrast, focus you can see, motion that respects a reduced-motion preference. Some of your visitors need this. All of your visitors benefit from it. It is dramatically cheaper to build in than to retrofit.
Being clear about the edges saves everyone a wasted call.
From the design work, or from what you already have. Ambiguity here becomes rework later, and rework is the expensive part.
Static, or a content system, or something in between. The question is how often the content really changes and who changes it, not what is fashionable. Complexity you do not need is a bill you pay forever.
Structure first, then styles, then behaviour. Tested on real phones, not just a narrowed browser window, and with the keyboard as well as the mouse.
Forms, delivery, DNS, certificates, redirects. This is where sites usually break, so it gets tested rather than assumed.
Live is not done. Indexable, measured, forms confirmed arriving, and the launch checklist actually worked through.
Your domain, your hosting, your code, documented. Ongoing care is your choice, not a condition of getting your site back.
We build the site and the systems it depends on, because in a small business they are the same problem. A site whose forms do not deliver is not a site with a form.
Design decides what the site says and how it looks and behaves. Development is making that real: the markup, the styles, the forms, the hosting, the things that have to keep working at two in the morning when nobody is watching.
For most small business projects they are one engagement, and we do both. This page exists separately because some people arrive already knowing what they want built, and the build is the actual question.
Not automatically, and the default assumption that you do costs small businesses a lot of unnecessary maintenance. WordPress makes sense when you genuinely publish often and need a full editing system. It brings plugins, updates, and a permanent security surface that has to be looked after.
A brochure site of a handful of pages that changes a few times a year does not need any of that. A static site has no database to attack, nothing to patch weekly, and it is faster by default. The right answer depends on how often the content really changes, not on what is popular. We will tell you which one your situation calls for, including when it is WordPress.
Yes, and this is worth more attention than it usually gets. The common failure is not the form. It is delivery: the form submits, the visitor sees a thank you, and the message quietly lands in spam or never sends at all. Nobody notices for weeks because nothing looks broken.
A form is only finished when it has been tested end to end and the sending domain is authenticated properly with SPF, DKIM and DMARC. That is the same work behind business email going to spam, and it is why we treat forms and email as one problem.
No. We do not build stores, carts, checkout flows or payment systems, and we do not take those projects. It is not a capability we have and pretending otherwise would not end well for you.
If you need a store, you want a specialist in that. We can still help with everything around it: the DNS and Cloudflare, the business email, and the technical SEO.
You should not be, and you should ask this of anyone quoting you. Your domain should be registered to you, the hosting account should be yours or transferable, and the code should be handed over. We build on standard tooling so someone else can pick it up.
Ongoing maintenance is a service you can choose to buy, not a hostage arrangement. A site you cannot leave is a bad site regardless of how it looks.
Design and build a site that explains your business and brings in enquiries.
Rebuild an existing site without losing the rankings you already have.
Find what is actually slowing the site down, then fix it.
The crawling, indexing and structure work search engines depend on.
DNS, SSL, caching and protection, configured properly.
What to verify before and after a site goes live.
Tell us what the site needs to do that it currently cannot. We will tell you whether it is a build issue, a hosting issue, or something that does not need a developer at all.