Commercial information shown only to the right audience.
This private commercial ecosystem is designed for business discussions with prospective Licensed Resellers or Corporate Users. Select one route first. The page will then show the relevant commercial logic, support layer, and activation path for that route.
Route-specific visibility
Reseller viewers do not see Corporate User content. Corporate viewers do not see Reseller content.
Principal-led model
VNT remains Principal and authorizes access to the Neurometric platform with EEG device infrastructure.
Meeting-friendly flow
Reseller viewers do not see Corporate User content. Corporate viewers do not see Reseller content.
Choose the commercial
route for this discussion
Once a route is selected, only the relevant information will be shown on this page.
Licensed Reseller
route
This view is designed only for prospective Licensed Resellers. It focuses on break-even visibility, payment flow, onboarding readiness, and the support features that reduce commercial uncertainty.
Illustrative break-
even scenario from
the reseller point
of
view
This simulation is intentionally built from the reseller point of view. The fixed annual access assumptions are locked at USD 9,500 in Year 1 and USD 8,500 from Year 2 onward. Only the token tier, selling price, report volume, evaluation horizon, and EEG device wear & tear profile are adjustable.
Adjust only the operating assumptions
Fixed commercial assumptions
Year 1 annual access = USD 9,500
Year 2 renewal = USD 8,500
VNT token tiers for Licensed Reseller
- 5 reports / monthUSD 120 / report
- 10 reports / monthUSD 115 / report
- 15 reports / monthUSD 110 / report
- 20 reports / monthUSD 105 / report
- 25+ reports / monthUSD 100 / report
Minimum monthly purchase is 10 reports. Additional token purchase follows packages in multiples of 10.
Interpretation
This simulator tests whether the reseller model reaches break-even under the current operating assumptions, using prepaid token logic, the fixed annual access structure above, token tier pricing, and a built-in EEG device wear & tear reserve.
Illustrative reseller economics
Under these assumptions, break-even is reached in about 7.7 months in Year 1. The business becomes viable when resellers actively manage three critical levers: maintaining premium pricing discipline, ensuring consistent monthly report volume, and building a repeatable client pipeline that sustains utilization.
How payment works for Licensed Reseller
- Payment method: manual transfer for annual license and report token purchase.
- Initial payment: VNT receives the annual license payment and EEG device purchasing payment first.
- Delivery step: VNT processes EEG device delivery to the partner address after payment confirmation.
- Token start: partners purchase their initial report tokens along with the annual license to prepare for post-onboarding delivery.
- Usage policy: minimum purchase target is 10 reports per month, with additional token purchase available in packages of 10 after the monthly minimum is met.
Asynchronous LMS onboarding included
- How to use the EEG device correctly and consistently
- How to maintain the device and manage routine care
- How to order additional or replacement devices
- How to understand the report structure
- How to interpret ANI reports for business discussion
Structured onboarding support
Implementation guidance, readiness checkpoints, and early activation support from payment through go-live.
View support detailsKnowledge base & LMS
Always-on learning modules, operating guides, and reference materials for devices, reports, and commercial workflow.
View support detailsTicket-based helpdesk
Centralized issue handling for delivery, device, usage, and
platform-related questions.
Available during weekdays office hours. VNT operates in
GMT+7, so time-zone difference should be considered in response
expectations.
Service response standards
Defined response expectations and escalation path for higher-priority support cases.
View support detailsDevice continuity support
Guidance for additional purchases, replacement planning, and device continuity when wear begins to affect operations.
View support detailsCommercial continuity review
Periodic review discussions to help align report volume, renewal readiness, and operating continuity.
View support detailsCorporate User
route
This view is designed only for prospective Corporate Users. It focuses on internal deployment logic, pricing, device replacement planning, payment flow, onboarding readiness, and the support structure needed for safe rollout.
Commercial logic for
organizations deploying
ANI internally
This route is designed for organizations using ANI inside their own leadership, talent, and transformation systems. The focus is on procurement clarity, deployment readiness, and safe internal rollout.
Corporate report tiering
- Purchase 30 reportsUSD 200 / report
- 30 < reports < 60USD 190 / report
- 60+ reportsCustom review recommended
Corporate pricing is intentionally higher than reseller pricing because it is a direct-use internal deployment model rather than a channel resale model.
EEG device replacement logic
- EEG devices typically need replacement after approximately 80–90 uses.
- Replacement need correlates directly with the number of reports executed.
- Reference device value = USD 999 / device.
- Corporate planning should therefore consider both report volume and replacement cycle.
How payment works for Corporate User
- Payment method: manual transfer for annual license and report token purchase.
- Initial payment: VNT receives annual license and EEG device purchasing payment first.
- Delivery step: VNT processes EEG device delivery to the corporate address defined during onboarding.
- Token start: organizations purchase their initial report tokens along with the annual license to ensure readiness upon completion of onboarding.
- Usage policy: minimum target is 5 reports per month, with additional per-report purchase available after the monthly minimum threshold is met.
Asynchronous LMS onboarding included
- Operational instruction for EEG device usage
- Maintenance and care guidance
- Additional device purchasing and replacement flow
- Understanding ANI report structure
- Interpretation for HR, leadership, and transformation stakeholders
Structured onboarding support
Implementation guidance, readiness checkpoints, and controlled activation from payment through operational start.
View support detailsKnowledge base & LMS
Always-on learning resources and documentation to support internal users and program owners.
View support detailsTicket-based helpdesk
Centralized handling for deployment questions, device issues, report usage,
and operating concerns.
Available during weekdays office hours. VNT operates in
GMT+7, so time-zone difference should be considered in response expectations.
Service response standards
Defined support response windows and escalation logic to make the platform feel dependable.
View support detailsDevice continuity support
Guidance for additional devices, replacement planning, and keeping internal deployment stable over time.
View support detailsCommercial continuity review
Periodic review discussions to help align deployment scope, replenishment planning, and renewal readiness.
View support detailsGetting you ready to deliver — properly.
Before you start working with clients, we walk your team through everything they need to know — from how to talk about the product, to how to run a session, to what to do when something unexpected happens.
Two tracks, eight modules
Modules 1–4 cover the big picture: what Vanaya does, how the partnership works, what you can and can't say to clients, and how to qualify the right opportunities. Everyone goes through this before anything client-facing begins.
Modules 5–8 are hands-on: how to set up and use the platform, how to run a recording session, how to generate reports, and how to communicate results confidently within the right boundaries.
| # | What it covers | Who attends | Time |
|---|---|---|---|
| 1 | How Vanaya works and your role as a partner | Everyone | 35–45 min |
| 2 | What the product does and how to explain it | Everyone | 40–50 min |
| 3 | Data handling, boundaries, and what's off-limits | Everyone | 45–60 min |
| 4 | Identifying and qualifying the right clients | Sales and account leads | 40–50 min |
| 5 | Setting up the platform and managing user access | Operational users | 45–60 min |
| 6 | Running a recording session from start to finish | Delivery team | 60–75 min |
| 7 | Generating and handling reports in the platform | Reporting users | 50–65 min |
| 8 | Explaining results to clients — and knowing when to stop | Client-facing leads | 50–60 min |
You unlock more as you complete each stage
This keeps things from moving faster than your team is ready for.
| Stage | After completing | What you can do |
|---|---|---|
| A | Modules 1–4 | Start having client conversations using approved materials. |
| B | Module 5 | Get into the platform with role-appropriate access. |
| C | Module 6 | Run supervised recording sessions. |
| D | Module 7 | Generate and handle reports. |
| E | Module 8 + sign-off | Communicate results to clients within approved limits. |
The onboarding teaches you how to use and deliver the product — not how to rebuild it. Source code, scoring logic, raw data, and analytical methods stay proprietary to Vanaya. That's what protects the integrity of what you're selling.
Your reference library — always open.
Live sessions get your team started. The knowledge base keeps them going. Whether someone's new, refreshing their memory, or stuck at 11pm in a different time zone — the answers are already there.
Step-by-step guides for setting up and running a session the right way, every time.
What to do after each session, how to spot wear early, and when to think about replacement.
A clear breakdown of what each section means and how to talk about results confidently.
Walkthroughs for every step: setting up projects, adding participants, and generating reports.
How to start sessions, sync data, and handle the common hiccups without needing to call support.
A quick reference for what you can say, what to avoid, and when to escalate.
No more starting from scratch
When a team member leaves or a new one joins, you shouldn't have to re-run the whole onboarding. The knowledge base means anyone can get up to speed on their own — without waiting for a live session to be scheduled.
Support that doesn't sleep
VNT's helpdesk runs on GMT+7. If you're in a different time zone and something comes up outside office hours, the knowledge base is your first stop. Most routine questions have an answer there — without needing to wait for a response.
The knowledge base handles routine operational questions. If something feels sensitive — a boundary question, an unusual report result, or a client request you're not sure about — escalate it. Don't try to look that up yourself.
A clear path when something needs attention.
Not everything needs a ticket — and not everything should be handled alone. The helpdesk makes it easy to know the difference. You get a structured place to raise issues, and a team that knows how to route them correctly.
- Can't log in or access the platform.
- The Runner app isn't syncing or a session didn't record properly.
- Something in Neurometric Web isn't behaving as expected.
- Device connection problems.
- Need a password reset or permission change.
- Not sure if something a client is asking for is allowed.
- A data or confidentiality question you don't want to answer without checking first.
- Someone requesting access or information that feels outside the agreed scope.
- Need to change a user's role or remove access.
- A client or stakeholder is asking something you're not certified to answer.
- A report came out looking unusual — something doesn't add up.
- You're not confident sharing a result without a second opinion.
- Want to refresh your interpretation training.
Weekday office hours, GMT+7
That's Indonesia time. If you're in a different time zone, plan ahead — tickets submitted outside hours will be picked up at the start of the next business day. For routine questions outside these hours, the knowledge base is your first stop.
What to include in your ticket
- Your role and what access you have.
- Which platform the issue happened on.
- What you were doing when it happened.
- What the issue actually looked like — not just the outcome.
- What you've already tried.
If something feels outside your authority — stop and escalate. That applies to sensitive client requests, unusual report outputs, or anything where you're unsure whether it's within scope. It's always better to check than to push through and get it wrong.
You'll know what to expect — and when.
A support system is only as good as the clarity behind it. We define how different issues are handled so you can plan around them — and so you're never left wondering whether your ticket is being looked at.
| Type of issue | Examples | What happens |
|---|---|---|
| Routine | Login problems, sync questions, standard workflow queries | Goes into the standard queue. Check the knowledge base first — many of these are already answered there. |
| Technical exception | Failed sessions, corrupted recordings, platform errors outside normal workflow | Escalated ticket. Include your device type, session reference, and what the error looked like. |
| Sensitive boundary question | Restricted client requests, data handling uncertainty, access changes | Goes to a separate review queue — takes a little longer. Do not try to resolve this independently. |
| Report or interpretation question | Client questions you're not certified to answer, unusual outputs, result anomalies | Interpretation review queue. Pause any client-facing communication until you get a response. |
Don't wait for a problem to get serious before raising it. Escalate early when:
- A session didn't complete properly and the standard fix didn't work.
- A client is asking for something you're not sure you're allowed to provide.
- A report result doesn't look right and you're not sure why.
- You're about to do something that might be outside your approved scope.
- You're unsure whether a result is ready to share with a client.
The final module of onboarding runs through real-world scenarios — technical hiccups, difficult client questions, sensitive requests. You'll have worked through the right response before you ever face it live.
Your device won't last forever. Plan for it.
The EEG device is physical hardware. With regular use, it wears down over time — and when it does, your ability to run sessions stops with it. Device continuity support helps you stay ahead of that, so a worn device never catches you off guard.
Roughly 80–90 sessions. That number can vary based on how the device is handled and cared for between sessions.
USD 800 per device. Factor this into your budget from the start — it's a predictable cost, not a surprise one.
Running 30 sessions a month? You'll need a replacement in about 3 months. Higher volume means a shorter cycle — plan accordingly.
Build it into your numbers
The BEP simulator already accounts for device wear as part of your cost per report. Year 1 starts with 2 devices — one working, one as backup. Order your replacement before the first one starts showing signs of wear, not after sessions start getting unreliable.
Include it in your program budget
Replacement isn't an optional extra — it's part of running the program. As your cohort grows, you'll be running more sessions, and replacement cycles will get shorter. Confirm lead times with VNT during onboarding so you're never left waiting for a new device while your program is mid-run.
- Order through VNT using the same payment process as your original device purchase.
- Once payment is confirmed, dispatch begins. Ask VNT about delivery lead time so you can order with enough runway.
- Not sure when to order? Raise a device continuity discussion through the helpdesk — we'll help you work out the timing.
The most avoidable disruption in any EEG deployment is a worn device with no replacement on its way. If your session volume is picking up faster than expected, let us know. We'd rather help you plan ahead than troubleshoot a delivery gap.
We check in. You shouldn't have to chase us.
After the initial setup, the relationship shouldn't go quiet. Commercial continuity reviews are structured check-ins where we look at how things are actually going — and make adjustments before small misalignments turn into real problems.
Is the number of sessions and reports in line with what you planned? If not, what's driving the difference — and what should we adjust?
Based on your current pace, when will you need a replacement device? Let's figure that out before it becomes urgent.
Is your license renewal coming up? We'll make sure you're not scrambling at the last minute — and that your renewal reflects what you actually need.
Thinking about expanding — more users, more clients, a new internal cohort? We'll map out what that looks like commercially and operationally.
- About 3 months in: once we can see how things are actually running — not just how they were planned.
- Mid-year: to get ahead of renewal and device planning.
- Before renewal: to make sure the next year reflects your current reality, not the assumptions from when you first signed up.
- Whenever you need it: if something shifts — volume, team, scope — don't wait for the next scheduled review. Just raise it.
If your numbers have shifted, your team has changed, or something just doesn't feel right about how the relationship is going — say so early. Raise a continuity discussion through the helpdesk. The earlier we look at it, the easier it is to fix.
Data Privacy & Neurometric Data Governance Policy
1. Purpose of the Policy
This policy establishes the foundational governance framework for the lawful and responsible collection, processing, storage, protection, and management of Neurometric® data generated through Vanaya NeuroLab research activities.
This policy defines the regulatory positioning of Neurometric® data governance within Vanaya’s technology architecture and research operations.
2. Scope of Application
This policy applies to Neurometric® research activities conducted through Vanaya NeuroLab and to affiliated entities within the Vanaya ecosystem that are formally authorized to support research, platform, or implementation activities.
This policy applies to Neurometric® research activities conducted through Vanaya NeuroLab and to affiliated entities within the Vanaya ecosystem that are officially authorized to support research activities, platforms, or implementation.
3. Legal and Regulatory Compliance
Vanaya NeuroLab conducts its research activities in accordance with applicable data protection laws, lawful research governance requirements, and relevant cross-border data protection principles where applicable.
Compliance obligations may vary across jurisdictions and shall be implemented under Vanaya’s internal data governance framework in accordance with applicable law.
4. Nature of Neurometric Data
Neurometric® data refers to analytical cognitive indicators derived from signal-based measurements processed through proprietary Neurometric® models developed within Vanaya research programs.
Signal-based data collected in Vanaya research activities are used exclusively for analytical and research purposes and are not intended for medical diagnosis, clinical evaluation, or healthcare decision-making.
5. EEG Device Classification
Devices used within Vanaya research activities are commercial signal measurement tools intended for cognitive analytics and research applications.
Such devices are not used for medical diagnosis, clinical care, or healthcare service purposes within Vanaya research programs.
6. Data Collection Principles
Neurometric® data collection is conducted based on informed consent, transparency principles, and lawful research governance requirements.
Participants are informed regarding the nature, purpose, and scope of data collection prior to participation.
7. Data Anonymization
Vanaya NeuroLab implements anonymization procedures to separate personally identifiable information from neurometric datasets.
Neurometric datasets used for research analytics do not contain identifiable personal information.
Anonymization procedures are implemented to ensure that neurometric datasets used for analytics cannot reasonably identify individual participants.
8. Longitudinal Research Data
Vanaya NeuroLab may maintain anonymized datasets for longitudinal research aimed at understanding cognitive development and adaptive capacity over time.
Longitudinal datasets may include repeated neurometric measurements collected across multiple time periods.
Retention of anonymized longitudinal datasets shall be conducted in accordance with lawful research retention principles, scientific justification, and applicable governance requirements.
9. Data Storage Infrastructure
Neurometric® datasets may be stored within secure cloud infrastructure that forms part of Vanaya’s technology architecture.
Data may be processed within secure infrastructure in accordance with applicable governance, security, and lawful processing requirements.
10. Neurometric® Dataset Ownership
All Neurometric® datasets generated through Vanaya NeuroLab research activities are legally owned by PT Vanaya IP Holder (Indonesia).
Ownership of Neurometric® datasets remains with PT Vanaya IP Holder (Indonesia) regardless of the location of collection, processing, or storage.
Ownership of Neurometric® datasets is established at the intellectual property governance level and remains independent of operational, research, or technical processing arrangements.
11. Data Security Measures
Vanaya NeuroLab implements technical and organizational measures to protect Neurometric® datasets from unauthorized access.
Security measures may include encryption, access control mechanisms, monitoring systems, and role-based restrictions on access to Neurometric® datasets.
12. Ethical Use of Neurometric® Data
Neurometric® data collected through Vanaya NeuroLab research activities shall only be used for scientific, analytical, research, and organizational development purposes.
Neurometric® data shall not be used for purposes that violate ethical principles, participant rights, or the intended non-clinical scope of the Vanaya system.
Ethical use obligations apply to all entities participating in Vanaya research, analytics, implementation, or related data handling activities.
13. Cross-Border Data Governance
Data may be processed within secure infrastructure as part of Vanaya’s technology architecture. Any such processing shall be conducted in accordance with applicable data protection requirements.
14. Research Transparency
Vanaya NeuroLab is committed to transparency in its research methodologies and data governance practices, subject to confidentiality, security, and intellectual property protections.
15. Policy Governance
This policy is governed by PT Vanaya IP Holder (Indonesia).
Operational implementation may be conducted through authorized research, platform, or commercial entities within the Vanaya ecosystem in accordance with their respective roles.
16. Intellectual Property Ownership Clause
PT Vanaya IP Holder (Indonesia) is the legal and exclusive owner of all neurometric datasets, analytical models, algorithms, and related technologies developed within the Vanaya ecosystem.
Such ownership includes all data generated through research activities, platform usage, and commercial assessments.
No rights, ownership, or access to underlying datasets or analytical models are transferred to any third party, including clients, partners, or licensees.
17. Local Transaction Clause
Any transactions conducted within Indonesia in relation to Neurometric® services shall be processed under Indonesian jurisdiction through Vanaya Strategic.
Refund Policy
Konten Refund Policy (bisa diubah nanti sesuai kebutuhan).
Structured Onboarding
A structured deployment sequence that aligns internal stakeholders, establishes operating discipline, and prepares teams for stable day-to-day use before broader rollout begins.
Governance expectations, ecosystem understanding, and deployment purpose. Covers program owners, administrators, and selected leadership stakeholders.
System access, recording workflow, report generation, and support handling. For users running sessions and managing output in Neurometric Web and Runner app.
Governance and output visibility only. No system operation access required. Stage 1 only.
System navigation, session recording, workflow management. Access unlocked after Stage 2 completion.
Report generation, review, and controlled internal release. Scoped to confirmed output-handling readiness.
- Clearer internal ownership and role accountability across the deployment team.
- Stronger alignment on governance expectations and usage boundaries before go-live.
- More disciplined system use with practical operational confidence.
- A reliable, auditable transition into live operations — not an improvised one.
- Internal readiness that can be refreshed as responsibilities evolve.
Source code · Scoring formulas or model logic · Raw datasets · Any information sufficient to reconstruct Vanaya's analytical methods. The program teaches approved use, internal workflow, and controlled report handling only.
Knowledge Base & LMS
Always-on access to learning modules, operational guides, and reference materials. Designed to keep teams capable and consistent beyond the initial onboarding session — especially when responsibilities shift or new members join.
Step-by-step instruction for correct EEG device operation, session preparation, and consistent recording practice.
Routine care guidance, wear pattern awareness, and the process for additional or replacement device purchasing.
Structural explanation of ANI report sections and practical interpretation guidance within approved boundaries.
Navigation walkthroughs, project and participant handling, report generation steps, and status recognition.
Session start, sync confirmation, offline contingencies, and troubleshooting for common recording issues.
Usage boundaries, approved language, restricted actions, and escalation expectations — accessible for ongoing review.
Reducing person-dependency
When key individuals leave or change roles, teams can lose operational confidence. The LMS keeps approved references accessible and repeatable — independent of any single person's memory — so new users can onboard without requiring a live session each time.
Available when live support isn't
Because VNT operates in GMT+7, partners and corporate users in other time zones may encounter situations where helpdesk support is not immediately available. The knowledge base is the first reference point for routine device, system, and reporting questions.
Situations that exceed approved operational scope should still follow the defined escalation path. The LMS supports routine operations — it does not replace governance judgment.
Ticket-based Helpdesk
Centralized issue handling across technical, governance, and interpretation-related matters. The helpdesk clarifies which situations may be managed directly, which must be escalated, and how support is routed.
- System access issues and login failures.
- Runner app sync problems and recording disruptions.
- Neurometric Web navigation and report generation issues.
- Device connectivity and offline contingencies.
- Account credential and permission reset requests.
- Confidentiality and data handling boundary questions.
- Restricted-use requests that may conflict with approved controls.
- Situations where an action's scope is uncertain.
- Governance-sensitive requests that need Vanaya review.
- Access revocation or role reclassification requests.
- Questions that exceed certified interpretation boundaries.
- Unusual or unexpected report outputs requiring Vanaya review.
- Output anomalies, missing data, or unclear result patterns.
- Re-certification or interpretation refresher requests.
Helpdesk availability
Weekdays office-hour model. VNT operates in GMT+7 — partners and corporate users in other time zones should factor this into response planning. Tickets submitted outside hours are handled at the start of the next business day.
What to include when raising a ticket
- Your role and access level.
- Platform and workflow step where the issue occurred.
- Session or project reference where relevant.
- Specific behavior observed — not just the outcome.
- Steps already taken, including any LMS or SOP reference consulted.
When a situation exceeds approved authority, stopping and escalating is a required step. Partners and internal users must not attempt to resolve governance, interpretation, or out-of-scope technical matters independently.
Service Response Standards
Defined response expectations by issue type and a clear escalation path for higher-priority cases. A predictable support structure is what makes the platform feel dependable — especially for globally distributed partners and internal program owners accountable to leadership.
| Issue category | Examples | Handling path |
|---|---|---|
| Routine operational | Login issues, sync errors, standard workflow questions | Standard helpdesk queue. Knowledge base is the first reference before a ticket is raised. |
| Technical exception | Failed sessions, corrupted recordings, platform errors outside normal workflow | Escalated helpdesk ticket. Include device type, session ID, and error description. |
| Governance-sensitive | Restricted-use requests, data handling boundary questions, access reclassification | Governance review queue. Additional response time applies. Do not attempt to resolve independently. |
| Interpretation-related | Report questions beyond certified boundary, unusual outputs, client communication uncertainty | Interpretation review queue. Pause client-facing communication until cleared. |
Escalation should apply during normal operations when warning signs appear — not only after a problem becomes serious. Escalate when:
- Sessions are incomplete, corrupted, or unsynced after following the standard troubleshooting path.
- A restricted request is received from a client or internal stakeholder.
- Report outputs are unusual or differ from expected parameters.
- Proceeding independently would risk governance drift, overreach, or mispositioning.
- Report output release or sharing should not proceed without Vanaya review.
Response standards are reinforced in Module 8 of the onboarding program through scenario reviews covering technical incidents, governance red flags, and difficult client questions — so escalation becomes a practised behavior, not an unfamiliar one.
Device Continuity Support
EEG device performance degrades over time with consistent use. Device continuity support helps plan around wear patterns, manage replacement timing, and keep operations stable as usage volume grows.
EEG devices typically need replacement after approximately 80–90 uses. Actual wear depends on session conditions, handling, and maintenance discipline.
USD 800 per device. Use this as the basis for replacement reserve planning alongside token purchasing assumptions.
At 30 reports/month and 90-use threshold, one device cycles approximately every 3 months. Higher volume shortens this cycle accordingly.
Device planning in the reseller model
- The BEP simulator already factors a device wear reserve per report produced.
- Initial Year 1 assumption is 2 devices for standard deployment and redundancy.
- Replacement should be planned before performance visibly degrades — not after session quality is affected.
Device planning in internal deployment
- Replacement is a predictable operating cost — not an unanticipated one.
- As internal cohort size grows, recording frequency increases and replacement cycles shorten.
- Confirm replacement process and lead time with VNT during onboarding to avoid operational gaps.
- Additional or replacement devices are purchased through VNT using the same payment channel as the initial order.
- Payment confirmation triggers dispatch. Confirm lead time with VNT before a device reaches its wear threshold.
- Device continuity support is available through the helpdesk for ordering timing, replacement scope, and lead time planning.
The most common operational disruption is waiting too long to order. If session volume is tracking faster than expected, raise a continuity discussion with VNT before the replacement need becomes urgent.
Commercial Continuity Review
The commercial relationship should feel managed, not left unattended after payment. Continuity reviews give licensed resellers and corporate users a structured opportunity to align on volume performance, renewal readiness, device replacement planning, and operating assumptions as the relationship matures.
Is actual volume tracking in line with the assumptions made at onboarding? Where are volume gaps appearing and why?
Based on current volume, when are existing devices likely to reach their wear threshold? Is replacement ordering ahead of this or reactive to it?
Is the annual license renewal being planned with sufficient lead time? Are there scope or access changes to reflect in the renewal discussion?
Is there demand to expand volume, add users, or extend into new segments? What commercial and operational steps does scaling require?
- First review (~3 months post go-live): once volume patterns and early operating behavior are visible.
- Mid-year review: aligned to renewal preparation and device replacement planning horizon.
- Pre-renewal review: confirm scope, adjust assumptions, and clarify changes to the commercial relationship.
- On-request: if volume performance, device wear, or governance changes require earlier discussion.
Raise a continuity discussion through the helpdesk whenever volume assumptions, device needs, or renewal readiness have shifted. Do not wait for the renewal conversation to surface issues that can be resolved earlier.