QuickSafa

Why this is on the site

Client work shows what I build. This shows what happens after launch, which is the part most portfolios never have to answer for.

QuickSafa is mine. I built it, I run it, and businesses close their month on it. That means I carry the parts of software that only appear once real people depend on it — a migration that cannot lose a row, a tax deadline that does not move, a bug reported at 9pm on the last day of the quarter. Those are the same conditions your product will live in.

The problem it solves

Corrugated box manufacturers in Pakistan run on spreadsheets and general-purpose accounting tools that do not understand their work. Paper roll inventory, multi-stage production, board grades and per-customer box pricing have no home in a generic chart of accounts, so they live in parallel spreadsheets that have to be reconciled by hand.

On top of that sits FBR — Pakistan's tax authority — which requires invoices to be submitted electronically. Tools that do not integrate with it leave a manual step at the exact point where a mistake is expensive.

What it does

An end-to-end ERP: chart of accounts, inventory, sales, purchasing, production, payroll and reporting, wired to a live FBR integration so an invoice reaches the government system as part of issuing it rather than as a separate chore.

• FBR e-invoicing — invoices submitted in real time, compliance handled as a side effect of normal work.
• Production tracking — paper rolls through board production, conversion and finished goods, across every stage.
• Pricing engine — per-customer tiers by board grade, size and order quantity.
• Roles and permissions — accountants, production managers, sales staff and owners each see their own system.
• Financial reporting — profit and loss, balance sheet, trial balance and GST returns generated on demand.

What running it taught me

Most of what I insist on in client work came from here. Weekly demos, because the features I was sure about were not always the ones users needed. Documentation written for whoever runs it next, because I have been the person reading my own notes eighteen months later. And no lock-in, because I have watched what it does to a business to be trapped inside software it cannot leave.