Choose the first launch
Name the first community, campaign, agent group, registration workflow, or listing path AIRES should prove before expansion.
Scope lock handoff
Turn the demo into one launchable decision.
Use this after the recap and Decision Room. It prevents the first proposal from becoming vague by locking the launch track, owner, support tier, CRM boundary, access model, and success metric before approval.
Lock before approval
The six decisions that make the proposal real.
Assign one approval owner
Confirm who can approve package, support, access, CRM/export posture, timeline, and launch boundary.
Select the operating package
Pick the monthly support path for hosting, maintenance, updates, Hub help, content changes, and post-launch improvements.
Keep day one practical
Lock dashboard proof and CSV/export first unless the CRM worksheet proves API or webhook discovery belongs in the first scope.
Name who gets in
List owner, broker admin, staff, agent, and read-only reviewer access so the Hub does not launch with shared credentials.
Define the first proof
Choose one operating outcome: captured registrations, routed leads, faster first contact, cleaner ownership, or broker accountability.
Scope boundaries
Keep the first launch tight enough to ship.
Included now
One focused public launch, Lead Hub setup, role access, routing map, basic notifications, broker dashboard, CSV/export posture, QA, and support handoff.
Decide before build
Brand assets, launch content, roster, featured listing links, routing owners, support tier, target date, CRM/export expectation, and approval owner.
Defer unless approved
Full MLS/IDX replacement, custom CRM API buildout, historical CRM migration, paid ad management, unlimited design variations, and enterprise SSO.
Proof required
The first launch is complete only after public forms, private Hub access, routing, notifications, exports, and support ownership are tested and archived.
Decision-owner questions
Answer these before final proposal approval.
- What is the first launch: community, campaign, agent group, registration event, or listing workflow?
- Who is the decision owner for package, support, timeline, and Hub access?
- Which agents or teams need day-one access and lead ownership?
- What should happen when a lead has no obvious owner?
- Which CRM, spreadsheet, inbox, or reporting handoff must AIRES support first?
- What single result would make the first launch obviously successful?
Handoff packet
Use these links in order.
What You Get Use as the recap before scope lock. Decision Room Choose the first launch track and owner. CRM Worksheet Use only when CRM/export affects the first proposal. First Launch Plan Collect roster, routing, content, support, and timing inputs. Proposal Review Approve the locked scope and move into implementation. Request Full Demo Send final notes when the owner is ready.
Approval threshold
Move to proposal only when the launch boundary is specific.
Scope lock is not a contract by itself. It is the client-safe checkpoint that makes the proposal accurate and keeps the first launch from expanding before proof exists.