Claude Code Workflows For Smb — Development skill for Claude Code

Claude Code workflows for SMB teams

Five one-page workflows we run every day in a small operating team: one human operator and a few Claude Code sessions. Each page is a recipe a non-engineer can follow in an afternoon, with the rule that made it survive contact with real work.

Written for Approved Claude SMB Trainer cohorts to reuse in workshops. Take them, rename them, teach them. MIT.

#	Workflow	Pain it removes	Time to first result
1	Memory between sessions	Every new chat starts from zero	1 hour
2	Follow-up after a call	Call ends, follow-up never gets written	30 minutes
3	Leads from your camera roll	Conference photos and contact screenshots die in Photos	2 hours
4	Session retro	Good tricks drown in long transcripts	20 minutes
5	Approval gate in a messenger	Agent needs a yes, nobody is at the keyboard	1 hour

How to teach them

Each page has the same shape: **Problem · Setup · The recipe · The one rule · What broke for us · Minimum viable version**. Run workflow 1 first; the other four assume Claude can read and write a folder of Markdown notes. Workflow 4 is the one that keeps the other three alive.

A 4-hour workshop maps onto them like this: hour 1 = workflow 1 (structure and memory), hour 2 = workflow 2 (first artifact), hour 3 = workflow 4 as the first skill the group writes, hour 4 = pick 3 or 5 depending on the room. For a room that "just chats", teach 3 and 5 from their **Minimum viable version** only: upload photos straight into Claude, write the question to a file. The scripts are the second workshop, not the first.

Ground rules we learned the hard way

1. Markdown files in a folder beat any database you have to maintain. Claude reads them natively, humans can fix them with a text editor.
2. The cheapest to