Description
What you're building A hands-off lead-routing system for a freight lead-matching platform (solo founder). Shippers submit a form, the system texts the lead to up to 2 verified carriers, carriers reply 1 to accept or 2 to pass, credits deduct on accept only. All accounts are mine (Supabase, Twilio, n8n Cloud, Stripe, WordPress). You build inside my accounts. I own all code and configs at handoff. Scope Supabase: run my 4-table schema (carriers, leads, lead_offers, credit_transactions) plus a small markets config table (slug, status open/waitlist, outbound Twilio number, waitlist alert thresholds, alert-notified flag). Leads add market, sms_opt_in (boolean, default false) and booked_carrier_id (nullable FK to carriers). RLS: service_role full access, anon = insert on leads only. Lead form: self-contained HTML/JS block (embeds in a WordPress Gutenberg Custom HTML block, no plugins) posting to Supabase. Client-side validation. Auto-classifies each lead standard (1 credit) or premium (3 credits) by freight type. Market dropdown (Laredo preselected) and an SMS-consent checkbox (writes sms_opt_in). Leads submitted for a waitlist market get an honest on-page + email "you're on the list" response instead of routing. Carrier signup: HTML block + signup logic that grants free credits by tier: carriers 1–5 get 6 credits, 6–10 get 3, 11+ get 0. Tiers count per market (each market runs its own 1–5 / 6–10 sequence) and a carrier's tier locks at verification time, in verification order — not