FUNDING DESK · UK · AI workflow and agent platform for wealth management (RIAs, multi-family offices and large wealth firms)
Nevis
Nevis is an AI operating system for wealth management firms that unifies meeting, email, CRM, custodian and performance data into one layer, using agents and workflows to automate advisors' administrative and middle/back-office work.
Company website ↗First-party material retrieved
Last retrieval:2026-11-09
Evidence gaps:Pricing · Technical documentation
It replaces advisors manually writing meeting notes, creating tasks one by one, switching tabs between CRM and custodian systems, opening accounts and moving money by hand, and juggling separate tools for meeting records, email drafts and task tracking.
The key commercial judgment is that in wealth management the value of AI lies not in a standalone chatbot but in packaging agents, data connections and auditable workflows into a single platform that can replace the existing stack; defending that position depends on deep custodian and CRM integrations and compliance trust, not on the model itself.
The following is editorial analysis based on public material. Inferences and open questions are labeled in the text. Funding is not evidence of revenue or product-market fit.
Product evidence checked 2026-11-09
01
What the product does
The site describes the product as "the AI operating system for wealth," built from four layers: agents for repeat work such as meeting prep and data collection; workflows covering Schwab and Fidelity account opening, cashiering and money movement plus custom processes; a data layer with native connectors to CRM, custodians and performance reporting; and a desktop that pulls advisors' tools into one place. The platform page also shows meeting recording and transcription, automatic task creation, AI-drafted client emails, shared notes and comments, voice commands and management dashboards. The scope clearly exceeds a point-solution meeting assistant, but the site gives no separate pricing, implementation timelines or availability details per module.
02
Users, buyers and demand
Users are advisors, associates and middle/back-office operations staff at wealth firms; the payer is typically the firm rather than an individual advisor. Pain points center on missed post-meeting follow-ups, repetitive manual account opening and money movement, cross-system switching and compliance record-keeping. The customers page names Focus, United Capital, IEQ Capital, GC Wealth, Dodds Wealth, Wedmont and AlTi, and claims coverage from national RIAs to multi-family offices. Pain frequency is high: meetings, emails, account opening and money movement are daily actions, so automation value is measured in hours saved per advisor per week.
03
The actual workflow
A typical flow: a client meeting is natively recorded and transcribed, the system generates summaries and action items, and tasks are created and assigned automatically; AI then drafts follow-up emails from the conversation while the team shares notes and comments in one place; when an account must be opened or money moved, the workflow executes directly against custodians such as Schwab and Fidelity without manual entry; management views adoption, activity and growth on dashboards. The site also shows voice commands creating tasks and agents generating review agendas in bulk or spotting attrition-risk clients. The chain runs from inputs (meetings, emails, system data) to deliverables (tasks, emails, account openings, reports) inside one platform.
04
Pricing and unit economics
The site discloses no pricing page, billing unit or contract structure, so it is not possible to determine whether it charges per advisor seat, by AUM or by module, nor to compute contract value or gross margin. What can be inferred: institutional sales, native custodian and CRM integrations, SOC 2 Type II auditing and enterprise agreements with multiple model providers typically imply long sales cycles and high implementation costs, so unit economics depend on expanding seats and workflow count within each firm. This is inference, not company-disclosed fact.
05
Adoption evidence and gaps
Company-reported figures include over $700B in AUM across customers, 90% weekly active usage, 8+ hours saved per advisor per week, 1,000+ back-office workflows automated per month, SOC 2 Type II compliance, and enterprise agreements with OpenAI and Anthropic under which private client data is not used to train models. The customers page names several firms and case studies. All of this is company-reported and not independently audited; retention, net revenue retention, paid seat counts and contract values are missing.
06
Competition and defensibility
Versus general-purpose models, Nevis's differentiation is not model capability but native custodian and CRM connections, automation of regulated actions such as account opening and money movement, and compliance commitments including SOC 2 and no training on client data; these make it hard for a generic chat tool to substitute directly. Versus the old process, it collapses scattered tools into one layer and reduces switching costs. The moat holds only if integration depth stays ahead, regulatory or security incidents do not erode trust, and clients do not bypass the platform to build their own as model prices fall. If model vendors or custodians launch similar workflows, the moat narrows.
07
How to read this round
This is a Series B; the amount and native currency are rendered by the deterministic layer, the investor list includes several institutions and an angel, but the list is not a lead-investor list and the use of proceeds is not disclosed in the evidence. The stage indicates the company has moved from early product validation to institutional deployment, and the funding supports expansion rather than proving demand. The next milestone should be converting the published customer stories into a repeatable enterprise deployment playbook, broadening custodian and CRM integration coverage, and demonstrating seat expansion and retention within firms.
08
Where it could fail
First, an error or compliance incident in regulated workflows such as account opening or money movement could quickly damage trust across a client base that manages hundreds of billions in assets. Second, if model vendors or custodians offer similar agents and workflows, Nevis's integration advantage could erode and clients may build in-house to reduce vendor dependence. Third, with no pricing or documentation on the site, high implementation cost and long deployment cycles could make growth dependent on a few large clients, raising revenue concentration risk.
09
What you can take from it
A transferable lesson is to embed AI in regulated, high-frequency, cross-system actions (account opening, money movement, meeting follow-up) rather than selling a generic assistant; build switching costs through native integrations and compliance audits, and make adoption and hours saved quantifiable promises to clients. For founders, going deep on one high-friction workflow before expanding to adjacent ones is more viable than launching a broad platform at once.
10
What to watch next
The next verifiable indicators are whether the company discloses paid seat counts, net revenue retention or per-client expansion data, and whether it publishes pricing and product documentation so outsiders can check workflow coverage and implementation cost. Another question worth tracking is whether custodian integrations beyond Schwab and Fidelity expand, and whether any independent third party verifies its security and compliance claims.