← Back
Solution modelling Client work Released

TicketAse - requirements, system flows and developer handover

The founder of TicketAse and FrontPageBD approached me directly to turn his ticketing-platform idea into screens and user flows.

RoleAnalyst - requirements to handover
EngagementDirect engagement with the founder
SectorEvents and ticketing

The brief

TicketAse began with discussions with its founder, who also runs FrontPageBD, an Instagram-based news publication in Bangladesh. He approached me directly with the idea for the platform.

The client brief covered nine areas: users, events, ticketing, search, marketing, administration, venues, refunds, and security. I worked from that material and our discussions to develop the experience.

My role

I worked directly with the founder to turn his idea into interface screens, develop the user flows and revise the experience before handover. My contribution covered flows across the platform.

The output

Interface designs and user flows for event discovery, event details, search, login and checkout, including separate guest and logged-in journeys. I delivered the revised work for development.

What happened next

TicketAse launched and is live. I have since left the project, while its team continues to update it. The current product includes work completed after my involvement.

Next case studyMulti-brand lead-capture QA - regression and traceability Get in touchDiscuss this project →
TicketAse - requirements to developer handover | Marjuk Sajid Hossain
← Back
Solution modelling Client work Released

TicketAse - requirements, system flows and developer handover

The founder of TicketAse and FrontPageBD approached me directly to turn his ticketing-platform idea into screens and user flows.

RoleAnalyst - requirements to handover
EngagementDirect engagement with the founder
SectorEvents and ticketing

The brief

TicketAse began with discussions with its founder, who also runs FrontPageBD, an Instagram-based news publication in Bangladesh. He approached me directly with the idea for the platform.

The client brief covered nine areas: users, events, ticketing, search, marketing, administration, venues, refunds, and security. I worked from that material and our discussions to develop the experience.

My role

I worked directly with the founder to turn his idea into interface screens, develop the user flows and revise the experience before handover. My contribution covered flows across the platform.

The output

Interface designs and user flows for event discovery, event details, search, login and checkout, including separate guest and logged-in journeys. I delivered the revised work for development.

What happened next

TicketAse launched and is live. I have since left the project, while its team continues to update it. The current product includes work completed after my involvement.

Next case studyMulti-brand lead-capture QA - regression and traceability Get in touchDiscuss this project →