ContraptionSoft solutions

CASE STUDY · DAMASCUS, AR

Rusty’s Machine & Tool.


Rusty runs a machine shop in Damascus. Every purchase order that came in meant about half an hour of retyping it into Zoho. We wrote down how he already does it, so any modern AI agent can do the typing, and nothing gets saved until he says yes.

The chore

When a customer sends a purchase order, someone has to turn it into a sales order in Zoho: find the customer, find every part, copy the quantities, prices and due dates, then fill out the traveler, the sheet that follows the job across the shop floor. It’s about half an hour per order, and it’s the kind of typing where one wrong digit becomes a wrong part.

It’s also not as simple as copying fields. Before we quoted it, we went through his past orders in Zoho to see how they really look. Sometimes the part number isn’t in its column but buried in the description. Some parts in Zoho had no part number at all, only a name. The payment terms on a PO can differ from the ones saved on the customer, and the price on a PO can differ from the catalog price. In each case the PO is what counts, so the agent has to know that too.

What we built

Not a custom agent. Rusty already had a process for handling a PO. It just lived in his head and his hands. We wrote it down: how to read a PO, where his main customer puts each field, how his sales orders and travelers get filled in, and which way to go when the PO and Zoho disagree. It’s a set of skills, plain files with instructions, plus small scripts for the steps that have to come out exactly the same every time, and a connection to his Zoho.

Any modern AI agent that can use skills and connect to other software can pick those files up and run them. Today that’s Claude Code on Rusty’s own computer, on his own Claude subscription. If Codex or Grok Build or whatever comes next does the job better, he switches and his process comes with him. The agent is the part that gets replaced every few months. The written-down process is the part that lasts, and it’s his.

Day to day: he drops a PO in. The agent reads it, finds the customer and each part in Zoho, and drafts the sales order and the traveler. Then it stops and shows him what it’s about to do. He approves it, fixes it, or asks why, and only then does anything get written to Zoho.

Why we build it this way instead of a custom agent: Don’t build an AI agent. Write the process down instead.

Illustration: Rusty’s own process for handling a purchase order, written down as skill files and scripts, is loaded by whichever agent he uses, such as Claude Code, Codex or Grok Build. The agent reads the PO and drafts the sales order and traveler, Rusty approves it, and only then are they saved in Zoho.1 · PO COMES INPURCHASE ORDER2 · ANY AGENT RUNS ITClaude CodeCodexGrok Build✓ Customer and parts found in Zoho✓ Terms and price from the PO✓ Sales order and traveler draftedHIS PROCESS, WRITTEN DOWNread-po/SKILL.mdhow he reads a POcustomers/main.mdwhere his customer puts each fieldsales-order/SKILL.mdhow he fills out a sales ordertraveler/SKILL.mdwhat goes on the travelerscripts/ · Zoho MCPexact steps, no guessingloads3 · RUSTY SAYS YESSave to Zoho?ApproveFix4 · SAVED IN ZOHOSALES ORDERTRAVELERSAVED
ILLUSTRATION · SAMPLE FILE NAMES, NOT RUSTY’S FILES

How it went

It went live on his machine in July 2026. We ran two real purchase orders through it from start to finish, and both came out clean: the right customer, the right parts, a correct sales order and traveler, with Rusty approving each step.

He owns all of it: the skill files, the scripts, and the computer it runs on. Since then he’s brought us the next chore on his list, estimating machine time for quotes.

Got a chore like this?

Automations start at $1,500 and usually take one to two weeks. See how automations work, or tell us what’s eating your week and we’ll tell you honestly whether it’s worth automating.