Client Email Landing Page as the required pre-call link, with the Monday Demo Link as the primary action inside it.
Internal run sheet
Monday demo: 20-minute walkthrough.
Use this page during the call. It keeps the demo tight: client-ready package first, public site second, private Hub third, scoped next step last.
Call structure
Keep the boundary clear from the first minute.
Rising Hills, Lead Hub overview, brief, pricing, and screenshots are optional supporting links.
Protected Hub screens are screen-shared live unless direct role-based access is intentionally granted.
Move into launch intake, decision path, CRM worksheet, and Proposal Builder.
What they review on their own
Client Email Landing Page as the required pre-call link. Its primary action opens the Monday Demo Link, which routes them through Rising Hills, the Lead Hub overview, and the real-launch prompt.
What you screen-share
Broker Dashboard Presenter Mode first, then Command Center, Broker Launch Wizard, Go-Live Handoff, Launch Artifact Vault, Security Review, lead inbox with CRM handoff readiness, Smart Lists, registration event, routing, agent queue, reports, and client/settings surfaces.
What you ask for next
First community/project, agent roster, listing links, routing rules, registration flow, CRM/export needs, and support package.
60-second opener
Use this if you need to land the idea quickly.
- AIRES is a fast public real estate website connected to a private operating layer.
- Rising Hills is the example launch: one community, curated listings, registration paths, and clear calls to action.
- The Hub is what makes it operational: every inquiry becomes an owned, routed, trackable opportunity.
- Smart Lists turn the inbox into reusable follow-up queues for broker oversight, teams, agent-visible work, and private agent focus.
- The Lead Inbox also proves the handoff path: filtered rows, selected export preset, mapped columns, CSV preview, and links to export history and integrations.
- The pre-call path is one client link: the Client Email Landing Page. It starts with the Monday Demo Link as the primary action; today I will recap that public path, then screen-share the protected Hub, then close on what a first launch would require.
- The Launch Artifact Vault is the final proof archive for approvals, CRM/import proof, access exports, handoff packets, and support-ready launch artifacts.
Pre-call setup
Open these before the call starts.
Demo Assets Command Center /sales-deck/demo-assets/ Monday Demo Link /sales-deck/monday-demo-link/ Monday Client Send /sales-deck/monday-client-send/ Monday Demo Snapshot /sales-deck/monday-demo-snapshot/ Presenter Checklist /sales-deck/monday-presenter-checklist/ Monday Client Handoff /sales-deck/client-handoff/ Client Demo Guide /sales-deck/client-demo-guide/ Public Screenshots PDF /sales-deck/useaires-front-end-current.pdf Rising Hills /rising-hills/ Client Preview /rising-hills/#client-preview Guided Hub Walkthrough /rising-hills/#demo-mode Broker Dashboard Presenter Mode /admin/dashboard?client_id=client_rising_hills Broker Launch Wizard /admin/launch?client_id=client_rising_hills Go-Live Handoff /admin/handoff?client_id=client_rising_hills Launch Artifact Vault /admin/artifacts?client_id=client_rising_hills Security Review /admin/security?client_id=client_rising_hills Lead Inbox /admin/leads?view=new Lead Inbox Export Proof /admin/leads?view=new&client_id=client_rising_hills Smart Lists /admin/smart-lists?client_id=client_rising_hills Event Dashboard /admin/registration/reg_rising_hills_model_home Agent Queue /agent/leads?view=all Client Brief /sales-deck/rising-hills-brief/ Proposal Builder /sales-deck/proposal-builder/ Proposal PDF View /sales-deck/proposal-print/
10-minute fast path
If the call gets squeezed, use this route.
Monday Demo Link
Frame one client link, Working Demo first, public site plus private operating layer.
Rising Hills
Show hero, sitemap concept, featured listings, and buyer paths.
Presenter Mode / Handoff / Security
Start from the Presenter Mode band, then show Command Center readiness, access proof, Production Hardening, Go-Live Handoff blockers, Security Review proof, lead health, stale work, and accountability.
Lead Inbox / Agent Queue
Show routing, ownership, AI context, tasks, agent simplicity, and CRM-ready export proof.
Close
Ask for first community, roster, listing links, routing, registration, CRM/export, and support package.
Live timing
Keep the story moving.
- Say
- This is not just a prettier website. The pre-call path is one client link: the Client Email Landing Page. It points to the Monday Demo Link, which starts with the Working Demo, then supports the review with Rising Hills, Lead Hub overview, pricing, and optional screenshots before we screen-share the private Hub.
- Show
- Start from the Client Email Landing Page and point to the one-link boundary, Monday Demo Link primary action, no-login note, and launch-package framing.
- Say
- Rising Hills is the example of what a brokerage could launch for one community: story, sitemap, curated inventory, agent ownership, and simple buyer paths.
- Show
- Show the hero, site map, and featured listing cards. Emphasize curated portal links over heavy IDX for the MVP.
- Say
- At a model home, open house, or community event, the visitor scans a QR code and enters the system with event and source context.
- Show
- Open the registration form. Do not spend too long filling it out unless the client asks.
- Say
- This is where AIRES becomes operational. Leads are not loose emails; they become owned, routed, tracked opportunities with next actions.
- Show
- Start with the Broker Dashboard Presenter Mode band for the four proof paths: client path, operating proof, launch proof, and close path. Then use the Command Center and Presenter Start Here cockpit before branching to Launch Wizard, Go-Live Handoff, and Security Review if the client asks how this moves from demo into paid operations.
- Say
- The broker gets visibility into lead health, stale follow-up, agent performance, source quality, and operational risk.
- Show
- Use the lead inbox, Smart Lists, and export panel. Call out CRM handoff readiness, preset selection, mapped columns, CSV preview, and proof links before download.
- Say
- Agents do not need the whole brokerage admin. They need their leads, their tasks, their profile, and eventually their featured listings.
- Show
- Open the agent queue and explain role-based access.
- Say
- The next step is not to build everything at once. Pick one community, one roster, current listing links, routing rules, registration needs, and CRM/export needs. Then AIRES can scope the first launch.
- Show
- Open Proposal Builder or First Launch Plan only if there is time. If the client is ready for approval, open the Proposal PDF View as the clean packet to print, save, or forward, then use the Launch Artifact Vault as the protected proof archive.
Access guardrails
Keep private Hub access intentional.
Send one required link first
Client Email Landing Page is the only required pre-call link. It points to the Monday Demo Link, which starts with the Working Demo; Rising Hills, Lead Hub overview, client brief, pricing, and PDF collateral are supporting links, not the first client task list.
Screen-share private Hub first
Broker Dashboard Presenter Mode, Command Center, Launch Wizard, Production Hardening, Go-Live Handoff, Launch Artifact Vault, Security Review, admin, agent, event dashboard, Smart Lists, CSV, packet, reports, routing, CRM handoff readiness, and settings screens should be shown live unless you intentionally grant demo access.
Use rotated local credentials
Prepare from the local credentials note on this machine. Do not paste passcodes into the deck, public pages, or forwarded client emails.
Use the Rising Hills broker demo account
For the Rising Hills workspace, sign in with the dedicated broker-admin demo account before opening Broker Dashboard Presenter Mode.
Do not paste credentials into client emails
If direct access is needed, send credentials separately, rotate them afterward, and keep shared admin credentials out of forwarded sales messages.
Normalize auth prompts
A 401, 403, or Hub login redirect is expected when protected links are opened signed out. Use screenshot PDFs if auth slows the call.
Proof points
Repeat these ideas.
- Public community website creates the premium front door.
- Curated listings avoid IDX drag while preserving buyer-friendly portal handoffs.
- Hub turns inquiries and registration into owned, trackable opportunities.
- Smart Lists organize follow-up into reusable broker, team, agent-visible, and private queues.
- Lead Inbox export panel shows CRM handoff readiness before anything is downloaded.
- Broker Dashboard Presenter Mode gives the first screen-share path, then the Command Center makes follow-up gaps visible before leads go stale and gives the presenter a clean walkthrough cockpit.
- Agent views keep the workflow simple and role-specific.
- Security Review translates auth, CSRF, client isolation, agent boundaries, and formal-audit status into an operator-friendly launch screen.
- Client layer supports branding, modules, plans, support packages, and feature flags.
- CRM export/import and future API/webhook sync reduce switching friction.
Close questions
Turn demo interest into scope.
- Which first community or project would be the best pilot?
- Who owns new leads today, and where does follow-up usually break?
- Which agents or teams would need access first?
- Do you want the first launch focused on listings, registration, lead routing, or accountability reporting?
- What CRM or spreadsheet format needs to be supported on day one?
Decision close
End with decisions, not compliments.
First launch use case
Which one community, project, event, or agent team would prove the most value first?
Routing ownership
Who should own each lead type on day one: broker, listing agent, buyer agent, team, or fallback owner?
Data handoff
Should day one use CSV export with preset proof, a CRM handoff job, a webhook/API sync, or a simple shared report?
Support package
Do they need Core Operations support or the Scale & Agent Growth package from the start?
Fallbacks
If the conversation turns, use these moves.
Protected screen stalls
Use the backend screenshots PDF or Lead Hub screenshots PDF. Both now include the Broker Dashboard Presenter Mode top band, Presenter Start Here, Command Center, and Security Review screens, so you can still explain production-readiness proof while auth catches up.
Public site stalls
Use the refreshed public screenshots PDF and keep the flow moving through the same story.
Client asks about MLS/IDX
Position curated listings as Phase 1 and IDX/API feeds as a scoped Phase 2 decision.
Client asks if it replaces CRM
Say AIRES can sit in front of the CRM first, prove clean capture/routing in the Hub, then sync or export using preset-ready handoff paths.
Client wants pricing
Open Pricing, then Proposal Builder for a scoped launch/support recommendation.
Client wants proof it scales
Show Clients settings and explain the central OS/client layer model.
After the call
Do not leave the next step vague.
Send the recap, ask for launch inputs, then turn the first-launch details into a proposal while the pain is still fresh.
Handoff checklist/sales-deck/client-handoff/Archive proof/admin/artifacts?client_id=client_rising_hillsSend recap/sales-deck/post-call-recap/Send client brief/sales-deck/rising-hills-brief/Collect intake/sales-deck/first-launch-plan/Build proposal/sales-deck/proposal-builder/Send proposal packet/sales-deck/proposal-print/