HOMESTEADProduct Vision & Navigation Architecture
Product Vision

One calm surface where a team talks to people, works its book of business, runs outbound, measures it, and reuses its best assets.

HOMESTEAD is a Gmail-class team inbox and a real CRM and an outreach engine that never feels like five apps stapled together. It wins on coherence: a contact, a thread, and a deal are the same record seen through different lenses, and the AI copilot rides on top of every lens. Self-hosted, AI-native, and honest about being a suite — some buyers live in one mode forever, others traverse all of them in a single train of thought, and nothing is walled off from anything else.

Self-hosted AI-native copilot Gmail-class team inbox Real CRM Outreach engine Total API + MCP parity
The one idea that scales forever: modes are the only top-level chrome, and modes never multiply. A mode is a job to be done, not a feature bucket. Each mode owns an extensive left sidebar of real pages, and that sidebar is the only thing that grows. New capability = a new page inside an existing mode. The product gets deeper, never wider.
The final set

Recommended modes

Six pinned "daily-job" modes form the default dock, plus two admin-flavored modes in overflow — still modes, just not competing for daily attention. Deliverability and Settings, the two things the draft tangled, resolve into pages, not top-level entries.

Pinned core — the daily dock
Overflow — "More modes"
Rationale

Why this beats the 5-mode draft

The draft was Inbox / Leads / Campaigns / Email / Library. Here is what changed and why.

DraftFinalWhy it's better
LeadsContacts (full CRM)A lead is a lifecycle stage, not a job. Modeling the mode around it strands companies, deals, tasks, and accounts that outlive the lead stage. "Contacts" is honest and future-proofs pipeline.
Inbox + EmailInbox only; "Email" dissolvesBoth sounded like mail — the draft's biggest confusion. Deliverability scoring → Insights (a report); sending infrastructure → Admin & Build (config). One fewer top entry, zero ambiguity.
analytics scatteredInsights promoted to a modeMeasurement is inherently cross-cutting (inbox SLA + pipeline + campaign perf + deliverability). It can't live inside one mode without going blind to the rest.
no AI homeAssistant as mode + ambient railHOMESTEAD is AI-native; the copilot's heavy work — history, background runs, queue — deserves a home, not just a slide-over.
CampaignsCampaigns absorbing SequencesA separate "Outreach" mode would grow chrome. Sequences stay prominent pages inside Campaigns (launchable from a contact), honoring the broadcast-vs-1:1 split.
Settings as chromeAdmin & Build + Automations in overflow"Configure the tool" isn't a daily job, so it shouldn't compete for pinned space — but it stays a real, searchable mode, not a buried gear menu.
The rules that keep it calm forever

Navigation principles

Seven load-bearing rules. The first is the one that stops a suite from rotting into an app-drawer.

Every feature, tied to a mode

Phased roadmap board

Growth = adding pages to modes, never new top-level chrome. Each item below lands as a page inside the mode it's grouped under.

Who it's for

The people at the surface

The chrome adapts per seat — same IA, same page names, different pins. Some live in one mode forever; some traverse all of them in a single thought.