AI AIRES

Internal live script

Monday demo script.

A tight 20-minute talk track for showing the public Rising Hills site, the private Lead Hub, agent access, CRM handoff path, and the close into first-launch scope.

Start script Presenter mode Demo assets

Open first

Presenter tabs.

Monday Demo LinkWorking DemoPresenter ModeRising HillsLead Hub OverviewBroker Dashboard Presenter ModeLead InboxRoutingSmart ListsRegistrationAgent PortalScope LockArtifact VaultLaunch Tasks CSVFollow-Up EmailPost-Call RecapProposal ReviewProposal PacketProposal PDF ViewCRM Worksheet

20-minute flow

Say this, click that, close here.

0-3 min

Monday Demo Link

Frame the outcome

Open screen
AIRES is not just a replacement website. It is a public real estate experience connected to a private lead operating layer, so a broker can see where leads come from, who owns them, and what follow-up is happening. The client pre-call path is one link: the Client Email Landing Page. It starts with the Monday Demo Link as the primary action, then supports the review with Rising Hills, the Lead Hub overview, pricing, and the optional screenshots PDF.
Show
  • Open the Monday Demo Link.
  • Point to Monday Demo Link as the first action inside that page.
  • Clarify that the client does not need private Hub access before the walkthrough.
Transition

Today I want to show what a first community launch could look like, then decide what your first launch should be.

3-8 min

Rising Hills

Show Rising Hills as the first launch

Open screen
Rising Hills is the concrete example: a brokerage gets a premium community site, curated property cards, buyer paths, registration capture, and a way to tell a specific local story without dragging in a heavy IDX search engine on day one.
Show
  • Hero and community positioning.
  • Sitemap or neighborhood structure.
  • Featured listings and curated portal handoff.
  • Calls to action and registration path.
Transition

The public site creates the demand and intent. The Hub is where that intent becomes accountable follow-up.

8-14 min

Presenter Mode, Dashboard, Inbox

Reveal the Broker Hub

Open screen
This is the operating layer. I start from Presenter Mode because it gives the broker the clean four-part proof first: client path, operating proof, launch proof, and close path. From there, leads are no longer loose emails. They are routed, assigned, tracked, organized into Smart Lists, and visible before follow-up gaps become invisible losses.
Show
  • Presenter Mode top band for Working Demo, Lead Inbox, Launch Wizard, and Meeting Tracker.
  • Presenter Start Here cockpit for the public demo, operating layer, and close path.
  • Client Demo Command Center and Post-Demo Follow-Up Pipeline.
  • Broker Dashboard metrics for lead health and stale work.
  • Lead Inbox and Lead Detail with assignment, priority, AI summary, journey/source context, and response actions.
  • Routing and Smart Lists for project, listing, agent, team, manager-focus, and transfer-notification proof.
  • Registration and Agent Portal for event capture, first-contact ownership, and agent-simple queues.
Transition

This is the difference between a site that collects inquiries and a system that manages opportunities.

14-18 min

Scope Lock, Registration, CRM/export

Show production setup and CRM path

Open screen
This is how we move from demo interest into a real first launch. Scope Lock turns the decision into accountable setup work: owners, due dates, launch-intake tasks, export proof, and go-live handoff. The CRM handoff can start with clean CSV/export proof before deeper API work.
Show
  • Scope Lock and Launch Intake with setup owners and open tasks.
  • Launch Intake task CSV/text exports as proof the setup board can be handed to a team.
  • Artifact Vault for approval packets, CRM/import proof, access/security exports, and support-ready launch artifacts.
  • Registration/Event Dashboard for open house or model-home capture.
  • Agent Portal filtered to the signed-in agent.
  • CRM worksheet as the scoped path for imports, webhooks, or API sync.
Transition

Day one can be clean exports and proof. API or CRM sync becomes a scoped next phase once fields, ownership, duplicates, and credentials are approved.

18-20 min

Post-Call Recap and Proposal Packet

Close into the first launch

Open screen
The next step is not to boil the ocean. Pick the first community, first roster, current listing links, routing rules, registration workflow, CRM/export needs, access model, support tier, and success metric.
Show
  • Post-Call Recap for the immediate follow-up.
  • Proposal Review as the single client-facing approval path.
  • Proposal Builder for package, support, timing, access, and CRM/export decisions.
  • Proposal PDF View for the client approval summary and print/save handoff.
  • Artifact Vault as the internal proof archive after client approval.
  • Launch intake if the client is ready to submit real first-launch details.
Transition

If this feels useful, the next decision is the first launch scope and who owns approval.

Click order

Keep the screen-share path predictable.

  1. Monday Demo Link
  2. Working Demo
  3. Rising Hills Client Preview
  4. Lead Hub Overview
  5. Broker Dashboard Presenter Mode
  6. Lead Inbox and Lead Detail
  7. Routing and Smart Lists
  8. Registration and Agent Portal
  9. Launch Wizard and Scope Lock
  10. Meeting Tracker and Decision Room
  11. Artifact Vault and proof archive
  12. Post-Call Recap and Proposal Builder
  13. Proposal Review
  14. Send proposal packet

Objections

Short answers that keep the call moving.

Is this replacing our CRM?

No. The first win is cleaner capture, routing, visibility, and export proof. CRM sync can come after we confirm fields, ownership, duplicate handling, and credential access.

Why not full IDX first?

Full IDX can be scoped later. The first launch focuses on curated community pages and portal handoffs so the site is fast, premium, and easier to maintain.

Can agents manage their own pages?

Yes. The direction is agent profile pages plus a simplified agent dashboard for their leads, featured listing links, and profile details.

Can this work for multiple offices or communities?

Yes. The architecture is moving toward a central AIRES operating layer with client-specific branding, modules, domains, support tier, feature flags, and role-based access.

Can clients log in directly?

Yes, but the first walkthrough should be guided. After approval, named broker/admin/agent accounts can be created intentionally with the right scope.

Close

Ask for the first launch scope.

Questions to ask live

  • What is the first community, project, listing campaign, or agent group you would launch?
  • Who should own buyer leads, seller leads, registration leads, and listing inquiries?
  • What CRM, spreadsheet, or reporting process has to be supported on day one?
  • Who is the decision owner for launch scope, support tier, and approval timing?
  • What result would prove the first launch worked?

After-call actions

Send quick follow-up Use when you need the clean recap email fast: what they saw, recommended first launch, inputs needed, and proposal-review ask. Send recap Summarize what resonated, the first launch idea, decision owner, success metric, and next ask. Build proposal Turn the selected package, support tier, access model, CRM/export path, and timing into a proposal packet. Send proposal review Use this as the one client-facing approval link before forwarding supporting proposal materials. Send proposal packet Use the print-ready proposal view when the approval summary, launch scope, and support tier are ready to send. Archive proof Use the protected Artifact Vault after the call to collect approvals, CRM/import packets, access proof, handoff packets, and support exports in one client archive. Collect CRM details Use when they are ready to discuss export fields, existing CRM, duplicate behavior, ownership, and sync path. Capture launch intake Use for first community, roster, listing links, routing, registration, and support needs.