Bring a real problem from your week. The demo will start there.
A hard-to-place appointment, an overlong field day, a forgotten client follow-up, or a number you cannot explain: choose a situation your team actually handles. The demo starts with that case, not with a generic tour of features.
Bring a situation your team already handles.
Describe what happens today, the constraint that matters in this case, and what you want to verify. The demo can then stay focused on that situation instead of a list of features.
A demo is a discovery process: it can examine behaviour in the context presented without guaranteeing a future financial or operational result.
- 01The situation
An appointment, a field day, a client follow-up, or a number you are trying to understand.
- 02The constraint
The condition that matters in this case: schedule, capacity, service area, price, or another relevant rule.
- 03What you want to verify
The behaviour to examine, the limits to confirm, and the questions that remain open.
Describe the problem you want to examine.
Five pieces of information are enough to prepare the request. Describe the situation without sending sensitive data.
- Name and business email
- Company and team size
- The main problem to examine
- No sensitive data