Multi-Market Platform
Muskogee Services
Next.js 15 community hub + 24/7 contractor dispatch for Eastern Oklahoma — Firebase App Hosting, shared Firestore leads.
Lighthouse scores
Live URL audit · 2026-07-24
Lighthouse CLI against https://muskogee.services after idle-deferred HomeBelowFold (mobile emulation).
Challenge
Local directories are usually static brochure sites or bloated WordPress portals. We needed one product that could run events + vetted contractor routing, survive storm spikes, and fork cleanly into Tulsa and NWA without rewriting the stack each time.
Solution
Next.js 15 App Router on Firebase App Hosting with Firestore (`ml_leads`), Resend/SendGrid intake, Sentry, CSP middleware, GA4, and Playwright e2e. Market forks share the data model via a `market` field — Muskogee is the origin build.
Stack
Engineering highlights
Dispatch
24/7 storm / home-services lead routing for Muskogee County
Community
Events + civic resources alongside contractor marketplace UX
Data
Firestore ml_leads with market tagging for multi-city ops
Hardening
CSP middleware, Sentry, Playwright, App Hosting secrets
Results
- Live Lighthouse: Perf 92 · A11y 89 · Best Practices 100 · SEO 100 (post-optimization)
- LCP ~3.0s / FCP ~1.7s / TBT ~40ms after idle-deferred below-fold JS (was LCP ~5.2s)
- HomeBelowFold + festivals catalog gated behind requestIdleCallback; GA deferred post-load
- Same platform DNA ships Tulsa + NWA forks without a new agency rebuild
Want this level of engineering?
Agency-grade builds without agency overhead. You own the repo. You talk to the engineer.
Inquire