Architecture

How Valere CRM is put together, drawn for Valere Group: who uses it and what is around it, its parts, its seventeen modules, how a figure is made, where it runs, and one action followed from the click to the Monday meeting.

The system in its world

The product, the people who use it and the systems around it.

Everyone at Valere Group works in one place: each role on the left does its part of the deal in Valere CRM, in the browser, signed in with their Microsoft account. Each sees what the role needs — Construction, for one, only the Sites with Construction Involved = Yes.

Around it are the services it relies on — mail, calendar and Teams, files, signatures, the AI, reporting, and the data sources and public records — each on Valere’s own account or licence. The AI only reads and drafts: nothing takes effect until a named person approves it (N-08). Ask Valere answers in your own Claude or ChatGPT with your rights, no more.

Landowners, RPs, contractors and solicitors never sign in: they receive email from the user’s own mailbox and agreements through Adobe Sign.

Valere CRM itself
A part of Valere CRM, or a person who uses it
Outside Valere CRM, on Valere’s own account or licence
Outside Valere: they never sign in
What moves, in the direction it moves
The official mark of the technology or service

Its parts

The applications and stores the product is made of, and how they talk.

Three parts and two stores. Staff work in the web application; every question and every change goes to one API, which checks the person’s rights first, does the arithmetic in code and keeps each record with its history in the database. The same API, documented, serves Power BI’s read-only views and Ask Valere through the MCP connector.

Behind the API sits one shared AI layer for every automation — lead generation, appraisals, outreach, build cost benchmarking, mail and meetings: it reads and drafts with its source and confidence, and nothing takes effect until a named person approves (N-08).

Anything slow or scheduled — reading a document, collecting candidate sites, sending an approved email — waits in the queue and is done by the job runner, so the screen never waits and every run is on record. Documents stay in Valere’s SharePoint; the product keeps the link, not a copy.

A part of Valere CRM, or a person who uses it
The shared AI layer
Outside Valere CRM, on Valere’s own account or licence
What moves, in the direction it moves
The official mark of the technology or service

Modules

The modules of the product and what each depends on.

Seventeen modules, one per item of the Scope of Works, and all seventeen are in the first release. Down the middle is the path a Site takes, from a candidate found by Lead Generation to the figures in Views, Scores and Dashboards; each arrow says what one module hands to the next.

At the sides are the modules that feed a step — mail and meetings, the master Accounts, imports, outreach, documents, actions; the connections to Adobe Sign, Creditsafe, Searchland, Glenigan, Lusha and BCIS live in the modules they serve. Legals hands exchange and completion back to the Site record.

The four automations — Lead Generation, Financial Appraisals, Outreach, Build Cost Benchmarking — and the mail capture share one AI layer, with one rule: a named person approves before anything takes effect. Admin sets the lists, thresholds and AI settings every module runs on (02-architecture › Relationships).

A step on the Site’s path
A module that feeds that step
The shared AI layer, behind the automations
Under every module
What moves, in the direction it moves

How data moves

From the first entry to the reported figure.

A figure on the Monday meeting starts as a candidate the lead-generation run found, an email or a Teams transcript, or as a row of an Excel tracker at import. The AI may read and propose, but a named person approves each value before it reaches the record. An import runs in parallel with the trackers for a short time, reconciled every day, until the cut-over makes the trackers read-only.

From the record on, every figure is calculated by code, the same way every time; the Morning Meeting shows it live, and when the week is locked and the month closed the figures are frozen, so the monthly pack never moves after the meeting.

The Site record
A step
The step, in order
What moves, in the direction it moves
Where it is kept
The official mark of the technology or service

Where it runs

The installation: hosting, regions, what runs where.

Valere CRM runs in a cloud account Valere Group owns, in the UK or the EU (N-05); the provider is not chosen yet. The code, the database, the AI keys and the Microsoft app registration are on Valere’s accounts from day one. Two copies run side by side: staging, where Valere accepts each release on its real data with no outbound channel — no sends, signatures, paid lookups or collection runs, AI spend off or sandboxed, and every screen marked as staging (D-040) — and production, where the team works.

Each part is packaged the same way in both, so what was accepted is what goes live. Data is encrypted at rest and in transit; production is backed up every day and the restore is tested on a schedule; every release has notes and can be rolled back (N-04).

Valere’s own cloud account
A part of Valere CRM, or a person who uses it
Outside Valere CRM, on Valere’s own account or licence
Nothing leaves staging
What moves, in the direction it moves

One request

The path of one user action through the system, numbered.

Dana Whitfield (Partnerships) records an offer of £6,150,000 from Ashby Rural Housing on Lea Bridge Works, Walthamstow; the web application sends it to the API as one change.
The API checks her role — Partnerships manages Buyers and Offers — and that she may see this Site, before anything is read or written.
The offer is saved as version 1 on the buyer’s journey, the buyer moves to Offered, and the change goes into the audit log with who, what and when (BUY-C14). Nothing earlier is overwritten.
Code on the server recomputes what depends on it: the offer’s % of GDV and suggested grade, the Site’s Deal Health and its deal clocks (D-023).
A notification for Land is queued; the job runner delivers it in the platform and, by the person’s choice, by email or Teams through Microsoft 365 (ACT-C18).
On its next load the Morning Meeting view shows the Site’s row with the new offer and its Deal Health — nothing is typed into the view.

One action, followed through every part. Each number is a step on the drawing and a line in the list under it.

The person never waits for the slow parts: the offer is saved and scored at once, and the message to Land is sent from the queue a moment later.

A part of Valere CRM, or a person who uses it
A check inside the API
One part, over time
The step, in order
What moves, in the direction it moves
The official mark of the technology or service

In this section

Domain and glossary

The words of the product and the things they name: every entity, how the entities relate, the Site’s life, who owns what — drawn, and then the glossary A to Z.