A working pilot
for the campaign peak.
Business problem Scattered spreadsheets made student-ambassador campaigns hard to coordinate, with repeated contacts, manual data transfer and limited visibility over calls and invitations.
I scoped the user journeys and delivery priorities for a SaaS pilot built in 2.5 weeks and field-tested during the November–December 2025 campaign.
My hands-on contribution
- 01
Scope for the deadline
I worked from the audit and business requirements to shape a first usable pilot for the approaching campaign peak. The pilot was built in two and a half weeks.
- 02
Design around each user
I specified the coordinator and student journeys: campaign briefs, group allocation, personal calling lists and clear next steps. UX/UI and navigation were part of the functional design.
- 03
Learn from real use
The pilot was tested during the November–December 2025 campaign and open days. Usage and delivery statistics made friction visible and enabled targeted rebriefing of students.
The workflow, in practice
Select a stage to see what happens.
Import
Salesforce API retrieves leads collected at student fairs, avoiding export and re-entry.
Assign & call
Coordinators distribute contacts. Students see their own lists and campaign briefs.
Confirm
Brevo sends email/SMS confirmations and personal QR invitations after the call.
Welcome & monitor
QR scans track attendance; campaign and delivery data feed the monitoring view.
What changed
Pilot delivered & field-testedA field test, with visibility the team did not have before.
No duplicate-contact incidents of the kind previously described were reported during the pilot. Teams could follow calls, message delivery and event attendance.
Qualitative observations from the November–December 2025 field test.
Further rollout was deprioritised after leadership and budget changes in January 2026. No restart is scheduled.