Make / Recur Make / Recur

Build on what works.

Practical skills, templates, and workflows for building software with AI. Shaped by real product work. Ready for your next idea.

Explore the tools The thinking behind them
An open sphere of stone, glass, and acid-yellow segments, revealing the structure within.
Everything interesting
happens twice.

For people building software with AI agents.

Plan / Design / Build / Review / Iterate

01 / The tools

A stronger starting point.

Turn the decisions that matter into a system your next session can build on.

02 / The Architect System

Where this
came from

This system was built through real product builds with AI implementation teams, not as a theoretical workflow.

After every build, the architects filed structured retrospectives: what worked, where agents drifted, what caused rework, and what should change before the next project. Those findings were folded directly back into the system.

That is where the core protocols came from:

Claim Protocol
Keeps agents from overlapping or starting work that is not ready.
Escalation Lifecycle
Defines when an agent should stop, what it should surface, and how work resumes.
Decision Blast-Radius Sweep
Makes sure architectural decisions propagate everywhere they need to.
Memory Budget
Controls what context persists so the project stays useful without becoming bloated.
Landing Check
Prevents an architect session from ending before decisions, state, and next actions are properly captured.

Every gate exists because its absence cost a real project real time.

We use what we sell. When the studio builds for a client, it runs this exact system.

03 / Who this helps

Who this is for

Built for people already using AI to ship real software:

  • Technical solo builders managing an entire product themselves
  • Indie developers using AI agents to increase what they can build
  • Designers who code and need structure around implementation
  • Founders directing AI coding tools without wanting every architectural decision to live in their head

You do not need to be a senior engineer.

The system exists so the judgment lives in the project, not in your head mid-session.

You do need to be building something real.

04 / Behind the work

Start with
the story.

I help build flexible software that helps teams make complex work feel effortless. With years of experience leading product strategy and software architecture, I focus on narrative first design, clear decision points, and systems that scale without losing their purpose. At Make/Recur, everything starts with the story you're trying to tell, then the tools required fall into place.

We have packaged what I’ve learned into practical skills, templates, and workflows for building software with AI agents, Claude Code and Codex. They’re shaped by real product work, refined through repeated use, and designed to give others a stronger starting point. Instead of beginning from scratch, you can build on proven approaches to plan, design, build, review, and iterate on your own end-to-end software.

Explore Make / Recur