What should you prepare for an emtech project consultation?
Prepare the business problem, affected users, current systems, constraints and a realistic description of the desired outcome. You do not need a complete technical specification. A clear starting brief helps the team identify the right questions and scope the next step.
Describe the current workflow
Explain how the work happens today and where it slows down or fails. Include who owns the process and which teams depend on it. A specific example is often more useful than a long list of technology names.
Bring the main constraints
State locations, operating hours, data restrictions, budget priorities and any target date. Identify dependencies such as another vendor, procurement or a planned office move. Distinguish a fixed deadline from a preferred schedule.
Define what success would look like
Choose a practical measure: a restored service, a supported user group, a functioning integration or a tested pilot. Avoid a broad objective such as “complete digital transformation” without a first deliverable.
Keep initial information appropriate
Share a high-level architecture or anonymised example when possible. Use an agreed secure process if the assessment later needs sensitive files or system access. Do not place passwords or access tokens in the website form.
The consultation should result in a clear next step and a list of information needed for a proposal. Implementation scope, service coverage and commercial commitments are confirmed through the agreed project process.
Put this guidance to work.
Explore the relevant emtech service, then discuss the scope that fits your business.