One platform for the whole advisor team.
The prototype brings together attribution, portfolio calculations, four workbook transforms and an Alpha interface. A pilot would connect these tools to approved data, identity and job scheduling. Team and partner views are available as demos; firm deployment and client access have not been established.
The work between the systems.
The starting point is the work between an advisor’s systems: spreadsheets, recurring preparation and requests that need a clear owner.
The demo shows how workbook calculations, research and a request queue could fit together. Its account records, service metrics and handoff examples are fictional. Email, calendar and CRM connections still need to be built and verified.
Start with one recurring task and prove the result before expanding the scope.
This is a proposed implementation plan. It does not represent an approved vendor relationship, a firm endorsement or a completed deployment. A pilot would establish the permissions, data boundaries and measured value of each workflow with its participating team.
An illustrative day, and the proposed workflow.
Answered by the next available member of the team.
Capped by headcountAlpha would answer from approved material and prepare a handoff when a person is needed. Response time would be measured.
Proposed work and acceptance criteria.
Alpha and the foundations
Phase 1, internal faceW1Approve hosting and data boundariesDeployment verified in a firm-managed environmentW2Job runner for the four VBA projectsOutput matches the hand-run result exactlyW3APIs for attribution and the optimizerSame output as running them directlyW4Unified dashboardEvery tool reachable from one domainW5Alpha, the engine, on firm computeCalls only approved models and drives every job and tool
Alpha service skill
Phase 2, after Phase 1 is stableW6Alpha answers requests itselfSource quality, permitted actions and handoff receipts verified; response times measured with the team
External face
Phase 3, after its own compliance reviewW7Client view and prospect pitchSame engine and confirmed data, approved language only
Every FA team
Once the pilot has measured resultsA team edition for advisor groups across the firm, and an advisor edition for individual FAs
Start with a workbook and an inspectable result.
The demo can calculate exposure and compare a holdings workbook with an illustrative model in the browser. Start with sample or sanitized inputs, inspect missing values and assumptions, and review the output. Statement extraction, live market pricing, approved proposal templates and firm data access remain pilot work. The durations below are planning examples, not measured savings.
External skills
Candidate workflows- Standing relationship, not a newsletterAdvisor + CSA, about 180 min planning example
- Bond comparisonCSA, about 40 min planning example
- Transition planAdvisor + CSA, about 90 min planning example
- Client questions, answeredCSA, about 15 min planning example
- Send the right documentCSA, about 10 min planning example
- Money movement intakeCSA, about 25 min planning example
- Account opening and transferCSA, about 60 min planning example
Internal skills
Candidate workflows- Daily flows and trade preparationCSA (trading), about 120 min planning example
- Advisor inbox loadAdvisor, about 90 min planning example
- Partner advisor questionsCSA / advisor, about 20 min planning example
- Maturity and call reinvestmentPM + CSA, about 45 min planning example
- Drift and rebalancePM, about 30 min planning example
- Credit event responsePM + CSA, about 60 min planning example
- Attribution and commentaryPM, about 240 min planning example
How they run, and improve
Pilot controls to verify- ActsProposed: approved routine tasks with completion receipts
- Acts within limitsProposed: tasks with explicit firm-set limits
- ProposesA PM or advisor reviews judgment calls
- LearningExperimental replay and evaluation; no automatic changes to facts, rules or permissions
Success is measured, not claimed.
No pilot results yet. This page will report them once the pilot has run.
Before using firm data.
A pilot requires an approved environment, named technical owner, identity and role integration, approved model endpoints, access logging and tested retention and deletion controls. These are acceptance requirements, not properties of the hosted demo. The demo uses an access code and ARCANE services; it is not connected to a firm’s production systems.