DEV Community: Hafsa Motiwala

Reverse-Engineering Messy Databases: My End-to-End Data Audits Across 17,000+ Relational Schema Logs

Hafsa Motiwala — Wed, 23 Sep 2026 11:49:47 +0000

From Raw Logs to Business Strategy: How I Taught Myself Data Engineering & Analytics

I didn’t take the traditional path into data. Over the past 12 months, I bypassed the university lecture halls to teach myself relational database architecture, pipeline optimization, and growth analytics by diving straight into raw datasets.

I look at data through an engineering and business lens. Instead of building passive charts that just look pretty, I query transaction logs and user event data to find hidden operational friction, map out user behavior patterns, and isolate exactly where systems are dropping value. I build end-to-end data systems: raw SQL schemas, data sanitization scripts, interactive Power BI dashboards, and single-page executive reports.

Below are the architectural breakdowns, technical challenges, and business impact metrics of the four core data infrastructure projects I have engineered from scratch.

Project 1: StockPulse — Multi-Regional Supply Chain Audit

Technical Stack: MySQL (Mathematical Window Functions), Power BI, Advanced Excel
GitHub Codebase & Dashboard Layout: [LINK]

The Operational Bottleneck

Horizon Marketplace faced shrinking profit margins from slow-moving warehouse stock, while simultaneous supplier shipping delays caused high-demand items to go out of stock on our mobile application. Traditional procurement tracking models failed because they relied on simple historical averages, which immediately miscalculate when data hits high seasonal sales volatility spikes.

The Technical Implementation

Audited 17,646 operational and sales ledger transactions using MySQL window functions to calculate cumulative revenue contributions per SKU.
Coded a predictive restocking matrix script utilizing sales volatility standard deviations and rolling manufacturer lead timelines.
Formulated dynamic Safety Stock buffers and programmed automated database Reorder Point triggers to flag supplier order alerts before shelves hit zero.

The Business Impact Metrics

ABC inventory segmentation proved that exactly 23 Class A items drive 80% of total marketplace revenue, showing that the remaining catalog space was tying up critical capital.
Quantified a hidden revenue bleed of $63,897.26 caused by a single high-demand apparel product sitting entirely out of stock for 42 days due to upstream logistics bottlenecks.
Transitioned a multi-regional operation from manual, time-intensive spreadsheets to an automated, predictive data framework.

Project 2: FunnelOpt — HabitArcade B2C Telemetry Audit

Technical Stack: MySQL (Session Overrides), Funnel Analysis, User Lifecycle Mapping
GitHub Codebase & Database Logs: [LINK]

The Operational Bottleneck

A B2C application tracking engine suffered from severe data execution drops where product behavioral logs completely failed to map user activation patterns. The relational schema dropped child telemetry records because they were importing prior to the absolute database finalization of the parent account index logs.

The Technical Implementation

Audited full-funnel growth logs across 6 independent acquisition pipelines to analyze customer conversion latency and drop-offs.
Structured specific MySQL session overrides to temporarily bypass structural foreign key constraints.
Forced clean data synchronization across child records to completely restore parent-child index synchronization without corrupting historical system logs.

The Business Impact Metrics

Isolated a systemic “Streak-Breaking Crash Tax” where application sync errors wiped 30-day user milestones, triggering immediate 1-star reviews and an active 6% to 7% monthly subscriber bleed.
Exposed an “Inverted Value Curve” revealing that high-value annual checkout tiers underperformed monthly subscriptions due to silent gateway billing processor failures blocking top-priced subscription cash settlement.

Project 3: LeakStop — Olist B2B Revenue Leakage & Onboarding Audit

Technical Stack: MySQL (Schema Engineering), Power BI, Business Intelligence
GitHub Codebase & Analytical Readme: [LINK]

The Operational Bottleneck

Cross-vendor data duplication across digital marketplace ledgers was heavily skewing gross reporting metrics. Standard relational database joins double-counted total transactions when a customer order spanned multiple independent business vendors in a single checkout loop.

