Before
Australian financial advisors with ongoing fee arrangements are required to conduct annual client reviews. The review obligation is documented in the fee disclosure framework and is central to demonstrating ongoing Best Interests Duty compliance. In most Xplan configurations, review scheduling is managed manually: an administration staff member looks at the client database each month, identifies clients whose annual review is due, and books appointments individually. Xplan's automated review scheduling workflow — which generates a review task for the advisor and sends a review invitation to the client based on the anniversary date — is not configured. Reviews fall behind when administration staff are busy. Clients who have not had a review in 13 or 14 months create a compliance record that is difficult to defend. The automation is available in the platform and not turned on.
After
The most immediate change is in the administration team's workload. Before configuration, the administration team spends time each month manually identifying clients due for annual review, manually creating FDS documents, and manually chasing onboarding documents by email. After configuration, those three processes run from the CRM without requiring the administration team to initiate them. The administration team's role shifts from initiating processes to managing exceptions — reviewing the FDS before it sends, following up the automated onboarding checklist, and confirming review completion records.
Before
Australian advisors on ongoing fee arrangements are required under the Corporations Act 2001 to send an annual Fee Disclosure Statement to each client on the anniversary of their ongoing fee arrangement. The FDS must include the fees charged in the preceding 12 months and the services provided. Generation and delivery of the FDS is triggered manually by administration staff in most practices — staff create the FDS from the Xplan template when they remember to, or when prompted by the compliance officer's quarterly reminder. The anniversary date for FDS delivery is not connected to a workflow trigger in the CRM. Late delivery of an FDS is a Corporations Act compliance breach that creates regulatory exposure and, in serious cases, has resulted in remediation obligations under ASIC enforcement action. The trigger connection between the client's fee arrangement anniversary date and the FDS generation workflow is a configuration change, not a platform change.
After
For the advisor, the change is in pipeline visibility. Before configuration, the advisor's sense of the new business pipeline depends on memory and informal conversations with the referral partner network. After configuration, the advisor opens a CRM view each morning that shows the referral partner pipeline, the new client onboarding status for each prospect in the pipeline, and the annual review schedule for the next 90 days. Business development and compliance management become activities driven by CRM data rather than by individual recollection.
Before
Australian financial advisors generate a significant proportion of new clients from referral partnerships with accountants, solicitors, mortgage brokers, and financial services professionals outside their immediate practice. The referral relationship is managed informally: the advisor and the accountant have lunch occasionally, and referrals come through when the accountant mentions a client who needs financial advice. There is no CRM pipeline recording the volume of referrals received from each partner, the conversion rate from referral to engaged client, or the value of referrals sent back to the partner. Without that data, the relationship has no measurement. The partners who are actually sending quality referrals are not identified and invested in differently from those who mentioned the partnership once and have never followed through.
After
For the compliance officer or practice principal, the change is in audit readiness. Before configuration, a compliance audit requires pulling information from Xplan, a separate FDS tracking spreadsheet, a review scheduling calendar, and individual advisor notes. After configuration, the compliance record for every client — review dates, FDS delivery confirmation, SOA version history, onboarding document receipt — is in the CRM. An audit request can be answered from a single system.
Before
Australian financial advisors require new clients to provide identification documents, tax file numbers, superannuation fund details, existing investment statements, and risk profile questionnaire responses before an SOA can be prepared. This documentation is collected by email — the advisor or administration team sends an email listing what is needed, and the client replies with attachments when they get around to it. There is no structured document collection workflow in the CRM. Onboarding stalls when one document is missing and the team does not have a systematic way to track what has been received and what is outstanding. The advisor cannot prepare the SOA until all documents are in hand, and no one knows at a glance which clients are waiting on which documents. A structured onboarding document checklist with automated follow-up for outstanding items reduces onboarding time from three to four weeks to seven to ten days in most practices.
After
For the self-licensed firm, the change is in independence. The compliance infrastructure that was previously maintained by the licensee is now built into the practice's own CRM. Review scheduling, FDS delivery, and Best Interests Duty documentation workflows run on the practice's own platform, owned and controlled by the practice, not dependent on a licensee's system.
