Strategy question

Suppose a new model capability performs well for one customer’s threat hunting workflow, but only with custom prompts, bespoke integrations, and heavy support from the team. How would you decide whether to turn that into a repeatable product? Explain how you would separate one-off requests from reusable platform capabilities, choose where to standardize, and decide when to say no to custom work.

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Product judgment on distinguishing genuine platform opportunities from expensive one-off customization.

Interview the custom deployment: identify exactly which parts are bespoke, the custom prompts, the specific integrations, and the manual support, and ask whether each addresses a need unique to this customer or a broader pattern.
Talk to other customers or prospects with similar workflows, like threat hunting, to test whether the same custom elements would solve their problem too, not just this one account's quirks.
Separate the reusable core, the underlying capability that worked, from the customer-specific wrapper, the bespoke prompts and integrations built around it.
Decide to standardize only the reusable core into the product, and say no to replicating the bespoke wrapper for every future customer, offering it instead through a documented customization layer or partner integration.
Define success: whether a second and third customer can adopt the standardized core with meaningfully less custom work than the first, proving it generalizes.

Proposes a concrete validation method, talking to other prospects with similar workflows, rather than assuming one success generalizes automatically.
Explicitly separates the reusable core capability from the customer-specific wrapper, which is the central distinction the question is testing for.
States a clear standard for saying no: if the bespoke elements do not reduce meaningfully for the second customer, it stays a one-off, not a roadmap item.
Proposes a measurable validation test, reduced integration effort for a second customer, to prove the decision to productize was correct rather than assumed.

Assuming one successful bespoke deployment automatically means it should become a standard product feature.
Failing to separate the reusable core from the customer-specific customization, treating the whole bespoke solution as one unit.

How would you handle the original customer's expectations if you decide not to fully productize their specific setup?
What would you do if no other prospect had a similar enough workflow to validate generalization?