BYD TechThe short answer
A freelancer builds what you ask for, an agency or studio builds and runs the project with a team, and a fractional CTO makes and reviews technical decisions part-time but usually does not write most of the code. For a first version, a non-technical founder usually needs both building and judgment: a studio that takes both on, or a freelancer paired with a fractional CTO who reviews the work. Whichever you choose, keep the code, the accounts and the written reasons for decisions in your company, so you can change partners without starting over.
Key points
- Building and deciding are different jobs. Know which one you are hiring for.
- A freelancer is the most direct option and the most exposed if that one person leaves.
- An agency brings a team and its own review, but the knowledge stays with the agency unless it is written down for you.
- A fractional CTO gives you technical judgment and review, not usually the hands to build.
- A full-time CTO or technical co-founder fits once there is a product and a team to lead.
- Whoever you choose, the repository and accounts belong to your company and decisions are written down.
What each option actually does
The names get used loosely, so start with the work, not the title.
- A freelancer is one independent developer or designer. They build the parts you agree on. Some are senior and will push back on a bad idea; many will build what the ticket says.
- An agency or studio is a company with a team: usually design, engineering and someone who runs the project. It takes on a defined piece of work, decides how to build it, and delivers it.
- A fractional CTO is a senior technical leader who works for several companies part-time. They set technical direction, choose the approach, review other people’s work, help hire, and speak for the technology to investors. Most do little of the day-to-day building.
- A full-time CTO or technical co-founder is inside the company, with a long-term stake in it. They build at first and later lead a team. How to find a technical co-founder covers that route.
| Freelancer | Agency or studio | Fractional CTO | Full-time CTO or co-founder | |
|---|---|---|---|---|
| Main job | Builds agreed pieces | Designs, builds and runs a project | Makes and reviews technical decisions | Owns the technology and the team |
| Who decides how it is built | You, unless they are senior and you let them | The agency, inside the scope you agree | The fractional CTO, with you | The CTO |
| Who reviews the work | Nobody, unless you arrange it | The agency’s own engineers | They review others; their own advice needs a second opinion | The CTO, then the team they hire |
| If they leave | Work stops until you find someone new | Another person on their team can step in | You keep the builders but lose the judgment | A serious loss; the company has to replace a leader |
| Where the knowledge sits | In one person’s head unless written down | With the agency unless handed over | With the CTO unless written down | Inside the company |
Who makes the technical decisions
Every product needs someone to decide things a non-technical founder cannot judge alone: how the system is structured, what to build and what to buy, what is safe to skip in a first version and what is not. If nobody is given that job, it still gets done, just by whoever writes the code that day.
- With a freelancer, the decisions are yours unless you hand them over. That works if the freelancer is senior and you agree in writing that they own the technical choices. It goes wrong when you are deciding things you cannot evaluate.
- With an agency, the decisions sit with the agency inside the scope. Ask to see the important ones written down, with the reasons, and to be asked before anything that is hard to undo.
- With a fractional CTO, deciding is the job. The risk is the opposite one: decisions made by someone who is not there for the consequences. Ask them to write each decision down so whoever builds it, and whoever follows, can see why.
Who checks the work
Code review is a second engineer reading a change before it goes in. Google’s engineering guidance describes its purpose as making sure the health of the codebase improves over time. Without it, problems pile up quietly, and a non-technical founder only finds out when something breaks or a new engineer refuses to work on it.
A solo freelancer has no second engineer by default. An agency should review its own work; ask who reviews it and whether you can see the reviews in the repository. A fractional CTO is often brought in exactly to be that reviewer for a freelancer or an outside team. The same applies to code written with AI tools, which can look finished and still have gaps; see Vibe coding to production.
What happens when someone leaves
People leave projects: they take another job, get sick, or the relationship ends. Plan for it on day one, whichever option you choose.
- The repository is in an organization your company owns, and the builders are added to it. GitHub, for example, recommends at least two organization owners; make both of them people from your company.
- Cloud, domain, app store and third-party accounts are in your company’s name, with your people as owners.
- The important decisions are written down. Michael Nygard’s architecture decision records are a light way to do it: a short note in the repository for each significant decision, with its context and consequences, so a newcomer neither accepts it blindly nor reverses it blindly.
- Someone other than the original builder can build and deploy the product from the repository and its notes alone. Test that before you need it.
Legal ownership matters too. In many countries an employee’s work belongs to the employer by default, while code written by a freelancer or an agency belongs to its author until it is assigned to you in writing. The details by country are in Who owns the code when you hire a developer or agency?.
What drives the cost
Comparing headline rates between these options is misleading, because each one buys a different mix of building, deciding and managing. What actually moves the cost:
- How clear the scope is. Vague scope costs more with every option, because someone pays for the discovery, either up front or as rework.
- Who does the managing. With freelancers, you or someone you hire coordinates the work. With an agency, coordination is part of what you buy.
- Seniority. Senior people cost more per unit of time and usually waste less of it.
- How much judgment you need. A product with hard technical choices needs more senior decision-making than one assembled from well-understood parts.
- Review and quality. Skipping review is cheaper at first and more expensive later, as explained in What is technical debt?.
- Handover. Documentation, tests and a clean repository take effort to produce, and save far more when the team changes.
Which fits which stage
| Your situation | What usually fits | Watch out for |
|---|---|---|
| Testing an idea, no product yet | Often no developer at all; validate first, or a freelancer for a prototype | Building before anyone has asked for it |
| First version, non-technical founder | A studio that designs, builds and reviews, or a freelancer paired with a fractional CTO | A single builder with nobody checking the work |
| Small, well-defined additions to a working product | A trusted freelancer | Knowledge piling up in one person |
| A project in trouble that needs rescuing | A fractional CTO or a studio to assess it first, then decide who builds | Committing to a rewrite before anyone has read the code |
| Traction and a team to build | A full-time CTO or a technical co-founder, with outside help where useful | Hiring a leader before there is anything to lead |
For a rescue, start with an honest assessment of the code and the accounts before choosing who continues; Rewrite vs refactor covers that decision. For a first version, How to build an MVP covers what to include, and How to choose a software development company has the questions to ask any team.
BYD Tech is a studio: the founders are on the calls, the code lives in the client’s GitHub from day one, and AI-drafted work is reviewed by an engineer. MVP development describes how a first version starts.
Sources
Checked when this guide was written.
