Small apps, owned end to end

Baran Labs doesn't take client work. Every app we publish is our own: conceived in-house, designed in-house, engineered in-house, supported in-house. When something we made breaks, the people who built it are the people who fix it.

This is a constraint, and it's also the entire strategy. It's worth explaining what it buys, because "independent studio" has become a phrase that can mean almost anything.

What no client work buys

Client work pays well and teaches fast, and plenty of good studios are built on it. What it costs is the roadmap. When revenue comes from other people's products, your best people are always on other people's problems, and your own products get the hours left over — which rounds to none.

Keeping the roadmap fully ours means we can make decisions that only pay off on a long horizon: pricing an app honestly instead of optimizing a funnel, spending a month on an export feature most users touch once a year but need desperately when they do, or declining to ship something in November because it will be better in February. Nobody outside the building gets a vote.

Small surface area is a feature

Every app we make is deliberately small — one job, done properly. Hometric's job is knowing what your home contains and whether you're covered for it. It does not track your packages, remind you to water plants, or offer a chat assistant.

The discipline isn't aesthetic. Surface area is the thing that kills small teams: every feature shipped is a feature supported, forever, across OS updates and edge cases and support mail. A small team that ships a sprawling app has signed up to maintain something larger than itself. We'd rather our apps be described as "it does one thing and it works" than "it does everything, mostly."

Support is part of the product

Support email at most software companies is a cost center with a deflection metric. Ours goes to the people who built the app, and we answer within a business day, Monday to Friday. This is partly principle and partly self-interest: support mail is the highest-signal product feedback that exists, and reading it ourselves is how the roadmap stays honest.

The same goes for the quiet parts — privacy policies written to be read, prices stated without asterisks, data that exports cleanly if you leave. None of this is growth hacking. All of it compounds.

Shipping in private

We don't pre-announce. Apps appear on this site when they're on the App Store, not before. Roadmap theater — public boards, "coming soon" pages, launch countdowns — creates an audience for promises, and promises are the one inventory we don't want to carry. We work in private until a product is ready, then we ship it and stand behind it.

One app is live today. More are in progress, and we'll say exactly nothing about them until they're real. If that patience reads as slowness, that's fine — the apps are meant to still be here, and still supported, years from now. That's the model.