About

We build the unglamorous software.

Not the app that gets written about. The system a company opens at nine in the morning and cannot work without — where being wrong does not produce an error message, it produces a wrong invoice, a missed order, or somebody paid short.

What we are

A software house in Islamabad, working with clients three continents apart.

We started from systems work rather than from websites, and it shows in how we build. Our background is government land records, payment platforms moving real money, payroll, healthcare claims and HR — places where an audit trail is not a feature request and “we will fix it next release” is not an acceptable sentence.

That is now a team covering web, desktop, iOS and Android, with the databases, cloud, documentation and support around them. The things we will not do are at the bottom of this page, and that list matters more than the one above it.

Where we areIslamabad, Pakistan · UTC+5. Nine hours ahead of US Eastern, four ahead of London, one behind Dubai.
Who we work withDistributors, clinics, agencies and traders in Pakistan; manufacturers, recruiters and operators in the Gulf and the United States.
How we chargeFixed price against a written scope, or monthly for support. Prices are published rather than quoted on request.
What you ownThe code, the repository, the accounts and the documentation — on final payment, in writing. The domain is in your name from day one.
How long we have been at itFour years of delivered systems behind the company, and the platforms are still running.

How we think about it

Four things we believe, that change what we build.

The happy path is the easy part

Anybody can make software work when everything goes right. The work is in what happens when a payment gateway accepts money and fails to tell you, when two systems disagree, when the connection drops after the money moved. That is where the value is and where the bugs live.

Records are proved, not stored

For anything that matters — a land title, a payment, a payslip, a custody chain — the question is never only what it says now. It is who changed it, when, and what it said before. So we append rather than overwrite, and derive current state instead of hoping it is right.

A system nobody can operate is a liability

Documentation is part of the product, not an apology at handover. If you decide to move to another developer you should be able to hand them a folder and have them start. That it also protects you from us is the point.

Deployment is part of the design

On a system people use every day, downtime is a design flaw rather than an inconvenience. The release process, the backups and the answer to “who finds out at 9pm” get decided at the start, not after the first outage.

The other list

What we will not do.

Any firm can list what it does. This is the list that actually tells you something.

Build on spec“Make it first, we will pay if we like it” — no. We will build a single page for a small fee instead, so the risk is real but small on both sides.
Learn at your expenseIf a project needs a skill we do not have, we say so and point you elsewhere. The alternative is you funding our education and finding out later.
Hold your domain or accountsRegistered in your name from day one. A developer who holds your domain has leverage over you, and that is not a relationship we want.
Cut the rate to win the jobWe will make the package smaller, which is honest. Cutting the rate just means cutting the care somewhere you cannot see.
Promise an SEO rankingNobody can, and anyone who does is either guessing or lying. We will tell you what we can actually control.
Put up a photograph of somebody who does not work hereStock team photos are the easiest thing in the world to buy, and the fastest way to tell a careful buyer not to trust the rest of the page.

If any of that sounded like the firm you wanted, talk to us.

And if it sounded like the opposite, that is useful too — we would both rather find out now than in week six.

Start a conversation