Websites and web applications built front-end to back-end — designed around what a visitor needs to do, and built so the next developer can pick them up.
Most websites we are asked to fix were not badly built. They were built without anyone deciding what the site was for, so every page hedges, nothing is easy to find, and the enquiry form sits at the bottom of a page nobody scrolls.
We start with what a visitor has to be able to do, and build backwards from that. The result tends to be smaller than what people expect to be quoted for, and it converts better, because a site that does three things well beats one that does eleven badly.
Layout, responsive behaviour and the front-end code, built to your brand rather than dropped into a bought template that a hundred other businesses are also using.
Forms that reach a real inbox, content you can edit yourself, and connections to whatever you already run — CRM, accounting, WhatsApp, payment gateways.
Compressed images, trimmed fonts, sensible caching. We check what the browser actually downloads rather than trusting a plugin that claims to have optimised it.
Correct titles and descriptions, a working sitemap, structured data, and analytics set up so you can tell which pages bring enquiries.
Code, hosting and domain in your name, with documentation. If you move to another developer later, nothing here is designed to make that difficult.
A conversation about what visitors should be able to do and who they are. We write it down, with the assumptions visible, so the quote can be compared against anyone else's.
Pages and navigation agreed before any design work, because rearranging a sitemap is cheap and rearranging a built site is not.
Design and development in one pass, with a staging link you can look at throughout rather than a reveal at the end.
Redirects from old URLs, Search Console verified, speed measured against real numbers. Then we watch it for a fortnight.
We would rather say so now than three meetings in.
A brochure site for a small business sits at the lower end. Anything with logins, payments, a booking flow or an admin panel is quoted per scope — with the assumptions written down so you can compare our number against anyone else’s.
Whichever costs less over the next two years. WordPress is a good answer when you want to edit content daily and the site is fairly conventional. It is a poor answer when the site does something specific, because you end up with nine plugins holding it together and every one of them is a security update you now own.
Usually. We look at the existing code first and tell you honestly whether repairing or rebuilding is cheaper. Sometimes the build is sound and the problem is one slow query or a bad information architecture.
You do — domain, hosting account and code. We will hand over access whenever you ask, without a conversation about it.
Describe the problem rather than the solution. We will tell you what it takes — including when the answer is smaller than you expected, or when web development is not what you need at all.
The thinking behind the work, at more length.
Most slow sites are not slow because of hosting. They are slow because of what the page loads before it shows anyone anything — and that is fixable without rebuilding.
Read moreWhat is happening in this corner of the industry right now.
Media3 1.11 expands the Compose UI modules with slot-based player layouts, gesture controls, new state holders and a PlayerPool for short-form video feeds. The Cast extension gains programmatic configuration and system output switcher support, alongside a Ktor network extension and Ogg and WAV muxing.
Read moreInternal tools, dashboards and integrations built around how your business actually runs — starting with the smallest version that removes the most pain.
What this involvesAndroid apps from a first version that proves the idea to the release handling logins, payments and notifications — with the yearly platform updates that keep it published.
What this involvesStores built on Shopify, WooCommerce or from scratch — chosen on what your catalogue and margins justify, not on what is easiest to build.
What this involves
