Insight · 6 November 2026 · 5 min read
Origin Growth sets out where everyday operations belong in CRM
Adviser IQ’s latest announcements put operational information and internal collaboration alongside customer records. For Origin Growth, the useful question is whether those additions make staff tasks simpler — not whether they make the platform bigger.
Adviser IQ has announced property-data integration and an intranet within its CRM platform, bringing operational information and internal collaboration alongside customer records. The Intermediary reported the property-data integration on 6 November 2026 and the intranet addition on 4 November 2026. Together, these announcements provide a useful starting point for UK organisations considering how far their customer relationship management (CRM) platform should extend into everyday work.
Origin Growth welcomes the ambition to make useful information easier to reach. Our view is that the boundary deserves careful design: a CRM addition should earn its place by helping staff complete a task, with clear information ownership and dependable connections to other systems. More functions in one place can be useful. More complexity in one place is still complexity.
Start with a small set of operational tasks that touch customer records, rather than a catalogue of available modules. For each task, ask staff to show how they begin, what information they consult, what decision they make and where they record the outcome. Include the awkward cases, not just the straightforward demonstration.
For example, an organisation assessing a property-data connection could map how an adviser identifies the relevant property, checks the information and uses it in the next customer conversation. This is a suggested assessment exercise, not a description of Adviser IQ’s implementation. The important detail is where the information helps the work, rather than merely appearing on screen.
Record four things for each task:
Then decide what the CRM needs to provide. The answer might be a complete workflow, a small information panel or a link to another service. Those are different design choices, with different maintenance obligations.
We recommend making this distinction explicit before procurement or configuration starts. A task map should explain why a function belongs beside a customer record, not simply establish that the platform can accommodate it.
Once operational information appears inside CRM, decide who is accountable for its meaning and accuracy. Showing information in a customer-facing team’s workspace should not quietly transfer responsibility for maintaining it to that team.
Create a compact ownership register for each proposed addition. Name the authoritative source, the business owner, the person or team permitted to change it and the route for reporting a problem. Specify whether the CRM stores the information, displays it from elsewhere or holds a temporary copy. These arrangements should be understandable without an architecture diagram.
Consider a hypothetical internal procedure shown beside a customer case. The procedure might belong to operations, while the case belongs to the customer service team. Staff should be able to distinguish approved guidance from case notes, see which version applies and find the owner when something looks wrong. Putting both items on the same screen does not make them the same kind of record.
We would also settle access rules before opening up a new information area. Ask who needs to read, edit, approve and administer each type of content. Review whether customer-record permissions are appropriate for internal collaboration, rather than assuming one set of permissions will serve both purposes.
This is particularly important when assessing an intranet addition. Give publishing, review and withdrawal of internal content an explicit home. Otherwise, the organisation risks creating another place where nobody is quite sure whether the instructions are current.
An integration needs a working agreement, not just a line between two boxes. Before approving one, document what moves between systems, in which direction, at what point and under whose authority. Separate information that staff only need to read from information they need to change.
Our preferred starting point is the smallest connection that supports the task properly. If staff need a current reference value, assess whether displaying that value is sufficient before commissioning a full copy of the underlying dataset. If they need to update it, establish where that update should happen and how other users will see the change.
For each connection, ask:
Use these questions to write acceptance criteria that business and technical teams can both review. For example, require the interface to distinguish unavailable information from an empty field, rather than leaving staff to guess what the absence means.
We also recommend agreeing a practical fallback. That might mean opening the source system, referring the task to a responsible team or pausing an action until information is checked. The right choice depends on the task. A seamless interface is welcome; an honest account of its limits is essential.
With tasks, ownership and integration needs mapped, make a decision for each proposed capability. Avoid approving an entire category such as “internal collaboration” as though every activity within it has the same requirements.
Embedding a function may be appropriate where it directly supports customer work and the CRM offers a suitable place to complete and record it. Connecting another system may be preferable where that system retains ownership of specialist information or processes. A straightforward link may be enough where staff only need occasional access and copying information would add little value.
For an intranet proposal, distinguish organisation-wide publishing from guidance needed during a particular customer task. We would assess these separately. A company announcement and an approved procedure may both be internal content, but they need not occupy the same position in the working interface.
Put the decision into a short capability brief: the task supported, the chosen approach, the information owner, access requirements, dependencies and support responsibility. Ask marketing, digital and operations leaders to review the same brief so that convenience for one team is not purchased through hidden work for another.
Then test the proposed arrangement with staff using realistic tasks before committing to a broader rollout. Our ambition is a robust, user-focused workspace that makes the next action clearer, without asking the CRM to become the home of everything. If your organisation is weighing up CRM additions, talk to Origin Growth about defining those boundaries before configuration begins.
