Multi-Market Platform
Tulsa Cloud
Tulsa metro fork of the leads platform — Next.js 15, Firebase, Resend, and storm-ready home-services dispatch.
Lighthouse scores
Live URL audit ·
- Performance
- 97
- Accessibility
- 90
- Best Practices
- 92
- SEO
- 100
Lighthouse CLI against https://tulsa.cloud (mobile emulation).
Challenge
Agencies usually clone a template per city and drift. Tulsa needed the Muskogee product DNA with metro-specific messaging, analytics, and email domain — without a second bespoke codebase.
Solution
Dedicated Next.js 15 app under `muskogee-leads/Tulsa-OK` on Firebase App Hosting backend `tulsa-leads`. Shared Firestore collection with `market: 'tulsa'`, Resend via `hello@tulsa.cloud`, Sentry, and GA4 stream Tulsa_Leads.
Stack
- Next.js 15
- React
- TypeScript
- Tailwind CSS
- Firebase App Hosting
- Firestore
- Resend
- Sentry
- Playwright
- GA4
Engineering highlights
Market fork
Tulsa-OK app + tulsa-leads App Hosting backend
Resend on hello@tulsa.cloud with Secret Manager grant
Analytics
Dedicated GA4 stream Tulsa_Leads
Dispatch
Storm + insurance-friendly home services across Tulsa County
Results
- Live Lighthouse: Perf 97 · A11y 90 · Best Practices 92 · SEO 100
- LCP ~2.3s mobile lab with CLS 0
- Independent App Hosting backend + secrets — blast radius isolated from Muskogee
- Market-tagged leads keep Tulsa ops separate while sharing platform code patterns
