How to Vet a Software House in Lahore
Eight questions that separate a real software house in Lahore from a bench broker, the answers a good shop gives, and the red flags that end a meeting.
Search for a software house in Lahore and you'll find a few hundred candidates: genuine engineering companies, two-person studios wearing enterprise websites, and brokers who win projects and then rent freelancers to deliver them. From the outside they look identical. Same stock photography, same wall of client logos, same promise of dedicated teams. The differences surface months in, which is the expensive way to discover them. We're one of the companies that search returns, so read this with the bias declared. What follows are the eight questions we'd put to any shop in this city, ourselves included, and the answers a good one gives without flinching.
Who Builds, and Can You Meet Them
Question one: who exactly will work on our project, by name? A good shop answers with a named team before you sign, including profiles and backgrounds, and tells you plainly if one seat is still being filled. A broker answers with 'we'll assign resources from our pool once we kick off.' Resources is the tell. People get named; benches get resourced. Question two: can we interview those engineers ourselves, before contract? A company confident in its people sets up the call within days, because its engineers interviewing well is how it wins work. A shop that routes everything through a salesperson and keeps the engineers away from you is telling you either that they don't interview well or that they don't exist yet and will be recruited after your deposit clears. If one question on this list does the most work, it's this one.
The Paper That Protects You
Question three: who owns the code, and from when? The only acceptable answer is you, from the first commit, written into the contract as IP assignment rather than offered as a verbal assurance. Read the clause yourself. Some shops assign IP 'upon final payment,' which sounds reasonable and turns every future dispute into a hostage negotiation over your own product. Question four: what happens when we leave? Good shops answer in specifics: your repositories, your cloud accounts, your credentials, a documented handover inside a defined notice period, and no per-file ransom for documentation. Then ask how the last offboarding actually went, because every shop that's been around has one. A shop that has never offboarded a client gracefully will practice on you.
Proof Over Promises
Question five: will you do a paid trial sprint? Two weeks, a real ticket from your backlog, normal rates, and either side free to walk away afterward. Good shops agree quickly, because trial sprints convert; we win work this way, and buyers learn more in those two weeks than any portfolio can teach. A shop that insists on a six-month commitment before writing a line of code is pricing in your inability to leave. Question six: give us two references we can call without you on the line, ideally including one project that hit trouble. Everyone has a project that hit trouble. The reference who describes how the shop behaved when the timeline slipped is worth ten who say everything went great. Written case studies with numbers attached are the warm-up. The live phone call is the test.
Access and Rhythm
Question seven: do we get repository access from day one, in an organization account we control? Yes is the only answer. The code should live in your GitHub or GitLab organization from the first commit, with the shop's engineers as members you can remove, and the same ownership rule applies to cloud accounts, domains, and app store listings. We've taken over rescue projects where the client didn't control their own production database, and the previous shop knew precisely what that was worth when the exit conversation started. Question eight: what do we actually see every two weeks? The right answer is working software in a demo, not a status report with green ticks on it. Ask what happens when a sprint demo goes badly. Shops with real delivery discipline have a concrete answer, because it has happened to them. Shops that promise it never happens are describing a process they don't run.
Red Flags That End the Meeting Early
- A quote far below the others, which means QA, project management, or the second half of the build is unpriced
- Engineers the shop is reluctant to name, or named engineers whose tenure doesn't survive a LinkedIn check
- IP assignment conditional on final payment
- Repository access promised 'at handover' instead of day one
- A wall of client logos but no client willing to take your call
- Pressure toward a long commitment before any paid trial
- Every technical question answered by a salesperson while the engineers stay invisible
The Part About Lahore Specifically
The uncomfortable truth behind all of this: the engineering talent in Lahore is real and deep, and that's exactly why the brokers exist. The city produces enough strong engineers that renting them out profitably works as a business model, and the broker's website usually looks better than the engineer's. Your job isn't to find the single best software house in the city; no honest ranking of that exists. It's to find one whose answers survive contact with a contract read, two phone calls, and a two-week sprint. We've published who we are, who runs our teams, and how our engagements work on our about page, and every claim there is one these eight questions can test. We'd genuinely rather you test them. The shops that welcome this list are the ones that stay boring to work with for years, and boring, in this business, is the compliment worth paying for.
Have a project that needs this kind of thinking applied to it?