Working with a software house in Lahore
We build for clients in any market from Lahore, with overlap hours set to your time zone. This is what a buyer needs before signing us as a vendor: how we bill, how our hours meet yours, the paperwork we sign and who owns the code at the end.
Based in Lahore, PKT, UTC+5. Hours set to your time zone.
Engagement models
All of them run under the same published terms. Prices and dates go in the written scope, once we have seen the work.
Fixed-scope project
A defined system, built and handed over.
- How it is billed
- Against milestones agreed in writing before work begins. A change in scope is priced in writing before we pick it up.
- When it fits
- You know the problem and want a finished system. Each service page gives a typical length, from one to three weeks for design work to four to eight for a cloud migration.
- What you hold at the end
- The repository with its commit history, documentation another team could follow, and staff trained where they work.
- Who owns the code
- You do, once the invoice covering it is paid. From then on it is yours to run, change, or hand to another team.
Monthly retainer
A running system, kept current.
- How it is billed
- Monthly, sized to the system being looked after. The build contract never requires one.
- When it fits
- Something is already in production, ours or another team's, and needs monitoring, security updates, fixes and the next feature.
- What you hold at the end
- Every month's changes in your repository and in the documentation, so another team can pick the system up the day the retainer stops.
- Who owns the code
- You do. Each month's work is yours once that month's invoice is paid.
Team extension
Our engineers inside your team.
- How it is billed
- For the people working in your team, at rates and on a schedule set in the contract.
- When it fits
- You have engineers and a roadmap, and need people who have shipped LangChain, LangGraph or cloud work in production. The team is sized to the phase.
- What you hold at the end
- Commits in your repository from the first day, and a handover of whatever is finished when the work ends.
- Who owns the code
- You do. It is written into your repository as it is built, and the same payment terms apply as on every engagement.
Every engagement includes
Whichever model you choose, these come with it.
- Scope and price in writing before anyone writes production code
- A working demo at the end of every build week, which you drive yourself
- The source in your repository, with its commit history
- Documentation another team could follow: deployment guide, runbook and API reference
- Direct contact with the people writing the code, on WhatsApp and email
- An NDA before the first technical discussion, if you want one
The Lahore office
- Office days
- Monday to Friday
- In Lahore
- 9am to 6pm PKT
- In UTC
- 04:00 to 13:00 UTC
- With you
- overlap hours set to your time zone
- First reply
- same working day
The rhythm of a build
- A weekly demo call where you drive the build yourself
- Written progress notes with every week of the build
- A shared board showing every task, its owner and its state
- WhatsApp and email straight to the team, with no ticket queue
- The Gulf
- The Lahore office day already runs alongside the Gulf working day, from its first hour through most of the afternoon. Calls fit almost anywhere in it.
- The UK and Europe
- The Lahore day shares the whole UK morning. Overlap into your afternoon is agreed when the project begins, and written updates cover the rest of your day.
- The US
- Overlap hours sit inside your working day, the weekly demo is booked at a time that suits you, and written updates are waiting when you start.
- Anywhere else
- Tell us your working hours. The overlap is set to them and written into the contract before the build starts.
Contracts and paperwork
What procurement usually asks for, and where each item stands. Ask for anything marked on request by email; an NDA or a DPA comes back the same working day.
| Document | What it covers | Status |
|---|---|---|
| Terms of service | What it coversApply to every engagement, alongside the signed scope. Where the two disagree, the signed scope wins. Read the terms | StatusPublished |
| Statement of work | What it coversScope, milestones and price, agreed in writing before work begins. A change, and what it costs, goes in writing before we pick it up. | StatusEvery engagement |
| IP and code ownership | What it coversOwnership of the deliverables transfers to you when the invoice covering them is paid. After that the work is yours to run, change, or hand to another team. | StatusEvery engagement |
| Open-source components | What it coversUsed under their own licences, which travel with the components and carry whatever obligations their authors set. | StatusEvery engagement |
| Non-disclosure agreement | What it coversSigned before the first technical discussion. Ours or yours, whichever you prefer. | StatusOn request |
| Data processing agreement | What it coversFor work touching personal data, with us as processor and you as controller. | StatusOn request |
| Master services agreement | What it coversOur published terms are the default. If procurement works from its own master agreement, send it before you sign and we agree the clauses that need to change. | StatusOn request |
| Invoicing and payment | What it coversCurrency, payment schedule and milestones are set in the contract for each engagement. | StatusAgreed in the contract |
| Ending an engagement | What it coversEither side can end it with notice. Work completed up to that point stays payable, and we hand over what is finished. | StatusEvery engagement |
| Security questionnaire | What it coversWe fill in what we can evidence and mark the rest open. How we protect data | StatusOn request |
Read before the first call
Send us the vendor form.
Email over the supplier checklist or the security questionnaire. We fill in what we can evidence and mark the rest open, and if procurement wants a call with an engineer, they get one.
Book a call- First reply
- same working day
- Hours
- Set to your time zone
- Built in
- Lahore, Pakistan