Let's be honest. You're a leader. You've built companies, you've shipped products, you've navigated brutal market shifts. But this AI thing? It feels like trying to catch smoke. The jargon is a nightmare, the pace is just insane, and it feels like if you don't have a machine learning PhD, you're already hopelessly behind.
I’ve had this exact conversation over coffee with at least 50 founders and executives in the last year. They see the headlines, they hear the noise, but they're stuck. They feel paralyzed. They all ask me some version of the same question: "Sahin, how can I possibly lead this kind of change if I can't even explain what a transformer model is?"
Here’s the secret: you don’t need to.
I’ve been in the Silicon Valley game for a while. I started my first company when I was 17. I’ve been in the trenches, built products from scratch, and had two successful exits: RemoteTeam, which was acquired by Gusto, and MovieLaLa, acquired by Gfycat. I’ve also been lucky enough to write checks for over 200 startups as an angel investor, including foundational AI companies like Anthropic, OpenAI, Scale AI, and Hugging Face. And I can tell you, without a doubt, the most successful AI adoptions I’ve seen were not led by the most technical people. They were led by the smartest business people.
Leading an AI transformation isn't about writing Python scripts. It’s about asking the right questions, empowering the right people, and being absolutely relentless about business value. Here’s my playbook for how to do it.
1. Stop Chasing Shiny Objects, Start with a Real Problem
The biggest mistake I see is companies starting with the tech. Someone on the board reads an article about generative AI, and suddenly the mandate from on high is "we need a gen AI strategy." That’s a guaranteed way to burn millions of dollars on a cool tech demo that goes straight to the trash heap.
Forget about AI for a minute. What are the biggest, hairiest, most expensive problems in your business right now?
- Is your customer churn rate making you sick?
- Is the cost of your customer support center completely out of control?
- Does it take your marketing team three weeks to get basic campaign analysis done?
Find a real, painful, and measurable business problem. Start there.
At RemoteTeam, we didn't set out to build an "AI company." We set out to solve the absolute nightmare of managing a global workforce. The compliance, the international payroll, the onboarding—it was a chaotic mess. We only turned to technology, including automation and intelligent workflows, after we understood the problem so deeply we could feel it. The tech was just a tool to solve the pain; it was never the goal itself.
2. Find Your "Translator"
You don't need to be the expert, but you absolutely need an expert in your corner. I call this person the "Translator." This is someone who can live in both worlds—they can talk to your engineers about model accuracy and then walk into the boardroom and explain the ROI to your executive team without breaking a sweat.
This might eventually be a "Chief AI Officer," but it doesn't have to be a C-suite role, especially when you’re just starting. It could be a sharp product manager who gets the business, a data-savvy analyst who's tired of the old way of doing things, or an engineer who actually likes talking to people.
Your job as a leader is to find this person, empower them, and give them a direct line to you. Shield them from the corporate bureaucracy. Let them run small, fast experiments. When I invested in Scale AI, their founder, Alexandr Wang, was obsessed with the messy details of data labeling. He was the ultimate translator between the abstract needs of AI developers and the operational reality of creating high-quality training data. He didn't just build tech; he built a solution to a fundamental, painful bottleneck.
3. Think Small, Win Fast
An "AI transformation" sounds massive and terrifying. So don't call it that. Call it "the customer support bot project" or "the sales forecasting experiment."
Pick one, maybe two, pilot projects. They must be:
- High-impact: It solves a real problem that people actually care about.
- Low-risk: It won’t crater the company if it fails.
- Measurable: You can clearly define what success looks like in 90 days, not in two years.
For example, instead of trying to automate your entire call center on day one, what if you built an internal AI tool that helps your support agents find answers 50% faster? The goal isn't to replace the agents, but to make them superhuman. That’s a concrete, achievable win. You get real results, your team builds confidence, and you learn a ton in the process.
4. Your Data Is Your Gold. Treat It That Way.
Every leader I talk to wants to build some incredible AI-powered future, but their data is a dumpster fire. It’s locked away in different departments, it’s riddled with errors, and nobody trusts it.
AI is nothing without good data. It’s like trying to cook a gourmet meal with rotten ingredients. It doesn't matter how fancy your oven is. Before you even think about complex models, you have to get your data house in order. This is not a glamorous job, but it is the most important one.
This is where you, the non-technical leader, have all the power. You can be the one to break down the organizational silos. You can mandate a single source of truth for key metrics. You can invest in the tools and the people needed to clean, structure, and govern your data. This is a leadership challenge, not a technical one.
5. It’s About Change Management, Not Project Management
Finally, you have to remember that you are not just implementing a new piece of software. You are fundamentally changing how people work. And people, by their very nature, resist change. They are worried about their jobs. They are comfortable with the old, inefficient way of doing things.
Your most important role is to be the Chief Evangelist for this change. You need to be a broken record, constantly communicating the "why." Why are we doing this? How will it make our customers’ lives better? How will it make our employees’ jobs more interesting and valuable, not obsolete?
When Gusto acquired RemoteTeam, a huge part of the integration was helping a 2,000-person organization understand the power of our tools. It wasn’t just about the tech. It was about painting a clear and compelling picture of the future of work and showing them how we could all get there together.
Don't just show them charts and data. Tell stories. Highlight the wins, even the tiny ones. Celebrate the people who are leaning in and experimenting. Address the fears head-on and be brutally honest about the challenges.
Leading an AI transformation is a massive opportunity. But it’s a leadership opportunity, not a technical one. Stop worrying about the jargon and start focusing on the fundamentals: real business problems, great people, and a relentless focus on creating value. The biggest risk isn't getting the technology wrong. The biggest risk is doing nothing at all.
Frequently Asked Questions
Do I need technical skills to lead an ai transformation (even if you don't understand the tech)?
Not necessarily. While technical understanding helps, the most important skills are clear thinking and the ability to break problems into smaller pieces. Many successful founders I've invested in started with zero technical background and either learned enough to be dangerous or found the right technical partner.
How do I measure success with this approach?
Pick one or two metrics that directly tie to your goal and track them weekly. Vanity metrics like page views or follower counts rarely matter. Focus on metrics that reflect real engagement or revenue impact.
What tools do I need to get started?
Start with the basics. You don't need expensive software or fancy tools. A spreadsheet, a note-taking app, and direct access to your customers will get you further than any enterprise platform. Add tools only when you hit a specific bottleneck.
How long does it take to lead an ai transformation (even if you don't understand the tech)?
The timeline varies depending on your starting point and resources. For most founders, expect 2-4 weeks for initial setup and 2-3 months to see meaningful results. I've seen teams move faster when they focus on one thing at a time rather than trying to do everything at once.