Skip to Content
ERP & business software — Odoo, Python, OWL

If your ERP is fighting you, we've probably already fixed this.

ThinkDevs is a small, senior engineering team that builds and rescues production Odoo ERP systems. Payroll that's quietly wrong, compliance that's one audit away from a problem, data entry nobody has time for — these are the same handful of failure patterns wherever they show up. We've solved them across two live platforms, five company instances, five countries.

2 Odoo platforms delivered
5 Live company instances
7 Operating companies served
5 Countries
Odoo 17 & 18 Python PostgreSQL OWL QWeb reports XlsxWriter ZKTeco · PyZK WhatsApp Graph API Twilio Groq · OpenAI-compatible APIs ZATCA UBL 2.1 Central Bank of the UAE rates PDF.js Gridstack Passlib Azure DevOps
Start here

Does one of these sound familiar?

Click through to see exactly how we solved it, for who, and what changed afterward.

MAFA Group · Odoo 17

“Payroll is off by half a day for a few people, every single month, and nobody can figure out why.”

See how we solved this
MAFA Group · Odoo 17

“We're manually retyping customer forms into the ERP all day — PDFs, scans, the occasional phone photo.”

See how we solved this
MAFA Group · Odoo 17

“Filing our VAT return is a multi-day spreadsheet exercise, and one missed row means it's wrong.”

See how we solved this
MAFA Group · Odoo 17

“Finance has a depreciation schedule and operations has a spreadsheet of who's holding what — and they don't agree.”

See how we solved this
MAFA Group · Odoo 17

“Our biometric attendance data is technically 'real' but practically fiction — duplicate punches everywhere.”

See how we solved this
MAFA Group · Odoo 17

“Changing a single letterhead logo on our invoices means opening a code editor and redeploying.”

See how we solved this
Aviation ERP · Odoo 18

“We need dashboards our team can actually build themselves, without a developer for every new chart.”

See how we solved this
Aviation ERP · Odoo 18

“We bill flight/project hours by hand, and disputes over 'how many hours was that really' happen constantly.”

See how we solved this
MAFA Group · Odoo 17

“Our database backups exist, but nobody's confident they'd actually work in an emergency — or that the admin console is even locked down.”

See how we solved this
Aviation ERP · Odoo 18

“Sales reps burn hours on repetitive CRM admin — writing the same follow-up checklists over and over.”

See how we solved this
Approach

Why the same fixes keep showing up

Two different Odoo versions, two different industries, three engineers moving between them — and the same root cause kept recurring: several parts of a system quietly disagreeing about the same fact. Payroll disagreeing with attendance. Tax logic scattered instead of centralized. A security secret stored somewhere a bad actor could also reach.

Our answer is never a fourth opinion. It's collapsing the disagreement into one definition everyone calls.

01

Start from the symptom

Every case study here opens with the sentence a client actually brought us. "Payroll is off by half a day" is a better starting point than a requirements document.

02

Find where the system disagrees with itself

The bug is rarely the arithmetic. It's usually several parts of the system quietly holding different opinions about the same fact.

03

Collapse it into one definition

One day classifier. One tax category. One stock move. Everything else reads from it, so there is nothing left to drift.

04

Guard it, then prove it

Put the rule where it can't be walked around, keep the off switch out of reach, and back it with tests — the payroll classifier shipped with 19.

Team

Who builds this

A small, senior team — every case study is credited to whoever actually led it.

Muhammad Umar

ERP Engineer

Leads attendance/payroll, finance and compliance engines, and AI-assisted integrations across both platforms.

Muhammad Yaseen

ERP Engineer

Leads the dashboard/reporting platform, security hardening, and infrastructure work across both deployments.

Haseeb Qureshi

ERP Engineer

Leads CRM and pipeline automation, including the AI-assisted checklist and activity generation tooling.

Facing something similar?

Tell us what's broken. Chances are we've already fixed a version of it.