Approach

Weeks to an answer, then real work.

Our process is short on purpose. A pre-seed company cannot afford a three-month diligence cycle, and there is rarely enough data to justify one.

Sourcing

Where we expect to find companies.

Almost none of it comes from inbound decks, and we would rather say so than pretend otherwise.

Out of the services firms

The strongest product teams here often start inside an agency that built the same thing five times for five clients.

University and community

NUST, FAST, LUMS, GIKI and the developer communities around them. We would rather meet people a year before they incorporate.

Returning operators

Senior engineers and product people coming back after a decade abroad, with a network on both sides.

Open source and public work

People who ship in public are the easiest to evaluate honestly, because the work is already visible.

Founder referral

The founders we back, including those we passed on, are our most credible source of the next one.

Second-time founders

People whose first company did not work, who now know precisely which part broke.

An empty office lounge
Services firms
Students working in a university hall
Campus
A city office tower seen from below
Returning operators
Circuitry standing in for shared infrastructure
Public work
A group of founders working side by side
Founder referral
A notebook and pen left open on a desk
Second attempts
Decision path

How the answer gets made.

Five steps, typically two to four weeks from first meeting to a decision.

  1. Screen against the thesis

    Hard-currency buyer, unfair build advantage, reachable customer, narrow wedge, workable structure.

  2. Two working sessions

    One on the product and what it actually does. One on the customer and how they were found.

  3. Use it, and talk to users

    We use the product ourselves and speak to people paying for it before generalising from a deck.

  4. A written view

    What we believe, what we are underwriting, and what would falsify it. Founders receive this whether the answer is yes or no.

  5. Answer and terms

    Lead, co-lead or pass. Standard instruments, no unusual rights, no exclusivity while we think.

A working session in progress around a whiteboard
Two sessions Product first, then the customer
A person working at a technical workstation
We use it Before we generalise from a deck
After the cheque

The first year, concretely.

Support is the most over-promised word in venture. Here is the specific list we intend to be judged on.

Legal paperwork and figures laid out on a desk

Structure and compliance

Offshore topco with a Pakistan subsidiary, intercompany agreement, IP assignment, founder vesting, an option pool sized for two years of hiring, and clean State Bank documentation for inbound capital.

A payment dashboard open on a laptop

Getting paid from abroad

Merchant of record or direct processing, invoicing that a foreign finance team will accept, and contracts that survive a procurement review.

An outbound sales conversation across a table

First ten customers

A worked outbound list, positioning that does not apologise for where the team sits, and pricing anchored to the buyer's alternative rather than to local salaries.

A new team member at work in the office

Hiring the first five

Compensation bands that hold against foreign remote offers, equity people believe in, and honest conversation about which roles cannot be junior.

Start the two weeks.

Send us the product and one customer story. That is enough for a first working session.