# CoolRoute Command rebrand license package

Defines what can be repeatedly sold from HVAC Dispatch: reusable product spine, white-label rights, buyer-specific boundaries, SEO/AEO route bundle, and clone-market expansion path.

## License Snapshot

Product: CoolRoute Command
Category: Field service dispatch software
License model: Productized setup license: $24k-$42k setup plus $1.2k-$4k/month recurring for one buyer tenant, with clone routes scoped per buyer segment.
Default tenant: Evergreen Mechanical
Production domain: hvac-dispatch.ideas-realized.com
Preview URL: https://hvac-dispatch.ideas-realized.com?screen=route
Preview screen: Route (route) - dispatch route board and technician schedule proof
Canonical page: https://ideas-realized.com/demo-library/hvac-dispatch
JSON manifest: /demo-library/hvac-dispatch/rebrand-license.json

## Commercial Model

Recommended tier: Dispatch board pilot
Setup fee: $24k-$42k
Recurring fee: $1.2k-$4k/month
Margin model: Target 58-68 percent implementation margin after job import, dispatcher training, route workflow tuning, and customer message review.

Add-ons:
- Field service system writeback: $18k-$45k
- SMS delivery integration: $8k-$18k plus carrier fees
- Parts inventory sync: $14k-$32k

## License Rights

- Use the proven workflow spine as a paid client setup (Included): Ideas Realized; Dispatch board and technician calendar, Inbound service request intake and triage, Work order detail view, Technician load and assignment controls can be re-skinned and configured for a named buyer tenant.
- White-label product identity, terminology, launch copy, and domain (Included): Implementation lead; [Company name] Dispatch Desk, [Service line] Command, or [Market name] RouteBoard. Use dispatch.clientdomain.com or service.clientdomain.com for production and keep hvac-dispatch.ideas-realized.com as the sales preview.
- Reuse demo proof assets for sales previews (Template): Sales lead; Keep hvac-dispatch.ideas-realized.com as the sales proof surface while the buyer tenant is configured on hvac-dispatch.ideas-realized.com.
- Publish buyer-specific SEO/AEO pages around the vertical problem (Buyer review): Growth lead; Industry and answer pages can be adapted after buyer approves terminology, claims, and local service angles for HVAC dispatch software.
- Resell as a full replacement for every buyer system of record (Excluded): Solutions lead; The license covers the scoped workflow layer, import templates, and app surfaces. Full ERP/PMS/CRM replacement is handled as a separate change order.

## Repeatable Assets

- Dispatch board and technician calendar (Core): Product workflow spine; Retain the module behavior while swapping terminology, roles, data labels, and buyer copy.
- Inbound service request intake and triage (Core): Product workflow spine; Retain the module behavior while swapping terminology, roles, data labels, and buyer copy.
- Work order detail view (Core): Product workflow spine; Retain the module behavior while swapping terminology, roles, data labels, and buyer copy.
- Technician load and assignment controls (Core): Product workflow spine; Retain the module behavior while swapping terminology, roles, data labels, and buyer copy.
- Customer communication queue (Core): Product workflow spine; Retain the module behavior while swapping terminology, roles, data labels, and buyer copy.
- Work orders (Template): Tenant data setup; Customer, site, job type, technician, service window, status, priority, value.
- Service requests (Template): Tenant data setup; Inbound calls and web forms with channel, received time, SLA, technician recommendation, and triage state.
- Technicians (Template): Tenant data setup; Role, skill context, current load, utilization, next stop.
- Rescue dispatch decisions (Template): Tenant data setup; Capacity recommendations, affected work orders, route ETA, customer promise, and decision state.
- Service command identity (Custom): Client marketing lead; Logo, fleet-safe color accents, dispatcher screen mark, and customer-message footer.
- ETA message tone set (Template): Service manager; Approved arrival-window, delay, and parts-delay copy for dispatch review.
- Route board labels (Template): Dispatcher; Capacity states, priority names, skill tags, and service territory labels.
- Customer ETA messages (Template): Integration setup; SMS/email wording and triggers are scoped for same-day dispatch.
- Service platform sync (Custom): Integration setup; Depends on ServiceTitan, Housecall Pro, Jobber, or custom records.
- Map routing (Template): Integration setup; Can be connected after technician and address data are live.

## Clone Market Rights

- Plumbing service dispatch board: plumbing dispatch software
  Segment: Residential plumbing service companies
  Launch path: /industries/plumbing-dispatch-software
  Fit score: 92/100
  License move: Swap HVAC equipment terms for plumbing fixtures
  Proof reuse: Reuses dispatch board, assignment drawer, route optimization, communications, closeout, and agreement conversion workflows.
  Risk control: Confirm emergency-call triage and after-hours escalation rules before pilot launch.
- Appliance repair scheduling desk: appliance repair dispatch software
  Segment: Appliance repair operators
  Launch path: /industries/appliance-repair-dispatch-software
  Fit score: 85/100
  License move: Swap systems for appliance categories
  Proof reuse: Reuses schedule board, route planner, communications, technician assignment, and closeout invoice flows.
  Risk control: Separate parts availability from appointment readiness before enabling customer notices.
- Pool and spa service route board: pool service route scheduling software
  Segment: Pool and spa maintenance teams
  Launch path: /industries/pool-service-route-scheduling-software
  Fit score: 79/100
  License move: Rename technicians as route techs
  Proof reuse: Reuses route optimization, board status, communications, closeout, and maintenance agreement screens.
  Risk control: Add recurring-route templates before promising automated schedule generation.

## SEO/AEO Route Bundle

