Lighthouse case study · LCS, since 1991
Low's Custom Stainless.
A third-generation custom stainless shop, founded by my dad in 1991, being repositioned from a local SoCal fabricator into a national custom-metal bar-top installer. NEWƎИ HQ's ops stack runs the place.
Founded
1991
Generation
3rd
Agents
20+ in production
Customers
245 dataset
What we shipped
- The data layer. QBO ingest pipeline — CSV exports fanned into per-customer folders, with revenue and AR reports generated automatically. 245 customers indexed.
- The map. A national partner-network map (US-Maps-style interactive) — public-facing, lays out who we install with and where. Lives as a static HTML page in the deliverables tree.
- The 50-blog content series.A complete content library with drafts, prompts, agents, and a social-media playbook. Voice locked to LCS's "Industrial Luxury" register — blue-collar craft elevated, not softened.
- The hero finish. M5 Oracle Sand — the brushed stainless finish that anchors the marketing site. Hero proof-of-craft, photographed in-shop.
- The agent stack. 20+ specialized Claude Code agents wired into a Windows ops dashboard (CommandGrid). AR pressure commander, estimate conversion officer, dormant-account raider, daily battle reporter, task-closure auditor — each in its own lane.
- The portal. Field Operations Portal — admin / crew-lead / crew workspaces. Next.js 14 + Supabase + Vercel + Resend + Backblaze B2. Currently in spec-reset with Devland at Media4U Riverside.
Why this matters for NEWƎИ HQ
LCS is the lighthouse case study. Every part of the NEWƎИ HQ install — agents, dashboards, content pipelines, data ingestion, multi-AI decision arenas — has been load-tested in a real shop with real customers and real AR pressure.
The pattern: build it for LCS first, then extract the install for anyone else. The work doesn't come out of a slide deck. It comes out of running the place.
The repositioning
LCS is moving from local SoCal fab shop (~30% margin) to a national custom-metal bar-top installer serving the Yard House / Darden tier. That move is what the portal unblocks. It's what the content series sells against. It's what the partner map shows. The map, the data, and the finish all point in the same direction.
What's public vs. what's not
The customer dataset, financial detail, and family photos stay private. What's here is the architecture and the public-facing deliverables. If you want a deeper look at the install or the agent stack, email me directly — happy to walk through it on a call.