Step-by-step guide

How to bet with Claude step by step: a Project with your rules and your history

A workspace that does not forget your limits: written bankroll rules, your history loaded and an artifact that checks every bet before you place it.

To bet with Claude, you create a Project with your bankroll rules, load your betting history and ask for an artifact that checks every bet before you place it. Claude does not bet for you and does not know the result: it reads your full log, flags your repeated mistakes and warns you when you break your rules.

Flamengo players during a match in Brazil
Flamengo: a team that plays several competitions at once leaves a long history, exactly what is worth reading in full — Photo: Artigas Pessio · CC BY-SA 4.0 · Wikimedia Commons
  • The Project stores your rules and your files: every new chat starts out knowing your limits.
  • Your own history is the most valuable data: it shows where you lose because of discipline and not bad luck.
  • The check artifact is a calculator that reviews stake, odds and value before every bet.

There are eight steps to take little by little. Bookmark this article: your ticks stay in this browser and you resume from the last step.

Your progress is saved in this browser.

Why does betting with Claude start with your history?

Most people ask the AI about the next match.

This workflow starts the other way around: with your past bets.

That is where your mistakes are, and they are easier to fix than chance.

Claude fits that task for two reasons.

It works with long texts, so it can read an extensive log in one go.

And its Projects keep instructions and files from one conversation to the next.

That does not make it better than other AIs at everything.

In the comparison of AIs for betting you will see that each one performs best at a different task.

If you are looking for the general version of the method, it is in how to bet with AI.

Features change: check in the app what your plan includes.

Claude does not know the result of any match and can make up data if you do not provide it.

Betting involves the risk of losing money, for adults 18 and over only.

What goes inside the Project

A well-organized Project has four pieces.

Each one is updated at a different rhythm.

PieceWhat it containsWhen it is updatedTypical mistake
InstructionsBankroll, maximum stake, minimum odds, marketsOnly on fixed datesChanging them during a bad run
HistoryYour complete betting logOnce a weekUploading only the winners
Mistake notesThe patterns you have already detectedAfter every reviewNever writing them down
Check artifactPre-bet rules calculatorWhen the rules changeUsing it after betting

How to bet with Claude in 8 steps

Steps 1 to 5 build the workspace.

Steps 6 to 8 are the routine for every bet.

Tick each one when you finish it.

AC Milan players during an Italian league match
AC Milan: the rules are written before the big match, not in the middle of the excitement — Photo: Saggittarius A / Derivative work: Danyele · CC BY 4.0 · Wikimedia Commons

What instructions you write for the Project

These instructions have a different goal from an analysis prompt.

They do not ask Claude to find bets.

They ask it to stop you.

Prompt
In this Project you are the auditor of my betting method, not a tipster.
My rules are:
- Bankroll: [BANKROLL].
- Maximum stake per bet: [MAXIMUM STAKE]% of the bankroll.
- Minimum odds: [MINIMUM ODDS].
- Allowed markets: [MARKETS].
- Maximum bets per day: [NUMBER].
- Date of the next rules review: [DATE]. Before that date I do not accept changing them.
The Project's history file is my only source on my past bets.
If I ask you for something that breaks a rule, tell me in the first line of your answer.
Always split it into two parts: “what your data says” and “what I am assuming”.
If you do not have a piece of data, write “I do not have it”. Do not fill in with your own estimates.
Never tell me what to bet on and never promise results.

The review date rule is the most useful one.

It prevents the classic mistake: raising the stake to win back what you lost.

Rules get changed with a cool head, calendar in hand.

How to ask it to read your whole history

This is the use where the long context shows.

Instead of looking at the monthly summary, Claude goes through the log bet by bet.

Look for behavior patterns, not predictions.

Prompt
Read the Project's full history, row by row.
First give me the totals so I can compare them with my spreadsheet: number of bets, total stake, net result.
Then look for these patterns and show the rows that prove them:
1) bets with a stake above the maximum, and what had happened in the previous bet,
2) days with more bets than my limit,
3) markets or odds ranges where my losses are concentrated,
4) bets outside the allowed markets.
For each point, say whether the number of cases is enough to call it a pattern or whether it could be chance.

The last line of the prompt matters.

With few bets, almost any result can be a coincidence.

We explain it in how many bets you need to know whether you are winning.

