The phrase software engineering studio shows up on more landing pages every year. It is often used interchangeably with agency, consultancy, or shop — but the operating model behind each word is genuinely different, and the differences matter when you are choosing who builds your product.
This is a short, honest guide to what a studio actually is, where the model comes from, and when it is the right choice over an agency, consultancy, or a roster of freelancers.
The short definition
A software engineering studio is a small, senior team — typically four to twenty people — that builds software products end-to-end as a single integrated practice. There are no juniors waiting to be staffed onto your project. There are no account managers between you and the engineers. Every project is delivered by the same partners who scoped it.
The model borrows directly from architecture and industrial design studios. A small bench of senior practitioners. Selective about clients. Opinionated about how the work is done. Closer to a craft practice than a services business.
Studio vs. agency vs. consultancy vs. freelancer
The four models look similar from the outside — all of them build software for hire — but the incentives, staffing, and economics differ sharply.
Agency
Agencies are built to scale headcount. They typically range from 30 to 300+ people, with a pyramid structure: a few principals, a layer of mid-level leads, and a wide base of junior developers and designers who do most of the day-to-day work. Sales and delivery are separate functions. The engineers you meet in the pitch are rarely the ones who write the code.
Agencies are the right call when scope is large, well-defined, and the work is more about execution than judgment — a known CMS build, a re-platforming with a clear spec, a campaign site with a fixed deadline.
Consultancy
Consultancies sell thinking more than building. They produce strategy decks, architecture documents, vendor recommendations, and assessments. The deliverable is usually a report or a roadmap, not running production code. Many consultancies will help you hire a separate team to actually implement what they recommend.
Consultancies are right when the question is what to build or which technology to adopt, not when the question is build this thing.
Freelancers and contractor rosters
Freelancers are the lowest-friction option for narrow, well-bounded work. You hire one person, they do one thing. The trade-off is that you become the integrator: you manage scope, coordinate handoffs, do the QA, and own architectural coherence across multiple contractors. For complex products, that integration work is often more expensive than the contractors themselves.
Studio
A studio is structured to do the opposite of an agency. Headcount is capped on purpose — usually fewer than twenty people — because adding juniors changes the economics and the output. The same people scope, design, build, and ship. There is no handoff because there is no chain.
Studios are the right call when the work requires judgment as much as execution: ambiguous problems, AI products without clear precedent, inherited codebases that need both an audit and a fix, the last 20% of polish that distinguishes good software from forgettable software.
Why senior-only matters
The most consequential structural choice a studio makes is to not hire juniors. It sounds elitist on the surface. The reason is economic and practical.
In a pyramid agency, the partners' time is paid for by margin on junior hours. Juniors are billed at $80–$150/hr but cost the agency $40–$70/hr, and the spread funds the senior bench. The model works, but it requires a constant supply of well-bounded work that juniors can execute under supervision. The senior people end up doing oversight more than they do the craft.
A studio inverts this. There is no junior bench to keep utilized. Rates are higher per person but team size is smaller, so total project cost is often comparable — and the work is being done by the people who would have been supervising in an agency.
A studio's promise is not lower cost. It is that the people in the room during the pitch are the same people writing the code at 2 a.m. on week 10.
What a studio actually does day to day
Most studios cluster their work into three or four practices. At Kirin, those are product engineering, design engineering, AI & interfaces, audit & refactor, and scale work — but the specific list matters less than the pattern. Practices are deep, not wide. A studio does not take on database migrations, brand identity, paid acquisition, and SEO under one roof. It picks a tight cluster of work where senior judgment is the differentiator and gets very good at that cluster.
Engagements are typically eight to sixteen weeks. Long enough to ship real software; short enough to keep the team from drifting into the role of an outsourced staff augmentation provider.
When a studio is the wrong choice
Studios are not the right answer for every situation. You probably want an agency or an in-house team instead if:
- The scope is large and well-specified, and you mostly need execution throughput rather than judgment.
- You need ongoing support — multi-year operations, 24/7 on-call, indefinite feature work. Studios sometimes do retainer work but it is not the model's strength.
- Budget is the binding constraint and you can accept the trade-offs that come with junior-heavy delivery.
- The work is genuinely commodity — a Shopify build, a WordPress site, a known framework re-skin.
How to evaluate a studio
If you have decided a studio fits the work, here are five questions that separate good ones from packaging:
- Will the people in this meeting write the code? If the answer is "we'll staff a team," it is an agency in studio clothing.
- How many people work here? Above twenty-five, the operating economics shift and the studio model becomes harder to maintain.
- What have you shipped in the last twelve months — links? Live products beat case studies.
- What would you refuse to take on? Studios with a practice have an opinion about what they don't do.
- Who owns the architectural decisions if we disagree? The answer should be specific and uncomfortable to give.
FAQ
Is a software engineering studio the same as a software agency?
No. Agencies scale headcount and rely on a pyramid of junior, mid, and senior staff. Studios cap headcount, keep the team senior-only, and deliver work with the same people who scoped it. The output looks similar; the economics and accountability are different.
How big is a typical software engineering studio?
Most are between four and twenty people. Below four, you have a freelance collective. Above twenty-five, the operating model usually drifts toward agency dynamics — sales separation, junior hiring, account management — even when the founders try to resist it.
How much does a software engineering studio cost?
Engagement costs vary by scope, but a useful frame is total project rather than rate. A senior-only studio for an eight-to-sixteen-week build typically lands in the $80K–$400K range. Agencies on the same work often land in a similar total range — they bill more hours at lower rates per hour.
When should I hire a studio instead of building in-house?
Studios are best for bounded, high-leverage work: a new product from zero to launched, an AI feature that needs senior judgment, an audit and refactor of a codebase that is slowing your team down. They are not a substitute for an in-house team for ongoing product operations.
What is the difference between a software studio and a software consultancy?
Consultancies primarily deliver thinking — strategy, assessments, architecture documents. Studios primarily deliver running software. A consultancy will tell you what to build; a studio will build it.
Kirin is a senior-only software engineering studio in Munich. We work with founders and product teams on AI product development, codebase audits, and design engineering.