CTO role - Campus events platform

Building Youni into a campus events, ticketing, entry, and society growth platform.

As CTO at Youni, I helped build the student mobile app, organiser web platform, and Youni Scan entry app used across Oxford, Cambridge, and other Russell Group universities for discovery, ticketing, attendance, and society revenue.

Role Employee CTO before Codtronix
Product suite Student app, organiser platform, and Youni Scan
Growth Expanded from 1 to 5 universities, including Oxford and Cambridge
Entry flow QR ticket validation for organisers and door staff
Youni campus events platform screens showing organiser tools, mobile event discovery, ticketing, entry scanning, and semantic search.
Youni web and mobile product screens, adapted for the Codtronix case study.

System delivered

One platform connecting discovery, ticketing, door entry, and society operations.

The product had to work across the full event loop: students needed to find and share events, societies needed commercial tools to sell tickets, and door teams needed fast, secure entry validation on the night.

01

Student mobile app

A campus-first app for discovering events, buying tickets, seeing who was going, and sharing plans with friends.

02

Society ticketing

Paid tickets, passes, event checkout, promo flows, and attendee visibility so societies could turn interest into real revenue.

03

Organiser web platform

Web tools for societies and hosts to create events, manage attendees, configure ticket releases, and track activity.

04

Youni Scan entry app

A companion scanner for organisers and doormen to validate QR tickets, reduce duplicate entry risk, and keep check-in moving.

05

Semantic discovery

LangChain and LangGraph workflows with Pinecone-backed retrieval to help students find events by intent rather than exact keywords.

06

Social event graph

Features around friends, attendees, groups, and sharing so events felt social before people arrived at the venue.

Event created Tickets configured Society shares Students discover Tickets purchased QR code scanned Attendees managed Revenue tracked

The challenge

Why the obvious build path was too risky.

Campus life is fragmented across society chats, social posts, ticket links, and informal recommendations. Students struggle to find events they actually want, while societies and organisers need better tools to sell tickets, manage attendees, validate entry at the door, and turn demand into sustainable revenue.

The approach

How the work was made smaller, clearer, and more accountable.

  1. Led product and engineering decisions as CTO across the student app, organiser web platform, scanner app, event creation, ticketing, attendee, sharing, and society workflows.
  2. Built the product around real campus behaviour: students wanted to see what was happening, who else was going, and how to share plans quickly with friends.
  3. Added semantic discovery using LangChain, LangGraph, and Pinecone so students could search by intent and context instead of relying only on exact event titles or categories.

The outcome

What the team gained beyond shipped code.

  • A mobile, web, and scanner product suite that supported student event discovery, ticket purchasing, attendee visibility, door entry, organiser management, and society revenue.
  • Grew from a single university to five, including Oxford and Cambridge, as the platform proved itself campus by campus.
  • Societies and organisers had a single operating flow to publish events, sell tickets, scan attendees, manage audiences, and reduce operational friction around campus nights.
  • The product direction helped bridge campus community, commerce, and AI-assisted discovery before the platform later evolved beyond university life.

Discuss your context

Building a marketplace or community product?

We can help turn existing community behaviour into discovery, payments, organiser tools, mobile journeys, and search that people actually use.

  • See what should be built, simplified, or avoided
  • Leave with risks, constraints, and a credible next step
  • Talk to senior product and engineering people, not a script
It could be yours Show us the workflow, product idea, or system constraint you want to turn into an advantage.

We will help you decide what to build first, what to avoid, and how to move from messy context to usable software.