Contractor site with a sales-ops backend

What it is

A full rebuild of a restoration contractor's web presence, prepared as a working demo. The public side carries the brand: services, projects, a blog with real articles, FAQs and a quote request flow.

Behind it is the admin the office actually needs. Leads arrive with their channel and status tracked. The blog runs 19 authored posts. Services, portfolio and FAQ content are managed without touching code.

Under the hood

• Lead pipeline: every lead records its source channel and status, with a filterable management view.
• Dashboard: stat tiles for new, weekly, open and won leads, with leads broken down by channel and status.
• Content system: a 19-post blog with authors, dates and publish state, plus services, portfolio and FAQ management.
• Settings and stats: site content, contact details and daily rollups in the same panel.
• Laravel with a hand-rolled admin over SQLite, 51 Blade views, in three complete iterations.

Why three iterations

The first build answered the wrong question. A contractor does not need a brochure, they need to know which calls became contracts and which ads produced them. The third version is built around that question. The site is just the front door.

Stack