BOOK A DEMO
Let us discuss your project.
A live walkthrough of the platform, assembled around your equipment, your protocols and the way your operation actually works — not around a fixed script.
SCOPE
A demo built around your use case.
We do not run a fixed slide deck. The session is assembled from the parts of the platform that matter to what you are trying to operate.
Devices and digital twins
How a category of equipment becomes a model, a version and an installed instance — with its serials, its location and its system.
Metrics and commands
How a raw payload is decoded into comparable metrics, and how a command is declared, validated and sent back to the field.
Rules and automation
How rules evaluate metrics and states, and what happens when one fires — on a schedule, on a threshold, or on a sensor reading.
Screens and integrations
Dashboards, widgets and the interactive map, plus how a protocol instance is configured for the equipment you actually have.
Tell us which parts to show.
The form below has a checklist for exactly that — tick what matters and we prepare the session around it, rather than around what we usually demo.
Prefer email? Write to sales@vision.ro
THE FORM
Tell us what you need.
Two checklists and a few lines about your infrastructure. That is all we need to prepare a session that is actually about you.
Your details go to the Vision sales team and are used only to arrange and prepare this session.
HOW IT RUNS
A focused technical and commercial conversation.
Around 60 minutes, remote by default. Longer or on site if the scope justifies it.
01
You send the brief
The form below. Your infrastructure, what you need, and which parts of the platform you want to see.
02
We prepare the session
We assemble the walkthrough around your answers and tell you in advance what we will and will not be able to show.
03
The walkthrough
A live tour of the platform on the points you selected, in the order that makes sense for your operation.
04
Questions
The part that usually matters most: your equipment, your protocols, your constraints, and what the platform does not do.
05
What happens next
A written summary of what was covered, what is configuration, what would need integration work, and what is not available today.
BEFORE THE SESSION
What to bring, and what we will not do.
The more concrete the input, the more the hour is worth. And it is only fair to say in advance where the session stops.
Bring us your infrastructure
None of this has to be complete. Whatever you have makes the conversation more specific.
- The equipment — what is installed, who made it, roughly how many units
- The transport — protocol, network, gateway, and who operates it today
- A payload — one real message, and what its fields mean
- The operation — who works in it, and what they need to see or control
- The constraints — hosting, security requirements, systems it has to talk to
What the session is not
We would rather say this here than in the meeting.
- We do not show another organisation’s live system or data
- We do not present benchmark figures or uptime numbers we cannot substantiate
- We do not demonstrate capabilities that are on the roadmap as if they existed
- We do not integrate your equipment during the call — we tell you what it would take
- We do not need a signed anything to have the conversation
WHO SHOULD JOIN
Three people are usually enough.
The session works best when the operational, the technical and the commercial questions can be answered in the same conversation.
The person who owns the infrastructure
Whoever answers for the lighting, the meters, the plant or the building portfolio. They know what breaks and what nobody can see today.
The engineer who will integrate it
The one who knows the protocol, the payload and the gateway. Most of the useful half of the session happens with them in the room.
The person who signs
Deployment model, hosting, access control, what is configuration and what is project work — that part is short, but it is better done in the same hour.