21 Oct
|
MindTickle
|
Canada
Mindtickle is the leading AI-powered revenue enablement platform, helping sales teams learn faster, practice smarter, and perform at their best. We bring together onboarding, training, coaching, content, digital sales rooms, conversation intelligence, and AI role-plays into one platform so revenue teams have everything they need to build winning sellers. Customers and industry analysts have also recognized us. G2 has ranked us the #1 Sales Training & Onboarding platform for 28 consecutive quarters, and Forrester has recognized Mindtickle as a Leader in revenue enablement. Mindtickle was also recognized as AI-Based Sales Solution of the Year by the 2025 AI Breakthrough Awards and has received Stevie Awards for Technology Innovation and Customer Support Excellence. At Mindtickle, we're helping companies create high-performing revenue teams, and we're looking for people who want to help shape what's next. Mindtickle is moving from a market perception as a sales training and enablement platform to recognition as the AI-native revenue enablement platform, powered by ElevateOS. The harder problem is market meaning: whether the market understands why any of this matters, why it matters now, and why Mindtickle is the company that should own it. Mindtickle, powered by ElevateOS helps revenue teams win every moment that matters by turning readiness into live execution. Your job is to make that idea true, specific, provable and repeatable, and then to make it show up identically on the website, in the sales deck, in the demo, in the analyst briefing and in the board narrative. You will work directly with the CEO, the co-founders, Product, Sales, Solution Consulting, Customer Success and Analyst Relations. It is also a hands-on role: you will personally write the positioning,
the message architecture and the persona narratives that the rest of the company draws from. Your measure of success is simple: does the market repeat it? Do customers hear a business argument rather than AI buzzwording? Hold the line on the four questions the market will ask in sequence: why change, why now, why Mindtickle, why not the alternatives. Codify master positioning, the differentiation argument, the claim set and the proof each claim rests on. Every downstream artefact draws from this document rather than from a fresh interpretation. You version it as the platform and the market move, you decide what enters and what is retired, and you are the person who says a piece of language is off-architecture. The bar is that an AE can take it into a live enterprise conversation without translating it first. 4
- Buyer pain as the default language for every capability Deal Guide gives sellers AI recommendations" fails the bar. "Deal Guide helps managers and sellers identify deal risk early by connecting Salesforce context, buyer questions, stakeholder gaps, competitive intelligence and win-loss patterns into one execution guide" passes it. Apply the same test to every claim: does the claim communicate differentiation, or does it prompt a follow-up question? Own why ElevateOS is architecturally different from conversation intelligence tools, content and enablement platforms, LMS incumbents, CRM add-ons and single-purpose AI agents.
The argument is structural: others attach AI to content, calls or CRM records, while Mindtickle connects readiness, seller behaviour, buyer engagement and deal execution in one system. Competitive Intelligence owns the tactical layer of battlecards, landmines and counters. You own the architectural argument those tactics are built on, and you own keeping it honest as competitors ship. Website, sales deck, customer deck, demo narrative, analyst pitch, webinar, executive and board narrative should be recognisably the same story told at different lengths. Drift is the normal state of a rapid-moving company, so treat detection and correction as standing work rather than a project. 7-The language quality bar Decide what the market should remember about Mindtickle and ElevateOS, in a handful of phrases, and then defend that simplicity against the pull toward more slides, more words and more qualifiers. The output you are after is language that a seller, a customer, an analyst and a board member can each repeat accurately from memory. 8-Category framing for analyst relations and launches Feed the category thesis and differentiation into analyst briefing cycles and launch moments, leading with the market problem before the product. Test messages in real conversations rather than in review meetings. Where the field keeps hitting the same objection, that is a positioning defect, and it is yours to fix. Feed differentiation gaps back into roadmap prioritisation so Product hears the market argument, not only the feature request. Head of Product Marketing PMM strategy, priorities, the org-level quality bar You author the category narrative and message architecture, the rest of PMM draws from You supply the
📌 Principal Product Marketing Manager (Canada)
🏢 MindTickle
📍 Canada