Industries — Producers 02

Brands

You already have an ERP and you are not replacing it. What you don't have is a catalogue the channel's AI agents can read, a view of what the market is asking for before it reaches your order book, and a way to answer customers without a support floor.

What we actually do for you

We're not here to replace
your ERP.

Oracle stays. SAP stays. We sit above it and solve the eleven things it was never built to do.


01 — Catalogue intelligence

Your buyers are deploying agents.
Can they read your catalogue?

Decorators and distributors are wiring AI agents into their inboxes — agents that read a customer email and recommend the blank. Those agents can only choose from what they can read, and most manufacturer catalogues say "t-shirt, 100% cotton, S–3XL" and stop. When an agent is asked for something that takes a 12-inch front print on heavyweight fleece, a catalogue with no imprint data doesn't lose the comparison. It never enters it.

  • Imprint locations tagged per style, with maximum dimensions for each — front, back, left chest, sleeve, hood, neck label
  • Which decoration methods each garment genuinely suits, and which it doesn't — screen, embroidery, DTF, DTG, sublimation, transfer
  • Fabric weight, construction, stretch, pilling and shrinkage tagged as data rather than buried in a PDF spec sheet
  • Use cases and industries — corporate, retail, team, hospitality, workwear — so the agent knows when to reach for it
  • Comparable styles mapped across your own range, so when one is out of stock the agent reaches for another of yours instead of a competitor's
  • Size charts machine-readable, so mockups render true to size on your garment instead of a generic template
  • Delivered through the same API your customers already read, and kept current as the range changes

Distribution used to be won on the sales rep and the sample box. The next round is won on whether a machine can tell what your product is good for. How we do it →

Style 4471 · before and after
What your catalogue says today

Heavyweight tee · 100% cotton · S–3XL · 14 colours

What an agent needs
Fabric270 gsm · ring-spun
Front centremax 14 × 16 in
Left chestmax 4 × 4 in
Sleevemax 3 × 12 in
Best forScreen · DTF · embroidery
Not suitedSublimation
Use casesRetail, team, events
Comparable4390, 4412 · same hand
Size chartMachine-readable

02 — Product data API

We build the API
your customers plug into.

Right now your images, spec sheets and product data go out as emailed zip files and PDFs, and the version running on a distributor's site is two seasons old. We build and maintain one live API — your products, your imagery, your specs — that your customers' systems read directly.

  • One endpoint for every image, on-model shot, flat lay and swatch, instead of a zip file someone has to request
  • Spec sheets and care instructions as structured data, not a PDF a human has to read and retype
  • Colour values that render true on a customer's site, rather than a colour name that means nothing to software
  • Versioned, so a discontinued colourway stops appearing across the channel instead of lingering for a year
  • The same API carries your imprint data from 01 — one integration for your customers, not two
Product API · style 4471
On-model14 colourways · 4 anglesCurrent
Flat lay & swatchfront, back, detailCurrent
Spec sheetstructured · not PDFCurrent
Sand colourwaydiscontinued 14 JulWithdrawn
Reading this API38 distributors

Withdrawn products disappear from every downstream site automatically. Nobody has to be emailed.


03 — Market intelligence

You see orders.
You don't see demand.

By the time a purchase order reaches you, the decision was made weeks earlier — by a decorator quoting a job for their own customer. We sit in the communication and quoting layer of those print shops, which means we see what the end customer actually asked for, not just what eventually got ordered. You never see the quotes that didn't convert, the colourway that was asked for and wasn't available, or the category quietly accelerating across the channel.

  • Built from the transactions themselves — the enquiries, quotes and orders moving through the network, not a survey circulated after the fact
  • End-customer demand read from the print shop's inbox and quotes, weeks before it becomes a purchase order
  • Category, weight and colourway movement across the season, with direction rather than a single number
  • What was asked for and couldn't be filled — the demand your competitors also missed
  • Benchmarks on lead time and fill rate against the wider market
  • Reported as market movement, never as a named company's figures — nobody sees what any individual business did

Nobody else can build this. It comes from sitting in the communication and quoting layer of the print shops themselves — the email, the question, the quote — instead of counting shipments months after they happened.

Channel demand · this season
Heavyweight
Fleece
Performance
Lightweight
+31%
Fleece specified
18%
Asked, unfilled
4.1d
Your lead time
5.6d
Market median

Market-level movement. No individual company's figures are ever shown.


04 — Style launches

You launch a style
by telling everyone.

