Choosing a partner · 6 min read

Product studio, dev shop or freelancer: who should build your software?

Published 3 March 2026 · Updated 2 September 2026 · By Sam Fourie, Niddo

A freelancer is right for a small, well-specified piece of work you can manage yourself. A dev shop is right when you already own a detailed spec and someone to run the project. A product studio is right when the product still has to be thought through as well as built, and you want one team accountable from the first screen to the running system.

The three models, side by side

	Freelancer	Dev shop	Product studio
Who decides what to build	You	You, from your spec	You and the studio, in scoping
Design	Usually not included	Sometimes, often subcontracted	Included, before code
Project management	You	A project manager, billed	The team that builds it
Pricing	Hourly or daily	Hourly, or fixed on your spec	Fixed on an agreed scope
Speed to first release	Fast for small work	Depends on the spec and the queue	Weeks, in visible increments
Risk of building the wrong thing	High, unless you are a product person	High, if the spec is wrong	Lower: scoping is the first deliverable
After launch	Depends on availability	A new statement of work	Run it with you, or hand over documented code
Typical fit	A feature, a fix, a small site	Executing a known plan at scale	A product or platform from idea to live

When a freelancer wins

You know exactly what you want, it fits in a few weeks, and you can review the work yourself. A landing page, a well-defined integration, a bug fix, a component. Good freelancers are excellent value here, and the best ones will tell you when the job is bigger than they should take alone.

The risk shows up when the work grows into a product: design, testing, deployment and support become your job, and continuity depends on one person's calendar.

When a dev shop wins

You have a detailed specification, an internal product owner, and you need capacity rather than judgement. Dev shops are built to execute a plan with many hands, and for large, well-defined programmes that is exactly right.

The risk is the spec itself. A dev shop is paid to build what is written down, not to question it, so if the plan is wrong the build is wrong at full price. Design is often a separate vendor, and the handoffs between them are where products lose their shape.

When a product studio wins

You have a business problem and a direction, not a finished spec. You want the product thought through, designed, engineered and launched by the same people, priced as one figure, by a team that has shipped and run products of its own, so the decisions along the way are made the way an owner would make them.

The trade-off is that a studio will push back. Scoping is a real phase, some of your feature list will move to version two, and the studio will want a decision-maker on your side who can answer quickly.

Five questions to ask anyone before you sign

Have you built and run a product of your own? The answer tells you whether they understand what happens after launch.
Who does the design, and when? "After the build" or "a partner agency" are warning signs for a product.
How is this priced, and what happens when scope changes? You want a fixed figure and a written change process.
Who owns the code, the repositories and the accounts? The only acceptable answer is you, from day one.
What do the first two weeks look like? If you cannot click something by then, the plan is document-heavy and risk-heavy.

Where Niddo fits

Niddo is a product studio in Johannesburg. We scope, design, engineer and launch software for companies in South Africa and worldwide, we price it as one fixed figure, and we run our own product, PanelDesk, which is how we know what a product needs after the launch party. If that is the shape you need, tell us what you are building.

Questions