DEV Community: Tudor Ioan

Why a football prediction platform needs an editorial verification system

Tudor Ioan — Wed, 05 Aug 2026 07:14:58 +0000

For years, football prediction platforms were built around a simple promise:

Give users a prediction before the match starts.

A percentage.A confidence score.A suggested outcome.

The entire product was built around one decisive moment: the final whistle.

Was the prediction correct?

Was it wrong?

Prediction performance remains important. But the football data ecosystem has changed, and users now expect much more than a percentage attached to a fixture.

They want context.

They want to understand why one team is favoured.

They want information about injuries, suspensions, tactical changes, recent form, competition pressure and historical performance.

They want to know what changed before kick-off.

They also want to understand what happened after the match—not only what was predicted before it.

This evolution is creating a new category:

The football intelligence platform.

However, moving from a prediction website to a football intelligence platform introduces a fundamentally different challenge.

Predictions are uncertain by nature.

Editorial information cannot be.

Once a platform starts publishing previews, match reports, player information and football news, it becomes responsible not only for probabilities, but also for facts.

That is why editorial verification is becoming one of the most important layers in modern football technology.

Prediction accuracy is not the same as editorial accuracy

A prediction model might say:

Manchester City has a 65% probability of winning.

If Manchester City loses, the model is not automatically defective.

Football contains randomness, variance and low-probability events. A team can dominate possession, create the better chances and still lose because of a deflection, a red card or an outstanding goalkeeper performance.

A probability is not a promise.

Editorial information is different.

Imagine that an article says:

Kevin De Bruyne started the match.

If the player was not in the starting lineup, that is not variance.

It is not an unlucky outcome.

It is an editorial error.

This distinction is essential because prediction quality and editorial quality must be measured differently.

Prediction systems can be evaluated through:

-Calibration

-Hit rate

-Expected value

-Long-term performance

-Market-specific accuracy

-Settled-result methodology

Editorial systems require different standards:

-Factual correctness

-Source reliability

-Evidence coverage

-Information freshness

-Internal consistency

-Transparent corrections

A platform can have a statistically strong prediction model and still publish unreliable football content.

The reverse is also possible.

The two systems may share data, but they solve different problems.

Why AI increases the need for verification

Artificial intelligence can process thousands of sources, identify patterns, summarise information and generate match previews at a scale that would be impossible for a traditional editorial team.

But generation and verification are different problems.

A language model is usually optimised to produce a useful, complete and coherent answer.

That instinct becomes dangerous in editorial environments.

When evidence is incomplete, a generative system may still try to connect the available fragments into a finished narrative. The text may sound convincing even when some of its claims are weak, outdated or unsupported.

Editorial systems need the opposite instinct.

Before generating more information, they must ask:

Do we actually know this?

-Is the source reliable?

-Is the information current?

-Is the claim supported by evidence?

-Are there contradictory sources?

-Should this information be published at all?

The most valuable editorial AI is not necessarily the system that writes the most.

It is the system that understands when it should not write.

Content generation is not editorial intelligence

BetLogic started as an AI football prediction platform.

As the product evolved, the objective changed.

The platform now combines:

-AI match predictions

-Match Intelligence previews and reports

-Prediction performance tracking

-Landed and missed prediction transparency

-A football News Hub

-A structured operator database

-AI Bet Slip Check

-Internal editorial review workflows

At that point, the primary challenge was no longer:

How do we generate more content?

It became:

How do we make sure every piece of content deserves to exist?

That question changes the architecture of the product.

A content generation system focuses on output.

An editorial intelligence system focuses on evidence, confidence, accountability and publication safety.

It treats generation as only one stage in a much larger process.

Building an editorial verification layer

A reliable football intelligence platform needs an evidence layer that exists independently from the final article.

Before generating a preview or report, the system must establish the identity and state of the fixture.

That evidence may include:

-Fixture identity

-Home and away teams

-Competition and season

-Kick-off time

-Fixture status

-Final score

-Goals and event chronology

-Starting lineups

-Substitutions

-Cards

-Team statistics

-Player statistics

-Standings

-Competition context

-Recent form

