I design and build business websites that load fast, read clearly and rank: static-first architecture, answer-first content structure, and schema wired in from the start — sites built to be found and to convert rather than to win awards.
What is wrong with most business websites
The average one is a brochure PDF wearing HTML. Five megabytes of hero animation. “We provide end-to-end solutions” set in nine fonts. And no answer anywhere to the only three questions a visitor actually has: what do you do, can I trust you, what happens next.
Underneath that, the technical layer is usually worse than the design. Rendered client-side by whichever builder was fashionable, which means search engines and AI crawlers receive approximately nothing — the rendering gate that decides whether you exist to the machines your buyers now ask first. Sundar hai, but sundar doesn’t rank.
What the build includes
- Static-first architecture. Every page real HTML, fast on a phone in a lift, crawlable without executing a line of JavaScript. This site is the demonstration — view source on any page.
- Answer-first structure. Each page opens with what it is, then earns the elaboration. Headings phrased as the questions buyers type, which serves readers and extraction engines identically.
- Copy help. Turning what you actually do into the words buyers search for. Most business sites fail on language before they fail on design.
- The invisible forty per cent. Schema, sitemap, analytics, Search Console, redirects, canonical discipline. Routinely skipped by design-led builds and routinely the reason those builds never rank.
- Handover that means it. Your team edits content without calling me.
How this differs from a design agency
A design agency sells you an appearance and treats performance and structure as someone else’s phase. I build the structure first and make it look considered — which is a different sequence with a different outcome.
That trade is worth stating honestly: if you want an award-winning visual experience with bespoke illustration and motion design, hire a design studio, and hire them properly. What I build is a site that is fast, findable, clearly written and easy to maintain. On this site those constraints produced something I am happy to show, but the constraints came first and the aesthetics followed.
The order that matters
Structure, then content, then appearance. Almost every disappointing website was built in the reverse order — a design approved in a presentation, content poured in afterwards to fit the boxes, and structure discovered at the end when someone asked why nothing ranks.
Doing it forwards feels slower for the first fortnight and is considerably faster overall, because nothing gets rebuilt to accommodate something that should have been decided first.
What the process looks like
Week one: structure. Sitemap, page purposes, the questions each page answers, and the URL scheme — which is a permanent decision and deserves an hour of proper thought rather than a naming convention chosen in a hurry.
Weeks two and three: content and build in parallel. Pages get written as they get built, because writing into a real layout produces better copy than writing into a document and pouring it in afterwards.
Week four: the invisible layer and handover. Schema, sitemap, analytics, Search Console, redirects from any old URLs, plus a short session so your team can edit confidently.
Throughout, you see it on a real URL rather than in flat mockups, because a design approved as an image regularly disappoints as a website — particularly on a phone, which is where most of your visitors are.
The maintenance question
A static site of this kind needs almost nothing: content edits by your team, dependency updates occasionally, and a re-crawl after any significant change. There is no plugin ecosystem to patch weekly and no database to fall over.
That is a deliberate reduction in ongoing revenue for me and a deliberate reduction in ongoing cost for you. It is also why I will not sell a maintenance retainer on a brochure site — there is not enough genuine work in it to justify one, and pretending otherwise is how agencies fund themselves after delivery.
What I do offer afterwards is a quarterly check and a re-crawl after any significant change, priced as the small piece of work it actually is. Most clients need it twice a year, notice when they do not, and appreciate being told the difference rather than billed through it regardless.
Related reading
/services/website-redesign — when a site already has traffic to protect · /services/technical-seo — the eligibility layer · /services/generative-engine-opt — being readable by answer engines · /blog/conversion-optimisation — making the pages convert
The five-second test
Open your site and time how long it takes a stranger to learn what you do. If it is more than five seconds, the problem is not the design. /contact — seedhi baat, fixed quote, fast site.
Questions I actually get
WordPress or custom?
Whichever serves the job. The non-negotiables are speed, static rendering and clean structure; the content management system is an implementation detail. I will recommend the boring option that your team can maintain over the impressive one they cannot.
How long and how much?
A focused business site is weeks and a fixed quote. If someone is quoting months for a brochure site, they are building their invoice rather than your website — the exception being genuine application work, which is a different service.
Can our team edit it afterwards?
Yes, and that is deliberate. A site only I can update is a hostage situation dressed as a service. Content editing goes to your team with a short handover; the parts that should not be casually edited are the parts that affect rankings.
Do you do branding and logos?
Light touch only, and I will tell you honestly when you need a real brand designer instead. Building a good site around a weak identity produces a competent site nobody remembers.
What about the redesign of an existing site?
Different service, different risks — see the redesign page. If your current site has traffic, the redirect work matters more than the design work, and getting that order wrong is how businesses lose years of rankings in a weekend.
Will it be fast?
Yes, because it is built static-first, and I will show you measured numbers on real pages rather than a score from a tool run on a laptop. Speed is a build decision rather than an optimisation phase bolted on afterwards.