Customer Success and Community Manager
or drop it." So we can include a short paragraph about company under About the role? Might be okay. We need sections: About the role (contains description of role, where work happens, etc). Responsibilities (list). Requirements (maybe qualifications). Qualifications (maybe separate). Skills (maybe competencies). Benefits (list). Pay (salary range). Schedule (maybe remote work). The posting includes "Fully remote work within the United States" under What We Offer. That's schedule/location. Also "Medical, Vision, Dental, 401k (US)" benefits. Also "Compensation Base salary range: $95,000 – $110,000". So we have Pay and Benefits and Schedule. We also have "Qualifications Required" and "Preferred" and "COMPETENCIES AND ATTRIBUTES". Those can be split into Requirements (required qualifications) and Skills (preferred/competencies). We'll include Requirements for required qualifications, Skills for preferred/competencies. We must not include sections with filler like "commensurate with experience". Not present. We must preserve all substantive info; not invent or summarize away detail. So we need to include all bullet points etc. We need to use
- for any list of duties/requirements/benefits. Use
for prose. We must not include cookie/navigation/legal/EEO etc. The posting includes "Powered by JazzHR UXElXAZPPY" at end - that's boilerplate; drop. Also "About Soutron Global" maybe not needed as a section but could be part of About the role. We'll include a short paragraph under About the role. Now craft HTML. Structure:
About the role
Soutron Global builds the technology that libraries, archives, and museums run on. Our public library portfolio includes Apollo, the cloud-native integrated library system (ILS) trusted by roughly 1,000 smaller public libraries with approximately 99% logo retention; VERSO, our ILS for mid-size public libraries and consortia; and SHAREit, the resource-sharing and interlibrary loan network that connects libraries across states and regions. Apollo joined Soutron in July 2026. Soutron Global is backed by Bloom Equity Partners.
This is the first dedicated customer success seat on Soutron’s public library base — well over a thousand library locations, most of them small, all of them running software they genuinely like. Logo retention on Apollo is approximately 99%. So this is not a churn job. It is a reach-and-engagement job. The single biggest constraint on this base is not risk; it is that nobody is talking to it. Our customers are librarians in small public libraries, and they are already talking to each other constantly — in Facebook groups, on state library association listservs and forums, in ALA and PLA communities, and at state conferences. Your job is to be present and useful in those places, run programs that reach the whole base at once, and turn that engagement into adoption and module attach. You will own product lines, not an account list. You are the person the Apollo and VERSO communities know by name — the one who runs the release walkthroughs, answers the question in the group thread, hosts the office hours, and knows which library solved the problem the next library is about to ask about. What this role is not: it is not a named-account enterprise CSM seat, and it does not carry renewal administration or renewal forecasting — those sit with Renewals and Sales Operations. If your experience is thirty enterprise logos and a renewal calendar, this will be a frustrating job and we would rather say so now.
Where the work happens
maybe not a standard heading but we could incorporate into About the role? The instructions only list specific headings; but we can include extra headings if they have real content? It says "Usefor section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add others if needed? Safer to stick to those headings. So we should place "Where the work happens" content under About the role or maybe under Responsibilities? It's more about where work happens; could be part of About the role. We'll embed that content in About the role after the initial description. Thus About the role will contain paragraphs covering company description, role description, and where work happens (the channels). We'll keep it as prose. Now Responsibilities: list from "Key Responsibilities" section. We'll extract bullet points. Key Responsibilities includes subheadings: Community ownership and engagement, Product Expertise and Advocacy, Low-touch, high-engagement programs, Adoption and module attach — the commercial outcome, Signal, measurement, and voice of customer. We need to preserve all substantive info; we can flatten into a list of responsibilities. Let's extract each bullet: Community ownership and engagement: - Build and own the Apollo and VERSO customer communities — where they exist today, and where they need to be created - Show up where librarians are already talking, as a credible participant rather than a vendor voice, and become the recognized Soutron face in those venues - Run a standing program calendar: release walkthroughs, office hours, feature clinics, and peer showcases - Surface and connect customers to each other. Peer proof moves this market more than anything we say ourselves - Develop references, case studies, and advocates in partnership with Marketing Product Expertise and Advocacy: - Be the customer-facing owner for your assigned product line or lines — the person the base knows by name and the internal person who knows the base best - Know your product properly: not just what it does, but how a librarian uses it on a Tuesday morning - Own release communication and education for your product line end to end - Represent your line internally to Product, Support, and Engineering with evidence rather than anecdote Low-touch, high-engagement programs: - Design and run one-to-many programs that reach the whole base rather than a managed tier: onboarding tracks, adoption campaigns, in-product messaging, and email sequences - Segment the base by product, size, tenure, and module penetration, and target programs accordingly - Use automation deliberately, so coverage does not scale with headcount - Kill programs that do not work and say why Adoption and module attach — the commercial outcome: - Grow module attach across the base — patron notification, events and room booking, acquisitions, and adjacent modules — against a defined penetration target - Drive adoption of the features that correlate with retention and expansion, and establish which those are - Source and qualify SHAREit resource-sharing and interlibrary loan interest inside the Apollo base, and hand shaped opportunities to Inside Sales to close - Be accountable for net revenue retention on the base as an outcome, delivered through engagement and attach rather than through individual renewal negotiation Signal, measurement, and voice of customer: - Stand up a lightweight, automation-first health and engagement view for the base. Today there is no health scoring, no NPS or CSAT program, and no cohort retention reporting - Launch NPS or CSAT on a cadence with a closed loop, sized for a base this large — not a manual survey program - Flag at-risk accounts to Renewals and Sales with the context they need; you spot the signal, they run the commercial play - Quantify and escalate systemic issues: defect patterns, release quality, documentation gaps, and long-standing feature requests We'll put these as
- . Now Requirements: from "Qualifications Required" section. Qualifications Required: - Three to five years in customer success, community management, customer marketing, or customer education in B2B SaaS, in a scaled or digital model covering hundreds of accounts — not exclusively named-account work - Demonstrated experience building or running a customer community: forums, user groups, social channels, or peer programs. You can point to something you built and how it grew - Experience designing one-to-many programs — webinars, onboarding tracks, email or in-product campaigns — with measured results - Strong written communication and a public voice. Most of your contact with this base will be written, one-to-many, and visible - Comfortable building a view from raw data: CRM exports, product usage, support history - Commercial literacy — you understand that engagement is the mechanism and adoption and attach are the outcome We'll list these. Now Skills: from "Preferred" and "COMPETENCIES AND ATTRIBUTES". We'll combine. Preferred: - MLIS, librarian, or library operations background. Someone who can talk to librarians as a peer has a genuine advantage in this seat, and we will weight it heavily - Direct experience with an ILS or library services platform — Apollo, VERSO, Polaris, Sierra, Symphony, Koha, Atriuum, Alexandria, Destiny, or similar - Experience with public-sector or institutional customers on annual budget cycles - Experience running an annual user conference or a regional user group program - Experience in a business integrating an acquisition, across two products with two inherited service models Competencies and Attributes (list): - Community instinct: naturally builds relationships at scale and enjoys it. Reaches for a program or a group thread before reaching for a calendar invite - Credibility with practitioners: librarians can tell within five minutes whether someone has bothered to learn their world. This person has, or obviously will - Scaled thinking: instinctively asks how a play reaches a thousand libraries, not one - Builds the missing structure: ships a rough first version and improves it rather than waiting for tooling or permission - Commercial ownership: treats attach and retention as numbers they carry, not outcomes that happen to them - Data-driven: can say which signal actually predicts adoption or churn in this base, and why - Public voice: writes and presents well enough to represent the company in a room full of customers, unsupervised - Intellectual honesty: reports the program that failed and the metric that went the wrong way, without being asked - Ambiguity and judgment: effective where processes, metrics, and ownership are not fully defined. Sound decisions on incomplete information We'll list these as Skills. Now Benefits: from "What We Offer": Medical, Vision, Dental, 401k (US). Also "Fully remote work within the United States" maybe schedule. Also "A loyal, high-retention customer base that nobody has systematically engaged yet — genuine greenfield, and you design it" and "Product-line ownership and a public-facing mandate". Those are more like role aspects; but we can include them under Benefits? Might be better to include them under About the role? However they are offered benefits. We'll include them as benefits list. Thus Benefits list: - Medical, Vision, Dental - 401k (US) - Fully remote work within the United States - A loyal, high-retention customer base that nobody has systematically engaged yet — genuine greenfield, and you design it - Product-line ownership and a public-facing mandate Now Pay: Base salary range: $95,000 – $1