Last month we shared that FutureLab was going through a rebrand.
February was about bringing that vision to life.
Our new website is now live, reflecting not only a refreshed visual identity but a clearer way of explaining how we help businesses design and build their digital future.
It’s simpler, more focused, and designed around how real conversations with clients actually happen.
We’re Refining How We Grow
February at FutureLab Digital wasn’t about big launches or flashy campaigns.
It was quieter than that and more useful. We spent the month stress-testing our own systems: our remarketing funnels, our internal workflows, our assumptions.
Because growth isn’t only about reaching new audiences. It’s about building smarter infrastructure around the people already paying attention.
Here’s what that looked like in practice:
Testing Our Own Systems: Remarketing
We’ve been optimising how we remarket our own website visitors running ourselves through the same process we use with clients.
And we confirmed that visibility alone is not a strategy.
Done properly, remarketing it’s about re-engaging people who already showed interest with messaging that actually adds context and value.
We’ve been using our own website traffic to test and refine these systems the same way we would for clients.
Adjusting:
• messaging
• timing
• audience segmentation
• landing experience
Every experiment teaches us something new.
Building Shelly, Our Admin Assistant
We’ve been developing Shelly, our internal digital admin assistant, originally built to eliminate repetitive administrative tasks.
She’s become something more interesting: a live case study in operational reality.
Automation sounds straightforward until you’re inside it. Building Shelly forced us to rethink data structure, communication workflows, human handover points, and what accountability actually looks like at scale. Every challenge sharpened our thinking, not just about automation as a concept, but about how operational systems either support growth or quietly resist it.
Marketing strategy without operational infrastructure is a ceiling, not a launchpad.
The Friction Is the Lesson
There’s a meaningful difference between advising on digital systems
and building them yourself.
When you optimise your own funnels and stress-test your own workflows, you encounter the friction first-hand.
February reminded us that every bottleneck is an invitation to design something smarter and that the most useful insights rarely come from smooth execution.
They come from the moments things don’t work the way you expected.
Case Studies: Strategy to Implementation
We’ve recently documented several detailed case studies covering the strategic challenges, system redesign decisions, and measurable outcomes from recent client work.
The outcome isn’t just traffic growth; it’s competitive advantage. Today, the Auckland Eye website sits clearly ahead of many competitors in key search categories and visibility metrics
Before writing a single line of code, we listened.The project began with workshops, discovery sessions and a full technical and marketing audit. We were given access to repositories, analytics, infrastructure and internal tools. We reviewed GitHub history, deployment patterns, performance data, content workflows and API behaviour. Nothing was assumed. Everything was inspected
Looking Ahead
Moving into March, the focus stays the same:
- Build systems that scale.
- Design marketing that guides.
- Create futures with friends.
If you’re rethinking how your business captures, nurtures, or operationalises demand, we’re always open to a conversation.
