SaaS

A SaaS business run from Pakistan is an export business that never ships anything, and Pakistani law meets it in three places: the contract layer, the money layer, and the ownership layer. Most founders get the product right and improvise the other three. The improvisation works until the first enterprise customer, the first tax assessment, or the first financing — the three events that read the paper.

The contract layer

The subscription agreement is the entire commercial relationship, and it deserves better than a template written for Delaware. Pakistani law supports electronic contracting — the Electronic Transactions Ordinance 2002 gives electronic records and signatures legal effect — but the questions that decide disputes are practical ones. Was acceptance captured in a way you can prove two years later? Do the auto-renewal and price-change mechanics actually bind the customer, or merely surprise them? Does the limitation of liability hold together under the Contract Act 1872, with carve-outs that match what your insurer covers? For companies selling upmarket, the service level agreement and the data-processing addendum stop being formalities: enterprise and foreign customers arrive with their own paper, and the negotiation is won by the side that understands both legal systems in the room. We draft and negotiate that stack — terms of service, MSA, SLA, DPA, reseller and referral agreements — for enforcement, not decoration. Two clauses deserve particular attention in the Pakistani context. Suspension and termination mechanics need to work against a customer who stops paying but keeps using the product, because collection litigation here is slow and the practical remedy is the off switch, exercised in a contractually defensible way. And the governing-law and dispute clause should be chosen deliberately: arbitration with a workable seat often serves a cross-border SaaS relationship better than a foreign court judgment that then needs enforcement in Pakistan.

The money layer

Cross-border billing is where Pakistani SaaS companies carry the most silent risk. Export proceeds are regulated: the State Bank's Foreign Exchange Manual requires services-export receipts to be realized through authorized dealers within prescribed timelines, and as of mid-2026 exporters may retain a portion of proceeds in a special foreign-currency account to pay foreign vendors [RETENTION PERCENTAGE — TO BE VERIFIED BY REVIEWING LAWYER]. Routing revenue through a founder's personal account abroad, or leaving it parked in a payment processor indefinitely, breaks that framework — and simultaneously undermines the tax position, because the reduced final tax on IT and IT-enabled service exports under section 154A of the Income Tax Ordinance 2001 is tied to proceeds arriving through proper channels and to Pakistan Software Export Board registration [CONDITIONS — TO BE VERIFIED BY REVIEWING LAWYER]. Domestic revenue adds a provincial dimension: a Lahore-based provider answers to the Punjab Revenue Authority under the Punjab Sales Tax on Services Act 2012, and the classification of software services under the current schedule determines whether invoices should have carried tax the company never charged. The outbound direction matters too: paying for foreign infrastructure, tools, and advertising from Pakistan runs through the banks under State Bank instructions that have loosened for technology companies but still carry documentation requirements and limits [CURRENT LIMITS — TO BE VERIFIED BY REVIEWING LAWYER]. We set up the channel architecture — banking, PSEB, FBR, provincial registration — as one design, because each piece is a condition of the others.

The ownership layer

Investors in SaaS buy two assets: the revenue and the repository. The second is the one Pakistani founders most often fail to own. Copyright in code vests under the Copyright Ordinance 1962, and the default rules do not transfer a contractor's work to the client who paid for it — assignment must be in writing. A codebase assembled from freelancers, a departed technical co-founder, and an agency engagement is, without assignment deeds, a title problem wearing a product's clothes. The same discipline extends to the brand (trademark registration under the Trade Marks Ordinance 2001 before a copycat registers first) and to what leaves with employees, which is a matter of confidentiality and IP-assignment clauses signed at hiring, not argued at departure. Pakistani courts enforce confidentiality far more readily than they enforce non-competes, so the protection strategy leans on assignment, confidentiality, and access controls rather than on restraining former employees from working.

How we serve SaaS companies

Our SaaS work is a standing arrangement more often than a one-off project: the contract stack maintained as the product moves upmarket, the export-channel compliance reviewed against the State Bank's current circulars, assignments collected as the team grows, and the company kept diligence-ready between rounds. The regulatory inputs here — SBP circulars, the tax treatment of IT exports, provincial schedules, and the pending data-protection legislation — change with unusual frequency, and everything on this page is stated as of mid-2026. Where the current instrument matters to a decision, we check it that week, not that quarter.