Skip to content
Shpëtim Shabanaj — home

Available. Open to freelance · Junior Technical Consultant at Joint Services ITLocal time --:--:--

P/N 06Case studyJunction Hackathon, Pyramid Backstage challenge

Pyramid OS Create Event screen on a laptop, asking what you want to host, in front of the Pyramid of Tirana

PyramidOs — Event Planning Platform (AADF Challenge)

A digital event-planning system built in 48 hours at the Junction Hackathon. It replaces scattered emails, calls and spreadsheets with one flow for requests, venue matching, proposals, equipment booking and task coordination. Top 3 in the Pyramid Backstage challenge and progressed to the final.

Role
Team lead and developer
Team
5 members
Duration
48 hours
Year
2026
Stack
LLM parsing · Next.js · Node.js · AI room recommendations · 3D venue mockup

Outcomes

  • 48h

    From idea to working demo

  • Top 3

    Pyramid Backstage challenge

  • Top 11

    Teams overall in the final round

Problem

Planning events at a venue like the Pyramid meant juggling emails, phone calls and spreadsheets across organizers, venue staff and suppliers. Requests got lost, bookings clashed, and nobody had a single view of the plan.

Constraints

48 hours, a team of five, a new problem domain and a jury expecting a working demo. We also had to visualize the physical venue and handle overlapping events correctly.

Architecture

A Next.js web application on a Node.js backend, organized around the event lifecycle: request intake, venue matching, proposal creation, equipment booking and task coordination. A scheduling check catches conflicts between overlapping events, and a 3D mockup of the Pyramid helps organizers picture the space.

The event lifecycle in one system: request, venue match, proposal, equipment booking, tasks, with conflict checks on every booking.

7 parts, 7 connections.

  • N01 — 3D venue mockup
  • N02 — Request intake
  • N03 — Venue matching
  • N04 — Proposal creation
  • N05 — Equipment booking
  • N06 — Task coordination
  • N07 — Scheduling check
  • Request intake to Venue matching
  • Venue matching to Proposal creation
  • Proposal creation to Equipment booking
  • Equipment booking to Task coordination
  • 3D venue mockup to Venue matching
  • Scheduling check to Venue matching
  • Scheduling check to Equipment booking

Key decisions

Cover the whole event lifecycle rather than one step in depth, so the jury could see the full value in a short demo.

Treat scheduling conflicts as a core rule, checking for overlaps whenever a venue or piece of equipment is booked.

Build a 3D mockup of the venue, so venue matching felt concrete instead of abstract.

Pyramid OS public site with an interactive 3D model of the Pyramid of Tirana and a prompt to enter it
The way in: a 3D model of the Pyramid of Tirana, open to explore before planning.

Results

Placed in the Top 3 of the Pyramid Backstage challenge and reached the Top 11 teams overall in the final round. As team lead and developer, I kept the team's scope and timing on track across the 48 hours.

Explore Pyramid: an orbitable 3D model of the Pyramid and its surroundings with floor controls, a list of spaces, and the Mane Foundation room selected, showing its capacity, facilities and what it hosts
Every space on every floor, with its capacity, facilities and what it hosts.
Pyramid AI analyzing an event request: parsing it, extracting requirements, sizing spaces, checking venue availability and building plan options
The AI reads a request in plain words, sizes the spaces and checks availability.
Two plans for a 60-guest workshop: Value in the Blue Room from €1,632 and Premium in the Orange Room from €2,076, each with its rooms and reasons
Two costed plans to choose from, each with its rooms and the reasons behind it.
Admin Event Requests screen with the request list and a workshop's schedule, configuration, estimated total and approve or reject actions
Venue staff review each request and approve it into planning.
Manager pipeline at the Understand step: event summary, the organizer's request and an Event DNA radar scoring eight operational dimensions
Every event gets an operational profile before planning starts.
Inventory overview with overall health, total, reserved and available assets, and the health of each equipment category
Equipment health and availability, live from the database.

Reflection

I would validate the workflow with venue staff earlier in the weekend. I would keep the habit of cutting scope quickly and protecting a demo-ready core.