We build kits, not platforms.
Workflow Kits is a small studio that ships bespoke agent kits for the highest-leverage workflow inside a real operating business. We shadow the operator, parameterize the business as a filesystem, install Hueks on their machine, and refine the kit every week.
In every business, one person owns a domain of knowledge.
Knowledge work is information moving through a human — flowing to them as they gather it, from them as they answer, and through them as they synthesise it into an output. That person is the operator. They own a domain — vendors and prices, staff roles, the ledger — and the judgement and accountability over it are theirs alone. We build for that person: not a company, but someone who owns a domain and is drowning in the formulaic part of running it.
Real businesses don't run on platforms. They run on desktops, paper, and what's in someone's head.
Walk into a kitchen and the truth is on a prep sheet pinned by the line. Walk into a workshop and it's on a clipboard next to the bay. Walk into a GP practice and it's in a billing clerk's spreadsheet and a stack of medical-aid PDFs.
Every workflow lives across three venues at once: files on a desktop, papers that get scribbled on, and multiple staff members' heads. Miraculously, it all comes together. But it's a little messy.
Most automation tools start by asking the operator to migrate. New platform, new schema, new vocabulary. Workflow Kits starts the other way around: we meet the business where it already lives.
The kit moves into the operator's existing folder structure. The agent reads the spreadsheets, PDFs, and inbox crud already on the desktop. The human keeps doing the judgement work. The agent drafts what's repetitive.
Five principles that shape every kit we ship.
An LLM alone is a wild horse.
Fast, brilliant, uncontrollable on its own. A kit is the harness — a saddle, a rider, and a map. A folder full of instructions only the agent knows how to read.
The agent drafts. The operator decides.
Hueks does not act unilaterally. He proposes purchase orders, vendor emails, claims appeals, estimates. Then he waits. The operator reviews, uses their judgement, and signs.
Every kit is shaped around one industry's reality.
Replenishment POs for a restaurant. Medical-aid claims for a primary-care practice. Materials sourcing for an apparel brand. We don't ship a generic agent. We ship a kit that knows your week.
It lives on your machine.
No new SaaS dependency. No vendor lock-in. The kit is a folder. The agent is Claude Code. The state is a file you can open and read. If we vanished tomorrow, your kit would still run.
Author once, coach many.
One operator or a whole team running the same workflow — the kit is authored once and shared across all of them. The build scales with workflows; the coaching scales with operators. It's the cheapest way to give a whole team the same leverage.
Shadow. Install. Coach.
Every engagement follows the same shape. Three scenes, one customer.
We shadow your operator.
We sit alongside the GM, the practice manager, the workshop owner — and find the one operator: the person who both holds the inputs (the files, the logins, the know-how) and makes the call (what to order, which claim to appeal). We map the information sources that feed the work and propose a file structure that makes the business legible to an agent. If there's no clear operator — or your existing platform already does the job — we'll tell you, and we won't sell you a kit.
Output: the operator identified, and a parameterized filesystem your team agrees with.We install the kit on your machine.
Hueks moves in. We author the first skill into the kit — the one workflow worth automating end-to-end. Every time Hueks is invoked, he re-onboards by reading the SKILL.md file. He reads the kit, scans the context, drafts the work, and hands it to the operator for approval.
Output: one workflow running, every week, in production.We keep it sharp — and coach you out of needing us.
Real workflows drift. Vendors change. Menus shift. New edge cases land in the inbox. We keep the kit sharp as it does — and coach the operator on a schedule we agree upfront: heavy at the start, tapering as they take it over, until the retainer steps down to a lighter maintenance tier. We're working ourselves out of the coaching seat by design.
Output: a kit that gets sharper, and an operator who needs us less.Hueks is the agent who moves in.
Hueks is named, on purpose. Every kit has one. He arrives with a hunch about how files and folders should be organised for an agent like him — but before he moves furniture around, he lets the operator take him on a tour.
He owns the operations cadence the kit is built for. He does not touch front-of-house, payroll, or anything outside his lane. When he closes shop for the day he saves the state, leaves a note for tomorrow, and bows out. He's a teammate, not a black box.
Operators who run real things, not knowledge workers in slide decks.
If your day is shaped by a prep sheet, a service ticket, a claims rejection, a tech pack, a brew log, or a job card — your workflow probably fits a kit.
A small studio, deliberately.
Workflow Kits is run out of Cape Town. The studio is small on purpose — every kit is hand-authored by a human who sat next to the operator the week before. We are not trying to be a SaaS platform. We are trying to ship five excellent kits to five operators a quarter, and refine them every week.
Behind the studio is a deliberate worldview. AI is real. The economic shift is real. But the bottleneck for most operating businesses is not access to a model — it is the messy, idiosyncratic, paper-and-spreadsheet shape of how the work actually gets done. That shape is what a kit is built to hold.
Workflow Kits exists to do the work of holding it. skill library v0.6 · last shipped Tuesday.