Loading...
how I work
Embedded, not handed a ticket.
Forward deployed means I work the problem from inside it — close to the users and the data — and I'm measured on the outcome, not the output.
01
embed
Sit inside the real problem, the messy data, the actual users — not a spec doc.
02
prototype
Working software in days. Ship something real to react to, fast.
03
ship
Production-grade: auth, payments, infra, observability. Live, not a demo.
04
measure
Prove it moved a number — revenue, conversion, retention, time saved.
the path
Contractor → operator → forward deployed.
Foundation
Business Analytics at BUP
BBA at Bangladesh University of Professionals — where optimizing for conversion and revenue became second nature, not an afterthought.
Build
Client brands, real revenue
Shipped production e-commerce for Rupomoti and Qalbbox — payments, inventory, admin dashboards. Measured in sales lift, not story points.
Own
Co-founded eBrikkho
Went from contractor to operator — built the platform and the inventory system, and lived the messy reality of running it.
Now
Agents + self-hosted infra
Building agentic automation (n8n + Claude + Gemini) and self-hosting Ghost + n8n + OpenCLAW on a single Dokploy droplet. The FDE core.
Brands I've built & grown
Real platforms, real revenue — two as a co-founder.
the differentiator
I speak business, not just stack.
Most engineers stop at the code. A forward deployed engineer has to read the room, the market, and the P&L. My BBA at Bangladesh University of Professionals (Business Analytics) is why I optimize for conversion and revenue, not just clean diffs.
Bangladesh University of Professionals
BBA · Business Analytics · Faculty of Business Studies
currently pursuing
Have a problem that needs shipping?
I take a small number of build-and-ship engagements at a time. Free 30-minute call to see if I'm the right deploy.