Systems / Platforms

Platforms and social products

Multi-user products where the thing being modelled is people and how they connect.

A platform is a product whose value comes from the people on it, so the hard part is never the feature list. It is consent, trust, the rules that protect the vulnerable user, and what happens at the edges. We design those rules first and the screens around them.

The work that proves it

  1. The BeGivvy headline with reminder chips around it.
    BeGivvy2024–26

    WhatsApp-native birthday reminders and gifting, built as a social graph rather than a calendar with notifications bolted on.

  2. The Tholakala search bar and the three actions beneath it.
    Tholakala2026

    A missing-persons and lost-property platform for gatherings of tens of thousands, built for the annual pilgrimage at Ebuhleni.

  3. The Riverrr member card with seven of twelve stamps.
    Riverrr2025

    A credit-builder concept for South Africa: twelve bureau stamps, an itemised monthly slip, and a journey map that shows what each month unlocks.

You need this when

  • Your product has more than one kind of user and they need different things from the same data.
  • The rules about who may see or contact whom are the product.
  • You need it to work at a scale you cannot test by hand.

You do not, when

  • A single-user tool with an account system is not a platform. Build the tool.
  • If the audience does not exist yet, build the smallest thing that finds them before building the thing that serves them.

What it is built from

Next.js, a relational database with an audit trail, role-based access, queued and offline-tolerant writes where signal is unreliable, Flutter or Expo when a native app is justified.

Related

All platforms work

Need platforms and social products to run on?

A thirty-minute call, then a written scope within five business days. No obligation either way.

Start a project
Call
30 minutes
Scope
5 business days
Build
Weeks, in the open