Choosing who builds your product
Freelancer vs agency vs in-house team for an MVP
These labels describe how people work together, not their skill. A freelancer can be an excellent generalist. A studio can be one person. An agency can offer a stable team or rely on contractors. Ask who will actually do the work.
By Vaclav Skarka · Reviewed 5 September 2026. I run a solo studio and use Flutter and Supabase; the recommendations below explain that perspective and its limits.
Short answer
Choose a freelancer or solo studio for bounded work that fits one person’s capacity. Choose an agency when several disciplines need to work in parallel or continuity requires backup. Build in-house when ongoing software development is central to your business and you can support hiring and management.
Side-by-side comparison
| Factor | Freelancer | Solo studio | Agency | In-house team |
|---|---|---|---|---|
| Delivery capacity | One person’s availability; specialists may need coordination | One person’s availability, with responsibility for the agreed outcome | Multiple disciplines can work in parallel | Depends on the team you can recruit and retain |
| Best fit | Focused work or support for an existing team | A small, complete website or tightly scoped product | A wider build needing simultaneous design, engineering, and QA | A continuous product roadmap |
| Your management role | Agree scope and cover any gaps | Agree scope, provide feedback, and set priorities | Manage one delivery relationship and verify the assigned team | Own recruiting, people, priorities, and delivery |
| Continuity | Ask about absence and handover | Single-person dependency still exists | Can provide cover; confirm it is actually included | More resilient with documented, shared ownership |
| Cost | Usually limited organizational overhead | Limited overhead; often packaged scope | More overhead, potentially greater delivery capacity | Ongoing salary, recruiting, and management commitments |
| Ownership to check | Repository, accounts, documentation, licensing | Repository, accounts, documentation, licensing | Repository access, subcontractors, licensing, handover | Shared knowledge, access control, retention, documentation |
A solo studio is still one person
HLT3 is a one-person studio. That means you speak directly with me and I can make decisions quickly. It also means there is a limit to the work I can do at once. The word studio does not create extra capacity or a backup team.
A $500 one-page website or a tightly scoped app sprint can fit that model. Several products in parallel, round-the-clock support, or a large simultaneous migration usually need a broader team. I confirm availability and scope before an engagement.
When an agency is worth the overhead
An agency can be the right choice when design, engineering, content, testing, and delivery need several people at the same time. Backup during leave and a dedicated project manager can also be useful. Ask for the names, roles, and availability of the people assigned to your project.
Check whether those people are employees or subcontractors, how changes are priced, and how you will receive working software. An agency’s size does not by itself establish quality, but sufficient staffed capacity can solve problems a single person cannot.
When to hire in-house
If software is a lasting part of your competitive advantage and the roadmap continues year-round, a permanent team can give you stronger internal knowledge and priority control. You also take on recruiting, management, and retention.
External help can bridge the period before hiring. For that to work, your company should own the repository and service accounts from the beginning, and receive enough documentation for the next engineer to continue.
Questions worth asking every supplier
Who will write and review the code? What happens if that person is unavailable? What do we see each week? What is excluded? Where do the repository and infrastructure live? How do we end the engagement and hand the product to someone else?
Compare answers and relevant work rather than titles or day rates alone. A short paid engagement can also reveal whether the communication and delivery style fit before you make a larger commitment.
Choose Freelancer when…
- You need a particular skill or bounded implementation
- Someone on your side can own the remaining work
Choose Solo studio when…
- One builder can cover the agreed scope
- You value a direct relationship and accept one-person capacity
Choose Agency when…
- Several disciplines must work in parallel
- You need documented backup or a larger delivery team
Choose In-house team when…
- The roadmap is continuous
- You can invest in recruiting, management, and retention
Want a recommendation for your product?
Bring the constraints, not a predetermined stack. I will tell you what I would choose and why.
Ask the senior engineer