Four numbers (clients, pipeline value, won, open tasks) plus follow-ups due. Start the day here; anything urgent also appears in Health → Needs you.

One card per tab with an OK or attention chip: inquiries waiting over 48 hours, overdue or blocked tasks, client or builder chats waiting on your reply, AI spend near its cap, and whether SSO, Stripe, email, and Gemini are switched on. It re-checks itself every hour while the console is open; press Refresh now anytime.

Open any client to edit their status, progress, and milestones, add invoices, reply in their message thread, and upload files into their portal. Everything you change appears on their dashboard instantly. Use the Reset password button if a client is locked out; remove an account when an engagement ends.

Leads move New → Contacted → Proposal → Won with the arrow buttons. Give each a value so the Overview pipeline number means something. This board is yours alone; clients and builders never see it.

All three site forms land here with whatever the visitor filled in. Work the status chain (New → Replied → Scoped → Won or Lost) so the queue stays honest. Health flags anything that sits in New past 48 hours.

Create a task, pick a service, set a due date and priority, and assign it to a builder. They see only their own tasks; you see all of them, with their status changes and notes as they work. Overdue and blocked tasks surface in Health.

Add a builder with an email and starter password; they sign in through the same portal door as everyone else and land in their own portal. Each builder has a private chat with you here, including file deliverables. Reset passwords or remove access the day someone leaves.

Sales, delivery, finance, support, and the rest: each card says what that department owns, which console tab runs it, the working rhythm, and what to watch. It is the org chart for a company of one (plus builders).

Ten services, five stages each (intake, scope, build, verify, deliver) with steps, checklists, and deliverables. Builders read the same library, so "how do I do this" always has one answer.

Complete starter templates for every sample on the site, plus the legal agreements (client services + builder). Preview opens a working copy; Download gives the file. Served only to you and builders through signed 15-minute links; there is no public URL.

It already knows your playbooks, pricing, and site facts, plus a live snapshot of the intake queue, task board, and roster on every question. Ask it to draft replies, summarize the queue, or pull a playbook step. Spend is hard-capped monthly; the meter shows where you stand.

Press Lock (top right) on shared machines; your session also expires on its own. Never put passwords, card numbers, or ID photos in any message thread. When a builder or client leaves, remove them in Team or Clients and their access dies immediately. The full model is written down in SECURITY.md.

1. Open public/index.html in the site folder.
2. Search for the text (each tab is one section in that file).
3. Edit and save.
4. Run "netlify dev", open localhost, read the tab you touched.
5. Deploy: "netlify deploy --prod", then walk the post-deploy checks in DEPLOY-CHECKLIST.md.

1. Drop the demo file into public/demos/ (one self-contained HTML).
2. Copy an existing Work-tab card in index.html and point it at demos/your-file.html.
3. Update the sample count so it stays honest.
4. Want builders to get the source too? Copy it into netlify/templates/demos/ and add one line to manifest.json.

1. index.html: add it to Services and to the contact form's "What you need" list.
2. netlify/templates/sop/sops.json: add its five-stage playbook.
3. netlify/templates/: add its starter template + a manifest.json line.
4. Optional: a public sample in demos/ with a Work-tab card.
5. Deploy, then quiz the AI assistant about the new service; it reads the playbooks, so a correct answer proves the wiring.

1. Google SSO: create an OAuth Web client at console.cloud.google.com, set GOOGLE_CLIENT_ID in Netlify env.
2. Stripe: set STRIPE_SECRET_KEY (start with the sk_test key), optionally STRIPE_WEBHOOK_SECRET for the webhook.
3. Email: set RESEND_API_KEY after verifying your domain at resend.com.
4. Redeploy. The Health tab's Integrations row flips from dormant to on by itself; nothing else to wire.

1. "netlify dev" in the folder (needs the .env).
2. Walk FUNCTIONALITY-CHECKLIST.md (F1-F41) top to bottom.
3. Walk UI-CHECKLIST.md (U1-U23) at desktop and phone width.
4. Open Health here; everything should read OK or be explained.
5. Zero browser-console errors on every page (one known local-only 405 is documented).

1. Copy the whole folder to omerica-site-v3-TIMESTAMP; never rebuild in place.
2. Keep netlify/ untouched first; the portals and all client data keep working while you redo the marketing pages.
3. Preserve the storage shapes (accounts, projects, intake, tasks, chats, files) and every client, message, and invoice survives with zero migration.
4. Re-skin portals last, one file at a time, re-running the checklists after each.
5. Deploy to a NEW Netlify site, prove it with the post-deploy checks, and only then move the domain. The old site stays live until the new one is proven.