Xplan Customisation Services

Make Xplan fit the way your team works.

Shape the everyday experience around your team's tasks, rather than asking people to work around the system.

Customisation that fits the work

AdviserMate customises Xplan so the everyday experience reflects how your team actually works — clean data capture, reliable documents, automated workflows and reporting that genuinely inform decisions. Every change is built around a real task, not a generic template, so the system stops getting in the way and starts supporting the work.

Custom pages and wizards

Streamlined pages and wizards that present only the fields your team needs, capturing data cleanly and triggering the right next actions without extra steps.

Coded document templates

Expertly coded Xplan document templates — for advice and compliance documents, client communications and reports — built for accuracy and a professional finish.

Threads/Cases workflows

Workflow design and build using Xplan Threads and Cases, automating tasks, emails and data updates so repeatable work runs consistently across the practice.

Exports and Excel-based reporting

From straightforward Xplan data exports to sophisticated Excel-coded reports, tailored to the outputs your business actually relies on.

Dashboards

Clear dashboards that surface the metrics that matter — for advisers, paraplanners and management — without drowning the team in unnecessary detail.

Power BI/Tableau connections and reporting automation

Connections to external tools such as Power BI and Tableau, with automated reporting that keeps business intelligence current without manual handling.

How the work is delivered

A practical, four-step path keeps each change anchored to the task it serves — from understanding the work to an agreed handover.

01

Understand the task

Start with the task your team performs, not the screen. We map the steps, the hand-offs and the friction, so change is defined against real work.

02

Specify the change

Agree a clear specification of what will change, how it behaves, and what good looks like — before any build begins.

03

Build and test

Build the change and test it against the agreed specification, exercising the realistic scenarios your team will actually encounter.

04

Agreed handover

Hand over with documentation and, where useful, a short walk-through, so the team can adopt the change with confidence.

Evidence, not mock-ups

Where we illustrate the value of a change, we use a permission-cleared before/after process example from real work — not a fabricated interface. You see what actually changed, and why it mattered, rather than an idealised screen.

Frequently asked questions

Which permissions are needed?

The permissions required depend on what is being changed — for example, configuration access for pages and workflows, or template-editing access for document coding. We identify the specific permissions needed for each change as part of scoping, and you grant only what is required.

Can changes be tested before release?

Yes. Changes are built and tested against the agreed specification before release, exercising realistic scenarios so your team can confirm the behaviour meets expectations before it goes live.

How are document requirements signed off?

Document requirements are confirmed with the responsible owner — typically your advice or compliance lead — and captured in a short specification before template coding begins. Final wording and compliance responsibility remain with your business and licensee.

All proposed steps and outputs require technical-owner confirmation.

Discuss an Xplan improvement.

Tell us the task that's harder than it should be. Let's shape a change that fits your team.

We use cookies to analyse website traffic and optimise your experience. See our Cookies Policy.