How an organic baby brand turned a full day of work into a single hour

An organic baby brand had Claude but no real way to use it, manual work eating whole days, and its core data locked in a legacy system. We changed all three.

Full day → 1 hr

Weekly shipment process

10+

People now query the data

4

Manual processes automated

James Oldham·8 June 2026·6 min read·New Zealand retail case study
TL;DR

An organic baby brand selling across New Zealand, Australia and the UK had Claude but no real idea how to use it. Core processes ran by hand, and the data that ran the business sat locked in a legacy system called OnTempo. We architected their AI, automated four manual processes (a full-day weekly shipment job down to about an hour, plus merch planning, procurement and order management), and connected OnTempo to AI so 10+ people now query it in plain English and feed live data straight into their own workflows, all behind role-based access.

This is a premium, sustainability-led organic baby brand, clothing, nursery and care products sold across New Zealand, Australia and the UK, running on Microsoft 365 and SharePoint.

On paper they had AI: the team had Claude. In practice nobody knew how to use it, so the real work was still done slowly and by hand, and the data that should have powered everything sat locked in a legacy system the team could not actually talk to.

The problem

Why does a team with AI still do everything by hand?

Because the tools were never set up around how the team works. Claude sat untouched while core processes, shipment, merch planning, procurement, order management, ran manually. The weekly shipment process alone ate a full working day.

Underneath that, their operational data lived in OnTempo, reachable only by a person clicking through it. The numbers that ran the business across three markets were there, but out of reach for the people and the AI that needed them.

What we did

What did we actually automate?

We set Claude up properly, shaped around how the brand works, then went after the workflows quietly costing the team days.

Working hands-on with their operations lead, we took the weekly shipment process, a full working day, and rebuilt it with AI into roughly a one-hour job. From there we automated three more core processes: merch planning, procurement and order management. Four manual jobs, handed to AI.

How did we open up their locked data?

The unlock was the data. We built a custom server that pipes their legacy OnTempo data straight into AI, so the team can finally talk to their own information in plain English. We also stood up a Claude coworker architecture over their Microsoft SharePoint directory, so the documents and the data sit in one reachable place.

Now more than ten people query the data directly, and more than ten feed it live into their own workflows. A concrete example: the merch planning team pulls sales data straight from OnTempo into their existing workflow to automate the merch planning process, work that used to be manual end to end.

How is access kept safe across the team?

Giving a whole company access to its data only works if the right people see the right things. So we layered in a role-based access control system over their SharePoint directory: owners and admins set permissions for each staff member, so every person gets exactly the data they should and nothing they should not. Trust built into the design, not bolted on after.

The results

What was the return?

Manual processes automated4 (shipment, merch planning, procurement, order management)
Weekly shipment processa full day → ~1 hour
People now querying the data10+
People feeding live data into their own workflows10+
Markets unified3 (NZ, AU, UK)
Legacy OnTempo datanow conversational + ingestible
The result

A team that had Claude but never used it now runs four of its core processes on AI, queries its own data in plain English, and feeds live numbers straight into the workflows that run the business, across three markets and behind role-based access.

Your turn

Could this be your team?

If you are paying for AI your team barely uses, losing whole days to manual processes, or sitting on data locked in a system nobody can query, this is exactly the kind of problem we solve. We start with a Discovery Week: we find your single biggest win, scope it, and ship a first working piece fast, so you feel the value before any bigger decision.

Contact Us

Frequently asked questions

We already pay for AI but barely use it. Why would this be different?

That was exactly their starting point. The difference is we set the tools up around how the team actually works, automate the real manual jobs, and connect the data the work depends on. AI stops being a licence nobody opens and becomes part of the day.

Was it safe to connect our core data?

Yes. We connect to the systems you already run rather than moving your data somewhere new, and access is governed by role-based access control, so owners and admins set exactly what each staff member can see. It operates under the New Zealand Privacy Act 2020.

Do non-technical staff actually use it?

Yes. The whole point is plain-English access. More than ten people across merch, procurement and operations now query the data and pull it into their own workflows, no technical skill required.

Do we have to replace OnTempo or our other systems?

No. We built a custom server that connects OnTempo to AI, and a Claude coworker layer over your existing Microsoft SharePoint. You keep the systems you run; we make them reachable.

How is access controlled?

Through a role-based access control system on top of your SharePoint directory. Owners and admins set permissions per staff member, so the right people get the right data and nothing more.

Explore AI Development

More case studies