tarek.in
Core Conceptual Layer

Problems I've Encountered

I don't build software because software is interesting. I build it because operational friction, broken incentive structures, and manual spreadsheets waste human potential.

01•Fleet & Logistics Operations
Status: system in progress

Fleet Operations & Trip Reconciliation

Field Context: Ground-level operational management across fleet leasing, driver administration, and shift handovers in Doha, Qatar—rooted in firsthand operational work across Al Arab Limousine and Keystar.

The Operational Friction

Working around real operations exposed recurring friction across drivers, vehicles, rental/lease arrangements, traffic fines, payments, contracts, attendance/workforce administration, operational records, and reconciliation.

The Ground Observation

You cannot fix fleet reconciliation with a complex multi-step web form. Drivers finish shifts exhausted; if intake takes more than 45 seconds on a phone, they will abandon it for WhatsApp voice notes.

The Architectural Response

A mobile-first 30-second shift closure protocol paired with back-office reconciliation rules that automatically flags anomalies between mileage and fuel expenses.

Build: OpsLedgerEssay: The problem with managing operations using Excel and WhatsAppLab: Cash Difference Calculator
02•Manpower & Administration
Status: operational prototype

Workforce Governance & Statutory Compliance

Field Context: Managing multi-national corporate workforces under Qatar Labor Law No. 14 of 2004 and statutory Wage Protection System (WPS) banking deadlines.

The Operational Friction

Manual tracking of residency renewals, statutory leave settlements, and Article 54 gratuity calculations on disconnected spreadsheets, resulting in emergency filings and compliance risk.

The Ground Observation

Companies do not fail compliance because HR lacks goodwill; they fail because spreadsheet cells have no proactive escalation ladder. A deadline 30 days away is invisible until it becomes an emergency.

The Architectural Response

Deterministic legal math calculators and proactive escalation queues (90/60/30 days) that enforce statutory validation before banking file submission.

Build: OpsFlow HR & ComplianceEssay: What building software taught me about running a companyLab: Qatar Labor Salary & Gratuity Calculator
03•Content & Web Systems
Status: system in progress

Editorial Lock-in & CMS Fragility

Field Context: Regional marketing and operational teams attempting to maintain custom websites without getting trapped in fragile plugin ecosystems or requiring full developer intervention for every text update.

The Operational Friction

Heavy legacy CMS architectures suffer from database bloat, security vulnerabilities, and brittle styling plugins. Meanwhile, pure developer headless setups isolate non-technical editors.

The Ground Observation

Writers do not want a complex developer dashboard with 40 raw database fields; they want a predictable, visual canvas that guarantees output without breaking site styling.

The Architectural Response

A decoupled, schema-validated block engine where authoring occurs on a lightweight canvas, validation is enforced via strict schemas, and delivery is static and edge-cached.

Build: PACKFOOAV CMSEssay: Why most small businesses don't need an ERP
04•Business Administration
Status: active research

Informal Tools & Operational Entropy

Field Context: Fast-growing businesses where daily operations rely almost entirely on shared Microsoft Excel sheets and group chat messaging.

The Operational Friction

Concurrent file edits overwriting data, zero audit history on deleted records, critical purchase orders buried in chat streams, and complete operational vulnerability when key coordinators leave.

The Ground Observation

Excel is the easiest tool to start with, but it becomes an invisible liability as transaction volume grows. You cannot fix it by banning Excel overnight; you replace the single most dangerous spreadsheet first.

The Architectural Response

Isolating high-risk operational spreadsheets (cash, inventory handoffs, fleet shifts) and translating them into focused, authenticated web tools with immutable audit trails.

Build: OpsLedgerBuild: FOOAV CommerceEssay: The problem with managing operations using Excel and WhatsAppLab: Invoice Delay Calculator
“I don't build software because software is interesting. I build it because problems are interesting.”