Knowledge Centre

Real situations, worked through.

Each example shows the people, the agreement, the conditions and the product that fits — so you can recognise your own situation.

These are demonstration records. No money moves in these examples.

Buying cement after delivery
Mock data
200 bags of cement delivered to the Kiambu site before the money becomes eligible.
People and roles
- Mary — Creator and condition confirmer
- James — Payer
- Kamau Hardware — Recipient and performer
- Site supervisor — Evidence provider
Money direction
One payer to one recipient.
Conditions
- Delivery confirmed at the named site
- Bag count matches the agreement
Evidence
Delivery photo, Delivery note
Recommended: SecureLink
One payer, one primary destination, one set of conditions.
Common mistake. Paying in full before delivery on the strength of a phone call.
Next step. Create a SecureLink and name the confirmer separately from the payer.
Hiring a fundi
Mock data
A named repair job completed to the described standard.
People and roles
- Homeowner — Payer and confirmer
- Fundi — Performer and recipient
Money direction
One payer to one recipient.
Conditions
- Work completed as described
- Site left clean
Evidence
Completion photo, Homeowner confirmation
Recommended: SecureLink
A single worker with a single scope and one destination for the money.
If the job runs across several trades, SecureFlow fits better.
Common mistake. Describing the work too loosely to confirm later.
Next step. Write the completion condition in the words you would use to judge it.
Website project in milestones
Mock data
A website delivered in three milestones with an approval at each stage.
People and roles
- Business owner — Payer and approver
- Developer — Performer and recipient
- Designer — Performer and recipient
Money direction
One payer to one or several recipients depending on the team.
Conditions
- Design approved
- Build delivered
- Site live and handed over
Evidence
Design files, Staging link, Handover document
Recommended: SecureFlow
Several responsibilities and allocations across milestones, each with its own condition.
If one freelancer does everything and receives one amount, a SecureLink with staged conditions is simpler. The distinction is the number of recipients and allocations, not the number of meetings.
Common mistake. Paying the full amount at the design stage.
Next step. List the milestones before choosing the product.
Estate CCTV collection
Mock data
Contributions towards one governed purpose: cameras installed and tested.
People and roles
- Estate residents — Contributors
- Three organizers — Organizers, one treasurer
- Security vendor — Recipient and performer
Money direction
Many contributors to one governed purpose.
Conditions
- Cameras installed
- Testing record confirmed
- Organizer approval recorded
Evidence
Installation photos, Testing record, Organizer approval
Recommended: Group SecureLink
Many contributors, one destination, one governance rule.
Common mistake. Treating the target as permission to distribute money.
Next step. Record the governance rule before publishing the public page.
Estate road project
Mock data
Contributions funding several responsibilities across a road improvement.
People and roles
- Residents — Contributors
- Committee — Organizers and approvers
- Grading contractor — Performer and recipient
- Murram supplier — Recipient
Money direction
Many contributors to several recipients.
Conditions
- Murram delivered
- Grading completed
- Drainage inspected
Evidence
Delivery notes, Inspection result, Completion photos
Recommended: Group SecureFlow
Many contributors and several destinations governed by one plan.
Common mistake. Paying suppliers directly and reconstructing the record afterwards.
Next step. Write the distribution plan before collecting.
Selling a song
Mock data
Delivery of a licensed track file on the agreed terms.
People and roles
- Musician — Recipient and performer
- Buyer — Payer and confirmer
Money direction
One payer to one recipient.
Conditions
- File delivered
- Licence terms accepted
Evidence
Delivery record, Licence acceptance
Recommended: SecureLink
One buyer, one creator, one destination.
Common mistake. Sending the file before the agreement is accepted.
Next step. Publish a product page and let the QR code carry the agreement.
Selling a poem
Mock data
A commissioned poem delivered by an agreed date.
People and roles
- Poet — Recipient and performer
- Buyer — Payer and confirmer
Money direction
One payer to one recipient.
Conditions
- Draft delivered
- Final version delivered
Evidence
Delivery record, Buyer confirmation
Recommended: SecureLink
One agreement, one primary destination, small and clear conditions.
Common mistake. Agreeing scope by voice note only.
Next step. Put the date and the deliverable in the condition wording.
House renovation
Mock data
One plan covering three trades, each with its own responsibility and allocation.
People and roles
- Homeowner — Payer and approver
- Mason — Performer and recipient
- Plumber — Performer and recipient
- Electrician — Performer and recipient
Money direction
One payer to several recipients.
Conditions
- Masonry stage complete
- Plumbing inspected
- Electrical testing record
Evidence
Stage photos, Inspection result, Testing record
Recommended: SecureFlow
One payer funding several responsibilities with dependencies between them.
Common mistake. Running three informal agreements that cannot be sequenced.
Next step. Map which responsibility must finish before the next may begin.
Group trip
Mock data
Contributions funding several trip destinations under one governed plan.
People and roles
- Members — Contributors
- Organizers — Organizers and approvers
- Transport, lodge and caterer — Recipients
Money direction
Many contributors to several recipients.
Conditions
- Booking confirmed
- Attendance recorded
- Transport confirmed
Evidence
Booking confirmation, Attendance record
Recommended: Group SecureFlow
Several contributors and several destinations that must be governed together.
Common mistake. One organizer holding all the money personally.
Next step. Record the governance rule and the distribution plan first.
School trip contribution
Mock data
Contributions towards one school trip.
People and roles
- Parents — Contributors
- Class representative — Organizer
- Bus company — Recipient
Money direction
Many contributors to one or several recipients.
Conditions
- Transport booked
- Trip completed
Evidence
Booking confirmation, Attendance record
Recommended: Group SecureLink
If there is a single destination, Group SecureLink keeps it simple.
If transport, entry fees and meals are paid separately and a detailed distribution plan is required, use Group SecureFlow.
Common mistake. Collecting into a personal mobile account with no recorded purpose.
Next step. Decide whether one destination or several is the honest description.

Want to walk through one from a participant's point of view? Open the guided demonstrations.

Real situations, worked through.

Buying cement after delivery

Hiring a fundi

Website project in milestones

Estate CCTV collection

Estate road project

Selling a song

Selling a poem

House renovation

Group trip

School trip contribution