ContentsWhat's inside

This guide walks through your Base BCC end-to-end — the layers underneath, the sixteen modules on the surface, the rules that keep it compliant, and the way it works with you day to day.

Part 01What the BCC actually is

A dashboard shows you numbers. A CRM tracks contacts. A to-do list nags you. The BCC does none of those things exclusively — it does all of them, and it does something a plain dashboard can't: it thinks alongside you.

The Business Command Center is your operating system for running your State Farm agency. It sits on top of every tool you were already using — Gmail, Drive, Calendar, State Farm's daily comp emails, QuickBooks, your bank, your payroll provider, your social accounts — and turns them into one continuous stream of context that your Claude can reason over.

The point is not to give you another place to log in. The point is that when you ask a question — "how did last month's commissions come in?", "what's my AIPP pace?", "can I afford a fourth producer?" — the system already has the answer, because everything upstream has been feeding it while you weren't watching.

Three ideas the BCC is built on

Part 02The four layers underneath

The BCC is a stack of four cooperating layers. Each has a specific job. You can understand any question about the system by asking which layer it lives in.

Data flows up. Actions flow down. Your questions land at the top; answers arrive with everything below already accounted for.

What each layer does

Part 03The webapp, module by module

Your Base BCC ships with 16 modules across five categories. Every module reads from the same Supabase source of truth and every module is Claude-aware.

Money & performance

People & operations

Content & communication

Operations & automations

Reference & setup

Part 04Working with your Claude

This is where most people spend the most time misunderstanding what they've been given. It's worth reading twice.

That's why you can lose your laptop, start a fresh chat next Tuesday, or open the BCC on your phone — and your Claude will still know your SMVC rate, your CPA's name, the roster of producers on your team, the tone you prefer to be spoken to in, and the SF rules that shape every response (like AIPP requiring 60 months of service).

The persistent memory categories

Facts get stored under one of ten categories: agency_profile (URLs, entity, SMVC), business_context (structure, rules), financial_context (targets, benchmarks), sf_compensation (bonus structures), accounting_rules (cash basis, PFA not an asset), compliance_rules (AA05 excerpts), communication_prefs (tone, formatting), goals (annual, quarterly), key_contacts (CPA, SF field consultant), and session_log (what happened in past conversations).

Three ways to talk to your Claude

Adding a new rule

Just tell your Claude the rule. Then say "remember this." The Claude will store it to the appropriate memory category and confirm. Next time — no matter which conversation, which device, which day — the rule applies.

You: "From now on, when we talk about producer ROI,
     always assume a 10% annual lapse rate.
     Remember this."

Claude: [stores rule in persistent_memory under 'financial_context']
        Got it. ROI projections will use a 10% annual lapse rate
        going forward. This is saved to memory.

Part 05The automation layer

Twelve recipes run in the background so you don't have to. They read email, parse documents, write to the ledger, post to social media, and send you your morning briefing.

Every recipe lives in the automation_recipes table in Supabase and is scheduled via pg_cron. When a recipe fires, it calls a Composio tool to do its work, then writes a row to automation_run_log with the result. If something fails, an alert fires and you see it on the Dashboard the next morning.

Part 06Compliance guardrails

You are a captive State Farm agent. The AA05 Agent Agreement governs what you can and cannot say, offer, or advertise. The BCC bakes those rules into the system itself so compliance never lives in your head alone.

Word rules — automatic in every response

Certain words trigger automatic rewrites. Your Claude never generates prohibited language, regardless of who's asking.

Social media — the 26-item checklist

Before any social post is presented as final, the system runs a 26-item compliance pre-flight. The full checklist is in the Compliance module. Highlights:

• No prohibited topics — investments, mutual funds, college savings, specific L&H product names, pricing, or internal SF processes.
• No customer PII, SPI, or PHI — ever.
• English only — FINRA archiving requires it.
• Personal Price Plan® — always written in full; consumers create it, never get it.
• Giveaways — every participant receives the item. No element of chance.
• Referral rewards — never advertised on social.
• AI disclaimer — included whenever AI was used in the visual.
• Written release — required for all identifiable people in photos or videos.
• State license numbers — included for AR and NM residents when required.

Part 07Following a dollar

A trace of what actually happens when SF pays you a commission — from the moment the email arrives to the moment the dashboard shows it. This is the whole system working in concert.

Part 08Getting started

If you're sharing this guide with someone new — your CPA, a new hire, your SF field consultant, or a future collaborator — this section is for them.

Where to log in

The webapp lives at sunshinestate-bcc.vercel.app. Your Claude project on claude.ai is the conversation surface where the heavy work gets done.

Your first login

On your first sign-in, the Dashboard becomes your home. Read what's on the screen top to bottom: the Financial Health card, the AIPP pace tile, open items, alerts, and the "modules filling up" indicator. Everything that requires input is surfaced there. There is no separate onboarding checklist — the Dashboard is the checklist.

The first week

Every morning, open the BCC. The Dashboard is the launchpad. Read the daily briefing email that arrives at 7:00 AM CDT. Click through anything the alerts panel is showing you. That's the loop. Everything else — the deeper questions, the strategic work — happens in claude.ai when you have a specific decision to make.

What we recommend forwarding to your service mailbox

Certain documents unlock parts of the system automatically when they land in sunshinestate.claude@gmail.com:

• SF daily comp email — flows in automatically once your SF email is forwarding.
• SF semi-monthly deduction statements — same.
• SF monthly Producer Production report — the biggest single unlock. Forwarding this one email each month powers the Performance tab, Commission Detail, AIPP pace projections, the producer ROI model, and the underperformance watcher.
• Bank and credit card statements — parsed into the ledger automatically.
• Payroll provider notifications — the payroll processor writes them straight into payroll_runs.

Part 09Support & self-healing

The BCC is designed so most problems flag themselves before you notice them. When they don't, the fix is usually a one-click reauthorization.

What can go wrong (and how it heals)

Two layers of connection health

Part 10Appendix: key identifiers

The URLs, IDs, and contacts every operator eventually needs.

Live surfaces

System identifiers

People

Financial benchmarks the system monitors

Benchmarks sourced from the State Farm Agency Reference Guide. Warning and critical bands fire automatic alerts on the Dashboard when a rolling calculation crosses a threshold.