Advice technology, client experience and operating systems. My work examines how portals, CRM, workflow, reporting and practical AI become one coherent delivery model.

The Advice Firm Operating Layer

Advice firms rarely have a simple software problem. The friction usually sits between systems: a client enters information in one place, an adviser reviews it in another, documents live elsewhere, and the team coordinates the work through email and memory.

I treat the portal, CRM, workflow, documents, reporting and automation as one connected operating layer. That starts with the client and advice journeys, identifies the source of truth for each piece of data, and makes ownership explicit at every handoff.

Financial Advice Client Portals

A client portal is not just a set of forms. It is the front door to the advice operating model. Effective portal work connects secure identity, client data capture, document exchange, CRM records, adviser visibility, task routing and timely client prompts.

I map what the client needs to understand, what information the advice process requires, where that data lands, what triggers next and how exceptions are handled. This avoids building a polished interface that creates more work behind the scenes.

AI-Enabled Advice Workflows

The practical opportunity for AI in advice is workflow-level assistance: meeting preparation, review preparation, summarisation, missing-information checks, document follow-up, knowledge retrieval and task routing.

I focus on small, auditable improvements with clear review points. The objective is to remove operational drag while preserving adviser judgement, privacy, accountability and the human relationship at the centre of advice.

Operating Principles

The objective is simple: fewer handoffs, cleaner data, and faster delivery. I fix constraints first, then choose tools.

Architecture Before Configuration

Roadmap, boundaries and ownership should be clear before technology decisions harden.

Workflow Automation

Automate repeatable work after the process is stable. Automation on messy workflows usually adds new friction.

Clear Implementation Governance

Set ownership, sequencing, and decision cadence so projects do not stall between teams.

Maintainable Execution

If an integration, internal tool or workflow cannot be run and maintained by its owner, it is not finished.

Systems and Stack Context

Typical environments include Fin365, Xplan, Adviser Logic, workflow engines, document systems, reporting layers, and API integrations.

Most projects fail on ownership, not tooling. I design the operating rhythm as carefully as the architecture.

Writing and Speaking

This site is the home of my essays, speaking and media profile and selected work.

Related Platforms

Luminair Capital

The business home for services, buyer-facing research, case studies and commercial enquiries.

Selected Work

First-party context on the systems, products and operating problems I have worked on.

Commercial Advice-Technology Work

I founded Luminair Capital to help advice firms design and build better client experiences, workflows and connected systems. Explore Luminair at https://luminair.au/.

Explore Luminair Selected Work

About Daniel Rickard

For background, positioning, and the homepage, see Daniel Rickard (Dan Rickard).