← Market
Ferretería El PuenteFictional business · real pattern
Built by Yagrumo

Level 2 · Trunk · Modern data stackThe problem

Three systems. Three numbers. One very long meeting.One number. Every system agrees.

El Puente supplies contractors and hardware stores from Bayamón. Sales lives in the CRM, invoicing in the ERP, and finance keeps its own spreadsheet. Every Monday starts with the same fight: whose October revenue is right?

October revenue · 3 sources3 versions
ERPinvoicing
$1,240,000
Books revenue by ship date
    CRMsales
    $1,310,000
    Counts deals marked "won"
      Excelfinance
      $1,180,000
      Pasted by hand on the 3rd
        "Whose number is right?"Monday meeting · 0 min arguing
        October revenue · one definition
        $1,210,000

        Revenue is invoiced amount − credit memos, counted by invoice date, one customer per tax ID. Defined once. Every report reads it.

        Versions of revenue1was 3
        Duplicate customers merged04,812 records → 4,390 customers
        Monday meetingDecisionsinstead of 40 minutes of arguing

        The fix: bring every system into one place, match the customers, and define revenue once. Then every report reads the same number.

        What our team built

        1. Pulled every system into one place

          ERP, CRM and the finance spreadsheet land in one cloud data platform, refreshed on their own.

        2. Matched the customers

          One customer per tax ID. 4,812 records became 4,390 real customers.

        3. Defined revenue once

          Invoiced, net of credit memos, by invoice date. Every report and dashboard reads that one definition.

        Data Foundation · Level 2

        End the "whose number is right" meeting.

        This is you if you have reports, but nobody trusts them.

        Thirty minutes, one question your data should answer. If we can't help, we'll say so.