/journey — a delivery record, 2017 → now
Available for new work — now
You're probably here because something needs shipping — a SaaS, an ERP, a product that's stuck at 80%. Let me show you what I've shipped. Scroll: the whole career is below, with receipts.
Rajshahi, Bangladesh · Fully remote · replies within a day
the story behind these numbers, in six chapters
/journey/01-origin
2017–2018
Mid-2017, Rajshahi: I opened my first HTML file and the question flipped from “how does this work?” to “what should I build?” It never flipped back.
I taught myself HTML, CSS, and JavaScript first, then PHP — tutorials at night, broken layouts by day, the slow-internet kind of stubbornness that turns out to be the actual prerequisite for this job.
Eighteen months of that and I wasn't a professional yet — but I was dangerous enough to be hired. In November 2018, somebody did.
$ date
mid-2017, rajshahi
$ cat learning-path.txt
html → css → javascript → php
$ cat motivation.txt
build the thing > watch the thing
$ history | tail -1
git push # and never stopped/journey/02-first-builds
2018–2020
Satt IT, November 2018: my first job, and the place where “it works on my machine” stopped being acceptable — because co-operative societies, schools, and factories were running on my code.
In a year and a half I shipped more domains than some careers cover: a micro-loan system and a micro-finance platform for a savings & credit co-operative, a school management system, a shoe-factory ERP that ran everything from production recipes and stock to HR shifts and online sales, a pharma order-management system for field reps, an advocate management system, a mini accounting ERP (I learned double-entry bookkeeping to design it), and an MCQ learning platform for Bangladesh's job seekers.
Two of those — the micro-loan and advocate systems — were mine alone, from planning to delivery to maintenance. The rest taught me the other half of the job: guiding juniors, planning with a team, owning a piece of something bigger. I left in June 2020 and spent five months freelancing — custom builds, subscriptions, payment integrations — sharpening for what came next.
| id | project | mode | year |
|---|---|---|---|
| loan-mgmt | micro-loan system | solo build | 2018 |
| shoe-erp | factory → storefront ERP | team | 2019 |
| pharma-om | SR/MR order management | team | 2019 |
| advocate | advocate management | solo build | 2020 |
| acct-erp | mini accounting ERP | team | 2020 |
/journey/03-scale
2020–2024
Spondon IT, November 2020: products with thousands of buyers on CodeCanyon, where every module ships to an audience you'll never meet — and every shortcut becomes a support ticket.
I joined as a Laravel developer and worked across the Infix product family: InfixEdu (a school platform whose module list reads like a syllabus — homework, online exams, fees, Zoom, Jitsi, BigBlueButton, Google Meet, AI assistant, WhatsApp support, biometric attendance, LMS, certificates, a page builder — plus a ground-up restructure of its legacy codebase), InfixAdvocate, InfixBiz, InfixBio, InfixHub, an Asana-style project management app, and a license-verification system I rolled out across 10+ products to kill pirated copies.
And payments — the deep end of it. Razorpay, MercadoPago, Xendit, Khalti, PhonePe, CCAvenue, SSLCommerz, bKash, Mollie, Flutterwave, Braintree, Coinbase, AmazonPay, JazzCash and more — 20+ gateways, plus an SMS-gateway layer (Twilio, MSG91, Textlocal, Africa's Talking) users can configure themselves.
+ braintree · coinbase · phonepe · ccavenue · khalti · jazzcash · 8 more
ZATCA e-invoicing · thermal printers · cash drawers · zkteco biometric
/journey/checkpoint
Sound like the kind of systems you need built? You don't have to read the whole story first.
/journey/04-operations
2020–2026
Code that ships is half the story. Twenty-plus production servers taught me the other half.
Somebody has to own uptime. For 20+ production servers — clients' and the office's — that somebody was me: aaPanel, cPanel/WHM, Plesk, and self-managed VPS boxes running Nginx and Apache with Redis, on Ubuntu, with AWS Lambda and S3 where serverless made sense.
Load balancing, CI/CD pipelines with zero-downtime deploys, Cloudflare security rules with automated DDoS mitigation, n8n automations gluing the boring parts together — and a homeserver at my desk, because I genuinely like this stuff.
| host | role | stack | st |
|---|---|---|---|
| web-01..08 | client apps | aaPanel / cPanel | ● |
| web-09..14 | client apps | Plesk / WHM | ● |
| vps-01..05 | self-managed | Nginx · Redis | ● |
| lb-01 | load balancer | Nginx | ● |
| edge | security | Cloudflare | ● |
| home-01 | homeserver | because I like it | ● |
/journey/05-leadership
2024–2026
January 2024: promoted to TPM — and suddenly “my work” meant ten products, every architecture decision, and stepping back into the code whenever a delivery needed saving.
The portfolio I owned end-to-end: Amazcart (multivendor e-commerce), Infix LMS (instructor marketplace, quizzes, certificates), Aorabooks (multi-tenant cloud ERP, one database per tenant), AoraSchool (SaaS school platform with custom domains), Lawcham, Aorasoft, ALVcard (SaaS business-card and bio-link builder), Aorachat (WhatsApp Business management suite), Amaz (Amazon seller platform), and the HR management system — plus ZATCA compliance work and two Python services bridging ZKTeco biometric devices to InfixEdu and Aorabooks.
My job became translation: client language into engineering tickets, engineering constraints into client decisions, and panic into plans. I stayed in the code on purpose — reviews, architecture, and the occasional rescue commit — because I can't honestly own a date for a system I couldn't build. That chapter closed 31 May 2026.
/journey/06-ai-first
2025–now
Two real products — StampBD and Amaz — taken from zero to deployment with zero lines of hand-written code. I architected, reviewed, and shipped. AI typed.
StampBD is a multi-database SaaS for Bangladesh's stamp vendors — stock tracking, sales, government reporting. Amaz is a complete Amazon seller management platform — inventory, purchase orders, forecasting, returns, multi-warehouse, SP-API. Both built through a fully AI-directed workflow — GitHub Copilot and Claude — backed by nine years of engineering judgment. Every schema, every architecture call, every review gate was mine; the keystrokes weren't.
It's not hands-off. It's hands-on at a higher altitude — and it's how I deliver faster without lowering the bar. Right now I'm deepening the foundation, studying system design and AI engineering (Md Emran Hasan's course) — and as of June 2026, I'm available. If you want your product built this way — judged by an engineer, accelerated by AI — this is exactly what I do.
/projects — selected case studies
/projects/aorabooks
2023–2026
Technical Project Manager & Tech Lead
A modular Laravel ERP — POS, accounting, inventory, HR — where every tenant gets its own PostgreSQL database. Subdomain routing swaps the connection per request, stays isolated on long-lived Octane workers, and ships ZATCA e-invoicing.
/projects/infixedu
2020–2024
Laravel Developer → module lead
Homework, online exams, fees, four video-meeting stacks, AI assistant, WhatsApp support, biometric attendance, LMS, certificates, a page builder — and a ground-up restructure of the legacy codebase so all of it could keep shipping.
/projects/ai-built-apps
2025–2026
Director of the build — architect, reviewer, deployer
Two real products from empty repo to deployment with every line typed by AI — GitHub Copilot and Claude — and every decision made by me. StampBD: a multi-database SaaS for Bangladesh's stamp vendors. Amaz: a complete Amazon seller platform.
/journey/the-door
You've seen eight years of shipped work. If any of it looks like the problem on your desk, the next chapter is a conversation — tell me what needs shipping.