Customer Success Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). But we can use other headings if they match content? The instruction: "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It suggests we should use those headings when appropriate. But we can also use other headings? Probably we should map content to those standard headings where possible. The posting includes "About Spekit" (company description) maybe fits "About the role"? Actually "About the role" is a heading for role description. But we have "The Role". Could map to "About the role". "What You'll Do" -> Responsibilities. "What We're Looking For" -> Requirements/Qualifications/Skills. "Why Spekit" -> Benefits? Actually benefits are listed there: competitive salary, equity, full benefits, generous PTO, culture. Also location info maybe as a short paragraph.
We must not repeat job title as heading. No Job ID. Remove boilerplate like EEO etc. We must preserve all substantive info.
We need to output only HTML fragment, no /, no markdown fences.
We'll create sections:
- About the role
maybe containing description from "The Role" paragraph(s). Could also include location info as a
About the role
maybe containing description from "The Role" paragraph(s). Could also include location info as abefore sections? The location info is not a heading; we can put a
with location and work auth details. -
Responsibilities
with- list from "What You'll Do".
-
Requirements
maybe combine "What We're Looking For" items. Could split into Qualifications and Skills but we can just use Requirements. -Benefits
from "Why Spekit": competitive salary, equity, full benefits (medical, dental, vision), generous PTO, culture, etc. Also mention headquarters Denver, thriving in-office community, fully remote-friendly. We must not create sections with filler like "Pay" or "Schedule" if not present. Pay is mentioned as competitive salary, but we can include under Benefits. No separate Pay section. We must not include boilerplate like equal opportunity employer. Let's extract details. Location paragraph: "Location: This role is fully remote within the United States or hybrid from our Denver, CO office. Candidates must be authorized to work in the U.S. without current or future need for sponsorship. We are not able to sponsor visas for this position. You must be located in and able to work from one of the following states: AZ, CA, CO, FL, GA, IL, LA, MA, MI, NC, NJ, NV, NY, OR, TX, UT, VA, WA, WI." We'll put that as a. About Spekit paragraph: "At Spekit, we’re building a truly context-aware experience where you never have to search for the right answer again. It starts with Sidekick, our execution layer that lives in your browser, Slack, and beyond. Sidekick anticipates a sales rep’s next move, translating complex signals into in-flow coaching, automated workflows, and deal-aware content creation — constantly answering the only question that matters: “Given everything I know about this deal, what should I say, share, or do right now?” But delivering that experience requires more than a chatbot. It requires an authoritative system of truth that governs how a company goes to market. A content platform that keeps information dynamic and accurate as the business evolves, connecting enablement to real revenue outcomes. An intelligence layer humans rely on, and the one other AI systems consume. It requires, Spekit. Recognized as a Visionary in Gartner’s 2025 Magic Quadrant™ for Revenue Enablement Platforms, we’re reimagining how people work and learn in an AI-first world. Come build with us! Backed by: $60M+ from Craft Ventures, Felicis, Foundry Group, and Renegade Partners Trusted by: A 2025 Gartner Visionary powering teams at Southwest Airlines, Justworks, Equifax, and FlorenceHQ." We could put that under About the role? Actually About Spekit is company description; maybe we can put under About the role as a brief intro. Or we could create a separate section "About Spekit" but not in allowed headings. The instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but suggests we should use those. Safer to map company description to About the role? Might be odd but okay. Or we could create a
About Spekit
but that deviates from examples. I'd follow instruction: use those headings only. So we need to fit content under those headings. Thus: -About the role
: include description of Spekit and the role overview (The Role paragraph). Could combine both. -Responsibilities
: list from What You'll Do. -Requirements
: list from What We're Looking For. -Benefits
: from Why Spekit. We'll not include Pay or Schedule sections. Now extract bullet points. Responsibilities (What You'll Do): - Own the post-implementation relationship for a portfolio of accounts — from adoption through renewal, expansion, and advocacy - Drive adoption of Spekit across your customers' revenue teams, helping them embed deal rooms, AI Sidekick, and just-in-time enablement into their daily workflows - Build deep, multi-threaded relationships with champions and economic buyers, including VP and C-level stakeholders in Revenue, Enablement, and Sales Operations - Lead strategic business reviews that connect Spekit's impact to your customers' revenue goals, not just product usage metrics - Act as the voice of the customer inside Spekit — partnering closely with Product, Engineering, Marketing, and Sales to ensure customer feedback shapes what we build and how we go to market - Identify and develop customer advocates for case studies, speaking opportunities, and peer references - Proactively monitor account health using data — surfacing churn risk early and building mitigation plans before things escalate - Manage escalations with urgency, ownership, and transparency: documenting issues, driving cross-functional resolution, and keeping customers informed throughout - Collaborate with Sales to identify and close expansion opportunities in your portfolio - Maintain deep product expertise, continuously learning as Spekit's platform evolves, and helping customers understand how to apply new capabilities to their specific use cases Requirements (What We're Looking For): - 4–8 years of experience in Customer Success, Account Management, or a strategic customer-facing role at a B2B SaaS company - A track record of owning net revenue retention — you can speak to renewal rates, expansion ARR, and churn you've prevented - Proven ability to build relationships at the VP and C-suite level, particularly with Revenue, Enablement, or RevOps leaders - Experience managing a portfolio of mid-market or enterprise accounts with ARR in the $30K–$200K+ range - Comfort operating in a fast-moving startup where the playbook is still being built — you're energized by ambiguity, not paralyzed by it - Strong analytical instincts — you use data to tell a story, identify risk, and make a case for action - Exceptional communication and facilitation skills: you run tight meetings, write clearly, and present with confidence - Familiarity with the sales enablement, revenue intelligence, or digital adoption space is a plus - Experience with Salesforce, Vitally, Gainsight, or similar CS tooling - Experience with AI tools like Claude, ChatGPT, etc - Must be legally authorized to work in the US Note: The last line about work authorization is also in location paragraph; we might duplicate but we can keep it in Requirements. Benefits (Why Spekit): - You'll join a team where CS is treated as a revenue function, not a cost center - Your customers will include some of the most innovative revenue teams in the industry — and they'll actually love the product you're supporting - You'll work directly with the founding team and have real influence over how CS is built and scaled - Competitive salary, equity, full benefits (medical, dental, vision), generous PTO, and a culture that means it - Headquartered in Denver with a thriving in-office community — and fully remote-friendly for the right person We need to preserve the phrase "and a culture that means it" maybe incomplete; but we keep as is. Now location paragraph as abefore sections. We must not include any boilerplate like equal opportunity employer. Now produce HTML:
Location: This role is fully remote within the United States or hybrid from our Denver, CO office. Candidates must be authorized to work in the U.S. without current or future need for sponsorship. We are not able to sponsor visas for this position. You must be located in and able to work from one of the following states: AZ, CA, CO, FL, GA, IL, LA, MA, MI, NC, NJ, NV, NY, OR, TX, UT, VA, WA, WI.
About the role
At Spekit, we’re building a truly context-aware experience where you never have to search for the right answer again. It starts with Sidekick, our execution layer that lives in your browser, Slack, and beyond. Sidekick anticipates a sales rep’s next move, translating complex signals into in-flow coaching, automated workflows, and deal-aware content creation — constantly answering the only question that matters: “Given everything I know about this deal, what should I say, share, or do right now?” But delivering that experience requires more than a chatbot. It requires an authoritative system of truth that governs how a company goes to market. A content platform that keeps information dynamic and accurate as the business evolves, connecting enablement to real revenue outcomes. An intelligence layer humans rely on, and the one other AI systems consume. It requires, Spekit. Recognized as a Visionary in Gartner’s 2025 Magic Quadrant™ for Revenue Enablement Platforms, we’re reimagining how people work and learn in an AI-first world. Come build with us! Backed by: $60M+ from Craft Ventures, Felicis, Foundry Group, and Renegade Partners Trusted by: A 2025 Gartner Visionary powering teams at Southwest Airlines, Justworks, Equifax, and FlorenceHQ.
The Role As a Customer Success Manager at Spekit, you own the outcomes for a portfolio of mid-market and enterprise accounts. You're the person your customers call when they need a thought partner, a strategic advisor, and internal advocate. You're not a support function — you're a revenue driver. You will be responsible for ensuring every customer in your book is actively realizing the value of Spekit, building champions at every level, and turning healthy accounts into expansion and advocacy opportunities. This is a high-impact, high-visibility role on a lean team where your work is directly felt by the business and by the customers you serve. We're looking for someone who brings the same relentless focus on outcomes to their customers that Spekit brings to its users: the right answer, at the right time, every time.
But we might want to keep the role description as part of About the role; we already have a paragraph about Spekit and then a paragraph about the role. That's fine. Now Responsibilities: