Trust should feel human and visible, not hidden behind policy language or insider access.
Helping each other. Building wealth. Properly governed.
Shared protection and collective wealth, governed in the open.
Helpmekaar is a community-driven stokvel platform for invite-led members who want disciplined investing, emergency protection, and visible rules.
Invite-led entry
New members join by invite or governed onboarding, not anonymous self-registration.
Visible rules
Money, support, and governance steps stay understandable before deeper detail appears.
Role-safe routing
One sign-in resolves the right member, governance, or rails surface after authentication.
Visible rules
Trust starts before any protected route opens.
The public front door should explain the entry model, the governance boundary, and the next safe step without making anonymous visitors feel like they are already inside Helpmekaar.
What a new visitor should understand first
rulesInvite-led entry stays explicit
New members continue through invite or governed onboarding. The public route should not imply open anonymous self-registration.
One sign-in opens the right surface
Returning member, governance, and rails actors all start from one bounded auth route before Helpmekaar resolves the correct signed-in context.
Duty work stays visibly separate
Sponsor, committee, trio, auditor, and rails work only appear as named duty switches after sign-in, not as hidden admin power.
Next safe step
Choose the right front door
entryUse sign-in if you already belong here. Use invite-led onboarding only if you are continuing a governed entry path.
Helpmekaar does not use open anonymous self-registration, and member, governance, and rails context only begin after the auth handoff resolves safely.
How Helpmekaar Works
Understand the model in under a minute.
The public route should make the member journey, the duty boundary, and the route-ownership model easy to scan before a visitor commits to sign-in or invite continuation.
Helpmekaar starts with the right front door, then keeps member, governance, and rails duties visibly separate.
Enter through the right front door
step 1Existing actors sign in. New members join by invite or governed onboarding, not through open anonymous registration.
Helpmekaar should never blur returning actors with new invite-led entrants. The public route keeps the handoff visible so people do not guess whether they belong in sign-in, onboarding, or a protected route.
This keeps trust high before the session resolves into a member, governance, or rails route.
What Your Money Is Doing
The money model stays layered, visible, and honest.
The public explanation should show that liquid value, invested value, and pooled value are not the same thing. That honesty matters before members ever see wallet totals inside the app.
Rand Wallet
available nowFor money that is available now or moving toward payout.
Rand Wallet is the everyday movement layer. Funding outcomes, approved credits, release completions, and ready-to-withdraw value land here before the product implies that cash can leave immediately.
Members should read this as the liquid layer, not as a summary of every other pool.
Members should understand where money sits and what it can do before a route implies cash is already free to leave.
Liquid, invested, pooled, and governed value stay visually separate so members do not confuse total value with direct cash.
Support When Life Happens
Difficult states should still feel respectful and specific.
The support story should show what is true now, who owns the next step, and how recovery works. Sensitive moments should feel dignified, not vague or improvised.
Help should feel dignified and concrete, especially when a member is already under pressure.
Support paths should show state, owner, and next step clearly instead of collapsing into vague reassurance.
Support when life happens
Difficult states should still feel respectful and specific.
Claims and support routes show the current state, next owner, and next action.
careWithdrawal and exit routes explain what is already true and what is still waiting.
careSigned-in routes stay calm in difficult states and avoid hype or vague reassurance.
careEntry Rules
What is true before you are inside Helpmekaar.
Members, governance-duty holders, and rails actors all sign in through one bounded auth surface. Invite-led onboarding stays explicit, and role separation stays visible once the session resolves.
FAQ / Trust Centre
Answer the obvious trust questions directly.
Trust grows when the visible rules, the support path, and the entry model can be read without insider knowledge or vague marketing language.
Trust grows when the visible rules, the support process, and the governance path can be read without guessing.
No. New members continue through invite or governed onboarding. The public home should not suggest open anonymous self-registration.
Yes. One sign-in surface resolves the correct actor context after authentication.
Yes. Member context still comes first, and duty work opens as an explicit switch.