I build calm operator systems for autonomous work.

Why I work this way

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 Operator systems: fast where the rules are clear, visible where judgment is required, and recoverable when something goes wrong.

What I do now

Micah Johnson. I am a Senior Systems Architect on the Marketplace Team at Webflow, where I build internal tooling, onboarding systems, and platform infrastructure serving millions of users. The problems are familiar: brittle handoffs, unclear ownership, and systems that look automated until the exceptions show up.

I have shipped integrations across Salesforce, HubSpot, Notion, Slack, Procore, and internal systems. That work informs where native tooling is enough, where MCP is the right wedge, and where approvals, policies, operator briefs, and recovery paths are the difference between a launch and a system people actually trust.

Based in Texas. Working with businesses across the US.

LinkedIn · Email

How I approach the work

Most teams do not need a giant AI initiative first. They need one workflow that stops creating manual cleanup. I start there, then add controls only when the cost of failure justifies the extra layer.

My methodology is the Subtractive Triad: remove duplication, excess, and disconnection before adding automation. Cleaner systems reduce handoff risk. Better constraints make automation more reliable.

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.

How clients experience the work

Clients do not hire me to become another internal admin. They bring the workflow, the operating constraints, and the approval owner. I bring the diagnosis, the control layer, and the artifacts your team needs to run and inherit the system.

Visibility comes through runbooks, approval states, release evidence, operator briefs, and working software, not meeting theater. If what a client needs is a full internal delivery team, I route that work to a better-fit partner.

Timeline

The through-line is not AI. It is learning how to turn messy systems into operating paths people can trust. That pattern shows up in science, creative work, client services, marketplaces, and now automation.

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 — Governed workflow infrastructure, reliability controls, and enterprise extension (you are here)

Client work informs the research. Research sharpens the methodology. The methodology raises the bar on client work.

Also building

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.