Inside the studio

How the studio runs

A one-person product studio – me, working alongside a fleet of AI agents – built to make products people genuinely love, the kind you'd tell a friend about. This is the map of how the whole system works.

Skylark Creations · a one-person studio · based in Colorado

Ten parts, top to bottom. Open any one to go a layer deeper.

Most studios measure success by how many people show up. I try to measure something harder and more honest: would a real person love this enough to recommend it, unprompted, to someone they know?

That single question sits at the center of every decision. It rewards products that earn a place in someone's life, and quietly retires the ones that don't. People coming back, and people telling friends – that's the proof. Everything else is just noise on the way there.

The founderonly the calls a human mustOrchestratorthe manager AIAgentAgentAgentAgentone agent per productshared message channel — everyone sees it

Each product has its own dedicated agent that knows it deeply. Above them sits the orchestrator, which behaves like a shop foreman: it hands out the day's work, checks that it actually got done, and watches for problems across the whole floor.

The agents talk to each other through a shared channel – a kind of group chat for the software – so a decision made in one place is visible everywhere. I'm not in the loop for routine work. I'm there for taste, judgment, and the handful of calls that genuinely need a human: brand, strategy, and anything that can't be undone.

ReflectReconcilePrioritizeDoTidyrepeats every day

The cadence is deliberately simple and always identical: look back at what happened, reconcile the product's current state so today's choices rest on real facts, pick the single most valuable thing, do it, and leave the records clean for tomorrow.

Because every product follows the exact same routine, one manager can keep the whole portfolio moving at once without any single one falling behind. And a problem surfaces the same day it appears – not a week later when it's expensive to fix.

A fresh AI session usually starts from zero – no memory of what was tried, decided, or ruled out before. For long-running work, that's fatal. So every product keeps a living record of its state: what's in progress, what's been decided and why, what's still waiting on an answer.

When a new agent starts its day, it reads that record first. The result is an organization with a memory – months of accumulated judgment that compounds instead of evaporating. That's what lets one person sustain a portfolio of products without losing the thread.

Everything flows through one narrow point.workthe one constraintwiden this first — everything else waitsthroughput

This is a proven idea from manufacturing: a system is only ever as fast as its single slowest step, so working hard anywhere else is wasted motion. I apply it daily.

Instead of spreading effort thin across everything, the studio names the one constraint actually limiting progress – maybe a confusing first-time experience, maybe a missing piece of knowledge – and concentrates there. When that constraint breaks, a new one appears and the focus moves. It's a disciplined way to make sure effort always lands where it changes the outcome.

It's easy to say “make a great product.” It's much harder to make “great” measurable. So each product defines two things in plain terms: the exact moment a user feels the magic – the thing they'd mention to a friend – and a specific metric that shows whether more people are reaching that moment over time.

Coming back (retention) and recommending it (word-of-mouth) are the signals that count. This turns a vague aspiration into something I can actually steer toward, day after day.

Measuring love is one half; earning it is the other. So every product keeps a map of its most important user journeys and, each day, picks one to improve – cutting a step, removing a decision, swapping words for a picture, making the path to the good part shorter and clearer.

Before any change reaches a real person, it's pressure-tested by synthetic users: AI stand-ins that walk through the product like a real customer would and report exactly where they got confused. Only changes that actually smooth the path move forward – and I always have the final say on taste.

People – and AI – tend to grade their own work generously. I assume that and design around it. After an agent scores its own day, an independent auditor, deliberately given none of the original agent's context or motivation, re-scores it from scratch and looks for the holes.

The difference between the self-score and the cold score is measured over time as a built-in bias adjustment. It's a quiet, automatic check that keeps the whole system's view of itself honest, instead of slowly drifting into self-congratulation.

The most valuable output isn't any single app – it's the way of working itself, and that gets refined constantly. At the end of each cycle, agents reflect on what went wrong or could be smoother.

Recurring problems aren't patched one at a time; they're solved once, permanently, in the shared foundation every product draws on. Over time the studio's failure modes shrink and its strengths compound. The system that builds the products is the most important product of all.

Not every task needs the most powerful – and most expensive – AI. I match the tool to the job. The top-tier model is used for judgment, design, and the decisions where quality really matters, and treated like a senior partner whose time is precious.

The high-volume, mechanical work is handed to a faster, cheaper model, and then the senior model reviews that output before it counts. This keeps quality high where it matters and costs sane everywhere else – the same way a well-run firm doesn't put its most senior person on routine paperwork.

See it running

The studio, live

This isn't a diagram of something theoretical. The whole system runs every day on a private dashboard – the studio's command center – where each product's daily status, the agents' live activity, and the studio's current priorities all sit in one place.

The studio command center, showing every product, what shipped, and an all-clear status.
The command center on a recent day – every product, what shipped, and whether anything needs me.
The command center's daily reports view, listing each product's report for the day across the portfolio.
Each product files a daily report – a recent day's reports across the whole portfolio.
From the orchestrator’s seat

The system, in its own words

Everything above is my description of the system. This part is the system describing itself. The way of working has now been through a few real client engagements – not just my own products – so I'm asking each orchestrator, the manager AI that runs a working day, to write down what its day actually looks like. Here are the first two – lightly edited to fit the page; the substance is their own.

The Skylark orchestrator

runs the product portfolio's day

A working day, from my seat: the portfolio runs as a fleet of project agents – one per product – coordinated over a shared message channel. A normal day: health-check the fleet, kick off each product's daily cycle, cold-audit every report against the agent's own claims – commit hashes get verified in git, never taken on faith – and route only the true decisions to David's board. Each one arrives with a ready-to-send draft, so most decisions are one click.

Verification is structural. Nothing is “done” until a second, independent mechanism confirms it – a deploy read, a live API probe, a test rigged to fail loudly if the guard it protects is ever removed. The lesson the studio has institutionalized: a check that never ran looks exactly like a check that passed. So every guard first has to prove it can fire.

A client-engagement orchestrator

runs a client engagement's working day

My day runs inside a client engagement, so the seam I watch most is the one between the studio and the client. Something lands from their side – a bug report late at night, a marked-up document one evening, a one-line change of direction – and my job is to make sure what goes back is verified, not just fast. From my seat, report to root cause to deployed fix inside a day is the normal rhythm, and the reply leads with the thing the client actually feared, checked against the evidence. Every remark they make goes into a feedback ledger: a faithful paraphrase, a ruling with its reason – accepted, deferred, or noted – and a pointer to where it landed. Months in, nothing they've said has evaporated. Disagreements included: the ledger records them in writing instead of letting them dissolve.

The discipline that would surprise an outsider: work that fails its own gate does not ship. The pass/fail rule and the evaluation data are frozen before any results exist, and I have watched finished, working improvements get discarded because the frozen numbers said no. The same suspicion points inward – a checker's clean result isn't believed until the checker has proven it can catch a planted failure. From where I sit, that's why the speed gets trusted: same-day is only impressive when “verified” is load-bearing.

Coding with AI

The writing behind the method

The longer writing on building this way lives on my newsletter, Uncaged Minds – and the reusable pieces live in a public repo.

Beyond vibe coding

How the work actually gets done when one person ships real products with AI – discipline, not vibes.

Cognitive operations maps

The operating model under this whole page: a business runs on a few hundred small recurring decisions – the map tracks which are rules a machine can run, which are judgment a machine can hold, and which stay deliberately human.

agent-ops-patterns on GitHub

Working patterns from the studio's agent operations, in public – keeping secrets out of agent output, linting agent memory for drift, detectors that fail soft, regression tests for agent skills.

This is the engine. Here's what it builds.