Choosing how to build your software — agency, freelancers, or in-house — is one of the highest-stakes decisions a CTO or founder makes. The wrong model does not just cost money. It costs months of the wrong people building the wrong thing in the wrong way.
The decision is not primarily about hourly rate. It is about which model fits the type of work, the timeline, the internal capabilities, and the strategic importance of what you are building.
This guide explains the trade-offs of each model without bias, gives you a structured evaluation process for selecting a partner, and covers the red flags that separate reliable partners from expensive mistakes.
Three Models, Three Different Problems They Solve
| Model | Best for | Primary trade-off |
|---|---|---|
| Agency | Complex multi-discipline projects, fast start, specialised expertise | Higher hourly rate, less institutional knowledge over time |
| Freelancers | Well-scoped tasks with clear deliverables, specific skills | Coordination overhead, availability risk, variable quality |
| In-house | Strategic, permanent software; deep domain knowledge; culture-critical work | Slow to build, expensive to maintain, high risk of poor hires |
No model is universally superior. Many successful engineering organisations use all three at different stages and for different workstreams.
When to Use an Agency
An agency makes sense when:
You need to move fast without building a hiring pipeline. Hiring a senior engineer takes 3–6 months from job posting to first day of productive work. An agency can start in 1–4 weeks with a team that has already worked together.
The project has a defined scope and end. A product launch, a platform migration, a security audit, a mobile app v1 — these have a beginning, a middle, and an end. Agencies are designed for project-based engagements.
You need specialised expertise temporarily. Mobile security, machine learning, cloud architecture, Kubernetes platform engineering — these are skills that are expensive to hire for and may not be needed full-time after the project. An agency brings the expertise for the duration you need it.
You want accountability for delivery. A well-structured agency engagement has defined milestones, acceptance criteria, and a contract that ties payment to delivery — creating an accountability structure that is harder to establish with a loosely organised freelancer team.
What to look for in an agency
- Genuine technical depth in your domain — ask about specific decisions in past projects, not just the logo wall of clients
- A defined process for discovery, requirements, development, and handover — agencies without process create chaos
- Reference clients willing to talk — not just testimonials on a website
- Ownership and continuity — know who will actually build your product, not just who presents in the sales call
- Cultural fit — you will work with these people for months; the relationship quality matters as much as the technical quality
When to Use Freelancers
Freelancers work best for well-defined, self-contained work:
- A specific feature with clear acceptance criteria
- A UI redesign with defined scope
- A code review or security audit with a clear deliverable
- An integration with a third-party API
- A one-time data migration or analysis
The coordination overhead of managing multiple freelancers across disciplines — a designer, a frontend engineer, a backend engineer, a QA specialist — is significant. It works when you have an experienced technical lead who can define the work and review the output. It breaks down when the team building the product is entirely distributed freelancers with no shared context.
Platforms for finding vetted freelancers:
- Toptal — pre-screened senior engineers, high acceptance bar, high cost
- Upwork — broad marketplace, variable quality, requires careful vetting
- Gun.io — senior engineers, US-focused
- LinkedIn — direct sourcing, most control over targeting
When to Build In-House
In-house development is the right long-term model for software that is:
A core competitive advantage. If your product is the business — if the software itself is what creates value that competitors cannot easily replicate — then the team building it should be yours. Institutional knowledge, domain expertise, and cultural alignment compound over years of an in-house team.
Evolving indefinitely. If there is no end date — if you will be adding features, responding to users, and improving the product for the foreseeable future — the economics of in-house improve relative to agency over time.
Highly regulated or sensitive. Some industries (finance, healthcare, defence) have requirements around knowledge ownership and data access that make fully outsourced development impractical.
The cost of building in-house
Recruiting a senior full-stack engineer in 2026:
- Time to hire: 2–4 months from job posting to start date
- Recruiting cost: 15–25% of first-year salary if using a recruiter
- Onboarding time: 3–6 months to full productivity
- Total compensation (US): $150,000–$250,000+ annually including equity and benefits
Building a team of 5 from scratch takes 12–18 months and a significant upfront investment before meaningful output is delivered. For an early-stage startup with a 9-month runway, this is not the right model.
The Hybrid Approach
Most mature engineering organisations use a hybrid model:
Core in-house team for strategic, permanent product development, domain knowledge accumulation, and culture-critical work.
Agency partnerships for specific projects: a new platform, a mobile app, a security assessment, a data engineering initiative.
Freelance specialists for defined tasks: a performance audit, a design sprint, a one-off integration.
The key is clarity on which work belongs in which model. Strategic, continuous, culture-defining work belongs in-house. Time-limited, specialist, or well-defined work can flow through agencies or freelancers without compromising what makes the core product distinctive.
Vendor Evaluation Framework
When evaluating agencies specifically, use this structured process:
Step 1: Initial screening (30 min call)
- Who will actually build this? (Names and experience of the specific engineers)
- What projects most similar to ours have you completed in the last 18 months?
- What is your development process from kick-off to delivery?
- Can you provide 2–3 client references for similar projects?
Eliminate any agency that cannot answer these questions specifically.
Step 2: Technical proposal review
Ask for a technical proposal — not just a commercial one. It should describe:
- How they would approach the problem technically
- The architecture they would propose and why
- Risks they have identified
- What they would need to clarify before starting
A proposal produced in 24 hours without a proper discovery conversation is not based on your requirements. A good proposal takes 3–5 days and involves real thinking.
Step 3: Reference calls
Call 2–3 past clients directly. Ask:
- What did you build together and over what timeline?
- What was the quality of what was delivered?
- How did the team handle problems or requirement changes?
- What would you do differently?
- Would you work with them again?
Past client conversations are the most reliable signal you will get.
Step 4: Paid pilot
Run a 1–2 week paid pilot before committing to a full engagement. A reasonable deliverable: a technical specification, an architecture document, or a proof-of-concept for one component of the project.
The pilot reveals communication quality, technical approach, how they handle ambiguity, and whether the relationship is productive — all before you have committed significant budget.
Contract Essentials
Before any significant work begins, a contract must be in place covering:
| Clause | Why it matters |
|---|---|
| IP assignment | All code and deliverables must transfer to you upon payment. Without this, the agency may own the code. |
| Confidentiality / NDA | Your business logic, data, and plans must be protected. |
| Payment milestones | Tie payments to deliverable acceptance, not calendar dates. Never pay > 30% upfront on fixed-price work. |
| Scope and change control | Define what happens when requirements change. Changes must be documented and priced. |
| Acceptance criteria | How will you know the work is done and acceptable? |
| Termination rights | What do you receive and own if the engagement ends early? |
| Warranty period | How long is the agency responsible for fixing defects? (Minimum 30–90 days.) |
A contract that protects both parties is a sign of a professional agency. One that is reluctant to include IP assignment or warranty terms is a warning sign.
If you are evaluating software development options and want to understand how IQCrafter approaches client engagements — our process, the type of projects we take on, and what collaboration looks like in practice — get in touch or explore our Enterprise Software Development capabilities.