Not every business needs the same website, and most of the disappointment we see comes from a company being sold the shape that suits the agency rather than the shape that suits the business. Here are the types we build, and how to tell which one you actually need.
Different businesses need structurally different websites: a campaign landing page, a multi-location site with an indexable page per branch, a multi-language site with proper hreflang, a booking site wired to a calendar, or a logged-in portal. The type decides the URL architecture, which is the decision hardest to change later.
From a single campaign page to a logged-in portal — the list below is the whole menu, not a sample.
Brief to live, with tracking, for a campaign that had a fixed launch date.
A multi-location site where each branch has its own indexable page and its own tracked enquiry form.
Every page type we ship is server-rendered with its own metadata. No JavaScript-only content.
Architecture document
Figma templates
Staging site with real content
Fully populated staging site
Live site and a validation report
A five-branch clinic with one 'Locations' page listing five addresses cannot rank in five cities. A course provider with one 'Courses' page cannot rank for any course. The content exists; it is just stored somewhere Google cannot award a ranking to.
The right answer is usually obvious once the question is asked properly. It rarely gets asked.
One locations page for eleven branches, so 'dentist in Ballygunge' ranks a directory instead of you.
A page per location with its own address, hours, staff, schema and enquiry form — and a template so branch twelve is a data entry job.
A Hindi or Bengali audience served an English site through a translate widget that search engines cannot index.
Real per-language URLs with hreflang, translated metadata and language-appropriate content rather than machine output.
Every ad points at the homepage, so the message match is poor and the cost per lead is high.
A landing page per offer with the ad's promise in the H1, one action, and tracking wired to the form.
Bookings taken over the phone into a paper diary, with no reminders and no record of who did not turn up.
Online booking against real availability, with confirmations and reminders on WhatsApp and a calendar staff already use.
A listings database rendered client-side, so none of the listings exist as far as search is concerned.
Server-rendered listing pages with structured data, sitemaps that update automatically, and pagination crawlers can follow.
Documents and updates emailed individually, with no record of who has seen what.
A logged-in area with roles, documents, notifications and an access log.
The value in these builds is rarely in any single page. It is in the template behind it, because that is what turns the eleventh location or the four-hundredth listing into content entry rather than a project.
Once a location template exists, a new branch costs an hour of someone's time. Without one, it costs a design round and a developer. That difference decides whether a site can grow with the business.
Search engines award rankings to URLs. Content that does not have its own URL cannot rank, no matter how good it is. Choosing the shape is choosing what is allowed to rank.
A template guarantees every location page has hours, a map, schema and a form. Left to individual pages, three of them will be missing something within a year.
With a template and a data source, hundreds of genuinely useful pages can be generated — service-by-city, product-by-application — provided each one is actually useful. Thin duplicates are a penalty, not a strategy.
Written, with reasoning, before design starts. Occasionally the recommendation is that you do not need us.
The structure for locations, languages, categories or listings — the decision that is most expensive to change afterwards.
Design per template rather than per page, which is what keeps a forty-page site inside a sensible budget.
CMS fields shaped so a non-technical editor can add a location, course or listing without breaking the layout.
LocalBusiness schema per branch, hreflang per language, and per-page metadata that is not a template with the name swapped.
Calendar integration or routed enquiry forms, with WhatsApp and CRM handoff so nothing sits in an inbox.
Generated from the content, so a new location appears in the sitemap without anyone remembering to add it.
A recorded walkthrough for the specific tasks your team will actually do, not a generic CMS manual.
Not every business needs the same website, and most of the disappointment we see comes from a company being sold the shape that suited the agency rather than the shape that suited the business.
Design can be changed later. Copy can be rewritten. URL architecture is the expensive one, because search engines award rankings to URLs — content without its own address cannot rank, however good it is. Choosing the shape of the site is choosing what is allowed to rank.
A five-branch clinic with one Locations page listing five addresses can rank once. A course provider with a single Courses page cannot rank for any individual course. The content exists — it is simply stored somewhere Google cannot award a ranking to. This is the cheapest and most common structural problem we fix.
Once a location or course template exists, adding one is filling a form: the sitemap updates itself, the schema is generated, the enquiry routing follows the rule. Without a template, every addition is a small web project — and eventually somebody stops bothering, which is why so many Indian business sites are nine months out of date.
Whatever the shape, the underlying requirements do not change: server-rendered content, fast on a mid-range Android, structured data, and conversion tracking that reaches your CRM. Those are covered on Web Development and Conversion & Analytics.
Every stage ends in something you can hold — a document, a build, a live account. If a stage cannot name its output, it is a meeting, not a stage.
What type of site, what the URL structure is, how many templates, and what the growth path looks like.
Design the templates that carry the site, mobile first, with real content in place.
Front end plus the CMS content model, built so the client team can extend it without us.
Locations, languages, courses or listings loaded and checked, with metadata written per page rather than generated.
Schema validation, hreflang checks, tracking verification, then launch with redirects if it is a replacement.
Everything here is part of the engagement at no extra cost. We do not itemise them on an invoice and we do not withhold them if you leave.
Including the times we conclude you need less than you asked for, or a CMS rather than a custom build. Free, and given before any quote.
Every build ships with the CMS structure behind it, so your eleventh location or fortieth course is data entry rather than a design project.
LocalBusiness markup per branch and a sitemap that updates itself when content is added — no one has to remember.
Recorded walkthroughs of the specific things your team will do, not a generic CMS manual.
Every old URL with traffic or links mapped to its new home, included, because this is what protects your existing rankings.
Longer answers to the questions people ask before they hire anyone for websites of every kind.
Built by us, free, no signup, nothing uploaded to a server. Take them whether or not you ever become a client.
A properly built campaign page — copy structure, mobile-first design, CRM handoff, full conversion tracking and a variant to test — is scoped on the number of unique templates and integrations rather than on page count. A template with your logo dropped into it costs less and performs like it.
Tell us what you have now and what you are trying to reach. We will audit it and tell you what we would do, what it would cost and whether you need us at all. The audit is free and yours to keep.