Abdul Basit Khan

Case study 01

Retail BI Dashboard

Internal dashboards turned scattered retail operations into clearer business visibility.

In production

Internal business dashboard

Client
Premium retail / F&B business
Duration
Production internal system
Role
Solo end-to-end product engineer

How it works

DATA INPUTSD1D2D3D4D5Sales · spend · stockRole InputsStaff-owned dataBI BackendOperational data modelSalesPurchasesAdsReportsOwner DashboardKPIs · ReportsPostgreSQLOperational factsVISIBILITYRevenueProcurementAd SpendMarginsDaily visibilitySales · purchases · spendOwner-facing business viewSYSTEM TOPOLOGY · RETAIL BI DASHBOARD

Situation

The business needed cleaner operational visibility across sales, purchases, procurement, ad spend, revenue, and day-to-day performance. Owners needed a dashboard they could trust without chasing scattered files or manual updates.

Build

I built a role-based internal BI platform where employees enter the data they own and owners review structured dashboards. PostgreSQL acts as the system of record for the operational facts behind the reports.

Result

The system is used internally and gives stakeholders a clearer view of the business. It shows practical BI, operational data capture, and business-facing product engineering.

Key decisions

  • Designed the data model around how the business reviews operations, not around a generic dashboard template.
  • Kept data entry role-based so responsibility stays close to the people who own each number.
  • Used PostgreSQL as the source of truth for operational facts instead of spreadsheet-only reporting.
  • Focused on owner-facing clarity while keeping staff workflows direct and repeatable.

Tools used

Next.jsReactTypeScriptPostgreSQLTailwindDocker

My role

DiscoveryData modelFrontendBackendDashboardsDeployment

Exploring something similar?

Reach out on LinkedIn, Telegram, or book a short call to discuss the workflow and whether software is the right move.