01
It loads too slowly to matter
A large share of visitors leave before the page appears. On mobile data, a heavy theme with six plugins and unoptimised images loses the visitor before your headline has even rendered.
Most small business websites are brochures. They describe the business, they look perfectly fine, and they generate almost nothing. I build sites around the path a customer actually takes — find you, trust you, contact you — and set up the tracking that proves whether that path works.
Three failures account for most of the small business sites that quietly generate nothing.
01
A large share of visitors leave before the page appears. On mobile data, a heavy theme with six plugins and unoptimised images loses the visitor before your headline has even rendered.
02
Most sites open with the company name and a stock photo. Someone who arrives with a specific problem has to hunt for evidence that you solve it, and most of them will not bother.
03
Without conversion tracking, a site producing two enquiries a month looks identical to one producing twenty. You cannot improve what you have never measured.
A website is not a design project. It is a sales asset that happens to need design — and it should be judged on enquiries, not on compliments.
Everything below is part of the standard build, not an upsell discovered halfway through.
Before any design happens, we map who is landing on the site, what they need in order to decide, and the shortest honest path from arrival to enquiry. That map becomes the sitemap.
Layout, type and colour built around your brand rather than a marketplace template — so the site looks like your business and not like four hundred others in the same category.
Hand-built lightweight front-end code or a clean CMS setup, chosen by how you will actually maintain the site. No plugin sprawl, no dependency on a theme that stops being updated.
Every page tested on real mobile viewports and tuned for Core Web Vitals: image formats and sizing, font loading strategy, script weight and layout stability.
Title tags, meta descriptions, heading hierarchy, internal linking, schema markup, XML sitemap and robots.txt all configured at launch — so the site is indexable the day it goes live.
GA4, Search Console and conversion events wired up, plus a walkthrough so you can update your own content without calling me every time a phone number changes.
A call to understand the business, the customer and what a good month looks like in enquiries. Then a written scope with a fee and a date.
Sitemap, page structure and messaging agreed before any pixel is designed. Cheap to change now, expensive to change later.
Design and development, reviewed on a live staging link rather than in flat images, so you see the real thing on your own phone.
Go live, tracking verified, Search Console submitted, and a handover walkthrough. Thirty days of support follows.
Every project starts with a short call, then a written scope: what gets built, what it costs and when it ships. You approve that before any work starts.
Changes that fall outside the agreed scope get quoted separately before anything is built, so the number you approve at the start is the number you pay at the end.
For a standard 5–8 page business site, kickoff to launch. Larger builds are scoped separately.
Quoted after scoping, never billed hourly.
Fixes, tweaks and questions included after go-live. Ongoing work is optional, never a locked retainer.
It depends on scope — a five-page business site is a very different build from one with a booking system or a multi-language catalogue. Every project is quoted as a fixed fee after a short scoping call, so you know the number before anything starts.
There is no hourly billing, and nothing that was in the agreed scope turns into a surprise invoice later.
A standard five to eight page business website usually takes two to four weeks from kickoff to launch.
The main variable is not development — it is content. Projects that run long almost always run long because copy, photographs and approvals are still being gathered. If your content is ready, the timeline holds.
Both, depending on what you actually need. If you will be publishing regularly and want to edit everything yourself, a clean CMS setup makes sense. If the site is mostly static and speed matters more than in-house editing, hand-built front-end code will load faster and cost less to maintain.
I recommend based on how you will use the site over the next two years, not on which is quicker for me to build.
Yes, and that is where it gets designed first. Most traffic to small business sites in India arrives on mobile data, so every layout is built and tested on real mobile viewports before desktop is finalised.
Core Web Vitals — how fast it loads, how quickly it responds and whether the layout jumps around while loading — are treated as build requirements, not as an optimisation project for later.
Often yes, and sometimes that is the wrong call. If the current site has rankings and content worth keeping, a redesign that preserves URLs and structure protects that investment. If it is built on a bloated theme that will never load quickly, rebuilding is cheaper than fighting it.
Run your current site through the free AI Growth Score first — the scan will show which of those two situations you are actually in.
Tell me what your business does and who you need to reach. I will tell you what the site needs to do differently — and roughly what that costs.