Founder Pass · The Founding Chapter
Build your studio through the founding chapter.
I’m building an AI-native studio, and this workshop is where we turn the work into something we can learn from and use in our own studios. Founder is an invitation to pursue that ambition with me through this chapter, with the complete Crafter experience.
Complete Crafter access from verified purchase through December 31, 2029. No automatic renewal.
Build the capability behind your apps.
I want more than a faster way to write the next piece of code. I’m building the agents, knowledge and workflows that can carry app work from intent to a result worth shipping. The product matters, and so does the system that makes the next product possible.
Turn the method into part of the studio.
Research, decisions, implementation and checks should not start from nothing every time. Keep the useful context, make good practice repeatable and connect the work where that connection earns its place. That is how a collection of tools begins to become a software factory you can direct.
Stay close enough to improve it.
A system is only useful if you can understand what it is doing. When an app or a workflow fails, get close enough to find the cause. Repair the result when it needs repairing, and improve the method when the method let you down. Delegating work does not mean delegating away the craft.
Let the studio grow through real work.
I’m taking this direction through native Apple apps, learning from what holds up and what needs another pass. Over the chapter, the aim is not simply to collect more outputs. It is to develop a stronger way of building, with learning you can carry into your own studio and your next app.
Develop the agents behind the work.
Context, model, prompt and tools are the four foundations I keep returning to. Improving one can help a task. Bringing them together well can change how much of the work an agent is able to carry.
Agentic coding tools like Claude Code make it possible to connect changes, checks, investigation and documentation into longer runs. The ambition is not an agent that stays busy for hours. It is work that holds up, and a workflow we can understand when it does not.
That is where I want to put more of my attention: developing the agents, their context and the methods they use, rather than steering every individual change. A useful improvement should help the next piece of work too.
This deserves sustained practice, not a promise that we have solved it once and for all. I keep the product direction and the shipping judgment. The agents carry more of the work as the capability earns trust, while I stay responsible for what we build.
Four overlapping circles: context and tools above, model and prompt below, each overlapping its neighbours.
Why Notion?
Notion became my command center gradually. When I started freelancing, I was using it for documentation and keeping track of my coding sprints. It already had a place in the work.
Then I started collaborating with clients there, and eventually setting up Notion for their businesses. It was no longer just somewhere to keep notes. It was somewhere we could hold the context together and follow the work.
When agents became part of how I worked, bringing their coordination and collaboration into that same place made more and more sense. I was already there. The command center grew out of the practice, rather than arriving as a setup I had planned from the beginning.
I can use my MacBook or another device while the agents on the Mac mini reach the shared context through MCP, browser use or connectors. We can work in the same place without using the same interface. There are other ways to build a command center. This is why I chose this one, and why it has continued to make sense for my work.
The direction of this chapter.
I’m leading the Lab toward a clear ambition: developing AI-native studio capability through real product work. I’m building my own studio, and sharing the reasoning so you can develop yours. That direction is not in question.
What I cannot honestly tell you is exactly how the tools, devices or the Lab itself will look three years from now. At this pace, pretending to know would be less useful than doing the work and paying attention to what changes.
January 2027 through December 2029 gives this chapter a deliberate horizon. We have room to develop the practice, then a point to question what chapter three should become. I want to lead that next decision with what we have learned, rather than lock the future to an answer I invent today.
- January 2027The chapter begins
- 2027–2029Build, share, improve
- December 2029Review the chapter and decide what comes next
Before you join.
If you want to pursue this work with me, Founder is a one-time commitment of $1,500. You get complete Crafter access from your verified purchase through December 31, 2029. There is no automatic renewal. If you join later, you join for the remaining chapter.
I’m keeping this founding group to ten original people. Those places don’t reopen when someone leaves. You’ll remain recognised as an original Founder after your access ends, and that recognition stays private unless you choose to share it. It doesn’t extend your access or give you ownership of the company.
Read the Founder Pass details and Founder terms before you decide.
One more think, Founder is for serious builders who want to pursue this work with care. It is not a beginner’s introduction, a one-prompt shortcut or a badge in place of doing the work. The ambition is to develop your own studio, not reproduce mine.
The shared Teamspaces contain parts of my working practice, not a template pack. You will find work in progress, decisions that changed and systems I’m still improving. Understanding why they take this shape matters more than copying them. Your studio should become your own.
I’m keeping the founding group small because I want the conversation to stay close to real work. If you want to pursue this chapter with that same intent, I’d love to have you here.
Complete Crafter access from verified purchase through December 31, 2029. No automatic renewal.