Skip to content

Taking on new engagements

DOONKHAVTechnologies
Engineering studioIslamabad · Kotli AJK

Integrated systems, built to outlast the team that ships them.

DOONKHAV Technologies is a senior engineering studio. We design, ship and operate integrated platforms — from EDI & ERP to AI agents and mobile flagships.

ERP rollouts
18+

ERP rollouts

Practices
6

Practices

Founded
2019

Founded

Offices
2

Offices

SECP · CRO Islamabad · Reg. 0323301

Integrated SystemsDevOpsFull StackMobileERPAIIntegrated SystemsDevOpsFull StackMobileERPAI
Technology

The stack we staff for.

Not a logo wall. These are the technologies our practices are staffed to run in production — and the ones the engineers further down are named against.

Platform

06

Clusters, pipelines and the telemetry to run them.

  • Kubernetes
  • Terraform
  • AWS
  • GitHub Actions
  • Grafana
  • OpenTelemetry

Data

05

Streams, ledgers and the stores underneath them.

  • Kafka
  • PostgreSQL
  • Temporal
  • NATS
  • pgvector

Application

04

Typed services and the interfaces on top.

  • TypeScript
  • Next.js
  • Go
  • Python

Mobile

05

Native and offline-first, built for the field.

  • Swift
  • Kotlin
  • React Native
  • SQLite
  • Firebase

Enterprise

03

ERP go-lives, migrations and custom modules.

  • SAP B1
  • Odoo
  • HANA

Intelligence

02

Retrieval, agents and the evals that gate them.

  • Claude
  • LangGraph
How we work

Opinions, held out loud.

Six things we believe about building systems. They're the reason engagements go well, and occasionally the reason we turn one down.

01

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.

02

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.

03

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.

04

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.

05

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.

06

Operate what we build

We share the on-call. Nothing improves an architecture like being woken up by it.

The engineers

The people who write your code.

Full team
/03Desktop3yr

Muhammad Hussam

Desktop & Frontend Developer

  • Desktop packaging & releases
  • Front-end build
  • Print & peripherals
  • Electron
  • React
  • TypeScript
  • Vite
  • SQLite

Kotli AJK

/04Mobile3yr

Labiqa Islam

Flutter & Android Developer

  • Flutter apps
  • Android releases
  • Offline-tolerant clients
  • Flutter
  • Dart
  • Android
  • REST APIs
  • Firebase

Kotli AJK

/05Backend3yr

Qura tul Ain

Backend Developer

  • API design
  • Multi-tenant data model
  • Background jobs
  • NestJS
  • Node.js
  • PostgreSQL
  • Redis
  • TypeScript

Kotli AJK

/06Frontend2yr

Muhammad Hassan

Frontend Developer

  • Dashboards & consoles
  • Design system work
  • Accessibility
  • React
  • Next.js
  • TypeScript
  • Tailwind CSS

Kotli AJK

Engagement

Discovery, then working software.

Four phases. You can stop after any of them, and you keep everything produced up to that point.

  1. /01

    Discovery

    2–3 weeks

    Map the current estate, audit the data and integrations, and produce a costed plan with the risks written down.

  2. /02

    Architecture

    1–2 weeks

    Agree the target shape — event flows, data ownership, failure modes — before anyone opens an editor.

  3. /03

    Delivery

    Weekly releases

    A senior squad ships to production every week. You see working software, not status decks.

  4. /04

    Operate

    Ongoing

    Shared on-call, defined SLOs, written incident reviews — until your team is ready to take it, if that's the plan.

Let’s build

Have 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.