See the whole picture.
What matters, what to check, and where to go from here.
- 01A LITTLE MORE CLARITY
Explain the proposed use case
Describe your organization, the people or workflow you want to support, intended countries and the decision you need help making. Distinguish an employee-wellbeing program, clinical workflow, partnership and developer integration; they have different delivery and data requirements.
- 02A LITTLE MORE CLARITY
Bring operational details to the discussion
Estimate the number of participants, timeline, existing tools and required support. Identify procurement, security or legal review needs early. Ask which parts of the proposal are currently available and which require scoping, rather than treating a public description as a contractual commitment.
- 03A LITTLE MORE CLARITY
Discuss data responsibilities before a pilot
Clarify consent, access, retention and whether reporting can remain aggregate. Do not include individual employee or patient health records in an initial enquiry. Any clinical or personal-data workflow needs its own review and documented responsibilities before records are shared.
Review your data choices - 04A LITTLE MORE CLARITY
Request a concrete next step
Ask for the relevant demo, current documentation or a scoped proposal, including price basis, support and acceptance criteria. A submitted enquiry is not an activated service or API credential. Use a pilot with a clear outcome before planning a larger rollout.
