Company

Superintelligence for
decorated apparel.

We are building an intelligence that understands this industry the way a twenty-year operator does — pricing, artwork, machines, suppliers, customers — and then puts it to work running the front and back office of a print shop.

The mission

Give every shop the operator it can't hire.

A decorating business does not lose money on the press. It loses money in the hours around it: an enquiry read three times, a quote priced from memory, artwork chased across four emails, a purchase order typed in twice, a margin nobody checks until the month closes. That work is skilled, endlessly repetitive, and it is where the profit quietly goes.

Big companies solve it by hiring — an estimator, an order-entry team, a purchasing manager, a controller. Most shops cannot, so the owner does all of it at night. Our mission is to close that gap with intelligence rather than headcount: an AI that quotes, buys, schedules, chases and reconciles at the standard of a shop's best employee, at every hour, for every job.

We call it superintelligence for this industry deliberately. Not a chatbot bolted to an inbox — a system that knows what a 5,000-stitch left chest costs on a 48-piece run at your rates, which supplier actually has the garment, and what the job will earn before you accept it.

What we believe
Domain knowledge is the moat. Colour counts and stitch counts aren't configuration — they're the product.
Context beats cleverness. An agent that can see the whole business beats a smarter one that can't.
An agent should do the work. Summarising an email is not doing the job.
One cost model, not two. The margin you quoted and the margin you got must be calculated the same way.
The owner stays in command. Automation you can't inspect, correct or switch off isn't automation. It's a gamble.

What we are building

The whole shop, front and back.

Automating one department moves the bottleneck to the next one. So we build across the business, on one shared model of your pricing, your products and your customers.

01

The front office earns

Enquiries answered, artwork read, quotes priced against your real tables, follow-ups sent, purchase orders turned into live jobs. Faster quotes win more work, and the quoting stops depending on who happens to be at their desk.

02

The back office protects

Buying, receiving, scheduling, invoicing, costing and payroll on the same numbers the quote was built from — so the margin you were promised is the margin you bank, and you find out during the job rather than after it.

03

The shop compounds

Every quote, correction and finished job teaches the system how your shop actually works. It gets better at your business specifically — which is the part a generic tool can never do.


Why us

Built by people who have run the shop.

This is an industry that has been sold software by people who have never counted a screen or explained a dye-migration problem to a customer. We have. That is why InkIQ prices by colour count and stitch count natively, why it knows a rush job is not just a flag, and why it does not ask an owner to describe their business in someone else's vocabulary.

It is also why we built the system of record first and the agents second. An agent bolted onto software that cannot see your pricing spends its life guessing. Ours doesn't have to. And because few companies can replace an ERP this year, the agents also run on top of what you already have.

What it knows
Your pricing. Colour counts, stitch counts, quantity breaks, rush tiers and the upcharges you actually apply.
Your catalogue and suppliers. Live stock and cost across the vendors you buy from, matched to what the customer asked for.
Your floor. Machines, methods, capacity and lead times — so a promised date is one you can hit.
Your customers. Every job, artwork, correction and conversation, on hand the moment the next email lands.

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.