All Insights
Positioning5 minMay 4, 2026

The studio is small on purpose

Why one builder beats six engineers — and the trade-offs that come with it

Astral Studio is one person. That's a strategic choice, not a stage I'm moving past. Most weeks I get asked when I'll hire — when there will be a team, an agency, a "real" company. The honest answer is: probably not, and definitely not for the reasons you're imagining.

Here's what the math looks like from the inside.

When I take on a school with multiple cohorts and a certification path, I'm holding the entire system in my head. The pricing logic, the prerequisite enforcement, the cohort scheduling, the AI substrate trained on the founder's teaching, the way the brand voice changes between the public site and the member portal. All of it. The architecture is consistent because there's one architect.

When you hire an agency, that consistency disappears. The strategist scopes the project, the project manager runs standups, three engineers split the work, the senior reviews PRs but didn't hear the founder's explanation of why this lineage matters. The deliverable looks like a website. It doesn't feel like the work.

"Small on purpose" means I take on a handful of engagements at a time. Usually 3-5 active. Each one gets weekly contact and continuous architectural attention. When something breaks at 11pm on a Tuesday, the same person who built it fixes it. The same person who shipped your platform is the one writing your AI prompts six months later.

The economics work because of the rev-share model. I get paid when the platform earns. That aligns me with the long-term success of the work, not with billing more hours. An agency that bills $200K up front has zero financial incentive to come back six months later and improve the AI substrate. I have every incentive — because that's when the platform starts compounding revenue, and I get a share of it.

But there are trade-offs you should know about before signing up.

**Capacity.** I take on a handful of engagements at a time. If you message me in March and I'm at capacity, you're waiting until June. I won't squeeze you in by hiring a junior to "help." That breaks the model.

**Speed of execution vs. team scaling.** A 6-week build with one person is a 6-week build. With four engineers, it could theoretically be 2 weeks — except in practice, the coordination overhead on a project this small eats the savings, and the architecture still has to be unified by someone. The shape of the work matches the shape of the studio.

**Bus factor.** This is the question every serious buyer asks: "what if Jordi disappears?" The honest answer is on the FAQ page. Code in your GitHub from day one, standard tools any senior engineer can pick up, the architecture is what you're paying for, not access to me. But I won't pretend the bus factor is zero. It's lower than an agency where institutional knowledge lives in three engineers who change roles every 18 months. But it's not zero.

**No "growing the team" path.** If your project succeeds enormously and you want to scale up to a 50-person engineering org, that won't come from me. At that point you're hiring an in-house team, and I become the technical advisor or the original architect, not the operator. That transition is part of the model, not a failure of it.

The studio is small on purpose because the work I do well requires holding the whole system in one head. The day I scale to "team of six," the work changes shape — and the kind of clients I serve well don't need a team of six. They need a builder who understood their work the first time and is still building for them three years later.

There's a version of this argument that sounds like artisan-romance — "I do the work myself because craft." That's not what I mean. I mean: this is the only structure that produces the result. A school with a coherent platform built around its specific lineage. A retreat center with infrastructure that holds the depth of the work. A maker with a slow-shop that doesn't feel like Shopify. These don't come from teams. They come from one person who got close enough to the work to understand it.

If you're looking for an agency, there are good ones. If you're looking for a senior builder who will sit with your work, learn your lineage, and ship infrastructure that compounds over years — the studio is small on purpose, and that's probably why we're a good fit.

Jordi Amat

Jordi Amat

Senior engineer, former CTO. Building custom digital infrastructure for schools, practices, and original work from Mazunte, Oaxaca.

Ready to talk?

If your work needs infrastructure that doesn't exist yet, I'd like to hear about it.

Start a Conversation