About Alex Solomon
I’ve always been
a builder.
I started by building things with my dad, drawing skateboard decks, and teaching myself design. Over time, I became more interested in the systems behind the work: how information moves, how decisions get made, and what allows good work to happen consistently.
Today, I design business and software systems that help people and AI work together more reliably.
The medium changed. The instinct didn’t.
Make
I began in design, photography, video, branding, and web development. I learned to take an idea from a rough concept through production and delivery.
Systemize
Creative leadership pushed me beyond individual deliverables. I began designing reusable processes, service structures, design systems, and predictable ways for teams to work.
Encode
Marketing operations, HubSpot, automation, and software gave me a way to encode those systems into data models, workflows, permissions, and governed execution.
How I got here.
I grew up around construction and wanted to become an architect before I really understood what that meant. I simply liked making things and figuring out how the pieces fit together.
That same curiosity led me into graphic design, photography, filmmaking, and web development. By my early twenties, I was already responsible for real clients, production workflows, vendors, deadlines, and creative teams.
Later, discovering Atomic Design changed how I thought about complexity. It gave structure to an instinct I had been developing for years: understand the smallest parts, define how they relate, and build deliberately from there.
Eventually, that thinking expanded beyond websites and creative work. I began applying it to CRM architecture, automation, business operations, software, and governed AI.
What I work on now.
Business systems
Designing the processes, information structures, ownership rules, and workflows behind reliable execution.
Governed AI
Building systems where AI operates inside clear evidence, permission, verification, and approval boundaries.
Marketing operations
Connecting CRM, research, strategy, production, reporting, and performance data into a coherent operating environment.
Ratchet Governed Agentic Development
Much of my current writing documents an approach I call Ratchet Governed Agentic Development, or Ratchet Development for short.
Inspired by established ideas in software quality ratchets, regression testing, and agent harness engineering, it explores how verified failures can become durable controls that future work inherits.
A lesson might become a test, contract, database constraint, permission boundary, provenance requirement, or approval gate.
The model proposes. Deterministic systems verify. Humans retain authority.
Principles behind my work.
Autonomy is not authority
People and agents need room to work without gaining permission to redefine the boundaries around that work.
Evidence should survive the output
Important claims and decisions should remain connected to the information that supports them.
Ownership should be explicit
Reliable systems depend on knowing which person or system owns each fact, decision, approval, and state.
Failures should improve the environment
Meaningful mistakes should make the same class of failure easier to catch the next time.
FAQs
My career has crossed all four. The consistent thread is systems thinking: understanding how complex work is structured, how its parts relate, and how it can become more reliable.
AI made it possible to encode increasingly complex workflows and forms of judgment into software. It also introduced new questions around evidence, authority, verification, and accountability. Those questions now sit at the center of much of my work.
I do not build my identity around that label. I design business systems, and governed AI is a major part of the systems I am currently building and studying.
Ratchet Development is shorthand for Ratchet Governed Agentic Development, an approach in which verified failures become proportionate controls that future work inherits.
Still building.
I live in southwest Missouri and still enjoy photography, home projects, learning unfamiliar tools, and the occasional Lego Technic set.
The scale and complexity of what I build have changed.
The instinct has not.