Sales CRM
Leads, pipeline stages, quotations, follow-up reminders, and conversion reporting that reflects your actual sales motion.
Every growing company reaches the same point: the CRM handles sales but not service, the accounting software will not model your discount structure, and the gap between them is a spreadsheet maintained by one person who is now indispensable.
A custom CRM or ERP is worth building when your process is genuinely yours — unusual pricing, multi-branch inventory, regulated approvals, or an industry the mainstream vendors ignore. When a standard product would fit, we will tell you to buy it.
Modules we build
Inventory and warehouse
Multi-location stock, batch and expiry tracking, transfers, stock takes, and low-stock alerts.
Procurement
Purchase requisitions, multi-level approvals, supplier records, and goods-received matching.
Finance and invoicing
Invoices, receipts, credit notes, ageing reports, and local tax handling with export to your accounting software.
HR and payroll support
Attendance, leave, appraisals, and payroll inputs — integrated with the rest rather than a separate island.
Field and service operations
Job scheduling, technician mobile app, checklists, photo evidence, and customer sign-off.
What decides success
- Getting the approval chain right. Most ERP failures are organisational: the system enforces a workflow nobody agreed to. We map it with the people who use it before designing anything.
- Data migration done properly. Your existing records come in cleaned and reconciled, with a report of what could not be matched.
- A parallel run. New and old systems run side by side until the numbers agree and your team trusts the new one.
- Role-based permissions. Sales sees pipeline, finance sees margins, branch managers see their branch only.
- Reports your management already asks for. Built from the questions in your existing meetings, not a generic dashboard.
- Training and documentation. Written for your staff in plain language, with a session per role.
Key facts
- Licensing
- None — unlimited users, no per-seat fee, ever
- Hosting
- Your servers, your cloud account, or ours — including on-premise for data residency
- Integrations
- Accounting software, POS, e-commerce, payment gateways, SMS and WhatsApp
- Access
- Web plus a mobile app for field and warehouse staff where needed
- Migration
- Existing data imported, reconciled, and verified before go-live
- Ownership
- Full source code and database, transferred on delivery
Custom vs commercial ERP
| Custom (Qalmax) | Commercial ERP (SAP, Odoo, Zoho) | |
|---|---|---|
| Fits unusual processes | Built to them | You configure, or you adapt |
| Cost model | One-off build + hosting | Per user per month, indefinitely |
| Implementation time | Weeks to months | Months, plus consultant fees |
| Feature breadth on day one | What you asked for | Vast, most of it unused |
| Upgrades | When you choose | Vendor's schedule, sometimes forced |
| Exit cost | None — you have the code | Data export and a re-implementation |
Commercial ERP wins on breadth and on being someone else's problem to maintain. Custom wins when the per-seat bill has become significant and the standard product still does not model the thing that makes you money.
Technology stack
We choose tools for what your team can maintain after handover, not for novelty. Typical stack for this service:
LaravelNode.jsReactPostgreSQLRedisMetabaseDockerAWS
Questions, answered.
Is a custom CRM cheaper than paying for Salesforce or Zoho?
Over a long enough horizon and a large enough headcount, usually yes — a custom build is a one-off cost plus hosting, while per-seat licensing compounds every year as you grow. For a small team it rarely pays off, and we will say so. The other factor is fit: licensing is only wasted money if the product does not do what you need.
Can it integrate with our accounting software?
Yes. We integrate with QuickBooks, Xero, Zoho Books, Tally, and most regional accounting platforms via API, and where no API exists we build a structured export in the format your accountant already imports.
Will our staff actually use it?
That depends more on the rollout than the software. We involve the people who do the work during process mapping, keep data entry to the minimum the process genuinely needs, run the new system in parallel with the old one, and train by role. Systems get rejected when they are imposed, not when they are built with the users.
Can it work offline for field staff?
Yes. Field and warehouse apps are built offline-first where connectivity is unreliable — data is captured locally and synced when the device reconnects, with conflict handling for records edited in two places.
How long does an ERP project take?
It depends heavily on module count and how much data migration is involved. We scope module by module and quote a written timeline before starting, and we usually recommend launching one or two modules first rather than a single large switch-over.
What about data security and access control?
Role-based permissions down to the field level, full audit trails on every change, encrypted data at rest and in transit, and hosting in the region your policy requires — including entirely on-premise if regulation demands it.
You do not have to commit to a whole build.
Most people arrive somewhere between “just curious” and “ready to sign”. These are the smaller, fixed-fee ways in — each one useful on its own, and each one credited or extended into a bigger project only if you decide you want that.
Code & architecture audit
You have a codebase — inherited, stalled, or just worrying — and want an honest read before committing to anything.
- Written report on architecture, security, data model and deployment
- A prioritised list separating genuinely urgent from merely untidy
- A straight answer on repair versus rebuild, even when rebuild pays us more
- The report is yours whether or not you continue with us
Fixed fee, agreed before we start
Ask about this →
Scoping sprint
You know roughly what you want but not what it should cost or contain. Turn a vague idea into a specification you could hand to any supplier.
- Process mapping with the people who actually do the work
- A feature-by-feature written specification
- Wireframes of the core screens
- A fixed build price and delivery date at the end
- Fully credited against the build if you go ahead with us
Fixed fee, credited against the build
Ask about this →
Starter build
One workflow, one screen set, live and in use — rather than waiting on a full platform.
- A single working feature deployed to production
- Real infrastructure, not a prototype
- Extends into the larger build later without rework
- Full source code on delivery, as always
Fixed price, scoped small on purpose
Ask about this →
Maintenance retainer
An existing product that needs keeping alive: patches, OS updates, store policy changes and monitoring.
- Security and dependency patching
- iOS and Android release compatibility
- Uptime and error monitoring with a named response window
- An allowance of small changes each month
Monthly, 30 days' notice, no lock-in
Ask about this →
Not sure which fits? Describe the problem and we will tell you — including when the answer is that you do not need us yet.
Six things we put in writing.
Not values on a wall — contract terms. Ask any other supplier to match them line by line.
A price in 24 hours
Send a brief, get a fixed written price and a delivery date the next working day. Free, no obligation, and the scope document is yours to keep even if you go elsewhere.
The price does not move
Fixed, not an estimate. If scope changes we re-quote in writing and you approve before we build it. You will never open a surprise invoice.
Half on delivery
50% to start, 50% when it is live and you are satisfied. You never fund the whole project up front.
Unlimited design revisions
We do not write production code until you approve the screens. Changing your mind at that stage costs nothing.
You own everything
Full source code, design files and credentials on delivery. No licence, no platform fee, nothing that stops another developer taking over.
30 days of fixes included
Free bug fixing for a month after launch, then an optional retainer only if you want one.
Every one of these is in the agreement before you pay anything. See how we evidence our claims →
Free quote
Tell us what you're building.
A paragraph is enough to start. You get a scoping conversation and a fixed written price with a delivery date within 24 hours — free, and yours to keep whether or not you go ahead with us.
- A senior engineer replies, not a salesperson
- Written quote inside 24 hours
- NDA before you send anything sensitive — just ask
- No obligation, no follow-up sequence
Prefer to talk now? WhatsApp +92 300 097 0544 or hello@qalmax.com.
Replace the spreadsheets.
Process mapped, price fixed, code yours. Written quote in 24 hours.