Private solutions
Six focused mandates for the moments when family geography, capital, property, education, and protection can no longer be handled as separate projects.
Find the right starting point
How should your family’s global life fit together?
A founder-led architecture of residence, capital, property, education, protection, and legacy — viewed as one system.
A clear target architecture, three scenarios, and the next three moves.Where does the family go if the primary base stops working?
A practical fallback geography built around legal access, readiness, schooling, liquidity, and real-world usability.
A reserve-base brief with activation priorities and dependencies.Which status supports the life you actually want?
A comparative route assessment that separates place to live, tax residence, business base, and long-term optionality.
A compliant shortlist for review with licensed immigration and tax counsel.What if the children’s next ten years choose the country?
An education-led migration plan connecting curriculum, admissions timing, family rhythm, and university pathways.
A family geography designed around the children’s real trajectory.What job should each property perform?
A portfolio view of homes, income assets, reserve bases, student housing, and legacy property across jurisdictions.
Role-based property criteria before any broker or listing is selected.Where are the hidden points of failure?
A coordinated review of digital exposure, travel readiness, home security, insurance, emergency access, and continuity.
A prioritised risk register and licensed-specialist implementation map.A deliberate boundary
Nomad Nova frames the mandate, helps select the right specialists, keeps the workstreams connected, and challenges recommendations against the agreed family architecture. Licensed professionals remain responsible for regulated advice and execution in their jurisdictions.
A private conversation
Tell us which parts of the family’s global life no longer fit together. The right starting product usually becomes obvious from the dependency.
Share the context