So I never miss a ticket or important update again.

AI-native intelligence system for Fluminense matches

Date

April 2026

Company

Personal project

Scenario

I have this passion: Fluminense.
Love attending the most matches possible, sometimes even short trips to away games. My father goes to most of it too. It's generational, it's emotional, it's Fluminense.

Challenge

Match and ticket info can be hard to find (and trusted). How do you plan for something if tickets can be released at any moment, and anything can change at short notice?

Results

First in line

for ticket sales

Zero

missed ticket sales

Zero

moments lost for details

Goals

Release a product to the market.

Solve a real and personal problem.

Exercise AI fluency.

Create a case study documenting the process.

Context

I’ve followed Fluminense my entire life — not just watching, but attending.

cadu
Maracanã
Instagram post
3 likes
cadu
Vila Belmiro - Santos
Instagram post
3 likes
cadu
Belo Horizonte - MG
Instagram post
3 likes

It's there everywhere I go. It's part of my life.

cadu
Pedra da Gavea - São Conrado
Instagram post
3 likes
cadu
Central Park - NY Marathon
Instagram post
3 likes
cadu
Maracanã
Instagram post
3 likes

My match system was broken

Fragmented: Information spread across social, news and ticket sites.

No default: Each away game has its own system and schedule.

Unpredictable: Frequent last-minute changes. (weather and violence incidents)

Blind decisions: It's common to land in a different city without yet having tickets.

Needed

Another app to check.

One system watching over everything.

Real-time, reliable alerts to prevent me from wasting time and money.

Information that gives me confidence before acting

Safety insights to help me navigate the turbulent waters of South American football.

Many sources, many formats

Solution

A system that monitors multiple sources and alerts me about important updates.

Home

Available tickets

Schedule

Match detail

1

General info: All basic stuff I need to know ahead of a match.

2

Data confidence: Compare sources to make sure I'm fed with the right data.

3

Ticket waves: Display all different ticket sale phases.

4

Safety history: A fresh look into the relation between teams and supporters.

5

Pre-match updates: Highlight recent content related to the game (road blockades, conflicts, incidents, and traffic).

6

Notifications: No more flood of information, now filtering the essential and most relevant to my planning.

Notifications

Settings

Outside the app

Telegram notifications

Action required events automatically synced to Calendar

Mon
Tue
Wed
Thu
Fri
Sat
Sun
10:00
11:00
12:00
13:00
14:00
15:00

How it works

Different problems demanded different flows

Match data (every hour)

Data scraper

5 sources

Normalization

Clean and standardize

Confidence engine

Data agreement, change detection

Fill content and Telegram alert

Inform and notify

This feeds

Ticket data (every 5 min)

Ticket Scraper

Club website

Instagram post
News article

Content extraction

Clean and standardize

AI parsing

Detect wave, date

and availability

Fill content and Telegram alert

Inform and notify

This feeds

Pre Match (hours before)

Weather lookup

Forecast

Safety check

Conflict incidents in

news and social media

Related News

Blocked roads, trafic,

public transportation…

Fill content and Telegram alert

Inform and notify

Notification prioraty

Event detected

Critical?

Yes or No

High

- Stadium changed

- Tickets live

Low

- Small confidence change
- Changes in far away matches

A sustainable, updated, sharp, non disturbing and always relevant system.

Tools & Stack

Chosen to move fast, minimize costs and last long.

ChatGPT

Planning, structuring and prompt optimization.

Claude

Data processing, project memory and context.

VS Code

Primary IDE for rapid iterations and code editing.

Vercel

Hosting and deploying platform.

Supabase

Database, storage and normalized match states

Github

Automation and background processing.

Next.js

Core layer powering ingestion and delivery.

Telegram Bot

Instant notifications informing significant infos.

Open-Meteo

Weather forecasting API.

Maps

Stadium logistics and directions.

BEFORE

AFTER

Now I can

Guarantee my tickets - Get alert and open the link directly from the notification.

Cancel on low confidence - Inconsistent info generally means a real and important change in the future.

Book trips with more certainty - Multiple sources and ticket "priority" help me decide.

My father will have his tickets - Different wave alerts prevent me from getting confused.

Mind my day with no concerns - System will pay attention so I can relax and wait for action time.

UX Key Decisions

  1. Speed vs Accuracy

Confidence score instead of binary truth. Sometimes a small change is enough to deserve attention.

  1. Automation vs Control

Some tasks are easy and light, but not all of them need complex processing. Smart, not hard processing.

  1. Coverage vs Reliability

A balance between too many sources and too few to be trusted.

  1. Intelligence vs Cost

Not the best possible tool, but will work long term and allows updates and improvements.

  1. Product vs Behavior

Meet user where he already is.

Quick reflections

Planning before prompting is key. Comparing plans and AIs. Prompt generators. These helped.

Be open to learning. As just a curious (non-technical) designer, understanding new tools and tech is crucial.

The AI will hallucinate. Things will break. So pacience might be the best skill dealing with it.

Results achieved

First in line

one of the first to know about ticket availability

Zero

missed sales since launch. If I want to go, I'll be there

Zero

moments lost to wrong stadium, wrong date, wrong wave

My dad

haven't missed his gratuity window once

Contact

Linkedin:

Phone:

+ 55 21 98623 2770

Create a free website with Framer, the website builder loved by startups, designers and agencies.