# HubSpot Decision Frame

HubSpot should be considered seriously, not as an afterthought.

## Why this matters

One of the key architectural questions is whether CleanOS needs to own CRM broadly, or whether it should focus on cleaning-specific operational truth while a stronger generic CRM handles relationship management, pipelines, and marketing automation.

## The real question

The question is not "Should we use HubSpot because it is modern?"
The question is:
- what should own contacts and customer relationship workflows?
- what should own quotes, bookings, schedules, and cleaning-specific logic?
- where does marketing automation belong?
- what creates the lowest-friction path to near-term leverage?

## Possible outcomes

### Option 1: HubSpot as CRM, CleanOS as operations layer
This is attractive if:
- HubSpot can handle contact history, pipeline, forms, and marketing better than custom building
- CleanOS can stay focused on the operational core
- integration complexity is lower than replacing everything yourself

### Option 2: Transitional CRM outside, later consolidation
This is attractive if:
- the near-term need is speed, not purity
- a clean long-term system of record is not yet clear
- dogfooding needs are still evolving

### Option 3: CleanOS owns more over time
This is attractive only if:
- the cleaning-specific workflow value clearly pulls CRM ownership into the product
- enough operational truth and workflow advantage accumulates to justify it

## Instruction for Claude

Do not assume the all-in-one path is superior.
Recommend the ownership boundary that best supports speed, reliability, and real business value.