Ways to work together
AI Workflow Clinic
Hands-on working sessions for people trying to automate messy work. Bring a stuck AI-assisted process, half-built automation, scattered repo, prompt/rules setup, or unclear "AI should help here" problem.
Automation / Ops Systems Review
For recurring work spread across tickets, documents, spreadsheets, email, forms, Google Workspace, workflow tools, or internal systems. We identify what should be automated, what should stay human, and what evidence or handoffs are missing.
Build Path / Technical Triage
For rough ideas, broken prototypes, AI-built apps, stalled repos, or "should this be automated?" decisions. The goal is a realistic build path, risk list, next-step checklist, or decision not to automate yet.
What we can work through
This is a practical working surface for individuals, founders, solo operators, builders, creators, and small business owners who are trying to make real work less manual.
Good fits include:
- messy workflow triage
- stuck AI-assisted process cleanup
- half-built automation
- repo or AI-built app rescue
- prompt, rules, and instruction cleanup
- Claude, Codex, Cursor, and similar agentic working patterns
- Google Workspace automation
- n8n, Zapier, Make, or similar workflow mapping
- agent boundaries and human-in-the-loop guardrails
- lightweight implementation planning
Tool names are examples, not the point. The point is making the work clearer, safer, and more repeatable.
What you leave with
Depending on what you bring, we can leave with:
- a clearer workflow map
- a practical action plan
- a safer agent or AI-assisted process boundary
- a repo, prompt, or instruction cleanup path
- a first automation slice worth building
- a risk list and next-step checklist
- a clear reason not to automate something yet
If the problem is small enough, we may fix or prototype part of it during the session. If it is larger, the win is removing ambiguity and deciding what should happen next.
Boundaries
Do not send secrets, API keys, passwords, tokens, production credentials, regulated records, or private third-party data.
A first working session does not require custody of production systems or employer/client access. Sanitized examples are preferred. This is not regulated legal, medical, financial, or compliance advice.
One session may produce a plan, map, prototype direction, cleanup path, or next-step checklist. It does not guarantee production deployment.
How to start
Email me a short note with:
- what you are trying to automate or untangle
- what you have tried so far
- where it currently gets messy or stuck
- what a useful outcome would look like