EMPORIUM · CRM BUILD SPEC v1.1
Five views of the same system. Start with the rule, then the shape of the data, then what actually happens when someone enquires.
Get this wrong and the system either becomes a nuisance or stops being trusted. Everything else follows from it.
Every relationship here is one the platform explicitly supports. The obvious design — making the operator a custom object — fails on task automation, which is why it looks like this.
The operator side, end to end. Every step is labelled YOUR JOB or AUTOMATIC — the dot colour just repeats it. Chips show which workflow fires and which document is in play.
From the expo, a referral, SEEK Business, the website or an inbound call. Everything gets a response — there is no filter at this step.
W1 sends a plain acknowledgement and creates a call task due in 60 minutes. This is the highest-value line in the whole build — speed to first human reply is the metric everything downstream depends on.
Tag the contact qnr-sent. That single tag starts the chase clock and sets the sent date.
Three chases, then it stops. At day 21 the contact is tagged archived-no-response and the opportunity closes as Lost. W6 exits the moment qnr-returned appears — a reply alone does not stop it, because "I'll get to it this week" is not a returned form.
You upload it. Every ticked line is copied verbatim into the workbook: five hard gates, nine dimensions, 100 points. A blank gate returns INCOMPLETE rather than a verdict. The result writes back to the contact.
PROCEED and PROCEED WITH CONDITIONS land on the qualified bench. HOLD waits for finance or timing to move. DECLINE gets told, in writing, with the reason.
The opportunity is associated to a Centre record. Many-to-many — the same centre can go to three candidates at once, and each one keeps its own stage.
Information Statement inside 7 days of interest · disclosure pack at least 14 days before signing · independent advice with written confirmation · 14 days cooling off. Roughly a month that no amount of speed can compress — so it belongs in the programme from day one.
The operator takes the store. Emporium's solo exposure on that tenancy ends — which is the whole point, and the moment the completion fee is triggered.
In this order. Several steps depend on the one before, and the two shaded rows cannot be undone once saved.
| Step | What you build | Time |
|---|---|---|
| 3.1 | Create the sub-account. No snapshot — snapshots bring pipelines and workflows you will spend longer unpicking than building. | 30 min |
| 3.2 | Create the Centre custom object. Its internal name and primary display field are locked permanently at save. Read them back before you click. | 1 hr |
| 3.3 | Contact fields, in three folders — Operator Qualification, Questionnaire, Qualifier Result. | 1 hr |
| 3.4 | Pipeline A — Landlord, Site Mandate. Six stages. | 30 min |
| 3.5 | Pipeline B — Operator, Site Search. Eight stages. Capital screening comes before owner fit, deliberately. | 30 min |
| 3.6 | Associations. Two, not one — Site Mandate and Candidate Operator. Sharing a label loses the ability to tell a lease from a candidate at a glance. | 1 hr |
| 3.7 | Six workflows, small and separate. W2 gets built and tested immediately after W1. | 4–5 hrs |
| 3.8 | Inbox. One existing sending domain. No warmup, no rotation, no tracking pixels. | 45 min |
| 3.9 | Custom values — thresholds and chase days in one place. | 15 min |
| 3.10 | Ten saved views. These are what actually gets opened each morning. | 30 min |
| 4 | The 13-step test script. Tests 6 and 11 are the ones people skip and the ones that matter. | 2 hrs |
Nothing here is redundant — but two things are deliberately temporary.
Emporium CRM Build Spec v1.1 · 17 August 2026 · six workflows, three record types, two pipelines. Verified against HighLevel documentation, August 2026.