Skip to content

Strategy

Build vs buy software: sort each process step before you write requirements

Sort every process step as commodity, differentiating or contextual before anyone writes a requirements document.

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

Send the process steps
3 min readComputing America
A mass-produced key beside a freshly hand-cut brass key and its filings on a workbench.

In short

  • Run the sort before any requirements document: it shows which steps you only need to describe to a vendor and which you must specify for yourself.
  • Decide per process step, not per system: commodity, differentiating or contextual. Each gets a different answer.
  • A feature matrix showing 85% coverage hides the cost: the missing 15% is often specific to you, and it becomes permanent manual work.
  • Buy the system of record and own a thin perimeter around it: the integrations, the one workflow that is yours, and the reporting the package can't do.
  • Put a yearly maintenance line in the build case. Our planning figure is 15–25% of the original build cost.

Buy what is generic. Build the steps that are specific to how you operate and drive your margin or service level, and any other step only when nothing on the market fits, and then small.

The usual debate pits a vendor quote against an internal-cost spreadsheet. Both price the software and leave out the work people do by hand around whatever you pick.

Why the feature matrix misleads

Feature matrices measure coverage, and coverage is the wrong axis. A platform covering 85% of your requirements sounds strong until you notice that the missing 15% is often the part specific to you. Those requirements become workarounds, the workarounds become undocumented process, and a person does that 15% by hand, on the clock. That labor isn't on the license quote.

Decide per process step, not per system

Split the process into steps and place each one on two questions: is it specific to how you operate, and does it drive your margin or service level? The four answers sort into the quadrants below.

Fig. 1

Drives your margin or service level: Yes or No

Specific to how you operate: Generic or Specific

Yes · Generic

Critical commodity: buy it, integrate it well

  • Generic, but it still drives your margin or service level

Yes · Specific

Differentiating: own it

  • The one workflow that is yours alone

No · Generic

Commodity: buy it

  • Payroll
  • Email
  • General ledger
  • HR records

No · Specific

Contextual: buy if it fits, else build small

  • Internal approvals
  • Onboarding checklists
  • Compliance workflow

Own only the step that is specific to you and drives margin; buy the generic ones.

SourceThe decomposition used in this article; a planning aid, not measured data.

The costly mistake is building the commodity and buying the differentiator: a bespoke expense tool built because a director disliked the vendor's interface, while the differentiating operation runs on a platform that constrains it. Tag the steps with the operators in the room as well as the executives. That's where they'll disagree.

Federal buyers have a rule that points the same way. FAR 11.002(a)(2) (opens in a new tab) tells acquisition officials, to the maximum extent practicable, to state requirements as functions, performance or essential physical characteristics, and to define them so offerors are encouraged to supply commercial products. It prefers describing a need in terms commercial products can meet; it doesn't decide your case.

The costs each side forgets

PathUsually left outAsk
BuyImplementation and configuration. Integration into your estate: a connector list names products, not your instance of them. Data migration. The internal administrator the platform needs. Per-seat cost at your three-year headcount. Customization, which is priced as configuration but behaves like development and is redone at each upgrade. The cost of leaving.Has this vendor connected to our exact systems, at a customer we can speak to? Which requirements are configuration, which are customization, and what happens to each at the next major version? What does leaving cost?
BuildTreating software as finished when it ships. Hosting, dependency upgrades, security patching, on-call, and a change budget for a system that will be asked to do new things. Our planning figure is 15–25% of the original build cost, every year.Who patches, upgrades and answers the page at 2 a.m.? Is the yearly 15–25% in the business case?
What each path's estimate usually leaves out, and what to ask before you decide.

Buy the system of record, own a thin layer around it

A package that is the system of record, with custom work around it, is usually the right shape. The package carries the compliance surface. Around it sits a thin layer you own. It holds three things: the integrations between the package and everything it doesn't know about, the one workflow that is yours alone, and the reporting the package can't answer. That layer is a fraction of the size of the system it surrounds.

Your workflow and your reporting depend on the integrations, so give them real engineering. A nightly CSV export is a weak foundation for them. The discipline on the build side is refusing to let the perimeter grow until it has reimplemented the package.

How to run the decision in a week

  1. 1.Write down the process end to end, including every step a person performs outside a system.
  2. 2.Tag each step commodity, differentiating or contextual, and mark any commodity that drives your margin.
  3. 3.For the differentiating steps only, ask whether any product on the market permits the behavior you want. Storing the data isn't enough.
  4. 4.Price both paths over five years, with escape cost on one side and maintenance on the other.
  5. 5.Decide per category. Do it before anyone writes a requirements document.

Sources

  1. 1.FAR Part 11: Describing Agency Needs (opens in a new tab), Federal Acquisition Regulation

Next step

Send us the list of process steps.

Send the process as you would list it on a whiteboard, including the steps a person does by hand. We will mark the steps we would expect a package to cover, the ones that are integration work rather than software, and the few that are yours to build.

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