About CREATE SOMETHING

The operator should see the whole court.

Division III basketball taught me to read spacing, pressure, roles, and the next decision as one shared picture. CREATE SOMETHING brings that discipline to AI operations: map the play, name who decides, and keep proof attached.

Court vision

One shared picture changes the pace.

Read the floor
Map

See the workflow, owners, handoffs, and opposition before AI acts.

Call the play
Build

Install the approved route with named decisions and executable Runbooks.

Review the film
Control

Run offense and defense with visible stops, recovery, and proof.

One operating story

The biography matters because it became the method.

Court vision, pressure, practice, and review became a way to build AI systems that operators can understand, trust, and own.

01 / 04 Read the whole floor

Division III basketball made the shared picture visible.

A good possession depends on spacing, roles, timing, and a shared read. An AI workflow needs the same operating clarity before the pace rises.

I played Division III basketball. It taught me to read the whole floor before forcing the next move. A shared picture gives every person a role, a route, and the context to adjust when the defense changes.

That is the model behind CREATE SOMETHING. The Playbook gives operators and approved AI the same view of the workflow. Offense advances approved work. Defense protects decisions, evidence, and recovery.

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.

Evidence
  • Division III basketball
  • Porsche 930 Turbo
  • Emergency medicine
  • Continuity of care
  • Webflow systems work
02 / 04 Rehearse the decision

Map the play before AI runs it.

The method makes the route, judgment states, control layer, and operator brief explicit before agent capacity expands.

Read the floor
Map the operating path

Find the workflow your team still completes or covers by hand and name the handoffs, owners, and failure modes.

Name the decision
Classify the judgment states

Separate safe work from approval-needed work and actions that should be blocked with an inspectable reason.

Install the play
Ship the control layer

Use MCP, skills, runbooks, release checks, and trust receipts to make the workflow portable and controlled.

Review the film
Brief the operator

Surface only the state that needs attention so the human returns for judgment, not constant monitoring.

Receipts
workflow mapjudgment statescontrol layeroperator brief
03 / 04 Offense + defense

Advance approved work. Protect operator authority.

One operating path becomes trustworthy before the system grows. The client keeps the Playbook, controls, evidence, and working software.

ApproachStart with the cleanup loop

Most teams need one workflow that stops creating manual recovery work before they need a larger AI initiative.

MethodSubtract before automating

The Subtractive Triad removes duplication, excess, and disconnection so automation has fewer failure paths.

Client contractBring the workflow and owner

Clients bring the operating constraints and decision owner. I bring diagnosis, controls, runbooks, evidence, and working software.

Salesforce, HubSpot, Notion, Slack, Procore, Webflow, MCP, and internal systems are useful only when ownership and recovery stay clear.

Receipts
cleanup loopSubtractive Triadclient-owned path
04 / 04 Each property has a role

Every CREATE SOMETHING property improves the next play.

Philosophy, research, experiments, and agency delivery remain distinct while passing useful evidence between one another.

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.

Read the philosophyInspect the researchExplore the tools
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.

Book a mapping session See the service path →
Owner
Workflow owner
Authority
Mapped control states
Proof
Safer first path
State
review
  1. 01 / Bring One workflow

    The manual operating path that should not need constant rescue.

  2. 02 / Map Control states

    What can run, what needs approval, and what should stop.

  3. 03 / Leave A safer first path

    The operating boundary before a production build starts.