One Party, Every Role — Unified Customer Intelligence Across Your Entire Business
A configuration-driven CRM built on Single Party Architecture: one unified record handles every party type (Individual, Organization, Application) and every role (Customer, Dealer, Agent, SSOUser, ProductUser) — no duplicate silos, no data migration when relationships change.
→ Every account, billing view and request in one place.
Three things that set it apart
One record, every relationship
A single party can simultaneously be a Customer, Dealer, and Agent. Add a new role in minutes via API — no new table, no migration, no downtime. Traditional CRMs need N tables for N entity types; ProCRM needs one.
Party → Billing → Product in one screen
Three-level hierarchy with lazy-loaded navigation across 500K+ products. Configuration-driven tabs, quick actions, collapsible banner and a notes sidebar — adjustable per persona and per tenant without code.
Config-driven forms, dashboards and workflows
12+ widget types, per-persona dashboards, per-tenant layout overrides — all defined in MongoDB config collections. New dashboards and form sections deploy instantly with no rebuild or integration project.
What ProCRM does
3 party types (Individual, Organization, Application) and 5 stackable roles on one unified record — any combination, any industry.
Full party → billing account → product hierarchy with lazy loading, collapsible banner, quick actions, and a slide-in notes sidebar.
12+ widget types (Stat, Chart, Gauge, Table, FlexList, Search, Notes, DocumentUpload…) with per-persona and per-tenant layout overrides.
6 relationship categories (Family, Manager, Contact, Legal, Business, Product), bidirectional linking, scoped to party, billing account, or product level.
Structural (JSON Schema) → Role-based → Component format → Business rules (duplicate detection). Pre-flight /validate endpoints for real-time feedback.
Every change creates a versioned snapshot with who/when/why. One-click restore to any prior state. Full audit trail exportable for regulatory review.
Name, ID, phone and email matching with constraint operators (eq, in, nin, exists), field projection, multi-field sort, and paginated results.
CSV/Excel import with preview and validation, batch create/update, operation history — handles large datasets with streaming responses.
8 languages including Arabic (RTL). All labels, validation messages, and country-specific address formats (India, Nigeria, UAE) fully localised.
Multi-step interaction wizards with context auto-population, draft save/resume, and automatic backend orchestration on submission.
How buyers use it
Top dealer Adamu Ibrahim is also a subscriber and a call-centre agent. Traditional CRM: three records, three IDs. ProCRM: one record, three roles — Customer, Dealer, Agent. Add or remove each role via a single API call.
→ One 360 view shows billing accounts, dealer territory and agent performance. No system-switching, no data sync, zero duplication.
Husband (existing Customer) and wife (new Customer) need a joint savings account with Spouse and Authorized Signatory relationships. Both parties linked to one billing account; relationship scoped at billing level.
→ Either party's 360 shows the shared account and the bidirectional spouse link. Hierarchy-aware notes cascade to both. No cross-department queries needed.
Three operators (Nigeria, Kenya, UAE) on one CRM instance with different address formats, languages, dashboard layouts and 360 tab configurations — all via per-tenant config overrides.
→ One deployment, three distinct user experiences. Shared infrastructure and APIs; completely isolated data and configuration.
ProCRM vs the legacy approach
| Capability | Legacy approach | ProCRM |
|---|---|---|
| Add new role type | Weeks — new table + API + UI | Minutes — add config |
| Same person in two roles | Two records, sync required | One record, two roles |
| Role transition | Data migration, downtime | Single API call, instant |
| Cross-role reporting | Complex joins across silos | Single unified query |
| 360 view | Separate screen per entity type | One view, all roles |
| Forms & dashboards | Hardcoded, dev required | Config-driven, deploy instantly |
| Multi-tenant | Separate deployments | Per-tenant config, one deployment |
See ProCRM on your use case.
A 30-minute walkthrough on your scenario — ProCRM alone, or as part of the full platform.
Book a demo