QuantAscent

QuantAscent · Article

I had Claude design a stock strategy. Then I tested it the honest way.

One unscripted 75-minute session: Claude picks the rules, a backtest and a two-year holdout judge them, then a paper account runs them.

Brandon Wilson · October 12, 2026 · Watch the full session · Also on Substack

I build portfolio software for people who manage their own money, and I wanted to know what happens when you let an AI pick the rules and a proper backtest gets the final say. So I recorded the whole thing in one sitting, no script, no retakes, and left in the parts where it went sideways. The video is 75 minutes. This is the short version, with the results and what I think they mean.

The setup

I opened Claude in an incognito window so it knew nothing about me or the software. I gave it the links to the QuantAscent documentation and one instruction: treat me as a complete beginner, both with the software and with investing, and walk me through building a custom strategy.

The goal I gave it was deliberately measurable. Risk-adjusted return at least as good as the S&P 500, with a lower beta. At least ten stocks, some of them technology companies, rebalanced quarterly, $25,000 allocated. Those are not recommendations. They are the constraints I needed so Claude had something to aim at. If you try this, give it your own.

The one thing Claude did that impressed me

Before building anything, Claude had me build the metrics database for January 2016 through December 2023 and keep 2024 to today out of it, “for an honesty check later.”

That is a holdout, and it is the single most important idea in the whole session. If you tune a strategy on a period and then report how it did on that same period, you are grading your own homework. Keeping two years unseen means the final test is on data the rules never saw.

It also picked 2016 as the start for a reason the documentation explains: that is where the delisted-company data gets dense. Testing only on companies that still exist today is survivorship bias, and Claude had read enough to avoid it.

Looking at the data before picking rules

The software ranks roughly 150 fundamental and price metrics by their information coefficient, which is a measure of how well a metric lined up with forward returns across the market. I set a floor of a $2 billion market cap, ran it, and sent Claude screenshots of the full table.

Two things stood out. First, a lot of metrics have error bars wider than the bars themselves, which means the signal is noise. That is normal in equities. If simple statistics worked cleanly, everyone would be rich.

Second, Claude had come in with a starting set of rules in mind, including an F-score and momentum. When the table said momentum had been weak over this window, it dropped it and rebuilt around quality and low volatility, which had the clearest track record. Changing your mind when the data disagrees is the right behavior. I still think it arrived with more preconceptions than it should have, and I say so below.

Building the rules

Six scoring criteria, each with a direction and a weight, led by one-year beta (lower is better) and a set of quality measures: return on capital, free cash flow yield, buybacks. Two filters: market cap of $2 billion and up, and filings no older than 135 days. A maximum of 15 holdings. Everything else on defaults.

Claude got a couple of field names wrong and asked for settings that do not exist for this strategy type. A screenshot of the screen fixed both. If you use an AI as a guide to unfamiliar software, that is the move: show it what you are looking at.

Version 1: not great

In-sample, 2016 through 2023, the first version trailed the S&P 500 by about four percentage points a year. Its Sharpe ratio was 0.50 against the index’s 0.73. It fell just as far as the market in March 2020, a 35% drawdown. The one box it checked was beta at 0.48: it moved about half as much as the market, but it gave up a lot of return to do it.

Version 2: clears the bar, barely

Claude’s one revision shifted weight toward the quality metrics. Same period, same settings:

  • Annualized return: 10.8%, versus 12.6% for the S&P 500

  • Sharpe ratio: 0.76, versus 0.73

  • Beta: 0.53, versus 1.00

  • Max drawdown: 36.6%, versus about 34%

Higher Sharpe than the index, lower beta, lower return, and a drawdown you would have to be able to stomach. Claude called it good enough and said we were done tuning. I agree, and the reason matters: if you keep adjusting weights until the backtest looks spectacular, the backtest is probably lying to you. That is overfitting, and it is the easiest mistake to make in this hobby.

The holdout

Then the test that counts. Same rules, January 2024 through October 2026, data the strategy had never seen:

  • Annualized return: 14%, versus 20% for the S&P 500

  • Sharpe ratio: 0.93, versus 0.98

  • Max drawdown: 11.6%, versus 18.8%

It trailed the index on raw return, which is what you would expect from a low-beta strategy during a stretch where technology led the market up 20% a year. It stayed close on Sharpe and lost noticeably less in its worst stretch. The reported beta of 0.02 is not believable: eleven quarterly data points is too few, and Claude flagged that itself.

Honest summary: on data it was not tuned on, the strategy behaved the way it was designed to. Smoother, lower return, smaller drawdown. Not a miracle, and not a disappointment.

What I think of Claude’s work

As a guide to the software, it did well. It explained concepts like the information coefficient without being asked, caught its own wrong assumptions when shown the data, and structured the whole exercise sensibly.

Where it fell short: it went straight from the rankings table to building rules. The software has a score analysis that shows, without running a full backtest, whether higher scores actually produced higher returns, and a breakdown by sector and by year. Claude skipped it. And it arrived with a preferred set of metrics before seeing any data. If I did this for myself rather than as a tutorial, I would spend more time challenging its first draft and asking why it believed what it believed.

Running it in a paper account

Testing is only half of what the software does, so I added the strategy to a paper account, meaning fake money with real market data through Interactive Brokers. That meant trimming two existing strategies to make room, setting a quarterly rebalance reminder, and previewing the full list of buys and sells. The market was closed, so I scheduled the rebalance for the next morning, then missed the window because of meetings, and did it by hand instead. The orders went through to the brokerage and the new strategy ended up holding about $23,600 against the $25,000 target, the difference being price movement between the preview and the fills.

One step I skipped on camera and would not skip with real money: reviewing every company on the buy list before placing the orders. The software has a company page for that, and an exclusion list if you decide you do not want one of them.

The process is identical for a real-money account. The only thing that changes is which account you are signed into.

Three things worth keeping

  1. Hold out data you will not tune on, and treat the holdout as the result.

  2. Stop tuning when the in-sample result is merely acceptable. A spectacular backtest is a warning sign.

  3. An AI is a useful guide and idea generator. The data and the test are the judge.

If you have tried this with your own setup, what did the holdout do to the AI’s first draft? And what would you want tested next? Walk-forward testing is my current plan for the next session.

The full session: I Built and Tested a Stock Trading Strategy Using AI (Claude). The software: QuantAscent, desktop portfolio management and strategy backtesting for self-directed investors. The documentation Claude read is at docs.quantascent.io. QuantAscent releases winter 2026; accounts created before November 12, 2026 get 50% off the first year. No card to sign up.

Everything traded here was in a paper account (fake money). The strategy, the metrics and the holdings are what my own rules selected for that account; nothing here is a recommendation to buy or sell any security. Hypothetical backtested research statistics about our software, gross of costs and taxes; not investment, financial, or tax advice. Past or simulated performance does not predict future results. QuantAscent Technologies LLC is a software company, not an investment adviser.