Luminair
Platform for advice-tech strategy, system architecture, and practical implementation sequencing.
Advice-Tech CTO. I help financial advice firms build the operating layer behind better client experiences: portals, CRM architecture, workflow automation, reporting and AI-enabled delivery.
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.
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.
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.
The objective is simple: fewer handoffs, cleaner data, and faster delivery. We fix constraints first, then choose tools.
Define roadmap, architecture, and boundaries so technology decisions match business reality.
Automate repeatable work after the process is stable. Automation on messy workflows usually adds new friction.
Set ownership, sequencing, and decision cadence so projects do not stall between teams.
Build integrations, internal tooling, and workflow services that your team can run and maintain.
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.
If you want a sense for how I think about investment governance and real-world decision-making, start here: Bridging the Gap: Understanding Small Cap Premium.
Platform for advice-tech strategy, system architecture, and practical implementation sequencing.
Client context that keeps system priorities tied to delivery outcomes and constraints.
Career context across advisory leadership, platform strategy, and execution environments.
If you are unsure where to start, send your current stack and bottlenecks. I will outline the next practical step.
For background, positioning, and the homepage, see Daniel Rickard (Dan Rickard).