Dev turned AI strategist. Here's what nobody told me before the switch
by•
I have spent years as a developer before moving fully into AI workflow strategy and enterprise deployment work.
The honest thing nobody told me before the switch:
Going from 'I build the thing' to 'I help enterprises actually use the thing' is a completely different skill stack. Less code, way more politics, compliance, change management, and explaining the same architecture three different ways to three different stakeholders.
What surprised me:
The technical work is easier now. The non-technical work is what carries the deals.
For anyone else who made a similar move from IC to strategy, what was the hardest part of the transition that wasn't on your radar going in?
Really hope that anyone can discuss this with me then.
18 views
Replies
Made a version of this jump building OsmO — went from 'ship the feature' to 'get a real person to actually change how they use their phone.' What blindsided me: as an IC, correct is the scoreboard. The moment you own adoption, the scoreboard quietly becomes 'did the human change their behavior?' — and people don't adopt the better thing, they adopt the less scary thing. So I spend way more time removing reasons-to-say-no than adding capability now. Your 'explain the same architecture three ways' line is the other half of it — half the job turns out to be translation: saying one idea in each stakeholder's own words and fears. Nobody warned me how much of it is emotional, not technical.
welcome Nolan! "the technical work is easier now, the non-technical work carries the deals" is such an underrated insight. I see the same thing from the marketing side... the product is never the hard part, it's getting the right people to understand why it matters and navigating the internal politics to get it adopted. we're building BetterClaw in the AI agents space and the enterprise deployment challenges you're describing are exactly the problems we think about every day. would love to connect 👋
the ic to strategist transition has a credential gap nobody warns you about. as an ic you had github commits and code review approvals, real signed artifacts. as a strategist the artifact is the deal you closed and the relationships you built to close it. linkedin captures neither well, but the strategist credential is harder to port because there is no github for sales motion. one tam receipt per deal, with the customer signature, the executive sponsor, the compliance reviewer all named, builds a strategist record that is actually stronger than the engineer one once you set up the format. happy to walk through if useful.