Twenty agents at work.One human
I'm Nicolas. I'm building crafters, and I'm its first user.
I've worn a lot of hats.Usually at the same time
Business school dropout, then a first startup that failed. So I learned to code.
Since then: developer, teacher, CTO, partner, startup-studio founder, consultant.
Every one of those jobs had me steering many crafts at once.
Then AI started working.But it could not decide on its own
I handed more and more of my work to an intelligence that kept getting better.
But it hasn't crossed the last gap of craft, and I believe it never will: knowing exactly what I want, and how I want my vision to come alive.
So I keep correcting course while it works. Correcting it once the work is done is always too late.
AI still talks to us in dense text.The feedback loop has become my bottleneck
On a normal day I have five Claude Code sessions open, four sub-agents each, across four projects.
They describe the work instead of showing it, and bury the questions that need me in paragraphs. I answer in paragraphs too, about a screen or a slide I could have just pointed at.
My attention goes into translating, not judging.
Humans belong in the work, not at the gate.Alongside AI, at full bandwidth capacity
That's crafters. The work comes to you with the question pinned on the exact spot that needs your call. You answer in place, while a decision is still cheap.
Any agent, on any craft. And the way you work becomes a process, encoded once, adopted by your team, then by anyone.
I'm building it for polymath crafters like me: people who make many kinds of things, and want every one of them to carry their intent.
NicolasFirst builder, crafters