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.
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.