Send
Client Email Landing Page only. The Monday Demo Link remains the primary action inside it.
Monday presenter start
Open this first.
One operator screen for the client link, private Hub tabs, 20-minute talk track, proof beats, close questions, and after-call actions.
Monday Demo Flight Plan
Send. Open. Show. Close.
Use this as the short operator script before the deeper tab list. It keeps the client path simple and the protected Hub walkthrough intentional.
Open
Presenter Start, Working Demo, Rising Hills, and Broker Dashboard Presenter Mode before the call begins.
Show
Dashboard, Lead Inbox, Routing, Smart Lists, Scope Lock, and Artifact Vault as one protected Hub story.
Close
Record Meeting Tracker outcome, then send Proposal Review after first launch scope and owner are clear.
Presenter demo spine
Same story, operator version.
Use this spine to keep the live call focused: public story, Hub workflow, first launch, decision path. Every tab below should serve one of these four moves.
Start with Rising Hills
Show the community website as the first-launch example before opening private Hub screens.
Public pagesMove into accountability
Screen-share dashboard, lead inbox, routing, Smart Lists, registration, reports, and launch controls as one operating layer.
Protected walkthroughMap the real use case
Ask for the first community, event, listing campaign, agent group, or routing problem that should become the pilot scope.
Scope discussionClose into proof
Record the meeting outcome, archive proof, send the recap, and use Proposal Review only after the owner and scope are clear.
Recap and approvalOpen tabs in order
Nine tabs. No wandering.
Client pre-call link
Use this as the only required client link before the walkthrough.
Open Demo LinkWorking Demo
Start the public story here after the client lands on the demo link.
Open Working DemoRising Hills case study
Show the community launch, curated listing path, and registration/lead capture story.
Open Rising HillsBroker Dashboard
Sign in before the call; screen-share this as the first protected Hub view.
Open DashboardLead Inbox
Show captured lead context, routing, assignment, AI insight, and response controls.
Open Lead InboxRouting and Smart Lists
Prove project/listing ownership, team queues, overrides, and follow-up visibility.
Open RoutingScope Lock
Move the demo into production setup: owners, launch tasks, exports, and approval handoff.
Open Scope LockArtifact Vault
Use this after the close path to show where approval packets, CRM/import proof, access exports, and handoff artifacts are archived.
Open Artifact VaultProposal Review
Use this as the single client-facing approval path after the walkthrough.
Open Proposal Review20-minute talk track
Say this, then move.
0-3 min
Frame the system
AIRES is not just a website. The public site creates intent, and the Hub makes follow-up accountable.
Show: Monday Demo Link, Working Demo3-8 min
Show the first launch
Rising Hills is the example of what a brokerage gets first: a branded community launch, curated property path, and lead capture.
Show: Rising Hills Case Study8-14 min
Reveal the operating layer
This is where the broker sees who owns the lead, what the visitor did, what follow-up is due, and where opportunities are getting stuck.
Show: Broker Dashboard, Lead Inbox, Routing14-18 min
Prove production setup
Scope Lock turns the demo into launch work: owners, access, routing, CRM/export questions, and a go-live checklist.
Show: Scope Lock, Meeting Tracker18-20 min
Close into the first launch
The right next step is one focused launch, not boiling the ocean. Pick the first community, owner, routing rules, CRM path, support tier, and success metric, then archive the launch proof in the Artifact Vault.
Show: Proposal Review, Artifact VaultProof beats
Make these obvious.
- The client only needs one pre-call link.
- Protected Hub access stays guided by screen share until roles are intentional.
- Lead context shows source, journey, routing, assignment, priority, and response actions.
- Broker accountability shows stale work, follow-up risk, command email proof, Smart Lists, and next actions.
- Launch setup is tracked through Scope Lock, launch intake tasks, exports, and go-live handoff.
- Artifact Vault shows where approvals, CRM/import packets, access proof, and handoff exports live after the walkthrough.
- Proposal Review is the clean approval path after the live walkthrough.
Close questions
End with the first launch.
- What is the first community, listing campaign, agent group, or event workflow you would launch?
- Who owns buyer, seller, registration, and listing leads?
- What CRM, spreadsheet, or reporting process has to work on day one?
- Who is the decision owner for launch scope, support tier, and approval timing?
- What measurable outcome would prove the first launch worked?
After the call