Copy the confirmed patterns into a short note.

Upload it to the Project as a file.

From then on, Claude reminds you of them when you are about to repeat them.

How to build the check artifact

An artifact is an interactive piece that appears next to the chat.

Here you use it as a calculator with your rules built in.

It does not predict anything: it checks.

Prompt
Create an interactive artifact called “Pre-bet check”.
Fields that I fill in: current bankroll, odds, my estimated probability in %, stake I want to place, market and bets already made today.
Have it calculate and show: implied probability of the odds, expected value in %, stake as a % of the bankroll.
Have it compare against my Project rules and mark each one green or red: maximum stake, minimum odds, allowed market, daily limit, positive expected value.
If anything is red, have it show the text “Breaks your rules”.
No decorative charts: a single screen, readable on a phone.

Test it with a known case.

Example: odds of 2.00 and an estimated probability of 55%.

The implied probability must come out at 50% and the expected value at +10%.

If the artifact shows other numbers, ask for a correction.

A calculator that nobody has verified is worse than having none.

And remember that the official log lives in your spreadsheet, not in the artifact.

Tottenham Hotspur players during a Premier League match
Tottenham: before betting on a match like this, the pre-bet check takes a minute and prevents the impulsive stake — Photo: Jim Easton · CC0 · Wikimedia Commons

How to use it before every bet

The daily routine is short.

Match data, probability, check and log.

When the artifact shows all green and you still doubt, ask for a second look.

Prompt
I am about to place this bet: [MATCH], [MARKET], odds [ODDS], stake [STAKE].
My estimated probability is [PROBABILITY]% and I got it from: [WHERE IT CAME FROM].
Review three things and answer one line for each:
1) does it meet all the Project rules?,
2) does it look like any of the mistake patterns in my notes?,
3) which piece of data in my estimate is the weakest?
Do not give an opinion on who is going to win.

The third question teaches the most.

It forces you to see where your number came from.

If the answer is “a hunch”, you already know what to do.

Which common mistakes to avoid

  1. Using the Project to ask for predictions instead of checks.
  2. Uploading an incomplete history, without the lost bets.
  3. Not comparing Claude's totals with those in your spreadsheet.
  4. Leaving the history file without an update for a month.
  5. Running a bet through the artifact after betting, when it is no longer useful.
  6. Treating as data a figure that Claude could not back up with a source.

When another AI is a better fit

This workflow is about checking and reading, not speed.

Depending on what you need, another tool may be a better option.

And for today's matches you do not need to build anything.

The Gambeta betting AI publishes free predictions with its track record in plain view.

Your Project helps you decide which ones fit your rules.

Responsible gambling: a good check reduces mistakes, not risk.

Bet only money you can afford to lose and read the responsible gambling guide.

For adults 18 and over only.

Your Project already stops you when you break a rule.

Now improve the raw material: a tidy log with the guide to betting control in Excel.

Then learn to read your numbers without fooling yourself with variance and sample size.

And if you want to add parameters to your instructions, continue with create and train your own AI.

Build the log in Excel

Frequently asked questions

Can you bet with Claude?

Claude does not place bets and does not connect to any bookmaker.

It is useful for organizing your method: rules, history and pre-bet checks.

The decision and the bet are yours.

What is a Claude Project?

It is a workspace with fixed instructions and its own files.

Every conversation inside the Project takes them into account.

That way you do not repeat your bankroll or your rules in every chat.

What is an artifact and what is it for here?

It is an interactive piece that Claude generates next to the chat, such as a calculator or a spreadsheet.

In this guide you use it as a pre-bet check.

Your official log is still in your spreadsheet.

Can Claude make mistakes when reading my history?

Yes.

It can miscount or misread a column, like any AI.

Always ask for the totals and compare them with those in your spreadsheet.

Does it work if I do not have a history yet?

Yes, but you start with half of the method.

Build the log first and load the rules.

The history diagnosis only makes sense once you have gathered a reasonable sample.

Does Claude look up match data on the internet?

It can use web search if it is available on your plan.

Still, it is best to ask for the source of each piece of data and open it.

For last-minute news there are faster tools.

–
Next generation
New AI picks
9
Picks today
9
Live
2,005
Total picks
Related topics

🧠 AI reasoning for upcoming matches