Nebverse plan
Core
For teams establishing one dependable people system- Employee master and organisation
- Onboarding and documents
- Leave and standard approvals
- Employee self-service
- Company branding and roles
Plans and pricing
Detailed scope first. A tailored commercial quote second.
Nebverse does not publish a one-size-fits-all rate that ignores modules, employee scope, migration, integrations and implementation ownership.
Three capability starting points
Choose the operating depth, then define the implementation.
Plan names describe module scope. The written quote confirms users, locations, data, integrations, rollout and support.
Nebverse plan
Operations
For multi-team businesses connecting time and daily workflows- Everything in Core
- Attendance and shift operations
- Regularisation and overtime
- Advanced approval queues
- Imports and operational reports
Nebverse plan
Complete
For broader governance, payroll and talent operations- Everything in Operations
- Payroll preparation and controls
- Performance and hiring
- Expenses, assets and statutory context
- Expanded implementation governance
Public monetary rates are intentionally hidden. Commercial terms are shared after scope confirmation.
Capability matrix
Understand what each starting point is designed to cover.
Capability areaCoreOperationsComplete
People foundationEmployee records · Organisation structure · Onboarding · Documents · Profile changes · ExitsCore scopeIncludedIncluded
Time and leaveAttendance capture · Shifts and weekly offs · Regularisation · Overtime · Leave policies · Manager approvalsLeave and approvalsIncludedIncluded
Payroll and financePayroll preparation · Variance checkpoints · Payslips and F&F · Benefits and loans · Expenses and travel · Controlled reportsScoped separatelyAvailable extensionsIncluded
Talent and servicePerformance cycles · KRA and KPI · Hiring pipeline · Learning context · Helpdesk · NotificationsScoped separatelyAvailable extensionsIncluded
GovernanceRole-based access · Tenant isolation · Audit history · Module entitlements · Platform oversight · India-first defaultsIncludedIncludedExpanded
Final module availability and depth are confirmed in the written scope. “Available extensions” are not assumed to be included.
What shapes the quote
Commercial scope follows operating effort.
Employee and company scope
Active employees, companies, locations, legal entities and expected growth.
Modules and policy depth
Enabled product areas, approval complexity, shifts, payroll and statutory configuration.
Migration scope
Source systems, history, cleansing, templates, rehearsal and reconciliation.
Integrations
Attendance devices, finance systems, identity, communication and monitoring responsibility.
Implementation and support
Discovery, configuration, training, launch coverage, response expectations and change ownership.
Implementation scope
Know what happens between signature and launch.
Discovery
Confirm roles, policies, modules, data and acceptance criteria.
Configuration
Set tenant identity, access, workflows and initial company rules.
Migration rehearsal
Validate templates, rejected rows and control totals before final import.
Role UAT
Complete employee, manager, HR, payroll and platform journeys.
Launch and stabilise
Release with monitoring, backup, support ownership and rollback evidence.
Support model
Define response and ownership before the first issue.
Support scope can include administrator guidance, issue triage, release coordination and controlled configuration changes. The quote records channels, service windows, severity handling and exclusions.
Discuss support requirementsAdministrator supportConfiguration and operating guidanceIncident triageSeverity, evidence and ownershipRelease coordinationChange, verification and rollbackScope governanceExplicit enhancements and commercial approval
Pricing questions
Commercial clarity without a misleading rate card.
Why are monetary prices hidden?
Employee count is only one cost driver. Modules, policy depth, data migration, integrations, rollout and support can materially change implementation scope.
Will every customer receive a written quote?
Yes. The quote should identify plan, employee and company scope, modules, implementation assumptions, support and commercial terms.
Can we start with fewer modules?
Yes. A phased release can begin with a focused operating scope while preserving a roadmap for connected modules.
Is migration included automatically?
No assumption is made. Source systems, history, cleansing and rehearsal are assessed before migration work is committed.
Can a partner resell or implement Nebverse?
Partnership scope can be discussed separately, including responsibilities, support, enablement and commercial governance.
Can a quote change later?
Changes in employee scope, modules, integrations or service expectations should be handled through an explicit written change rather than hidden assumptions.
Build the quote from real scope
Tell us how your organisation works today.
Share employee range, locations, priority modules, current systems and target timeline. We will use that context for a guided conversation and tailored proposal.