AI Adoption Manager

WhyHireWrong?•Capon Bridge, WV

6h•Hybrid

About The Position

I'm hiring for this role on behalf of a pan-European SaaS company in the property and facility management space. The Company A cloud-based B2B SaaS platform operating across multiple European markets. Solid product, real customers, growing team. They've decided AI can meaningfully change how their internal teams work, and they need someone to make that happen. This is a new role, created specifically for this purpose. What You'll Do Day to Day You'll start by shadowing teams: sales, marketing, product to understand how they actually work, where time gets lost, and where a well-built automation would change something concrete. Then you build it. On a typical week you might: Identify that the marketing team spends four hours a week adapting one piece of content for different formats, and build a workflow that reduces it to twenty minutes Run a one-hour session teaching a sales rep how to use AI to research accounts before calls, then follow up two weeks later to check if they're actually using it Troubleshoot why a workflow that worked last month is now producing inconsistent outputs and fix the prompt architecture Evaluate a new tool that just dropped and decide whether it's worth introducing or just noise Write a one-page guide so a team can run a workflow you built without calling you every time There's no team under you yet. You work directly with department leads and individual contributors. Expect resistance from some, enthusiasm from others. Your job is to turn skeptics into regular users not by selling them on AI, but by showing them something that saves them time today. The Hard Parts You're the first person in this role. There's no existing playbook, no predecessor to ask, no defined process for how AI adoption gets done here. You'll need to build the structure as you go. Non-technical colleagues won't always know what they need. They'll describe a symptom, not a problem. Part of the job is asking the right questions to get to something buildable. Tools change constantly. What you build in March may need rebuilding by June. You'll need to stay current without chasing every shiny object. Adoption doesn't end when you ship the workflow. If people stop using something three weeks later, that's on you too.

Requirements

A track record of building AI-powered workflows that other people actually used: not prototypes, not demos, production use
Hands-on experience with at least three AI platforms (OpenAI, Claude, Gemini) and at least one automation tool (Make, n8n, Zapier, or equivalent)
The ability to explain how something works to someone who doesn't care how it works: they just want it to solve their problem
Experience working inside a B2B SaaS or tech company (not as an external consultant)
Based in Warsaw, this is hybrid, not remote
Valid work authorization for Poland required. No visa sponsorship available.

Nice To Haves

You've done internal enablement or process improvement before
You actively document and share what you build — publicly or internally
You've held a "first of its kind" role and know how to operate without being told what to prioritize