Two teams. One Shopify admin. Someone always waiting.

Most website relaunches don't run late because of the design or the build. They run late because of the content.

The chatbot on your website disappears the moment a visitor closes their tab. Every conversation, every question, every potential customer. Gone. A WhatsApp Business chatbot doesn't work that way — and that difference is costing businesses more than they realise.

You've probably felt this without naming it. You install a web chatbot, customers ask questions, your team gets optimistic. Then you check the numbers. Most conversations end without a conversion.

Visitors who seemed interested just... stopped. No follow-up. No contact. No way to reach them.

This isn't a configuration problem. It's a structural one. Web chatbots are session-bound by design.

When the browser closes, the conversation ends. You have no record, no channel, no way to continue. You've lost them, and you don't even know who they were.

There's a better approach, and it's already on your customers' phones. A WhatsApp Business chatbot built on the right architecture does three things a web chatbot cannot: it persists across sessions, it continuously learns from your website content, and it connects to your CRM and ERP to deliver personalised responses at every stage of the customer relationship.

This article explains the architecture, the business case, and what a real NZ implementation looks like in practice.

Your team chose Contentful for the flexibility. Then they discovered that every content change still goes through a developer.

That's not a Contentful problem. It's an implementation problem—and it's more common than it should be. The platform itself is built for structured, scalable content management. But without the right editing layer on top, marketers end up navigating a field-level back-end that wasn't designed for day-to-day publishing. Developers get pulled into work that shouldn't need them. Content updates queue up. Campaign launches slip.

Contentful no-code editing closes this gap. When the implementation is built correctly, and the right app layer is in place, Contentful for marketers becomes what it should have been from the start: a platform where your team can edit pages from the front end, restructure layouts, run SEO audits across the entire site, and publish—all without touching a developer or raising a ticket.

This article explains what that looks like in practice, using Octana, Apolinar's Contentful editing app—the editing layer Apolinar configures as part of every Contentful implementation.

If you’ve hit Contentful’s content type limit, the platform isn’t the problem. Your content model is.

That’s a frustrating thing to hear when you’re staring at an error message and a deadline. But it’s almost always true. Teams that design their content model architecturally, before any types are created, rarely come close to the limit. Teams that build reactively, adding a new type for each new campaign, page template, or feature request, hit the wall eventually.

Contentful content type limits exist, and understanding them matters. But the more useful question is why you’re approaching the limit in the first place. In our experience, a structured two-day audit typically takes a bloated implementation from 40+ types down to under 20 — without deleting a single piece of content. And most teams then stay within their existing plan.

This guide covers the actual limits by plan, the patterns that cause content type bloat, and a practical approach to auditing and reducing your count without losing content or breaking your site.

Most New Zealand businesses running Zoho are getting about 30% of its value. The other 70%? Locked behind a wall their website has never heard of.

If your Zoho CRM holds hundreds of contacts but your website sends form submissions into a spreadsheet, you have two systems pretending to be one. Your marketing team builds campaigns based on email opens, not the three blog posts that prospect read last week. Your CRM records have no idea what your leads are actually doing online.

This is the Zoho CRM integration problem that most New Zealand businesses haven’t solved yet, not because the technology doesn’t exist, but because nobody has owned the architecture between the CRM and the website.

This guide covers what genuine Zoho CRM integration looks like, the three levels most NZ organisations work through, and what a properly connected platform achieves in practice. Whether you’re evaluating Zoho for the first time or trying to get more from a system you already have, here’s what you need to know.