Fractional CTO vs product studio vs in-house team.
Three engagement models, three failure modes, three sweet spots. A side-by-side from a studio that has worked alongside all three — and the single question that decides it.
Fractional CTO.
What it is: One senior person, 1–3 days/week, doing strategy, hiring, architecture, and review. Cost: $8–25k/month. Engagement: usually 6–18 months.
Sweet spot: You have engineers but no senior leadership. You need someone to make architectural calls, hire the next 3 people, and represent engineering to the board. The fractional CTO does almost no implementation themselves.
Failure mode: Used as a "let's hire someone to figure out what to build" stand-in. They can't, by themselves, build the thing. If you don't have a team, a fractional CTO is paying $15k/month for advice on a thing that doesn't exist yet.
Product studio.
What it is: A small group (3–6 people) ships a defined product or surface in a finite window (4–14 weeks). Cost: $60–700k per engagement, by scope. Engagement: ends with a hand-off.
Sweet spot: You have a clear hypothesis to test or a product that needs to exist by Q3. The studio brings team, methodology, and the discipline to ship in the window. This is what Oviompt does.
Failure mode: Used for ongoing operations. A product studio is wrong for "we need someone to keep the platform running." Studios are bad retainers. They're great ships.
In-house team.
What it is: Full-time employees, your stack, your process. Cost: $200–600k per engineer per year fully loaded. Engagement: indefinite.
Sweet spot: You have a product with a multi-year roadmap, predictable scope, and the volume to keep 5+ engineers busy. The in-house team is the only model that compounds knowledge.
Failure mode: Used too early. Hiring three engineers before you have a validated product means you're paying $1.5M/year to learn what a $150k studio engagement could have taught you in 8 weeks. The other failure: hiring without senior leadership; you'll get a stack but no shape.
The question that decides it.
"What does done look like, and when?"
- "We need to ship something specific by [a date], then maintain it." → Studio for the build, in-house for the maintenance.
- "We have engineers but no compass." → Fractional CTO for the compass; keep the engineers.
- "We have a multi-year roadmap and money." → In-house, plus a fractional CTO if you don't have senior leadership yet.
- "We don't know what we're building." → None of the above. Spend two weeks defining "done." Then come back.
The hybrid that often wins.
The combination we see most in 2026: fractional CTO + product studio for the build + in-house for ongoing. The CTO sets direction and hires; the studio ships the product in a finite window; the in-house team takes it and runs. Each model does what it's actually good at. None pretends to be the others.
File an intent if a studio engagement is the right fit for the question you're answering.