Roadmap update

Hi.

We’re both back to share some exciting updates about our roadmap progress this quarter and what’s ahead over the next six months. Remember, you can catch all our past roadmap updates and product demos on our Squiz Global YouTube page, so make sure you check that out.

Before we dive in, I thought it would be useful to explain what drives Squiz’s product direction. From my perspective, we’re here for the teams who own the vision and accountability for digital customer experiences—marketers, comms managers, content creators and editors, and digital leaders.

To be successful, teams like mine need to build high-performing site experiences. That means spinning up campaign pages quickly, running experiments, optimising for what works, personalising content, and maintaining brand control—no matter who is editing.

But today, that’s not the reality. Personalisation is a great example. I’ve lived this in previous roles—teams often end up creating workarounds or avoiding it altogether because it requires too much developer support. When time and resources are limited, we settle for a basic MVP that falls short of the original vision. Then, once it’s live, it often stagnates.

We talk about this a lot at Squiz. Teams like mine want to go from idea to live experience without being stuck in developer backlogs. Developers are essential, but they should focus on strategic, complex work—not day-to-day content changes. The delays impact performance and, frankly, reputations—and we hate that.

It feels like the industry has failed marketers and digital leaders in this space. But I know we’re heading in the opposite direction. Julie, can you unpack how Squiz is addressing this in our roadmap?

Julie: What really keeps us up at night is this question—how can marketers create great content quickly, make it discoverable, test and optimise continuously, and enable users to take action seamlessly, all without relying on developers?

Right now, bringing ideas to life often requires handing them over to developers. But we believe creating and refining digital experiences shouldn’t depend on that. CMS and DXP platforms let you create content, but how do you know if it’s working? Are users finding it useful? Are you achieving your goals?

To answer those questions, teams need analytics, personalisation, and optimisation tools—but integrating those often brings you back to developer dependency. The industry hasn’t solved this problem. It doesn’t empower vision holders to build and optimise experiences as intended.

We hear this from every customer we speak to, and we see it as a critical problem to solve. Our roadmap is focused on changing that.

Mei: So essentially, our DXP is designed to reduce reliance on developers for day-to-day experience creation and give control back to marketers and digital teams.

Some might say, “Why not just use WordPress, Webflow, or Wix?” But our customers aren’t running simple brochure sites. They manage complex ecosystems—multiple sites, large volumes of content, multiple audiences, transactional services, and regulatory requirements.

We’re aiming to make that complexity easy to manage. That’s not something most platforms focus on—is that fair to say?

Julie: Absolutely. We don’t see many others tackling this problem, but it’s one we see everywhere.

Mei: Let’s talk specifics. Last quarter, we discussed integrating AI into the DXP. What progress have we made?

Julie: We’ve now defined our AI vision—an intelligent DXP that supports both content creators and end users.

For creators, that means generative AI tools to quickly produce and refine content. For users, it includes conversational interfaces like chatbots.

We think of AI as “creation magic”—but the real value is how that output is applied in a seamless, secure, and usable way within digital experiences.

Starting with search—our existing capability already uses AI-driven ranking. Now, we’re expanding with automated synonym generation, launching in October. This removes the need to manually map terms like “solicitor” and “attorney” or “trekking” and “hiking,” improving accuracy while reducing effort.

We’re also introducing vector search, which focuses on understanding intent rather than exact keywords. For example, instead of needing to search “cactus care,” a user could search “how to look after drought-resistant plants” and still get relevant results. This will be available in February.

We’ve also released two AI-powered features for early adopters. First, content rewrite tools that help maintain brand voice and adjust readability levels—for example, ensuring content meets a specific reading age.

Second, chatbots that allow users to ask natural language questions directly on your site, helping reduce call centre load and guide users more efficiently.

These capabilities support our broader vision—helping users reach the right information and outcomes with minimal friction.

Mei: That’s a lot of progress—and clearly more to come. What can we expect in the next six months?

Julie: One major focus is enhancing the visual page builder. We’re introducing inline editing, so you can edit content directly on the page without switching between views. This makes content creation faster and more intuitive.

You’ll also be able to preview personalisation and A/B test variants in real time, making it easier to optimise experiences on the fly.

In search, we’re redesigning the curator tool into a visual, drag-and-drop interface. This will allow non-technical users to control search behaviour—promoting content, adjusting results, and personalising experiences—without complexity.

Another key feature is user journey mapping. Unlike traditional analytics tools, this focuses on conversions and outcomes—such as applications, payments, or requests.

You’ll be able to track where users succeed or drop off, analyse behaviour across devices and pathways, and identify friction points. This provides actionable insights to improve your digital experiences.

Mei: It’s clear the roadmap is about empowering marketers and digital teams to work independently.

We’re making editing faster within a single interface, enabling real-time personalisation previews, simplifying search configuration, and introducing goal-driven journey insights.

These improvements make the reduction in developer reliance very tangible—and as an internal user, I can say I’m excited to get my hands on these.

Finally, as we always say at Squiz, nothing we build is theoretical—we solve real customer problems. Julie, how can customers contribute to the roadmap or get involved in beta programs?

Julie: We love feedback. Customers can reach out via email at ask@squiz.net or use the feedback tools in the DXP console or MySquiz support portal. Feedback goes directly to the product team.

We’re always looking for early adopters and beta participants, so we’d love to hear from you.

Mei: That’s a wrap. Thanks again, Julie—and to everyone watching, have a fantastic week ahead.

Thanks, May.