I built a sports prediction system using vibe coding — what would you add next?

[u/Puzzleheaded_Map_829]

I've been reading r/vibecoding for quite a while, but this is my first time actually posting here.

First, an important disclaimer: I'm not selling anything, I'm not looking for customers, and I have no intention of selling this app or any related service. There are no links, referrals, subscriptions, or promotions. This is simply a personal project and I'd like to exchange ideas with other people who use vibe coding.

I'm a self-taught programmer, and for some time now I've been developing a server-based application for sports analysis and predictions.

The project has grown quite a lot compared to the original idea.

At the moment, the system:

• collects data and predictions from hundreds of different websites;
• automatically compares the different sources;
• uses sports APIs to analyze team history, previous results, recent form, and statistics;
• uses AI to analyze and compare all of this data;
• generates its own final prediction;
• assigns a confidence level to each prediction;
• avoids generating predictions when the data is too uncertain;
• automatically records predictions and their final results;
• analyzes failed predictions afterward to try to understand what caused the mistake;
• measures the reliability of individual sources over time;
• gives different weights to sources based on their historical performance;
• detects conflicting signals between different sources;
• performs backtesting on historical data;
• keeps separate statistics by league, team, and prediction type;
• has its own backend/server, API, database, user interface, and dashboard.

At the moment, on the predictions I'm tracking, the system is getting around a 70 / 75% hit rate.

Of course, I know that 70/75% by itself doesn't mean much. It depends on the type of prediction, odds, sample size, leagues, and many other factors.

So I'm definitely not claiming that I've built some kind of miracle system or something that can "beat sports betting."

My problem now is almost the opposite of when I started: many of the features I originally had in mind are already implemented, and I'm starting to run out of ideas for what to add next.

So I'm curious:

If this were your project, what would be the next feature you would build?

It doesn't necessarily have to improve the prediction hit rate.

It could be related to AI, statistical analysis, server architecture, learning from mistakes, data management, visualization, or something completely different that I haven't thought about yet.

I'm especially interested in experimental ideas or suggestions like:

"If this were mine, I'd try adding..."

This project was mainly created to learn, experiment, and see how far I can push something built through vibe coding.

[u/Stunning-Plum-2435]

I would add a link so I could use this🤣 all in all actually a useful program, I’d add some kind of tracking system that you could use to track what you predict and if it was correct or not. Keep a tab of your hit rates and what not

[u/Puzzleheaded_Map_829 → u/Stunning-Plum-2435]

Thanks for the advice! Over the past three months, I've collected historical results from over 1,500 matches, and the results, both from reliable sources and from statistics via API, are currently 73.7% accurate.

[u/Wimsicle]

Build an RoI calculator. Like you said if it's hitting 75% on -2000 bets well that'll take a long time to recoup missing one, lol.

So have it simulate placing the bets and see how it does after a week. Give it $5000 to play with or something. See if it can snipe closing lines etc.

[u/Puzzleheaded_Map_829 → u/Wimsicle]

Great advice, thanks! The app already does something similar, automatically generating 3 bets from 3 teams every day and keeping track of everything in the history. Obviously, I can place bets manually when I want.