Pages that arrive on a bad connection
Static HTML, compressed images, self-hosted fonts and no third-party script that has not earned its weight. The target is a page that opens on one bar, not one that tests well on office fibre.
Northeast India
Eight states, and a set of things national agencies reliably get wrong. They quote metro rates for a market they have never worked in, or they do not reply at all. We are in Assam, we build for the phones and connections people here actually have, and the quote does not go up because the invoice is going to Aizawl.
01 The region
Not out of malice. Out of distance, and a set of assumptions that were formed somewhere else entirely.
The Northeast is eight states — Assam, Meghalaya, Tripura, Manipur, Nagaland, Mizoram, Arunachal Pradesh and Sikkim — joined to the rest of the country by a corridor you can drive across in an hour. Most of the Indian digital industry treats it as one undifferentiated place, or as too small to send a proposal to.
Businesses here get two responses from a national agency. One is a metro quote: a rate card built for a Bengaluru client, handed to a firm in Shillong or Agartala by somebody who has asked nothing about the market. The other is silence, because the deal is not large enough to chase.
The technical picture gets missed just as often. Customers here are on mid-range Android phones, often on a connection that drops between one cell and the next, often watching their data. A four-megabyte homepage with three sliders and a chat widget does not load slowly in Kohima or Itanagar — it fails. That is the whole case for building light: a page of a few hundred kilobytes arrives on a bad connection and a heavy one does not. An engineering constraint, not a taste.
And the language changes every few hours of road. Assamese in the Brahmaputra valley, Bengali and Sylheti in the Barak. Khasi and Garo in Meghalaya. Kokborok in Tripura, Meitei in Manipur, Mizo in Mizoram, Nagamese across Nagaland — with English doing more official work in several of these states than elsewhere in India. So the question is never which languages to translate into. It is which one the transaction happens in.
An agency that has never watched a page die on a bad handover will happily build you one that does.
The states we work across
02 The work
Five decisions that come out differently when the person making them lives inside the market rather than reading about it.
Static HTML, compressed images, self-hosted fonts and no third-party script that has not earned its weight. The target is a page that opens on one bar, not one that tests well on office fibre.
Not designed wide and left to reflow. Small screens and modest hardware are the primary case here, so they get decided first rather than checked last.
Which language the site is read in, which one the enquiry arrives in, and what that means for form labels and directions. Half-done bilingual sites age worse than single-language ones.
A map pin that lands where the door is, hours that hold, and identical details across every listing. That is most of local search where nobody navigates by street address.
The quote for a Dimapur business is the quote for a Guwahati one. No distance loading, and no discount offered on the assumption that a business outside a metro expects less.
Silchar and the Barak Valley, where we are based and where most projects are first websites. And Guwahati, where nearly everybody already has a site and the work is to beat it. Each has its own page, because the argument in each is genuinely different.
What changes between one state and the next is the argument a page has to make. The method underneath it does not, and it is set out in full on its own page.
Website design services in full03 Working together
Remote delivery inside India is not remote delivery from overseas. Most of the usual complaints do not apply. The ones that do are named here.
We do travel when a project justifies it, agreed beforehand. Across this geography a visit is a real cost and most of a real day, so it gets planned rather than promised loosely and quietly dropped.
04 Cost
The most useful thing on this page may simply be that this section says exactly what the pricing page says.
Starting at ₹12,999 One-time
Four packages, published, identical in every state, with no loading for distance. Starter covers up to five pages; Business, Professional and Custom go further. Landing pages start at ₹8,999 and maintenance at ₹1,499 a month. If you have been quoted several times this for a comparable brief, ask what justifies the difference. There may be a good answer, and it is worth hearing somebody say it out loud.
What each package includes, page allowances, revision rounds and the maintenance plans.
See Full Pricing05 Questions
The first one is the objection we would raise ourselves if we were sitting on your side of the table.
Select a question to expand
One answer at a time.
Some of them are very good, and if one wants your business, take the meeting. What a studio inside the region gives you is the set of assumptions that never has to be explained: that your customers are on mid-range phones and variable data, that a Shillong buyer and a Silchar buyer are not the same person, that the enquiry will arrive on WhatsApp. Those assumptions shape the build. Reading them in a briefing document is not the same as already holding them.
No. The packages are published and the price is the same whether the business is in Guwahati, Aizawl or Gangtok. Travel, where a project needs it, is agreed and costed separately and in advance — across this geography that is a real expense, and it does not get buried inside a project fee.
Substantially. It rules out heavy page builders, image carousels, several font families, and third-party scripts loaded site-wide for the sake of one widget. It pushes toward static HTML, images compressed and served at the size they are displayed at, and JavaScript only where it earns its place. This site is built that way — you are welcome to check what it weighs.
Sometimes, and it should be a decision rather than a default. A full second language means every future change happens twice, and the version nobody maintains is the one customers eventually land on. The usual answer is English for the site, with the local language where the customer acts — the enquiry, the call, the directions. If a full version is right we will say so, and quote what keeping both current costs.
Or look at what the work actually comes out like, project by project.
See the WorkNext
State, sector, and the words a customer would type before they found you. That is enough for us to say what the site has to be and roughly what it will cost.