-Historical meetings

-Source timestamps

-The article should not become the source of truth.

It should be a controlled interpretation of structured and verified evidence.

This distinction matters because generated text can change. The underlying match facts should not.

Fixture identity comes first

Many editorial errors begin before the article is generated.

Two teams may have played several times in the same season. A club name may appear in multiple competitions. Provider identifiers may not match across data sources.

If the system attaches evidence from the wrong fixture, every sentence generated afterwards may be internally coherent and still completely incorrect.

Before any drafting begins, the platform should verify:

-Both teams

-Competition

-Fixture date

-Provider fixture ID

-Match status

-Relevant season or stage

-Fixture identity is not a minor implementation detail.

It is the foundation of the entire editorial record.

Freshness must be measurable

Football information changes quickly.

A player reported as doubtful in the morning may be confirmed in the starting lineup before kick-off.

A suspension may be overturned.

A transfer may be announced after an article has already been drafted.

Every piece of evidence should therefore include freshness metadata:

-When was it published?

-When was it retrieved?

Is it still valid for the current fixture state?

Has a newer source contradicted it?

A trustworthy platform should never treat “available” and “current” as the same thing.

Articles should be verified claim by claim

An article should not be approved simply because it appears correct as a whole.

It should be evaluated claim by claim.

Consider the following statements:

The player scored twice.

This requires event evidence showing two goals attributed to that player.

The team dominated the midfield.

This may require possession data, passing patterns, territory statistics, tactical evidence or credible analysis.

The manager changed the approach after half-time.

This requires contextual evidence such as a formation change, substitutions, altered pressing behaviour or a reliable post-match statement.

These claims have different evidence requirements.

A structured editorial system should identify:

-The claim being made

-The type of claim

-The evidence required

-The supporting source

-Any contradictory evidence

-The confidence level

-Whether the claim is safe to publish

-This creates a claim-to-evidence relationship.

Without that relationship, factual statements and generated interpretation become mixed together, making reliable review much harder.

Contradictions must stop publication

Some inconsistencies should be treated as hard blockers.

They should not reduce a quality score by a few points. They should prevent the article from being published.

Examples include:

Score mismatch

One source reports a 2–1 result while another part of the system reports 1–1.

The article cannot be approved until the authoritative score is established.

Wrong goalscorer

The generated report attributes a goal to one player while the event feed records another.

This is a factual contradiction.

Own-goal conflict

A goal may be credited differently across providers before official confirmation.

The system should not silently choose the version that creates the best narrative.

Lineup conflict

The article says a player started, while verified lineup data shows that the player was on the bench or absent.

Qualification error

A report claims that a team qualified, was eliminated or won a group when the competition rules and standings do not support that conclusion.

Contradiction handling is one of the clearest differences between a writing tool and an editorial system.

A writing tool tries to finish the article.

An editorial system is allowed to stop.

Verified brevity is better than invented depth

Generative systems are often evaluated by the apparent richness of their output.

Longer previews seem more complete.

Detailed tactical narratives seem more intelligent.

But depth without evidence is not intelligence.

Sometimes the strongest article is the shorter one.

A system that says:

We do not have enough verified evidence to support this claim.

is stronger than a system that fills the missing space with plausible language.

This principle should influence both product design and editorial metrics.

The objective should not be to maximise:

-Article length

-Number of claims

-Number of generated sections

-Publishing volume

-The objective should be to maximise:

-Supported claims

-Reliable evidence

-Useful context

-Transparent uncertainty

-Reader trust

Publishing less can be a sign that the verification system is working.

Human review is not a weakness

There is a tendency in AI product development to treat human involvement as an obstacle to full automation.

In editorial systems, that assumption is dangerous.

AI can scale research.

AI can collect evidence, compare sources, detect inconsistencies, create timelines and prepare structured drafts.

Humans provide judgment.

A reviewer can decide whether a tactical conclusion is reasonable, whether a source is trustworthy, whether a sentence is misleading and whether the article contributes genuine value.

The strongest workflow is not necessarily human versus AI.

It is AI and human review with clearly separated responsibilities.

AI can help answer:

