Spotting Scope Creep on a Startup Hardware Project
A short detective guide for individual contributors on startup hardware builds — three signals visible in the first 60 days that the build has expanded silently.
Three hardware-specific signals that scope is growing in the field
On startup hardware projects, scope doesn't creep on paper. It creeps on the site, where the contractor is interpreting ambiguity and nobody's reading along.
On startup hardware projects, scope creep takes a different form than on software work. The expansion happens in the field — at the site, in the contractor's interpretation of ambiguous specifications, in change orders that look small individually. By the time anyone notices, the cumulative cost is significant and the contractor has already invoiced for some of it.
The three signals below are visible in the first 60 days. Each takes ten minutes to check. They're calibrated specifically to hardware — software-trained PMs joining hardware projects often miss them because they don't show up in the dashboards software work uses.
Three hardware scope creep signals
0 / 3- Signal 1: change order volume in the first 30 days. More than two change orders in the first month means the original scope was ambiguous in ways the contractor is interpreting in their favor. Three or more is a clear pattern.
- Signal 2: 'while we're on site' additions. When the contractor proposes additions because they're 'already on site,' scope is expanding by convenience rather than need. One or two are normal; three or more in a month indicates the contractor sees the project as flexible.
- Signal 3: contractor invoicing variance. First invoice variance from the contract. Variance over 5% in the first month is signal; variance over 10% is data.
- Day 30First signal checkWalk the three signals. 30 minutes total. Identify which are present.
- Day 30, day 3Address signal 1 if presentIf change orders are accumulating, the corrective is upstream — re-read the scope baseline with the contractor and identify the ambiguities they're interpreting. Resolve them in writing.
- Day 45Address signal 2 if presentIf 'while we're on site' additions are common, establish a discipline: every contractor-proposed addition gets a 24-hour pause and a founder decision. Most don't survive the 24 hours.
- Day 60Address signal 3 if presentIf invoicing variance is significant, the conversation isn't with the contractor — it's with whoever signed the original contract. The variance signals that the contract or the scope baseline is wrong.
The three signals are deliberately light. Their value is catching scope creep when the project is still in its first 60 days, when corrective action is cheap. For the corresponding view on software, see spotting scope creep on startup software; for the heavy enterprise implementation system, see spotting scope creep on enterprise implementation; for the upstream scope statement work, see five scope statement mistakes on startup hardware.