Skip to content
All articles

What is an app studio?

Making appsPublished September 11, 20266 min read

What is an app studio?

An app studio is a small company that designs, builds and publishes its own apps, keeping ownership rather than delivering them to a client. This distinguishes it from an agency, which is paid to build someone else's product, and from a startup, which usually commits everything to a single app.
Overhead view of a small worktable with two laptops, paper sketches of phone screens and one lamp

The term gets used loosely, and a fair number of companies calling themselves app studios are agencies with better typography. The distinction that actually matters is ownership: who holds the product at the end.

Studio versus agency

An agency is paid to build a product someone else specified and will own. The client sets the brief, the agency delivers, the relationship ends or renews. Revenue is predictable and tied to hours or projects. The agency carries almost no product risk and captures almost none of the upside.

A studio decides what to build, funds it, ships it, and keeps it. There is no brief and no client sign-off; there is also no invoice at the end of the month. Revenue arrives later, from users, and only if the thing works. The studio carries all of the product risk and all of the upside.

Practically, this changes every decision. An agency is rewarded for delivering what was asked. A studio is rewarded for being right about what people want, which is a completely different skill and a much less comfortable one.

Studio versus startup

A startup and a studio both own what they build. The difference is concentration. A startup picks one product and commits everything — funding, headcount, several years — to making that one bet pay. Failure is usually terminal for the company.

A studio runs a portfolio of small bets and expects most of them to stay small. If four apps out of five never find an audience, that is not a crisis; it is the model working as intended, provided each attempt was cheap. The structural requirement is that the cost of being wrong stays low.

That requirement explains nearly everything else about how studios operate: small teams, short build cycles, no fundraising cycle to service, and a strong preference for shipping a narrow version early rather than a complete version late.

How the economics actually work

The honest version is that most studios are funded by one of four things, and it is worth knowing which:

  • Client work, part-time. The most common arrangement: contracting pays the bills while the studio's own apps are built in the remaining time. Slower, but nobody owns a piece of the outcome.
  • An earlier product that still earns. A single app that found its audience can fund several years of attempts at the next one.
  • Outside investment. Rare for studios, because investors generally prefer the concentrated bet of a startup to a portfolio of small ones.
  • Nothing at all. Evenings and weekends, until something works or the interest runs out.

None of these is more legitimate than the others, but they produce different studios. One funded by client work will ship more slowly and take stranger risks. One funded by investment will be pushed toward the single concentrated bet, and gradually stops being a studio.

What being small actually buys

The usual claim is speed, which is true but secondary. The real advantage is that the people making the decisions are the people doing the work. There is no translation layer between the person who noticed the problem and the person writing the code, and so nothing is lost in the handoff, because there is no handoff.

The second advantage is that the bar for trying something is low. A two-person team can spend a week on an idea, find out it is wrong, and drop it. In an organisation where a week of two people's time required a meeting to approve, that idea never gets tested at all.

The costs are real and worth stating plainly: no specialists, so everyone does work slightly outside their strength; no redundancy, so illness or burnout stops everything; and no distribution beyond what the app stores and your own audience provide.

How to tell which one you are looking at

  1. Look at the work page. A studio lists apps under its own name. An agency lists clients.
  2. Check the app stores. If the seller name on the listings is the company itself, it owns the products.
  3. Look for failure. A real portfolio contains apps that clearly did not take off. A page showing only successes is a case-study page.
  4. Read the about page for the word 'we'. Studios describe what they decided to make; agencies describe what they can make for you.

Where Hot Forge sits

Hot Forge is a studio in the strict sense: we design and publish our own apps from Paris, and most of them start as something we wanted and could not find. Globo, a camera app that identifies the place in front of you and tells you its history, is the one currently taking most of the heat.

Questions about this

What is the difference between an app studio and an app agency?
An app studio builds and owns its own products, earning from users after launch and carrying the full product risk. An agency is paid by a client to build a product the client specifies and owns, earning predictable project or hourly revenue and carrying little product risk.
Is an app studio the same as a startup?
No. Both own what they build, but a startup concentrates all of its funding and time into a single product, where failure is usually terminal. A studio runs a portfolio of small, cheap bets and expects most to stay small, which only works if each attempt costs little.
How do app studios make money?
Typically through subscriptions and paid downloads on their own apps, often subsidised in the early years by part-time client work or by an earlier app that still earns. Some take outside investment, though this pushes them toward the concentrated single-product bet of a startup.
How many people work at an app studio?
Usually between one and ten. The model depends on keeping the cost of a failed attempt low, which caps headcount. Small size also means the people deciding what to build are the people building it, removing the handoff between product and engineering.