One afternoon on-site. Four departments, each sending a leader and the person who does the work. Every pair leaves with a working agent on a process they own, tested in front of you on work it has never seen, and a 30-day pilot with a named owner. Paid from training budget, delivered before the books close.
Nearly half of North American manufacturers are still at the awareness stage on AI. Not because the technology is hard. Because the person who would own it does not exist on the org chart, and the req to create them has been open all year. The fix is not one hire. It is four department heads who have each watched an agent do their own department's work, correctly, on a Tuesday afternoon.
Two weeks of sourcing, four hours in the room, thirty days of pilot support, and nobody leaves with a certificate instead of a result.
The afternoon only works because of what happens on either side of it. That is what the fee covers.
A 45-minute sponsor call to pick the departments. Each pair then runs a sourcing prompt I give them inside your own AI account. It interviews the operator, applies the screening rules (document in, draft out, no logins, repeats weekly, five real examples exist), and returns a ranked shortlist. Discovery confirms the pick, redacts the examples, and gets accounts sorted. I write the context file.
Every pair runs the same seven blocks on the clock, each on their own department's process. The operator types. I never touch their keyboard. By the demos, four agents exist, each has been tested on work it never saw, and each has an approval step written in front of it by the leader who will own it.
One hour a week, remote, whole cohort. Bring what ran and what broke. I review, unblock, and push. Day 30 is the pilot review: each pair reports against the number they said it would move. Keep, fix, or stop. All three are fine answers.
Year-end AI projects usually fail for accounting reasons, not technology reasons. This one is shaped to get past them.
It comes out of the training budget. Which is the most classically use-it-or-lose-it line on a corporate P&L, and it is not the external consulting line that 40% of mid-market companies say they are cutting to fund AI. Different pocket, different conversation, usually a different approver.
The expense books when the work is delivered, not when it is signed or paid. A Lab in November is delivered in November. Four department heads can clear one afternoon; nobody can clear two days. Net 30 means you pay it in December or January while it lands in this year's budget.
Logins for me. Everything runs in your environment on your team's accounts. I never touch your systems, which means there is no security review of a vendor, and that is the step that quietly kills most year-end deals.
Not a demo agent. Not a sample. One of your workflows, with your data, doing the work on examples it was not built on. I have never had to honor this, because the sourcing weeks are where the bad picks get killed. The thirty days after are the part that takes discipline, and that is why they are included.
I'm Matt Sitek. Before Rivet I spent two decades in enterprise technology consulting, and a good share of it in rooms where people were being taught about a tool instead of building with one. Rivet is where I build automations for companies in Metro Detroit, and the Lab is how I teach leadership teams to do it themselves.
The approach is simple and it is the same one I use on every engagement: rent the commodity layers, build the proprietary ones. The model and the tools are the same for everyone. Your business's context and your way of working are not, and once your team learns to encode those, every agent they build after is faster than the last.
I'm local on purpose. On-site means I am in your building, with your people, and you can call me the week after.
Tell me the four departments and what each one is stuck doing by hand. I will tell you whether an afternoon is enough, and I will tell you honestly if it is not.