Each one starts with a plain-language summary of what it does and why a business should care, then goes into the design decision, the trade-off I accepted and the measurable result. Read the first section or the whole thing - both work.
Reads the news in Bangla and English all day, removes the duplicates, and answers questions about what it found.
Retail software with a full online store, a till that keeps selling when the internet drops, and one stock truth for both.
Hajj and Umrah agencies launch a branded booking platform on their own subdomain — with seat integrity, branch RBAC and finance in BDT and SAR.
Software that runs a whole gym chain - memberships, billing, staff, door access, and AI that reads ID cards at the front desk.
The software a salon runs on — online booking, chair-side operations, payroll and an AI assistant guests can actually talk to.
Sends hundreds of thousands of emails without wrecking the sender's reputation - and lets you manage contacts by talking to it.
Removed a hardware purchase from the sales conversation - old fingerprint terminals now work with a cloud product.
A public Python package other developers install - and the release process that makes it safe to depend on.
Attendance and payroll engines that replaced manual timesheets, messaging infrastructure across email, push, SMS and WhatsApp, payment and sign-in integrations, and the monolith-to-services migration I am leading now. I can walk through the architecture and the outcomes of any of it in a conversation, without the client-identifying detail.