A registration platform live in under 48 hours

The situation

Abaya Walk is a community in Doha, run by Mariam Farid. The community had an event coming, people who wanted to take part, and no way to take their details except by message. Every registration was a WhatsApp thread, and every change to the plan meant messaging everyone again.

The constraint

Time. The date was fixed, the community had been running on Instagram alone, and there was no room for a long build. Whatever we made had to be something Mariam could run herself the next morning, in either language, without calling us.

What we built

A site that presents the community and the event, a registration flow that takes a participant from interest to confirmed in one screen, and an admin panel where Mariam sees every registration, changes the details, and exports the list. All of it on accounts in the owner's name, with the admin login hers from the first day.

The whole thing went from brief to live in under 48 hours. That number is the client's, not ours.

How we handled the hard part

Speed is only useful if the thing built fast does not fall over on the day. We kept the scope to what the event needed and nothing else: one form, one table, one admin screen. No accounts for participants, no payment step, no content management system to learn. Every decision that would have added a day was written down as out of scope, and the site shipped without it.

What changed

Registrations stopped arriving as messages and started arriving as rows. The owner controls the site herself, which is the thing she mentioned first.

What we would tell the next client

When the date is fixed, cut scope, not quality. A registration form that works in 48 hours beats a platform that is still in review on the morning of the event. The extra features can arrive in phase two, once there is a phase two.