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.
28 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.
@getosmo Thanks Anuj, the OsmO example is such a perfect illustration of this shift. "As an IC, correct is the scoreboard. As an owner of adoption, behavior change is the scoreboard" should honestly be printed and taped above every engineer's desk before they take their first strategist role.
The "people don't adopt the better thing, they adopt the less scary thing" line hits hard. That's the whole game once you're accountable for outcomes, not just outputs. Spending more time removing reasons-to-say-no than adding capability is exactly where I ended up too, but nobody warned me it would take a year to internalize that mindset shift.
BetterClaw
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 👋
@tina_chhabra Thanks Tina, really appreciate the welcome and yeah, "the technical work is easier now, the non-technical work carries the deals" is honestly the underrated truth of building in AI right now. Everyone celebrates faster shipping, nobody celebrates the internal politics wins that actually make deployments stick.
BetterClaw sounds like it's operating in exactly the same messy space we live in daily. The enterprise deployment challenges never really solve themselves, they just shift shape. Would love to connect and trade notes on how you're navigating adoption inside your customers' orgs, that's where all the interesting problems are 🤝
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.
@thenameisarian Thanks Mustafa, the "credential gap" framing is genuinely one of the sharpest things I've read about this transition. As an IC you had commits, PRs, code review approvals, real signed artifacts. As a strategist your artifact is "the deal you closed" and there's no GitHub for that. Nobody talks about how disorienting that shift feels in the first few months.
Your idea of the "TAM receipt per deal" (customer signature + executive sponsor + compliance reviewer all named) as a portable strategist credential is honestly brilliant. That's a legit format that builds a track record way stronger than LinkedIn ever captures. Would genuinely love to walk through this if you're open to it, feels like the kind of framework that could reshape how AI strategists get evaluated moving forward.