Agency vs freelancer vs in-house: what it actually costs

You’re looking at an $80/hour freelancer versus a $150/hour agency, and the math seems straightforward. The freelancer appears to save you $30k on a three-month project. But that’s not how it plays out in reality. The base rate is only 50% to 70% of the total cost once you factor in vetting, management, handoffs, and rework.

The question isn’t which option has the lowest hourly rate. It’s which option gets the job done for the least total cost and the least risk of delays or restarting entirely. Most companies learn the hard way.

What does a freelancer actually cost?

A freelancer at $80/hour for a 480-hour project seems like it will cost $38.4k. But that number ignores everything else you end up paying for.

You’ll spend 15 to 25 hours reviewing candidates and conducting interviews, which costs $2.5k if your time is worth $100/hour. Finding a qualified freelancer takes two to three weeks, so your timeline is already behind before anyone writes a line of code.

Once the freelancer starts, someone on your team has to manage them. Freelancers don’t manage themselves. If you spend 10 hours a week on check-ins, scope clarification, and reviewing work, that’s $16k over 16 weeks. Most companies underestimate this because they treat internal time as free.

When the project ends, the freelancer leaves. If you need changes or bug fixes later, you either bring them back at a potentially higher rate or hire someone new who needs 20 to 40 hours just to understand the existing code. Knowledge transfer always costs money.

In practice, a significant portion of freelance engagements require a second pass. Add another $8k to $15k for fixes. A project that starts at $38.4k can easily end up costing $60k once you factor in vetting, management, and rework.

Freelancers aren’t a bad choice, but they work best for small, well-defined projects under 200 hours where you have someone internal to review the code and manage the work. Anything bigger starts to rack up hidden costs.

What does an agency actually cost?

An agency at $150/hour for the same 400 hours of work looks like it will cost $60k. Agencies often estimate fewer hours because they work faster with established processes and multiple people to tackle problems.

The difference is what you don’t pay for. Agencies manage themselves, so you don’t spend 10 hours a week tracking progress. Instead, you spend two to three hours per week on status calls, cutting your internal time cost from $16k to around $3.6k.

Agencies handle code review, QA, and project management internally. When the project ends, they document what they built, so you don’t lose institutional knowledge. If you need changes later, they already understand the system, or someone else on their team can pick it up.

The real cost for an agency on a three-month project is around $66k, including your internal time. That’s $13k more than a freelancer, but you’re paying for predictability, continuity, and lower execution risk.

Agencies make sense when the timeline matters, you lack internal technical leadership, or the scope is likely to evolve.

What does an in-house developer actually cost?

A senior developer earning $130k per year seems like they’ll cost $65k for six months of work. But that ignores benefits, recruiting costs, equipment, and management overhead.

The fully loaded cost of an employee is 1.25 to 1.4 times their salary, plus $5k to $15k for equipment and licenses, plus $10k to $25k for recruiting. If you hire through an agency, the fee is typically 25% of the annual salary. If you hire directly, someone on your team spends 40 to 60 hours sourcing, screening, and interviewing candidates.

Hiring a senior developer takes three to four months on average. You post the job, wait for applications, conduct interviews, make an offer, and onboard them. If your project needs to start in less than six weeks, hiring in-house isn’t feasible.

The real cost for six months of in-house work is closer to $113k before the developer contributes to the project. And after six months, you either keep paying them or lay them off, neither of which is cheap.

In-house developers become cost-competitive at 18 to 24 months of continuous work with a stable team of at least three people. Before that, project-based models are more economical. After that, in-house wins because the per-hour cost drops and the team builds institutional knowledge.

In-house is the right choice when you have a multi-year roadmap, the work is core to your competitive advantage, or you already have a team that justifies an engineering manager.

How do successful companies handle this?

Most companies don’t stick with one hiring model forever. They match the model to the type of work.

Early-stage startups often use an agency or senior freelancer to build the MVP because speed matters more than cost. Once the product is validated, they hire a founding engineer to own the core platform and keep the agency for design or new features.

Growth-stage companies with 10 to 50 employees usually have a small in-house team for the core product and use agencies for project-based work like redesigns or mobile apps. Freelancers fill specialist gaps, like data pipelines or infrastructure.

Established companies with 50 or more employees typically have a large in-house team and use agencies for overflow or specialty projects. They rarely use freelancers due to compliance and IP concerns.

Across all stages, successful companies match the hiring model to the work. Core platform development stays in-house. Project-based work goes to agencies. Small, well-defined tasks go to freelancers when there’s someone internal to review the work.

What question should you actually ask?

The decision between a freelancer, agency, or in-house hire comes down to five questions.

Can you wait three to four months for someone to start? If not, in-house isn’t an option. Freelancers take three to five weeks, while agencies take two to three weeks.

Will the work last more than 12 months? If so, in-house starts to make economic sense. If not, project-based models are better.

Do you have someone internal who can review code and manage developers? If not, freelancers are risky. Agencies manage themselves.

Is the scope clear, or will it evolve? If it’s clear, freelancers can execute. If not, agencies handle scope changes better.

Is this work core to your competitive advantage or auxiliary? Core work should probably stay in-house eventually. For the rest, a custom software development agency offers the balance of speed and quality. Auxiliary work is better suited to project-based models.

The right answer depends on your situation, what you’re building, and how much risk you can tolerate. If you’re evaluating options for a project that needs to start soon or has an evolving scope, talk to us about custom software development. We can walk through what works for your situation.