-What information is available?

-Which sources agree?

-Which claims are unsupported?

-Where are the contradictions?

-What changed since the previous version?

-The human reviewer can answer:

-Is this interpretation fair?

-Is this worth publishing?

-Could the wording mislead the reader?

-Does the article meet the publication’s standards?

Human approval should not be a ceremonial button at the end of an automated pipeline.

It should be a meaningful editorial decision.

Corrections create trust

Even well-designed editorial systems will make mistakes.

The important question is not whether corrections will ever be needed.

It is how the platform handles them.

A serious publisher should not silently overwrite history.

Corrections should preserve:

-The previous version

-The corrected version

-The reason for the correction

-The evidence that triggered the change

-The reviewer responsible for the decision

-The date and time of the update

This requires an immutable or append-only correction history.

Readers do not expect perfection from every publisher.

They do expect accountability.

A visible and structured correction process can create more trust than pretending errors never happened.

Prediction tracking also needs editorial standards

Prediction platforms often focus heavily on winning selections while treating missed predictions as temporary or disposable information.

That approach undermines trust.

Predictions should be preserved once published.

The platform should clearly define:

-When a prediction becomes immutable

-What counts as settled

-How void selections are handled

-How postponed or abandoned fixtures are treated

-Which market result is used

-How performance percentages are calculated

-Whether edits were made before or after kick-off

-Missed predictions should not disappear.

Historical performance should not be reconstructed only from successful outcomes.

Transparency requires both landed and missed results.

Prediction tracking may be statistical rather than journalistic, but it still requires editorial discipline:

Clear methodology

Consistent settlement rules

Immutable historical records

Honest presentation

No selective deletion

Trust is damaged just as easily by hidden misses as by incorrect match reports.

The future of football intelligence

The next generation of football platforms will not compete only on the number of predictions they generate.

They will compete on the quality of the intelligence surrounding those predictions.

The most valuable platforms will connect:

-Probabilistic forecasting

-Structured match data

-Verified editorial content

-Performance transparency

-Reliable source attribution

-Human judgment

-Accountable corrections

AI will make football content easier to generate.

That does not mean reliable football publishing will become easier.

In many ways, the opposite is true.

As generation becomes cheaper and faster, verification becomes more valuable.

The future will not belong to the platforms that publish the most predictions, the longest previews or the highest volume of AI-generated articles.

It will belong to the platforms that know the difference between probability and fact.

It will belong to the platforms that refuse to publish unsupported certainty.

Most importantly, it will belong to the platforms that users can trust.

Why I Built a Medieval Mini-Game Inside a Football Platform

Tudor Ioan — Thu, 09 Jul 2026 12:46:38 +0000

When people hear about BetLogic, they usually think of AI match analysis, football statistics, betting tools, or casino bonus comparisons.

So why did I spend time building a medieval tower game?

At first glance, it makes absolutely no sense.

But for me, it makes perfect sense.

BetLogic was never meant to be “just another predictions website”

There are already hundreds of websites publishing football tips.

Most of them look almost identical.

Lists.
Odds.
Predictions.
Ads.

I wanted to build something that people actually enjoy opening every day.

Something that feels less like a database and more like a place.

A website can feel like a world

I’ve always loved medieval fantasy.

Castles.
Knights.
Taverns.
Boss fights.
Exploration.

Instead of creating another dark dashboard full of numbers, I started asking myself:

What if BetLogic felt like entering a medieval tavern?

A place where visitors don’t only check tomorrow’s matches.

They stay.

They explore.

They interact.

Knight’s Trial

That idea eventually became Knight’s Trial.

It’s a small browser game inside BetLogic where you climb eight floors of a tower.

Each floor is protected by a guard.

Win the fight and your multiplier increases.

Lose, and your run ends.

You can also leave the tower at any time and secure your current multiplier.

Just like in real decision-making, knowing when to stop can be just as important as knowing when to continue.

Three different personalities

I didn’t want the game to be random.

I wanted every risk level to feel different.

Classic rewards consistency.

Brave increases the tension.

Mythic is intentionally brutal, with extremely rare high-multiplier runs.

