Operations teams
Find the recurring work where files, approvals, exceptions, and evidence do not line up cleanly.
- Client and fund onboarding
- Reconciliation and exceptions
- NAV and valuation checks
- Administrator and custodian files
Solutions
Solutions for the operational work that falls between systems.
Fontana starts with the seams buyers already recognise: onboarding, analysis, reconciliations, valuation checks, files from administrators and custodians, and governed AI-assisted operations.
Find the pain your team already works around.
Each solution begins with a real operational seam, then applies the same Fontana control pattern: govern the logic, run deterministically, and create evidence as the work happens.
1 Operations
Client and fund onboarding
Bring new clients, funds, accounts, feeds, rules, and approvals into a reusable operating pattern instead of rebuilding each onboarding from scratch.
Onboarding Rules capture Reusable logic
Explore solution →
2 Operations + technology
Data analysis and operating specification creation
Turn source files, reporting requirements, field-level decisions, and SME knowledge into review-ready operating specifications and evidence.
Source analysis Specs Evidence
Explore solution →
3 Operations
Reconciliation and exceptions
Detect breaks, assign ownership, route exceptions, preserve evidence, and reduce repeated root-cause analysis across recurring controls.
Breaks Ownership Routing
Explore solution →
4 Operations + risk
NAV and valuation checks
Run recurring NAV, valuation, and position checks faster while keeping tolerances, approvals, lineage, and replay explicit.
Checks Tolerances Replay
Explore solution →
5 Operations + technology
Administrator and custodian files
Govern intake, validation, normalisation, mapping, exception handling, and downstream evidence for files that change shape across providers.
File intake Validation Normalisation
Explore solution →
6 Technology + operations
Governed operational agents
Use agents to assist analysis, drafting, and explanation while approved controls decide what can run and deterministic workflows execute.
AI assistance Approval gates Model governance
Explore solution →
Different buyers see different seams. The control pattern is shared.
The overview should let operations, technology, and risk/compliance teams recognise their own pressure points without forcing them through internal product taxonomy.
Technology teams
See where workflow logic, integrations, model use, testing, and replay need a governed execution boundary.
- Data analysis and operating specifications
- Administrator and custodian files
- Governed operational agents
Risk and compliance teams
Track the control pattern: owners, approvals, lineage, exception history, replay, and audit evidence by default.
- Exception routing
- Approval history
- Lineage and replay
- Audit evidence
The same governed pattern applies across operational seams.
Fontana is not a pile of disconnected point automations. The work varies; the control model stays consistent.
Messy input
Files, feeds, PDFs, emails, exports, exceptions, and local process knowledge arrive in inconsistent shapes.
Governed interpretation
Rules, mappings, standards, assumptions, and operating decisions are captured for review and reuse.
Approved controls
Owners, tolerances, approval gates, and exception paths determine what can become accepted process.
Deterministic run
Approved workflow logic executes predictably rather than relying on ad hoc judgement or black-box AI.
Exception routing
Breaks are assigned, escalated, explained, and tracked with the surrounding decision context.
Evidence by default
Lineage, approvals, replay context, versions, and audit evidence are created as part of the work.