Build note 01
How Blackvault turned fragmented relationship, delivery and administration records into a finished local-first Windows CRM that can be configured, modified and extended around each client's requirements.
A factual account of Blackvault's own product and technology work, using evidence that is labelled and available for direct inspection.
01
Blackvault treated operational memory as the product boundary. Contacts, organisations, opportunities, projects, tasks, meetings, documents, money context and activity history belong together because each explains the others when a team needs to act.
02
The core product remains coherent while onboarding maps users, named admins, permissions, imports, backup routines and selected provider connections to the client environment. Where requirements go further, Blackvault can modify and extend the product without turning the implementation into a disconnected collection of add-ons.
03
A conversation can become an opportunity, delivery work, supporting documents, money context and accountable follow-up without shedding its history at every stage. The business keeps the memory even when people, priorities and busy weeks change.