Software development in Lahore, with the tradeoffs written down.

Lahore is one of three cities where Pakistan’s software industry concentrates, alongside Karachi and Islamabad, and it has the deepest university pipeline of the three. FAST NUCES, LUMS, UET, ITU and COMSATS push computer science cohorts into the same few square kilometres of Gulberg and Johar Town every summer. That’s the supply side. Large, young, and most of the reason a Lahore engineering hour costs a fraction of a London one.

The demand side is the part buyers never see. Systems Limited, NETSOL Technologies, Contour Software and Arbisoft aren’t our clients and aren’t our partners. They’re who we compete with when we hire, and they set the floor. An engineer who has carried a production system through two years of incidents has offers in this city. They’re not on a marketplace waiting to be discovered at nine dollars an hour, and a studio quoting that rate is describing somebody else.

Now the part a location page isn’t supposed to say. The graduate pipeline is enormous. The pool of engineers who have owned a system in production is small. Most of the local industry is organised around that gap: seats billed by the month, teams assembled from whoever sits on the bench, one lead engineer split across three accounts. That’s why so much offshore work arrives technically complete and operationally naive, with no indexes, no error states and no evaluation set.

We’re built the other way round, and the tradeoff cuts against us as often as for us. We can’t put fourteen people on your project next Monday. If you need fourteen next Monday, hire a firm that can, and there are good ones here. Where we draw that line is set out on the page about how this studio works.

Payments first, because that’s where these engagements stall. Stripe does not support businesses incorporated in Pakistan. Neither does PayPal. That’s a fact about the country rather than a signal about the studio. What works is a SWIFT wire in USD, Wise, or Payoneer. Wire fees run higher than people expect and clearing takes two to four working days, so write payment terms as business days from invoice.

On our side the proceeds arrive through a bank under State Bank of Pakistan rules, and exporters registered with the Pakistan Software Export Board may retain a share of earnings in a foreign currency account. That share has been revised more than once, so it is not worth quoting a figure here. What matters to your finance team is that the money is documented, banked, and traceable end to end.

US clients normally want a W-8BEN-E on file before the first payment. UK and EU clients generally treat a services invoice from Pakistan as outside the scope of domestic VAT under the business-to-business place-of-supply rules, and account for it their own side. Both are your accountant’s questions rather than ours, and a studio that answers them with confidence instead of paperwork should worry you.

IP assignment is the clause to read twice. Ask for present-tense assignment on creation rather than a promise to assign on final payment, and check that it names the whole surface: source, designs, prompts, evaluation sets, infrastructure configuration, and repository history. Then ask what happens if the work stops in week three. Our answer is structural rather than contractual. The repository is yours from the first commit and every deployment runs in a cloud account you own, so there’s no handover event to negotiate. A vendor that stages work in its own repository and migrates it at the end is telling you where the leverage sits. Pay in milestones tied to something you can open, never to percentage complete, and treat resistance to that shape as information.