What this guide answers
These are the questions people tend to ask first—whether they find this page on search or someone forwards the link. Skim the list, then read at your own pace. The headings below come back to each topic with plain language, examples, and habits you can reuse in your own circle chat.
- What decisions should be made in week zero before anyone configures Sousou?
- What belongs in week one (circle setup, invites, and “can everyone see the schedule?” checks)?
- How do you run the first collection so proof, cutoffs, and “send vs cleared” rules are explicit?
- How should you verify the first payout aloud—and what do you do if totals do not match?
- Which delays, documentation packs, and parallel roles prevent timelines from derailing after launch?
These guides use a calm, practical tone on purpose: money and friendships in the same room deserve clarity, not hype.
Most circles fail from impatience, not fraud. People rush invites before agreeing on proof, or they start collections before everyone has actually installed the app. A simple timeline keeps excitement high while sequencing decisions in the right order.
Week zero: social alignment before software
Hold a conversation (video, phone, or in person) covering amount, frequency, order, late policy, and rails. Capture decisions in a short note everyone acknowledges. Only then should the creator configure Sousou—otherwise you will edit settings three times and confuse early joiners.
Week one: configuration and invites
Create the circle, double-check currency, send invites, and host a fifteen-minute screenshare for anyone less comfortable with apps. Verify each member can see the schedule page. Troubleshooting login issues now saves midnight panic before the first due date.
First collection period: execute deliberately
Announce recipient zero (or first in order), restate due date, and pin payment instructions. As payments arrive, mark them promptly. If someone’s bank delays settlement, document whether the round officially closes on “send” or “receive” so expectations stay aligned with bank reality.
First payout: verify totals aloud
On payout day, read the expected total from Sousou while the recipient confirms their account balance after transfers finish. Applaud—literally—when numbers match. If they do not, pause and investigate before starting round two. First-payout integrity trains everyone that the ledger matters.
Beyond: rhythm and retrospectives
After three rounds, run a retrospective: are reminders landing well? Is the amount still comfortable? Adjust before resentment accumulates. Sousou preserves history so you can compare cycle one to cycle three objectively.
Common delays and how to absorb them
KYC refreshes, public holidays, and payroll freezes routinely stretch “one week” into ten days. Build a buffer day into your published due date instead of pretending banks move instantly. If a delay affects the recipient’s downstream obligation (rent due Monday), escalate compassion options early rather than debating policy on Sunday night.
Documentation pack for new joiners mid-timeline
Anyone joining after round two deserves a one-page recap: amounts paid so far, order remaining, and links to this blog’s glossary. Sousou shows the future; your recap explains the past emotional arc so newcomers do not feel like extras in someone else’s movie.
Parallel workstreams founders forget
While you chase payments, someone should own “member experience”: answering basic app questions, translating notices for elders, and confirming invites did not land in spam. Another person can own “finance reconciliation” if volumes are high. Splitting roles prevents one hero admin from ghosting the group after burnout.
Legal and tax touchpoints (non-advice)
Large pots or cross-border flows sometimes trigger reporting expectations. Keep dated exports of who received what—even if your counsel later says you did not need them—because retroactive reconstruction is painful. When amounts feel “real business” sized, pause marketing hype and get professional guidance before marketing the circle publicly.
Finally, publish a “day-one vs day-thirty” FAQ answering predictable worries: “What if my bank freezes my transfer?” “Can I pay two rounds early?” “Who sees my phone number?” Link to glossary terms so curious members self-serve at 11 p.m. instead of pinging admins. Self-service documentation scales love.
Timeline discipline converts a fragile idea into a dependable tradition.