Muhammad Yaseen
Software Consultant
Team lead
Leads the dashboard/reporting platform, security hardening, and infrastructure work across both deployments.
We support Odoo 16–19 · ERP rescue
If your ERP is fighting you, we've probably already fixed this.
When payroll, VAT or stock quietly disagree, it is usually because several parts of the system each keep their own version of the same fact. We are a small, senior team that gives that fact one definition.
- Free, no card
- 48-hour trial
- Link by email right away
2
Production Odoo platforms
7
Companies
5
Countries
For example: payroll that was off by half a day, every month. Read the fix
Placeholder · clip to record: Your logo becomes your theme
Odoo 16
Odoo 17 & 18
Odoo 19
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
Try it
How your trial works
Your own Odoo, in your company's colours, built while you watch.
-
Choose your apps
Pick the Odoo apps your business would use, from sales to payroll.
-
Tell us about your company
Your name, email and phone, so the system is set up in your company's name.
-
Add your logo
We take its colours and theme the whole system with them. No logo? Your initials work too.
-
Open your own system
It is built while you watch, and you are signed straight in.
Placeholder · screenshot pair to record: plain vs. themed Odoo
Questions
Is the trial free? Do I need a card?
It is free, and there is no payment step: we ask for your name, email and phone, nothing else.
How long does the trial last?
48 hours from the moment you activate it. When your system is ready you are signed straight in, and an email asks you to activate it within 3 hours to keep it.
When does the link arrive?
Straight away. Your personal link is emailed as soon as you send the form; a request that needs a closer look waits for a person on our team. Open it, pick your apps and add your logo, and you watch your system being built.
Which Odoo version does it run?
Odoo 18 Community, with the apps you pick and our own add-ons for them.
What happens to my data when it ends?
Sign-in closes, and your data is kept for 3 more days. Ask for an extension in that time and we open it again. After that the database is removed, and its backup is deleted after 30 days.
Can the trial become my production system?
The trial is a demo on our servers, built to be thrown away. If you want Odoo for real, talk to us: the apps you tried are the ones we build and support.
- Free, no card
- 48-hour trial
- Link by email right away
Start here
Does one of these sound familiar?
Click through to see exactly how we solved it, for who, and what changed afterward.
“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“We're manually retyping customer forms into the ERP all day — PDFs, scans, the occasional phone photo.”
See how we solved this“Filing our VAT return is a multi-day spreadsheet exercise, and one missed row means it's wrong.”
See how we solved this“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“Our biometric attendance data is technically 'real' but practically fiction — duplicate punches everywhere.”
See how we solved this“Changing a single letterhead logo on our invoices means opening a code editor and redeploying.”
See how we solved this“We need dashboards our team can actually build themselves, without a developer for every new chart.”
See how we solved this“We bill flight/project hours by hand, and disputes over 'how many hours was that really' happen constantly.”
See how we solved this“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“Sales reps burn hours on repetitive CRM admin — writing the same follow-up checklists over and over.”
See how we solved thisStuck on a version, or paying for one
Two more we hear often. Neither is written up as a case study yet, so this one goes straight to what we do about it.
We're stuck on an old Odoo version and scared to upgrade.
Our Enterprise licence costs keep rising.
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.
Two platforms
Two industries, different systems, the same discipline
Every case study on this site comes from one of two production systems we build and maintain.
Platform 01
MAFA & sister companies — Odoo 17
One Odoo 17 codebase, deployed independently four times for four separate companies, each its own database: MAFA (root company, industrial engineering, Jeddah), TechTrade24 KSA and TechTrade24 Germany (B2B industrial trading), and Eesint (Pakistan). Maintained continuously since April 2025.
Odoo 17
4 companies · 4 databases
Saudi Arabia · Germany · Pakistan
10 case studies
Platform 02
Aviation & Charter ERP — Odoo 18
A second Odoo 18 deployment for a Gulf-based charter aviation and logistics group, operating across the UAE, Saudi Arabia, and Bahrain as three companies under one multi-company instance. Built collaboratively across three engineers since October 2025.
Odoo 18
1 instance, 3 companies
UAE · Saudi Arabia · Bahrain
5 case studies
Selected work
Three of the fifteen
Each case study starts with the problem a client brought us and is credited to whoever led the work.
Payroll that was off by half a day, every month
Four parts of the system each decided what counted as a working day. We replaced them with one classifier everything reads from.
~28,000 LOC Read the case studyDashboards management builds itself, without seeing data it shouldn't
A drag-and-drop builder driven by typed, whitelisted conditions, so every viewer sees only what their access rights allow.
~20,800 LOC Read the case studyCustomer forms that read themselves, with a person signing off
A vision model extracts registration forms straight from incoming mail. It never writes to the database — an admin approves.
~4,350 LOC Read the case study
Team
Who builds this
A small, senior team — every case study is credited to whoever actually led it.
Muhammad Umar
Software Engineer
Leads attendance/payroll, finance and compliance engines, and AI-assisted integrations across both platforms.
Haseeb Qureshi
Software Engineer
Leads attendance administration, CRM checklist and approval workflows, and flight-log accounting across both platforms.
Journal
Field notes, not marketing
The case studies told the long way: the problem, the root cause, and the fix.
We read our own attendance engine twice, and the second pass corrected six things
Nine things a business believed about its overtime, allowance and payroll rules — checked line by line against the code, then checked again.
Read the noteThe payroll bug that wasn't arithmetic
Half a day, a handful of people, every month — and four parts of the system with four opinions.
Read the noteA recovery secret in the database protects nothing from a database administrator
Why our security features keep their off switch in the server config file.
Read the noteSomething broken in production?
Give us the problem. We'll tell you what we see.