Spotameet

Finding the right venue for an event often means calling spaces individually and trying to reconcile details such as capacity, layout, Wi-Fi, power, setup time and noise restrictions.

At the same time, people struggle to discover relevant events nearby and venue owners have unused capacity that is difficult to expose to the right organisers.

Spotameet treats people, events and spaces as one connected system instead of three separate workflows.

For people, the platform provides nearby event discovery.

For organisers, it provides space discovery based on the details that actually matter for an event.

For venue owners, it provides a way to list spaces, manage availability and reach organisers.

I co-founded Spotameet and worked across product direction, interface design, engineering and system decisions.

The product started from the observation that event discovery and venue discovery are usually treated as separate problems.

We instead treated them as connected sides of the same system.

That shaped the product around People, Events and Spaces and forced the design to account for how changes to one side affect the others.

Spotameet is a full-stack web application built around React and TypeScript, with systems for authentication, data management, venue imagery, availability, bookings and related product workflows.

The application uses a modern web stack including React, Vite, Express, MongoDB, PostgreSQL tooling, AWS S3, tRPC, React Query, Framer Motion and GSAP.

Building Spotameet made one thing obvious:

Marketplace products are not single-user interfaces.

Every product decision affects another actor.

A venue feature affects organisers.

An organiser workflow affects attendees.

Discovery affects supply.

Supply affects what discovery can show.

The interesting engineering problem is therefore not simply:

"How do I build this screen?"

It is:

"What happens to the rest of the system when I change this workflow?"

That became one of the most important lessons from the project.