Decisions5 min read
Freelancer, agency or one accountable technical lead: who should build your app?
By Sannan MalikPublished
Short answerA freelancer suits a small, well-defined task you can manage yourself. An agency suits a large build that needs several specialists at once and a budget for project management. One accountable technical lead suits a founder who wants one senior person answering for the whole app, from scope to store launch. Whichever you choose, put code ownership, accounts in your name and a written scope in the contract.
Who answers when something goes wrong
When founders compare ways to get an app built, they usually compare price. The more useful comparison is accountability: when something goes wrong in month two, who is responsible for fixing it, and who do you call?
A freelancer is responsible for the piece of work they were given. An agency is responsible as a company, through an account manager or project manager. A technical lead is one senior person responsible for the whole product: the scope, the architecture, the build, the release and the decisions in between. The table below shows where the responsibility and the management work sit in each.
The three models side by side
Freelancers and agencies vary a lot, so treat this as a list of things to ask about.
| Freelancer | Agency | One accountable technical lead | |
|---|---|---|---|
| Who is accountable | For their task; you own the overall result | The company, through a manager | One person, for the whole product |
| Who you talk to | The developer doing the work | A project or account manager | The person making the technical decisions |
| Cost structure | Usually hourly or per task | Often a project quote that includes management overhead | Usually a fixed price against a written scope, or a retainer |
| Continuity risk | High if they become unavailable | Lower; staff can be replaced, but the people on your project may change | Depends on documentation, code ownership and handover |
| Breadth of skills | Often one specialism | Several specialists in-house | Broad across design, app, backend and release, with specialists added where needed |
| Your management load | High: you coordinate and review | Low to medium | Low: you decide, they plan and build |
Small, bounded jobs: a freelancer
A freelancer is a good choice when the job is small and clearly bounded, and you, or someone on your team, can judge the work. Fixing a set of bugs, adding a screen to an app that already exists, designing an icon set, or connecting one API are all reasonable freelance tasks.
It gets harder when you hire several freelancers for one product: a designer, an app developer and a backend developer. Somebody has to make the pieces fit, and if nobody technical is on your side, that somebody is you. That coordination is a job in itself, and it needs someone technical.
Large parallel builds: an agency
An agency makes sense when the build genuinely needs several people working at the same time: a large product with separate web, mobile and backend teams, a deadline that one person cannot meet, or a company that wants a supplier with a formal structure behind it.
You pay for that structure. A share of the quote covers project management, account management and the agency's overheads, which is fair when you need them and wasteful when you do not. Ask who will actually work on your app, whether they will stay on it to launch, and whether you can speak to the developer directly when a question is technical.
A first app with one owner: a technical lead
This model suits founders and small businesses building a first app or business system who want a known price and one person who answers for everything. You describe the business problem; the technical lead turns it into a scope, makes the architecture decisions, builds it or directs the build, and takes it through store review.
The weakness is continuity: everything rests on one person. The fix is the same as for a freelancer, only enforced from day one. The code lives in your repository, the accounts are in your name, and the setup is documented, so another developer could pick it up if they ever had to. If you are unsure how to pay for the work, the fixed price vs hourly guide covers that decision separately.
What to put in the contract, whichever you choose
Put these in the contract whoever you hire. If a supplier will not agree to one of them, ask why before you sign.
- Code ownership: the source code and designs belong to you once paid for, and live in a repository you own.
- Accounts in your name: Apple developer, Google Play, hosting, domain, database and third-party services are registered to you, with the developer added as a user.
- A written scope: screens or a screen count, user roles, features, and what is explicitly excluded.
- A change process: changes are written down and priced before anyone builds them.
- Who does the work: named people, and what happens if one of them leaves.
- Handover: credentials, setup notes and a short document explaining how to build and deploy the app.
- Support after launch: what is covered, for how long, and what is billed separately.
How I work, and where CTO consulting fits
I work as the third option, one accountable technical lead. You get a fixed price against a written scope ($999, $1,699 or $2,500 depending on size), the app goes out under your own store accounts, and the code is yours. Hosting, third-party fees and maintenance after launch are billed separately, and a few features, such as custom AI or complex payment gateways, get their own quote.
If you already work with a freelancer or an agency and want a senior person on your side, that is what my CTO consulting is for: architecture and code reviews, vendor evaluation and development planning, as a fixed-scope engagement or a monthly retainer.
Questions
- Is it safe to hire one person to build my whole app?
- It can be, if the contract protects continuity: the code in your repository, every account in your name, and written setup notes. Those make the project transferable to another developer if needed.
- Why are agency quotes often higher than freelancer quotes?
- An agency quote usually includes project management, account management and company overheads as well as development. Whether that is worth it depends on how much coordination your project needs.
- Can someone independent review the work my agency or freelancer is doing?
- Yes. A code and architecture review gives you a written assessment of what is solid, what is risky and what to fix first, without changing who builds the app.
Sannan Malik is a software architect and product builder with 8+ years in software, CEO of Alpha Notic FZC and a Certified Scrum Product Owner. He builds mobile apps and business software for companies in the UAE, UK and US.
