We build, maintain, and rescue WordPress sites for businesses in 102 Indian cities, with real developer hours attached instead of a plugin that emails you after something already went wrong. Gaurav has been building on WordPress since 2008 and contributes to WordPress core.
“We are scared to run updates.”
Updates belong on a staging clone with a visual diff, not on production at 2am. See care plans
“We need a custom feature the plugins do not do.”
That is plugin work, and it is scoped separately from a site build. See custom development
“Our site was built by someone we can no longer reach.”
We take over inherited sites, starting with an audit that is honest about what we find. See how takeover works
“I want the page for my city.”
Every city we cover has its own page. Open the city index
These figures cover every Gatilab service, not this one alone. We’d rather say that plainly than imply a per-service record we haven’t published.
Brands we’ve delivered work for
Maintenance, custom development, and platform work are priced separately because they are genuinely different jobs with different risks.
For business sites that need someone watching but rarely change week to week.
One site · 48-hour response
If an update breaks the site, we roll it back and fix it at no extra cost.
For teams whose workflow needs a real feature rather than five plugins stitched together.
Custom plugin · scoped per feature
If an existing plugin already does it well, we will tell you and save you the build.
For multisite networks, integrations, and sites where the architecture itself is now the problem.
Architecture and integration work
We will say plainly when the honest answer is a rebuild rather than more patching.
WordPress work is delivered remotely and quoted in dollars, matching the published rates on the maintenance and plugin development pages. We do not resell hosting, so leaving us never means moving your site.
Inherited WordPress sites hide their problems well. Every stage below produces something you can check rather than trust.
Week 1
Plugins, PHP and WordPress versions, existing backups, and everything installed then abandoned. Most sites we take over are running at least one plugin nobody remembers adding.
You leave with: a written inventory and the risks ranked.
Weeks 1 to 3
Staging, version control, and a tested backup come before any feature work. Without them, every later change is a gamble taken on your live site.
You leave with: a staging environment and a restore you have watched work.
Scope dependent
Features get built as proper plugins and fixes get made in code rather than in a settings panel, so a theme update cannot quietly undo them.
You leave with: code in your repository, documented and reviewable.
On delivery
Access, documentation, and the reasoning stay with you. We are deliberately easy to leave, because that is the only version of this that is fair.
You leave with: ownership of everything, in your accounts.
WordPress work attracts vague retainers. Half this list is reasons we say no.
Each city has its own page covering what businesses there typically need. Filter to find yours.
No city matches that search. Try a shorter word, or tell us where you are and we will say whether we cover it.
WordPress work is delivered remotely, so the index shows where we have written a local page rather than where we can work.
Something not covered? Ask directly and you will get a straight answer, not a calendar link.
No, deliberately. Bundling hosting means leaving us also means moving your site, which is a lock-in dressed up as convenience. You keep hosting in your own name and we work inside it.
Updates run on a staging clone first and get visually compared before they touch production. If something still breaks, we roll it back and fix it without an extra invoice, because that is the job you paid for.
Yes, including Bricks and GenerateBlocks, and Gaurav has been a Bricks expert. We will tell you when a builder is the reason a site is slow, but we are not precious about it.
Usually yes, and that is most of what we do. The audit comes first and it is honest, including when the honest answer is that rebuilding costs less than untangling.
Yes. Custom work is delivered as a proper plugin in your repository, documented, with no license check phoning home to us. You can hire anyone to maintain it afterwards.
Usually yes. WordPress work is delivered remotely, so the index below shows where we have written a local page rather than the limit of where we work.
Send the URL and whatever keeps you up at night, whether that is an ancient plugin, a backup nobody has tested, or a form you are not sure still works. You will get a straight read on what needs doing and what does not.
