First, describe the product question
An initial conversation should establish what the product does, who uses it, what remains uncertain, and why that uncertainty matters to the next decision. A redacted screenshot, a sample message, or a short description is often enough to discuss the scope.
We identify the information already available and the material that would need to be supplied. If the question depends on device access, household data, or specialist equipment, the scope records that dependency rather than assuming it will be available later.
Then, agree the work in writing
The project brief defines activities, deliverables, acceptance criteria, review points, responsibilities, and commercial arrangements. It also addresses access, confidentiality, rights to supplied material, and the treatment of changes. Timing and fees depend on the actual scope and are agreed directly.
An early phase may produce a dataset review or a limited proof of concept before a larger commitment. Intermediate reviews help the client examine assumptions and decide whether the next stage remains useful. A change in equipment or intended behavior may require a revised scope.
Finally, review what the work supports
The closing review connects the delivered evidence with the original question. It records what the team can reasonably decide, what remains uncertain, and which follow-on activities require different inputs or specialists.
The engagement ends with the agreed files and instructions. A possible next phase is discussed on its own merits. There is no automatic commitment to installation, ongoing hosting, production support, or a field trial simply because a research prototype has been completed.