Review the proposal
Use the print-ready Proposal PDF View to confirm package, support tier, timing, access model, CRM/export path, and launch assumptions.
Proposal review
Approve one focused AIRES launch first.
Use this page after the walkthrough and recap. It gathers the proposal, decision room, CRM worksheet, and first-launch checklist into one approval path.
Approval path
Four steps from proposal to scope lock.
Confirm the launch boundary
Keep the first approval focused on one launch. Expansion to more agents, communities, and deeper CRM sync comes after the first workflow is proven.
Send the missing inputs
Provide brand assets, roster, listing links, routing rules, CRM/export needs, and decision-owner timing.
Move into scope lock
Once approved, AIRES moves the agreed scope into launch intake, Hub setup, QA, go-live handoff, and support rhythm.
Approval readiness checkpoint
Confirm these before treating this as approved.
Proposal Review is the approval path only after the post-demo handoff has narrowed into one launch, one owner, and one clear CRM/export posture.
Recap reviewed
What You Get or the post-call recap has been sent so the client understands the full system.
Decision owner named
One person owns approval for package, support, timing, and launch boundary.
First launch selected
Community, campaign, registration workflow, agent group, or listing path is specific.
CRM boundary clear
CSV/export first unless the CRM worksheet proves API or webhook discovery belongs in scope.
Support tier chosen
Monthly hosting, maintenance, Hub support, updates, and response expectations are clear.
Success metric named
The first launch has one measurable operating outcome.
Approval-ready terms
What approval means.
This keeps the client decision clear: approve one focused launch, understand the assumptions, keep exclusions visible, and move into scope lock only after the decision owner is aligned. Use the Scope Lock Handoff before approval if the launch track, owner, support tier, CRM boundary, access model, or success metric is still fuzzy.
Approval summary
Approval means AIRES can convert the selected first launch into Scope Lock: package, support tier, client workspace, Hub users, routing, CRM/export path, launch assets, QA, and handoff plan.
Working assumptions
The first launch starts with one focused community, campaign, agent group, or registration workflow. Day-one CRM handoff is CSV/export-ready unless a separate API credential scope is approved.
Exclusions
Approval does not include full MLS/IDX replacement, custom CRM API buildout, paid ad management, unlimited design variations, or bulk historic CRM migration unless those items are added to scope.
Approval to proceed
Once the decision owner confirms package, support, timing, access model, and success metric, AIRES moves into launch intake and returns a scoped milestone packet for final go-live approval.
Approval checklist
What the decision owner should confirm.
Launch package
Approve the first community, campaign, agent group, or registration workflow that AIRES should launch first.
Support package
Choose the monthly support path for hosting, maintenance, updates, Hub support, and post-launch improvements.
Access model
Confirm the owner, broker admin, staff, agent, and reviewer accounts needed for the first launch.
Routing rules
Confirm who owns buyer, seller, registration, listing, and fallback leads on day one.
CRM/export path
Approve CSV/export readiness first, plus any scoped follow-on CRM/API discovery.
Success metric
Name the one outcome that proves the first launch worked: capture, speed, routing clarity, reporting, or accountability.
Review materials
One page, all supporting links.
Monday Handoff
Use the post-demo index when the client needs one ordered follow-up path before proposal approval.
Open handoffProposal PDF View
Print, save, or forward the approval-ready proposal summary.
Open proposalDecision Room
Review demo recap materials, launch tracks, decision questions, and first-launch inputs.
Open decision roomWhat You Get
Review the full AIRES system in plain English before approving the first launch.
Open recapScope Lock Handoff
Confirm launch track, owner, support tier, CRM boundary, access model, and success metric before approval.
Open scope lockCRM Worksheet
Clarify the day-one export/import path and future CRM/API discovery boundaries.
Open worksheetFirst Launch Plan
Gather roster, listing links, routing rules, content, support tier, and timing.
Open launch planRequest Full Demo
Send the first-launch notes when the approval owner is ready for scope review.
Send inputsWhat approval unlocks
The first launch proves the operating system.
- Public community or campaign site creates the polished buyer/seller front door.
- Lead Hub preserves visitor context, routing, ownership, Smart Lists, agent queues, and accountability.
- Broker Dashboard shows follow-up risk, proposal-stage status, and operating health.
- Agent portals keep each agent focused on their own leads and follow-up.
- CRM/export readiness starts practical on day one and can deepen into APIs after scope lock.
- The client layer supports future scaling across branding, domains, modules, agents, and feature flags.
Ready for the next move
Send launch inputs when the approval owner is aligned.
The next operational step is scope lock: confirm the launch boundary, gather inputs, create Hub users, configure routing, test capture, and prepare go-live handoff.