Skip to content

Strategy

Hire in-house developers or a software firm? When each is right

Two questions that sort a system into in-house or outside, the one-engineer trap, and the hybrid that fails.

Computing America. Applications, integrations, data analysis and AI/ML engineering.

Describe year three
4 min readComputing America
An empty desk set up for a new hire, the chair still wrapped in plastic.

In short

  • Two questions decide it, not project size: does the system keep changing after launch, and is it the reason customers choose you? A standing in-house team is for a yes to both.
  • Software that supports the business can stay with a firm indefinitely. Software that is the business but has stabilized is built by a firm with a dated handover to your own people.
  • One engineer is not a team. A single hire carries no review, no cover and no second opinion, and their departure takes the institutional knowledge with it.
  • The hybrid that fails is a firm building while a first hire watches. Watching doesn't transfer a system; write the handover into the engagement as scope with a date on it.
  • If you're hiring to save money, compare the firm's rate with the full cost of the role, not the salary.

Hire an in-house team when the system will keep changing after launch and is the reason customers choose you. Use a firm for everything else, with a dated handover if a stable system is also your product. Project size doesn't decide it.

We're a software firm, so this includes the version where you shouldn't hire us. A firm on a system that changes every week becomes a queue. An engineer on a system that changes twice a year has little to do.

Two questions: change rate, and whether you sell it

Some systems stabilize. Take a quoting tool, an inspection app, or scheduling for a business whose scheduling is stable. These get built, corrected for six months while reality argues with the design, and then run on patching, monitoring and a few changes a year. An engineer hired to look after that is underused.

Other systems keep changing: a pricing engine in a business where pricing is the strategy, a marketplace, anything where the software is how the company competes. There every change generates the next, and the work needs a standing team, yours if the software is also what customers buy.

The second question separates software that supports the business from software that is the business. The first can live outside indefinitely, and companies can run entirely on systems another firm built. The second needs an owner on your side. If it also keeps changing, that owner is a team. If it has stabilized, a firm can build it, and the handover to your own people is written into the engagement. If it keeps changing but isn't your product, such as an internal order system, use a firm under a standing arrangement with a named lead, and expect a queue.

Fig. 1

Is it why customers choose you?: It is the business or It supports the business

Change after launch: Stabilizes: list cleared or Keeps changing: backlog grew

It is the business · Stabilizes: list cleared

Firm builds, you take over

  • Built, corrected for six months, then a few changes a year
  • Handover to your people written into the engagement

It is the business · Keeps changing: backlog grew

Hire a team

  • Every change generates the next
  • Last quarter's backlog grew faster than it cleared
  • Two engineers, not one

It supports the business · Stabilizes: list cleared

A firm, indefinitely

  • Can live outside the company for good

It supports the business · Keeps changing: backlog grew

A firm on a standing arrangement

  • A named lead
  • Expect a queue

Only a system that keeps changing and is also your product needs a standing in-house team; a stable one that is also your product is a firm's build with a dated handover.

SourceThe two questions in this article; no measured data.

One engineer is not a team

A single hire is a mistake capable people make for sensible reasons.

  • Their work goes unreviewed, so the only quality control is their own discipline on their worst week.
  • There's no cover. A holiday is a freeze and an illness is an outage.
  • There's no second opinion, so an early architectural decision gets made alone.
  • Everything they know is in one head, and their resignation loses all of it.
  • They may be managed by someone who can't evaluate the work.

Two engineers can review each other and cover each other's absences. If the budget supports only one, consider a firm or a dated handover instead.

The hybrid that works, and the one that doesn't

The failing hybrid is a firm building the system while your first hire watches, on the theory that they'll absorb it and take over. Watching someone build a system doesn't teach you to own it. The new engineer spends months with no ownership, learns the parts they happened to be shown, and inherits the rest as a surprise.

The version that works puts the handover in the engagement as scope. Your engineer owns named parts of the system from an agreed point, our people review their work, and a written date follows after which they're on call and we're the ones called for advice. It costs more than a week of walkthroughs. It also leaves you with a team that has already carried the system.

What to do before you decide

  • Write down what the system will be doing in year three and who will be asking for changes. Then count the changes people requested in the last quarter. If the list cleared within the quarter, the system has stabilized. A backlog that grew faster than it cleared means the changes are real. For a system not yet built there is no quarter to count, so judge from the year-three list alone.
  • Mark it: does it support the business, or is it the reason customers choose you?
  • If you're hiring, plan for two engineers or a dated handover, not one engineer alone.
  • Ask any firm to put in writing how you would leave: who owns the code, what handover help is included, and the notice period.

Sources

  1. 1.Employer Costs for Employee Compensation, June 2026 (opens in a new tab), U.S. Bureau of Labor Statistics,

Next step

Tell us what the system has to do in year three.

Not what it does at launch, but what it is expected to be doing two years after, and who will want it changed. We will tell you honestly whether that is a team you should be hiring rather than a firm you should be paying.

Reply
A person replies, not a sequence: within one business day, from someone who would be on the engagement.

Packages

Start with a package

Four packages, each with its price on the page. Pick one and buy it online.

Billing