Monday client send

Send one clean link, then guide the Hub live.

Use this page as the final send station before a client walkthrough. The client gets one public link. The protected Hub stays screen-share-first until role-specific access is intentional.

Open send email Open client email page Open client-safe demo link Open client-safe send kit Open client-safe invite Open Broker Dashboard Presenter Mode Open Artifact Vault Open presenter start Open presenter checklist Open Decision Room Open optional PDF

Final client send checklist

One prep link before. One approval path after.

Use this when you are about to send the email. It keeps the Monday package tight and protects the guided Hub walkthrough.

Send first

Client Email Landing Page

This is the required client URL before the call. It contains the Monday Demo Link as the primary action.

Keep optional

Public screenshots PDF

Useful backup if they want to skim visuals, but do not make it a required review step.

Show live

Private Lead Hub

Open Broker Dashboard Presenter Mode before the call and screen-share protected Hub screens live.

Follow up

Proposal Review

Send only after the walkthrough, once the first launch idea and decision owner are clear.

Final Monday Send Lock

Send one thing. Keep one boundary. Open one cockpit.

This is the locked Monday operating rule. It is designed for the moment before you send anything: client-safe link first, private Hub live, proposal path after the walkthrough.

Client gets

One public prep link

Send `https://askaires.com/sales-deck/monday-client-email/` as the only required pre-call link. It points to the Monday Demo Link and keeps the first touch calm.

Client does not get

Private Hub access yet

Do not send admin links, agent links, shared credentials, or protected packet URLs before the guided walkthrough.

You open

Presenter cockpit and Hub

Open Presenter Start, Broker Dashboard Presenter Mode, Lead Inbox, Scope Lock, Meeting Tracker, and Artifact Vault before the call starts.

You close with

One recorded next step

Record the Meeting Tracker outcome, then send Proposal Review only after the first launch idea, decision owner, support tier, and CRM/export path are clear.

Monday Demo Freeze Status

Ready to send. Keep the path stable.

Use this lock before Monday: send one link, keep optional collateral optional, and avoid changing the demo flow unless new feature work intentionally reopens QA.

Ready to send

Client email page

Use the copy-ready email on this page and keep the Client Email Landing Page as the only required pre-call link.

Optional only

Public screenshots PDF and Client Demo Guide

Use these as backup or supporting detail, not as extra required homework before Monday.

Do not change

Private Hub access boundary

Do not send private Hub credentials or protected admin links in the first client email. Screen-share the Hub live from the Broker Dashboard Presenter Mode view, then use the Command Center for deeper proof.

Client Email Send Status

Not sent yet.

Copy the email below, send it to the client, then record Client email sent in Meeting Tracker as the durable Hub record. The local button is only a quick browser cue.

Record durable outcome in Hub

Monday quick send path

Send this. Show this. Follow up here.

This is the reduced version of the Monday package: one client link before the call, one protected Hub screen-share path during the call, and one approval link after the call.

Send before call

Client Email Landing Page

The only required client link before Monday. It gives the client a polished prep page with the Monday Demo Link as the primary action.

Open

Show live

Broker Dashboard Presenter Mode

Presenter-only. Open this before the call and screen-share the protected Hub after the public story lands.

Open

Send after call

Proposal Review

The clean approval path after the walkthrough. Use it once the first launch idea and decision owner are clear.

Open

Archive proof

Launch Artifact Vault

Presenter-only. After the demo, use the vault to show where approval packets, CRM/import proof, access exports, and handoff artifacts are stored.

Open

Monday Demo Flight Plan

The exact client walkthrough path.

Use this as the operator script when the clock is moving: send one public prep link, open the presenter cockpit, screen-share the Hub in order, then close with one recorded next step.

Send the client prep link

Send only the Client Email Landing Page before the call.

Proof: The first action inside that page is the Monday Demo Link.

Open the presenter cockpit

Start from Monday Presenter Start, then open Broker Dashboard Presenter Mode before screen-share.

Proof: Private Hub access stays guided and no credentials go into the client email.

Screen-share the Hub path

Show Dashboard, Lead Inbox, Routing, Smart Lists, Scope Lock, and Artifact Vault in that order.

Proof: The client sees capture, assignment, accountability, launch setup, and final archive proof.

Close with one next step

