Start with What You Get
Review the public site, private Lead Hub, routing, agent portals, broker dashboard, CRM/export path, launch support, and roadmap in plain English.
Open recapMonday handoff
One clean path after the walkthrough.
Use this page after the live AIRES demo. It keeps the follow-up simple: recap what the brokerage gets, choose one first launch, lock the scope, clarify CRM only if needed, then move into proposal review.
Recommended order
Send this one path after the call.
Open the Decision Room
Choose the first launch track, name the decision owner, and decide whether the first scope should be Community Launch, Brokerage Growth, or Multi-Community OS.
Open decision roomUse Scope Lock
Confirm launch track, owner, support tier, CRM boundary, access model, and success metric before proposal approval.
Open scope lockUse the CRM worksheet only if data handoff affects the proposal
Keep day one practical: dashboard proof and CSV/export first unless the worksheet proves API or webhook discovery belongs in the first scope.
Open CRM worksheetReview the proposal path
Use the proposal review once the first launch boundary, support tier, access model, CRM/export posture, and success metric are specific.
Open proposal reviewComplete the First Launch Plan
Gather the roster, listing links, routing rules, launch content, support package, target timing, and launch-owner inputs.
Open launch planRules for a clean handoff
Keep the follow-up specific.
Send one link
Use this Monday Handoff page after the walkthrough instead of sending a pile of separate links.
Keep Hub access guided
Private Hub screens should still be screen-shared or provided later with role-specific credentials.
Scope one launch
The first approval should stay focused on one community, campaign, agent group, registration workflow, or listing path.
CRM stays practical
Start with dashboard proof and CSV/export unless the CRM worksheet justifies deeper sync in the first scope.
Outcome
What this should make clear.
- The brokerage understands that AIRES is a website plus an operating layer.
- The first launch track is named before proposal approval.
- The approval owner, support tier, and success metric are visible.
- The CRM conversation stays bounded to day-one handoff needs.
- The next step is a scoped launch plan, not an open-ended rebuild.
Supporting links
Use only if the client wants more context.
Next move
Choose one first launch and lock the approval path.
The clean handoff is not more browsing. It is one specific launch decision, one owner, one support tier, one CRM posture, and one proof metric.