Independent business analysis · Greater Manchester & UK-wide

What needs to be agreed before changing a system?

A supplier can configure exactly what was requested while your teams still disagree about when a deal is qualified, who owns a handover or which record is correct. Resolve those decisions before the software makes an unclear rule permanent.

Review of the current process · Clearer project scope · Questions to settle before approval

The missing part of a project

Supplier deliverables and internal operating changes

A proposal may include pipeline configuration, data migration and dashboards. It may not include agreeing what qualifies as an opportunity, who validates records, or who acts on an exception after go-live.

Those tasks remain real even when they are outside the supplier's scope. See the costs and responsibilities often overlooked in a CRM project.

How an independent review works →

First decisions, not a technology catalogue

Checks before approving the proposal

Before you sign

What the CRM quote excludes

Compare promised deliverables with the work your team must do to use them.

Review questions →
Before you budget

Internal implementation costs

Include licences, staff time, clean-up, testing and continuing ownership.

Cost checklist →
Before you automate

Constraints outside the proposed system

Test whether local time saved can change fulfilment, capacity or margin.

Five checks →
When a project needs a second look

Document the present workflow before approving changes

A useful review should tell you which questions really need an answer before you commit, who is responsible for answering them and whether anything in the proposal should change.

Ask about a proposal review