Industries — Programmes 05

Uniform & workwear programs

Every new hire needs a kit. Every location orders differently. Every invoice has to split by department. The hard part was never the printing — it's the programme around it, and it runs forever.

Where the hours go

The order is small.
The admin is not.

Two polos for a new starter in Cleveland takes the same paperwork as a thousand-piece run, and there are forty of them a week.


01 — The company store

Their HR manager
emails you a spreadsheet.

Someone at the customer collects sizes on a form, emails it over, and your team retypes it. Then a starter joins in week three and the whole loop runs again for two garments. The programme has no front door, so every order goes through a person on both sides.

  • A branded store per customer, built from a template and live in an afternoon rather than a project
  • Only the garments that account is approved to buy, at the price agreed with them
  • Allowances and budgets per employee or per department, so spend is controlled without you policing it
  • Their own logins and order history, so "what did I order last time" isn't a question for you
  • Mockups generated on the real garment, so nobody orders a polo imagining a different logo

The store is the product. Once it exists, most of the programme stops touching your inbox.

Store · Northside Health
Approved catalogue14 garments · 3 departmentsLive
Clinical staffscrubs, fleece, name embroidery6 items
Front deskpolos, cardigan4 items
Allowance$220 / employee / yr
Active logins318
Orders placed without you94%

02 — New hires & reorders

Forty orders a week,
two garments each.

Programme work isn't big runs, it's a permanent drip. A starter here, a replacement jacket there, someone who changed size. Each one is a quote, an order, a production ticket and an invoice for eighteen dollars of product, and the admin costs more than the goods.

  • Reorders placed straight from history — same garment, same logo, same placement, new size
  • Small orders batched onto the same production run instead of being handled one at a time
  • Every setup, screen and digitised file already attached to the account, so nothing gets recreated
  • Automations that chase approvals and payments without anyone remembering to
  • The whole trickle visible as one queue, so a slow week is obvious before it's a bad month
This week · programme orders
61
Orders
2.4
Avg units
3
Prod. runs
0
Retyped
New starterskit ordered from the store38
Replacementsreordered from history19
Needs a humannew department, no pricing yet4

Fifty-seven of sixty-one never reached a person.


03 — Names & departments

Three hundred garments,
no two the same.

Uniform work is personalised by default. A name on the chest, a department under it, a different logo for the service arm, a spelling somebody typed wrong on a form three weeks ago. The run is only as good as the list, and the list arrives as a spreadsheet.

  • Name, role and custom fields captured per garment at the point of order, by the person whose name it is
  • Held as structured data on the order line, not as a note somebody has to read
  • Production sees the personalisation list as a list, in run order, with placement and thread against each
  • Spelling confirmed by the wearer before it's stitched, not after
  • The same file and placement reused on every reorder for that person

A misspelled name is a remake, and remakes on personalised goods can't be resold to anyone.

Personalisation · order 5512
A. OkaforClinical · left chestConfirmed
M. DelgadoClinical · left chestConfirmed
S. WhitfieldFront desk · left chestConfirmed
J. Bergstromspelling differs from last orderCheck
ThreadMadeira 1076 · white
Run ordergrouped by department, then size

04 — Locations & billing

One customer.
Nine ways to invoice them.

Head office wants a single monthly statement. The franchise sites pay their own way. One region insists on a PO number per order or accounts payable rejects it. Somebody in your office holds all of that in their head, and takes it with them when they leave.

  • Locations under one account, each with their own contacts, ship-to and billing rules
  • Contract pricing applied per account, so the store shows the right number without anyone checking
  • PO numbers captured at order time where the customer requires them
  • Consolidated or split invoicing, with payment links, straight out of the order
  • A/R aging per location, so you know which site is slow rather than which customer
Account · Northside Health
Head officeconsolidated, monthly1 invoice
Clinics × 6billed to head officerolled up
Franchise sites × 3billed direct · PO requiredseparate
Contract pricingApplied automatically
Over 60 days1 site · $2,140

The slow payer is a location, not the account. Now you can see that.


05 — Stock & replenishment

You're holding their
inventory for free.

To ship a new starter in two days you have to hold decorated stock, which means capital sitting on a shelf. Nobody knows exactly what's there until somebody counts it, and the sizes that run out are always the ones you didn't watch.

  • Held stock tracked per customer and per size, so the shelf and the system agree
  • Reorder points per SKU, so replenishment triggers before a size runs out rather than after
  • Decorated stock drawn down automatically as store orders ship
  • Blanks purchased against the programme's real burn rate instead of a guess
  • What's slow-moving surfaced before it becomes dead stock in a discontinued colour
Held stock · decorated
Polo M
Polo L
Polo S
Fleece XL
Polo Sbelow reorder pointReplenish 40
Fleece XL2 weeks of cover leftReplenish 25

Triggered on burn rate, not on someone noticing an empty shelf.


06 — Ask it anything

The one you actually
talk to.

The other agents work the store 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 programmes, not a help article. And it doesn't just answer: it does things.

  • Ask which programme is actually profitable once the small orders are counted
  • Ask what's held for a customer, in which sizes, and what it's worth
  • Tell it to do the job — pull the list, draft the notice, create the task
  • 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 uniform programmes lose money once setup and small orders are counted?”

Northside Health24% margin
Harbour Hospitality17% margin
Vale Logisticsavg order 1.6 units4% margin

“Draft a note proposing a minimum order for Vale.”

DraftReady to review

Every action it takes is written to the audit log.

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.