Not an agency?
My solutions are universal.
Systems design, automation, and AI are business mechanics, not industry specifics. My three-stage process and five frameworks apply the same way whether you run a product company, a services firm, or any business.
How it works?
Three stages, any business.
The sequence is the strategy. Diagnose before you architect. Architect before you build. Most businesses reverse this, start with tools, and then try to fix the workflow after the tool creates friction.
Diagnose
Map how the business runs today. Surface key-person dependency, workflow ambiguity, ownership gaps, and every place AI or automation is being asked to cover for missing structure.
- Founder and team interviews
- Live swimlane mapping the business end-to-end
- Workflows scored across all 5 frameworks
- KMRA measurement of key-person dependency
Architect
Design the target system before implementation begins. Workflow logic, routing, decision points, triggers, and the right AI layer for each workflow.
- Target workflows designed end-to-end
- Automation and AI layer specified per workflow
- Priorities sequenced in build order
- Founder debrief closes the diagnostic
Implement
Build the workflows, automation, and AI support in the right tools. The engagement is done when the system runs without collapsing back onto one person.
- Workflows and automations built inside your stack
- AI introduced at the right layer per workflow
- Decisions move from human heads into the system
- Scope sized by the diagnostic, not a fixed package
Systems first. Automation on top. AI on top of that.
Five diagnostic frameworks. Every engagement uses them.
These frameworks are how the Diagnose stage actually gets done. They work because they diagnose how a business operates, not what industry it is in.
The AI Enablement Pyramid
Why AI fails without a foundation.
Four layers for AI inside a business: Visibility, Classification, Decisioning, Execution. Each depends on the one below, and none of them work without a foundation of documented workflows, clean data, and clear ownership.
Most businesses try to start at the top: drop an AI tool into an unclear workflow and wait for magic. That is why AI breaks. The pyramid shows you which layer your business is actually ready for and what has to exist underneath it first.
The Operating Constraints Model
Three types of broken. One correct fix each.
Every operational problem is one of three things: a missing process, a person who has become the process, or tools that do not fit the work. Each type has a different correct fix.
Applying the wrong fix is how businesses spend six months automating chaos. The model classifies every constraint into System, People, or Tool, and tells you which one to solve before the others have any chance of holding.
System Constraint
No documented process exists. Nothing to automate, measure, or hand off.
Build the process first, then automate.
People Constraint
The process depends on one person, usually the founder. They ARE the system.
Remove the dependency before automating.
Tool Constraint
Tools don't integrate or don't match the workflow. Misaligned, not broken.
Align tools to the designed system.
The Impact × Readiness Matrix
Fix the ten that matter. Stop worrying about the other forty.
Every workflow gets scored against two questions: how badly does the business suffer if this breaks, and how ready is it to stand on its own. The top-left quadrant is the real to-do list. The rest of the matrix is permission to stop worrying.
System readiness is AI readiness. Q1 workflows can take AI today. Q2 workflows need the foundation built first. Q3 and Q4 workflows get simplified or left alone.
The Systems Goal Alignment Framework
The difference between a calendar and a trigger.
Every workflow is either Cadence (time-based, predictable) or Response (event-triggered, reactive). Each needs a different architecture. Getting this wrong is the most common design error in operations.
It is why weekly meetings keep trying to solve problems that needed a response three days earlier. Once you classify them, automation and AI finally have the correct logic to sit on.
Time-Based Systems
Weekly reports, monthly check-ins, recurring delivery milestones. Calendar-driven. Built on templates, schedules, and automated reminders.
Event-Triggered Systems
Client escalations, new leads, change requests. Trigger-based routing, conditional logic, escalation paths. Built to react instantly, not on a calendar.
The Key Man Risk Assessment (KMRA)
How fragile is the business, actually.
KMRA scores how dependent the business is on any single person across four dimensions: Knowledge, Execution, Decision, and Relationship. It turns an abstract feeling into a precise number.
Seeing 13 out of 16 next to the founder's name changes the conversation, because you cannot fix what you refuse to measure. Any dimension scoring above 2 is a workflow AI has no structure to act on yet.
What gets built?
Three layers, in order.
You cannot automate chaos, and you cannot AI-enhance something that isn't measured yet. The order matters. Systems first. Automation on top of systems. AI on top of automation.
Systems Design
Workflows, ownership, triggers, handoffs, documentation, a single source of truth. The operating foundation. Nothing else works without it.
Automation Design
Middleware, integrations, event-driven workflows. The execution layer that runs the systems without human attention. Built once, runs forever.
AI Design
The four AI layers (Visibility, Classification, Decisioning, Execution) applied on top of the automated foundation. AI that works because the substrate is clean.
Pricing, scoped to the business.
Every engagement starts with a diagnostic conversation. Pricing is shared after scoping. It's a function of what the business actually needs, not a menu.
Diagnostic
A fixed-scope audit that maps the business as a system and produces a prioritized action plan. Always the first engagement.
- Team interviews and live workflow mapping
- Workflows scored across all 5 frameworks
- KMRA measurement of key-person dependency
- Prioritized build order and debrief
Build
Design and implementation of systems, automation, and AI. Scope and ordering come directly from the diagnostic. Priced per scope.
- Workflows designed and built inside your stack
- Automation across tools, no glue left on humans
- AI introduced at the right layer per workflow
- Team training and handover documentation
Ongoing
Monthly retainer for continued operation, iteration, and new builds once the foundation is in place. Optional, not assumed.
- Maintenance of built systems and automations
- New workflow and AI builds as the business grows
- Quarterly re-diagnosis to catch new drift
- Priority access for urgent operational questions
What past clients have said.
Let's talk.
If someone sent you here, mention their name when we talk. It helps me prep.