# CoolRoute Command client launch plan A buyer-facing launch plan for taking HVAC Dispatch from demo approval to a branded field service dispatch software pilot, with order terms, domain setup, data intake, SEO/AEO distribution, acceptance evidence, and support handoff in one packet. Buyer default: Evergreen Mechanical Sponsor role: Client sponsor Target launch window: Weeks 2-6; 1 week job import, 2 weeks board and notification workflow, 2 weeks same-day dispatch pilot. Configured domain: hvac-dispatch.ideas-realized.com Sales preview URL: https://hvac-dispatch.ideas-realized.com Canonical page: /demo-library/hvac-dispatch Industry page: /industries/hvac-dispatch-software JSON manifest: /demo-library/hvac-dispatch/client-launch-plan.json ## Commercial Order Default Dispatch board pilot: $24k-$42k setup and $1.2k-$4k/month recurring. 45 percent due at signature for territory setup, job import mapping, and dispatcher workflow design. ## Launch Steps - [queued] Approve commercial order packet (Dispatch manager, Commercial): Pilot territory, technician roster, skill tags, and schedule windows validated. Recommended tier: Dispatch board pilot. - [needs client] Confirm brand, domain, and tenant defaults (Client DNS owner, Brand and domain): Use hvac-dispatch.ideas-realized.com for production after Use dispatch.clientdomain.com or service.clientdomain.com for production and keep hvac-dispatch.ideas-realized.com as the sales preview.. - [needs client] Send source data and approve import sample (Dispatch manager, Data import): Start with a read-only job and technician import, reconcile service categories, then allow dispatchers to update pilot board status while the source platform remains system of record. First template: hvac-dispatch-work-orders.csv. - [template] Publish SEO/AEO launch links (Growth lead, SEO/AEO): Publish dispatch and technician-capacity pages together, then add comparison pages for field-service systems and spreadsheets. Primary intent: HVAC dispatch scheduling software. - [blocked] Run acceptance gates and release checks (Dispatcher, Acceptance): Dispatch board and route panel show technician load and sequence changes. - [ready] Activate support and monitoring handoff (Dispatch launch thread, Support): Dispatch launch thread: Business days during pilot. Renewal signal: Dispatch scheduling inquiry: 2 qualified HVAC service inquiries per quarter. ## Go-Live Evidence - Reassign same-day job and preserve route context (complete): Dispatch board and route panel show technician load and sequence changes. - Send ETA message draft from comms queue (queued): Message queue data is present; SMS provider not selected. - Hold a job for unavailable parts (complete): Parts hold workflow shows ETA, risk, and owner. - Pick pilot dispatch window (complete): Service manager; Start with weekday same-day calls before after-hours workflows. - Approve ETA message templates (queued): Operations lead; Customer-facing SMS copy needs final tone and compliance approval. - Clean technician skills (in progress): Dispatcher; Normalize install, service, warranty, and refrigeration certifications. - Demo app availability: Homepage and app route return 200 from production domain after DNS cutover. - Urgent jobs assigned with approved ETA or parts status before service window risk: Pilot usage is visible in the buyer dashboard within the first review cycle. ## SEO/AEO Distribution - Canonical demo page: /demo-library/hvac-dispatch - Industry pillar: HVAC dispatch software at /industries/hvac-dispatch-software - Primary intent: HVAC dispatch scheduling software - What should HVAC dispatch scheduling software show? CTA: Open the HVAC dispatch board demo. - How can dispatchers manage parts delays without losing the route? CTA: Show the parts hold workflow in the demo. - Can ETA messages be drafted before sending to customers? CTA: Use queued ETA messages as the communication proof point. - HVAC dispatch scheduling software for same-day service teams: /industries/hvac-dispatch-scheduling-software - HVAC parts hold workflow for dispatch teams: /resources/hvac-parts-hold-workflow ## Handoff Assets - Client proposal markdown: /demo-library/hvac-dispatch/client-proposal - A client-ready proposal for turning the HVAC Dispatch demo into a scoped, rebrandable field service dispatch software pilot with clear launch owners, commercial terms, acceptance criteria, and follow-on SEO/AEO expansion. - Client launch plan JSON: /demo-library/hvac-dispatch/client-launch-plan.json - Machine-readable go-live manifest with launch steps, assets, SEO/AEO routes, and implementation pointers. - Deal desk package JSON: /demo-library/hvac-dispatch/deal-desk.json - Machine-readable commercial order form with line items, add-ons, payment milestones, approval gates, and redlines. - Deal desk package markdown: /demo-library/hvac-dispatch/deal-desk - Buyer-ready order packet for pricing, scope boundaries, approval evidence, and commercial handoff. - Statement of work package JSON: /demo-library/hvac-dispatch/statement-of-work.json - Machine-readable SOW with scope modules, milestones, acceptance criteria, responsibilities, service levels, exclusions, and signature blocks. - Statement of work package markdown: /demo-library/hvac-dispatch/statement-of-work - Buyer-signable SOW packet for final scope review, support terms, data responsibilities, and change controls. - Rebrand license package JSON: /demo-library/hvac-dispatch/rebrand-license.json - Machine-readable reusable-license manifest with rights, repeatable assets, clone markets, SEO/AEO routes, boundaries, and approval requirements. - Rebrand license package markdown: /demo-library/hvac-dispatch/rebrand-license - Partner-ready package defining what can be repeatedly sold, rebranded, SEO-cloned, and handed to implementation. - Buyer launch room: /demo-library/hvac-dispatch/launch-room - Single buyer review room for app proof, launch readiness, handoff assets, and acceptance gates. - Deployment launch plan JSON: /demo-library/hvac-dispatch/deployment-launch.json - Machine-readable domain, DNS, environment variable, release gate, monitoring, rollback, and SEO launch plan. - Deployment launch plan markdown: /demo-library/hvac-dispatch/deployment-launch - A production handoff plan for taking HVAC Dispatch from sales preview to a client-owned launch domain with Netlify hosting, environment gates, monitoring, rollback, and canonical SEO/AEO checks. - Buildout roadmap markdown: /demo-library/hvac-dispatch/buildout-roadmap - A dispatcher can see unassigned work, technician capacity, route order, parts blockers, and customer ETA message readiness from one daily board. Package one-territory dispatch board pilot with job import, technician load rules, ETA message review, and parts-hold report. - White-label rebrand kit JSON: /demo-library/hvac-dispatch/white-label-kit.json - Machine-readable tenant identity, naming pattern, variants, terminology swaps, launch copy, and rebrand checklist. - White-label rebrand kit markdown: /demo-library/hvac-dispatch/white-label-kit - Buyer-facing rebrand terms, tenant defaults, copy blocks, brand assets, and launch naming. - Implementation JSON: /demo-library/hvac-dispatch/implementation.json - Machine-readable route, setup, security, and tenant configuration. - OpenAPI implementation spec: /demo-library/hvac-dispatch/openapi.json - Machine-readable tenant API, schema, dry-import, workflow action, and event manifest. - Sample data package JSON: /demo-library/hvac-dispatch/sample-data-package.json - Machine-readable CSV template, seed row, validation, and dry-import manifest. - Sample data package markdown: /demo-library/hvac-dispatch/sample-data-package - Buyer-ready data collection packet with CSV templates, sample rows, and validation gates. - Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json - Machine-readable production entity, source, event, route, and tenant-boundary contract. - Production data contract markdown: /demo-library/hvac-dispatch/data-contract - Implementation-facing entity, source, event, route, and tenant-boundary contract. - Tenant clone package JSON: /demo-library/hvac-dispatch/tenant-clone-package.json - Machine-readable rebrand-and-launch package for turning the demo into a buyer tenant. - Tenant clone package markdown: /demo-library/hvac-dispatch/tenant-clone-package - Rebrand lanes, clone targets, production domain, and reusable launch moves. - Tenant cutover plan JSON: /demo-library/hvac-dispatch/tenant-cutover-plan.json - Machine-readable cutover manifest with phases, acceptance gates, rollback controls, SEO/AEO publication, and handoff routes. - Tenant cutover plan markdown: /demo-library/hvac-dispatch/tenant-cutover-plan - Buyer and implementation cutover packet for commercial signoff, tenant identity, data dry-run, access, go-live, rollback, and SEO/AEO launch. - Tenant seed package JSON: /demo-library/hvac-dispatch/tenant-seed-package.json - Machine-readable tenant users, roles, data sources, integrations, feature flags, automations, notifications, and launch assets. - Tenant seed package markdown: /demo-library/hvac-dispatch/tenant-seed-package - Implementation-facing seed artifact for standing up the first branded buyer workspace. - Work order import: /demo-library/hvac-dispatch/import-templates/work-order-import - hvac-dispatch-work-orders.csv: Creates dispatch board jobs, priority state, appointment windows, and customer communication context. - Technician roster import: /demo-library/hvac-dispatch/import-templates/technician-roster - hvac-dispatch-technician-roster.csv: Loads technician capacity, service role, territory, and next-stop visibility. ## Buyer Kickoff Fields - Buyer name: Evergreen Mechanical - Sponsor role: Client sponsor - Target launch window: Weeks 2-6; 1 week job import, 2 weeks board and notification workflow, 2 weeks same-day dispatch pilot. - Configured domain: hvac-dispatch.ideas-realized.com - Preview URL: https://hvac-dispatch.ideas-realized.com ## Support Handoff - A buyer-ready support model for launching HVAC Dispatch with triaged tickets, service levels, training artifacts, success milestones, and renewal proof tied to the first pilot cohort. - Kickoff (Week 1): Dispatch manager; Daily job import template and technician skill map are accepted. Review 1 client-owned integration decisions before production cutover. - Configuration (Weeks 2-3): Implementation lead; Dispatcher can assign sample jobs and prepare ETA messages. Confirm 2 notification templates before enabling outbound automation. - Pilot (Weeks 4-5): Dispatcher; Assignment clarity, ETA readiness, and parts blocker report are accepted. Export implementation spec after 3 acceptance checks are reviewed. - Pilot support scope: $1.2k-$4k/month recurring for hosting, support, and workflow tuning. - Daily job import template - Technician roster and skill map ## Acceptance Summary 85/100 buildout readiness. Next milestone: Pilot same-day dispatch board with two technicians and one coordinator. 2 blocker(s) remain.