An ERP or a standalone CRM, DMS or WMS: how to choose
An integrated ERP solves problems that arise at the borders between departments; a standalone system solves a problem that lives inside one department. Five questions show which one is yours.
- Published
- Author
- Konis Software
A company looking for new software rarely starts by asking whether it needs an ERP. It starts from the pain: sales does not know what was promised to a customer, a contract takes half a day to find in someone's inbox, the warehouse runs from memory. From the pain it is easy to jump to a category — we need a CRM, we need a DMS, we need a WMS — without checking whether the pain really lives in one department or merely surfaces there.
The difference is decisive. A problem that lives in one department is solved by a standalone system, faster and with fewer changes to the rest of the company. A problem that arises at a border — between sales and the warehouse, the warehouse and finance, a document and its posting — is not solved by a standalone system but moved: you get a better tool on one side of the border and the same data transfer across it.
Where the problem lives, and where it only surfaces
The simplest test is to follow one piece of data through the company. Take a customer, an item or a contract and count how many times it is entered, and in how many systems. If the customer lives in one sales tool, and everything else about them is known to an accounting system that works well and is staying, the problem is in sales. If the same customer is keyed into the quote, then the order, then the delivery note, then the invoice, and every time someone checks that it matches the previous step, the problem is not in sales but in the handover.
The same holds for documents and for goods. A company whose contracts get lost in folders and mailboxes has a findability problem, and a good document system solves it. A company whose warehouse stock disagrees with the stock in the books has the problem of two truths about one pile of goods, and a better warehouse tool beside the existing books does not solve it — it is solved by the stock figure existing once.
Five questions before you choose
- 1
How many processes share the same master data?
If customers, items and stock are read and changed by sales, the warehouse, purchasing and finance, every standalone system means one more copy of that data and one more transfer. If essentially one department uses them, the copy is a small cost.
- 2
Is the pain confined to one department?
Ask the people doing the work where they lose time. If everyone points at the same place — the pipeline, finding documents, receiving goods — the starting point is a standalone system. If everyone points at the border with their neighbour, the starting point is an integrated system.
- 3
Is the existing ERP staying?
Many companies run an accounting or inventory system that covers the regulation and that they are happy with. Then the right move is to add what is missing, not to replace what works. If the existing system is leaving anyway — it is outdated, it does not keep up with the regulation, or the vendor is retiring it — the question changes and an integrated ERP comes onto the table.
- 4
How soon must the solution be working?
A standalone system changes one flow and is introduced with fewer decisions in the rest of the company. An ERP changes how the whole company posts, reserves and approves, and it needs a process analysis, a migration and a period of parallel running. If the deadline is short, that is an argument, not a detail.
- 5
Who runs the implementation?
An ERP rollout needs people from finance, sales and operations who set aside time for months to decide the chart of accounts, the dimensions and the approval rules. If those people are not available today, a smaller, clearly bounded project is a more honest start than a large one nobody can lead.
Typical situations
| Situation | Sensible starting point | Why |
|---|---|---|
| Sales tracks opportunities in spreadsheets; accounting and inventory work and are staying | Standalone CRM | The pain is in one department; the rest of the company does not need to change |
| Contracts and incoming mail are hunted through folders and inboxes | Standalone DMS | The problem is findability and order in documents, not posting |
| The warehouse runs from memory, while stock accounting in the existing system is correct | Standalone WMS | What is missing is physical logistics — locations, receiving, picking, counting |
| The same data is re-keyed between sales, the warehouse and finance | Integrated ERP | The cost is in the handovers, and a standalone system does not remove them |
| The existing ERP is leaving in any case | Integrated ERP | If the core is changing anyway, that is the moment to close the borders |
When a standalone system is the right choice
A standalone system is not a half-measure. For a company whose problem sits in one department it is the whole answer: it goes in faster, it leaves working accounting alone, and it does not ask the entire company to change its habits at once. The NG family has three such products, each with its own site and its own status.
NG CRM — when the problem is in sales
NG CRM covers sales and the pipeline, quotes, a shared Inbox for email, Viber through Mailbook and web chat, marketing, support, documents from templates, analytics, mobile work through a PWA, and the NG Copilot assistant, which carries out an action only after confirmation. NG CRM is commercially available. Details are at ng-crm.app.
NG DMS — when the problem is in documents
NG DMS is a document system: capture and OCR, full-text search, classification and metadata, access rights and data isolation, approval workflows, the registry book and the archive, with NG Copilot answering with a citation of the exact page. NG DMS is commercially available. Details are at ngdms.app.
NG WMS — when the problem is in the warehouse
NG WMS runs warehouse management: inbound goods, outbound with preparation and checking, stock and replenishment of pick locations, counting, a warehouse model with zones and locations, labels, a scanner app, and integration with the ERP a company already runs. NG WMS is commercially available, with NG Copilot for questions about stock and orders. Details are at ngwms.app.
When an integrated ERP is the right choice
An integrated ERP makes sense when the largest cost is in the handovers. In NG One, sales and CRM, documents and processes, and inventory with the warehouse are parts of the same system, over the same master data: an opportunity becomes a quote, the quote an order, the order a delivery note and an invoice, and each of those changes moves the same stock figure and the same posting. There is no overnight transfer because there is no second system to transfer to.
The price of that simplicity is the scope of the rollout. An ERP requires decisions that are made once and are hard to change afterwards — the chart of accounts, the dimensions the business is measured by, the approval rules, the warehouse structure. So an ERP is not a better choice than a standalone system in absolute terms; it is the better choice for a problem that genuinely sits at the borders.
What this piece does not claim
- That moving from a standalone product to NG One is automatic. Every move between systems is a project with its own migration.
- Any prices, implementation timelines or results. They depend on scope, and scope is established by a conversation about your processes.
- That one approach is always better. A standalone system and an ERP solve different problems, and the wrong choice costs in both directions.
How to decide in one conversation
Before the conversation, write down three things: which piece of data you enter more than once, where people wait the longest, and which of your current systems is certainly staying. Those three items usually show whether the problem sits in one department or at the borders — and which product in the family is the right starting point, including the answer that you need none of them. An overview of the whole family is on the Ecosystem page of this site.