Leave with a time audit, one mapped workflow and a working build.
How you do anything is how you do everything.

AI ExchangeBuilding Phoenix's AI community, together. Workuity hosts tonight, and we present Founder Weekend side by side.
Automates whatever was loudest this week.
Five people. Six new clients a week.
Hours a week x Rules x Risk, each 1 to 3.
Client onboarding: 7 hrs, 6x a week. Score 63.
Categorizing transactions: 18
"Where's my report?" emails: 15
Month-end review: 6
claudeWhich tasks come back every week?
youOnboarding, chasing documents, client emails.
✓ TIME-AUDIT.md: log table, 4 scoring columns
Interview me about my recurring work, then write TIME-AUDIT.md with a log table and the scoring columns. Stop there.
Onboarding · 7.0 h · 6x · R3 · K3 · 63
Categorizing · 9.0 h · 25x · R2 · K1 · 18
claudeOnboarding is mostly rules. Map it first?
Total the log, propose Rules and Risk scores for me to correct, rank by score, and recommend one workflow to map.
Trigger, inputs, decisions,
handoffs, outputs, exceptions
A written rule decides. Same input, same output.
Drafting, reading and matching. A person checks the result.
Anything that sends, spends or touches the books.
claudeWhat happens when a document doesn't match?
youIt goes to the office manager.
✓ WORKFLOW-MAP.md: 9 steps · 3 automation · 3 AI · 3 human
Interview me about the top workflow, then write WORKFLOW-MAP.md: a step table marked AI, Automation or Human, exceptions and a mermaid flowchart.
Mermaid renders in Markdown files on GitHub.
Intake form submitted after the engagement letter.
9 steps: 3 automation, 3 AI, 3 human.
Unsure match, client question, day 14: a person.
Nothing sends without Approve
Uploads tick the right items
Minutes per client compared
Run it twice. The second run creates nothing.
The firm owns rules/checklists.md.
Three sample clients, no real names.
tracker.csv remembers who's done.
Write the firm's checklist rules, three fake clients and onboard.mjs: folder, CHECKLIST.md and a tracker row per client. Safe to run twice.
✓ outbox/mesa-lawn-welcome.md · awaiting approval
✓ bank-statement-oct.pdf → Bank statements · high
? scan-0042.pdf → NEEDS-REVIEW.md · low
I add my API key. Then Claude drafts welcome emails into an outbox, matches uploaded PDFs to the checklist, and drafts reminders. Nothing sends.
platform.claude.com/docs
One bad draft reaches every inbox.
A one-page local approval queue: Approve sends through Resend once and logs it, Reject and Edit don't. Dry-run until I set up Resend.
1 new client · 2 drafts awaiting approval
4 items ticked · 1 needs review
claudeOnboarding: 41 min per client, down from 70.
One npm run daily with a summary, a RUNBOOK.md, and a minutes-per-client log to compare against the audit. Then check Done when.
youPlan it for Zapier.
Step 5 → Human in the Loop · Request Approval
✓ BUILDER-PLAN.md · 9 steps · 2 unverified
Pick n8n, Zapier or Make, read its docs, and turn WORKFLOW-MAP.md into a step-by-step build plan with the approval steps in place.
More talks at shipai.club/talks. Bring your map to the Discord.
An Arizona AI hackathon. Teams of 1-4.
See the hackathon ↗