Request a Demo
Book a Free Demo
Grow your profits with V-Count – join the world’s leading companies already increasing their profits with us.
What to Expect From Your V-Count Demo
Booking a demo is the first step. This section explains what usually happens next, how to prepare and which questions to bring. It also covers how to judge a pilot, so you can make a fair decision. You do not need any technical knowledge to book. Our expert will guide the conversation.
What happens after you submit the form
- We receive your request. The form above asks for your name, company, email, phone number and industry.
- An expert reaches out. As the confirmation message says, one of our experts will contact you.
- We agree on a time. The demo is a live conversation, tailored to your sites.
- We walk through the platform. You see how sensor data becomes reports in BoostBI.
- We discuss next steps. This may include a site survey, a quote or a pilot.
What a demo usually covers
- Entrance counting. How Nano AI counts people crossing defined indoor entrance lines, with accuracy up to 99%.
- Zones and heatmaps. How Nano Prime supports zone measurement, heatmaps, dwell and visitor flow.
- Outdoor counting. When Nano Outdoor fits weather-exposed sites.
- Reports and KPIs. How BoostBI shows traffic, conversion and occupancy.
- Integrations. How sales data connects to visitor data.
- Pricing structure. How the quote is built per sensor.
How to prepare
A little preparation makes the demo far more useful. Try to gather:
- Your sites. How many locations, and what type: store, mall, museum, office or other.
- Your entrances. How many doors each site has, and roughly how wide they are.
- Ceiling height. Nano AI supports mounting from 2.2 to 7 m. A rough height helps.
- Power and network. Nano AI uses 5 V USB-C power and Wi-Fi, with an optional external PoE splitter.
- Your sales system. The name of your POS or e-commerce platform.
- Your goals. What you want to learn: traffic, conversion, staffing, zones or occupancy.
- Your team. Invite people from operations, IT and finance if they will be involved.
Who should join the demo
Different people care about different parts of the solution. Consider inviting:
- Operations or retail managers. They will use traffic, conversion and staffing reports.
- IT. They can answer questions on Wi-Fi, power, network rules and integrations.
- Finance. They will compare the full quote and plan the budget.
- Marketing. They may want storefront capture rate and campaign timing.
- Facilities or venue teams. They may need occupancy reporting.
Questions we may ask you
To tailor the demo, our expert may ask:
- What decisions do you want the data to support?
- Do you already count visitors? If so, how?
- Which KPIs do you report today?
- Are any entrances outdoors or exposed to weather?
- Do you want to see zones, dwell time or heatmaps?
- How many staff work at a typical site?
KPIs worth asking about
Ask the expert to show how these KPIs are calculated in BoostBI:
- Conversion rate = eligible purchase transactions ÷ eligible store visits × 100, for the same store and period.
- Revenue per visitor = net sales ÷ eligible visits.
- Storefront capture rate = eligible entries from a defined passing stream ÷ eligible passing traffic × 100. See storefront analytics.
- Sales per labour hour = net sales ÷ paid labour hours.
- Visits per labour hour, which describes workload, not individual performance.
If you need occupancy, ask about coverage of all entrances and exits, the baseline and checks for missing data. Counting does not replace venue safety procedures.
Questions to bring
- Which sensor suits each of our entrances or areas?
- What does the site survey check, and who does it?
- How will staff be excluded from the counts?
- How often will reports refresh?
- Can BoostBI connect to our sales system?
- Which features are included, and which are optional?
- How is the data processed, and who can access it?
- What should a pilot look like for our sites?
Answers to common demo questions
Staff exclusion: V-Count offers three methods: lanyard, shoulder tag and mobile app. Staff movement should be tested separately.
Refresh timing: BoostBI typically refreshes reports every 10 minutes. Enabled real-time configurations can refresh as often as every minute. POS import timing is separate.
Integrations: Native Shopify and Nebim connectors; working integrations for VendPOS, Nayax, ImagineX and QuickBooks; manual sales import; and a scoped REST API.
Pricing: Pricing is per sensor. Some sublicences are included in the quoted BoostBI package. API access, staff exclusion, demographics, queues and heatmaps are separately selectable. Compare the full quote: hardware, software, installation, integration and support.
Data handling: Compatible sensors process measurements on the device and send analytics outputs to the platform. Review data flows, access, retention and connected systems for your setup.
After the demo: the site survey
If you decide to move ahead, installation starts with a site survey. It checks:
- Mounting height.
- Field of view.
- Obstructions, such as signs, displays or beams.
- Power access.
- Network access.
Each model has its own installation specifications. There is no universal installation time, so ask for a plan for your sites.
How to evaluate a pilot
After the demo, many teams run a pilot. A representative pilot is the fairest way to judge the results. Agree on these points before you start:
- Counting lines and zones. Decide exactly what each sensor should measure.
- Exclusions. Agree how staff, repeat entries, returns and cancellations are treated.
- Coverage. Check that every relevant entrance is covered.
- Reference counts. Plan manual counts to compare with the sensor data.
- Busy periods. Include peak hours and group traffic, not only quiet times.
- Acceptance criteria. Write down what "good enough" means before you look at results.
Test optional analytics, like gender-and-age, separately from entrance counts. For zones, define and validate boundaries.
Reading pilot results fairly
- Compare equivalent periods, such as the same weekdays.
- Note promotions, weather and opening hours.
- Remember that a before-and-after change does not prove causation.
- Use clear KPI formulas. Conversion rate = eligible purchase transactions ÷ eligible store visits × 100.
- Revenue ÷ visits is revenue per visitor, not conversion.
A simple planning scenario
This is an example, not a forecast. Take 1,000 daily eligible visits. A 3-percentage-point conversion increase at $45 per transaction would add $1,350 in daily revenue. Over an assumed 30-day month, that is $40,500. Use your own figures to see what a change could mean. No uplift is guaranteed.
Quick FAQ
Do I need to know my exact ceiling heights?
No. A rough idea helps in the demo. The site survey later confirms height, field of view and obstructions.
Can you work with outdoor entrances?
Nano Outdoor is intended for weather-exposed counting. Mounting, coverage, sunlight, direction rules and peak traffic should be validated on site.
How do I exclude staff from counts?
You can choose a lanyard, a shoulder tag or the mobile app. Whichever you pick, test staff movement separately and keep the rules consistent.
Can the demo cover several sites?
Yes. Share your site list and entrance counts in advance, so the expert can discuss each type of site.
Is the demo free?
Yes. This page offers a free demo.
Can you count in dark spaces?
Nano AI has built-in IR LEDs that support counting at 0 lux.
Can you show visitor demographics?
Nano AI supports entrance counting and gender-and-age analytics together, with the compatible configuration and selected licence. Validate demographic results separately.
What does the AI Sales Coach do?
It gives targeted weekly suggestions from each store's data in BoostBI. Managers review them, act and compare the KPI later. It is guidance, not a guaranteed uplift.
Will the data explain why sales changed?
No. Counting data shows what happened, not why. It helps you ask better questions and compare periods fairly.