An independent freelancer
You have a clear, bounded task (a landing page, a fix, a feature) in one discipline, and you're comfortable managing the work and the decisions yourself.
A guide to building
Different ways to build. Find the right one.
Every product needs the right people behind it. Whether you're hiring a freelancer, working with an agency, building an internal team, or partnering with a product studio, each approach comes with different strengths, costs, and responsibilities.
01Introduction
There's no best option. There's a best fit.
This guide compares four common ways to get a product built: an independent freelancer, a traditional development agency, an in-house engineering team, and BlindspotLab. Each suits different projects, budgets and stages.
It's written by BlindspotLab, so read it with that in mind. Other providers vary widely, so the descriptions are of what is typical, not of any one firm, and the guide says plainly where another option is the better choice.
02Side by side
Four ways to build, compared.
Twelve things that matter when choosing who builds your product. Where it depends on the provider or the agreement, the table says so.
| Criterion | Independent freelancer | Traditional development agency | In-house engineering team | BlindspotLab |
|---|---|---|---|---|
| Typical engagement model | An hourly, daily or per-project contract with one person. | A project contract or retainer with a team, usually through an account or project manager. | Salaried employees, with recruiting, benefits and management on your side. | A package agreed in a written scope, or a monthly retainer, led by the founder. |
| Pricing transparency | Varies by provider. Rates are often public; the total depends on hours. | Varies by provider. Usually quoted after discovery rather than published. | Salaries are known; the full cost of recruiting, tools and management is often higher than it looks. | Public starting prices for every package. The final price is fixed in the written scope. |
| Product strategy | Depends on the person. Many focus on delivering a defined brief. | Often available as discovery or strategy work, sometimes a separate paid phase. | Strong once the team knows the business, if product leadership is in place. | Part of every engagement: what to build first, and what to leave out. |
| Design and development | Usually one discipline. A full product may need several freelancers. | Full teams across design, engineering and testing, able to work in parallel. | Whichever disciplines you hire for. | Product design and web engineering from one operator. Native mobile and brand identity sit outside the core offer. |
| Engineering accountability | One person, which is clear, but depends on their availability. | Contractual, through the agency. The people doing the work may change. | Direct and ongoing, through your own management. | The founder is accountable for the build, from scope to deployment. |
| Communication | Direct with the person doing the work. | Usually through an account or project manager. | Direct and daily, inside your organisation. | Direct with the founder who builds the product, at agreed milestones. |
| Flexibility | High. Easy to start, adjust or stop. | Moderate. Changes go through the contract and change requests. | High day to day; slow to scale up or down. | Moderate. Changes are written up with price and schedule; retainers are monthly. |
| Scope management | Varies by provider; often informal. | Formal, through statements of work and change requests. | Set by your own priorities. Scope can drift without product leadership. | A written scope with inclusions and exclusions. Changes are priced before they're added. |
| Time to begin | Often quick, depending on availability. | Varies. Usually after a sales, discovery and contracting process. | Usually the slowest: recruiting and onboarding come first. | Once the written scope is agreed, subject to the studio's availability. |
| Product ownership | Depends on the agreement. Confirm code ownership and access in writing. | Depends on the agreement. Confirm code ownership and access in writing. | Usually yours, as work done by employees. | Yours once paid in full, in accounts you control, as set in the signed agreement. |
| Maintenance | Depends on the freelancer's availability after the project. | Often available as a support retainer. | Built in: the team maintains what it builds. | Care and Evolve retainers, with planned monthly hours. |
| Best-fit project types | Well-defined tasks in one discipline, and tight budgets. | Large, multi-disciplinary projects that need formal process and many people at once. | A core product that needs full-time development for years. | Turning an idea into a first production product, or getting a stalled one moving. |
03Fit
When each option makes sense.
A traditional agency
The project needs many people at once (several platforms, brand, content, testing) with formal reporting, and the budget matches that scale.
An in-house team
The product is the business, development will be continuous for years, and you can recruit, manage and keep engineers.
BlindspotLab
You want one accountable person to take an idea or a stalled product to a working production version, with the product thinking and the engineering in the same hands.
When BlindspotLab isn't the right choice
- Large enterprise transformation programmes
- Work that needs many engineers building in parallel
- A native iOS or Android app as the main product
- Round-the-clock support with guaranteed response times
- Projects that require a vendor with specific industry certifications
For these, an agency, a specialist firm or your own team will serve you better.
04With BlindspotLab
What you get with BlindspotLab.
- 01
Direct founder involvement
The founder scopes, designs and builds the work. There's no account manager in between.
- 02
A written scope
Deliverables, price, milestones and exclusions, agreed before anything is booked or paid.
- 03
Strategy and engineering together
What to build first is decided by the person who will build it.
- 04
Working software at milestones
Each milestone is something you can open and use, not a status report.
- 05
Deployment and handover
The product goes live on your domain, with access and documentation handed over.
- 06
Maintenance when you need it
Care and Evolve keep the product healthy, or keep it improving, after launch.
05Investment
Compare the investment.
Freelancer, agency and in-house costs vary too widely by market and provider to quote fairly, so they aren't listed here. The fairest comparison is several quotes against the same written scope.
- Launch · for independent founders
- From $1,500, indicatively 5–10 working days. A focused website or landing page, live on your domain.
- Spark · for independent founders
- From $2,500, indicatively 7–14 working days. One workflow, working: a prototype or a constrained automation pilot.
- Ship · for growing teams and businesses
- From $5,500, indicatively 3–5 weeks. A focused production MVP with one core journey.
- Forge · for growing teams and businesses
- From $12,000, indicatively 6–10+ weeks. A substantial production application with custom architecture and integrations.
- Care · after launch
- From $450 / month. Keep a live product healthy: up to three hours of planned maintenance a month.
- Evolve · after launch
- From $1,500 / month. Keep improving the product: up to twelve hours of planned engineering a month.
- Product Clarity Review
- From $350. A bounded assessment of your idea, prototype, product or site, with a written recommendation.
Starting prices in US dollars; the written scope sets the final price. See what each package includes, excludes and how payment works.
06Selected work
Built and run by the studio.
Each case study states the studio's role and who owns the product.
Next step
The right partner starts with the right conversation.
Tell us what you're building and where you are in the process. We'll help determine whether BlindspotLab is a good fit.