45 Albemarle Street, 3rd Floor, London, United Kingdom, W1S 4JL
Existing client support020 8087 4981

Strategy & growth / A PRACTICAL GUIDE

Choosing CRM or ERP without buying a new set of problems

Define the workflow, information and adoption plan before comparing feature lists.

A CRM or ERP project affects how people work across the business. The product demonstration is only part of the decision. A strong starting point is a clear process, usable information and agreement on what should improve when the system is introduced.

THE KEY IDEA

A business system succeeds when the workflow, information and people are ready to use it together.

Write down the workflow you need to improve

Choose a real process such as managing enquiries, preparing quotes, scheduling work or reconciling stock. Record the handovers, duplicate entry and missing information that create difficulty. Identify the people making each decision. Use that process to build a short requirements list. Broad ambitions such as have everything in one system are difficult to test unless the important activities are described first.

Use a scenario in every demonstration

Give each potential supplier the same representative task and ask them to show it from beginning to end. Include an exception, such as an amended order or a returning customer. Record where customisation, additional products or manual work would be required. Ask about access roles and reporting. A shared scenario makes comparisons more useful than allowing each demonstration to focus only on the supplier’s favourite capabilities.

Plan information and integration work

Identify the records to migrate, the quality problems to fix and the applications that must exchange information. Ask who designs and supports those connections. Clarify ownership of exports, configuration and any custom development. Include the cost and effort of preparing information, training people and changing a process. Purchasing a subscription does not complete the implementation work that turns it into an operational system.

Judge adoption and ongoing ownership

Name a business owner who can make process decisions and a route for technical support. Pilot with representative users and check whether they can complete the required tasks. Define the review points and reporting that show progress after launch. If a specialist implementation partner is needed, clarify its responsibilities alongside your IT provider. Good infrastructure and access support are valuable, but they should not be confused with business-system implementation expertise.

PUT IT INTO PRACTICE

Your starting checklist.

Use these prompts to prepare your next decision or conversation.

YOUR NEXT STEP WITH IT MOUNTAIN

Turn the question into a plan.

Discuss the workplace, access and infrastructure dependencies with IT Mountain. Agree where specialist CRM or ERP implementation support is also required.

LET’S TALK ABOUT YOUR IT

Request a callback

Leave your details and tell us how we can help.

Your details are used to respond to your enquiry.