Fractional engineer, dev agency, or full-time hire?
The short answer: match the route to how much engineering you actually have. If software is the product and there’s forty hours of work a week indefinitely — hire. If you need a whole team moving fast for a defined project and the budget to match — agency. If you need senior capability steadily but nowhere near full-time — which describes most small businesses — fractional gets you there at a fraction of the cost. And if an off-the-shelf tool covers it, the honest answer is none of the above.
The comparison that matters
Ballpark US figures as of 2026. The columns people forget to compare are the last two — speed to something shipped, and what happens after launch.
| Route | Real monthly cost | Time to first shipped thing | When it breaks later |
|---|---|---|---|
| Full-time senior hire | ~$14–20k+ (salary + ~30% benefits/taxes/overhead) | 2–4 months of hiring and ramp before real output | Covered — it’s their job. But one person is also your single point of failure, and a mis-hire costs half a year. |
| Dev agency | ~$20–50k+ for a project team (US blended rates ~$150–250/hr) | Fast once started — after discovery phases and contracts | A support contract, a ticket queue, and hourly billing. The people who built it may have rotated to another client. |
| Fractional senior engineer | A few $k/mo for ~a day a week | Days to weeks — no ramp committee, no discovery theater | The person who built it is on retainer and monitoring it. The honest limit: one person’s capacity and availability. |
| Off-the-shelf / no-code | $50–500/mo in subscriptions | Immediate | You’re bounded by the tool. Fine until your process stops fitting its boxes — then you’re back at this table. |
When each route is actually right
Hire full-time when software is the business.
If the product is code, or engineering demand is genuinely forty-plus hours a week for the foreseeable future, nothing beats an owner on payroll. The mistake is hiring that person to handle ten hours a week of real work and paying full-time rates for idle capacity — or worse, inventing work to fill it.
Use an agency when you need a team, fast, for a defined thing.
Five engineers for nine months to build something big is what agencies are for. You pay for coordination overhead and account management, but you get parallel capacity no individual can match. The failure mode: small projects, where the overhead is most of the bill — and incentives that reward billable hours over shipped outcomes.
Go fractional when you need senior breadth, not full-time depth.
Most small businesses need product work this month, an automation next month, infrastructure the month after — a day or two a week of someone senior enough to do all of it. That’s the fractional shape: steady output, compounding context, no ramp, no severance. The honest limit is capacity — it’s one person, and if your need is really a team’s worth, fractional will feel slow.
Choose none of them when a tool already does it.
A brochure site belongs on a site builder. A standard store belongs on a commerce platform. Custom engineering is for when your process, data, or product genuinely doesn’t fit the boxes — paying any of the three routes above to rebuild what $100/mo of software does is the most common waste in small-business tech.
Five questions that expose the wrong choice
- — “Who owns the code and the accounts?” If the answer isn’t “you, in your name, from day one,” walk.
- — “Who answers when it breaks at 2 a.m.?” Every route has an answer; make sure you’ve heard it before signing, not after the outage.
- — “What ships in the first two weeks?” Vague answers predict months of discovery. Something real should be visible fast in any model.
- — “What happens when we stop?” Documented handoff should be a stated feature, not a negotiation. No lock-in is a design choice.
- — “Is this actually 40 hours a week of work?” Answered honestly, this one question usually makes the decision for you.
Common questions
What does a fractional engineer cost?
Market rates for a senior fractional engineer at roughly a day a week run a few thousand dollars a month — order of magnitude cheaper than a full-time senior hire and far below an agency team's monthly burn. The trade is capacity: you're buying a steady slice of one senior person, not a team.
How is fractional different from hiring a freelancer?
A freelancer is usually task-shaped: you define work, they deliver it, they leave. Fractional is ongoing and accountable — the same person carries context month over month, owns the systems they build, and tells you what you should be doing next, not just what you asked for.
Who owns the code in each model?
In all three, insist on: you own the code, the accounts, and the infrastructure, in your name from day one. Agencies sometimes hold repositories or hosting hostage-by-default; a good engagement of any shape hands you a documented codebase you could walk away with.
Can a fractional arrangement scale up when we need more?
Within limits — a push can temporarily take more days a week, and calm months can take less. But one person has a ceiling, and honesty about it matters: if you genuinely need several engineers for a year, that's an agency or hires, not fractional.
What happens if we outgrow a fractional engineer?
That's the good outcome. The systems, documentation, and roadmap become the foundation your first full-time hire inherits — and the fractional engineer who built them is the best-positioned person to help you hire and hand off well.