What not to build, mapped in a week.

THE SITUATION

A seed-stage SaaS startup had raised a modest round and spent the first year building. Their product roadmap was ambitious: eighteen months of features spread across three concurrent workstreams: a core platform, an analytics module, and an API marketplace for third-party integrations. The team was talented, the product worked, and early users liked it. But revenue was flat, runway was shrinking, and the company was six months from running out of money with no clear sense of which workstream would change that.

The founders were engineers at heart; they defaulted to building more when the business got uncomfortable. The roadmap had grown by accretion: every customer call, every competitor announcement, every internal brainstorm added another feature to the list. Nobody had ever asked whether any of them were the right features, because the instinct was always to build first and ask questions later.

THE ENGAGEMENT

The engagement was short by design: one week, one question. The question was not 'what should we build?'; that is the question the roadmap was already trying to answer, poorly. The question was: 'what is the smallest thing that proves anyone will pay for this?' Answering it meant looking at the business from the outside in; examining who the actual paying customers were, what they had in common, and what they were trying to accomplish that they could not accomplish today without the product.

The analytics module and the API marketplace were parked; not killed, but removed from the active plan. They were answers to problems the startup did not yet have. The core platform had one feature: a scheduling workflow; that a small cluster of paying customers used daily and had independently cited as their reason for subscribing. That feature became the bet: three months to harden it, package it as a standalone product, and sell it to fifty more customers who matched the profile of the ones already paying.

THE RESULT

The roadmap shrank from eighteen months to a single three-month bet with concrete success criteria: fifty new paying customers at a defined price point. If the bet paid off, the company would have revenue, product-market clarity, and enough runway to fund the next bet from earnings rather than from the remaining seed capital. If it did not, they would know within three months; not eighteen; and could pivot or wind down without burning through the rest of the runway on features nobody had asked for. The fifteen months of parked features stayed parked until the first bet proved itself.