Client project · Fitness academy · Anonymised
We built this for a fitness academy running online classes, so that a member missing sessions gets a timely nudge — and staff can see exactly what was sent.
Attendance sat in Google Meet. Nobody had time to work out, week by week and course by course, who had stopped turning up — so follow-up happened late, if at all.
Screenshots are real screens from the system, with every name, figure, logo and QR code replaced by fictional data.
Each course lists its members. After a Google Meet session, the attendance file is uploaded and every member is marked present, absent or not expected.
The academy sets how many missed sessions count and over what period. The list shows each member's misses for the week and how many in a row.
The rule builds the recipient list. Staff untick anyone it should not go to before the course-wise emails go out.
Sent, failed or excluded — recorded per member and per address, never claimed for the whole batch.
The report lists each email's send time, bounce time and bounce type, and why anyone was excluded — for example, an address that had already bounced.
Your workflow will not be identical, and it does not need to be. Tell us what is slow, manual or missing, and we will tell you honestly whether something like this would help.
Client project · Restaurant · Anonymised
The problem: Guests need an easier way to browse, order and ask for service — without adding work for the floor team.
What we built: A table-QR menu for ordering and service requests, with the floor team and the owner seeing the same requests the moment a guest taps.
See how it works: Make every table visit an opportunity to serve better.
Our own product · UniqBrio
The problem: Manual follow-ups make it hard to keep track of due dates, payment status and new enquiries across courses.
What we built: Course-wise payment tracking, WhatsApp reminders with a pay link, and a simple online path from enquiry to enrolment.
See how it works: Spend less time chasing fees.