The Technical Implementation

Engineered robust MySQL ingestion and data sanitization scripts to enforce strict primary key integrity down to individual item vectors, removing all reporting bias.
Processed user account lifecycles to calculate onboarding completion latency across specific B2B verticals.
Programmed a real-time database filter to flag slipping user accounts precisely on Day 16 of transaction inactivity.

The Business Impact Metrics

Isolated an annual revenue leakage of R$ 600,600 (approximately $119,175 USD) stemming from 462 merchant accounts that stalled out completely during the onboarding phase.
Exposed an invisible latency anomaly where logistically complex business profiles stalled for an average of 112 days in domain routing and tax mapping phases.
Implemented a Day 16 early-warning database filter to flag at-risk accounts before they reached a terminal, zero-recovery retention cliff.

Project 4: CohortPace — SaaS Behavioral Retention Engine

Technical Stack: MySQL (Subqueries & Relational Joins), Cohort Modeling, Data Analytics
GitHub Codebase & Technical Report: [LINK]

The Operational Bottleneck

Initial application dashboards focused blindly on feature exploration depth, which completely masked why healthy-looking active user profiles were suddenly canceling subscriptions. Traditional active-user metrics acted as a lagging indicator, hiding friction because churning accounts remain active inside broken workflows right up to their exit timelines.

The Technical Implementation

Modeled simulated user cohort transactions across multi-platform SaaS behavioral profiles to analyze the core drivers of long-term Monthly Recurring Revenue (MRR).
Used advanced MySQL subqueries and relational joins to reconstruct full lifecycle interaction sequences.
Mapped user interaction velocity trends against subscription lifecycles to isolate clear behavioral churn signatures.

The Business Impact Metrics

Proved through data pacing sending signals that churning users maintain consistent interaction velocity close to their exit date, showing churn is driven by late-stage workflow utility limits rather than gradual disengagement.
Demonstrated that long-term user monetization is strictly dependent on habit formation within a single core workflow rather than broad, multi-feature platform exploration.

Conclusion: Turning Code Into Business Strategy

I don’t need a playbook to get started, and I don’t need a manager to hand me a static checklist. I find the question, ingest the data, clean the schemas, model the answer, and present the metric that directly protects business margins.

I am actively available for analytical remote contract roles, standalone data audits, and freelance pipeline optimization. If your startup is scaling fast and dealing with messy relational pipelines, let’s connect and fix your backend infrastructure loops.

** Interactive Portfolio Hub:** [LINK]
** Contact:** motiwala603@gmail.com
** Connect with me:** [LinkedIn]

Open to analyst remote roles across product, growth, and business analytics. Based in Pakistan, available worldwide.

The SaaS Behavior Modeling Project (CohortPace Focus)

Hafsa Motiwala — Thu, 02 Jul 2026 11:21:17 +0000

Traditional active-user metrics are dangerously misleading lagging indicators. A user can maintain a high interaction volume, click around your SaaS platform daily, and look completely healthy on a standard dashboard—right up until the exact morning they cancel their subscription.

To study the core drivers of long-term Monthly Recurring Revenue (MRR), I modeled simulated user cohort transactions across multi-platform SaaS behavioral profiles using advanced MySQL subqueries and relational joins.

The data velocity pacing revealed a fascinating structural pattern:

Churning users do not gradually disengage. They maintain consistent interaction volume close to their exit date because their churn is driven by sudden utility failure within a single core workflow, not a slow loss of interest.
Long-term monetization is strictly dependent on habit formation within one single core workflow, rather than broad, multi-feature platform exploration.

If you want to protect your retention metrics, you have to stop optimizing your codebase for feature breadth and start tracking the depth of a single habit loop.

I have published the full behavioral interaction sequences, technical reports, and code schemas on my interactive portfolio hub: lucky-bit-036.notion.site/HAFSA-5fd489cedd70459ca0237c36a168f30a

