VR AR CRM
In VR and AR, sales do not sell a product but a pilot: the customer first wants to put the headset on, then to see their own scenario. When where the demo device is — which trade fair or which customer — and what the pilot has to prove are kept in separate places, both cause trouble in the same week.
Every headset is a record with a serial number; the event it is at, the person who received it and the expected return date are its fields, and overdue ones appear in a list.
- Plan trade fair and customer demos as tasks; record where, with whom and with which device they were done, with location verification
- Write the pilot project's scope, scene count and success criterion into fields on the opportunity record so that sales and production share the same definition
- Track headsets and stations by serial number; see which device is with whom and its return day from a single list
- Keep the technical, purchasing and marketing stakeholders at the enterprise buyer in separate contact records and link their objections to the record
| Demo Task | A demo is a task; the date, the venue, the participants and the device used are in fields, it is closed from the mobile app, and the location is verified. |
|---|---|
| Pilot Opportunity | The pilot is an opportunity record with its own stages; the scene count, the device model and the success criterion sit in fields, and a change of scope is recorded. |
| Hardware Inventory | Every headset and station is a record with a serial number; the event it is at, the person who received it and the expected return date are in its fields. |
| Stakeholder Map | The technical, purchasing and marketing representatives are separate contact records under the account; the role field and the meeting note stay separate on each one. |
In a VR/AR studio the sales cycle is long and starts with a physical step: the headset goes on the customer. This demo sometimes happens at a trade fair, sometimes in the customer's meeting room; then the pilot is discussed — how many scenes, which device, which venue, how long. The pilot's success criterion is left spoken in the meeting, and once production starts the link between the scene count and the budget breaks. Meanwhile the hardware travels: headsets going to fairs, the demo kit left with a customer, the station installed in the showroom. Which serial-numbered device is with whom lives in the memory of somebody on the team. On the enterprise buyer's side, the decision is not with one person; the technical team, purchasing and marketing are each convinced separately, and these conversations are scattered across different people's notes.
In Rapitek CRM a demo is a task; where it was done, with whom and with which device sits in fields, it is closed from the mobile app in the field, and its location is verified. The pilot is an opportunity record with its own stages: because the scope, the scene count, the device model and the success criterion are written into fields, production and sales both look at the same definition, and a change of scope leaves a trace. Hardware is a record that carries a serial number; which event it is at, who has it and since when are tracked, and those past the expected return day appear in a list. Every stakeholder at the enterprise buyer is a separate contact record under the account; who raised which objection stays on the card. After installation, the person taking delivery signs on the signature screen in the mobile app.
The scope of the plans and the separately priced items are written on the pricing page.
