Project Details
Home/Project Details
Relay
Project description
WhatsApp marketing that asks first
The Challenge
Broadcast messaging is the default way small businesses reach customers, and it is built backwards: the list is assembled first and the permission is assumed. The result is that the channel people actually read is the one everybody is trying to escape.
WhatsApp's own rules are the constraint, and they are not advisory — template approval, opt-in evidence and rate limits are enforced by the platform, not by the product. A workspace that ignores them gets the sender blocked.
The Solution
Consent is modelled as a record, not a checkbox: who agreed, when, and to what. Campaigns are built against that record, and the compliance requirements become the workflow rather than a warning banner bolted onto a send button. The client is Flutter so the workspace works on a phone, which is where the person running the campaign actually is.
Skills and deliverables
Features delivered
The hard part
Making compliance the path of least resistance. Every marketing tool can show a modal about consent; almost none can stop you sending. The design work was arranging the product so that the compliant route is also the fastest one.
The Impact
Running on Render, with the consent ledger, campaign builder and WhatsApp Cloud API integration live. It is the project in this portfolio with the most explicit point of view: the tool is shaped by the argument that permission is the mechanism, not the paperwork.
