Nature Baby

How we migrated 7 different departments into Claude for Nature Baby

An organic baby brand selling across New Zealand, Australia and the UK had Claude seats and almost nothing to show for them. Seven departments, from finance to the shop floor, now run their day-to-day work through a skills library they own, and a weekly eval keeps it getting better.

Nature Baby skills library case study

50+

Skills deployed and counting

40+ hrs

Saved per week

12

Data connections into Claude

James Oldham·8 June 2026·7 min read·New Zealand retail
ClaudeMicrosoft 365SharePointOutlookExcelTeamsShopifyXeroAirtableAsana

TL;DR

Nature Baby runs on Microsoft 365 and Claude. In August 2026 we built the harness over the top: their usage data switched on, their real workflows captured and written as skills, one plugin that puts more than fifty of them on every seat, a wiki of how the business runs that Claude reads as a connector, and a weekly eval that reads the telemetry and ships fixes as pull requests. Legacy data in OnTempo and Zentempo is reached through connectors in the same repository. Ten people were active in the last week, across finance, product, merchandising and operations, and the whole thing is owned by Nature Baby.

What they were paying for

Nature Baby is a premium organic baby brand: clothing, nursery and care, sold across three markets on Microsoft 365, SharePoint, Shopify and a retail warehouse called Zentempo. The company had bought Claude seats. Like most teams that do, a couple of people got good at it and nobody could say whether it was doing anything.

The first thing we did was switch on the usage data. In the first week it showed that eight of thirteen seats had been opened, one person was two thirds of the usage, and five of the eight active people had used it on exactly one day. That is not a training problem. Nothing had been built, so everyone started from a blank box and got a different answer.

What we installed

Two things land in their Claude organisation, both set up once by their admin, the same two we install for every business on the AI Operating System. A plugin that puts the team's workflows on every seat as skills, and a Brain connector that sits in the connector list next to Shopify and Xero. Those connect Claude to their systems. The Brain connects it to the company: how they actually run, what a trade pack is, which report the board reads.

PieceAt Nature Baby
Skills librarylive50+ skills across seven departments, one plugin on every Claude seat. On its 99th release since August.
BrainliveTheir operation as a wiki, in their repo, served to Claude as a connector next to Shopify and Xero.
Roles and accessliveRole-based access over their SharePoint directory. Finance data stays with finance.
Approval gateliveRead is open across twelve systems. A write waits for a person.

The skills

50+

Skills deployed

25

Used in the last month

13

Used in the last week

2

Run every working day

Forty-five of those are in the library we maintain, and five more the team wrote themselves and run every day. The library is written from watching the team, not from a workshop. The person who does the job runs it once with a capture skill watching, and the method comes out as a skill file: the steps, the systems, the checks, and what to do when Zentempo times out.

sales-reconciliation

Finance · month end

Ran for the first time on 3 September: thirty steps across Zentempo and Xero, zero failures. The first month-end skill to fire, and the one their finance lead had been doing by hand.

ZentempoXeroXeroExcelExcel

outlook-email-triage

Product · every working day

Their head of product opens with it every morning. The weekly sales report follows on Monday. That is what a habit looks like in the telemetry: the same skill, the same seat, the same hour.

OutlookOutlookSharePointSharePointAsanaAsana

agent-commission-report

Finance · captured, then fixed

The finance lead ran the monthly agency commission workbook once, with a capture skill watching. The review before it shipped found two defects nobody had seen: a check column that is zero by construction, and a match key that can silently double one agent's base. Both are now in the skill.

XeroXeroExcelExcelSharePointSharePoint

The rest cover a whole retail year: the season critical path, trim ordering, landed-cost allocation, the board report, Klaviyo reporting, the sell-through report, print performance, staff onboarding. Each one reads from the systems it needs, and nothing else.

ZentempoOnTempoShopifyShopifyXeroXeroKlaviyoAirtableAirtableOutlookOutlookSharePointSharePointExcelExcelTeamsTeamsOneDriveOneDriveAsanaAsana

Seven departments, one library

Each department got the skills for its own jobs and the connections those jobs need, and nothing else. The finance seats reach Xero; the design seats do not.

