Vesper CRM: A Multi Tenant Portal Built To Scale

The Problem

Vesper had grown by acquisition. Each of its eleven regional offices had kept its own way of tracking leads, quoting work and invoicing, which meant head office could not answer basic questions like how many open quotes existed company wide. Quotes took three days because they required a phone call to whoever held the relevant spreadsheet.

What We Did

• Spent two weeks in the offices watching how work actually flowed, not how the org chart said it did
• Designed a multi tenant model where each office keeps its own data and head office sees the aggregate
• Built quoting as a guided flow with regional pricing rules baked in, so quotes stopped needing a phone call
• Migrated nine spreadsheet formats into one schema with a reconciliation report signed off per office
• Rolled out office by office over six weeks rather than all at once
• Trained a champion in each office instead of running one central session nobody remembered

The hardest part of this project was not the code. It was the two weeks of watching before any code was written.

Why It Worked

Internal tools fail when they are designed from the org chart rather than from the work. The two weeks of observation surfaced three pricing exceptions that nobody had documented and which would have made the system unusable in two regions. Finding those before the build was the difference between adoption and quiet abandonment.

The staged rollout was equally deliberate. By the time the last office went live, four offices had already been running for a month and their champions handled most of the questions themselves.