Explore The Fund Onboarding Platform
screen by screen
This walkthrough shows what each screen is for, who uses it, and how it supports sponsors, AIFMs, administrators, and law firms through the same launch lifecycle.
Each module shows the screen, the buyer, and the actual use case
The previews below are screenshot-style representations of the live product. Each section explains what a buyer is looking at, why it matters commercially, and when that screen becomes useful in a real Luxembourg fund launch.
See every client launch in one portfolio view
This is the entry point for multi-client delivery. It shows where launch pressure sits across the portfolio before teams disappear into individual files.
Use one project cockpit as the source of truth for a launch
The cockpit condenses execution, control readiness, approvals, external pressure, and AI summary into the first screen buyers will care about.
Control execution with a workplan built for launch delivery
This screen tracks who is doing what, when it is due, what sits on the critical path, and which actions are driving the launch date.
Track launch risks in operational terms, not generic audit language
The risk register shows what could slip the date, undermine governance readiness, or create post-launch control issues if left unmanaged.
Separate today’s blockers from the dependency chains behind them
This screen is where teams track live issues, required decisions, and the dependency chains that explain why a single slip has wider impact.
Manage documents as live launch controls, not a passive filing list
The document register links version status, review state, blockers, and evidence coverage back to the launch plan and go-live logic.
Turn launch readiness into an explicit verdict backed by evidence
This screen converts project activity into a go, conditional-go, or no-go recommendation that stakeholders can actually defend.
Use AI to summarize the launch, not replace judgment
The AI layer turns a dense delivery record into briefings, follow-up prompts, and control observations that help teams act faster.
Bring external parties into the process without opening the whole workspace
This screen gives each provider a clean delivery lane while keeping internal oversight, auditability, and evidence linkage intact.
Manage launch timing as a chain of gates, not just dates in a list
The calendar shows which milestones matter, what they depend on, and how slippage changes downstream launch planning.
Monitor the operational systems that launch delivery depends on
Readiness depends on tools and feeds as much as documents and meetings. This screen surfaces those operational dependencies before they fail silently.
Export packs from the live launch record, not from offline status decks
This screen ensures boards, CSSF follow-up teams, and launch committees receive reporting that reflects the current project truth.
Run multiple launches with a clear functional ownership model
This screen rolls up ownership, pressure, and workload across the portfolio so multi-client teams can see where they are stretched before delivery breaks.
Want the live workspace behind these screens?
Start with the AI-generated launch baseline, then use the same modules for execution, counterparties, approvals, dependencies, and governance reporting.