A buyer requests a capability and suggests that signing depends on it. The founder sees a major contract. Engineering sees several months of work that other customers may never need.
Identify the common problem beneath the request
Ask what outcome the buyer needs and whether an existing capability or smaller change could achieve it. Avoid treating the requested implementation as the only possible solution.
GOV.UK’s alpha guidance uses prototypes to examine risky assumptions. A limited prototype can help determine whether a proposed capability belongs in the standard product before a full build is promised.
An illustrative logistics customer may ask for a bespoke dashboard while the actual need is a reliable exception export. The narrower response could serve more accounts with less complexity.
Include continuing obligations
Estimate maintenance, support, testing and future compatibility, not just initial development. Consider what happens if the customer later leaves.
Clarify intellectual-property and commercial terms through the appropriate review. Do not assume that accepting payment for development gives either party unlimited rights.
If the capability is genuinely customer-specific, price and govern it as such rather than hiding it inside the standard subscription.
Make the strategic trade-off explicit
Record which existing work will be delayed and why the request fits the company’s direction. A decision can be commercially sensible while still carrying opportunity cost.
Review the result after delivery. Did the capability create repeatable value or become a permanent exception requiring specialist attention?
Document the product outcome separately from the requested implementation. If the customer later accepts a smaller solution, the team can judge it against the outcome without remaining attached to the original feature list. This also makes it easier to identify reuse across other suitable customers after the first delivery.
GAT’s analysis of growth bottlenecks explains the danger of apparent scale that increases execution burden. A large customer strengthens a startup when the resulting product and delivery commitments remain manageable beyond the first invoice.
Published by the Global Apex Tech Editorial Desk. Partner involvement, when applicable, is disclosed above the headline. For editorial questions or source material, contact editor@globalapextech.org.