The problem I kept seeing
Most sim-racing tools either talk too much, say the obvious, or feel
disconnected from the way serious drivers actually improve. The real
value is not just saying "car left" or reading out a lap time. It is
knowing what should stay local, what should wait, and what is worth
bringing back after the session.
That is the core idea here. Urgent race-day calls need to be
immediate and predictable. Debrief, trend reading, and strategy can
take a little more thought. Mixing those two layers badly is where
most products start to feel noisy.
How the product is meant to feel
I want this to feel like there is a real team in your ear, not a
chatbot pasted onto telemetry. That means the product should be
useful in the moment, quiet when it should be quiet, and honest
enough to help you improve after the run.
Also, it should be configurable. Different drivers want different
radio styles. Some want concise prompts. Some want more context.
Some only want feedback after the session. That should be a
first-class part of the product, not an afterthought.
What RACEngineer.ai is aiming for
- →Local spotter calls that stay fast and deterministic
- →Cloud-side judgement for strategy, coaching, and debriefs
- →Driver memory that becomes more useful over time
- →A system that respects attention instead of fighting for it
Where this is today
This is still early. I am shaping the first release with real
product constraints in mind: how it behaves under pressure, how it
should talk, what it should remember, and what it should never
interrupt. If this resonates, I would love to hear how you race and
what would make a tool like this actually useful for you.