Case study · Own product, not client work

A nightlife platform I designed, built and run.

NOCTVM is a nightlife and events platform for Bucharest and Constanța. It is my own product, not client work. This page shows what I built and how the ticket flow works, so you can judge the same approach for your launch or your venue.

Visit noctvm.app ↗

Status
Own product, not client work
What I did
Design, build and run
Where
Bucharest and Constanța
Built for
Phones first, dark-first for use at night
NOCTVM shown on a laptop and a phone, listing nightlife events in Bucharest and Constanța over a night view of the city
NOCTVM, my own nightlife and events platform.

What it is, and who it is for

NOCTVM helps people find what is on tonight, and helps venues and promoters reach them. Guests browse events, venues and artists. Organisers list events and, where they use it, sell tickets.

It installs on a phone as a web app, so there is no app store between a guest and the page. The whole experience is in Romanian and English.

The problem

Nightlife discovery is scattered. Events sit in Instagram stories that vanish, venue pages that are not kept up to date, and group chats you have to already be in.

That hurts both sides. Promoters struggle to reach new people, and people struggle to find what is on tonight. I have worked on both sides of the bar, which is where I saw both sides of the problem.

What I designed and built

An event page for every event

Every event has its own page with date, time, venue, line-up and a ticket button, plus structured data that search engines can read.

A page for every venue

Every venue has a page with its address, map position, social links, and upcoming and recent events. Guests can follow a venue.

A tonight page for each city

Every event happening tonight in a city is listed on one page that loads as plain HTML.

The organiser side

Venues manage ticket types, refunds and their team in a dashboard. The site also has a section for organisers who want to list an event.

The NOCTVM app on desktop, showing nightlife event cards and a live map
The NOCTVM app on desktop.

How the ticket flow works

  • 1. Choose. The guest opens an event page and taps the ticket button, then picks a ticket type and quantity. Free ticket types are supported too.
  • 2. Pay. Payment happens online through Stripe Checkout. Seats are held while the guest pays.
  • 3. Receive. The ticket arrives by email with a QR code and is also kept in the app. A Save to Google Wallet option is built in.
  • 4. Scan. On the night, door staff scan each ticket once. A door list grouped by name sits alongside.

I have built the ticketing flow. I make no claims here about sales or users.

The stack, in one line

Figma for design, Next.js, Supabase and GSAP for the build, Stripe Checkout for tickets and Vercel for hosting.

What this means for your launch

Running NOCTVM taught me what guests and venues need from a website, and I bring that to client work. Two pages show how it applies to you:

A build like this is scoped by what sits at its core. A Platform starts from £1,795. Anything with accounts, payments or custom workflows at its core, such as an App / Marketplace, is scoped from £2,500. The full list is on the services page.

Have a launch in mind?

Tell me what you are launching and what it needs to do. The fit call is free and takes 20 minutes.