Pick one SaaS subscription. Walk the six rows. Tick which column matches your reality for that tool.
| Variable | Buy indicator | Build indicator |
|---|---|---|
| Workflow specificity | You use 60%+ of the SaaS features as designed. | You use <20% of features and patch the rest with workarounds. |
| Integration depth | The SaaS is the integration hub for 5+ other systems. | The SaaS is a single-input, single-output node in your stack. |
| Vendor moat | Vendor has unique data, compliance posture, or marketplace. | Vendor offers no moat beyond UI and the API you could call directly. |
| Workflow stability | Workflow changes monthly. New requirements arrive often. | Workflow has been stable for 6+ months and is unlikely to change. |
| Cost trajectory | Annual cost <$3,000 and not scaling with team or volume. | Annual cost >$5,000 and growing linearly with seats or usage. |
| Audit & compliance requirement | Tool is your audit trail for accounting, payroll, or legal. | Tool produces no compliance artefact you cannot reproduce. |
Most build-vs-buy frameworks fail because they over-count features. Whether a tool has a Slack integration or a webhook doesn't predict replacement viability. The six rows above are the ones that actually decide the call across 30+ engagements.
Anything missing matters less. If you want to add a seventh row (e.g. "executive sponsor for the rebuild"), do it — but the marginal accuracy gain is small.
Published under CC BY 4.0.
NodeSparks (2026). "The NodeSparks SaaS Replacement Matrix." https://www.nodesparks.com/frameworks/saas-replacement-matrix.
Last updated 2026-06-02. Originally published 2026-05-05.