← LeasingLama
CRM Project

LeasingLama · HubSpot Support

How Metawork built a HubSpot system for a German vehicle leasing marketplace — inquiry-to-ticket conversion, contact enrichment, PDF proposals, vendor coordination. ~679 hours delivered.

Duration 31 months
Tasks 280

What was built

Area Description
Ticket integration Multi-source inquiry ingestion from web forms, email forwarding and lead platforms (Leasingarkt, Emil Frey, GoLeasy)
Company & contact resolution CDSystem API lookups for vehicle data, fuzzy contact matching, company deduplication, multi-location handling
Ticket enrichment Vehicle ref ID, make and model, UTM parameters, lead source and vendor assignment extracted automatically
PDF generation Leasingangebot generated with branding, leasing terms, vehicle details and customer data
Vendor coordination Lead distribution to vendor partners with notifications, status tracking and multi-company handling
Email management Incoming mail parsing, attachment extraction, bounce detection and thread management
Pipeline management Separate deal pipelines per source with stage automation

LeasingLama's HubSpot Setup project is a long-running, production-heavy engagement managing a complex multi-source lead integration and processing system. The core system ingests vehicle lease inquiries from multiple channels (web forms, email forwarding, API integrations from Leasingarkt, Emil Frey, GoLeasy), converts them to HubSpot tickets, and enriches them with company/contact data before routing to the appropriate sales team or vendor.

The system's complexity stems from the multi-stakeholder nature: LeasingLama manages vendors (Volvo, Subaru, and others) each with their own sales processes, multiple lead sources with different data formats and quality levels, and complex routing logic. Work includes integrating the CDSystem API to look up vehicle information and availability, implementing fuzzy contact matching to deduplicate customer records, and handling multi-location company structures. The system generates lease proposal PDFs with branding and leasing terms, processes email attachments (customer self-disclosure forms), and coordinates lead flow between sales teams.

The project has involved 280+ production issues and enhancements, ranging from data quality fixes (incorrect pipeline assignments, missing owners, malformed contact data) to feature work (new lead source integration, email parsing improvements, pipeline reorganization). Recent activity includes migrating workflows to HubSpot's native automation, filtering out duplicate lead sources, and improving contact phone number handling.

Project stats: 280 tasks, complex multi-source integration, 7+ years of production support, extensive troubleshooting and optimization, ~388h

Tech stack

Technology Role
HubSpot CRM, tickets, deals, pipelines, customer email
Make.com Lead ingestion, enrichment, PDF generation, vendor routing

Recently touched

  • 2024-12-19 [W50] Support Done
  • 2024-12-10 [W49] Support Done
  • 2024-12-03 [W48] Support Done
  • 2024-11-26 [W47] Support Done
  • 2024-11-18 [W46] Support Done

Other projects in this case study

  • Ongoing Support

    The maintenance stream behind the LeasingLama integration: a production system taking enquiries from several external portals every day, where a change on any one of those sources shows up as a…

    What we built

    • Health monitoring
    • Break recovery
    • Data quality
    • Configuration updates
    Read case study
  • NBS Support 2025

    The 2025 rebuild of the NBS lead layer, run as a handover rather than a delivery: every source scenario rewritten as v2, and the client's own automation specialist taken through it until the system…

    What we built

    • v2 lead scenarios
    • Alerting
    • Parallel deployment
    • Break handling
    • Training
    Read case study
  • NBS Support

    NBS is the arm of the LeasingLama group that handles leasing enquiries for the Emil Frey brands and their partner portals. Every channel arrives in a different shape, by email or by form, and each…

    What we built

    • Source pipelines
    • Lead parsing
    • Vehicle data
    • Documents
    • Owner routing
    • Data load
    Read case study