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.