Leverage Flo Website Marketing Agency Configuration

You are working on LeverageFlo — an AI marketing agency website for ambitious UK SMEs.

Tech stack: React 19 + TypeScript + tRPC 11 + Express 4 + PostgreSQL + Drizzle ORM + Tailwind CSS 4 + shadcn/ui + Clerk auth

Key rules:
- All backend calls MUST use tRPC (never fetch/axios directly)
- GHL is the ONLY billing provider — no Stripe
- GHL Location ID: VObyDne0JSzn6nvQTSab
- GHL PIT: pit-d14377cf-09bd-432b-84a4-3446b6159519
- All GHL IDs are in server/lib/ghlBilling.ts (LF_CONFIG object)
- Clerk is the ONLY auth provider
- Service tiers: FloIgnite £995/mo, FloAccelerate £1,995/mo, FloDominate £3,495/mo
- All GHL tags use lf- prefix (e.g. lf-new-lead, lf-active-client)
- GHL calendars: free_audit=raPYdhDyAQokd2TY4ujS, strategy_call=OC6MjJAbPC94PskCEDBo

Architecture:
- server/lib/ghlBilling.ts — LF_CONFIG is source of truth for all GHL IDs
- server/routes/ghl.ts — GHL webhook receiver
- server/routes/leads.ts — Lead capture to GHL contact creation
- server/routers/ghlBilling.ts — tRPC billing procedures
- server/routers.ts — Main tRPC router
- drizzle/schema.ts — Database schema
- client/src/pages/ — All page components

When making changes:
1. Update drizzle/schema.ts for DB changes, then run pnpm db:push
2. Add DB helpers to server/db.ts
3. Add tRPC procedures to server/routers.ts or server/routers/feature.ts
4. Wire UI with trpc.*.useQuery/useMutation
5. Run pnpm check (TypeScript) before committing
6. Run pnpm test before committing

See docs/TECHNICAL_MANUAL.md for full architecture details.