Meet the host
The homepage introduces him in his own words, with connecting and watching the shows as the two immediate actions.
Personal brand · Show archive · Booking site
Rafsan Sabab
An in-progress website for a Bangladeshi host and content creator, built so an event organiser can judge whether he is right for their stage — and book him — without leaving the page.
Read the case study Visit the live siteA personal brand site for a host, content creator, and storyteller who works corporate conferences and live events alongside his own show. It is built to do one job well: convince an organiser he is right for their stage, then make the booking easy.
What success needed to look like
- 01
Establish the host's voice and range within the first screen.
- 02
Collect the shows and hosted events into one place an organiser can judge quickly.
- 03
Keep the booking route reachable from anywhere on the site.
- 04
Carry the personality of a live performer without slowing the site down.
In build
Actively in development on a staging deployment
How the solution works
From problem to outcome.
A simple view of how work moves through the solution, without exposing private implementation details.
Read the background
The about page traces the route from the classrooms of IBA to hosting stages and screens.
See the work
The media gallery collects the events he has hosted, so an organiser can judge the range rather than take it on trust.
Make the booking
The shows archive and contact route turn a convinced organiser into an enquiry. Both are in progress.
Read the step-by-step workflow
- Meet the host: The homepage introduces him in his own words, with connecting and watching the shows as the two immediate actions.
- Read the background: The about page traces the route from the classrooms of IBA to hosting stages and screens.
- See the work: The media gallery collects the events he has hosted, so an organiser can judge the range rather than take it on trust.
- Make the booking: The shows archive and contact route turn a convinced organiser into an enquiry. Both are in progress.
The product in action
How BDBot works inside Discord.
Players never need to leave the community space they already use. The bot turns commands into clear match, profile, and leaderboard experiences directly in the channel.
The host introduces himself
The homepage opens in his own voice against a photograph of him working a stage. Two actions follow — connect, or watch the shows — because a visitor is either booking him or checking him out.
The route to the stage
The about page traces the path from business school to hosting, and names the three roles he works in, so an organiser can place him before reading any further.
The events, as the argument
The media gallery collects the events he has hosted. For a booking decision this is the evidence that matters, so it gets its own page rather than a strip on the homepage.
The situation that needed to change.
A host's proof of ability is footage and past stages, but it was scattered across YouTube, social posts, and other people's event pages. An organiser deciding who to book had no single place to see the work, and no obvious way to make contact once convinced.
What I changed and built.
- Opened with the host in his own voice, so a visitor knows within one screen what kind of performer they are considering.
- Gathered the shows and hosted events into a gallery an organiser can judge quickly, instead of asking them to hunt across platforms.
- Kept the booking route visible from the first screen, so interest can turn into an enquiry the moment it appears.
Key choices
Why this approach worked.
Let him speak first
The homepage opens in the host's own voice rather than a third-person biography, because an organiser booking a personality is judging exactly that.
Two actions, not a menu
The hero offers connecting and watching the shows and nothing else. A visitor either wants to see the work or wants to book, and both are one click away.
Show the work, do not describe it
The gallery leads with the events themselves. For a host, footage and stages are the argument; adjectives are not.
Ship the site in sections
Home, about, and the gallery went up on a staging deployment first, so the client could react to the direction while the shows archive and booking flow were still being built.
What I was responsible for.
I am building the site: the layout and navigation, the home and about pages, the media gallery, and the shows and contact sections now in progress.
- Build the site layout, navigation, and responsive behaviour.
- Build the home and about pages.
- Build the media gallery of hosted events.
- Build the shows archive and contact and booking flow (in progress).
- Deploy to a staging environment for client review ahead of launch.
Outcome
What changed because of the work.
The site is running on a staging deployment while the sections are built out. Home, about, and the media gallery are in place, with the shows archive and booking flow in progress.
Home, about, and media gallery pages built
Shows archive and contact flow in progress
Running on a staging deployment for client review
Booking route reachable from the first screen
What it took to deliver
Client deliveryPersonal brandMedia galleryBooking enquiryNext.jsWork in progress
Clear about what can be shared.
Some client material and implementation details remain private. The numbers, responsibilities, and outcomes shown here are limited to what can be shared and verified.