Dawloom is a software agency based in Pakistan. About ten of us work here, led by founder and CEO Haleem Khan, who has been building software for more than ten years.
We’ve shipped as this team since 2021, but the habits go back further. Before Dawloom existed as a company, most of us were already working on freelance platforms, going back to 2016, the kind where every finished job ends in a public review you can’t edit or delete afterward. That history shaped how we work more than any mission statement could. You can’t talk your way out of a bad outcome when the review is sitting there for anyone to read.
That record is still public. We’ve delivered 525 orders on Fiverr, rated 4.9 from 335 reviews, and we’re rated 5.0 from 156 reviews on Freelancer.com. Check both for yourself on our reviews page instead of taking our word for it. We work in English, Urdu, and Pashto.
Two clients are public by name so far: FurnitureAxis and Elviepr TV. What’s on those pages is what we actually built for them, not a summary written to sound better than the work.
Why we write this down and publish it
Most agencies keep their internal process private, or save it for a pitch deck once you’re already talking to sales. We put ours on the website instead, in this handbook, because clients deserve to see how we work before they hire us. If you can read exactly how we scope a project and run one once it starts before signing anything, you’re making a better decision. So are we: it filters out the projects that were never going to fit.
The values
None of this is aspirational language. It’s what we’ve already been doing, and what shows up everywhere else on this site.
Every claim is checkable
If we say something about our track record, it links to the source, whether that’s a review count, a named client, or a number. We don’t invent testimonials, and we don’t round a number up to make it sound better. Call it the no-slop rule if you want a name for it: nothing here exists just to sound impressive.
You talk to the builder
There’s no account manager relaying your questions to an engineer sitting somewhere else. When you ask something, the person who knows the answer is the person you’re talking to.
Fixed prices, written scope
Before any code gets written, you get a number and a document describing exactly what that number buys. Changes to scope get priced the same way, in writing, before we start on them.
Built for handover
The repositories and the hosting accounts are yours from day one. There’s no separate handover step at the end, because how a project gets set up never depended on keeping us around afterward.
No when no is right
If your problem is better solved by an existing template, a smaller build, or a cheaper approach than the biggest thing we could bill for, that’s what we’ll tell you. We’d rather say that up front than take on a project we don’t think you need.
Read the rest of the handbook to see these in practice: how we price work, how projects actually run, who’s on the team, and the tools we build with. If you’d rather just talk to someone, get in touch.