Current product boundary

A governed operating foundation with CRM released end to end.

VercentLabs ERP currently delivers identity, organisation context, permissions, governed business data, approvals, audit history, billing controls and CRM across web and mobile. Eleven operational modules remain explicit roadmap scope.

Book a released-scope demo Inspect all released features

Released CRM

Run the customer lifecycle from capture to governed decision.

The released module supports staff entry, signed public capture, import, assignment, scoring, qualification, conversion, opportunity progression, activities, campaigns, reports and privacy records.

Supported opportunity stage changes and activity completion can be requested through transactional approvals with permission checks, separation of duties and immutable decision history.

Lead capture, duplicate controls and deterministic scoring
Lead conversion into partner, contact and opportunity records
Opportunity pipeline, forecasting and stage history
Tasks, calls, meetings and follow-up ownership
Campaigns, sequences and consent-aware outbound processing
CRM dashboards, reports, mobile workflows and offline-safe mutations

Implemented foundation

Keep identity, context and evidence consistent underneath the module.

Account lifecycle

Registration, verified email, sessions, password recovery and protected authentication flows live in the secure ERP application.

Organisation context

Companies, branches, departments, teams, cost centres and active operating context constrain application behaviour.

Permission enforcement

Navigation, APIs, commands and PostgreSQL row-level security enforce role, organisation, company and branch boundaries.

Governed master data

Business partners, contacts, items, warehouses, currencies, terms and tax setup provide shared records for current and future modules.

Audit and approvals

Security events, business changes and supported CRM decisions retain traceable user, version and command evidence.

Commercial controls

Organisation-level trials, entitlements, usage and Razorpay integration remain gated by production configuration.

Roadmap — not released

Eleven modules are visible product direction, not current functionality.

Accounting, Procurement, Sales, Stock, Manufacturing, Projects, Assets, Point of Sale, Quality, Support and HR & Payroll cannot be activated in the current release.

Each module will become available only after its records, permissions, workflows, approvals, reporting, migrations, web experience, mobile scope and acceptance evidence are complete.

Review the transparent module map

Evaluation method

Test a real operating scenario—not a feature slideshow.

Use at least two organisations to prove tenant isolation
Use administrator and restricted roles to prove permission denials
Import realistic records and inspect row-level recovery
Run lead qualification, conversion and opportunity progression
Request and decide a supported approval command
Inspect reports, audit history and mobile permission behaviour

Review implementation approach

Next step

Evaluate what exists today before discussing what comes next.

Bring one customer workflow, the real users, operating boundaries and measurable acceptance criteria. The demo will stay inside released scope.

Book a released-scope demo Open the module roadmap

Current product boundary

A governed operating foundation with CRM released end to end.

Book a released-scope demo Inspect all released features

Released CRM

Run the customer lifecycle from capture to governed decision.

The released module supports staff entry, signed public capture, import, assignment, scoring, qualification, conversion, opportunity progression, activities, campaigns, reports and privacy records.

Supported opportunity stage changes and activity completion can be requested through transactional approvals with permission checks, separation of duties and immutable decision history.

Lead capture, duplicate controls and deterministic scoring
Lead conversion into partner, contact and opportunity records
Opportunity pipeline, forecasting and stage history
Tasks, calls, meetings and follow-up ownership
Campaigns, sequences and consent-aware outbound processing
CRM dashboards, reports, mobile workflows and offline-safe mutations

Implemented foundation

Keep identity, context and evidence consistent underneath the module.

Account lifecycle

Registration, verified email, sessions, password recovery and protected authentication flows live in the secure ERP application.

Organisation context

Companies, branches, departments, teams, cost centres and active operating context constrain application behaviour.

Permission enforcement

Navigation, APIs, commands and PostgreSQL row-level security enforce role, organisation, company and branch boundaries.

Governed master data

Business partners, contacts, items, warehouses, currencies, terms and tax setup provide shared records for current and future modules.

Audit and approvals

Security events, business changes and supported CRM decisions retain traceable user, version and command evidence.

Commercial controls

Organisation-level trials, entitlements, usage and Razorpay integration remain gated by production configuration.

Roadmap — not released

Eleven modules are visible product direction, not current functionality.

Accounting, Procurement, Sales, Stock, Manufacturing, Projects, Assets, Point of Sale, Quality, Support and HR & Payroll cannot be activated in the current release.

Each module will become available only after its records, permissions, workflows, approvals, reporting, migrations, web experience, mobile scope and acceptance evidence are complete.

Review the transparent module map

Evaluation method

Test a real operating scenario—not a feature slideshow.

Use at least two organisations to prove tenant isolation
Use administrator and restricted roles to prove permission denials
Import realistic records and inspect row-level recovery
Run lead qualification, conversion and opportunity progression
Request and decide a supported approval command
Inspect reports, audit history and mobile permission behaviour

Review implementation approach

Next step

Evaluate what exists today before discussing what comes next.

Bring one customer workflow, the real users, operating boundaries and measurable acceptance criteria. The demo will stay inside released scope.

Book a released-scope demo Open the module roadmap

A governed operating foundation with CRM released end to end.

Run the customer lifecycle from capture to governed decision.

Keep identity, context and evidence consistent underneath the module.

Account lifecycle

Organisation context

Permission enforcement

Governed master data

Audit and approvals

Commercial controls

Eleven modules are visible product direction, not current functionality.

Test a real operating scenario—not a feature slideshow.

Evaluate what exists today before discussing what comes next.

Loading the operating context.

A governed operating foundation with CRM released end to end.

Run the customer lifecycle from capture to governed decision.

Keep identity, context and evidence consistent underneath the module.

Account lifecycle

Organisation context

Permission enforcement

Governed master data

Audit and approvals

Commercial controls

Eleven modules are visible product direction, not current functionality.

Test a real operating scenario—not a feature slideshow.

Evaluate what exists today before discussing what comes next.