Most people who search for a WordPress developer in India have already made the big decision. They have weighed hiring locally, tried a marketplace or two, and settled on working with a team in India. What is left is the harder part: finding one that does careful work, writes things down and does not disappear halfway through a job. This page is about that part, and about how we work with owners in the US, the UK and elsewhere.
What you can hire us for
We are a small WordPress team based near Kolkata. The work falls into four kinds, and it helps to know which one you need before you ask anyone for a quote.
- A fix. Something is broken or wrong: a form that no longer sends, a layout that collapsed after an update, a checkout error. This is quoted as a single task, usually after we have looked at the site. Our WordPress bug fixing service covers this in detail.
- A project. A new site, a redesign, a custom plugin or a set of new pages. It is scoped in writing first, with what is and is not included, and then priced. See website development and custom plugin development.
- Monthly care. Updates with a backup before each one, checks afterwards and a written report. This is our website maintenance service, and it is the same plan whether you are in Ohio or Kolkata.
- Ongoing capacity. A regular block of developer time each month for a list of tasks you keep adding to. This suits owners who always have something waiting and do not want to brief a new freelancer every time.
How the work runs when you are not in India
The time difference sounds like the main problem. In practice it rarely is, provided the work is set up to run in writing. You describe what you want in an email or a WhatsApp message, with screenshots or a short screen recording if it is visual. We reply with questions, then a written scope and a price. Nothing starts until you have said yes to that scope.
Indian Standard Time is 9½ to 10½ hours ahead of New York and 4½ to 5½ hours ahead of London, depending on daylight saving. For a US owner, that often means a request sent in the afternoon is looked at while you are offline, and the notes are waiting the next morning. When a conversation is quicker than a thread of messages, we agree a time for a video call that suits both sides.
Our post on how to brief an outsourced developer shows what a good request looks like. It is written for agencies, but the same habits save an owner a lot of back and forth.
Access, ownership and your data
Hiring a developer you will never meet in person means trusting them with your site. You should not have to trust blindly. The arrangement we use keeps control with you at every stage:
- The hosting, the domain and any premium plugin licences stay in your name. We do not move them into accounts of ours.
- We work through a WordPress login you create for us, and hosting or SFTP access only where the task needs it. You can remove that access the moment the job is done.
- Before changes on a live site, a backup is taken. If something goes wrong, the site can be put back as it was.
- Customer details, orders and form entries are only looked at when the task requires it.
If you have not handed a site to a developer before, how to give a developer access to WordPress walks through creating a separate account you can delete later, rather than sharing your own password.
Paying from the US, the UK or elsewhere
Every job is quoted in writing before work starts, so you know the figure in advance. Clients outside India pay by PayPal or Wise, and the details are on the invoice. For monthly maintenance, our Growth Care plan is a set $100 a month or $1,000 a year outside India, rather than a currency conversion of the rupee price. Other work is priced once we know the scope, because a one-line CSS fix and a WooCommerce rebuild are not the same job.
How to judge any Indian WordPress developer, including us
There are good developers in India and there are poor ones, just as there are anywhere. A few checks separate them quickly:
- Ask for a written scope. A developer who quotes without asking what the site runs, who hosts it and what “done” looks like will be guessing.
- Start with something small. A real fix you need anyway shows how someone communicates, how careful they are and whether they finish. Our post on a paid test task explains how to set one up fairly.
- Notice how they handle access. Asking for your main admin password, or for hosting credentials on a simple content change, is a warning sign.
- Look for plain answers. “I do not know yet, I need to look” is a better reply than a confident promise before anyone has opened the site.
The article on offshore developer red flags goes further, with the patterns that usually come before a project goes wrong.
When we are not the right choice
We only work on WordPress and WooCommerce. If your site is on Shopify, Wix or Squarespace, or it is a custom application built on another framework, someone else will serve you better. We are also not the answer if you need a developer to sit in your office or attend meetings at fixed hours in your working day. And if you run an agency and want help delivered under your own brand, the WordPress outsourcing for agencies page explains how that arrangement differs.
If none of that rules us out, send a short description of the site and what you need. You will get questions back, then a written scope and a price, and you decide from there.