7 Signs Your Startup Is in Build Purgatory

Build Purgatory does not announce itself. Teams enter it gradually, often while believing they are making progress. By the time the pattern becomes undeniable, the average team has spent $60,000–$150,000 inside the loop.

These seven signs identify the pattern early. If you recognise three or more, you are either in Build Purgatory or approaching it.

Sign 1: Your ship date is always "soon"

Not a specific date. Not a week. "Soon."

Teams with locked scope and a fixed build plan can name a ship date. Teams in Build Purgatory cannot — because the target is still moving, and naming a date would require admitting that.

Ask your team: "When does the current version ship?" If the answer contains the word "soon," "almost," "couple of weeks," or "depends on," you do not have a ship date. You have a placeholder.

Sign 2: Stakeholder reviews always produce new requirements

Post-demo feedback should answer one question: "Is this on track to meet the agreed definition of done?" Instead, stakeholder reviews produce feature requests, scope additions, and pivots.

This happens because there is no agreed definition of done. Without a locked scope document, every review is implicitly a product design session. Stakeholders are not wrong to suggest features — you invited the conversation by not closing it with a document.

Sign 3: A core feature has been rebuilt more than once

Rebuilds are expensive in engineer time and morale. A feature that has been rebuilt indicates an underlying decision that was not resolved the first time.

The rebuild was not a technical failure. It was the delayed resolution of a scope or design decision that should have been made before the first version was built. The decision debt from Sprint 1 is being paid with engineer time in Sprint 4.

Sign 4: The team describes the product differently depending on who you ask

Ask your CTO, your head of product, and your lead investor to each describe what the product does in one sentence. If you get three meaningfully different answers, your team is building against three different mental models.

This is not a communication problem. It is a decisions problem. Aligned teams produce aligned descriptions because they are working from a shared, written definition of the product. Misaligned teams produce divergent descriptions because the shared definition does not exist.

Sign 5: The backlog grows faster than it shrinks

In a healthy build, the backlog decreases as work is completed. In Build Purgatory, the backlog grows because every sprint adds more than it completes — partly through stakeholder additions, partly through dependencies uncovered by earlier decisions, and partly because "nice to have" items that were meant to be deferred keep finding their way back in.

If your team has been running sprints for more than two months and the total backlog item count is higher than it was at the start, you are in Build Purgatory.

Sign 6: You have rebuilt the scope definition document

The original scope document — if one existed — has been revised multiple times. Or the original scope was defined informally (in a Notion page or a Slack thread) and was never formally agreed upon and locked.

A scope document that changes is not a scope document. It is a wish list. Scope that is locked cannot be changed without a formal decision process that involves all stakeholders. If your scope is changing without that process, it was never locked.

Sign 7: The team is working hard but morale is declining

This is the most telling sign and the easiest to dismiss. Teams in Build Purgatory are often working long hours and producing significant output. But morale declines because the output is not accumulating toward a visible finish line.

Engineers who care about shipping — the best engineers — find purgatory particularly demoralising. They came to build products, not to rebuild features indefinitely. When you see a hardworking team with declining morale, the cause is almost always that the work is not moving toward a fixed, achievable goal.

What to Do

If you recognise your product in three or more of these signs, the intervention is structural, not operational. You do not need a new project manager or a better sprint process. You need to pause the build long enough to lock decisions.

The Product Clarity Sprint is a two-week engagement that produces a locked scope document, an aligned stakeholder position, and a fixed build plan. It is the structural intervention that breaks the purgatory loop.

Read more about what Build Purgatory is and how teams enter it, or read our guide on how to escape it and finally launch your product.

If you want to talk through your specific situation, start a conversation — we can tell you whether you are in Build Purgatory within one call.