The hardest part of a care plan isn’t the work. It’s proving you did it.
Every month you log into MainWP, run the updates, check nothing’s on fire, and move on. Plugin updates, theme updates, the WordPress core bump that quietly patches a security hole nobody will ever thank you for. It’s real work: it’s the work that keeps a site from falling over, and it is completely invisible to the person paying for it.
So when renewal comes round and a client squints at their care plan and asks “what exactly am I getting for this?”, you’ve got nothing to point at. The traffic report shows visitors. It says nothing about the forty updates you applied to keep those visitors landing on a site that actually loads.
That’s the gap we’ve just closed. SendTidings now integrates with MainWP, so your monthly report can show the upkeep alongside the analytics, pending plugin updates, theme updates, WordPress core, all in the same branded email your client already opens. A report becomes a care report.
Why this matters
Agencies have sold care plans for years, and they’re a genuinely good deal for everyone: the client gets a site that keeps working, you get recurring revenue you can rely on. The problem has always been the optics. Maintenance is most visible when it fails. Do it well and it disappears. The site just works, and “the site just works” is a hard thing to invoice with a straight face.
Putting the maintenance in the report flips that. Now the client sees the plugins kept current, the core kept patched, the quiet diligence that’s the whole point of paying you a retainer. You’re not asking them to take your word for it. It’s right there, next to the visitor numbers, on the first of the month.
How it works
One connection covers everything. You connect your MainWP dashboard once, at the organisation level: not per client, not per site. If MainWP already manages thirty sites, SendTidings sees all thirty.
From there it matches each client site to its MainWP entry automatically, by domain. There’s no fiddly per-site mapping, no dropdown to wrangle for every property. If the domains line up — and they will — it just connects.
And then, deliberately, it does nothing until you say so. The maintenance section is off by default and opt-in per site. You choose which clients see it.
That last part is on purpose. For a client on a proper care plan, a tidy summary of everything you kept up to date is exactly the reassurance they’re paying for. For a client who isn’t (say, someone you built a site for two years ago and haven’t touched since) a section headed “pending updates” reads less like care and more like a nudge that their site is quietly ageing. Same data, very different message. So you decide, site by site, where it actually helps.
This is a v1
What’s shipping today is the maintenance overview: updates pending across plugins, themes and core. It does the most work for the least setup, which is why it’s first.
It’s also a foundation. MainWP surfaces a lot more than update counts: backups, security scans, uptime, performance. The plan is to pull more of it through over time, so the care report gets richer without you changing anything. Each addition will turn up in the changelog as it lands.
Switch it on
If you’re already running MainWP, this is about as low-effort as a new feature gets. Head to Organisation → Integrations, connect your MainWP dashboard, and flip the maintenance section on for the clients where it earns its place.
The work was always there. Now it shows up.