FinanceMonth-end reconciliation, agency commissions, freight and 3PL charges
XeroXeroZentempoExcelExcel
ProductEmail triage, the season critical path, trim ordering
OutlookOutlookSharePointSharePointAirtableAirtable
MerchandisingSell-through, promo planning, stock on hand
ZentempoExcelExcel
MarketingKlaviyo reporting, web analytics, new-release performance
KlaviyoShopifyShopify
Design and printPantone recolours, colourway batches, the print library
SharePointSharePointOneDriveOneDrive
LogisticsInwards and shipping, cross-dock tracking, the shipment schedule
OnTempoExcelExcelOutlookOutlook
LeadershipThe board report, the executive summary, store KPI targets
ZentempoTeamsTeamsExcelExcel

What the loop found

Every week a judge reads the telemetry and writes the eval: what loaded, what failed, what nobody touched, and what to change. It opens the pull request itself. A person merges it, and the next release reaches every seat.

One finding from the 7 September eval. Queries against the Zentempo warehouse that described the table first failed fast on 21 of 200 requests. Queries that skipped that one call failed on 37 of 112, three times the rate for skipping a 300 millisecond step. The reporting skill now makes it mandatory. That is the kind of thing nobody notices while doing the work and something reading it cold cannot miss.

Another, smaller. The documents skill was barely loading. Its description was rewritten on 1 September in the words people actually type. A week later it was the most loaded skill in the library, from six seats.

What Nature Baby owns

One repository, in their name. In it: the skills library, the wiki of the operation, the connectors to OnTempo and Zentempo, the outcome register, and every weekly eval since August. Versioned like software, owned by the company, in their tenant. Models will change and staff will move on. The library keeps compounding, and a competitor can buy the same Claude seats but not the architecture built around how this team works.

The result

A team that had Claude and no way to use it now runs month end, the weekly trade pack, email triage and the board report through a library of its own workflows, on every seat, with a weekly eval that ships the fixes. Ten people active in a week, twelve systems reachable in plain English, all of it theirs.

The custom development underneath

Some workflows need more than a skill file before Claude can run them, so alongside the library we did the custom development necessary to enable them. Two pieces did most of the work. A custom flat lay image generation process, so the product and marketing teams turn a garment into a finished flat lay image from inside Claude rather than through a photographer and a retoucher. And a VPS that connects their legacy database to Claude, so the operational data that used to live in OnTempo, reachable only by a person clicking through it, can now be queried in plain English from any seat. A second connector does the same for the Zentempo warehouse. Before the library existed, the operations lead reported the weekly shipment process going from a full day to about an hour on the back of that database connection.

Could this be your team?

If you are paying for Claude your team barely uses, or your best person's way of working lives only in their head, this is the problem we solve. We start with a free AI Opportunity Audit: enter your company, connect the tools you already pay for, and see your three biggest opportunities mapped before you spend a dollar.

Frequently asked questions

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

That was Nature Baby's starting point. When we switched the usage data on, eight of thirteen seats had been opened in the previous week and one person was two thirds of the usage. Nothing was built, so everyone started from a blank box. The difference is the harness: their workflows as skills on every seat, their operation as a wiki the assistant reads, and a weekly eval that fixes what failed.

What is a skill, exactly?

A folder, not a saved prompt. It says what the job is, how Nature Baby does it, which systems it reads from, and what to do when one of them fails. The month-end reconciliation skill is thirty steps across Zentempo and Xero. A release puts it on every seat at once.

Who owns the skills and the wiki?

Nature Baby. They live in a repository the company owns, versioned like software. If we walked away tomorrow the library, the wiki and the eval history would stay exactly where they are.

Was it safe to connect our core data?

We connect to the systems they already run rather than moving data anywhere. Access is governed by role on top of their SharePoint directory, credentials are read-scoped, and any action that changes a record waits for a person. It operates under the New Zealand Privacy Act 2020.

Do non-technical staff actually use it?

Ten people were active in the last week, across product, finance, merchandising and operations. Nobody writes a prompt from scratch: they open Claude and the skill for their job is already there.

Do we have to replace OnTempo or our other systems?

No. OnTempo and Zentempo are connectors inside their own AIOS repository, so Claude reads the legacy data in place. They keep the systems they run and we make them reachable.

Explore the AI Operating System

More case studies