rishanto

Dhaka, Bangladesh

Odoo ERP Consultant & Business Systems Specialist

Your business already has a system. It's spreadsheets, WhatsApp, and someone's memory.

I replace it with one that holds.

Odoo implementation and business process analysis for teams that outgrew the workarounds.

View selected workLet's talk
ONE SYSTEMSPREADSHEETS · CHAT · MEMORY

02 / Selected work

Systems I’ve built, and businesses running better on them.

Also delivered

03 / The problem

Growth doesn’t create the mess. It makes the mess impossible to ignore.

Six, in the words owners actually use.

01 / 06 · Stock & inventory

“We track stock by hand, and the count is never right.”

Two counts, and neither one is the real one.

Today

  • Paper count
  • Till receipts
  • Second branch
  • Memory

After

  1. Scan in
  2. Live count
  3. Both branches
  4. One number

Odoo · Point of Sale + Inventory

Cafe Laundrette — UK, two branches

Read the case study

02 / 06 · Orders & approvals

“Orders and approvals live in WhatsApp, email, and someone's head.”

Nobody can say what shipped last week.

Today

  • WhatsApp
  • Email
  • Paper invoice
  • One person

After

  1. Order placed
  2. Docs verified
  3. Paid
  4. Delivered

Custom platform · Multi-tenant B2B

RondaShip

Read the case studyOpen the live product

03 / 06 · Reporting

“I can't see the numbers without asking someone to build a report.”

Decisions shouldn't wait for reports.

Today

  • Bookings tool
  • Finance sheet
  • Property list
  • Ask someone

After

  1. One record
  2. Live dashboard
  3. Decision today

Odoo · Dashboards + Accounting

Stayverz

Read the case study

04 / 06 · Manual re-entry

“The same information gets typed in three times a day.”

Typed twice is wrong twice.

Today

  • Intake note
  • Retype to system
  • Retype to invoice
  • Chase status

After

  1. Captured once
  2. Flows through
  3. Human confirms

Odoo · Workflow automation

Smart Laundry — UK

Read the case study

05 / 06 · Software that fits

“Our website or app is old, slow, or doesn't do what the business needs.”

The workaround quietly became the process.

Today

  • Phone the clinic
  • Office hours only
  • Diary on a desk

After

  1. Search
  2. See availability
  3. Book
  4. Confirmed

Custom product · Next.js + Supabase

BookMyDoc

Read the case studyOpen the live product

06 / 06 · Making it stick

“We bought the software. Nobody uses it.”

The money is spent. The old way came back.

Today

  • Requirements as prose
  • Built to guesswork
  • Argument at UAT

After

  1. Given / When / Then
  2. Tested against it
  3. Trained on site
  4. Used

Business analysis · Sales + HR

Tyre & Tube manufacturer

Read the case study

Every one of them was a workaround that used to work.

04 / How I work

How a project is run.

Written down. Built. Seen by you. Delivered.

DOCUMENTRequirements written as testable criteriaBUILDOne slice at a time, tested as it goesREVIEWYou see it working before it countsDELIVERSigned off, trained, handed overBRD · STOCK AND RECEIVING1.1 A sale at the counter reduces stock the moment it is taken.1.2 Both branches read one figure. No evening reconciliation.1.3 Receiving is a scan at the door, by whoever handles the box.2.1 A supplier submits dispatch details without an account.2.2 A status change notifies the owner, not a person chasing it.GIVENa sale is completed at the tillWHENthe order is closedTHENstock for that SKU falls by the quantity sold1export async function recordSale(sale) {2 const line = await stock.find(sale.sku);3 if (!line) throw new UnknownSku();4 5 await db.tx(async (tx) => {6 tx.decrement(line.id, sale.qty);7 tx.append("sale", sale);8 });9}a sale reduces stockan unknown SKU is rejectedboth branches report one figure3 PASSED · ON STAGINGYOUon stagingCOUNTERMenuTake an orderStock updates as you ring it up.Start a saleBranch two · Till 0112LIVE · THE TEAM WORKS HERE NOWToday's ordersCounter and onlineStock on handBoth branches, one figureInvoices dueRaised from the orderRunbookTraining deckUAT sign-offHandover notesEverything the team needs to run it without me in the room.

  1. 01 Document

    Requirements written as testable criteria

  2. 02 Build

    One slice at a time, tested as it goes

  3. 03 Review

    You see it working before it counts

  4. 04 Deliver

    Signed off, trained, handed over

05 / Expertise

Three kinds of work, one engagement.

ERP

Odoo, configured around the operation rather than the other way round.

  • Odoo implementation
  • Point of Sale
  • Inventory
  • Accounting
  • Purchase
  • HR
  • Multi-branch
  • Customisation

Business

The analysis that decides whether any of it lands.

  • Process mapping
  • Gap analysis
  • BRD
  • Given / When / Then
  • UAT
  • Workflow design
  • Training

Tech

What gets built when a configured product will not fit.

  • Python
  • JavaScript
  • TypeScript
  • React
  • Next.js
  • SQL
  • Supabase
  • APIs

The three overlap on every project. That overlap is the job.

Md Rafiqul Islam Shanto, Odoo ERP Consultant & Business Systems Specialist based in Dhaka, Bangladesh

06 / About

I work where business operations meet technology.

Rishanto, also known as Md Rafiqul Islam Shanto, is an Odoo ERP consultant and business analyst based in Dhaka, Bangladesh. He implements Odoo for growing businesses — inventory, point of sale, accounting, purchase and HR — and builds the custom software that sits around it.

I start with the problem, not the software: how the work runs today, where it stalls, and who is quietly holding it together.

Odoo ERP Consultant & Business Systems Specialist · Dhaka, Bangladesh

Insights

All insights

07 / Contact

Have a process that’s starting to break?

Tell me where the business is getting stuck.

rishanto.001@gmail.comLinkedIn