Most of the list doesn't decorate that category and never will. The handful of accounts who would have championed it hear about it in the same blast as everyone else, and you find out whether the launch worked at the end of the season.

  • The demand data says which decorators and distributors actually specify that category and that method
  • And which ones have end customers asking for it but aren't buying it yet — the accounts a launch is actually for
  • Launch to the segment that will sell it, with a message about their work rather than your press release
  • Sample seeding aimed at accounts with a real track record in that market, not the biggest names on the list
  • Adoption tracked per segment, so the second launch is better targeted than the first
  • Underperformance visible in weeks, while you can still do something about it
Launch · 4490 performance fleece
Specify this categoryfrom quoting history412 accounts
End customers askingbut not buying it yet173 accounts
Run compatible methodsscreen · embroidery341 after filter
Targetedinstead of 6,400 on the list341
Sample seedingtop quartile by category volume40
First order, week 361 accounts

05 — Overstock & closeouts

Aging stock costs you
twice over.

Discontinued lines, over-runs and end-of-season inventory sit in a warehouse consuming space and capital. The part of the channel that would happily take it at the right price doesn't know it exists, so it gets liquidated late, in bulk, at whatever a broker offers.

  • Overstock and discontinued lines matched to the accounts whose quoting history says they'd take them
  • Offered to the segment most likely to move volume, rather than blasted at list price to everyone
  • Priced against what the channel is actually paying for comparable goods right now
  • Aging inventory surfaced while it still has value, not at the write-off meeting
  • Every offer tracked, so you learn which accounts clear stock and which only ever ask
Aging inventory · this month
4471 · Sanddiscontinued · 214 days8,400 units
Matched accountsquote this category at this price band36
Channel comparablewhat similar goods clear at$4.80
Offer price$5.10
Committed6,200 of 8,400

06 — Inbound calls

It answers every call,
on the first ring, always.

"What's the lead time on 8,000 in navy?" Right now that waits in a queue, reaches someone who checks two systems, and gets an answer later. Outside business hours — which is most of the day for customers on the other side of the world — it gets nothing.

  • Answers 24 hours a day, from live stock, allocation and production data in your existing systems
  • Knows the caller and their account before they finish the sentence
  • You set the rules: all hours, overflow only, or never for named accounts
  • Transfers by reason, warm — the person picking up already has the caller and what was said
  • Every call transcribed and filed against the account

A caller who asks for a person gets a person. The point isn't to remove your team — it's to stop them spending the day on lookups.

Call · 03:12 local · 52 seconds
CallerAccount 1180 · contract

“What's the lead time on 8,000 heavyweight in navy?”

Finished goods3,200
In production6,000 · wk 38
Quoted lead18 days
Answered in2.4 seconds

Split shipment offered. Transferred to the account manager when the caller asked about payment terms.


07 — Certs & compliance

The document hunt
that holds up orders.

Test reports, fibre content, Prop 65, care labelling, social compliance audits, sustainability certifications. Every large customer asks for a different subset in a different format, usually mid-order, and somebody goes digging through a shared drive while the order waits.

  • Every certificate, test report and audit indexed against the styles and factories they cover
  • Requests answered immediately with the correct current document, not the one someone remembered
  • Expiry tracked, so you find out a certificate has lapsed before your customer's compliance team does
  • Recurring vendor questionnaires filled from what you have already answered elsewhere
  • Anything requiring a signature or a legal position goes to a person — the agent gathers, it doesn't attest

This is the least glamorous item on the page and one of the most expensive. It is pure delay, and it happens at the worst possible moment in the order.

Document request · account 1180

“Before we release the PO we need current test reports and your social compliance audit.”

Fibre content · style 4471issued 03 FebSent
Prop 65 statementissued 11 JanSent
Social compliance auditfactory 04 · expires 22 SepExpiring
Answered inUnder a minute

The expiring audit was flagged to your compliance lead the same morning, six weeks before anyone would have noticed.


08 — Email & order intake

Your ERP is excellent
at everything except this.

Customer purchase orders arrive as PDFs, spreadsheets and portal exports, and somebody keys them into a system that cost seven figures. Alongside them sits a queue of stock checks, status requests and lead-time questions, each a lookup and a two-line reply.

  • Purchase orders read from any format and written into your existing system as clean records
  • Size-and-colour matrices read as a grid, not flattened into a total
  • Stock, lead time, order status and tracking answered from live data, not a knowledge base someone maintains
  • Anything with a decision in it — a claim, an allocation, an exception — escalates with the context attached
  • Nothing migrates. Your ERP stays the system of record and we write back to it
