Pricing · Indicative, in rupees

What software actually costs, before you spend an hour on a call

Most software houses will not publish a number. We understand why — cost genuinely follows scope, and a price quoted before anyone has seen your operation is invented. But refusing to say anything at all wastes your time and ours, so here are honest starting bands, what moves them, and the two ways you can own the result.

Get a scoped quote How ownership works ↓

Where projects start

Every figure below is a starting point in Pakistani rupees, not a quotation. What you finally pay follows the written specification we agree before development begins — which is also the document that keeps the price honest on both sides.

  • 01

    Onboarding onto a system we already run

    PKR 100,000 – 300,000

    A school joining the School Management ERP System, or a mill joining the Textile Management Expert System.

    The software already exists and is in production elsewhere, so what you are paying for is configuration to your institution, migration of your existing records, per-role training and go-live support. For a school, the figure moves with the size of the school — a single-campus academy sits near the bottom of that range and a large multi-section institution near the top.

    WHAT MOVES THE NUMBER

    • How many students, staff or units the system must carry
    • How many paper records need digitising before go-live
    • How many roles need training, and whether that training is on-site
    • Configuration depth — sections, streams, production stages, fee structures
  • 02

    Custom development, focused scope

    from PKR 100,000

    A single-purpose tool, a focused module, a landing page or a small business website.

    Small projects are real projects here, and we quote them as such rather than pushing you toward something larger. A tool one team uses daily, one workflow taken off paper, or a well-built website starts in this band. If your requirement genuinely fits an off-the-shelf package instead, we will say so at scoping and save you the build.

    WHAT MOVES THE NUMBER

    • The number of screens, user roles and documents produced
    • Whether it must talk to systems you already run
    • How much existing data has to be migrated and cleaned
    • Whether the design is bespoke or works from our existing patterns
  • 03

    Custom development, multi-workflow

    around PKR 200,000 and up

    A CRM for a sales team, an accounting system, a multi-module operational build.

    Most custom engagements land here or above: several connected workflows, a handful of user roles, real reporting, and integration with accounting or FBR digital invoicing. The number rises with the number of distinct workflows the system has to model — including the exceptions, which is exactly what on-site scoping exists to find.

    WHAT MOVES THE NUMBER

    • How many workflows and departments the system spans
    • Integrations — accounting, FBR e-invoicing, an existing ERP, a website
    • Reporting depth: how many named reports and printed documents
    • Whether the system must work offline or across multiple locations
  • 04

    A new system for your industry

    from PKR 200,000, scaling with complexity

    A clinic, a distributor, a fleet, a property developer — an operation designed from first principles rather than configured from an existing product.

    Designing an operation from first principles is precisely what a custom software house is for, and it is what we have done since 1998 — the school ERP and the textile system were each, once, a first. The engine transfers: role-scoped access enforced in the database, scheduling under real constraints, stock and costing that reconcile, double-entry accounting underneath. What changes is your vocabulary, your stages and your exceptions — which is exactly what on-site scoping is for. You are paying for that design work, and what you get is a system shaped to your operation rather than a package you spend years bending.

    WHAT MOVES THE NUMBER

    • How many operational stages and roles the system has to model
    • How far your workflows diverge from systems we already run
    • Regulatory or traceability requirements specific to your sector
    • How much of the process exists only in people's heads today

Two ways to own what we build

This choice affects the price as much as the scope does, and it is worth making deliberately rather than discovering at handover.

OUR USUAL ARRANGEMENT

Built for you, licensed monthly

We build the system to your requirements, host and maintain it, and charge a monthly retainer for you to use it. Support, fixes and hosting sit inside that retainer, so the system keeps being maintained rather than ageing quietly. The retainer is quoted alongside the build once the scope is agreed — it scales with the size of the system, not with a per-user headcount.

  • Lower up-front cost than buying outright
  • Hosting, backups, support and fixes included
  • No per-user licence fee as your team grows
  • The system keeps being maintained and improved
SOURCE CODE HANDOVER

Built for you, owned outright

If you want to own the build — for investment, audit, strategic reasons, or because you intend to white-label and resell it — we hand over the full source code and database schema. This costs more up front than the licensed arrangement, and how much more depends on the project. The ownership terms are written into the agreement before development starts rather than negotiated afterwards.

  • Full source code and database schema transferred
  • White-label and resale arrangements supported
  • Higher up-front cost, no ongoing licence
  • Optional continuing support, or a clean separation

Where you buy the source outright, the handover includes the database schema, deployment configuration and documentation — the things that make ownership real rather than nominal. The terms are agreed in writing before development starts. More on build-to-own and white-label work →

What the price always includes

These are not line items we add at the end. On-site scoping where you are in Karachi, a written specification you approve before we build, migration of your existing records, per-role training on your own data rather than demo data, and written user manuals so the system outlives the staff who launched it.

Row-level and column-level security, encryption in transit and at rest, role-based access and automated backups are standard on every build — never quoted separately. So is edge-delivered hosting on cloud deployments, so the system responds quickly wherever your people are.

How we work What "secure" means here →

Money questions, answered

How much does custom software cost in Pakistan?

Focused custom builds start from around PKR 100,000, and most multi-workflow systems — a CRM for a sales team, an accounting system, a multi-module operational build — start around PKR 200,000 and rise with scope. Onboarding onto a system we already run, such as the school or textile ERP, typically falls between PKR 100,000 and 300,000. These are starting points, not quotations: the figure follows the agreed written scope.

What can I get for a budget of PKR 200,000?

At that level we would normally build either a multi-workflow custom system — a CRM, an accounting system, or a focused operational module set with real reporting — or onboard a mid-sized school or mill onto one of our existing platforms with configuration, data migration and per-role training included. Tell us the figure on the first call and we will tell you honestly what can be built well within it.

What does it cost to put a school on your school management system?

Typically PKR 100,000 to 300,000, depending on the size of the school. A single-campus academy sits near the lower end; a large multi-section institution with many staff and years of paper records to digitise sits near the upper end. Configuration, record migration, per-role training and go-live support are part of that, not extras.

Do you charge a monthly fee or a one-time price?

Our usual arrangement is that we build the system to your requirements and charge a monthly retainer for you to use it, with hosting, backups, support and fixes included. If you would rather own the build outright, we hand over the full source code and database schema for a higher up-front cost. Both models are quoted before development starts.

How much does it cost to buy the source code?

More up front than the licensed arrangement, and the difference depends on the project — its size, whether it was engineered for resale, and what exclusivity you want. What does not vary is that the ownership terms are written into the agreement before development begins rather than negotiated at handover.

Why will you not publish a fixed price list?

Because a fixed price quoted before anyone has seen your operation is a number invented to keep you in the conversation. Cost follows scope, and scope follows what your business actually does — which is what on-site scoping establishes. The bands on this page are honest starting points so you can judge whether we are in your range before spending an hour on a call.

Is the scoping conversation free?

Yes. We listen, ask questions, and tell you honestly whether custom software is the right answer — including when an off-the-shelf package would serve you better, or when your budget will not produce something worth having.

Tell us the budget on the first call.

We will tell you honestly what can be built well within it — and if it cannot produce something worth having, we will say that too.

EST. 1998 · KARACHI
Book a consultation How we work