You're The Already Building.
You're already building. You've shipped at least one thing where AI is doing real work, and the team can feel the difference. The question you're working on now is what the next build is worth doing, and which one will compound.
Here's what's actually happening.
You're in the middle of the curve. The early wins gave you a working sense of what AI can actually do, and the team has stopped asking whether to use it. You're picking what to build next instead of debating whether to build at all. That's a real shift, and you got there yourself.
The honest version of where you are: the strategic question is harder than the technical one now. You can ship the next thing, and you know it. What you can't always see from inside the work is which next thing is going to compound and which is going to be a one-off. The compounding builds change the shape of the operation. The additive ones save time without changing what the operation does.
Where most operators in this archetype get stuck.
The pattern: the next build that pops up is usually the most legible one. Someone on the team flagged it, the use case is obvious, the build is straightforward. So you build it. It works. It saves a few hours a week. Then the same shape repeats with the next legible build. You end up with a portfolio of small useful builds that didn't change the operation in a structural way.
The deeper version is that the legible builds are rarely the compounding ones. The compounding builds touch the seams between functions: the place where sales hands to delivery, where one project closes and the next opens, where the inputs that everything else depends on get assembled. Those builds are harder to spec because they live across teams. They're also the ones that change the shape of the work for everyone downstream.
What I'd build first.
The first build I'd run with you is one of the cross-functional builds you've been circling but haven't picked up because it sits between teams. The build that nobody on the inside owns yet, because the inputs live on one side and the outputs land on another. We map the seams, pick the one with the most leverage, and design the build to live in the middle where the existing systems don't quite reach.
Once that build is live, the next two get easier because the seam pattern is now visible. You'll see where the next compounding build is. The reason a partner helps at this altitude is the second perspective: a system you've been close to for too long is hard to see clearly from inside.
Tell me how it landed.
I drafted a starting message below. Edit anything, then send. I read every one and reply within one business day.