It shipped, and it was sinking them

“Two engineers, three months of code, and none of it worked.”

An AI startup · team of 1 to 10 · fully remote

Result

3 months → 4 weeks

Three months of broken, AI-generated code rewritten so it works

The situation

I built the system side of this product from the start: the mobile app, the .NET API, the database and the Azure setup. That side ran stable and on budget. The trouble was in the AI features. A PhD graduate specializing in AI built the AI features. After a month, he was let go because features were coming too slowly. A second engineer was hired to focus on the AI. Two weeks later, he asked me to review his code.

What I found

Nearly all of the code had been written by AI. Features didn’t work as needed and the logic failed, because neither AI engineer understood application architecture. The AI tools were producing code nobody could reason about.

What I did

  • Rewrote 3 months’ worth of code in 4 weeks
  • Spent a month training the AI engineer in application architecture and craftsmanship
  • Wrote the team’s coding practices and conventions into the AI agents’ instruction files

The result

  • 3 months of broken code replaced in 4 weeks
  • An engineer trained to build properly
  • Much of the product can now be built AI-first, with AI agents following the right standards

← See all five stories

Sound like your situation?

In 15 minutes, you’ll know what’s wrong, whether to repair or rebuild, and roughly what it’ll cost.

Book a free 15-minute call