Record the outcome in Meeting Tracker, then send Proposal Review after the walkthrough.

Proof: Decision owner, first-launch scope, support tier, CRM/export path, and follow-up timing stay captured.

Send package

What goes to the client.

Monday Send Control

Use this as the operator command page for what to send before Monday, what to send after Monday, and what to keep guided live.

Open send control

Monday Client Send Email

Paste-ready Gmail copy with the Client Email Landing Page first, Lead Hub walkthrough path, optional direct demo link, optional current screenshots PDF, and no private Hub access.

Open send email

Client-safe email landing page

Use this as the polished URL that mirrors the pre-call email and gives the client one obvious Monday Demo Link.

Open email landing page

Client-safe demo link

Use this when you want a clean client-only review page before the Working Demo path.

Open demo link

Lead Hub walkthrough path

Use this when you want the public explanation of the send, click, share, close path before the protected Hub screen-share.

Open walkthrough

Client-safe invite page

Use this when you want the clean pre-call email and instructions without internal controls or protected Hub shortcuts.

Open client invite

Final send packet

Use this as the final client-safe Monday packet: pre-call invite first, then What You Get and the current screenshots PDF after the walkthrough.

Open final packet

Development Status Brief

Use this internally when you need the current readiness summary, remaining hardening work, and time-to-completion estimate before talking about launch timing.

Open status brief

Primary action inside Demo Link

This remains the first action inside the client-safe Monday Demo Link.

Open Working Demo

Optional visual backup

Use this if they want a visual leave-behind or if a live page stalls. It mirrors the current public demo path.

Open public PDF

Supporting detail

Send only if they ask for a deeper self-guided explanation before or after the walkthrough.

Open Client Demo Guide

Post-call decision room

Send after the walkthrough when the client needs one clean page for recap links, decision questions, CRM worksheet, and first-launch inputs.

Open Decision Room

Proposal review link

Use as the single client-facing approval path once the proposal packet, launch boundary, and support tier are ready to review.

Open Proposal Review

Proposal packet

Use after the Decision Room and CRM/export needs are clear so the package, support tier, access model, and approval timing become a client-ready packet.

Open Proposal Builder

Print-ready approval view

Use when the client needs the proposal as a print/save PDF view with the approval summary and launch-intake handoff.

Open Proposal PDF View

What You Get leave-behind

Use after the walkthrough when the client needs a plain-English summary of the public site, Lead Hub, agent workflow, launch support, and roadmap.

Open recap

Client outcome expectation

What the link should make obvious.

The client should arrive at the walkthrough understanding the public story, the private operating layer, and the first practical launch question.

What they will see

Rising Hills as a working example of a brokerage/community launch, plus the public Lead Hub overview and client walkthrough path.

What they will understand

AIRES is not only a website. It connects public demand, lead context, routing, agent follow-up, accountability, and CRM/export readiness.

What they should bring

One real launch idea: a community, agent group, listing campaign, registration workflow, or routing problem worth testing first.

Copy-ready email

Use this message.

It keeps the ask simple, sets expectations for the private Hub, and gives the client three useful questions to bring.

Hi [Name],

I wanted to send over the AIRES working demo before our walkthrough.

Start here:
https://askaires.com/sales-deck/monday-client-email/

That is the only link you need before the call. It opens a short prep page with the Monday Demo Link as the primary action:

1. Open the Monday Demo Link
2. View the Rising Hills public website
3. Review the Lead Hub overview and its client walkthrough path
4. Bring one real launch idea to discuss

Direct demo link, if you want to skip straight to it:
https://askaires.com/sales-deck/monday-demo-link/

After 10 minutes, you should have a clear picture of what a brokerage gets:

- A polished community or campaign website
- Lead capture that preserves visitor context
- A private Hub for routing, agent follow-up, accountability, and CRM/export readiness
- A launch path that can start with one community, agent group, listing campaign, or registration workflow

Suggested 10-minute prep:

- 3 minutes: view Rising Hills
- 4 minutes: review the Lead Hub overview
- 3 minutes: think about the first community, listing campaign, agent group, registration workflow, or routing problem you would want to test first

You do not need to log into the private Hub before the walkthrough. I will screen-share that part live from the Broker Dashboard Presenter Mode view so the dashboard, lead inbox, lead detail, routing, Smart Lists, agent portal, registration workflow, broker accountability view, launch checklist, CRM/export path, Security Review, Launch Wizard, and Meeting Tracker make sense in context.

The walkthrough is simple:

- Send: this is the one public prep link
- Click: review Rising Hills and the Lead Hub overview
- Share: I will screen-share the private Hub live
- Close: we choose one first-launch path to evaluate

Optional visual backup:
https://askaires.com/sales-deck/useaires-front-end-current.pdf

Helpful questions to bring:

- Which community, project, agent group, or listing campaign would you launch first?
- Who should own new buyer, seller, registration, and listing leads?
- Which CRM, spreadsheet, or reporting process would AIRES need to support?

Best,
Jackson

Open email draft

Presenter prep

What stays internal.

Checklist

Send the Client Email Landing Page as the only required pre-call link.
Keep the Monday Demo Link as the primary action inside the Client Email page.
Do not send private Hub credentials before the guided walkthrough.
Keep the public screenshots PDF open as fallback collateral.
Open /lead-hub/#walkthrough if the client needs the public send/click/share/close framing before the live Hub screen-share.
Sign into the Hub in a separate tab before the call starts.
Start protected screen-share from the Broker Dashboard Presenter Mode band, then use the Command Center and Launch Wizard.
Open the Meeting Tracker before the call ends so next steps are captured.
Open the Launch Artifact Vault after the close path to show where proof packets and launch exports are archived.
Close into the proposal packet only after the first launch idea is clear.

Open before the call

Monday Send Control Client Send Email Development Status Brief Presenter Start Presenter Checklist Working Demo Lead Hub Walkthrough Public screenshots PDF Live demo script Broker Dashboard Presenter Mode Broker Launch Wizard Lead Inbox Meeting Tracker Launch Artifact Vault Post-call recap Proposal Review Proposal Builder Proposal PDF View

Lead Hub walkthrough map

Show the private operating system in this order.

Use this when the client asks, "What do we actually get?" It starts with the broker view, then proves capture, routing, agent workflow, production setup, and follow-up accountability.

1. Broker Dashboard Presenter Mode

Start here after the public review. Show the operating pulse, launch proof, client command center, and follow-up accountability before drilling into detail.

Open Dashboard

2. Lead Inbox and Lead Detail

Show how a website inquiry becomes an assigned lead with status, priority, visitor context, source path, AI insight, and response actions.

Open Lead Inbox

3. Routing and Smart Lists

Explain project, listing, and agent routing, then show saved queues, team ownership, transfer notifications, and manager-focus lists.

Open Routing

4. Registration and Agent Portal

Connect an open-house or model-home workflow to agent queues, duty ownership, first-contact follow-up, and client-safe QR capture.

Open Registration

5. Launch Wizard and Scope Lock

Move from demo interest into production setup: checklist, owners, launch-intake tasks, CSV/text exports, and go-live handoff proof.

Open Scope Lock

6. Meeting Tracker and Decision Room

End by recording the decision owner, next follow-up, proposal track, client email sent status, and the post-call Decision Room path.

Open Meeting Tracker

7. Artifact Vault and proof archive

Close the internal operator path by showing the protected archive for go-live approvals, handoff packets, CRM/import proof, access exports, and support-ready launch artifacts.

Open Artifact Vault

After the call

Turn the demo into a next step.

Capture follow-up

Log decision owner, next touch date, proposal track, estimated value, and the next ask.

Open

Write recap

Turn the conversation into a copy-ready follow-up with the launch idea and requested inputs.

Open

Build proposal

Move from interest into package, support tier, CRM/export path, access model, and approval timing.

Open

Send proposal review

Use one client-facing approval link before sending the supporting Proposal PDF View or approval packet download.

Open

Send proposal packet

Use the print-ready proposal view as the final client approval artifact after the proposal builder is aligned.

Open

Send decision room

Give the client one post-demo link for recap materials, decision questions, and first-launch input collection.

Open

Send What You Get recap

Use the client-safe leave-behind when they need the full value summary in one printable page.

Open

Archive launch proof

Use the Artifact Vault internally after the call to collect approvals, handoff packets, CRM/import packets, access proof, and support exports in one client archive.

Open

Use final send packet

Open the final send packet when you want the exact pre-call and post-demo emails side by side.

Open