You finished a Claude workshop. What's next for your order desk?

The workshop was worth your evening

If you went to a Claude workshop this fall, you weren't alone. Anthropic says more than 150 organizations of approved trainers will run over 750 workshops for small-business owners. Its spring tour reached more than 1,000 owners in 10 cities. Here in North Texas, Dallas AI held a "Claude Workshop for Business" in Richardson on Oct. 8, with 170 people marked as going. The listing promised a hands-on introduction to Claude's Cowork and chat, with no programming needed.

We think these workshops are good, and we'd tell any owner to go. They get you past the blank chat box. The sample listing promises you leave with a real task working, not a slide deck about AI.

This article is about the next question, the one owners ask us after: "Can this run my order desk?" Sometimes the honest answer is yes. Often it's "part of it." Here's how to tell.

What the workshops set you up with

We only know the workshops from their public pages, so that's all we'll describe. A typical listing on Anthropic's workshop calendar says attendees connect Claude to tools like QuickBooks, Shopify and Gusto. The workflows it lists include answering leads, turning a voice memo into a priced proposal, closing the books, and a Monday brief with cash, leads and priorities in one place. The session is free, and it's built for owners, not engineers.

Underneath, it runs on Claude for Small Business. Anthropic's Sept. 15 update says the plugin now has 43 workflows and 27 new integrations and has been installed more than 900,000 times. It runs in Claude Cowork, and workflows can run on a schedule. One line from Anthropic matters most for a business: Claude "waits for your approval before anything sends, posts, or pays."

The building blocks are worth knowing by name, because you'll keep using them:

• Instructions for Claude. House rules applied to all of your conversations: who you are, how you write, what to never do.
• Projects. Self-contained workspaces with their own chat history and files, like your price list and terms.
• Connectors. Links to the apps you use. Claude can only see content you already have permission to view.
• Plugins. A plugin bundles skills, connectors and sub-agents. The Small Business plugin is one.
• CLAUDE.md files. Plain text files of persistent instructions that Claude reads at the start of every session, used in Claude Code.

That's a real toolkit. For an owner's own week, it can save hours.

Where it shines

A chat with good instructions and a few connectors is strongest when one person is in the loop on every result and the work changes from day to day. Think of:

• A weekly brief of overdue invoices and open quotes, which you read and act on.
• Drafting a reply to an unhappy customer, which you edit and send.
• Summing up a supplier contract before a call.
• Turning notes from a plant walk into a punch list.

In each case, the person asking is also the person checking. If Claude gets something wrong, you catch it, because you were going to read it anyway. Mistakes are cheap and rare enough to fix by hand.

That matches what owners report. In the Federal Reserve's survey of small employer firms, the most common use among AI users was writing and marketing, at 83%, and 71% said AI raised their productivity.

Small firms use AI widely, but few have built it in

Share of U.S. small employer firms that use AI, by what they report. Survey answers, 2025 Small Business Credit Survey.

1. Use it for writing or marketingof AI users83%
2. Say it raised productivityof AI users71%
3. Name accuracy as a top challengeof AI users46%
4. Struggle to adapt tools to their businessof AI users43%
5. Have fully integrated AIof AI users7%

Source: Federal Reserve Banks, 2026 Report on Employer Firms (2025 Small Business Credit Survey), March 3, 2026.

Where a chat and a folder stop

The same Fed survey has the other half of the story. Of the firms using AI, just 7% had fully integrated it into their business. About half were still experimenting. The top problems were accuracy, named by 46% of users, and adapting tools to fit the business, named by 43%.

Those two problems are exactly what you hit when you point a chat setup at the order desk. Here's why.

Volume changes the math on mistakes. If Claude misreads one email a week, you shrug. If your desk keys 60 orders a day and one in fifty has a wrong part number or ship-to, that's more than one bad order a day reaching your ERP, your warehouse and your customer.

A chat does the task its own way each time. That's fine for a draft. For an order, you want the same steps every time: read the PO, match the customer, match each line to your part number, check the price against the contract, flag what doesn't match, then enter it. A built process runs those steps in order, every time, and stops when one fails.

Your rules live in people's heads. "Acme's buyer always writes the old part number." "Never ship that customer partial." "Prices on the PO don't override the contract." You can type some of this into instructions. A process puts each rule where it's checked, so a missed rule is a flagged order, not a silent error.

The work has to land in the ERP. The launch post names integrations for tools like QuickBooks. If your orders live in Epicor Kinetic, Prophet 21, Sage 100 or another ERP, check whether there's a connector at all, and whether it can create orders or only read. Many mid-size companies find the last step, getting a clean order into the system of record, is the hard part.

Someone has to approve, and you need to know who did. "Ask before it sends" is the right default. On a desk, approval should be a quick check of a filled-in order with the doubtful fields highlighted, not rereading the whole PO. You also want a record of who approved what.

A chat is great when the person asking is the person checking. The order desk needs a process that checks itself first.

A five-question test

Take one task you'd like Claude to handle and answer these honestly.

1. How often? Weekly or less, keep it in chat. Dozens a day, think process.
2. Where does the result go? If you read it and act, chat is fine. If it goes into your ERP, accounting system or to a customer, it needs fixed steps.
3. What does a mistake cost? A redo, or a wrong shipment and a credit memo?
4. Are the rules written down? If the rules live in two people's heads, writing them down is the first job either way.
5. Who checks? If the person asking won't be the person checking, you need an approval step built in.

Three or more answers on the process side usually means the order desk deserves more than a prompt.

What the other side has right

Plenty of owners will never need more than the workshop setup, and that's fine. If your company takes ten orders a week, you probably shouldn't build anything. Keep improving your instructions, add a connector, and let Claude draft while you check.

The tools are also moving fast. Anthropic added scheduled workflows and dozens of integrations in a few months, and the approval-first design is the right one. Some of what took custom work last year is now a setting. Before you build, check whether the plugin already covers your case. We'd rather tell you to keep your setup than build something you don't need.

And building a process has costs: someone has to map the steps, the rules have to be written down, and the system has to be kept up when customers change their PO format. That's the trade. It pays when the volume is high and the mistakes are expensive. It doesn't when they aren't.

What we'd do next

1. Keep using your workshop setup for your own week. The Monday brief and drafting are real time savers.
2. Write down your desk's rules. Spend an hour with whoever enters orders and list every exception they handle by memory. That list is worth having whatever you decide.
3. Time one task. Minutes per order for a week, and how many need fixing later. That's your baseline.
4. Try it in chat first. Paste ten real POs into a project with your rules and see how many come out right. If nine or ten do and volume is low, you may be done.
5. If it isn't enough, build the process around the steps and rules you wrote down, with a person approving every order before it reaches the ERP. We compare the two paths in ChatGPT vs. custom AI for business processes, and we wrote about the jobs that become worth doing in the work your team never had time for.