Behind every mode is a transparent mathematical model.

Every multiplier comes directly from survival probabilities while keeping the RTP fixed.

Nothing is hidden.

Nothing changes behind the scenes.

It’s only a demo

Knight’s Trial doesn’t use real money.

It isn’t connected to deposits.

It isn’t even meant to become a gambling product.

The goal was different.

I wanted visitors to spend a few extra minutes inside BetLogic.

To smile.

To discover something unexpected.

To feel that the platform has personality.

Building a hub instead of a website

BetLogic keeps growing beyond football predictions.

Today it includes:

AI match previews
AI Bet Slip Check
live match experiences
casino and sportsbook reviews
responsible gambling resources
bonus comparisons
community features
and now…

…a small medieval game.

None of these features exist in isolation.

They’re all pieces of the same vision.

A global hub where football fans can read, analyze, play, learn and interact.

Still only the beginning

Knight’s Trial is only the first experiment.

The medieval theme is becoming part of BetLogic’s identity.

More interactive experiences are already planned.

The goal isn’t to compete with game studios.

The goal is to make BetLogic memorable.

Because in the end…

People rarely remember another statistics website.

But they remember places that feel alive.

Why I Chose Vercel Analytics Over Google Analytics for BetLogic

Tudor Ioan — Wed, 24 Jun 2026 10:46:01 +0000

Why I Chose Vercel Analytics Over Google Analytics for BetLogic

When I started building BetLogic, one of the first infrastructure decisions I had to make was how I wanted to measure product performance.

The obvious answer seemed to be Google Analytics.

It powers millions of websites and has become the default choice for many companies.

But after spending time building, deploying, and optimizing BetLogic, I found myself relying more and more on Vercel Analytics instead.

This wasn’t because Google Analytics is a bad tool.

It isn’t.

The reason was much simpler:

I cared more about product performance than marketing reports.

⸻

The Questions I Actually Needed Answered

BetLogic is built with Next.js and runs on Vercel.

The platform includes:

AI-powered football match previews
Daily match insights
Bonus and operator comparison pages
OCR-powered Bet Slip Check
World Cup coverage
Email marketing infrastructure

As the project grew, the questions I wanted answered were things like:

Which pages are actually getting used?
Which routes are becoming slower?
Did a deployment improve performance?
How do users navigate the platform?
What happens after a major release?

Those are product questions.

Not marketing questions.

⸻

The Problem With Too Much Data

Google Analytics is incredibly powerful.

But power often comes with complexity.

For a solo founder, I found myself spending more time configuring reports than using them.

I didn’t need dozens of attribution models.

I didn’t need advanced advertising funnels.

I didn’t need endless dashboard customization.

I needed actionable information.

Fast.

⸻

Why Vercel Analytics Felt Different

Because BetLogic is hosted on Vercel, Vercel Analytics integrated directly into my workflow.

The setup took only a few minutes.

No complicated event configuration.

No tag management.

No custom dashboards required before getting value.

Instead, I immediately had access to:

Real visitor activity
Traffic trends
Core Web Vitals
Geographic distribution
Route performance insights

Most importantly, everything felt connected to the actual product.

⸻

Performance Is a Feature

One lesson I’ve learned while building BetLogic is that performance isn’t a technical metric.

It’s a product feature.

Users don’t care how elegant your code is.

They care whether pages load quickly.

They care whether interactions feel smooth.

They care whether the site responds instantly.

For that reason, Core Web Vitals became one of the most important metrics I monitor.

Vercel Analytics makes those metrics easy to access and understand.

That shortens the feedback loop between:

Build → Deploy → Measure → Improve

And that loop is incredibly valuable.

⸻

Google Search Console Remains Essential

Choosing Vercel Analytics didn’t mean abandoning Google’s ecosystem.

In fact, Google Search Console is one of the tools I use most.

Search Console answers completely different questions:

Which pages are ranking?
Which keywords generate impressions?
How is indexing performing?
Which content opportunities exist?

For SEO, Search Console is indispensable.

For product performance, Vercel Analytics became my preferred solution.

Together, they complement each other extremely well.

