You have agreed to hand your website’s upkeep to a team in another country. The payment is sorted, the welcome email has arrived, and now there is a quiet gap. Nothing visible happens. You wonder whether to chase, whether you should have sent something, and what “getting started” is supposed to look like. The first 30 days of a website maintenance plan are the stretch where good habits are set or missed, and a bit of preparation on your side makes a large difference to what you get afterwards.
What follows is a general yardstick for a sensible first month with any provider, aimed at owners abroad who have never done this before. Use it as a yardstick for whoever you hire, including us.
Why the first month is not a normal month
Once a plan is running, a month is routine: updates, backups, security checks, a few content changes, a report. The first month is different because the provider is learning your site as well as caring for it. Nobody knows yet which plugin is fragile, which page earns the most enquiries or which form feeds which inbox. The work is investigation as much as maintenance.
Searching for a maintenance team in India turns up many plan pages that look alike, and the differences only show once the work starts. Our page on India-based maintenance lists what that kind of monthly plan covers, so you have something to compare the early weeks against. If your first month feels very different from what was described, ask why.
Before day one: what you can prepare
The fastest way to slow a first month down is to make the provider wait for logins and decisions. A little homework helps:
- Gather the access. WordPress administrator login, hosting, domain registrar, and any tools tied to the site such as analytics, email delivery or a CRM. Create a separate account for the provider, rather than sharing yours. There is a short guide to how to hand over access without sharing your own password.
- List the pages that matter. The three or four that bring in enquiries or sales: the home page, one main service page, your contact page and, for a shop, the checkout.
- Write down what worries you. A form that sometimes fails, a slow page, a plugin you no longer trust. Those go on the provider’s list from day one.
- Name one decision-maker. If three people can approve changes, the provider will wait for the slowest of them.
- Say what you are about to change. A redesign, a new payment provider or a campaign launch next month all affect how cautiously updates should be handled.
The first 30 days of a website maintenance plan, week by week
Week one: access and a safety net
The opening days should be about establishing control and safety, not changing anything. Expect questions rather than activity you can see. A careful provider will:
- Confirm they can log in and that each login works as intended.
- Take a full backup of files and database before touching anything, and store it away from the web server.
- Note the current versions of WordPress, the theme and every plugin.
- Set up uptime monitoring, so someone is told if the site stops responding.
- Ask who to contact, how, and what counts as urgent.
You should receive a short message confirming what has been set up. If a week passes with no contact at all, send a polite question. Silence at this stage is not a good sign.
Week two: an honest look at what is there
Now the provider reads the site rather than changing it. The useful output is an inventory and a list of findings. That usually covers plugins that are out of date, abandoned or duplicated; the PHP version on the hosting account; whether backups on the host work as claimed; the security scan result; the speed of your key pages; and whether the forms deliver mail.
Expect the findings to include things you did not know. Most sites have some. What matters is how they are presented: clear, in plain language, ranked by importance, with the risky items separated from the cosmetic ones. A message full of jargon and no priorities is a poor start.
Week three: the first round of updates
With a backup in hand and a baseline recorded, the provider can begin the first update cycle. The first round is often the largest, because a neglected site has a backlog. A sensible approach is to work in stages, checking the important pages and forms after each stage rather than updating everything at once. If a staging copy exists or can be made, it should be used for the risky ones.
This is also where you may be asked a question: a plugin might be abandoned and need replacing, or a theme might be too old to update without changing how the site looks. Replacing something is not routine upkeep, and you should be told that before it happens.
Week four: the first report and a conversation
By the end of the month you should have a written summary of what was done and what was found. A monthly maintenance report worth reading names things rather than summarising. Read it for specifics: which items were updated, what the scan showed, how long the site was reachable, what was left alone and why.
A short call or message exchange to go through it is worth more than the document alone. Ask what worries them about the site, what they would do next, and what should wait.
What you should have in writing by day 30
At the end of the first 30 days of a website maintenance plan, these should exist on paper, not just in a conversation:
- A list of what is covered each month, and what is not.
- The limit on content changes included, and how extra requests are quoted.
- Who holds the logins, backups and licence keys, and where the backups are stored.
- The agreed way to report an urgent problem, with the channel named.
- How to pause or cancel, and what you receive if you do.
If any of these were vague at the start, now is the time to tidy them up. Our website maintenance proposal checklist is a good way to compare what was promised with what you are getting. Keep the agreed details in one place that more than one person on your side can find.
Working across time zones in month one
With a team in India and your business in another continent, the working days overlap only partly. That is perfectly workable, but the first month is when you discover how. Decide early which messages are urgent and which can wait for the next working day, and prefer written requests that contain everything needed, so nobody waits half a day for a missing detail. A screenshot, the page address and a sentence on what you expected will save a round trip. The practical side of working across time zones with a team in India has a post of its own.
Warning signs worth noticing early
Onboarding a website maintenance provider rarely goes perfectly, but certain things are worth noticing in the first 30 days of a website maintenance plan, because they tend to continue:
- Nobody asks for a backup or mentions one in the first week.
- The provider wants your own administrator password rather than creating a separate login.
- Updates are applied to the live site on day one with nothing recorded beforehand.
- Reports say only that everything is fine.
- Questions about what is covered are answered with reassurance rather than specifics.
- Pressure to buy extras before the first report has arrived.
One of these on its own is a reason to ask a question, not to leave. Several together are a pattern.
How to tell whether the month worked
You do not need technical knowledge to judge this. Ask yourself a handful of plain questions on day 28 or so:
- Do I know what the site runs on, and what was found that needs attention?
- Could I explain to a colleague, in two sentences, what the provider does for us each month?
- Did anything I asked get done, or at least answered, in a way I could follow?
- If the provider disappeared tomorrow, do I hold the logins, the backups and a list of what is installed?
- Do I trust the report, meaning that it names things rather than saying everything is fine?
If most answers are yes, the plan has started well, even if the site looks exactly the same as it did. Much of good maintenance is invisible by design. If most are no, say so in writing and ask for a plan to put it right before the second month begins.
Mistakes owners make in the first month
Providers get blamed for plenty that starts on the owner’s side. The usual ones are sending logins late, approving changes slowly, mixing small tasks and large requests in one message, and expecting redesign-level work from a maintenance plan. Another is asking for new content changes in the same week the first update cycle is running, which makes it hard to tell what caused a problem. Keep your own edits modest while the first updates are in progress, and tell the provider if you make any.
The other mistake is treating the first month as a test the provider must pass in silence. A sensible start is a conversation: you share what you know, they share what they find, and by day 30 you both have a clear picture of the site and of each other.
If you would like to see how an ordinary monthly routine is organised before you commit anywhere, the WordPress monthly maintenance page sets it out without pressure, and you are welcome to ask us anything it does not answer.
Next in this series: What Website Maintenance Plans Do Not Cover
