Per site
Its own reading of the website
Each client site is analysed separately — its services, its wording, its town. A Te Awamutu electrician and an Auckland dentist come out sounding nothing alike, because the source material is nothing alike.
For web designers & agencies
Keep client websites alive after launch, without hiring a writer
You built them something good. Then it sat there. Blog Lab lets you add real content to a maintenance plan without it becoming a job you do at eleven at night.
The awkward gap in every maintenance plan
Most web design businesses in New Zealand end up in the same spot. You sell a build, you sell hosting, and then you sell a maintenance plan that is mostly updates, backups and the occasional text change. It is fine money. It is also the plan that clients cancel first, because from where they sit, nothing visible has happened for a year.
Meanwhile the client keeps asking a version of the same question: why is the site not bringing in more work? And you know the answer. The site says the same eight things it said at launch. Nobody new has a reason to find it. The pages that could pull in traffic — the specific, awkward questions people actually type — were never written, because writing them was never in scope.
Content is the obvious upsell and almost nobody sells it, because the economics do not work. A copywriter costs $250 to $600 a post. Writing it yourself means twelve hours a month you cannot bill. Handing the client a login and telling them to blog produces exactly nothing, every time, and you both know it.
What changes when the writing costs a few dollars
Once a researched, properly linked post costs a few dollars instead of a few hundred, content stops being a separate project and starts being a line on the plan you already sell. Four posts a month on a client site is a visible, obvious, monthly reason the plan exists. It is also the thing that makes the hosting sticky, because now there is something running.
What matters is that the posts are actually different from each other. If you look after twenty sites, the fastest way to lose all of them is twenty near-identical articles with the business name swapped out. That is the specific thing Blog Lab is built to avoid, and it is worth understanding how.
How it works across a client list
Every site is treated as its own business
Nothing is shared between client accounts except your login. The research, the tone and the linking all start again from each website.
Per page
Its own link target
You choose which page each post should send readers to. For most clients that is the service they most want more of, which is a much better conversation to have with them than "what should we blog about".
Per month
Its own click report
Views and click-throughs by city for each site. That is the slide that keeps a maintenance plan alive, and it takes you ten seconds to pull rather than an afternoon in an analytics dashboard.
Getting it onto their site
Two options, depending on how much you want to touch the client's site
Option one
Export and paste
Take the post as HTML or Markdown and put it in wherever they publish. Headings, links and formatting survive the trip. Works with WordPress, Webflow, Squarespace, Shopify, Craft, or the CMS you built them yourself.
Best when the client wants the content genuinely inside their own site, or when you are handing them a plan they might one day take elsewhere.
The WordPress version of thisOption two
One line of embed code
Drop a single script tag onto a page once. Every post you approve appears there automatically, styled to fit. No plugin to keep updated, nothing that breaks when the theme changes, and no reason to log into their site again.
Best when you look after a lot of sites and do not want a monthly publishing chore multiplied by twenty.
See the whole process
The numbers
What this looks like on a plan you already sell
We are not going to tell you what to charge. But here is the input cost, so you can work out whether it fits what you charge now.
Trying it
$3 a post
Buy a handful, put them on one client site, and see what the client says before you rewrite your maintenance plan. This is how we would do it.
A few client sites
$300 a year
The Growth plan is 12 posts a month. Spread across three client sites at four posts each, that is a few dollars a post — and 144 posts across the year.
A real client list
$600 a year
Pro is 26 posts a month, which covers six or seven client sites publishing monthly. At that point the cost per site is smaller than the hosting.
All figures in New Zealand dollars. Full breakdown on the pricing page, and NZDH clients get 20% off.
Where this is the wrong tool
We would rather say this on the website than three weeks into a subscription.
If your clients are large enough to have a marketing manager and a brand voice document, they need a copywriter and you should sell them one. If a client's whole business depends on being the definitive authority in a narrow field, the flagship pages should be written by a human who knows that field. Blog Lab is very good at the twenty supporting articles around those pages. It is not a replacement for the two that matter most.
And if a client's website is slow, unclear about what they sell, or missing an obvious way to get in touch, adding a blog will not fix any of that. Fix the site first. That is a build, and you are already the person who does builds.
Where it works is the long middle: the client who is good at their trade, has a decent website, and has published nothing since launch. There are a lot of those, and they are all wondering why the phone is quiet.
Agency questions
What people building sites for a living ask us
Is it white label?
The content is yours, with no attribution required, and nothing in the exported post points back to us. Your client sees a blog post on their website. There is no badge, no footer credit and no link home.
Can I manage several client sites from one account?
Yes. Each site is analysed and researched separately, and posts stay grouped by the site they were written for. If you would rather keep clients in genuinely separate accounts, talk to us and we will sort out a sensible arrangement.
Will twenty client sites end up with the same posts?
No, and this is the failure mode we designed hardest against. Topics come from each site's own research, aimed at each site's own pages and towns. Two clients in the same trade in different towns will get genuinely different articles.
Should I tell the client it is written with AI?
That is between you and them, but we would tell them. Most clients are relieved that their blog is finally moving. Being straight about it also lets you have the more useful conversation: that you are the one choosing the topics, checking the facts and pointing the links.
Do I have to edit every post?
You should read them. Whether you change anything is up to you — most people adjust a paragraph and publish. What you should never do is publish twenty posts unread across twenty client sites, for the same reason you would not push code you had not looked at.
Who is behind this?
NZDH Ltd in Hamilton — a web design and hosting company, which is why the tool is shaped the way it is. We hit this problem on our own client list first. More about that here.