FAQ
Questions clients ask before they engage.
Clear answers on mandate scope, onboarding, confidentiality, technology, and how the platform supports complex wealth in practice.
Before Engagement
Anticipating the obvious questions.
These are the practical questions prospects and family principals tend to ask before they trust a private office with sensitive information and operating responsibility.
Who is Hautelaire designed for?+
Hautelaire is built for principals, entrepreneurial families, and family offices managing complexity across multiple entities, custodians, jurisdictions, and advisor relationships. It is most relevant when coordination, reporting, and governance matter as much as investment selection.
How is this different from a wealth management app?+
Traditional apps focus on aggregation and personal finance. Hautelaire adds family-office operating layers: entity oversight, document governance, cashflow orchestration, meeting support, advisor coordination, and controlled access to sensitive information.
Do you replace banks, lawyers, accountants, or asset managers?+
No. We coordinate them. The objective is to create a clear operating model around the existing advisory network so the family has one decision-ready picture rather than fragmented reporting from multiple providers.
What does onboarding look like?+
Onboarding starts with a confidential discovery phase, followed by structure mapping, data-source review, access design, and reporting configuration. We then phase the mandate into live operations with agreed priorities, cadence, and governance checkpoints.
Can the platform support clients based in France?+
Yes. The product model is well suited to families operating between France, Switzerland, Luxembourg, Belgium, and the UK. Before launch, the legal wording, regulatory disclosures, and privacy language should be tailored to your exact operating structure and client base.
What can clients actually do in the portal?+
Clients can access documents, review reports, monitor wealth and cashflow, track dividends, review entities, manage meetings, submit requests, and follow operational alerts. The portal is designed to reduce back-and-forth while preserving discretion.
How are confidentiality and access handled?+
The intended production architecture uses role-aware access control, auditable document events, MFA, session controls, and secure storage. The current codebase demonstrates the product shape; the next step is connecting the auth and storage layers to production services.
How selective is the mandate process?+
Deliberately selective. The model is designed for deep service rather than volume. That usually means a structured qualification process, mutual due diligence, and a phased engagement rather than instant self-serve onboarding.
If the questions are specific, the answer should be too.
We welcome confidential conversations with families and principals who want to assess fit, operating model, reporting scope, and implementation depth.
Submit a confidential inquiry