Q: How is the rubric scored?

4-5 "build" answers = strong replace candidate, move to the SaaS Replacement Matrix for the full call. 3 "build" answers = possible candidate, revisit after one more quarter of stability. 0-2 "build" answers = stay on the SaaS, the rebuild fight is not worth it.

Q: Why is workflow stability the first question?

Volatile workflows burn rebuild budget. Building a custom replacement for a workflow that is still being defined means the team is rebuilding the rebuild within months. Six months of stability is the cheapest sanity check we have found across 30+ engagements.

Q: What is the $300/month threshold and why?

$300/month per team is the empirical break-even point where the math typically favors building inside 12-18 months. Below it, the savings do not pay back the engineering hours fast enough. Above it, the math usually wins — but the other 4 questions still have to support the call.

Q: When should I use the rubric vs the full Matrix?

Use the 5-Question Rubric on intake calls and first-pass triage — it takes 5 minutes and surfaces 80% of obvious decisions. Use the 6-Row Matrix when the rubric points toward "build" and you need to validate against the full decision space before committing engineering hours.

Q: Is the rubric free to use?

Yes. CC BY 4.0. Free to share, adapt, and reproduce with attribution to NodeSparks (2026).

Question 1

What are the 5 questions in the NodeSparks Build-vs-Buy Rubric?

Accepted Answer

Q1: Has the workflow been stable for 6+ months without major changes? Q2: Does the team actively work around the SaaS limits every week? Q3: Is the recurring cost above $300/month per team using it? Q4: Could a senior engineer rebuild the actually-used 80% in <60 hours? Q5: Would losing the SaaS today put a compliance, payroll, or accounting deadline at risk?

Question 2

How is the rubric scored?

Accepted Answer

4-5 "build" answers = strong replace candidate, move to the SaaS Replacement Matrix for the full call. 3 "build" answers = possible candidate, revisit after one more quarter of stability. 0-2 "build" answers = stay on the SaaS, the rebuild fight is not worth it.

Question 3

Why is workflow stability the first question?

Accepted Answer

Volatile workflows burn rebuild budget. Building a custom replacement for a workflow that is still being defined means the team is rebuilding the rebuild within months. Six months of stability is the cheapest sanity check we have found across 30+ engagements.

Question 4

What is the $300/month threshold and why?

Accepted Answer

$300/month per team is the empirical break-even point where the math typically favors building inside 12-18 months. Below it, the savings do not pay back the engineering hours fast enough. Above it, the math usually wins — but the other 4 questions still have to support the call.

Question 5

When should I use the rubric vs the full Matrix?

Accepted Answer

Use the 5-Question Rubric on intake calls and first-pass triage — it takes 5 minutes and surfaces 80% of obvious decisions. Use the 6-Row Matrix when the rubric points toward "build" and you need to validate against the full decision space before committing engineering hours.

Question 6

Is the rubric free to use?

Accepted Answer

Yes. CC BY 4.0. Free to share, adapt, and reproduce with attribution to NodeSparks (2026).

The 5-Question Build-vs-Buy Rubric

The five questions

Scoring

How to cite

Related

Let's start with a real conversation.We’re ready when you are.