Does your product team measure feature adoption by breadth or by workflow velocity? Let's talk in the comments.

The B2B Marketplace Project (LeakStop Focus)

Hafsa Motiwala — Thu, 02 Jul 2026 11:19:54 +0000

When a customer orders multiple items from independent business vendors in a single checkout, standard relational database joins will double-count your macro transaction metrics. If you don't catch this early, your gross revenue reporting becomes a complete work of fiction.

To secure data integrity across a complex digital marketplace database, I engineered robust MySQL ingestion and sanitization scripts from scratch to strictly enforce primary key constraints down to individual item vectors, removing all reporting bias.

Cleaning the backend logs uncovered a massive onboarding latency anomaly:

I isolated an annual revenue leakage of R$ 600,600 (~$119,175 USD) coming from 462 accounts that stalled completely during implementation phases.
Tracing merchant lifecycles showed that complex profiles were stalling for an average of 112 days in domain routing and tax mapping before making an initial value transaction.

To stop this attrition, I programmed a real-time database filter to flag slipping profiles precisely on Day 16 of transaction inactivity, allowing customer success teams to intervene before the account hit a terminal retention cliff.

The full data validation script architecture and my interactive Power BI layouts are public: lucky-bit-036.notion.site/HAFSA-5fd489cedd70459ca0237c36a168f30a

How does your data architecture enforce primary key integrity when handling multi-vendor checkout streams?

The B2C Funnel Project (FunnelOpt Focus)

Hafsa Motiwala — Thu, 02 Jul 2026 11:16:05 +0000

During a full-funnel telemetry audit tracking user logs across 6 independent acquisition pipelines, I hit a massive engineering bottleneck: severe data ingestion drops.

The relational database schema was dropping child telemetry records because they were importing prior to the absolute finalization of the parent account index logs. In simple terms, the platform tried to record user app activity before it verified the user had actually completed account registration.

To prevent extensive system downtime, I avoided rewriting the core ingestion script. Instead, I structured specific MySQL session overrides to temporarily bypass the foreign key constraints. This safely forced data synchronization across the child records and completely restored parent-child index synchronization without corrupting any historical server logs.

Cleaning this data pipeline exposed two critical product liabilities:

Isolated a systemic "Streak-Breaking Crash Tax" where application crashes wiped 30-day user milestones, triggering an active 6% to 7% monthly subscriber bleed.
Exposed an "Inverted Value Curve" where silent checkout gateway billing processor failures were dropping high-value annual subscription tiers.

I've documented the full technical case study and query scripts on my hub: lucky-bit-036.notion.site/HAFSA-5fd489cedd70459ca0237c36a168f30a

What is the messiest data synchronization error you have had to debug in production?

The Supply Chain Project (StockPulse Focus)

Hafsa Motiwala — Thu, 02 Jul 2026 11:13:17 +0000

Most inventory tracking systems fail because they rely on simple historical averages. The second a business hits seasonal sales volatility, those baseline averages miscalculate, leaving capital frozen in slow warehouse stock while top-selling items sit completely empty on the client app.

To fix this operational double-edged sword, I ran an independent database audit on 17,646 raw ledger transactions for a multi-regional digital marketplace.

My backend implementation:

Formulated MySQL window functions across a 50-item catalog to run cumulative revenue models, proving just 23 Class A items drive 80% of total revenue.
Quantified a hidden $63,897.26 revenue bleed caused by a single high-demand product sitting out of stock for 42 days due to external logistics bottlenecks.
Coded a predictive restocking matrix script utilizing sales volatility standard deviations and rolling manufacturer lead times to automate dynamic Reorder Points (ROP) inside the database.

The full repository code and interactive Power BI layout are completely open-source. Check out my full data breakdown on my project hub: lucky-bit-036.notion.site/HAFSA-5fd489cedd70459ca0237c36a168f30a

How does your team handle tracking demand volatility inside relational database schemas? Let's discuss in the comments.