Giant Pumpkin · internal platform
ConnectIQ is the internal operational platform for the Giant Pumpkin business — CRM, deployment, subscriptions, inventory, support and customer dashboards. It is being built to take over, in order, the jobs currently done by HubSpot and by parts of the Airtable system.
This is the canonical set. The design system fixes how it looks, the object model fixes what the entities are, the architecture fixes how they are separated and how one domain may reach another, and the delivery plan fixes what gets built and in what order. When they disagree, the order of precedence is model → architecture → plan → screens.
The set
Each is self-contained and readable on its own. Read them in this order the first time.
Tokens, colour, type, components, chart gradients, KPI cards, accent lines, motion and the footer mark. The visual source of truth, with a copy-to-clipboard block for Claude and Lovable.
Stable Open 02 · ModelThe persistent, location-anchored ConnectIQ object that jobs act on rather than hang off. Separates what persists from what happens, and sets the Accounts / Deployment boundary the whole system inherits.
For review Open 03 · Binding rulesOne Postgres database, separated by domain prefix and built to split into real services later. The cross-domain interaction matrix, the outbox event pattern, read projections, snapshot-versus-reference and the identifier conventions — plus a copy-ready knowledge block for Lovable.
Revised · binding Open 04 · MethodHow anything ships, independent of what is shipping. Lovable projects as the unit of isolation, git and Supabase branching with their real costs, what gets tested and by whom, Vercel and the path to production, and the guardrails that keep a code-generating assistant inside one domain.
Decided · 4 open Open 05 · PlanPhase 1 — build the CRM and retire HubSpot. The release boundary, what the prototype extraction established, the entity map, the M1–M8 milestone sequence, migration and cutover, and the risks. Plus a register of every decision still outstanding, and one build prompt per milestone.
Draft · decision-grade Open 06 · DeferredEverything after cutover, and everything phase 1 chose not to carry. The deployment domain — jobs, inventory, support, device health — the shape the dependencies force, what sits parked and why, and the decisions that only matter once phase 1 has shipped.
Scoped · not planned Openstyle-kit/ holds the machine-readable tokens and the AI instruction files — tokens.json, DESIGN.md, CLAUDE.md, LOVABLE_WORKSPACE_KNOWLEDGE.md, LOVABLE_PROJECT_KNOWLEDGE.md — the last two sized for Lovable's two 10,000-character Knowledge slots. sources/ holds the superseded definition documents, the sidenav component spec, and the original CRM functional specification the phase 1 plan is derived from.
Where things stand
Giant Pumpkin currently runs sales in HubSpot and operations in Airtable, with a prototype CRM built in Lovable that proved the shape of the quote and forecast model. Phase 1 turns that prototype into a real system and retires HubSpot. Airtable stays exactly where it is.
Replaced by ConnectIQ CRM in phase 1. Data migrates once, then syncs one-way during the parallel run.
Remains the operational system of record. Read into ConnectIQ; nothing is written back in phase 1.
Accounts and commerce domains first. The deployment domain lands in a later phase.
Specification input, not the build. Its functional spec is preserved in sources/.
The long-term intent is that ConnectIQ absorbs the Airtable operational system table by table. That is phase 2, and it is deliberately not phase 1. Phase 1 earns the right to do it by first replacing a system with a clean boundary — HubSpot — and proving the accounts and commerce model against real data.
How to use this