About Commit Software

A small software house in Lahore. We build the systems that run shops, clinics and warehouses, and we keep them running after the invoice clears.

Built in Lahore. Reply within the same working day.

What we are for

Most businesses here do not need new software. They need the software they already have to stop losing stock, dropping payments and hiding numbers. We build for that case first, and we build the ambitious thing only once the boring thing is solid.

The long version: we want to be the people a business calls when the system that runs their money has to change. That means the work has to survive contact with a real counter, a patchy connection and a staff member who has never read a manual.

What working with us looks like

You talk to the person writing the code, not to an account manager
Every system we ship is running in a business you can call
The stack is boring where it has to be: PostgreSQL, Next.js, your own server if you want it
We say what a change will cost before we start it, and we say when a date slips

Where the depth is

Three things we have shipped enough times to be sure about. Everything outside this list, we will tell you we are learning.

AI and agent workflows

LangChain, LangGraph, RAG

Stateful agents with retries and human approval steps, sitting on top of the databases a business already keeps. We use them where ordinary code cannot follow the branching, and ordinary code everywhere else.

Cloud and data

Google Cloud, AWS HealthLake, Keepa

Hosting, data lakes and deploys. Health records on AWS HealthLake, marketplace pricing through Keepa, systems of record on PostgreSQL wherever the client wants them to live.

Product built at the counter

Polaris ERP and POS

No feature in Polaris started as a spec. Each one started as a problem someone hit while billing a customer, and the fix went back to that same counter the same week.

Polaris was built with its users in the room

It was never designed in isolation. These are the cases that arrived from production and changed the product. None of them appeared in a requirements document.

Case	What it means at the counter
Partial refunds	A return covering part of an order, paid back across more than one tender.
Spot payments	Cash handed over outside the billing cycle, posted against a running customer balance.
Multi-location stock	One stock position across branches, and the transfers that move goods between them.
Reporting on demand	The report an owner asks for at the counter, not the one we planned for.

Live businesses: 19
Permissions: 157
Built-in reports: 52

How the work runs

Six rules. Each one is something you can hold us to, and each one costs us something when we keep it.

01We fix the open bug before we add the next feature.
02Boring tools for the parts that must not fail. New ones only where they earn their place.
03Decisions come from what the system logs, not from what anyone remembers.
04Dates we can keep. When one slips you hear it from us first.
05If a client's problem is better solved by software we did not write, we say so.
06The code and the data belong to the client, on their infrastructure if they ask.

Tell us what your system keeps getting wrong.

Thirty minutes on a call. We look at how work moves through your business today and tell you where the time and the money go. If someone else is a better fit, we will point you at them.

Book a call