Every role the app actually has, from the head of family logging their first asset to the beneficiary who never opens the app at all. Journeys are built from what's implemented today, not aspirational flows.
Get everything they own arranged to skip the slow Faraid/probate queue, before anyone needs it to.
Creates the family and sets jurisdiction
Signs up, starts a family, picks Malaysia/Singapore/UK once in Settings — this quietly drives every legal note downstream.
Logs everything they own
Property, cash, vehicles, business interests, digital assets — each with ownership share, then attaches proof (title, grant, cover note) for later verification.
Sees the gap, not just the data
Coverage Dashboard shows the exposed percentage; the recommendations list turns that into a specific next tab to open.
Closes the gap with the right instrument
Hibah for immediate lifetime gifts, Family Waqf for a dedicated corpus, Nomination Registry for EPF/Takaful/bank mandates/trusts/business continuity/digital custody.
Writes the discretionary third
Bequests non-heirs within the one-third cap, generates a draft will document, and requests a professional's review before treating it as final.
Rounds out the picture
Logs Takaful/insurance policies, runs the Zakat check, builds the family tree with photos, and sets up their own death-trigger attestors — though they can never fire their own trigger.
Delegates
Invites a mutawalli/agent and other adult family members, so the estate outlives any one person managing it alone.
Handle their own share of the estate planning without needing to run the whole family's affairs.
Accepts an invite
Joins a family the owner already created — no family of their own to set up.
Sees the shared estate, adds to it
Views family-wide Assets, Hibah, and Nominations; can add assets and confirm another member's asset as a second witness — but can't manage who's in the family.
Authors their own documents
Their Wassiyah, Waqf, Insurance, and Zakat are theirs alone — visible to the mutawalli for execution, invisible to other members.
Adds themselves to the tree
Places themselves and their relatives in the family genealogy, with photos where they have them.
Execute what the family already planned, exactly when it's needed — and never for themselves.
Accepts the mutawalli invite
Joins with agent-level access; switches into this family from any others they already serve.
Reviews each member's documents
Picks a member from the chip list, reads their Wassiyah, Waqf, and insurance, and checks whether professional review has been requested or completed.
Sets up the trigger for that member
Executor name, death certificate reference, two attestors who each confirm independently — never for the member who happens to be themselves.
Fires it, and notifies heirs
Once both attestors confirm, fires the trigger and sends the automated heir-notification email — a real send, not a preview.
Works the execution packets
Uses the per-asset packets generated for each covered instrument to actually carry out the transfer.
Serve several unrelated families as their appointed trustee, without one family ever seeing another's affairs.
Holds the same role across families
Accepts separate agent invites from each client family, all under one login.
Switches, executes, switches again
Every action — trigger status, attestor count, review state — is scoped to the active family and the specific member, so firing one client's trigger can never touch another's, even if the same person happens to belong to both.
Find out what was left to them, without needing to have planned any of it themselves.
Named, not signed up
A family member enters their email against a Wassiyah bequest or a Waqf beneficiary — the heir never touches the app at this point, or maybe ever.
Gets one email, once
After the mutawalli confirms death and fires the trigger, an email lands in their inbox — sent through the app's own mail relay, not a third-party marketing tool.
Give a real legal opinion on a draft before a family relies on it — without the app pretending to replace them.
Contacted outside the app
A family member marks their Wassiyah "review requested" and reaches out directly — no in-app marketplace or booking.
Reviews the actual draft
Reads the generated will document — clearly watermarked as a draft, not a claim of legal validity — with jurisdiction-specific notes already flagging what execution requires.
Sign-off gets recorded
The family member marks it "reviewed" with the reviewer's name — visible to the mutawalli from then on.
Grandparents, deceased relatives, young children — most nodes in a real family tree have no account and never will. Anyone with access adds them as a lightweight person record with a name, dates, and an optional photo, and can link them to a real account later if one gets created. They're a data subject in this app, not a user of it.