Should I hire a freelancer, an agency or a studio to build my MVP?
By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published
Mctaba runs a software studio and founder programmes. This guide is written to be useful whether or not you ever work with us.
Choose by how clear your scope is and how much product judgement you need. Hire a freelancer when the scope is small, written down and you can manage the work. Hire an agency when the specification is fixed and you want a team to deliver it. Hire a studio when you need help deciding what to build, then building it.
Three quotes arrive for the same product. One is from a developer a friend recommended, and it fits on a single WhatsApp message. One is a twelve-page proposal from an agency with a project manager and a timeline in colour. The third is from a studio that wants to spend two weeks on scope before it will give a number at all.
The prices are far apart, and the natural instinct is to compare them. That is the wrong comparison. The three are not selling the same thing. One is selling hours of a skilled person. One is selling delivery of a specification. One is selling a product outcome. Which you should buy depends on your situation, and mostly on one question: how much of the thinking have you already done?
What is the difference between a freelancer, an agency and a studio?
The difference is who carries which risk.
A freelancer is one person who writes code for you. You carry almost all the risk: you decide what to build, you manage the work, you test it, and if they fall ill or take a full-time job, the project stops.
An agency is a team that delivers what the specification says. The agency carries delivery risk: it replaces people who leave and coordinates design, code and testing. You still carry the product risk. If the specification was wrong, you get exactly the wrong thing, on time.
A studio is a team that takes part in deciding what to build as well as building it. It carries some of the product risk with you: it will question the scope, cut features, and design around what customers do. You pay for that judgement, and you give up some control over the details.
The labels are loose. Some agencies think hard about product and some studios only take orders. Judge by how they behave in the first meeting. Do they ask about your customers, or only about your features?
Which one fits my situation?
Find your row in each line of this table. The column where most of your answers fall is your answer.
| Your situation | Freelancer | Agency | Studio |
|---|---|---|---|
| How fixed is your budget? | Small and flexible. You can absorb a surprise | Fixed, and you need a fixed quote against a fixed specification | Fixed, and you want help fitting the scope to it |
| How defined is the scope? | Small and written down. One or two screens, one job | Fully specified, with designs or detailed requirements | A clear problem and proof of demand, but no specification |
| Do you need product thinking? | No. You or an adviser supply it | A little. You mostly need delivery | Yes. You want someone to challenge what you build |
| Who manages the work? | You, every week | Their project manager, reporting to you | Their team, with you in regular reviews |
| What happens after launch? | By arrangement, if they are still available | A separate maintenance contract | Often offered, on terms you should ask for in writing |
| What if one person leaves? | The project stops | They replace the person | They replace the person |
Two patterns cause a lot of the bad outcomes.
The first is the founder with a vague idea and a freelancer. Nobody is doing the product thinking, so the freelancer builds what was said instead of what was needed, and the founder pays twice.
The second is the founder with a vague idea and a fixed-price agency contract. The agency has to guess the scope to price it. Every later change becomes a change request, and the relationship turns into an argument about what was included.
If your scope is vague, fix the scope first. That is true whoever you hire.
What should I ask before I hire?
Ask different questions of each, because each fails in a different way. There is a longer list in questions to ask before hiring a software studio. These are the ones that matter most.
Ask a freelancer
- What else are you working on, and how many hours a week will I get?
- Can I see something you built that is live and has real users?
- What happens to my project if you take a full-time job?
- Will you work in a code repository that I own, from the first day?
- Have you integrated M-Pesa or another payment provider before, and can I see it working?
Ask an agency
- Who will write my code? Can I meet them before I sign?
- Is any of the work passed to another company?
- How do you handle a change to the scope, and what does it cost?
- What exactly is in the fixed price, and what is not?
- What does support look like in the three months after launch?
Ask a studio
- Which of my features would you cut, and why?
- How do you decide what goes into a first version?
- Who makes the final call when we disagree about the product?
- How will I see progress every week?
- If I want to move the product to my own team later, what do you hand over?
Listen to the answers, and notice the questions that come back. A builder who asks nothing about your customers will build whatever you say. Sometimes that is what you want. Usually it is not.
What must the contract say?
Three things, whoever you hire: who owns the code, how payment follows progress, and what the handover contains.
Who owns the code. Under section 31 of Kenya's Copyright Act, copyright in a commissioned work is deemed to be transferred to the person who commissioned it, unless the parties agree otherwise. That helps you, but do not rely on it alone. Developers reuse their own earlier code, open-source libraries and paid components, and a contract can limit the transfer. Have the contract say in plain words that the company owns everything written for the project once it is paid for, list anything the builder is bringing that stays theirs, and confirm you have a licence to keep using those parts.
Milestones. Tie each payment to something you can see working, not to a date or a percentage. "Customer can register and pay on M-Pesa in the test environment" is a milestone. "Backend 60% complete" is not. Keep a final payment back until the handover is done.
Handover. List what you will receive: the code in your repository, the database, the login details for every service, and a short document that explains how to run and deploy the product. Add a period after launch during which defects are fixed without a new invoice.
Then a practical point that sits outside the contract. Open the accounts yourself: the code repository, the hosting, the domain, the Daraja or Paystack account, the app store accounts. Use a company email address and invite the builder in. A product built inside the builder's accounts is a product you rent.
Where does Mctaba sit, and when is a studio the wrong choice?
Mctaba is a software and AI development studio first, with training second. Its record so far: 50+ products shipped, 30+ clients, and more than KES 50 million in sales generated for clients by products Mctaba built. The founder offer is described at MVP for founders.
A studio, this one included, is the wrong choice in three cases. If your scope is one small, well-defined job, a good freelancer will do it for less. If you already have a product lead and a full specification, you are paying for judgement you will not use. And if you have not yet tested whether anyone will pay, no builder should take your money. Test demand first.
What does this choice mean for the product?
It decides what kind of first version you get. A freelancer will give you what you described. An agency will give you what you specified. A studio will give you what you and it agreed the customer needs, which is often smaller than what you first asked for.
None of those is wrong. The mistake is choosing on the quote alone and discovering afterwards which of the three you bought. Decide how much of the thinking is done, be honest about how much time you can give each week, and pick the arrangement that covers the gap.
Key takeaways
- The question is not who is cheapest. It is who carries the risks you cannot carry yourself.
- A freelancer suits a small, written scope and a founder who can check the work every week.
- An agency suits a fixed specification that needs several skills at once.
- A studio suits a founder who needs product thinking as well as code, and support after launch.
- Whoever you choose, the contract must say you own the code, tie payment to working milestones, and describe the handover.
- Hold every account, from the code repository to the domain, in your company's name from the first day.
Frequently asked questions
- Is a freelancer always the cheapest way to build an MVP?
- The quote is usually the lowest, but the quote is not the cost. Add the hours you will spend managing, testing and chasing, and the cost of a rebuild if the work stops halfway. A freelancer is the cheapest route only when the scope is small and you can supervise it closely.
- Can I begin with a freelancer and move to a studio or an agency later?
- Yes, if the handover is clean. That means the code is in a repository you own, there is a short document explaining how to run it, and the contract gave you ownership. Without those, expect a new team to quote for a rebuild instead of taking over someone else's work.
- Should I give the builder equity instead of paying cash?
- Be careful. Equity is the most expensive money you have, and a builder paid in shares has little reason to finish quickly. If you do offer shares, make them vest against delivered milestones and get legal advice first. For a first version, paying cash for a small scope is usually cleaner.
- How do I check someone's past work?
- Ask for two products that are live today and use them yourself. Then ask to speak to the people who paid for them, and ask those people one question. Would you hire them again? A builder who cannot arrange that conversation has told you something.
- What if I cannot write a specification?
- Then you are not ready for a fixed-price build by anyone. Either pay for a short scoping exercise first, which produces a written scope you own and can take anywhere, or choose a partner whose work includes deciding what to build with you.
Sources
- Copyright Act (Cap. 130), section 31, First ownership of copyright, Kenya Law (National Council for Law Reporting). Checked on 19 November 2026.
- The Lean Startup: How Today's Entrepreneurs Use Continuous Innovation to Create Radically Successful Businesses, Eric Ries (book, 2011). Checked on 19 November 2026.
