AI Workflow Adoption Lead

About this role

<p><em>Most AI rollouts fail not because the tools are wrong — but because nobody owns the behavior change.</em></p> <p><em><span data-contrast="none">On-site | Vancouver Office – 675 W Hastings St.</span></em><span data-ccp-props="{"134233117":false,"134233118":false,"335551550":0,"335551620":0,"335559738":240,"335559739":240}">&nbsp;</span></p> <p><span data-ccp-props="{"134233117":false,"134233118":false,"335551550":0,"335551620":0,"335559738":240,"335559739":240}">&nbsp;</span></p> <p><strong>The Problem We're Solving</strong></p> <p>EviSmart's business teams — sales, customer success, finance, product, marketing — have access to powerful AI tools. The gap isn't the technology. It's that adoption is uneven and this role exists to close that gap: map how each function actually works, identify where AI creates real leverage, build the playbooks that make adoption stick, and track usage until it's no longer an experiment.&nbsp;</p> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">Why EviSmart</span></span></strong></p> <ul> <li style="line-height: 2;">300 people. Two hubs: Vancouver HQ and Manila operations.</li> <li style="line-height: 2;">145% year-over-year SaaS growth — the market is responding.</li> <li style="line-height: 2;">28 countries. One platform. The dental industry's Autopilot.</li> <li style="line-height: 2;">An in-house AI model research and development team building proprietary intelligence.</li> </ul> <p>&nbsp;</p> <p><strong>Why This Role, Right Now</strong></p> <p>EviSmart has the tools. What it needs now is someone who can operationalize them across every business function — not by presenting a framework, but by doing the work: shadowing teams, building function-specific prompt libraries, running adoption sprints, and iterating until usage holds. The 2026 roadmap assumes AI is embedded in how the business runs. This role is what makes that true.</p> <p>&nbsp;</p> <p><strong>A Note from the Team&nbsp;</strong></p> <p><em>“This isn't a strategy role. We don't need decks about AI potential — we need someone who will sit with our CS team on Monday, understand how they actually work, and hand them something useful by Friday. If you've driven a real software rollout across multiple functions and you know what it takes to get a skeptical ops lead to actually change how they work, that's the person we're looking for.”</em></p> <p><strong>— Paolo Kalaw, CEO, EviSmart</strong></p> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">What </span><span data-ccp-parastyle="heading 3">You’ll</span><span data-ccp-parastyle="heading 3"> Own</span></span></strong><span data-ccp-props="{"134233117":false,"134233118":false,"134245418":true,"134245529":true,"335551550":0,"335551620":0,"335559738":281,"335559739":281}">&nbsp;</span></p> <ul> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Map</strong> workflows across all business functions — sales, customer success, finance, product, and marketing — to identify where AI creates the highest leverage.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Build</strong> function-specific prompt libraries: how a CS rep uses Cowork differently from a finance analyst or a sales rep.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Create</strong> role-specific onboarding templates, workflow SOPs, and quick-reference guides each team can follow independently.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Run</strong> adoption sprints per function — track weekly active usage, identify resistance, and iterate on playbooks until usage becomes habit.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Navigate</strong> strong, opinionated team leads to earn genuine buy-in — not compliance.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;"><strong>Maintain</strong> a living internal AI workflow wiki covering all business functions, kept current as tools and workflows evolve.</li> </ul> <p>&nbsp;</p> <p><strong>What You'll Get</strong></p> <ul> <li class="whitespace-normal break-words pl-2" style="line-height: 2;">Direct ownership of how AI gets embedded into EviSmart's operations — a rare mandate with visible, measurable impact from week one.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;">Access to Claude, Cursor, and LLM-powered workflows built in-house — you're using the tools you're rolling out.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;">A company where AI is a strategic priority, not a side project — leadership is bought in and the resources follow.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;">Clear growth path: as EviSmart scales, the complexity and scope of this role scales with it.</li> <li class="whitespace-normal break-words pl-2" style="line-height: 2;">Competitive compensation with salary range disclosed at offer.</li> </ul> <p>&nbsp;</p> <p><strong><span data-contrast="none"><span data-ccp-parastyle="heading 3">How We Work</span></span></strong></p> <p>We ship before we’re 100% certain. We write things down because we have two offices and memory is lossy. We debate loudly and move without resentment. We treat the customer’s real problem as more important than an elegant internal process. If you’ve spent time waiting for permission to try something obvious — you’ll notice the difference here immediately. <span data-ccp-props="{"335551550":0,"335551620":0}">&nbsp;</span></p> <p>&nbsp;</p> <p><strong>The Question You're Probably Asking</strong></p> <p><em>"EviSmart already has an AI and automation engineer. How is this role different? The AI &amp; Automation Engineer builds and integrates technical systems. This role changes how people work. The automation engineer builds the infrastr