Freelancer, dedicated team, agency, or in-house: the real rate math, the interview questions that actually filter, and the red flags for each hiring model.
Codestreaks Team

Somewhere in your inbox right now: a freelancer's proposal at $35 an hour, an agency quote for $60,000, and a recruiter pitching a senior mobile engineer at $165,000 plus benefits. All three say they can build your app. The spread isn't noise. It's different hiring models wearing the same job title, and choosing the wrong model costs more than choosing the wrong candidate.
Up front: Codestreaks is an agency, so we're one of the options compared below. We've shipped 30+ projects to production since 2024, most in 4 to 8 weeks on fixed prices between $8,000 and $60,000. We've also inherited enough half-built projects from every other model to know where each one genuinely wins. This is the comparison we'd give a friend, bias declared.
There are four ways to buy the same software. Each is right for somebody, and each fails in a specific, predictable way.
| Model | Typical cost | Time to start | Best for | Biggest risk |
|---|---|---|---|---|
| Freelancer | $20-$120 per hour | Days | One-workflow apps with technical oversight | One person is the whole team |
| Dedicated developers | $4,000-$10,000 per month, per developer | 1-3 weeks | Ongoing product work you can direct | Management lands on you |
| Agency | $8,000-$60,000+ fixed price | 1-4 weeks to kickoff | Shipping version one with a full team | Quality varies wildly |
| In-house hire | $130,000-$180,000 salary plus overhead | 2-4 months | A product that is the business | Slowest, priciest path to v1 |
Freelancers are the cheapest route to a simple app, and some are excellent. The model works when the scope is genuinely one workflow and someone technical reviews the work. It fails on concentration: one illness, one better offer, one disappearing act, and your project has no team. Solo developers also rarely cover design, backend, mobile, and QA equally well, so quality clusters around whatever their strong suit is.
Dedicated developers are a staffing product, usually offshore, billed monthly. You get named engineers who work only on your product, at rates well below a US salary. The catch sits in the job description: they execute, you direct. If nobody on your side can write tickets, review pull requests, and make architecture calls, you haven't hired a team, you've hired a queue. Hire dedicated mobile app developers at month twelve of a product's life, when the roadmap is long and the direction is clear. They're expensive overkill for finding out what version one even is.
Agencies sell a delivered outcome: scope in, working product out, with design, engineering, and QA included. That's the model we run, and honesty requires saying the category has a wide floor. The vetting sections below exist because "agency" spans everyone from disciplined studios to slide-deck factories.
In-house hiring is right when the app is the company. It's also the slowest and most expensive way to get a first version. Hire in-house for a product, not for a project.

Hourly rates are the least useful number in this decision. Here's the math that matters.
The in-house number. A senior US mobile engineer runs $130,000-$180,000 in salary, in line with federal wage data for software developers. Payroll taxes, benefits, and equipment push the loaded cost to roughly 1.25-1.4x, call it $180,000-$240,000 a year. Add a recruiter's fee (typically 20% of first-year salary) and 2-3 months of hiring and ramp before real output. And that buys one discipline; an app still needs design, backend, and QA from somewhere. In-house is a capacity purchase, not an app purchase.
The freelancer number. $40 an hour looks unbeatable next to that. But total cost is build cost plus rework, plus your own hours writing specs and reviewing builds, plus the delay if the first codebase can't grow. A $40-per-hour build that takes 900 hours and then needs a partial rewrite costs more than a fixed-price build that ships once. We've inherited several of those, and the rewrite always cost more than an honest quote would have.
The dedicated-team number. $6,000 per month per developer sounds like a bargain against a US salary, and for long-running work with technical direction it often is. Multiply honestly, though: two developers for eight months is $96,000, before your management time. If the goal was a scoped version one, that money bought an open-ended process instead of an outcome.
The agency number. Fixed price means the estimation risk sits with the vendor. Our tiers run $8,000-$20,000 for a single-purpose app, $20,000-$45,000 for multi-feature work, and $45,000-$60,000+ for enterprise builds. The mechanism to check is simple: if the vendor misjudges the effort, who pays? Fixed price means they do. Hourly means you do.
A chatbot or AI agent project is not a CRUD app with a text box. The hard part isn't getting a model to answer. It's getting it to answer correctly on your data, fail gracefully, and cost sane money in production. When you hire chatbot developers, you're filtering for reliability engineering, not prompt tricks.
Three things to demand. First, an evaluation suite: a set of real user queries with expected behavior, run before every release. An agent without an evaluation suite is a liability with a chat interface. Second, grounding: how the bot stays anchored to your actual catalog, policies, or docs, and what it does when the answer isn't there. Third, cost engineering: production inference typically runs $50-$2,000 per month, and good engineering (caching, model routing, prompt design) cuts that 3-10x. A developer who has never had to cut an inference bill has never run a bot in production. Our chatbot development work lives almost entirely in these three areas.

Skip "tell me about yourself." These questions separate people who have shipped from people who have followed tutorials.
For mobile app developers:
For chatbot developers:
For any vendor, one question above the rest: "Do I own the repository from day one?" There is exactly one acceptable answer. If an agency won't give you the repo, walk away. Code ownership isn't a feature, it's the deal.
The most common project we inherit follows one script. A team hired on the strength of a demo that impressed everyone in a meeting: fast answers, slick UI, five test cases in a row. Then it met real data (real users, real edge cases, real typos) and fell apart. The chatbot invented policies. The app choked on the offline case.
The lesson isn't that demos are frauds. It's that a demo that works on five hand-picked examples tells you nothing about the five thousand real ones. Moving from 90% to 99% reliability is where the actual engineering lives, and it never shows up in a demo. Interview for the boring parts: evaluation suites, error handling, sync logic, rollbacks. Whoever answers those well is who you hire.
We're an agency, so grade us with this article's own rubric. Fixed prices published ($8,000-$60,000), 4 to 8 weeks from kickoff to live, 30 days of post-launch support, 100% code ownership from day one, and real capacity stated plainly: we take on two engagements per quarter, and we say no when scope doesn't fit. Ask us the interview questions above on a call. A vendor who resists being graded by their own criteria has already answered.
Depends on the model. Freelancers run $20-$120 per hour, dedicated developers $4,000-$10,000 per month each, agencies $8,000-$60,000+ fixed for a scoped build, and an in-house senior engineer $180,000-$240,000 per year fully loaded. Compare the total cost of a working product, not rates.
Freelancer for a genuine one-workflow app with technical oversight on your side. Dedicated developers for long-running work you can direct yourself. Agency when you want a scoped version one delivered by a full team. In-house when the product is the company.
The skill under test is reliability, not UI. Filter for evaluation suites, grounding on your data, graceful failure handling, and inference cost control. A chatbot developer without an evaluation habit is shipping a liability with a chat interface.
Interview the actual engineers, not the sales team. Get repo access from day one, require weekly builds you can install, and start with a paid two-week pilot before any long contract. Swapped engineers after signing is the classic failure mode.
For version one, an agency is usually severalfold cheaper and months faster: a $45,000 fixed-price build against $200,000+ in loaded first-year salary for a single engineer. In-house wins later, once there's a proven product and a roadmap long enough to keep a team busy.
If you're weighing quotes right now, bring them to a free 30-minute scoping call. Tell us what you're building, and we'll tell you which hiring model fits, what we'd flag in the proposals on your desk, and whether the scope fits us at all. We respond within two business days, and if the right answer is a freelancer or an in-house hire, we'll say exactly that.
Book a scoping call or read about our mobile app development services.