⸻

Simplicity Scales Better Than Complexity

One of the biggest lessons from building BetLogic is that simplicity compounds.

Every hour spent configuring tools is an hour not spent improving the product.

Every unnecessary dashboard adds friction.

Every layer of complexity creates maintenance overhead.

As a solo founder, I try to optimize for speed of decision-making.

Not for the largest possible feature set.

That’s ultimately why Vercel Analytics won for me.

⸻

Final Thoughts

Google Analytics remains one of the most powerful analytics platforms available.

For many businesses, it’s absolutely the right choice.

But for BetLogic, Vercel Analytics provided something I valued even more:

clarity.

It gave me the information I needed without forcing me to navigate through layers of configuration and reporting.

Sometimes the best tool isn’t the one with the most features.

It’s the one that helps you make better decisions faster.

And for BetLogic, that’s been Vercel Analytics.

⸻

Building in public: https://www.betlogic.eu

Tech stack: Next.js, TypeScript, Vercel, PostHog, Neon, OpenAI.

Building BetLogic with Next.js: AI Football Previews, Bet Slip Checks and Automated Content

Tudor Ioan — Wed, 17 Jun 2026 12:19:21 +0000

I’m building BetLogic, an AI-powered football intelligence platform focused on match previews, risk-aware predictions, transparent tracking and football content automation.

The idea started from a simple problem:

Most football prediction platforms show a pick, but not enough reasoning.

I wanted to build something that explains the context behind the analysis — form, match risk, AI-assisted reasoning, weak selections, and post-match accountability.

BetLogic is still early-stage, but it already combines several product layers:

daily football match previews
AI-assisted match analysis
AI Bet Slip Check
transparent tip tracking
World Cup news hub
casino and sportsbook operator reviews
bonus comparison pages
internal email marketing hub
SEO-focused content architecture

This post is a quick look at how I’m thinking about the product and why I decided to build more of the infrastructure myself.

Why I’m Building BetLogic

The football prediction space is crowded.

A lot of platforms publish short predictions, confidence numbers, odds-focused content or generic operator reviews. The problem is that many of them do not explain enough.

I wanted BetLogic to take a different approach.

Instead of only asking “what is the pick?”, BetLogic tries to answer:

why does this prediction exist?
what context matters?
what are the risk signals?
what could go wrong?
did the prediction land or miss after the match?
is the user trusting a slip blindly?

The goal is not to promise outcomes.

Predictions are informational only. No result is guaranteed.

The Core Product

BetLogic is built around a few main user flows.

Daily Matches

The Daily Matches page gives users a central place to explore football fixtures, AI previews, tips, live status and results where available.

The goal is to make the match board easy to scan, but still connected to deeper analysis.

A user can go from:

Daily match board
→ match card
→ match detail page
→ AI preview accordion
→ risk/context sections

That structure matters because the product should not feel like a random list of predictions. It should feel like a system.

AI Match Previews

Each match page can include an AI-assisted preview with plain-language reasoning.

Instead of only showing a number or a final pick, the preview is designed to explain:

match context
team form
risk signals
tactical or situational notes
match tips
result context when available

The preview is displayed in a simple accordion format so users can explore the reasoning step by step.

For me, this is one of the most important parts of the product.

Football analysis should be understandable, not just statistical.

The AI Bet Slip Check Tool

One of the features I’m most excited about is the AI Bet Slip Check tool.

The idea is simple: users should be able to review the risk of a football bet slip before trusting it blindly.

A lot of slips are built emotionally.

Someone adds one more match. Then another. Then a low-odds favourite. Then a random league. Suddenly the slip looks confident, but the risk is stacked across too many selections.

BetLogic tries to slow that process down.

The AI Bet Slip Check tool lets users upload a slip screenshot. The system reads selections, odds and stake when visible, then allows the user to review and correct the extracted details before returning an informational risk breakdown.

The goal is not to say:

This will win.

The goal is to highlight things like:

weak selections
risky combinations
stacked risk
false confidence from low odds
selections that may need review
OCR mistakes that should be corrected
overall slip risk awareness

