Portfolio Management
Orion Workflow Automation for RIAs
Orion can keep doing the portfolio-accounting, performance, and reporting work it's built for. Advisor Nexus connects that context to the workflows around it, meeting prep, client service, planning, and documents, so permitted Orion data moves into the rest of your stack with less manual assembly.
Diagram: people and work (advisors, operations, client service, compliance, and clients) use Microsoft 365 — Outlook, Teams, SharePoint, and calendar — for communication and documents. The Advisor Nexus workflow and intelligence layer sits between that and the firm's wealth-management systems (CRM, custodian, planning, portfolio, documents, and e-signature), providing workflow orchestration, deterministic automation, supervised AI, human approvals, and exception handling, following the operating model connect, gather context, interpret, act, review, deliver. Advisor Nexus sits between these systems rather than replacing them, and work can move in both directions.
In short
An RIA can use permitted Orion portfolio and account information as part of connected workflows involving CRM, meeting preparation, client service, planning, and documents. Depending on Orion's APIs, permissions, product configuration, and the firm's surrounding systems, Advisor Nexus can help gather portfolio context, route operational work, prepare downstream actions, and coordinate cross-system workflows, while portfolio accounting, trading, and other specialized investment functions stay in Orion and under the firm's existing investment controls.
Role in the RIA Tech Stack
What Orion Handles, and What It Doesn't.
Orion handles
- Portfolio accounting, positions, and performance data, the data foundation Orion's own trading, reporting, billing, and planning modules read from
- Investment performance reporting, including its own Denali AI-driven Report Assistant and Query Studio for natural-language data questions
- Trading and rebalancing, where the firm uses Orion's trading tools
- Client and advisor portal delivery of portfolio and performance information
It does not replace
- CRM client-relationship, activity, and task records
- Custodian systems, which remain authoritative for custodial records and servicing
- Financial-planning software
- Microsoft 365 communication, calendar, and documents
- Firm-specific service and approval workflows that span more than one system
Advisor Nexus is the workflow and orchestration layer that uses permitted Orion context inside firm-specific workflows, not a portfolio-accounting platform, a trading system, or a reporting replacement. The objective isn't to duplicate what Orion already does; it's to bring portfolio and performance context into the CRM, meeting, planning, and service workflows that involve more than one system, with Orion remaining the source of truth for portfolio and investment data.
Example Connected Workflows
What Connecting Orion Looks Like in Practice.
Client Meeting Preparation
Household context from the CRM combines with permitted Orion portfolio and performance data and planning information into one reviewed brief before the meeting.
- Upcoming meeting identified
- Household identified in CRM
- Permitted Orion account, portfolio, and performance context retrieved
- Planning context gathered where supported
- Recent CRM and email context reviewed
- Brief prepared
- Advisor review (human review point)
Meeting Follow-Up With Portfolio Context
A portfolio-related discussion point becomes a proposed task or service workflow, not an executed instruction. Any trade or investment decision stays with the advisor and Orion's own investment controls.
- Meeting ends
- Approved notes or transcript retrieved
- Portfolio-related follow-up identified (a review request, an allocation question)
- Relevant Orion context gathered
- Task or service workflow prepared
- Advisor review (human review point)
- Approved downstream action
Client-Service Request With Account Context
An account or reporting question becomes a routed, owned task informed by permitted Orion context, not just a CRM note.
- Client request arrives
- Client identified in CRM
- Relevant Orion account context gathered
- Request classified (account question, reporting request, document need)
- Task routed to owner
- Custodian or document workflow initiated if appropriate
- Human review (human review point)
- Completion recorded
Reporting and Review Preparation
Orion's own Denali AI, including Report Assistant and Query Studio, can already draft client reports and answer data questions inside Orion. Advisor Nexus becomes useful when that reporting or review workflow needs to combine with CRM, planning, or Microsoft 365 context beyond Orion, or trigger follow-up work in another system.
- Scheduled review or reporting workflow begins
- Relevant clients and accounts identified
- Orion portfolio and performance context gathered where supported
- CRM and planning context combined
- Internal review materials prepared
- Human review (human review point)
- Approved output delivered
Cross-System Data and Exception Workflow
A mismatch between Orion, the CRM, and planning records becomes a routed task instead of a discrepancy nobody notices until it matters.
- Approved portfolio or account condition identified
- Compared against CRM and planning records
- Mismatch or exception identified
- Task created and owner notified
- Human investigation (human review point)
- Approved update applied in the appropriate system
How It Works
How the Connection Works.
- The Orion developer platform (Orion Connect / Integrations API), with API-key or OAuth authentication and firm-specific service credentials, for permitted portfolio, performance, and account data
- Orion's documented notification webhooks, where configured, for alerts to a registered endpoint
- Microsoft Graph, for the Microsoft 365 side of a workflow
- CRM and other vendor APIs, where available
- Scheduled synchronization for data that doesn't require an immediate write
- Custom orchestration for logic beyond what a single connector covers
Works Alongside
Systems Commonly Used Alongside It.
See our Microsoft 365 integration. See our Redtail integration. See our Wealthbox integration.
Connected Does Not Mean Uncontrolled
Every Connection Has a Boundary.
Deterministic automation
- Detecting a scheduled review, meeting, or workflow trigger
- Retrieving permitted Orion, CRM, and planning context
- Creating and routing tasks
- Notifications and status updates
- Flagging a data mismatch or exception
Supervised AI
- Summarizing portfolio-related meeting discussion
- Drafting internal briefing language from combined context
- Identifying a potential follow-up topic or service request
- Synthesizing CRM, planning, and portfolio context into one brief
Human authority
- Investment recommendations and trading decisions
- Portfolio or allocation changes
- Confirming a client instruction
- Suitability and financial-judgment calls
- Consequential client-facing communication
- Any compliance-sensitive decision
Security & Limitations
What to Confirm Before You Rely on It.
- What a workflow can read depends on the specific Orion products the firm uses; Portfolio Accounting, Trading, Reporting, Billing, Planning, and Risk Intelligence are separate modules that don't all expose the same data or actions.
- API and integration access require firm-specific credentials provisioned through Orion, and permissions vary by product and deployment.
- Orion documents notification webhooks for registered endpoints, but availability and configuration depend on the firm's Orion setup, not something to assume by default.
- Orion does not publish a public rate limit; a production workflow should still be designed to handle throttling gracefully.
- Every automated action is scoped to least-necessary access, logged, and subject to a defined exception path.
- This is not an Orion partnership, certification, or compliance guarantee. Firms remain responsible for their own regulatory, suitability, and recordkeeping obligations.
- Advisor Nexus does not place trades, change portfolio models, or make investment decisions; those stay with the advisor and Orion's own investment tools and controls.
Go Deeper
Related Reading and Solutions.
Common Questions
Questions About Orion.
Portions of the work around Orion can be, using permitted portfolio and account context to support CRM, meeting, and service workflows. Portfolio accounting and trading stay inside Orion's own tools and controls.
Yes, where the firm's Orion permissions support it. Portfolio, account, and performance context can be combined with CRM and planning information into a reviewed meeting brief.
Orion has its own CRM, Redtail, which it acquired in 2022 and has integrated closely for years. With other CRMs, workflows can coordinate Orion and CRM context together, depending on each platform's API availability and the firm's configuration.
Orion context can participate in a Microsoft 365 workflow, for example a meeting brief delivered into Outlook, through Advisor Nexus's orchestration rather than a direct native Orion-to-Microsoft integration.
Yes. Portfolio and planning context can be gathered together for meeting preparation or a review workflow, depending on API availability for both platforms.
Yes, for context like account information or a reporting question, where permitted. Custodians remain authoritative for custodial records and servicing.
No. Orion remains the firm's portfolio accounting, performance, and reporting platform; Advisor Nexus connects the workflow around it.
No. Advisor Nexus is not positioned to autonomously make or execute investment decisions. Trading and portfolio changes stay with the advisor and Orion's own investment tools, permissions, and supervision.
Investment recommendations, trading and portfolio changes, suitability judgments, and any consequential client communication drawing on portfolio context.
Start With Clarity