Web development built around the work your product has to do

When does a custom build beat a template?

When the product has workflows, permissions, integrations or interactions that a template cannot carry without being fought. The signal is usually plugins: once a managed platform needs five of them to approximate what you need, you are already maintaining a custom system with none of the advantages of one.

When the honest requirement is publishing and updating information, a managed platform is the better answer and we will say so. Paying for a custom build to run a brochure site is a poor trade, and it is not a trade we will recommend.

The clearest line is state and permissions. Once people have accounts, data that changes, and different things they are allowed to do, you are building an application regardless of what it is called — and applications want to be designed as applications from the beginning.

What does an engagement include?

Product definition: the prioritised scope, the key journeys, and acceptance criteria written in observable terms. "An authorised member can create a record, find it later, change it, and see a comprehensible error when a required field is missing" is reviewable. "Intuitive" is not.

Interface and application: responsive layouts, accessible interactions, front-end implementation and the server-side features in the brief. Loading, empty, error and permission-denied states are part of this, not an afterthought — most of the difference between a demo and a product lives in those four screens.

Connected systems: APIs, content management, authentication and third-party services chosen around the requirements. Where the integration is the risk, we prototype it early rather than discovering its limits during the final week.

Release and handover: testing, deployment configuration, documentation and an agreed maintenance plan. Repository access, hosting accounts and third-party licences are named in the proposal, because ownership is much easier to agree before launch than after.

What kinds of web systems have you built?

AgencyOS is a multi-tenant white-label platform: operator, admin and client portals running off one API across 78 data models, with each operator's marketing site provisioned from an embedded generator. It uses a transactional outbox and message queues because a service business cannot afford a record and the event announcing it to drift apart.

Materials Suppliers is a B2B marketplace where every supplier has their own payment account and each order splits automatically between platform commission and vendor wallet, gated behind automated KYC. The food-delivery marketplace serves diners, restaurants and riders through separate front doors and one shared API described by a single OpenAPI spec, with rider payouts gated on onboarding eligibility.

Wen is product engineering at the other end of the scale: one account spanning perpetuals, spot and copy-trading, with embedded wallets so the backend never holds a private key. Swift MVP replaced the discovery call with a structured brief and a guided wizard, delivering hosted sites inside a fixed window.

Different products, one pattern: the interesting work is the part where data, money or permissions change hands, and that is where the design effort goes.

Is SEO included in web development?

The technical foundations are, when they are in scope, and we would rather they always were. Semantic markup, real crawlable links rather than buttons that only work with JavaScript, unique titles and descriptions, sensible URL structure, valid structured data, and a build whose performance was considered rather than measured afterwards.

Editorial SEO is different work and should be agreed separately so nobody is disappointed. Keyword research, content production, digital PR and search reporting are ongoing activities with their own cadence, and folding them silently into a build estimate helps no one.

We do not offer ranking guarantees, and we would treat an agency that does with suspicion. What can be promised is that the site will not be the reason you cannot rank: that the pages are reachable, the markup is honest, the content is in the HTML rather than assembled only in the browser, and the structure matches how people actually search.

If discovery is the main objective rather than a constraint, our web design and technical SEO service covers it in more depth.

Can you improve an existing site instead of rebuilding it?

Often, and it is usually the cheaper answer. An existing-site engagement starts with an assessment: the code, the hosting, the dependency health, the analytics you have, the journeys that matter commercially, and where the friction actually is.

That assessment decides the recommendation. Targeted improvement wins when the architecture is sound and the problems are localised. A rebuild wins when the foundations block every change, and it is worth doing in stages, keeping URLs and their search equity intact, rather than as one release that replaces everything at once.

What shapes the estimate?

The number of distinct workflows, not the number of pages. Ten pages that present content cost less than one screen where four roles do different things to the same record.

Then: integration quality — a documented API with a sandbox behaves very differently from an undocumented legacy system; content readiness, which is the most commonly underestimated item in any web project; data migration, if there is any; and how many review cycles the organisation genuinely needs.

Hosting, external service charges, ongoing support and ownership are stated in the proposal rather than left implicit. Our guide to custom software cost sets out the same reasoning in more detail.