A dev shop is a company that builds software for other businesses for a fee: websites, apps, internal tools, integrations, whole products. It sells its developers' time and judgement, and the client owns what gets built. In the UK, Pakistan, India and much of Europe the same kind of firm is usually called a software house.
That's the dictionary answer. The useful part is what it means in practice: how a dev shop differs from an agency, a studio or a consultancy, how it gets paid, and why the same two or three problems turn up once one grows past a handful of people. This guide covers all of that, whether you're hiring a dev shop or running one.
Dev shop meaning, in one paragraph
"Shop" is the old sense of a workshop: a place where things are made to order. A dev shop takes a client's idea, brief or spec and turns it into working software. It doesn't sell a product of its own (or if it does, that's a side line). Its inventory is hours: the team's available time this month, and how much of it is sold. That single fact explains most of what's good and hard about the business.
Some people use "dev shop" a little dismissively, to mean a firm that writes code to order without questioning the brief. Plenty of dev shops do far more than that, and plenty proudly use the name. Treat it as a neutral description of the business model.
Dev shop vs software house vs agency vs studio vs consultancy
The labels overlap and firms pick whichever sounds right to their clients. Here is how they're usually used.
| Label | Usually means | Typically hired for | Usual pricing |
|---|---|---|---|
| Dev shop | Engineering-led firm building to order | Building an app, MVP or integration to a brief | Hourly/daily T&M, fixed price, dedicated team |
| Software house | Same model; the common term in the UK, Pakistan, India and Europe | Custom software, outsourced development, long-running product work | Same as above; dedicated-team monthly fees are common |
| Software / digital agency | Strategy, design and engineering sold together | An outcome: a launch, a redesign, a product that converts | Fixed price per project, retainers |
| Studio | Smaller, design- or product-led, often selective about work | Product design and build, brand-heavy work | Fixed price or weekly rate |
| Consultancy | Advice first, sometimes with delivery | Architecture, audits, technical due diligence, fractional CTO | Day rate or retainer |
Two practical tests separate them better than the label. First, who writes the spec? If the client mostly does, it's working like a dev shop. If the firm does, through discovery and design, it's working like an agency. Second, what does the client think they're buying: hours of capable people, or a result?
Neither is better. A founder with a clear spec and a technical co-founder may want exactly a dev shop: good engineers, no strategy layer to pay for. A non-technical founder usually needs someone to write the spec with them first, which is agency or consultancy work even if the firm calls itself a dev shop.
What "software house" means in the UK and Pakistan
If you search "software house" from Lahore or Karachi you'll find lists of local firms; from London you'll find much the same. The term means the same business, and a couple of local facts make it concrete.
UK. When you register a company at Companies House you describe it with SIC codes. The list includes 62012 "Business and domestic software development", 62020 "Information technology consultancy activities" and 62090 "Other information technology service activities". A software house building to order typically sits under 62012, and one that mostly advises under 62020. An advertising agency is 73110 and a design studio 74100, which is a tidy way to see how differently the government already files these businesses.
Pakistan. Software houses that export services can register with the Pakistan Software Export Board (PSEB), which sits under the Ministry of IT & Telecom. PSEB's own membership benefits page says registered companies "pay only 0.25% tax on export proceeds" of IT and IT-enabled services, against 1% for non-registered companies, and that IT companies may keep up to 50% of export remittances in a foreign currency account. Those figures are as stated by PSEB on 15 November 2026; tax rates change with each Finance Act, so confirm them with PSEB or your tax adviser before you rely on them.
In both countries the shape of the business is identical: a team of developers, a pipeline of client projects, and an hourly cost that has to come in under the price.
How dev shops charge
There are four common models, and most dev shops end up mixing two of them.
Time and materials (T&M). The client pays an hourly or daily rate for the hours actually worked. The client carries the risk of the work taking longer; the shop's margin per hour is fixed. Clients like the flexibility and dislike the open-ended bill.
Fixed price. One price for a defined scope. The shop carries the risk. It pays well when the estimate is right and badly when it isn't, which is why the scope document matters more than the price. There's a fuller worked comparison in fixed price vs time and materials vs value pricing.
Dedicated team or retainer. The client pays a monthly fee for a set number of people or hours. Common for long-running product work and in software houses that serve overseas clients. The quiet risk is that the hours drift up while the fee stays put; retainer pricing that's still profitable in month nine walks through how that happens.
Hybrid. A fixed-price discovery or design phase, then T&M or a retainer for the build. This is often the most honest option for a new client: you price what you can see and bill the rest as it becomes clear.
A worked example: one project, three ways
These numbers are hypothetical. A small dev shop has a loaded cost of $45 an hour per developer (salary, overheads and tools, divided by the hours a developer can really bill). It estimates a client portal at 400 hours.
| Model | Price | Hours actually worked | Revenue | Cost | Margin |
|---|---|---|---|---|---|
| T&M at $75/hr | $75 × hours | 520 | $39,000 | $23,400 | 40% |
| Fixed price | $30,000 | 520 | $30,000 | $23,400 | 22% |
| Fixed price, on estimate | $30,000 | 400 | $30,000 | $18,000 | 40% |
The project runs 30% over. On T&M the shop's margin holds and the client pays more. On fixed price the shop absorbs the overrun and margin almost halves. Whichever model you choose, you need to see the hours climbing while there's still time to act, and the end of the project is too late.
What a dev shop actually does, week to week
The sales pages talk about code. The working week looks more like this:
- Scoping. Turning a brief into questions, a written scope and a breakdown of modules, user stories and tickets with hour estimates. Most of the money is won or lost here.
- Building. Sprints or a board of tickets, code review, QA, releases.
- Reporting. Telling the client where things stand, every week, often in more detail than they'll read.
- Change control. Deciding whether a new request is in scope, and pricing it if it isn't.
- Billing. Invoicing hours, milestones or the monthly fee, and chasing the ones that are late.
- Staffing. Keeping the team busy without overloading the best people, hiring when the pipeline justifies it, and onboarding contractors.
Only one of those six is writing software.
What breaks as a dev shop grows
At three people everyone sits in the same chat and knows what everyone else is doing. Somewhere between five and fifteen people a few things stop working on their own.
You stop knowing what happened today. The founder asks for status in the morning, again after lunch, again before the client call. Developers find the questions disruptive; the founder finds the silence worrying. A written daily check-in, where each person says what they'll do and later what got done, fixes more of this than another meeting does. There's a longer piece on getting status updates without chasing people.
Work stretches and nobody says so. A ticket estimated at six hours takes fourteen. Nobody hides it; nobody mentions it either, because there's no moment where anyone would. On a fixed-price project that's the margin going quietly. On T&M it's a client surprised by an invoice. The fix is comparing estimates with logged hours ticket by ticket while the project is running, and treating new requests as change requests with a price on them. See how to say no to scope creep.
The tool bill grows with every hire. A project tool per seat, a chat tool per seat, a time tracker per seat, a docs tool per seat. Each one is small. Add a developer and all of them go up at once, which is why many small dev shops end up with three half-used tools and data spread across all of them.
Output gets hard to measure. Lines of code and hours logged both mislead. What a founder wants to know is simpler: did the planned work get done, where is it blocked, and is the project on its estimate?
There are no systems to grow on. The founder is the scoping process, the QA process and the client-communication process. That works until a second project lead joins and does all three differently.
None of these are signs a dev shop is badly run. They are what happens when the informal habits of a small team meet a bigger one.
If you're hiring a dev shop: a short checklist
Questions worth asking before you sign, whatever the firm calls itself:
- Who writes the spec? If it's you, are you able to? If it's them, is discovery priced separately?
- How will I see progress? A weekly written update, a shared board, a client page? "We'll keep you posted" isn't an answer.
- What happens when I ask for something new? Ask to see their change request process before you need it.
- What's estimated, and how have their estimates held up? A shop that tracks estimate against actual can tell you.
- Who owns the code, the accounts and the deployment keys? It should be you, in writing.
- Who exactly will work on it? Names, not a team size, and what happens if one leaves.
- How is it priced if it runs over? Get the overage rate or the cap agreed up front.
If you're running one: where Suprwork fits
Suprwork is one workspace for running a small service business, and dev shops are one of the kinds of firm it was built around (there's an overview on the dev shops page). The parts most relevant to this article:
- Scoping. The Business Analyst reads a client brief, lists what's missing, writes a scope and, for software projects, breaks it into modules, user stories and tickets with hour estimates. Those tickets can become a project in Suprwork once, or go out to ClickUp, Linear, Asana or Monday.
- Projects and time. Projects & Time holds tickets, sprints, a board and a timer, and shows how estimates compared with the hours actually logged, person by person.
- Daily check-ins. Check-ins has each person type or speak their plan in the morning and what got done at the end of the day; the owner gets one written summary of the whole team by email, with blockers called out.
Chat, invoicing, a client portal and time off sit in the same workspace, at one flat monthly price with everyone on the team included (pricing). If your shop already lives happily in Jira and Slack and you only need better estimates, a dedicated time tracker may be all you need; the Toggl alternatives comparison covers those.
Sources
- Companies House, SIC codes list (checked 15 November 2026).
- Pakistan Software Export Board, membership benefits (checked 15 November 2026).