CJM re-demo.
One enquiry, end to end.

Same portal, same build, different narrative. Ashleigh is not asking for a different demo. She wants the Directors to visualise CJM operating in HubSpot.

Feedback	What it means on the day
Audience is now the Directors	They decide. Talk outcomes and visibility, not configuration. Ashleigh is the champion in the room.
One end-to-end story, not feature by feature	Follow a single enquiry from form submission to the executive dashboard. Every screen advances the same story.
Lean into the enquiry workflow	Conditional form, routing by practice area, client acknowledgement, internal notification in Outlook, task creation. This is the centrepiece and it runs live.
CJM language throughout	Enquiry, matter, practice area, Relationship Manager, Directors. Never lead, deal, pipeline category or sales rep.
More Marketing Hub	Attribution, segmentation, email automation, executive reporting each get explicit airtime.
LEAP positioned, not explored	One line: HubSpot runs the client lifecycle, automation and reporting; LEAP remains the practice management system. Go deeper only if asked.

"It's 9.15 on a Tuesday morning. Someone in Brisbane has just found CJM online. She's selling her house and needs a conveyancer. Let's watch what happens."

The whole demo follows this one enquiry. The live form submission at the start creates the record that every later scene returns to, and the seeded matters (deals B through E) play the same enquiry at later stages of its life. The Directors never see a feature in isolation; they see Tuesday morning at CJM.

1. The enquiry arrives: live form submission with conditional fields, watched end to end
2. The first sixty seconds: acknowledgement to the client, Outlook notification internally, task on the Relationship Manager's list
3. The Relationship Manager's morning: one screen showing every open enquiry by practice area
4. Enquiry becomes matter: consultation, engagement, closed won, handover to LEAP
5. The firm stays in touch: review requests, referral thank-yous, segmented lists (Marketing Hub)
6. What the Directors see: attribution and revenue by practice area on the firm dashboard

Scene 1: The enquiry arrives (8 min)

Show: the CJM enquiry form on the landing page. Pick Property and Conveyancing from the enquiry type dropdown and let the room watch "buying or selling" and "settlement date" appear. Say the line: "the form asks conveyancing questions of conveyancing clients and family law questions of family law clients." Submit live with a fresh name.

Scene 2: The first sixty seconds (7 min)

Show, in order:

1. The acknowledgement email in the client's inbox: "CJM has received your enquiry."
2. The internal notification arriving in Outlook, addressed to the practice area's Relationship Manager.
3. The new enquiry sitting in the New Enquiries pipeline, owner already assigned by practice area.
4. The same-day call task created on the Relationship Manager's task list.

Scene 3: The Relationship Manager's morning (6 min)

Show: the Sales Workspace, framed as "the Relationship Manager's morning screen": the call task W1 just created sitting in today's tasks, today's consultations, and their open enquiries, all on one screen. From the task, open the enquiry created in Scene 1: the CJM record view has the key information on the left (practice area, enquiry channel, settlement date) and only the relevant related records on the right. Glance at matter B for one mid-flight: logged call, booked consultation, open follow-up task. Close the scene with Ashleigh's view: the "CJM · Ashleigh's day-to-day" dashboard showing the same picture firm-wide (open enquiries by practice area, matters in progress by fee earner, matter status).

Scene 4: Enquiry becomes matter (6 min)

Show: matter C, the full arc: form submission, consultation, engagement letter, closed won. Then the timeline notes: "LEAP sync: matter M-2026-0341 created", status updates, billed to date.

Stop there. If a Director asks how the sync works, answer briefly and offer a follow-up session. Do not open settings or talk integration mechanics.

Scene 5: The firm stays in touch (8 min, Marketing Hub)

Show:

• Email automation: matter D's timeline, where the review request email went out automatically when the matter completed, and the cross-sell task that followed. Then matter E, where the referring accountant got an automatic thank-you with the outcome.
• Segmentation: the active client lists by practice area. "Every past conveyancing client who doesn't yet have a will with us" is a list HubSpot maintains by itself, ready for a campaign.

Scene 6: What the Directors see (7 min)

Show: the "CJM · Firm performance" dashboard and tell the attribution story in the seeded numbers:

• Revenue by channel: referrals are the engine at roughly $167k.
• Conversion by channel: referrals convert at 65%, Google Ads at 29%.
• Revenue by referral partner: Sable & Roe has sent about $94k of work; Rivergum converts at 29% and has sent $5k. "Same category of partner, very different value. Now you know where the Christmas hampers go."
• Revenue and conversion by practice area, matters won by month.

Buffer: ~3 minutes for questions mid-flow. If time is tight, compress Scene 4; never cut Scenes 1, 2 or 6.

The narrative in Scenes 1 and 2 promises four live behaviours. Two of them are not built yet. This work is the difference between telling the story and showing it.

Item	State	Work needed
Conditional form fields	Pending	Add the reveals in the form editor: Conveyancing → buying or selling + settlement date; Family Law → matter urgency; Commercial → company name.
Routing by practice area	Pending	W1 currently assigns everything to Adrian. Add practice-area branches with a different owner per branch (needs 2 or 3 extra demo users in the portal so the routing is visible).
Client acknowledgement email	Not built	Create the automated "we've received your enquiry" email and add a send step to W1. Submit with an inbox that can be shown on screen.
Internal notification in Outlook	Not built	Add an internal email notification step to W1 addressed to a mailbox open in Outlook on the demo machine. The in-app notification alone doesn't land the "Outlook" point Ashleigh asked for.
Landing page styled + published	Pending	Finish styling and publish so the live submission starts from a real page, not the form editor.
Fresh test submission	Pending	Full rehearsal submission the night before: prove the form, the emails, the routing and the task all fire. W1 has never been test-submitted.
W4 / W5 workflows	Optional	The review request and referrer thank-you emails are already visible in the timelines of matters D and E, which is enough for Scene 5. Build the live workflows only if time allows.

Everything below is built and tempting. None of it maps to what Ashleigh asked the Directors to see, so it stays out.

• W2 advanced allocation (postcode and availability waterfall). One sentence at most: "routing can get as sophisticated as CJM needs." Showing branch logic to Directors kills the room.
• LEAP mechanics. No sync architecture, no field mappings, no "how would the integration be built". Ashleigh explicitly asked for this to stay high level.
• Admin and settings screens. Property setup, record view customisation, team configuration. The Directors should only ever see finished surfaces.
• Feature-by-feature Sales Hub. Quotes, meetings links, sequences. Nothing outside the story.
• The build itself. No mention of scripts, APIs or seeded data. The portal is simply "CJM, six months in".

Say	Not
Enquiry	Lead, submission, contact
Matter	Deal, opportunity
Practice area	Category, product line, team
Relationship Manager	Sales rep, owner, user
The Directors	Management, execs, leadership
Client	Customer
Engagement (letter)	Contract, quote

Some HubSpot screens will still say "Deals". Pre-empt it once, early: "wherever HubSpot says deal, read matter; the labels are configurable and would say matter in CJM's build."

1. Complete the four build gaps in Section 04 (conditional fields, routing branches, acknowledgement email, Outlook notification).
2. Rehearsal submission the night before: confirm deal creation, routing, both emails, and the task. Archive the rehearsal records after.
3. Open in tabs before the call: published enquiry form, client inbox, Outlook, Sales Workspace, New Enquiries pipeline, both dashboards, matters B, C, D and E.
4. Confirm every dashboard tile renders with data.
5. Check matters C and D timeline notes read in date order.
6. Screenshot fallback of a routed enquiry in case the live submission fails.
7. Silence notifications from the other demos in the shared Fibonacci portal.