Esano — Lead-Management SaaS for Automobile Dealers (Canada)

Esano operates a lead-management SaaS purpose-built for automobile dealers in Canada. The market is specific — Canadian regulatory environment, bilingual customers, dealer groups with multiple rooftops, lead sources ranging from manufacturer-driven campaigns to local marketing — and generic CRM tools don't match the operating reality of an auto dealership cleanly.

The Challenges Esano Faced

• Lead capture across heterogeneous channels. Leads come from OEM portals, third-party listing sites, the dealer's own website, walk-ins, and direct phone. Each source has its own data shape. The platform had to normalise all of them into one record type.
• Routing logic that fits the dealership. A lead for a specific model + a specific trim + a specific budget needs to route to the right salesperson within the right rooftop. That logic varies per dealer group and has to be configurable, not hard-coded.
• Multi-tenant with per-tenant data isolation. Each dealership sees only its own pipeline. Sharing a single platform across many dealer groups required strong isolation guarantees.
• Canada-specific regional needs. Bilingual support (English / French), provincial regulatory differences, Canadian currency and tax handling. The platform had to be regionally correct, not a US tool with a flag flipped.

How Linescripts Built the Solution

Multi-tenant SaaS architecture

A single platform serving many dealer groups, each in its own tenant with its own data, users, configuration, and dashboards. Tenant isolation is enforced at the data layer, not assumed at the application layer.

Channel-agnostic lead capture

Lead intake from OEM portals, third-party sources, the dealership's website, phone, and walk-ins, all normalised into one lead record type. Each lead carries its source attribution so reporting on channel performance is honest.

Configurable routing engine

Routing logic — by model, trim, geography, budget, time of day, salesperson availability — is configurable per dealer group rather than hard-coded. New routing rules go live without engineering work.

Dealer-facing dashboards

Dashboards built for the audiences inside the dealership: sales managers see pipeline and conversion; salespeople see their own assigned leads; ownership sees aggregate performance across rooftops. Each role gets the views and actions that match its decisions.

Canada-first regional configuration

Bilingual UI (English / French), Canadian currency, provincial differences in regulation, Canadian-specific data handling. Built as a Canadian platform from the ground up, not a US platform with bolted-on localisation.

What Changed for Esano

• One platform serves many dealer groups cleanly. Tenant isolation, per-tenant configuration, per-tenant dashboards.
• Every lead lands in one queue, regardless of channel. Source attribution is preserved; reporting on channel ROI is honest.
• Routing is configurable, not hard-coded. Dealer groups change their own routing rules without an engineering ticket.
• Bilingual + Canada-correct out of the gate. No localisation retrofits.

Closing

The architectural decision that made the platform scale was treating the dealer group as a first-class tenant — own data, own users, own configuration, own dashboards — rather than as a customer of a shared multi-tenant database with permissions on top. The isolation makes onboarding new dealer groups a configuration exercise instead of an engineering project.