Never in My Life Did I Think Marketing Would Be Harder Than Coding

Hello everyone, I am a 20-year-old studying economics. I'll cut to the chase. I have been really fascinated with building things, but due to my 0 technical background, I was never able to build anything. For the last 2 years, I started getting a grasp of what things are, understanding all sorts of technicalities, and building a few projects. Now I built a project myself, and after 2 months of 12 hours daily, I built a project that I think can actually be something.

a small summary-AuditChess is a chess analysis platform that goes beyond analyzing individual games. It analyzes your game history to identify recurring patterns in your play such as tactical weaknesses, opening problems, missed opportunities, blown wins, and endgame tendencies and turns those insights into a personalized report. It can also generate puzzles based on positions and mistakes from your own games, so you can actively work on the weaknesses it finds. their are a 100 more features on the website.

It took me some time to realise that building was not that tough of the part, but getting people to try it .i learned how to use typescript,java,python.sql,css while having a non technical background and never in my life did i think the difficult part would be marketing .I get 100–200 users daily, and 60% are unique, but the problem is I am not able to understand how can I market it. I try posting on Reddit or forums, people start thinking I am spamming, and they are already tired of a lot of people trying to use these platforms for marketing (I don't disagree with them, they are right, and I would have had a similar reaction to that).

  • I am very paranoid and am not able to post anywhere. How can I actually market my product where people don't see me as a spammer?
  • How can I get genuine feedback?
  • How can I get rid of being very self-conscious and paranoid so I can actually post online?
  • what are the different channels i can use people to use my web app other than
  • how can i actually post about it without people thinking i am spamming everywhere.
  • how to stop the overbuilding issue,one thing i faced that i tend to overbuild ,everytime i think "wait i can even uild this feature"and tend to forget i need to get people to try it.

I would really love it if people could help me get out of this mindset and figure out how to actually put myself and my product out there .

reddit.com
u/atulyahumea — 2 days ago

The Best Way to Work on Your Opening & Repertoire

For years, openings were probably the weakest part of my game.

I'd memorize a few "book" moves, feel confident, and then my opponent would play something I hadn't seen around move 6 or 7. Suddenly, I had no idea what I was supposed to do.

Eventually, I realized that improving your repertoire isn't about memorizing endless theory. It's about reaching positions you understand and continuously fixing the gaps in your preparation.

The basic loop is:

Play → find where you got lost → understand it → add it to your repertoire → practice → repeat.

The problem was that I couldn't find a tool that helped me do this efficiently.

So I built one.

AuditChess

AuditChess is a chess analysis tool for Chess.com and Lichess, built around build → view → practice → stress-test.

Build: Build your repertoire directly on the board. Stockfish evaluates your moves, while master-game statistics show what strong players actually played.

View: See your entire repertoire as a tree, with evaluations under each move, making gaps and weak lines easier to spot.

Practice: There are two modes:

  • Exact Recall: Reproduce your prepared lines from memory. Get a move wrong? Retry or reveal it.
  • Dynamic Deviation: AuditChess deliberately takes you out of book with a strong move you haven't prepared for. You then have to find the best continuation yourself, with your moves graded by the engine.

That second mode is the part I care about most. It's not enough to know your opening when your opponent follows your preparation — you need to know what to do when they don't.

It's not a course and it doesn't give you a "perfect" repertoire. It's a workbench for building, memorizing and stress-testing your own repertoire using the games you actually play.

I've been building AuditChess for the past few months, and I'd genuinely appreciate your thoughts. I'm still improving it, and feedback from actual chess players would help me make it more useful for the community.

If you try it, I'd love to hear what you liked, disliked, found confusing, or think is missing. Even small suggestions are useful.

And finally:

What's the opening position where you always reach move 8 and think, "Okay... I have absolutely no idea what I'm doing now"? 😭

Share it - maybe you can avoid ending up like my past self. And if you have any other thoughts on how opening preparation could be made better, I'd genuinely love to hear them.

u/atulyahumea — 3 days ago

I built a tool that treats your chess history like a dataset

I'm a statistics student, and I've always been fascinated by how much information you can extract from a sufficiently large dataset.

That got me thinking:

What if you treated someone's entire chess history as a dataset instead of analyzing each game independently?

So I built AuditChess.

You can import hundreds or thousands of Chess.com/Lichess games (or upload PGNs), and AuditChess tries to find statistically meaningful patterns in how you actually play.

For example, it can analyze:

  • Opening performance — not just win rate, but performance across different openings and sample sizes.
  • Recurring mistakes — which types of mistakes occur repeatedly rather than being isolated events.
  • Evaluation loss distributions — where and how severely you tend to lose advantage.
  • Conditional performance — how your results change depending on color, opening, time control, game phase, etc.
  • Longitudinal trends — whether your decision-making and performance are actually changing over time.
  • Blown winning positions — how often you fail to convert positions where you had a significant advantage.
  • Tactical patterns — recurring types of missed tactics and mistakes.
  • Statistical confidence — because a 70% win rate over 10 games doesn't mean the same thing as 70% over 500 games.

I'm particularly interested in questions like:

>

That's where concepts like sample size, confidence intervals and Wilson lower bounds become interesting in chess analytics.

It also generates personalized puzzles directly from your own games, so instead of solving completely random positions, you can practice positions that you actually reached and got wrong.

And there's a visual mistake tree that lets you see how mistakes are distributed across your games.

The whole idea started as a statistics experiment:

How far can you push the analysis of a chess player using nothing more than the games they've already played?

I built it for free and would genuinely love to see what people think:

https://www.auditchess.com

Especially interested in hearing from anyone who works with data/statistics:

What other patterns or statistical measures would you want to extract from a large chess dataset?

u/atulyahumea — 6 days ago

I’m building AuditChess - large-scale chess game analysis beyond single-game Stockfish review

Hello everyone,

I'm a statistics student and chess player, and over the past few months I've been building AuditChess, a chess analysis platform focused on extracting patterns from a player's entire game history rather than only analyzing one game at a time.

The core problem I'm trying to solve is:

>

What AuditChess currently does

The system can analyze large game histories and identify things such as:

  • Move-by-move Stockfish analysis and game reviews
  • Opening Tree statistics from a player's actual games
  • Opening-specific mistakes and recurring opening problems
  • Endgame profiling and performance patterns
  • Positions where a player throws away a winning advantage
  • Missed checkmates and positions where the player allows mates
  • Personalized puzzles generated directly from the player's own games
  • Repeated mistakes in similar positions across 100, 200, 1,000 or 5,000+ games
  • Playing-style profiling based on historical game data
  • Opponent analysis based on their previous games

The interesting part for me isn't simply running Stockfish.

It's the data aggregation and pattern detection layer on top of the engine.

For example, instead of:

>

I'm trying to answer:

>

That requires treating a player's games as a dataset rather than independent analysis sessions.

Some of the technical problems I'm working through

I'm currently using Stockfish for evaluation and chess.js/python-chess depending on the pipeline, with game histories represented through PGNs/FENs and derived positional data.

Some of the engineering challenges include:

  • Efficiently parsing and processing thousands of PGNs
  • Avoiding redundant engine analysis across repeated positions
  • Position normalization and comparison
  • Detecting recurring tactical/positional patterns
  • Aggregating engine evaluations across large game samples
  • Distinguishing meaningful recurring mistakes from statistically insignificant events
  • Generating useful personalized puzzles from engine-labelled positions
  • Handling opening statistics at scale
  • Keeping browser-side analysis responsive when using Stockfish/WASM
  • Caching expensive analysis without introducing stale or inconsistent evaluations
  • Making engine evaluations deterministic across positions
  • Turning raw engine output into something that is actually useful for human improvement

One particularly interesting problem is position similarity.

Two positions don't necessarily need to have the exact same FEN to represent essentially the same recurring mistake. I'm interested in how far this can be pushed without producing meaningless clusters.

There is also an interesting statistical problem here: if a player has 5,000 games, you can find hundreds of "patterns" simply by chance. So I'm thinking about how to distinguish genuine recurring weaknesses from noise.

What I'm looking for

I'd love feedback from people who have worked on:

  • Chess engines
  • Stockfish integrations
  • PGN/game databases
  • Chess ML
  • Position embeddings
  • Game-state clustering
  • Large-scale game analysis
  • Recommendation/personalization systems
  • Statistical analysis of sequential data

I'm particularly interested in:

How would you approach identifying recurring mistakes across thousands of chess positions?

Would you use handcrafted positional features, board representations, embeddings, clustering, engine evaluations, or some combination?

And more broadly, what would you want a system like this to extract from a player's game history that current chess analysis tools generally don't?

AuditChess is still actively being developed, so I'm very interested in technical criticism, architectural suggestions, and ideas for analyses that would actually be meaningful rather than just producing more statistics.

Project: AuditChess

reddit.com
u/atulyahumea — 9 days ago

What’s are the things you wish chess analysis could tell you?

Hello everyone! I'm a statistics student and a chess player.

I'm working on a chess improvement project and I've reached a bit of a blind spot. I have quite a few things working already, but I don't want to keep building features just because I can.

Some of the things I already have working :

  • Game analysis with detailed move-by-move feedback
  • An Opening Tree showing how your openings actually perform
  • Endgame profiling based on your games
  • Finding your opening blunders and recurring opening mistakes
  • Finding games where you threw away winning positions
  • Finding missed mates and mates you allowed
  • Puzzles generated directly from your own games
  • Finding the exact positions where you repeatedly make mistakes across 100, 200, 1,000 or even 5,000 games
  • playing-style profile based on your entire game history

These are just a few of the features I have. The idea is to go beyond simply telling you "you made a -3.5 move here" and actually identify patterns in your chess over a large sample of games.

But this is where I'm stuck, and I'd genuinely appreciate some help from the chess community.

What would you personally want a tool like this to do?

What is something you wish existing chess tools could tell you, analyze for you, or help you practice?

It can be something small, something completely crazy, or even something you think would be extremely difficult to build. I'm really interested in hearing ideas from players of all levels.

This is not a promotional post. I'm not sharing a link or trying to advertise anything here. I'm genuinely trying to understand what chess players would find useful, and your opinions and experiences would really help me decide what to build next.

I would honestly really appreciate your time, thoughts, and suggestions. Thank you so much to anyone who takes the time to share their views.

reddit.com
u/atulyahumea — 9 days ago