ERP implementation & product development — Dhaka
Your business already has a system. It's spreadsheets, WhatsApp, and someone's memory.
I replace it with one that holds.
ERP implementations and custom software for teams that outgrew the workarounds.
01 / Where does it hurt?
Pick the one that sounds like your week.
Each one opens what I actually did about it, and the project where I did it.
“We track stock by hand, and the count is never right.”
Someone recounts every evening, and the branches still disagree.
Odoo · Point of Sale + Inventory“Orders and approvals live in WhatsApp, email, and someone's head.”
Nobody can say what shipped last week without asking three people.
Custom platform · Multi-tenant B2B“I can't see the numbers without asking someone to build a report.”
By the time the report arrives, the decision has already been made.
Odoo · Dashboards + Accounting“The same information gets typed in three times a day.”
Every re-entry is another chance to get it wrong.
Odoo · Workflow automation“Our website or app is old, slow, or doesn't do what the business needs.”
The team works around it, and customers notice.
Custom product · Next.js + Supabase“We bought the software. Nobody uses it.”
The team quietly went back to the old way.
Business analysis · Sales + HR
08 / Method
Every stage leaves you something you can hold.
Discover
Interview the people doing the work, not only the people describing it.
- Stakeholder notes
- Affinity map
- Gap analysis
Map
Draw the process as it actually runs, so everyone is arguing about the same picture.
- Process map
- Flow diagrams
- BRD
Configure & build
Vertical slices on staging every week — judged by using them, not by reading about them.
- Working system on staging
- Weekly demo
UAT
The client tests against the acceptance criteria written in the BRD.
- UAT script
- Sign-off sheet
Train
On site, on the real cases — including the ones that always go wrong.
- Training sessions
- Training deck
Handover
Documentation the team can follow once I'm no longer in the room.
- Runbook
- System documentation
Discovery output from a real engagement: user needs clustered into themes before a single screen was designed.
09 / Delivery
A twelve-week plan you can hold me to.
Taken from a real implementation plan, not a template. Each milestone carries a demo on live staging and a defined thing you sign.
Foundation
Weeks 1–2
Core features
Weeks 3–4
High-risk systems
Weeks 5–6
Operations
Week 7
Web sign-off
Week 8
Mobile
Weeks 9–12
Vertical slices, not layers
Every feature goes data → API → UI → tested, so progress is always demonstrable.
Weekly demos on live staging
You see the actual system every week. No status document standing in for working software.
Highest-risk work mid-project
Integrations and payments are scheduled in the middle, not left to the end where they sink a deadline.
Sign-off with a warranty
Each milestone is signed against its acceptance criteria and carries a 30-day defect warranty.
4
UK Odoo deployments
6
Odoo modules implemented
31
User stories restructured
12
Week delivery plan
3
Sided multi-tenant platform
10 / All work
Eight engagements, each one a problem before it was a project.
Stayverz
Property rental
Property, bookings, and finance lived in three tools that never agreed.
ERP implementation & automationCafe Laundrette
Retail & services — UK
Two branches, no shared view of stock or sales.
ERP implementationJak's Cafe
Hospitality — UK
An outdated point of sale the staff worked around instead of using.
ERP implementationSmart Laundry
Services — UK
Orders tracked by hand from intake all the way to delivery.
ERP implementation & automationTyre & Tube manufacturer
Manufacturing
31 user stories nobody could test against.
Business analysisGlobal Shipping & Logistics
Logistics
A live system the team had never been trained on.
Training & documentationRondaShip
B2B logistics
Importers were chasing suppliers, invoices, and shipments across WhatsApp, email, and paper.
Product developmentBookMyDoc
Healthcare
Patients phoned around to find out which doctor was free.
Product development
11 / Toolkit
What I reach for, and what it’s for.
- ERP implementation
- Odoo
- ERPNext
- Point of Sale
- Inventory
- Sales & Purchase
- Accounting
- Manufacturing
- HR
- Business analysis
- BRD authoring
- Given / When / Then
- Process mapping
- UAT scripts
- Flow diagrams
- Product development
- Next.js
- React
- TypeScript
- Tailwind CSS
- Supabase
- PostgreSQL
- Prisma
- Stripe
- Automation & AI
- OCR (Textract)
- Claude API
- WhatsApp Business API
- Webhooks
- REST integrations
- Delivery & enablement
- Vertical-slice delivery
- Staging demos
- On-site training
- Technical documentation
- Project management
12 / About
The unglamorous parts are the job.
I work at the intersection of business processes and software. On the implementation side I run Odoo projects across Sales, Purchase, Inventory, Manufacturing, Accounting, and HR — writing requirements with testable acceptance criteria, mapping workflows, configuring modules, and running end-user training on site.
On the product side, RondaShip — a multi-tenant B2B logistics platform for importers — plus BookMyDoc, a doctor appointment booking app. Between them I've worked through multi-tenant architecture, third-party integrations, AI and OCR features, and payment flows.
I care about the parts nobody photographs: clear documentation, flow diagrams a client can actually follow, and requirements written so nobody argues about scope three months later. Based in Dhaka, working with teams internationally.
13 / Contact
Tell me what’s breaking.
One sentence is enough to start. If it’s something I can’t help with, I’ll say so rather than sell you a project.