Dashboards
- One definition per metric, used by every report.
- A first page that answers the question.
- Live ERP data, not a deck built by hand.
- Totals checked against SQL before release.
- Model documentation generated from the model itself.
Two ways I work, step by step. Tap a step to see what happens there, with a real example.
I start with the decision, not the chart. Who reads the report, what they decide, and which number tells them.
Leadership needed one view of the business. The first executive dashboard covers 12 business areas.
See the caseReports run on live ERP data, the company’s core business records. No exports pasted by hand.
Leadership had been reviewing sales data up to 5 days old. The report now runs on live ERP data.
See the caseOne shared data model holds the business definitions. Every report reads from it, so a metric means the same everywhere.
Every production report now uses one shared model. Standard metric names ended conflicting numbers between departments.
See the caseThe first page answers the question. Each figure shows where it stands against plan, and the detail sits behind it.
10+ Power BI dashboards and reports, from sales and invoicing to inventory and production.
Open the dashboardsBefore a report goes out, its totals are checked against SQL on the source data. Numbers get checked before they get published.
The monthly sales meeting report went from 3 to 4 days to under an hour, checks included.
See the caseThe report is there for a decision. It shows the gap, who owns it, and what to fix first.
The inventory risk analysis flagged 26% of raw material items as high risk, with ~25M AED of stock at risk, early enough to act.
See the caseWork starts from a normal request. No special format and no form to fill in.
The pricing engine starts from customer change requests on modified HVAC units, such as a bigger fan or a new casing.
See the caseAI reads the request and proposes what to change. It never does the fixed math.
A review found 37 contradictions in the method documents. The old AI handled about 70% of fixed calculations unreliably.
See the caseEvery calculation runs in Python. Automated tests check the rules each time the code changes.
The pricing engine now runs on 446 automated tests. It closed a ~97K AED material costing gap.
See the caseThe proposal goes to a person, who approves or rejects it. Anything a person must confirm is flagged.
AI use stays inside company security rules: approved connectors, tools that run locally, and a person signing off every change.
See the caseRecurring work runs on a schedule. Data pull, checks and the finished output, every time.
The monthly sales meeting report runs as a scheduled AI workflow. Prep went from 3 to 4 days to under an hour.
See the caseEach run ends in an Excel workbook anyone can audit. Anything a person must confirm is flagged in it.
Manual costing work became 10 AI automations. They pull live ERP data, build Excel workbooks anyone can audit, and flag anything a person must confirm.
See the caseFive working rebuilds of reports I build, with made-up data. Change the period, tap a figure, open an area.
Open the dashboardsThe AI automation flow on made-up data. AI reads a request, tested Python prices it, and you approve each change.
My own tool, written by AI coding agents that I directed and tested. Watch a made-up page become an Excel table, cell by cell.
Open the demo