Frequently asked questions

Seven lines: custom ERP development, custom CRM development, financial accounting systems, custom software development, website and landing-page development, software product development with source-code handover, and support and modernisation for systems built by others.

Yes — custom CRM development is a core service line. We model your actual sales practice rather than configuring a generic funnel: an account timeline of visits, calls, quotations, orders and commitments; follow-ups as dated obligations with a named owner; and integration with your operational data so the salesperson sees ledger balances and open orders on the same screen as the conversation.

Yes, at any scale. Engagements often begin with a single module where the pain is sharpest — inventory, costing or invoicing — and grow module by module. Because everything writes to one database, each addition inherits clean, connected data instead of becoming another silo.

Both. We connect a CRM to an existing ERP so orders won in one flow into the other, and we also build hybrid systems carrying full CRM capability and full ERP capability as a single product against one database — which removes the synchronisation problem between them entirely.

Yes — business websites, landing pages, portfolio sites and web applications. They are built as engineering rather than decoration: static HTML containing the full content so crawlers and AI assistants can read it, per-page metadata and structured data, edge delivery for speed, and optional integration with your CRM or ERP.

Not as a service you can hire us for. We build the technical foundation into every website — rendered HTML, unique metadata, heading structure, canonical URLs, structured data, speed and a sitemap — because a site without it cannot rank whatever anyone does afterwards. The ongoing half, keyword research and off-site authority, is a different discipline run over months, and we will say plainly that it is not what we sell.

Not as a standalone service. Every system we build works properly on a phone browser as standard, which covers most of what businesses ask an app for. Where the work genuinely depends on the device — offline capture with no signal, camera, barcode scanning, push notifications — we build the app as part of the system it belongs to, the way our HR system captures field attendance offline and syncs when the signal returns.

Yes, as part of the system rather than as a separate product. Retrieval-based assistants answering from a client's own documents, an assistant inside an ERP that teaches new users how the system works, a daily business brief compiled from the client's own records, and workflows that read and route documents someone currently retypes. An assistant that cannot reach your real data is a demonstration, not a tool, which is why we build these inside the systems we also build.

Yes, provided you can supply the source code and reasonable environment access. We add modules, fix long-standing problems, build integrations and modernise legacy systems — and we tell you honestly when the existing code is a liability rather than a foundation. Client source code is handled under NDA and deleted from our systems once the work is delivered.

With discovery at your premises. We visit the factory floor, school office, warehouse or showroom and watch the work happen — the registers people keep privately, the approvals skipped when it is busy, the exception nobody documented. In Karachi that visit is standard; elsewhere it is replaced by structured remote sessions with your operational and accounts staff.

Yes, always. Modules, screens, roles and reports are agreed on paper and approved by you before development starts. It keeps scope honest on both sides and means nobody discovers a misunderstanding at delivery.

Yes — per-role training after deployment, on your own migrated data rather than demo data. Each person learns the portal they will actually use; nobody has to learn the whole system to do their part of it.

Yes. Written user manuals are part of delivery, produced so that a new employee joining years later can understand the system with nobody left who was there at launch. A system only one trained person understands is a risk pretending to be an asset.

Yes. Cloud is the default because it is faster to serve and easier to back up reliably, but offline-capable and fully on-premise builds are normal alternatives. The choice is made with you at scoping based on connectivity, security policy and where your users are.

Support from the engineers who built the system — fixes, adjustments and new modules as the business changes — Monday to Saturday, 9am to 6pm PKT, with a response inside 24 hours. Some Linksoft systems have been maintained continuously since the late 1990s.

Yes, across Pakistan — Lahore, Islamabad, Faisalabad and beyond. Systems are cloud-based so nothing needs installing locally; discovery runs as structured remote sessions, records are migrated and verified with your team, each role is trained by video, and support hours are identical to those Karachi clients get. We do not claim offices we do not have.

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

At that level Linksoft 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 an existing platform with configuration, record migration and per-role training included. Tell them the figure on the first call and they will say honestly what can be built well within it.

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 included rather than charged as extras.

The usual arrangement is that Linksoft builds the system to your requirements and charges a monthly retainer for you to use it, with hosting, backups, support and fixes included. If you would rather own the build outright, they hand over the full source code and database schema for a higher up-front cost. There is no per-user licence fee in either model, so growing your team does not grow the bill.

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. The ownership terms are written into the agreement before development begins rather than negotiated at handover.

Five things, in roughly this order: the number of distinct user roles and their screens; how many workflows must be modelled including the exceptions; integrations with accounting, FBR invoicing or existing systems; how much historical data needs migrating and cleaning; and whether training and documentation cover a handful of people or several departments.

Usually yes, by shaping the scope to it. Tell them the figure on the first call and they will say honestly what can be built well within it — and if the budget cannot produce something worth having, they will say that too rather than taking the work and disappointing you.

Yes. The scoping conversation costs nothing: 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.