← Case studies

Three business lines, one deal hub.

A California group works across property deals, financing and the legal side of both. We built one CRM hub for the whole pipeline, on the client's own domain, with each person seeing exactly their own book.

One hub
Three business lines in one system
Role-scoped
Coaches see only their own people
Client's own domain
Not a generic vendor URL

Book a call about your pipeline

Client · Private client — real estate group, California

The starting point

Several people working one pipeline, none of them seeing the same picture of it.

The client

A real estate group whose work spans three related businesses: property deals, financing, and the legal work that comes with both. Several people work the pipeline, and they don't all need — or want — the same view of it.

The problem

Deals were tracked across scattered tools, so nobody had one reliable picture of what was in flight. Adding a person meant adding another spreadsheet, and there was no way to give somebody their own slice of the pipeline without handing them everything.

What we built

One system, built to take the next project

A hub rather than a one-off, on infrastructure the client owns.

The deal hub

CRM core
Live

A single home for the group's deal flow, running on the client's own domain rather than a generic vendor URL.

Laravel + MySQLhosted and maintained by us

Role-scoped pipelines

access control
Live

Team-level users see everything; coaches see only the people assigned to them. Access is a property of the role, not a convention people have to remember.

see only your own bookno honour system

Self-serve account setup

onboarding
Live

New users set their own password through a reset flow, so no working credential is ever sent by email.

no passwords in inboxes

Transport security

hardening
Live

Forced HTTPS and session cookies that only travel over it — not a given when an app moves onto a new hostname.

HTTPS enforcedsecure session cookies

Continuous development, not a one-off

New projects hang off the same system.

This one is built as a hub deliberately. Work from any of the three business lines lands on the same foundation as it comes up, and the hostname is a single configuration value, so the whole thing can be rebranded without a rebuild.

The outcome

One place the deals live, under their own name.

What changed for the team

Everyone works one pipeline instead of a private spreadsheet, and each person sees exactly the slice of it they are meant to.

What changed for the group

The deal flow sits on a system and a domain they own, and the next project starts on that foundation rather than from scratch.

Laravel + MySQL CRM, hosted by us role-based access with per-user scoping self-serve password reset as the account path forced HTTPS with HSTS and secure cookies client-branded hostname in one config value

Similar problem?

Pipeline living in spreadsheets and inboxes?

Book a discovery call. We'll map what one system would need to hold before it's worth building.

Book a discovery call

No slides, no obligation.