Ficus is an infinitely flexible financial modeling workspace. Start with a blank canvas, describe the portfolio you actually have, review every proposed change, and turn approved data into dashboards for individuals, advisors, wealth managers, and family offices.
Chat, data, dashboards, and approvals in the same surface.
The core loop is intentionally simple: ask the agent, inspect the proposal, approve the changeset, and let compiled widgets update from approved data.
FFicusPersonal / Net worth
ReadyNP
Pip Agent
Ready
Chart my net worth over the last year
PIP
Done - your holdings valued daily against live market prices, summed for the trailing 365 days.
Total Net Worth USDwidget
Ask Pip to model anything...
Net worth
$232,299
$30,140 | 30d+18.4% | 1y
1M3M1YAll
Holdings by fund
VTI$142k
VXUS$57k
Cash$33k
Allocation
Equity 58%
Cash 27%
Other 15%
Who Ficus supports
One flexible model, four levels of operating complexity.
Ficus does not ask users to conform to a preset portfolio template. The same approval boundary and semantic data model scale from one person tracking a portfolio to a firm managing many client workspaces.
Complex wealth
Model the family balance sheet without forcing it into someone else's schema.
Ficus gives family office teams a controlled workspace for modeling total wealth without hard-coding a single asset class, tax view, reporting convention, or ownership vocabulary.
Track ownership structures, private holdings, cash, liabilities, market positions, and custom settings in one tenant-local model.
Attach documents to conversations and preserve provenance when those files justify a changeset.
Run repeatable workflows for planning questions, scenario outputs, and board-ready dashboards.
A financial model should fit the life it is supposed to support.
Whether the question is a single household plan, a client conversation, or a multi-entity family office dashboard, Ficus lets the model follow the portfolio instead of forcing the portfolio into a template.
custom assetsprivate holdingsscenario dashboardsapproved changes only
Feature catalog
Everything is built around the approval boundary.
Ficus is intentionally generic underneath. That is the source of the flexibility: personal models, firm templates, complex family office structures, and new planning workflows can all exist without baking user-specific finance concepts into platform code.
AI cannot directly mutate financial data.It proposes. Ficus validates. The user approves.
Blank workspace modeling
No asset class, currency, tax, or net-worth assumption is forced into a new tenant. The model grows from the user's approved intent.
AI proposal loop
The agent can propose entities, fields, records, settings, widgets, projections, and templates without bypassing review.
Reviewable changesets
Every financial mutation passes through approve or reject, with business impact, preview rows, operation detail, and durable history.
Semantic widgets
Widgets come from query specs, not raw AI-authored SQL. Ficus compiles and validates read-only SQL for approved chart surfaces.
Live dashboards
Users can create, duplicate, publish, rearrange, and pin chart and table widgets as their model and market data evolve.
Bank projections
Connected feeds stay raw until a reviewed projection maps transactions or holdings into the model with record lineage.
Documents and provenance
Files can be stored in Ficus, attached to conversations, routed for approval, and linked as evidence for later changesets.
Templates
Strong workspace slices can become reusable, versioned templates containing entities, settings, widgets, and dashboards.
Workflows and scenarios
Guided workflows collect facts and tweakable inputs, then produce repeatable scenario metrics, widgets, and narratives.
Workspace isolation
Tenant, workspace, member, operator, and admin boundaries are explicit so client data does not blur across contexts.
Public dashboard safety
Published views expose only what the read-only UI needs, never raw widget SQL, tenant IDs, workspace IDs, or full query specs.
Operational controls
Admin and operator portals cover users, firms, access grants, profile-only accounts, temporary passwords, and rate-limit relief.
Control and trust
Flexible enough for real wealth. Bounded enough for review.
Ficus keeps the agent useful by surrounding it with durable contracts: tenant isolation, structured proposal validation, read-only generated SQL, document provenance, and explicit human approval before mutation.
Tenant isolation
Workspaces, operators, users, and public views are scoped so data stays in the right context.
Semantic query layer
Charts are generated from validated query specs over approved read surfaces, not free-form AI SQL.
Client-ready surfaces
Dashboards, documents, and scenarios are useful for conversation without forcing technical details up front.
Approval ledgerlive workspace
Agent proposesAdd private fund capital call scheduleproposal
Document attachedQ2 capital account statementevidence
