CRM layer
Fin365 and Dynamics 365
xLuminairFin365 / CRM Build Layer
Fin365 can be the base. The experience can be anything you need.
Fin365 can hold the operating record while the portal, Power Apps, Power Pages, workflow views, automation, and reporting read and write to the same Dataverse-backed source. One data layer. Multiple useful experiences.
Shared source
Dataverse-backed records
Experience layer
Portal, Power Apps, Power Pages
Outcome
No duplicate client data
Same data, two experiences
Edit either side. The record stays identical.
The portal and Fin365 are not separate copies. The client experience can read and write to the same Dataverse-backed source used by Fin365, Power Apps, Power Pages, workflow, and reporting.
Dynamics 365Fin365 CRM
SaveSend surveyCollaborateRecalculate
2211 - Steve Jobs - Get Started
OpportunityFin365 Software OpportunityOwner: Daniel Rickard
Software ProspectSoftware DemoSoftware Contract
Opportunity Summary
Workflow Status
Luminair PortalSecure onboarding
Welcome back, Steve Jobs
This client-facing form is writing to the same record shown in Fin365. Change a field here and the CRM side updates immediately.
Portal onboarding form
Fin365 as the operating core
Portal
Client dashboard and secure digital experience
Workflow
Visual status, service lanes, approvals
Power Platform
Power Apps, Power Pages, Dataverse tables
Automation
Notifications, handoffs, reporting hooks
Build Areas
The CRM becomes more valuable when the experience around it is clearer.
This work can be a focused integration, a workflow rebuild, a portal foundation, or a full digital product layer connected back into Fin365.
Data syncing
Connect client, household, advice, review, document, and service data to one source so Fin365, the portal, Power Apps, Power Pages, and reporting stay aligned.
Workflow visualisation
Turn CRM activity into usable operational views: lanes, cards, statuses, blockers, due dates, approvals, and handoffs.
Portal foundations
Use Fin365 as the CRM source behind a client portal so clients get a simple experience while the same Dataverse-backed record remains structured for the team.
Automation and service events
Trigger reminders, review events, data checks, document requests, adviser tasks, and internal notifications from shared CRM state.
Reporting and decision views
Expose the service rhythm: what is overdue, where onboarding stalls, which teams are overloaded, and what clients are actually doing.
Custom digital experiences
When the firm wants something beyond a portal - an education journey, a calculator, a client workspace, an adviser tool - Fin365 can become the data backbone behind it.
Where It Fits
Use Fin365 as the base, then build the missing product layer.
When the portal needs CRM data
We define which Fin365 and Dataverse records should surface to clients, which should stay internal, and how edits flow back without creating duplicate data.
When the team needs workflow clarity
We can design visual workflow views that make CRM state easier to understand for advisers, operations, client service, and leadership.
When reporting is too manual
We shape the data model and reporting hooks so Power BI and operational dashboards are reading from better structured shared activity.
When the experience needs to feel custom
We build the product layer around the client and staff experience, then connect it to Fin365, Power Apps, Power Pages, or Dataverse instead of making users navigate CRM complexity directly.
Delivery Rhythm
CRM work needs product thinking, not just configuration.
Audit the CRM reality
Understand the current Fin365 setup, data quality, workflow usage, integration points, and where the operating model is leaking time.
Map the experience layer
Define what should become a portal screen, an adviser view, a workflow board, a dashboard, or an automation path.
Build the bridge
Connect Fin365 to the right frontend, workflow, reporting, document, identity, and notification layers.
Make it usable
Test the flows, simplify the states, support launch, and keep improving the experience once real client and staff behaviour appears.
Next Step
Start with the CRM reality, then design what people should actually use.
If you already use Fin365, we can help shape the portal, workflow, reporting, and integration layer around the same data source. If the brief is still forming, the scope builder gives a practical starting point.