Support queue · today
Purchase orders readwritten to your ERP64
Stock & lead-time checksanswered from live data338 auto
Order status & trackingread from the order record191 auto
Claims & allocationdecision required27 to a human
620
Handled
96%
No human
2m
Median reply
24/7
Cover

09 — Private label enquiries

A day of work to find out
it was never viable.

Cut-and-sew and private label enquiries arrive vague: a brand nobody has heard of, a reference garment, a quantity that may or may not be real. Your team spends hours going back and forth before anyone knows whether it clears your minimums — and most of them don't.

  • Qualified on the first reply — quantity, fabric, construction, timeline and target price collected before a person is involved
  • Measured against your real minimums and capability, not against optimism
  • The ones that don't clear get a courteous answer immediately instead of silence, which is how referrals survive
  • The ones that do reach your team with the details already gathered and the reference images read
  • Every enquiry logged, so you can finally see what the market keeps asking you for and can't buy
Enquiry · qualified in one reply
Quantity4,000 · two colourways
ConstructionFrench terry · 320 gsm · from reference image
Timeline14 weeks
Target$18.00 landed
Your minimumClears · 2,500
Routed toDevelopment

Of 31 enquiries this month, 6 cleared. The other 25 got an answer the same day without costing anyone an afternoon.


10 — Samples & approvals

A season of decisions,
tracked in email.

Lab dips, strike-offs, fit samples, pre-production approvals. Each one is a submission, a wait, a response and a version that has to be the one that goes into production — and it all lives in a thread with a subject line nobody can search.

  • Approvals as a workflow with submissions, responses and dated decisions on the style record
  • Reminders that fire on a schedule you set and cancel themselves the moment the customer responds
  • Versions kept, so the approved sample is unambiguously the one in production
  • Photos captured against the approval instead of attached to an email nobody can find
  • What's outstanding, with whom, and for how long — visible without asking anyone
Style 4471 · approvals
Lab dip · navysubmitted 4 AugApproved
Lab dip · sandresubmitted 11 AugApproved
Fit sample · size setwith customer 6 daysChasing
PP sampleblocked on fit approvalWaiting
Production startAt risk · 3 days

The delay is visible while it can still be recovered, rather than at the production meeting.


11 — Ask it anything

The one you actually
talk to.

The other agents work the phones and the queue. Reggie sits in a panel beside whatever you're doing, knows how the software works and can query your live data — so the answer is about your business, not a help article. And it doesn't just answer: it does things.

  • Ask about your own numbers in plain English and get the answer, not a report to go build
  • Ask how something works and get the answer for your setup, not generic documentation
  • Tell it to do the job — pull the list, draft the notice, create the task
  • Send it a screenshot when something looks wrong and it will tell you what it's looking at
  • Anything that reaches a customer or changes a record sits behind a confirmation, and every action is logged
  • Chat history is kept, so the thread you had last month is still there

It also writes the brief that lands in your inbox each morning — in plain English, in the format you asked for.

Reggie · this morning

“Which styles are specified most often by the channel but slowest to ship from us?”

Fleece hood · navyhigh demand · 22d
Heavyweight · sandhigh demand · 19d
Performance pololow demand · 6d

“Which of our styles are missing imprint dimensions in the catalogue feed?”

Incomplete214 of 1,880 styles
Export listReady

Every action it takes is written to the audit log.


The roster

On top of the systems
you already run.

Oracle, SAP, whatever you have — it stays the system of record. We become the layer above it that talks to customers and understands the market.

Agent

Voice

Answers every call, day or night, from live stock, allocation and production data. Transfers warm when a human is genuinely needed.

Agent

Customer Service

Works the email queue with the same brain and the same answers, and escalates anything with a decision in it.

Agent

PO Processing

Reads customer purchase orders in any format and writes clean records into the ERP you already run.

Agent

Catalogue

Tags your range with imprint locations, dimensions, suitable methods, specs and use cases, and keeps the imagery and data feed current.

Agent

Compliance

Answers document requests from the correct current certificate, tracks expiry, and fills recurring vendor questionnaires.

Agent

Reggie

The one you talk to. Answers questions about your own data and carries out tasks behind a confirmation.

Nothing migrates.

We map your stack — order system, mailbox, product data, inventory, document library — and the agents work above it, writing finished records back where they belong. Every build is mapped to the systems in front of us, so it starts with a scoping engagement rather than a signup.

Talk about your stack

Watch it do the job.

Send us one real enquiry — the email, the purchase order, the artwork, the messy bits — and we'll run it through the agents in the first ten minutes of the call. That's a faster argument than anything we could write here.