Relationship management
Contacts, organisations, notes, meetings, documents, file links, activity history and connected context for every relationship.
Use the demo to inspect the CRM workspace, review setup questions and decide whether a scoped evaluation makes sense before real operational data is used.
Available in the guided demo: CRM workspace, imports, backups, permissions, activity history and populated fictional records. External provider automation is confirmed separately during setup.
Contacts, organisations, notes, meetings, documents, file links, activity history and connected context for every relationship.
Projects, opportunities, tasks, follow-ups, owners, stages and priority views for the work that sits behind income and delivery.
Money records, metrics, imports, exports, backups, archive and restore workflows so important operational data stays usable and recoverable.
Users, admins, role-based permissions, activity logs and audit-style history for teams that need clarity around access and change.
Provider pathways are handled during setup. Local calendar export is available in supported builds; external calendar, email and provider automation are confirmed only when live setup evidence exists.
A Windows-first workspace designed around data custody, exportability and practical daily use rather than unnecessary subscription sprawl.
We start by understanding how your team manages relationships, delivery work, records, tasks and follow-up.
Guided users receive practical setup guidance from the people building the product.
Guided access is structured around Blackvault CRM: relationships, documents, tasks, money, imports, backups, admin and provider pathways introduced when they are useful and properly scoped.
Users keep access to export routes and direct support throughout the evaluation.
Blackvault responds directly, confirms the context, runs a guided demo with fictional data and agrees whether a scoped setup conversation makes sense.
No. Initial demos can use fictional data. Real operating data should only be used after scope, setup and data-handling expectations are agreed.
It suits founders, small teams, service-led teams and community-sector organisations that need more structured records, follow-up, permissions, imports, backups and support.
The first step is a conversation about fit, data sensitivity and what your team needs to see before any scoped setup work begins.