# System Landscape

## Purpose

This document maps the major systems in the current No More Chores stack and the roles they may play in a future architecture.

## Current systems

### Launch27
Role today:
- booking and scheduling backbone
- service and pricing reference
- historical booking and customer data

Known issues:
- official API is not reliable enough for live scheduling and booking operations
- some operational work requires direct UI interaction or workaround methods
- needs deeper analysis of what it still does well and what is hardest to replace

### GoHighLevel (GHL)
Role today:
- communications and CRM-like functions
- pipelines and follow-up support
- current comms hub for parts of the business

Known issues:
- viewed as archaic
- may be a poor long-term foundation
- may still be useful as transitional infrastructure

### Airtable
Role today:
- operational support data and lookup workflows

Known issues:
- some fields are unreliable as canonical truth
- should not automatically be treated as system of record

### Twilio
Role today:
- messaging and telephony transport
- essential infrastructure for SMS and phone workflows

### Vapi
Role today:
- voice AI layer for Leah
- currently used in staging for voice workflows

### Leah
Role today:
- AI-facing customer interaction layer for SMS and voice
- strategically important because it represents the front door of the future system

### HubSpot
Role under consideration:
- possible CRM layer
- candidate for simplifying customer relationship management and automation architecture

Key question:
- should HubSpot own CRM while CleanOS owns cleaning-specific operations?

## Architectural question

The key strategic issue is not whether one tool can do everything.
It is whether the future stack has clear ownership boundaries for:
- customer records
- conversations
- quotes
- bookings
- schedules
- automation
- reporting

## Hypothesis to test

A better future architecture may be hybrid rather than all-or-nothing:
- keep best-in-class generic systems where they are strong
- build or own the cleaning-specific operational core where existing tools are weak