Ask who makes and carries the decisions
Find out whether the people in the first meeting will remain responsible through delivery. Every hand-off creates another interpretation of the problem, and ambiguity compounds fastest between strategy, design and engineering.
- Who owns the product argument and prioritisation?
- Who can change scope when evidence contradicts the brief?
- Who is accountable for the behaviour of the production release?
Distinguish a demonstration from a product
A prototype should answer a specific uncertainty. Production software must also handle accessibility, failure states, security, observability, performance and change. A credible partner is explicit about which standard is being delivered and what remains before real operation.
Inspect the path after launch
Ask how the system will be documented, measured and transferred. The strongest partner is not the one that makes itself permanently necessary; it is the one that leaves clear decisions, maintainable foundations and an honest view of the next priorities.