Blog · field notes
For people who need the mechanism to trust.
12 dense pieces. Operators and technical buyers who want receipts - not a feature tour.
- Pillar15 July 2026
Not a Chatbot. A Boardroom: Inside the AI Village's Board of Wardens
Seven specialists, each with a genuinely different lens, reviewing the same proposal and sometimes disagreeing with each other. ODIN synthesises the debate. You approve, modify, or reject. Here's what's actually running underneath "AI Village."
Read article → - Pillar15 July 2026
The Testing and Simulations Behind Craft11
Migrations that taught us when not to use AI. A testing suite we ended up calling Velvet. Years of simulated business history, run for real. Here's what we actually checked before calling any of this done, and what we're honest we haven't.
Read article → - Pillar13 July 2026
The Question That Failed Every Time, Until It Didn't
Five separate test runs. The same question, asked honestly each time: propose a package grounded in what has actually worked. Every single one came back "I don't have that." Then we changed how the Vault gets searched, not what it knows, and asked again.
Read article → - 10 July 2026
The New Hire Who Didn't Need Anyone to Explain Anything
A newly invited team member logs in for the first time on an established company. No onboarding wizard, no "let's set up your pipeline." Stark already knows he's not the founder, and gives him a real tour of what's actually happening right now.
Read article → - 9 July 2026
The Commitment You Forgot You Made (Stark Didn't)
"We'll check back in with them in two months." A line in a raw note, typed once and never thought about again. Stark read it, worked out the real date, and quietly turned it into a task with a deadline. Nobody asked it to.
Read article → - 30 June 2026
How to Run a Monthly Alignment Session in Under 20 Minutes
Most founders never write down their actual pricing philosophy, what makes their best clients different, or what the team needs to know when they're not in the room. Not because it's hard, but because nothing ever asks. Here's the structured ritual that does, and why it gets faster every month.
Read article → - 30 June 2026
How to Stop Losing Context Between Client Meetings
The fix isn't a better notes app. It's accepting that the messy, half-formed note you'd normally never write down is more valuable than the polished summary you write an hour later, and building a system that keeps both, instead of forcing you to choose.
Read article → - Pillar30 June 2026
Migrating Messy Client Data Without the Nightmare
Most software makes you clean your data before it will take you seriously. We built the opposite: throw it the mess, and it tells you honestly what it found, what it guessed, and what it couldn't fill in. Here's exactly how, including the bug we found building it.
Read article → - Pillar30 June 2026
The Complaints We Built Craft11 to Avoid
We read through real user complaints about business software, the kind people post when nobody's watching, not the kind that ends up in a case study. A handful of patterns kept showing up. Here's what we built differently for each one.
Read article → - Pillar30 June 2026
The Two-Click Offer: How Automode Actually Works
An inquiry comes in missing half the details. Stark drafts a request, you approve. The reply comes back. Stark drafts a priced offer, you approve. That's the whole flow: two clicks, with everything in between done for real, not simulated for a demo.
Read article → - Pillar30 June 2026
What Actually Happens After Twelve Months of a Memory That Compounds
Most AI tools answer the same question the same way on day one and day three hundred. We wanted to know if ours actually got better, or just more verbose, so we tested it, including asking it to grade our own progress. It didn't flatter us.
Read article → - 30 June 2026
What Is a Sacred Spine in Business Software?
A direct answer: it's the one enforced sequence, Client, Inquiry, Offer, Project, Invoice, that every piece of client work has to follow, with nothing allowed to exist out of order. Here's why that single constraint changes more than it sounds like it should.
Read article →