Web development services in Varanasi serve an unusual mix: hotels and operators selling to visitors on 3 continents, silk weavers and handicraft exporters shipping worldwide, and institutions with archives worth more than any homepage. Gatilab builds image-heavy sites that still load quickly abroad, and publishes starting prices before the first call.
Delivery is remote, with calls in IST. You keep the code, the hosting account, and every login in your own name.
Three patterns account for most of the web development work we take on in Varanasi. Yours may not be here, and that is what the scoping sprint is for.
Travelers compare across several tabs and decide on trust signals. Honest pricing, clear availability, and a booking flow that works on a phone in another time zone matter more than the photography everyone already has.
These catalogs live on photography, and photography is what makes them slow. Modern image formats at the right dimensions, plus a host or CDN near the buyer, are the difference between a gallery that sells and one people abandon.
Long-lived content needs a structure that survives 400 pages and the next administrator. That means real information architecture, accessible markup, and documentation, not a template chosen for its homepage.
Pick by how much of the build is genuinely unknown. Prices are in rupees and exclude tax.
For teams inheriting a site, taking over a stalled project, or deciding between a repair and a rebuild.
The fee comes off the build price if you go ahead with us.
For businesses whose site is the main sales channel and cannot afford another rebuild in 2 years.
If a rebuild is not warranted, we quote the repair instead and it is cheaper.
For stores where downtime, checkout friction, or stock errors cost money the same day.
If your volume does not justify a custom store yet, we say so and name a platform.
Development is delivered remotely, so location changes meeting times and payment method rather than price. Hosting is never resold, so leaving us never means moving your site.
The same table we work from internally. If a line is not ticked, it is not in the price, and we would rather you saw that here than found it in week 6.
| What you get | Scoping sprintfrom ₹27,000 | Custom buildfrom ₹72,000 | Ecommerce buildfrom ₹2,55,000 |
|---|---|---|---|
| Code, plugin, and database audit on the live site | Included | Included | Included |
| Written scope with assumptions and risks named | Included | Included | Included |
| Performance traced to the query or asset causing it | Included | Included | Included |
| Build estimate you can take elsewhere | Included | Not included | Not included |
| Performance budget agreed before the first template | Not included | Included | Included |
| Component system your editors can use without a developer | Not included | Included | Included |
| Staging environment your team reviews weekly | Not included | Included | Included |
| Redirect map crawled from the old site and tested | IncludedRisks named only | Included | Included |
| Before and after crawl at launch | Not included | Included | Included |
| Payments, stock, variants, and tax configured | Not included | Not included | Included |
| Load tested at the traffic you actually expect | Not included | Not included | Included |
| Launch runbook with a rollback path | Not included | IncludedBasic | Included |
| Documentation and every account in your name | IncludedAudit document | Included | Included |
| Post-launch monitoring for 2 weeks | Not included | Included | Included |
Taxes are extra and always printed. Every track opens with the scoping pass, because an honest build price depends on what is already there. If the audit shows a rebuild is not warranted, we quote the repair instead and it costs less.
Most engagements start with one and add the others once the first has paid for itself.
WordPress built as a real component system with version-controlled themes and purpose-built blocks, so your editors change pages without filing a ticket. No page builder sprawl, no 40 plugins holding the layout together.
WooCommerce stores scoped around the checkout rather than the catalog. Payments, stock, variants, and tax are settled before launch, because those are the parts that cost money the same day they break.
Dashboards, portals, booking flows, and internal tools. We scope the data model first and the interface second, which is the reverse of how most quotes are built and the reason ours hold.
Moving off Wix, Squarespace, Drupal, or an abandoned custom stack without losing rankings. Redirects are mapped from a full crawl of the old site, tested on staging, and shipped with the launch rather than after it.
Slowness has a cause you can point at, usually a query, an unbounded asset, or a plugin doing work on every request. We trace it to the line rather than installing another caching layer over the problem.
Updates, backups, uptime monitoring, and security patching on a schedule, with a named person who answers. Retainers are month to month, because a maintenance contract you cannot leave is a hostage situation.
Chosen because they stay maintainable for whoever comes after us, not because they are new. Most builds are the WordPress column. We reach for the JavaScript column when the front end genuinely needs it, and we say so when it does not, because headless roughly doubles what you have to maintain.
Overruns come from work nobody scoped. Every stage below produces an artifact you check before the next one starts.
We read the existing code, the database, and the hosting before quoting. Most of the risk in a rebuild is invisible from the front end, so pricing it without looking is a guess dressed as a number.
You leave with: a scope with the assumptions and risks written down
Everything is built and reviewed on a staging environment your team can reach. You see the site grow weekly instead of getting a reveal at the end and a week to react to it.
You leave with: a staging URL you can click through as it grows
Redirects are mapped from a crawl of the old site, tested, and shipped with the launch. This is the stage most agencies skip and the one most post-launch traffic losses trace back to.
You leave with: a redirect map plus a before and after crawl
We monitor errors, crawl stats, and Core Web Vitals under real traffic for 2 weeks. Problems surface when actual people use the site, not during internal testing.
You leave with: documentation, every account in your name, and a post-launch report
None of these are bundled into the headline price, because most projects do not need all of them. You see what each one costs and can decline it.
A component library with locked styling, so marketing assembles new pages from approved parts without a deploy and without drifting off brand.
Schema, crawl budget, internal link structure, and indexation checked before the site goes live rather than diagnosed 3 months later.
Events wired into the build against the real funnel, so you can tell which step loses people instead of guessing.
Translation workflow and correct hreflang. Priced separately because the cost sits in the workflow, not the templates.
Least-privilege access, 2FA, hardened file permissions, and a patch schedule. Standard on ecommerce, optional elsewhere.
Transactional email that actually arrives, plus the sequences that run after a form submission or an abandoned cart.
Development is where vague quotes do the most damage. Half of this list is reasons we turn Varanasi projects down.
Cost, timelines, rankings, hosting, and how engagements actually run.
Yes, and it changes the scope. Multi-currency, international shipping rules, customs documentation, and the payment methods your buyers actually hold are checkout architecture decisions, so they are settled during scoping rather than after launch.
Almost always, and usually without touching the design. Serving modern formats at correct dimensions, deferring offscreen images, and putting a CDN in front typically recovers most of the load time. That is a performance engagement, not a rebuild.
Published floors are ₹27,000 for a scoping sprint, ₹72,000 for a custom build, and ₹2,55,000 for an ecommerce store, plus taxes. The final number depends on template count, integrations, and how much of the existing stack has to survive the move. You get the assumptions in writing rather than a range.
A scoping sprint runs 1 to 2 weeks. A custom build is typically 6 to 10 weeks from kickoff to launch, and ecommerce runs longer because payments, stock, and tax need real testing. We quote a timeline against your actual scope and say early if a date is not achievable.
Not if the redirects are done properly, which is the part most rebuilds skip. We crawl the old site, map every URL, test the redirects on staging, and ship them with the launch, then run a before and after crawl so any loss shows up immediately.
Neither. We do not resell hosting, so leaving us never means moving your site, and maintenance retainers run month to month. The code, the hosting account, and the domain are in your name from day one.
Send the current URL, what is underperforming, and the 1 outcome the site most needs to produce. The more specific you are, the more specific the reply.
Prefer to talk first? Message us on WhatsApp. Budgets under ₹27,000 are better served elsewhere and we will say so rather than take the project.
