Studio vs agency vs freelancer vs in-house.
Four options when you need software shipped. They are not interchangeable. This page lays out the cost, speed, control, and risk of each so you can pick the one that fits your situation, even if the answer turns out not to be us.
Side by side.
| Dimension | Product studio (Oviompt) | Marketing agency | Freelancer | In-house team |
|---|---|---|---|---|
| Sells | Finished software, finite scope | Campaigns and ongoing services | Hours or tasks | Salaried capacity |
| Pricing model | Fixed-fee per engagement (USD ranges on the page) | Monthly retainer or hourly | Hourly or per-task | Salary + benefits + equity |
| Typical cost | $3k–$500k per engagement | $8k–$25k / month, ongoing | $50–$250 / hour | $120k–$280k / yr per engineer |
| Time to start | 2–4 weeks (next available slot) | 1–2 weeks | Days | 2–6 months (hiring cycle) |
| Time to ship v1 | 6–14 weeks (First Ship MVP) | Variable, often open-ended | Variable, dependent on freelancer | 3–9 months from hire to ship |
| Decision-making | Studio decides architecture and stack | Buyer decides; agency executes | Buyer decides; freelancer executes | Buyer's team decides everything |
| Risk | Capped at engagement fee | Unbounded if retainer keeps renewing | Bounded but quality-variable | High up-front; pays off over years |
| Best for | First version, regulated builds, multi-surface | Ongoing growth marketing, content, ads | Narrow, well-specified work | Long-lived core product |
| Worst for | Open-ended work without a defined outcome | One-off product builds | Strategic decisions and architecture | Anything you need shipped this quarter |
Five common situations.
You're a first-time founder with an idea and no team.
You don't have a CTO. You don't know what stack to use. You have a small budget ($15k–$50k) and you want a working product to test with real users.
Pick a studio. A freelancer will execute whatever you ask, but you don't know what to ask. An in-house hire is months away and tens of thousands of dollars before you ship anything. An agency will sell you a website, not a product.
You have a CTO and a team. You need one specific surface shipped.
Your team is busy on the core roadmap. You need a regulated voice-AI feature, or an offline-tolerant floor tool, or a CLI for your buyer-side platform team. The work is bounded and the stack is yours.
Pick a studio. A freelancer can do it but won't write the decision register. An in-house team has the wrong cost shape for a 10–14 week project. An agency doesn't ship software like this.
You need ongoing growth marketing — content, SEO, ads, social.
The work is recurring. The deliverable is impressions and conversions over time, not a finished thing.
Pick an agency. A studio is the wrong shape for ongoing work. We will do an SEO/AEO build (one engagement), but we won't run your campaigns.
You know exactly what you want — a single component, a small fix, a one-off integration.
You have the spec. You have someone internally who will check the work. You're paying for hands.
Pick a freelancer. A studio's overhead doesn't make sense for a 20-hour task. We will refer you to one of three or four freelancers we trust if you ask.
The product is your business and you need to own it forever.
You're series B+. The roadmap stretches 3–5 years. You're hiring senior engineers anyway.
Pick in-house. Hire the team. Use a studio for the first version of new surfaces (AI, mobile, a new admin tool) where the in-house team doesn't have the muscle yet, and hand off when the surface stabilizes.
The hybrid that works.
The most common pattern we see in practice is studio → in-house. The studio ships v1 in a finite window. The buyer hires their first engineer somewhere between week 8 and week 12 of the engagement. The studio writes the hand-off doc on day one and updates it weekly. By the time the engagement ends, the in-house engineer owns the product, has the decision register, and starts shipping their second feature.
This pattern beats both alternatives. Skipping the studio means six months of in-house thrash before v1 ships. Skipping the in-house hire means an open-ended dependency on the studio. Doing both, in order, gets to a working product fast and a sustainable team after.
Frequently asked.
How much does a product studio cost compared to an agency?
At Oviompt, engagements range from $3k (audit) to $500k (multi-surface build). Comparable agency engagements often run on retainer ($8k–$25k per month, ongoing). The studio model has a defined ceiling; the agency model accumulates cost over time. For a one-time product build, the studio is almost always cheaper in total dollars.
Why not just hire a freelancer for everything?
Freelancers are great when you know what good looks like. They are not great when you don't. A freelancer will execute your decisions. A studio will make the decisions with you, write them down, and ship against them. If you have a CTO who can spec the work, a freelancer is cheaper. If you don't, a studio is cheaper because it doesn't waste your runway on bad decisions.
Why not hire in-house from day one?
Three reasons. First, hiring senior engineers takes 2–6 months. Second, your first hire defines your stack and culture for years; it is a high-stakes decision to make before you have a product to validate it against. Third, paying a salary before there is anything to ship burns runway with no measurable outcome. Use a studio to ship v1, then hire against the proof.
What kinds of work do you decline?
Open-ended retainers. Hourly billing. Work with no defined outcome. Single-page websites. Pure design work without engineering. Crypto and gambling. Anything that requires us to misrepresent who we are.
How do I know which option fits me?
Submit an intent (low-friction tab is fine). We will reply in plain language within 48 hours and tell you if a studio is the right fit, or refer you to a freelancer or agency we trust if it isn't. We turn down work that doesn't fit; the referral costs us nothing and saves you weeks.