This is where I think AI can be useful in a responsible way.

Not by promising results, but by helping users understand risk.

Building My Own Email Marketing Hub

One decision I made early was to build my own email marketing hub inside BetLogic.

Instead of relying entirely on third-party email marketing platforms, I wanted more control over:

subscribers
campaigns
match-preview emails
World Cup updates
bonus comparison emails
operator review updates
product announcements
campaign logs

This gives me the ability to connect email directly to the product.

A new AI match preview can become an email campaign.

A World Cup update can become a newsletter.

A sportsbook comparison can become a targeted email.

That may sound simple, but for a small product it matters. It means distribution is part of the product infrastructure instead of a separate workflow.

The AI News Hub

Another part of BetLogic is the automated news hub.

Football moves fast, especially during tournaments. Matches, results, previews and storylines change every day.

The goal of the news hub is to support AI-assisted workflows around:

World Cup news
match previews
match reactions
tournament context
editorial-style updates
post-match reports

The bigger idea is to connect multiple outputs from one core workflow.

A match preview can become:

a page
an email
a social post
a post-match review
a news update

That is the kind of content system I want BetLogic to become.

Operator Reviews and Bonus Pages

BetLogic also includes sportsbook and casino operator reviews.

This part has to be handled carefully.

I do not want these pages to be thin affiliate content. The goal is to build them with structure, clarity and compliance.

Operator pages can include:

bonus details
payment information where available
country availability
restrictions
eligibility notes
terms and conditions reminders
responsible gambling language
comparison sections

The key principle is simple:

Inform, compare and explain.

No guaranteed outcomes. No “free money” language. No unrealistic promises.

Why I Built the Infrastructure This Way

BetLogic is not just a collection of pages.

It is becoming a connected product system.

The main pieces are:

Match data
→ AI analysis
→ match pages
→ tip tracking
→ bet slip risk checks
→ news hub
→ email marketing
→ social distribution
→ SEO pages

That is why I care so much about automation.

Football content has scale. There are daily matches, tournament updates, live results, operator pages, emails and social formats.

Trying to manage all of that manually would be slow and inconsistent.

AI helps with speed and structure, but it does not remove responsibility. The product still needs human judgment around UX, compliance, SEO, content quality and brand direction.

Tech and Product Focus

BetLogic is built as a modern web product, not just a content site.

The current focus areas are:

Next.js architecture
responsive UI
SEO metadata and content hubs
AI-assisted content flows
match detail pages
email marketing infrastructure
analytics
performance monitoring
affiliate/commercial pages
World Cup coverage

As a solo founder, I’ve had to think across the full product stack: frontend, SEO, content, automation, compliance, distribution and user experience.

That has been difficult, but also the most valuable part of building this.

What Makes BetLogic Different

The product is built around a few beliefs:

Reasoning over blind picks

Users should understand why an analysis exists.

Risk awareness over hype

Football is unpredictable. The product should make risk visible.

Bet slip analysis over emotional decisions

A slip can look confident while still being fragile.

Transparency over perfect-looking records

Tracking landed and missed tips matters.

Product infrastructure over random content

AI previews, news, email, match pages and operator reviews should work together.

What’s Next

The next stage for BetLogic is growth and refinement.

I’m currently focused on:

improving AI match previews
making the AI Bet Slip Check tool more useful
expanding World Cup coverage
improving post-match accountability
growing organic traffic
improving email campaigns
building more shareable social formats
strengthening the operator review structure

There is still a lot to build, but the foundation is now in place.

Final Thoughts

Building BetLogic has shown me that AI is most useful when it is part of a real product workflow.

Not just text generation.

Not just predictions.

But a system that connects analysis, content, email, SEO, social distribution and user experience.

That is what I am trying to build with BetLogic: a football intelligence platform that explains more, tracks more, and communicates more responsibly.

BetLogic is live here:

https://www.betlogic.eu

AI Bet Slip Check:

https://www.betlogic.eu/tools/bet-slip-check

Daily Matches:

https://www.betlogic.eu/daily-matches

18+ | Predictions are informational only and never guaranteed. Always gamble responsibly.