- Canonical demo plan: /demo-library/hvac-dispatch (indexable canonical) - Primary product/spec page that proves the reusable demo before a buyer-specific launch.
- Live app proof: https://hvac-dispatch.ideas-realized.com?screen=route (noindex app) - Route: dispatch route board and technician schedule proof
- Industry pillar page: /industries/hvac-dispatch-software (indexable industry) - Buyer-intent page for HVAC dispatch software.
- Buyer walkthrough: /demo-library/hvac-dispatch/buyer-walkthrough (indexable handoff) - Public proof path for sales calls and implementation review.
- Pilot package: /pilot-packages/hvac-dispatch-pilot-package (indexable handoff) - Field service dispatch software pilot package
- HVAC dispatch scheduling software for same-day service teams: /industries/hvac-dispatch-scheduling-software (indexable answer) - HVAC dispatch scheduling software: Service manager wants better schedule and technician visibility.
- HVAC parts hold workflow for dispatch teams: /resources/hvac-parts-hold-workflow (indexable answer) - HVAC parts hold workflow software: Dispatcher wants fewer same-day route surprises.
- HVAC dispatch board vs field service software customization: /compare/hvac-dispatch-board-vs-field-service-customization (indexable answer) - HVAC dispatch board software: Buyer wants a practical dispatch layer around existing field service software.
- Plumbing service dispatch board: plumbing dispatch software: /industries/plumbing-dispatch-software (indexable clone) - plumbing dispatch software
- Appliance repair scheduling desk: What should HVAC dispatch scheduling software show? Proof source: Assignment change history and ETA message approval queue (indexable clone) - appliance repair dispatch software
- Pool and spa service route board: How can dispatchers manage parts delays without losing the route? Proof source: Parts hold blocker report (indexable clone) - pool service route scheduling software

## Implementation Boundaries

- Client data remains buyer-provided until import approval: Buyer operations lead; 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.
- Terminology and claims require buyer approval before publication: Client sponsor; Buyer must approve live ETA, delay, and parts-message language before notifications are enabled.
- Production domain and DNS are client-specific: Technical lead; hvac-dispatch.ideas-realized.com
- Support, SLA, and legal terms follow the signed SOW: Procurement owner; This demo SOW package is a sales and implementation planning artifact, not legal advice.
- Change-order trigger: Project sponsor; Live SMS/email sending or customer communication automation: Requires sender approval, compliance review, and separate messaging implementation. Owner: Client sponsor.
- Change-order trigger: Project sponsor; Two-way field-service writeback, invoices, or technician mobile app: Quote as a follow-on integration or module after daily board pilot acceptance. Owner: Implementation lead.

## Buyer Handoff Requirements

- Technician roster and territories: Service manager. Technician names, skills, service areas, shift windows, and capacity assumptions.
- Sample work orders: Dispatcher. Recent calls with status, priority, location, time window, customer note, and parts need.
- Customer message templates: Client sponsor. ETA, delay, technician assigned, and parts-hold message templates ready for approval.
- Provide daily job export and technician roster before configuration starts.
- Approve customer message language before any send workflow is considered.
- Assign one dispatch lead to validate board behavior and field-service handoff.
- Daily job export with customer, address, priority, service type, window, status, and assignment fields.
- Service command identity: Logo, fleet-safe color accents, dispatcher screen mark, and customer-message footer.

## Partner Operating Notes

- Use hvac-dispatch.ideas-realized.com as the reusable sales preview and hvac-dispatch.ideas-realized.com as the buyer tenant target.
- Keep app-only routes noindex; route search demand through /industries/hvac-dispatch-software, answer briefs, pilot package pages, and clone industry pages.
- Do not publish buyer-specific claims, client names, ROI, or integrations until the SOW and procurement review are approved.
- Use the tenant clone package score (81/100) as the handoff signal before committing to launch timing.

## Approval Checklist

- Territory and schedule accepted: Pilot territory, technician roster, skill tags, and schedule windows validated.
- Customer message copy approved: ETA, delay, and parts-hold templates approved with opt-out/compliance notes.
- Dispatcher workflow accepted: Dispatcher completes reschedule, route review, and parts-hold scenarios in the pilot workspace.
- This demo SOW package is a sales and implementation planning artifact, not legal advice.
- Final MSA, DPA, payment terms, taxes, procurement language, and security addenda require buyer/legal review before signature.
- No regulated production data should be loaded until data-processing, access, retention, and incident-response terms are approved.
- Confirm field-service vocabulary: Role, job, ETA, and parts language can be applied before service-system mapping.
- Approve customer-message copy: Buyer must approve live ETA, delay, and parts-message language before notifications are enabled.
- Configure dispatch domain: Production domain and app-subdomain routing are ready after the client chooses the service URL.

## Handoff Links

- White-label kit: /demo-library/hvac-dispatch/white-label-kit
- White-label kit JSON: /demo-library/hvac-dispatch/white-label-kit.json
- Tenant clone package: /demo-library/hvac-dispatch/tenant-clone-package
- Tenant clone package JSON: /demo-library/hvac-dispatch/tenant-clone-package.json
- Statement of work: /demo-library/hvac-dispatch/statement-of-work
- Statement of work JSON: /demo-library/hvac-dispatch/statement-of-work.json
- Deal desk package: /demo-library/hvac-dispatch/deal-desk
- Deal desk JSON: /demo-library/hvac-dispatch/deal-desk.json
- Procurement pack: /demo-library/hvac-dispatch/procurement-pack
- Production data contract: /demo-library/hvac-dispatch/data-contract
- Production data contract JSON: /demo-library/hvac-dispatch/data-contract.json
- Deployment launch plan: /demo-library/hvac-dispatch/deployment-launch
- Deployment launch plan JSON: /demo-library/hvac-dispatch/deployment-launch.json
- Launch room: /demo-library/hvac-dispatch/launch-room