Build log

Client portal CRM

This backend CRM was delivered alongside the website it manages. It gives the owner one place to work leads, inquiry history, and site health. The CRM is shown with sample data.

This is a studio build, designed and built in-house, shown with sample data.

What had to exist

A website generates activity, and somebody has to work that activity. This build's premise: the management surface ships with the site instead of being bolted on later. Leads, inquiry history, and site health, one place, delivered together with the website they describe.

That connection defined the build. The website and its management view shipped as one piece of work.

Leads, history, and site health in one owner view. Sample data.
Leads, history, and site health in one owner view. Sample data.

The overview decision

The dashboard puts lead counts, an inquiry trend chart, recent leads, and site health checks on one screen, matching the three jobs the portal exists for: work the leads, read the history, check the site.

No module sprawl, no separate admin for each concern. The owner opens one view and knows the state of the operation.

The customer-history decision

The customers view groups every website inquiry by person, so history stays attached to the human behind it instead of scattering across a flat inbox.

Status filters cover new, quoted, won, and lost. Four states, mapped to how a lead actually moves, giving every record a visible working state inside the customer view.

The site-health decision

Site health checks live inside the same backend as the leads and inquiries. The reasoning is simple: if the site goes down, the leads stop, so the site's operating state belongs next to the activity it produces, not in a separate tool the owner never opens.

What shipped

The studio delivered the website and its backend CRM together. The CRM includes:

  • Leads and recent-lead information
  • Inquiry history grouped by person
  • Lead-status filters for new, quoted, won, and lost
  • Site health checks

The published portal runs on sample data and makes no claim about client activity or measured results.

See the website capability for structure, responsive pages, connected lead capture, launch checks, and written handoff. Work with us to send the audience, intended use, existing material, and technical requirements in writing.