The operator can step away.
About
I build calm, transparent workflow systems for operator-owned outcomes.
The operator should not carry the chaos of automation. My work turns toolchains into clear workflow states: what agents and tools can do, what needs judgment, and what must stop with a reason.
Judgment is required before action.
The system explains why it paused.
Why this work
Power needs control. Pressure needs protocols.
I grew up between two reference points: a Porsche 930 Turbo and emergency medicine. One taught me that power needs control. The other taught me that when pressure rises, clear protocols matter more than improvisation.
Later, as an equine veterinary technician, I learned what continuity of care, logging, and operating discipline actually feel like in the real world. That stays with me in systems work now.
Today that shows up as calm, transparent, reliable workflow systems: fast where the rules are clear, visible where judgment is required, and recoverable when something goes wrong.
I am a Senior Systems Architect on the Marketplace Team at Webflow. That work keeps the problems concrete: brittle handoffs, unclear ownership, internal tools, onboarding systems, integrations, and platform infrastructure that have to survive real operators.
Calm Operator Method
Protect the operator before you scale the agents.
The method is simple enough to fit on an e-ink surface: map the workflow, classify the judgment states, ship the control layer, and brief the human only when attention changes the outcome.
Find the workflow your team still completes or covers by hand and name the handoffs, owners, and failure modes.
Separate safe work from approval-needed work and actions that should be blocked with an inspectable reason.
Use MCP, skills, runbooks, release checks, and trust receipts to make the workflow portable and controlled.
Surface only the state that needs attention so the human returns for judgment, not constant monitoring.
Working contract
The work stays narrow enough to trust.
The goal is not more automation. The goal is one operating path that lets the operator stop watching the dashboard until judgment is actually required. Salesforce, HubSpot, Notion, Slack, Procore, Webflow, MCP, and internal systems are only useful when the ownership and recovery path are clear.
Most teams need one workflow that stops creating manual recovery work before they need a larger AI initiative.
The Subtractive Triad removes duplication, excess, and disconnection so automation has fewer failure paths.
Clients bring the operating constraints and decision owner. I bring diagnosis, controls, runbooks, evidence, and working software.
System
The rest of CREATE SOMETHING
CREATE SOMETHING operates as a connected system. Each property has a distinct job, and each one sharpens the others:
- .ltd — Philosophy and principles
- .io — Research and validated patterns
- .space — Tools and experiments
- .agency — Calm, transparent workflow systems, reliability controls, and enterprise extension (you are here)
Client work informs the research. Research sharpens the operating model. The operating model raises the bar on client work.
I am also building WORKWAY. When clients need fuller system development and onboarding than .agency is meant to carry, I provide a direct referral path to trusted partners, including Half Dozen.
Start with one workflow
Bring one workflow your team is ready to delegate.
I map the signals, decision owner, allowed actions, approval pauses, stop conditions, and proof record before AI runs it.
Bring One workflow
The manual operating path that should not need constant rescue.
Map Control states
What can run, what needs approval, and what should stop.
Leave A safer first path
The operating boundary before a production build starts.