Core Modules

CCJV Core - Modules

The operating modules behind this ERP: one wallet, one tenant, shared records — a deal won in CRM becomes a Project, time-off lands on the Calendar, and closed workflow runs are saved to the Vault as SHA-256 hash records. Nothing is re-keyed from one module to another.

  • CRM - Tenant-aware contact management. 1 CJV/month, held — not spent.
  • HRM - Tenant-aware employee management. 1 CJV/month, held — not spent.
  • Accounting - Tenant journal and ledger. 1 CJV/month, held — not spent.
  • PMP - Project management (PMP). 1 CJV/month, held — not spent.
  • Assets - Asset register. 1 CJV/month, held — not spent.
  • IoT - Device and sensor workspace. 1 CJV/month, held — not spent.
  • Calendar - Shared scheduling. 1 CJV/month, held — not spent.
  • Vault - Document vault: hash records queued for anchoring. 1 CJV/month, held — not spent.
  • Dashboard - Core dashboard. 1 CJV/month, held — not spent.
  • Workflows - Cross-module automation: triggers, steps, approvals. 1 CJV/month, held — not spent.

All 10 modules together: 10 CJV held. The holds add up - each module you use adds its own hold, and you hold only for the modules you choose. Every wallet holds for its own modules: a collaborator's hold never covers yours.

Access runs on a hold, not a subscription: your balance is checked, never taken. While the hold stands the module is active; if it lapses the module pauses and your records stay yours.

Connect Wallet

Binding takes a minute: sign in or register, connect the wallet that holds your CJV, and sign once to prove it is yours. See what each module does — the full brief for every module, with its workflow and its output.

See the operating picture — the Command Center’s morning panel, rendered by the product itself

Prefer to see it first?

Request a walkthrough. The request lands as a lead in our own CRM - the CRM module described above - with your note attached, and the walkthrough is arranged from it.

Your details go into our CRM as a lead and are used to arrange the walkthrough. Nothing else is done with them.

The party, run in the open — the Workers First ERP

One workspace for the party’s own work: who has joined, who is volunteering and where, the events that bring the party together, every riding association, the communications the party issues, and the decisions its bodies make.

The party’s working loop: New Member to Active Volunteer — a new member is welcomed, assigned to a riding, and confirmed as a volunteer, with the first riding meeting on the calendar.

The hold: entry is a hold of 1 WKF, and each module is a further 1 WKF hold per month — 8 WKF held opens the full party suite. Holding is the gate; nothing is spent, transferred or deducted.

Connect Wallet

Shared infrastructure — CRM, HRM, projects, assets, accounting, calendar, IoT, vault and workflows — is operated centrally by CCJV and gated in CJV, 1 CJV per module per month.