01 · Build
Sandcastles
Products designed for specific problems we keep seeing in the work. We target four to five a year, each built and run in public. Beacon (codename), a GEO recommendation engine, is the first.
Agent-native studio · Denver, CO
A small studio building several select agent-native products a year. We explore what works in AI for the people doing the work, then share what we learn. Beacon, a GEO recommendation engine, is our first, currently in development.
01 · Build
Products designed for specific problems we keep seeing in the work. We target four to five a year, each built and run in public. Beacon (codename), a GEO recommendation engine, is the first.
02 · Explore
The decisions, the numbers, what broke, what surprised us. We share what we are exploring so others can learn from it, build on it, or try something different.
03 · Advise
A small number of SaaS sales and marketing teams each quarter. We help you put the right AI tools to work, ours and others, to drive real efficiency for your team.
Active arcs
Each arc is a bounded story with a defined start, middle, and ending question. Posts inside an arc come from one or more series. Subscribe to the question you actually care about.
The studio's first arc. How Sandcastle Labs got built: the marketing site, the brand voice, the Chronicler pipeline. Drawn primarily from past work, intentionally so. The catalogue needs depth before forward content kicks in.
Ending question
What does an agent-native studio actually look like once it has finished building itself?
Opens with S5, deliberately before any shipped code. Establishes the bet, the question, and the season's stakes. Subsequent posts populate as Beacon commits land.
Ending question
Did our bet on the GEO space hold up after first contact with the market?
Products
Real products, built and run in public. We commit to one or two at a time. Every sandcastle carries a build log on this site and ships under its own name.
A GEO recommendation engine. Clear, actionable strategies to help your business be found by agents and humans alike. Our first sandcastle, currently in active development.
Follow the build →
Recent
Build the machine, then hand someone the keys
A small AI-native software studio scales by building loops that collaborators can run, not by adding headcount. The unit that compounds is the loop.
Dropping GitHub Actions when the bill came
Our GitHub Actions billing lapsed. We replaced it with a pre-push hook. The machine that ships is now the machine that checks.
Wiring Center Pane so a non-technical editor can publish without touching the repo
The content pipeline worked fine for people who live in git. A designer coming on board does not. We built a hub round-trip so non-technical collaborators can revise and publish from Center Pane, with a GitHub Action running Claude headless to do the repo work.