Skip to Content

A small, senior team

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.

Our story

Two platforms, two industries, one recurring root cause

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.

That's why our security hardening looks the same on both platforms even though we built it a year apart, independently: a recovery secret that lives in the database protects nothing from a database administrator. Both platforms keep it in the server config instead — a house pattern, not a coincidence.

MAFA & sister companies Aviation & Charter ERP
Companies MAFA · TechTrade24 KSA · TechTrade24 Germany · Eesint —
Odoo version Odoo 17 Odoo 18
Shape One codebase, four separate databases One instance, three companies
Industry Industrial engineering and B2B industrial trading Charter aviation and logistics
Countries Saudi Arabia · Germany · Pakistan UAE · Saudi Arabia · Bahrain
Team-built modules 55 24
Timeline Maintained since April 2025 Built since October 2025
Case studies 10 5
Team

Who builds this

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

Muhammad Yaseen

Software Consultant

Team lead

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

Credited on

Muhammad Umar

Software Engineer

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

Credited on

Haseeb Qureshi

Software Engineer

Leads attendance administration, CRM checklist and approval workflows, and flight-log accounting across both platforms.

Credited on

Where we work

Remote across Pakistan and Saudi Arabia

The systems we build run for companies in five countries.

Saudi Arabia Germany Pakistan United Arab Emirates Bahrain
What we believe

The house patterns, in short

One definition everyone calls

When several parts of a system each decide the same fact, they eventually disagree. We don't add a fourth opinion — we collapse the disagreement into one definition and make everything else read from it.

Keep the off switch out of the threat's reach

A recovery secret that lives in the database protects nothing from a database administrator. Security settings and recovery secrets live in the server config instead, on both platforms.

The model fills the form; a person approves it

AI earns its place where a person can check the output. Our models never write to the database directly: they draft, and someone signs off.

Enforce the rule where it can't be walked around

A rule that only lives on a screen can be bypassed by an import, a script or a busy person. We put it in the model: constraints, gates on stage changes, access checks on every data path.

All eight patterns, with the evidence

Something broken in production?

Give us the problem. We'll tell you what we see.

Tell us what's broken See the problems we've solved