Monday presenter checklist

Run the AIRES demo from one page.

Send the Monday Demo Link, confirm the Working Demo is the first action inside it, open the Broker Dashboard Presenter Mode view, screen-share the protected Hub, capture the first launch idea, and leave with a proposal path.

Client send page

20-Minute Flow

Before call

Send one link

Send the Client Email Landing Page only. Confirm the Monday Demo Link is the primary action inside it, and keep the public PDF optional and private Hub credentials out of the client email.

Use Monday Client Send as the source of truth: Send the Client Email Landing Page, confirm the Monday Demo Link is the primary action inside it.
0-3 min

Frame AIRES

Position Rising Hills as the first launch package: public community site plus private brokerage operating layer.

Open Client Email Landing Page, then Monday Demo Link, Working Demo, and Rising Hills.
3-8 min

Show public experience

Show community story, sitemap, curated listings, registration, and request-demo path.

Ask which community, project, or listing campaign they would launch first.
8-15 min

Walk the Hub

Use the seven-step Hub path: Broker Dashboard Presenter Mode, Lead Inbox and Lead Detail, Routing and Smart Lists, Registration and Agent Portal, Launch Wizard and Scope Lock, Meeting Tracker and Decision Room, then Artifact Vault and proof archive.

Show that leads become owned, routed, tracked opportunities and that launch setup can be exported as CSV/text proof, then archived as protected approval and handoff artifacts.
15-20 min

Close the next step

Capture decision owner, first launch idea, CRM/export needs, access model, and proposal timing.

Open Meeting Tracker, then Proposal Builder.

Proof Points

  • One public website can feed a private lead operating system.
  • Curated listing links avoid the weight of a full IDX rebuild for the MVP.
  • Broker Dashboard Presenter Mode gives the first screen-share path, while the Command Center exposes accountability, stale follow-up, source quality, next actions, and the guided presenter cockpit.
  • Lead Inbox and Lead Detail prove capture, source context, routing, assignment, AI insight, and response actions.
  • Routing and Smart Lists prove project/listing ownership, team queues, transfer notifications, and manager-focus lists.
  • Agents get filtered portals instead of the full admin system.
  • Scope Lock proves production setup: owners, launch-intake tasks, CSV/text exports, and go-live handoff.
  • Artifact Vault proves launch artifacts are organized: approvals, CRM/import proof, access exports, handoff packets, and support-ready operations exports.
  • Smart Lists, routing, registration, CSV exports, and meeting follow-up turn the site into an operating workflow.

Close Questions

  1. What is the first community, project, or listing campaign you would want AIRES to launch?
  2. Who should own new buyer, seller, registration, and listing leads?
  3. Which CRM, spreadsheet, or reporting process needs to be supported first?
  4. Who should be the decision owner for scope, access, and approval timing?

After The Call

Log follow-upArchive proofWrite recapBuild proposalSend follow-up email