Generic question
This question provides little account-specific structure for the conversation.
For IT-services teams, pre-call research prepares hypotheses, the client conversation validates them, and requirements work converts confirmed business logic into a basis for solution design.
Research should cover the business situation, stakeholder role, provider relevance and the consequences to be tested. Recent business change is included where material but is not required.
A useful hypothesis is specific enough to improve a question and remains provisional until tested with the client.
A generic question list provides coverage. Account research adds prioritisation based on the client context.
This question provides little account-specific structure for the conversation.
This question tests a specific hypothesis while leaving the answer open.
The brief should also state what client evidence would make the hypothesis irrelevant or already resolved.
Findings that survive discovery can move into requirements analysis, solution design and scope. Contradicted hypotheses are removed and unresolved points remain explicitly uncertain.
Founders, technical directors, architects and senior consultants often reconstruct client context while also diagnosing the problem. Pre-call account research separates external context preparation from the validation and reasoning that require client participation.
ROI and impact should not be assumed before discovery. If the client confirms an issue, the conversation can then establish where it appears operationally or financially and which measure is appropriate.
Business situation, stakeholder decision and a specific hypothesis.
Confirm or reject the issue and establish how the client experiences it.
Quantify the relevant effect: time, conversion, margin, capacity, cycle time, forecast variance or another measure the client actually uses.
The brief prepares account context, areas worth testing and questions for client validation. Delivery is within two working days.