Saadiq Rodgers-King
4 exits · Facebook, GoDaddy, Gerber Life, Yuga Labs
Smart leaders are stuck on AI. I get their teams unstuck.
You've purchased the licenses. You've made the proclamations. You may even have an internal champion. Nothing has changed. I take a hands-on approach to showing your team what's possible and how.
exits_ Facebook · GoDaddy · Gerber Life · Yuga Labs
before_ Princeton CS · MIT Sloan MBA · 20+ years in product and engineering
The problem
6%
Executives who can point to org-wide AI ROI. 89% say AI made work faster
— Atlassian State of Teams, via SVPGThe tools exist. The results don't. The gap is not access. It's knowing what to aim for.
What shipped
8–12 hrs
of manual calling per request, replaced by a voice agent in production
A B2B corporate-housing company
embedded technical leadership · thirteen months and running
0%
AI mention rate across seven models, diagnosed with the cause in a two-week sprint
A venture-backed database company
2-week discovery sprint · converted to a 6-month retainer
~3 hrs
per prototype iteration, down from weeks, after three weeks embedded
A consumer product team
3 weeks embedded · AI-native prototyping
7 engagements, anonymized until each client signs a release. The details stay exact.
What you've already tried
The internal champion.
A senior PM or engineer gets tapped as the AI person. But they have a day job. The old way is easier and less risky. AI stays a side project. This is my only job.
The one-off training.
Everyone learns generic prompting tricks. Nobody goes back to work and knows what to do next. It doesn't stick because it's not connected to your actual processes. I work on your real data, your real sprint work, your real pipeline.
The status quo.
You feel the pressure. You bought the licenses. You keep talking about it. Nothing changes.
All three fail for the same reason. There's no one showing your team what good looks like in the context of your actual business.
What changes
Product teams operate on live intelligence.
Customer support signals, sales conversations, competitive moves, and usage analytics synthesized as fast as the data comes in. Not every six months when someone has time to do a research cycle. Fewer sprints wasted building the wrong thing.
elsewhere_
Midjourney's product team runs one to three user interviews a week through a shared research skill. Interview start to company-wide insight takes 45 minutes.— The Skip
Engineers build systems instead of grinding through tickets.
Routine work gets executed by agents. Engineers focus on architecture, strategy, and the decisions that actually require judgment. Output per engineer increases because the nature of the work changes, not just the speed.
elsewhere_
intercom_2x merged PRs per R&D head in 9 months, defect backlog down 54%amplitude_3x PRs in 6 months, bug reports down 55%salesforce_Effective output up 151%, incidents down 5%replit_2.9x code per engineer, reversions and incidents flatSelf-reported by each company. Four independent teams, output up and defects down in every one.
When I leave, the systems are already running.
I embed with your team and work on your actual processes. The environment is set up. The workflows are built. Your team has done it, not just watched it. The capability is theirs.
Services
Talks, advisory, sprints, builds, and embedded leadership.
Five shapes of engagement, from a single talk to ongoing technical leadership. Each one stands on its own and earns the next. For CEOs facing decisions they can't delegate, a standing weekly advisory session is the usual starting point.
How I work →About
I've spent my career at the intersection of product, engineering, and strategy. Four of the companies I built and led were acquired, by Facebook, GoDaddy, Gerber Life, and Yuga Labs. I know what high performance with these tools looks like firsthand.
If you're a CEO or CPO who wants your team working with AI and can't get traction, I'll show you where to start.
More about me →