Questions people ask before we start.

Businesses that need a website, online store, or web app built properly, whether it is their first site or a redesign that cannot afford to lose its search traffic. I also take on dashboards, internal tools, integrations, and technical audits.

Both. A new site starts from the offer and the page structure. A redesign or rebuild starts one step earlier, with a crawl of the current site, so the pages that already earn search traffic and enquiries are kept.

Yes. Online stores for retail and trade buyers, from catalogue structure and product pages to checkout or quote flows, with payment signing kept on the server. Stainless & Aluminium and Zahar Fragrance are both live examples.

Yes. I work remotely with clients in the UK, the UAE, and elsewhere. Updates come in writing, and we book a call when a decision is easier to make live.

Send the current URL or product context, who uses it, what is not working, the outcome you want, and any timing or budget constraint. Rough notes are enough if the problem is clear.

Website builds typically start at £750. Beyond that, the price depends on the scope, the risk, the timeline, and how much product thinking the job needs. A focused build is usually a fixed fee. Product work that keeps changing is split into milestones or an ongoing monthly arrangement.

Usually I can give a useful range from a clear brief, the current URL, and a list of what the site has to do. The final quote comes once I understand the main flows, the integrations, who writes the content, and what has to be ready at launch.

A focused website usually takes three to six weeks. Dashboards, portals, and builds with a lot of integration work tend to take six to twelve weeks. I confirm the schedule once I know the scope, because content, approvals, and other systems all affect it.

Four stages: agree what the site has to do, plan the pages and how they behave, build and test, then launch with written handover notes. You review working builds along the way, so the finished site is never a surprise.

Short written updates, links to working builds, and a clear list of anything I need you to decide. Routine updates go by email or whatever project tool you use. Calls are for the first conversation, reviews, and decisions with real tradeoffs.

Mostly React, Next.js, TypeScript, Node.js, and PostgreSQL, plus whatever APIs and services the business needs. If a project is better served by something else, I will say so instead of forcing my usual stack onto it.

Yes. Layouts that work on phones, keyboard access, readable contrast, a proper heading structure, correctly sized images, and performance checks are all part of the build. If an existing platform or third-party tool limits any of that, I tell you early and write it down.

Yes: existing APIs, databases, CRMs, sign-in providers, payment gateways, and other business tools. Before I commit to a plan I check the documentation, the access I will have, the data model, and what happens when the other system fails.

The technical foundations: page titles and descriptions, a sensible heading structure, crawl controls, sitemaps, structured data where it is accurate, and fast pages. Ongoing content writing and link building are separate jobs and are not part of a build.

It will be built to be found: titles, descriptions, headings, structured data, sitemaps, and speed are part of the build rather than an add-on. Where a page ranks still depends on your competition and your content, so nobody can honestly guarantee a position.

You get handover notes and a set period in which I fix anything related to the launch. Ongoing maintenance, monitoring, content changes, and new features can be arranged separately if you need them.

You do. At handover you get the repository, the deployment, and written notes on where to change what, so the site never depends on me to keep running.

Most sites run on Vercel's Pro plan or a similar host for a small monthly fee, with no server to patch and no plugin subscriptions. Maintenance, content changes, and improvements are available as a monthly support engagement, from £600 a month.

Often, yes. I start by auditing the interface, the code structure, the dependencies, performance, and the deployment setup. If fixing what is there is safer than rebuilding, the plan says so.