Projects, with the reasoning attached

Business Problem

Every sales invoice had to reach the FBR digital invoicing service in real time. Staff were re-keying invoices into a government portal, and timed-out submissions created duplicate-filing risk.

Solution

A validation and submission layer between the billing system and FBR: local schema checks, a durable queue with bounded retries, idempotent submissions and a reconciliation sweep.

Technology Stack

Business Outcome

Manual re-entry removed, duplicate filings eliminated, and month-end reconciliation reduced to a query against a complete audit log.

Business Problem

A B2B sales team spent most of its week researching prospects rather than selling. Generic automation tools solved volume by destroying personalisation.

Solution

An agent pipeline that researches, enriches and drafts outreach grounded in verified facts, then routes every draft to a human approval queue before sending.

Technology Stack

Business Outcome

Research-and-draft became a review step. Personalisation was preserved, and no message leaves the system without a named human approving it.

Business Problem

Operations ran on disconnected spreadsheets. Stock figures disagreed between locations, approvals happened over email, and management reporting took a full day to assemble.

Solution

A modular ERP configured around existing processes, rolled out one module at a time — inventory first, then sales and purchase, then assets and reporting.

Technology Stack

Business Outcome

One source of truth across locations, purchase approvals on record with value limits, and management reporting available on demand.

Business Problem

A working single-customer application could not be sold to the waiting pipeline: no tenant boundary, no billing, and onboarding that required a developer to deploy a copy.

Solution

Introduced enforced tenant isolation, migrated the existing customer without downtime, and added roles, subscription billing, usage metering and a support console.

Technology Stack

Business Outcome

Customers onboard themselves, billing runs automatically, and support works through an audited console instead of direct database access.

Business Problem

Clients needed apps on both iOS and Android but could not justify funding two native codebases and two release processes.

Solution

Cross-platform Flutter applications from a single codebase, with offline-first data sync, push notifications, analytics and full store submission handled end to end.

Technology Stack

Business Outcome

One team, one codebase and one release cycle covering both platforms, with apps usable in poor-connectivity conditions.

Business Problem

A casual game concept needed to reach players on both stores with a monetisation model that did not compromise the early experience.

Solution

A published casual puzzle game with level progression, rewarded video advertising and in-app purchases, plus event analytics to tune difficulty curves.

Technology Stack

Business Outcome

Shipped to both app stores with monetisation live and analytics feeding ongoing level-design decisions.