Your workflow
Tell us who uses the system, the tools you have and the task that needs attention.
Demo request · BANDEVI01 02 03
Request a focused walkthrough.
Bring one workflow you want to improve. We’ll review a relevant example, discuss what your business needs and agree the next step.
A relevant example
Review the available demonstration and identify the features or integrations your project would need.
A clear next step
Agree the open questions and whether to prepare a written scope and quote.
Your preferred time is a request until the team confirms it. Demonstration availability, project scope and commercial terms are agreed separately.
Tell us what you want to review
Name, email, service and a short description are enough to begin. Fields marked optional can be left blank.
Before you hire us: ownership, handover, payments and support
Your walkthrough agenda
Know what we will discuss before you request a demo.
Use this agenda to plan a focused conversation. The team confirms which demonstration screens are available and agrees the meeting format with you.
1. Understand your workflow
Describe one task you want to improve, the people involved and the tools you use today. Choose the outcome you want to review first.
2. Walk through a relevant example
Review the available example from enquiry to next action, including the records, roles and reports relevant to your request. Identify what needs configuration or development.
3. Agree a practical next step
List open questions, required integrations and the proposed first release. Decide whether to prepare a written scope and quote, arrange another discussion or pause.
Bring these three things
- Your main business problem and current tools.
- An anonymized example of a task, enquiry or report.
- The people who will use or approve the proposed system.
Please leave out passwords, payment details and customer personal information.
Leave with clearer requirements
Use the discussion to distinguish available demonstration features from proposed development and third-party dependencies. Any price, delivery date, ownership or support commitment belongs in the written proposal.
Prepare your project briefChoose the conversation you need.
Explore a service before requesting a walkthrough.
Websites & Apps
Pages, customer journeys, enquiries, portals and app workflows.
Explore serviceCRM & ERP
Lead control, operational records, permissions and reporting.
Explore serviceTravel Technology
Travel websites, agency workflows, supplier dependencies and booking requirements.
Explore serviceWhat happens after you send?
1. Keep your enquiry reference
A successful submission shows your saved enquiry reference on screen. Keep it for follow-up; submitting a request does not reserve a meeting.
2. Confirm the meeting details
The team reviews your selected service and priorities, then contacts you to agree availability, the format and the relevant demonstration. Your preferred time is a request until confirmed.
3. Review the proposed scope
After the discussion, agree the next action. If you proceed, review the written scope, dependencies, pricing, acceptance checks and support arrangements before approving work.
Review the proposal checklistDoes a demo request commit me to a project?
No. Project scope, pricing, payment milestones and support terms are agreed separately in writing.
Do I need to share customer data?
A description of your workflow is enough for the first discussion. Use anonymized examples if they help explain your requirements.