Should you hire a fractional CTO, a dev shop, or an agency?

A founder or COO asks "who should I hire to build my software" and gets three different answers depending on who they ask: a fractional CTO, a dev shop, or an agency. All three will pitch them, and the pitches sound close to identical. They are not identical services. Confusing them is one of the most expensive mistakes we watch mid-market and early-stage buyers make. Here is the honest breakdown.

Fractional CTO

What it actually is

A senior engineering leader working part-time — typically 10 to 25 hours a week — for a company that is too small to justify a full-time CTO. The fractional CTO does not write code. They design the roadmap, hire and manage engineers or vendors, make architecture decisions, handle security and compliance posture, and sit in the executive team.

When it is right

• Pre-Series-B startup with a small engineering team that needs senior technical leadership without a $400K/year hire.
• Non-tech-founder company (a professional services firm, a healthcare practice, a family office) building its first software.
• Post-acquisition situations where the existing engineering leader is exiting and a real search will take six months.

When it is wrong

• You need software built. A fractional CTO is a leader, not a builder. They will hire builders or engage a vendor. If you skip the builder layer and try to have the fractional CTO ship code themselves, you are paying a $300/hour rate for junior-engineer output.
• You already have a strong engineering leader in place. A fractional CTO layered on top of an existing head of engineering is confusing at best.

What it costs

NYC market rate in 2026: $250–$400 per hour, or $10K–$25K per month on retainer. Serious fractional CTOs will not take more than three or four clients at a time.

Dev shop

What it actually is

An engineering firm that builds software for clients. The honest definition of a dev shop is: engineers, engineering managers, and enough process to ship real software, sold as a service to clients who either don't have in-house engineering or need to scale it. That's us. That's most of the market.

When it is right

• You have a defined problem and want a defined outcome. Fixed-scope builds (POC, MVP, platform build) are the classic dev shop engagement.
• You have an existing engineering team and need to add capacity without hiring. Staff augmentation from a dev shop with a strong bench is the fastest path.
• You need a specialist capability — AI/ML, blockchain, regulated-industry compliance — that your team does not have and cannot hire in a reasonable timeframe.

When it is wrong

• You need executive-level technical judgment on a founder team with no CTO. Dev shops build. Fractional CTOs decide. Do not conflate them.
• You need positioning, brand, and creative work as the primary output. That is agency work, and dev shops are the wrong shape for it.

What it costs

Onshore US dev shops in 2026: $150–$225 per hour for individual contributors, $200–$300 per hour for senior architects and engineering managers. Fixed-scope engagements: $5K discovery up to $500K+ platform builds.

Agency

What it actually is

An agency's core capability is creative and marketing — brand, design, campaign, content, positioning. Many agencies also build websites and light applications as part of larger brand engagements, and some have spun up "digital product" practices that overlap with dev shop work. But the core weight of an agency is creative, and the engineering is typically not the strongest part of the org.

When it is right

• Marketing site, brand launch, campaign work, content production. The agency's core competency.
• A single-vendor engagement where brand and a marketing site have to be built together, and the site is genuinely a marketing artifact (not a complex application).

When it is wrong

• Actual software with real state, real users, real compliance. Agencies typically staff these engagements with generalists or subcontractors, and the delivery quality is uneven. When we're called in to rescue a project, more often than not the original vendor was an agency that over-promised on the engineering side.
• Any engagement where the primary deliverable is an application, not a brand. If you are paying for engineering output, hire an engineering firm.

What it costs

Widely variable. Brand engagements at a serious agency: $150K to $2M. Agency-built websites: $50K to $500K. Agency-built applications: whatever they quote, plus a 40–100% overrun on average.

The overlap zone (where buyers get confused)

The confusion happens in three places. First, some agencies have real engineering practices and can deliver software at dev-shop quality. Second, some dev shops have grown design practices that can deliver reasonable brand work. Third, fractional CTOs often recommend or run dev shop engagements on the client's behalf, and the buyer isn't sure who is responsible for what. Three rules cut through the confusion:

• Who writes production code? If the answer is "the vendor's engineers," it's a dev shop engagement, regardless of whether the vendor calls itself an agency.
• Who owns the technical decisions? If the answer is "an outside senior person on retainer, not a full-time employee," you also need a fractional CTO.
• What is the primary deliverable? If it's software with users, it's a dev shop. If it's a brand or a campaign, it's an agency.

Common right answers by stage

Non-technical founder, pre-product

Fractional CTO for four to six months to lock the roadmap and hire the first engineer. Then either the first engineer plus the fractional CTO, or a dev shop engagement for the initial build with the fractional CTO overseeing.

Series A / B, small in-house team, ambitious roadmap

Dev shop for staff augmentation to scale the existing team, with your own head of engineering owning direction. No fractional CTO needed — you already have one full-time.

Mid-market non-tech company, first serious software

Dev shop for a fixed-scope MVP, plus a fractional CTO on retainer to handle vendor management and long-term direction. Once the software is mission-critical, replace the fractional CTO with a full-time head of engineering.

Enterprise, brand refresh plus new marketing site

Agency for the whole thing. Do not fragment brand work across three vendors.

Bottom line

The three roles serve different needs and cost different amounts, and the biggest wins come from picking the right one for the job instead of trying to make one vendor do all three. Buyers who mix them up spend the most and get the least. The honest answer for most mid-market situations we see is a dev shop plus a fractional CTO — one to build, one to decide — with an agency brought in only when the brand and marketing side needs real creative firepower.