A record of whether the setup actually worked

The startup idea

The problem

A chart pattern feels true because the last time it worked is the one they remember.

Who would pay for this?

Primary

Technical traders who already have a setup and a machine they will keep their data on.

Secondary

A small desk that wants the same report on every rule.

Early adopter

Someone who journals trades by hand and already suspects the memory is flattering.

How could it make money?

Possible models. Nothing here is a claim about what LuxAlgo charges.

• The post says the engine is free and open source. A paid layer is data, a hosted run, or a private rule set.
• Do not charge for a prediction. Charge for the record, if anyone asks to keep it.

What would the MVP look like?

1. One setup.
2. A count of how often it played out.
3. The sample size next to the number.
4. A way to open the trades behind it.

How to validate the idea

• Run it on one setup you actually trade. See if the number changes what you do next week.
• If you ignore the number, the product is a chart toy.
• Ask two other traders to bring a setup. Watch whether they want the losing trades listed, or only the summary.

How to differentiate

• One market you know, not every asset.
• Local data, for people who will not upload a blotter.
• The losers are visible. A product that hides them is a marketing page.
• Leave order execution to the broker they already use.

Product that inspired this idea

An open-source statistics engine for technical traders. The post says it runs on your machine, shows how often a setup played out, and includes the sample size on each number.

Posted by @LuxAlgo. Watch the original launch. No separate product site is listed unless the post itself is the source.

• markets
• open-source

Related startup ideas

• Human-looking cursors for computer-use agents

  A small open library of mouse motion so an agent cursor does not look like a teleport.

• Post-train an open model without leaving its original format

  A framework for teams that want to tune an open model and still publish it as a normal model repo.

• Spatial scenes built in code, not shipped as files

  A kit that generates a Vision Pro scene at load time, so the app does not carry a folder of models.

• A browser inside the coding agent’s terminal

  Open a real browser from the agent session so the agent can see the page it just changed.

• A coding agent that runs a small model in the browser

  A coding assistant that runs locally in the browser on a small model, for people who will not send the repo out.

• A desktop for making games with the model you already pay for

  A local app that turns a Claude or ChatGPT subscription, or a local model, into a game-making bench.

More developer tools ideas