An engineering studio with opinions.
Founded in 2019. Two offices, six practices, and a strong preference for shipping working software over presenting plans to build it.
- Founded
- 2019FoundedIslamabad
- Practices
- 6PracticesOne studio
- ERP rollouts
- 18+ERP rolloutsSAP B1 & Odoo
- Offices
- 2OfficesIslamabad · Kotli AJK
DOONKHAV started in 2019 with a narrow bet: that most of what breaks in enterprise software is not the code, it’s the seams between systems. The ERP that doesn’t know what the warehouse knows. The bank feed that arrives in a format nobody owns. The overnight job that everyone has quietly built a workaround around.
We grew from that into six practices, but the bet hasn’t changed. Whether we’re running a SAP Business One go-live, building an offline-first field app or standing up a retrieval pipeline, the question is the same: what does this need to talk to, and what happens when that conversation fails?
We are deliberately senior. There is no bench of juniors behind a senior sales team — the people in your kickoff are the people writing your code, and they carry the pager for what they build. It makes us more expensive per head and considerably cheaper per outcome.
We also say no. Sometimes the honest result of a discovery is that the system shouldn’t be built, or shouldn’t be built yet. You keep the plan either way. That has cost us work. It has saved clients considerably more.
Opinions, held out loud.
Senior people, on the tools
The engineers in your kickoff are the engineers writing your code. We don't run a bench of juniors behind a senior sales team.
Integrated, not adjacent
A system that doesn't talk to the rest of your estate is a new silo. We design for the whole picture — ERP, banking, logistics, payments — from the first sketch.
Measured before it ships
Especially with AI. If we can't score it against a real evaluation set, it doesn't go to production. Confidence is not a metric.
Built to be handed over
Documentation is written as we go. Every engagement has an exit plan, because a partner you can't leave isn't a partner.
We say no
Sometimes the honest answer to a discovery is 'don't build this'. You keep the plan either way. It has cost us work and saved clients more.
Operate what we build
We share the on-call. Nothing improves an architecture like being woken up by it.
How we got here.
- 2019
DOONKHAV founded in Islamabad by Adnan Khattak.
- 2021
Integrated Systems practice formalised around EDI and event-driven work.
- 2022
ERP practice established with certified SAP Business One consultants.
- 2023
Kotli AJK branch opened; mobile practice moves offline-first by default.
- 2024
DevOps practice takes on shared on-call for client production estates.
- 2025
AI practice ships its first evals-first extraction pipelines.
Discovery, then working software.
- /01
Discovery
2–3 weeksMap the current estate, audit the data and integrations, and produce a costed plan with the risks written down.
- /02
Architecture
1–2 weeksAgree the target shape — event flows, data ownership, failure modes — before anyone opens an editor.
- /03
Delivery
Weekly releasesA senior squad ships to production every week. You see working software, not status decks.
- /04
Operate
OngoingShared on-call, defined SLOs, written incident reviews — until your team is ready to take it, if that's the plan.
Two offices.
Islamabad
House # 365A, Phase 4 c-2,Street-2, Ghouri Town,Islamabad, PakistanKotli AJK
2nd Floor, Galaxy Plaza,Shaheed Chowk, Kotli,Azad Kashmir, PakistanHave a system in mind? We'll engineer it.
Tell us what you’re trying to make work. If a discovery is the right next step we’ll say so — and if it isn’t, we’ll say that too.