The question most ISP founders ask first is the wrong one: which license do I need. The more important question is whether the entity you have built is capable of satisfying PTA's application requirements at all, and if not, what needs to be in place before you apply.

This article focuses specifically on startup ISPs, defined here as entities that have not previously held a PTA license and are pursuing their first authorization. The requirements look different for a startup than for an established operator seeking an additional license, primarily because PTA's financial verification process has nothing historical to work from.

Choose the Right License First

Before anything else, the license category has to be right. Applying for the wrong license wastes time, money, and potentially flags your entity to PTA's attention for a structure that doesn't fit you. For a startup planning to provide broadband internet access in a single district, the district-level CVAS Internet license is the correct path. For a startup planning to own and operate its own last-mile infrastructure, the FLL is correct. For data services, VPN, or vehicle tracking, the CVAS Data license applies. The PTA License Finder on this site identifies the correct license in five questions.

Corporate Setup Requirements

PTA accepts applications from private limited companies, public limited companies, partnerships registered with the Registrar of Firms, and in some categories other legal entities. For a startup, a private limited company registered with SECP is the most common and most straightforward structure.

The SECP registration itself is a prerequisite: PTA requires a certified true copy of the Certificate of Incorporation not older than three months. This means the company must exist as a registered legal entity before you can apply.

The company's principal line of business in the Memorandum of Association must cover telecommunications or internet services. A company registered as a trading company or general services company cannot apply directly: the MOFA needs to reflect the telecom activity. If your company was incorporated with a different principal business object, a SECP amendment may be required before the PTA application is valid.

Active taxpayer registration with FBR is required for FLL applications and good practice for all applications. Register with FBR as part of the corporate setup process, not as a last step before application.

The Financial Minimum

There is no single published minimum capital figure for most license categories, but the financial verification process effectively sets one. For the district-level internet license, your bank statement must demonstrate funds covering the total project cost, the initial license fee, and the advance annual fee. The project cost is defined by your own cost statement, which you control, but which must be credible: a cost statement proposing to build a district network for PKR 500,000 in equipment will not satisfy PTA that you understand the financial commitment involved.

For FLL applications, the capital structure in the five-year financial projections must show at least 20% equity at all times. The bank statements must support the investment figure in the cost statement. For a startup with no operating history, personal bank statements of sponsor directors are accepted to supplement company bank statements where the company itself has not yet accumulated funds.

Practically, a startup should have enough capital to cover: the equipment described in the technical plan at realistic market prices, the licensing fees for the target region or district, 6-12 months of operating costs before subscriber revenue is at breakeven, and a reasonable contingency buffer. Founders who approach the application with exactly the minimum required in the bank account are in a fragile position if PTA asks questions about financial capacity.

Technical Plan as a Startup

The technical plan is where many startup applications fail. A plan that says "we will connect to an upstream provider and provide internet to subscribers" with no specifics is not adequate. PTA expects: a named upstream provider (you need to have identified and engaged with an upstream before applying, not just planned to), a specified last-mile technology with implementation detail, an equipment list with specific makes and models and corresponding costs, and a location for the NOC or PoP.

This means the technical work needs to happen before the application, not after approval. The approval is for a specific plan: you cannot get licensed on a vague proposal and then figure out the details after. For startups who need help designing a network that is both technically sound and application-ready, Network Design & Optimization covers the technical planning work.

CTDISR-2025 From Day One

The compliance undertaking in the application commits the startup to CTDISR-2025 compliance from the date of licensing. Most startups do not have the compliance infrastructure in place at licensing time and build it during the first year of operation. This is understood by PTA as a practical reality, but it means that a first CTDISR audit in year two will assess a startup that should have been building its compliance programme for 18-24 months. Starting earlier rather than later is the practical advice.

ISP Audit provides a baseline gap assessment that tells you where your compliance programme stands relative to all 104 CTDISR controls, which is the starting point for knowing what to build first. For operators who want support preparing the full licensing application and the compliance programme that follows, ISP Consulting & Advisory covers both.