Skip to content

David's morning scripts now run in about a third of the time.

Teams ask us what people actually bring to office hours. David at Broadview sped up his morning run without rewriting a single script.

Outcome: The morning scripts run in about a third of the time, as he reported, started before he leaves for the office.

Same R scripts, a third of the time: David's morning run0:58
“It runs like in a third of the time and I can hit go on it before I leave for the office.”
David · Broadview Group

Before

Every morning, scripts ran one after another.

David starts each day by running a few R scripts in the right order. His team used AI a lot, just not on the scripts that affect trades.

What he built

Same scripts, a new runner.

David kept the scripts as they were and wired up a runner around them, so they run in parallel. He credits a lot of his day-to-day speed to Claude Code.

What changed

A third of the time.

The run now takes about a third of the time, and he starts it before he leaves for the office. He shared it at B43 office hours, one of several wins the team brought that week.

What's next

Put it on a schedule.

The next step is to run it on a schedule, so it's done before he gets in.

Read the video transcript

Every morning, David runs a few R scripts. Each one has to run in the right order. The team already used conversational AI a lot. Not on the scripts that affect trades. Keep the same R scripts. Wire up a runner around them. Hit go before leaving for the office. By the time he gets there, it's done. A third of the time. He shared it at office hours. It got the whole team spotting other ways to use conversational AI. In his words: "I use a lot of Claude code and I find a lot of efficiency in that and that's helped us." "It runs like in a third of the time and I can hit go on it before I leave for the office."

More stories

Ready to see where your team stands?

30 minutes with Bryce. No commitment.