Phasing an 18-Month Product Build to Stay Competitive in the Meantime

You are the product manager for a new product. Your team estimates that building it properly will take 18 months, but the competition will not wait: by the time a full version ships, rivals will have built a lead the company could no longer close. How would you plan delivery so the company stays competitive while the product is being built? Explain what you would ship first and to whom, what you would build, buy or partner for, which shortcuts you would refuse to take, and how you would know the plan is keeping the company in contention. ```hint Take the 18 months apart Before picking a tactic, split the estimate into work customers would notice and foundations they would not, and find out which part of the competitors' lead is actually costing deals. Those two answers decide what can ship early and what must not be rushed. ``` ### Clarifying Questions - Are competitors already selling a product in this space, or are they building toward the same market on a similar timeline? - What drives the 18-month estimate: foundational work such as the data model, security and scale, or the breadth of features needed to match rivals? - Who are the target customers and how do they buy: multi-year contracts with fixed renewal windows, or self-serve purchases they can switch quickly? - Are acquisitions, licensing or partnerships an option, and is the team size fixed? ### What a Strong Answer Covers - A diagnosis of what fills the 18 months and where the competitors' lead actually hurts (lost deals, renewals, mindshare) before any tactic is chosen - A phased plan with an early, narrow release that solves one valuable problem for a defined segment, then increments toward the full product - Build, buy, partner and extend-an-existing-product options weighed on speed, differentiation and integration cost - Explicit lines between what is never compromised (security, core data model, reliability) and what is deferred, with a plan to repay shortcuts - Leading metrics and decision gates that show whether the company is staying in the race, plus commercial risks such as overpromising the roadmap ### Follow-up Questions - Your early release delights design partners but keeps losing head-to-head evaluations on missing features. What do you change? - Sales wants to promise the full 18-month roadmap to close deals this quarter. How do you respond? - What evidence would lead you to recommend not entering this market at all?