Solo builder or agency?
You have an idea, a budget, and two ways to spend it. This is the honest version of that trade-off — written by one of the two options.
What you are actually choosing between
An agency sells you a team: an account or project manager, a designer, one or more developers, a QA pass. A solo builder sells you one mind holding the entire product — strategy, design and code — with nothing handed between people.
Both models ship working software. They fail differently, and they fail at different sizes. The useful question is not which one is better. It is which one fails in a way you can afford.
Side by side
| One accountable builder | Agency | |
|---|---|---|
| Who makes product decisions | The person writing the code | A product lead or PM, coordinating between roles |
| Handoffs between people | None — one person holds the brief, the design and the code | Brief → design → implementation |
| Price for a first version | Fixed for a landing page or an MVP ($2,500 / $5,000); larger builds are scoped first, then fixed in writing | Quoted per project, commonly after a paid discovery phase |
| Time to something live | 7–14 days for a landing page or a full MVP | Usually measured in months |
| Parallel workstreams | One at a time | Several at once |
| If the individual is unavailable | Work pauses; codebase and handoff notes come to you | Another person is assigned |
| Paperwork | One agreement, one invoice, one point of contact | Procurement-friendly, multiple named resources |
| After launch | 30 days of fixes included, then a separate engagement | Usually a retainer |
When an agency is the right call
There are projects I turn down. These are them.
- Several workstreams have to run in parallel against one deadline — native mobile, web and brand at the same time.
- Procurement requires a company entity, insurance, or a formal statement of work naming multiple resources.
- The work cannot pause for any reason, including illness. You are buying guaranteed continuity, not a build.
- You need sustained capacity for years rather than a product shipped once.
If one of those describes your situation, hire an agency. I would rather say so on the first call than take the project and be the wrong answer.
When one builder is the right call
- The scope genuinely fits one person: a landing page, an MVP, a focused platform.
- You want the person making product decisions to be the person writing the code.
- You are non-technical and would rather not write a specification before anyone will quote you.
- Speed matters more than headcount — you need something real in front of users this month.
The real risk of hiring one person
The honest objection is not quality. It is what happens if the one person disappears. That risk is real, so here is what stands against it.
- Scope and price fixed first
- What gets built, to what specification, at what price — agreed in writing before any work begins. No renegotiation mid-build.
- Paid in two halves
- 50% to start, 50% on delivery. If either side ends the engagement, work completed up to that point is invoiced and all in-progress code and assets are handed over within five business days.
- A documented exit
- If I become unavailable mid-project you receive a documented codebase, handoff notes, and help moving to another builder. Not a dead end.
- Two clients maximum
- Never more than two active projects. If both slots are full you get your queue position and the earliest start date, not a vague promise.
- Delays cost you nothing
- If a delay is caused by me, the timeline extends at no extra cost. Same deliverables, same price, delivered later.
- 30 days after launch
- Bugs introduced during the build are fixed at no charge for 30 days after go-live.
What one person has shipped
Six products built end to end, including a national remote-employment portal and several bilingual platforms serving Arabic and English users.
See the case studiesStill think one builder fits?
Tell me the idea and the budget. You get a fit-or-no-fit answer within 48 hours — and if an agency is the better answer, I will tell you that instead.