Anyone else in a non-dev role accidentally become the AI tooling person for their team?

I’m in corp finance at a midsize company, and I’ve spent the last couple months going deep on Claude Code, Cowork, Claude Desktop, skills, agents, MCPs, 3rd party tools, patterns, context and harness engineering, etc etc.

It’s been genuinely exciting. Haven’t learned this much or seen such opportunity since learning what a pivot table was or how to use power query.

It’s also made me feel like I live in a collapsing ontology markdown sea where every object has 3 names, 5 overlapping use cases, and one doc page that contradicts the other 4. And everything is definitely a graph and subsequently definitely not a graph in a loop.

Speak up other non-dev folks!

Multiple hats - How do you separate builder mode from user mode when you’re the same person doing both?

Agentic capability overlap - skills vs MCPs vs agents vs software? I.e. skills can hold knowledge, execute scripts, MCPs retreive knowledge from elsewhere and execute scripts themselves. Python frameworks seem easily accessible for an all in one department solution. But then you own it. Hell MCPs can be apps now. They can play piano too.

Why does it feel so hard to bridge major agent framework and agents sdk (where all the hype is at) to the claude code or desktop runtime experience? Every concept is applicable within the runtime and on top of it.

When do you put business logic in claude things vs shared traditional workspaces? Any opinions on collab and governing tools and business logic with teammates?

Anyone else confused and disappointed to find that Cowork has nothing to do with helping your coworkers and is just an agent sdk instance with a nice gui to make non dev people feel nice and safe?

Amd to that end, anyone actually deploying team empowering, automation multi-surface Claude Code / Cowork/ Desktop / Excel / PowerPoint / SharePoint, or mostly just building personal productivity tools?

If you’re the only builder on a small team, are you bringing people along or just translating all this back to them yourself?

Also very curious about practical setup:

repo/worktree/projects for non-dev, dev work?

monorepo vs separate repos especially across personas

How much of this ends up being markdown/config vs actual code?

Would love to hear from people doing this for real, especially outside engineering.

And maybe simultaneously would love to hear devs point out any obvious unlocks. Thanks!