Sahin Boydas
Random theme
Select theme
Back to all articles

The Real Reason Your AI Models Are So Slow (It's Not Your Code)

How AI hardware choices make or break a startup: GPU shortages, cloud versus owned clusters, custom chips, and what each option really costs founders.

2024-09-237 min read763 words

After years in the trenches of Silicon Valley, I've seen firsthand how the right AI hardware can make or break a company. I'm sharing the hard-won lessons and contrarian insights I wish I had when I started, from navigating the GPU shortage to building our own custom silicon.

The Reality Nobody Talks About

A lot of the advice on AI hardware rests on assumptions that made sense five years ago. The world has moved on.

The first thing to understand is that customer feedback is the only metric that matters. I've seen this play out across dozens of companies. The pattern is unmistakable.

Many teams spend months on the wrong path before realizing that your team matters more than your technology. Once they make the switch, everything changes.

The Framework That Actually Works

Here is a simple framework for evaluating AI hardware. It's not complicated, but it requires discipline.

Step 1: your team matters more than your technology

This is where most people go wrong. They skip this step entirely and jump straight to execution. Don't do that.

Step 2: you should focus on one thing and do it exceptionally well

Once you have the foundation right, this becomes much easier. I've watched founders struggle with this for months when the answer was staring them in the face.

Step 3: Iterate relentlessly

Nothing works perfectly the first time. The companies that get AI hardware right treat it as an ongoing process, not a one-time project.

Why Most Approaches Fail

Many common approaches to AI hardware are flawed at the root.

The root cause is usually one of three things:

Copying what big companies do without understanding why they do it. What works for Google doesn't work for a 10-person startup.

Over-engineering the solution when a simple approach would work better. I've seen teams spend six months building something that could have been done in two weeks.

Ignoring the human element. Technology is the easy part. Getting people to actually use it is where the real challenge lives.

Lessons From the Trenches

I want to share a few specific lessons I've picked up over the years. These aren't theoretical. They come from real companies, real failures, and real successes.

Lesson 1: The best time to start thinking about AI hardware was yesterday. The second best time is now. Don't wait until you have the perfect plan.

Lesson 2: Hire for attitude, train for skill. The best people at AI hardware are rarely the most technically gifted. They are the most curious and persistent.

Lesson 3: Your competitors are probably getting this wrong too. That's your opportunity. While everyone else is following the same playbook, you can zig when they zag.

This connects to broader themes around TPU, AI chips, quantum computing, NVIDIA that I've been thinking about a lot lately.

What's Next

Best practice in AI hardware is changing fast. What worked last year might not work next year. That's both the challenge and the opportunity.

My advice: stay curious, stay humble, and stay close to the people who are actually doing the work. Read less thought leadership and do more experiments. Talk to fewer consultants and more practitioners.

If you're building in this space, the best time to get AI hardware right is before you need to. Don't wait for a crisis to force your hand.

I'll keep sharing what I learn. This stuff matters too much to keep to myself.

FAQ

Frequently Asked Questions

Q:How has this view evolved over time?

My thinking on most topics has changed significantly over the years. Early in my career, I held many conventional views that experience proved wrong. I try to update my beliefs when the evidence changes.

Q:Do all experts agree with this view?

No, and that's fine. The best ideas in business are often contrarian. I share my perspective based on my experience and data, but I encourage you to seek out opposing viewpoints and form your own conclusions.

Q:How can I apply this thinking to my own situation?

Start by identifying the core principle behind the opinion, not the specific example. Then ask yourself: does this principle apply to my context? If yes, test it in a small, low-risk way before going all in.

Q:What experience informs this perspective?

This perspective comes from over a decade of building companies in Silicon Valley, two successful exits (RemoteTeam to Gusto, MovieLaLa to Gfycat), and investing in 234 startups including Anthropic, OpenAI, and Scale AI. I write about what I've lived.

Written by

Sahin Boydas

Serial entrepreneur, #1 angel investor, author of Becoming Top 1%

Get Sahin's Weekly Insights

Join 10,000+ founders and investors. One email per week with actionable advice on startups, investing, and building in the AI era.

No spam. Unsubscribe anytime.