top of page

Give AI coding agents the structure they need to accelerate your team’s machine learning (ML) projects even further.

Icon of a laboratory flask with molecular structure inside, enclosed in an orange circle

CASE STUDY / THEN CAME AI

Alkemy Brought the Discipline:AI Coding Agents Brought the Speed

How Team d²l discovered a winning combination

Project Overview

Recipe for a Repeat Win

Across the ML lifecycle, Alkemy made the difference by stepping in where AI coding agents struggle on their own.

​

​AI coding agents bring a huge amount of machine learning knowledge to the table, but every session starts from an empty chat. They don’t inherently know what success looks like, what decisions were made last week, and how to navigate scattered notebooks and scripts.

 

Alkemy was built to give data scientists a complete operating framework for the ML lifecycle:

 

  •  Structured projects

  •  Reproducible datasets

  •  Structured experiments

  •  Artifact management

  •  Deployment from the same code used in experiments

 

It became immediately clear that these players could benefit from this coach.  Then the team really geeked out to prove the concept...

Video Transcript (left)

[00:00] Introducing Alkemy Hi, I'm Devin. I work with Team d²l, and I'm one of the creators of Alkemy. Alkemy is a Python framework that structures machine learning projects end to end, from dataset to deployment. We built it for data scientists, but what surprised us is that Alkemy turned out to give coding agents exactly what they need to do ML work reliably. This means the person driving an ML project doesn't have to be a data scientist or experienced coder anymore. Basic Python skills are helpful, but what matters most is using your domain knowledge to describe the problem clearly, decide what good enough looks like, and flag results that don't make sense. In this video, I'll ask Codex about a project we've been building together and walk you through what it's doing and why it matters. [00:49] Working with Codex and Alkemy As I work with Codex, I'll voice over what it's telling us. If you'd like to see exactly what it's doing, I recommend just watching the video through, then come back, slow down the video while it's working, and then pause once you see the final output. In this project, we're looking at a fraud data set with credit card transactions. It's a public data set, but I've done my best to prevent the agent from knowing I got it from Kaggle, so it can't just go out on the web and figure out what the best solution is automatically. I'm doing a tech demo, and my team is evaluating Alkemy. Introduce us to the project and what we've achieved by working together. How much effort do you think we're saving versus using Codex without Alkemy? I'm sharing my screen and we're doing this live, so keep your response less than five bullets. [01:35] How Alkemy Guides AI Agents What we're seeing is the agent is checking workflows and rules before it decides what to do. This keeps them on track and frees you up from having to provide the same instructions over and over again. With Alkemy, agents are less likely to hallucinate or forget critical details because they're instructed to always journal their progress and record your feedback. A predictable project structure and a set of tools prevent agents from having to improvise as your project grows. The more experiments you run, the more the benefits compound. Let's try something else now. I'm about to walk into a standup, take a look at the project, and put together three bullets I can share. Data scientists need to understand performance, and our product manager needs to relay an update across our organization. [02:29] Using Domain Knowledge to Guide the Model One of my favorite parts of this project was that the agent recommended using historical transaction patterns because they're often useful for predicting fraud. Alkemy gave it the awareness to ask whether the features would actually be available at predict time. Without this, we could have spent days or weeks building a perfect model that can't actually be used. I told the agent, "The features aren't currently available, but we should attempt to prove their value in case it's worth putting on the engineering roadmap." From there, the agent was not only able to build a model that met our performance goals, but it was also able to make the case that a scoped investment was justified. [03:07] Deploying Machine Learning Models In Alkemy, deployments are easy. We give you everything you need to stand up an API or run batch scoring. Launch the API for the deployed model, generate some predictions, and show us the results. The agent launched an API and made a few requests so we can see the model in action. Deployments are easy. The same code that gets packaged for production is the same code that trained your model. Deployments can be run on any platform where Alkemy can be installed. [03:37] From Model to Reliable Deployment Whether you're an experienced data scientist or someone with strong domain knowledge and a problem to solve, Alkemy makes all the difference. It isn't just for building models. It's the difference between a model that lives in a notebook and one that ships reliably every time. That's it for today, guys. If you'd like to know more and take a peek under the hood, click the link in the description to reach out to Team d²l. Please like and subscribe, and I'll see you next time.

Video Transcript (right)

[00:00] What Is Alkemy? Hi, it's Mark with d²l. Today I'm going to talk to you a little bit about Alkemy. Alkemy is a framework that provides structure around the entire machine learning life cycle. So, everything from the feature generation step to the experimentation process to model selection and deployment, and pretty much everything in between. [00:17] Using AI Agents with Alkemy Today, we're actually able to use agents on top of Alkemy to accelerate the machine learning process even further. This means teams can move even faster without deep expertise and with far more consistent outcomes. So today, I'm just going to go over a quick little case study that we did using Alkemy to predict outcomes of March Madness games. [00:35] March Madness Case Study Okay. So we used Codex to interact with Alkemy for this project, but you can use whatever agent you want. Alkemy is actually agent agnostic. So first, I'm just going to ask it for the results of our back testing, as well as the results of our live bets that we placed in 2026. [00:54] Backtesting and Live Betting Results Okay, so as you can see, the backtesting results looked pretty great. Through 229 graded bets over the course of four seasons, we ended up with a 60.7% hit rate and a 15.9% ROI. So, that was super promising. Let's see how we actually did in live betting in 2026. We actually did even better. We had a hit rate of 66.7% over 39 bets with an ROI of 27.3%, which is pretty great. [01:29] Model Experiments and Selection So, next, let's ask it how many experiments were run before choosing the champion model. So, we ran 108 total trials across two different experiments, and that was all handled through Alkemy. And the experiments that we ran were Elastic Net and CatBoost, and then we blended those together. But you can run any model you want using Alkemy. [01:52] Learn More About Alkemy That's it for today. Please like and subscribe, and if you'd like to learn more about how Alkemy works and how it can help you accelerate your machine learning projects, just click the link below to reach out to Team d²l. Thanks for watching.

Results

What Team d²l Learned

Across the ML lifecycle, Alkemy made the difference by providing the defense where AI coding agents struggle on their own:

Project Setup

Agents inherited a standard project layout with built-in conventions for code, config, and artifacts.

Building Datasets

Datasets were validated objects agents could reference by name across sessions.

Running Experiments

Experiments and artifacts were tracked automatically, with results and feedback recorded so agents could use prior runs to guide iteration.

Comparing to a Benchmark

Benchmarks and prior runs lived inside the project structure, so agents could compare new results against the current bar.

Deployment

Deployment used the same code path as experiments - no rewrite and no drift.

Handing off Mid-project

New session inherited structure, history, and current state from the framework itself.

Ongoing Maintenance

Lifecycle structure was part of the system, not something the team had to build and maintain.

Ready to get in the game? Get in touch to take the next step in your data journey.

bottom of page