Customer Success Manager, Data Intelligence
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). They gave examples but we can use appropriate headings based on content. Must not repeat job title as heading. Must not put Job ID etc. Must include a section only when posting has real specific content. Must not create Pay/Schedule/Benefits sections unless posting actually states them. Pay is present: "Base salary range: $70,000 - $85,000, plus a 10% annual bonus potential." Also benefits mention. So we can have a Pay section (maybe combine Pay and Benefits). They said prefer few substantive sections over many thin ones. Could combine Pay, Benefits & Total Rewards into one section with heading maybe "Pay, Benefits & Total Rewards". That's okay.
We need to remove boilerplate: cookie/navigation/legal/EEO etc. Not present.
We need to preserve all substantive information. Must not invent or summarize away detail. Must not omit details. Must keep all content.
We need to format using for headings, - for any list of duties/requirements/benefits, and
for prose.
We need to identify lists: In "What You’ll Own" there are bullet-like sentences but not explicit bullet list. However we can treat each sentence as a list item? The instruction: Use
- for any list of duties/requirements/benefits. The posting includes bullet-like items but not marked with bullets. We could still wrap each duty in
- if we consider them a list. But we need to decide: Are they a list? The text: "Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer. Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes. Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals. Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules. Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity. Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility."
These are separate sentences describing duties. Could be considered a list. Safer to wrap each sentence in
- within a
. Similarly for "Monthly Customer Operating Rhythm", "Customer Enablement and Scaled Adoption", "Relationship, Health, and Renewal Readiness", "Cross-Functional Partnership", "How We’ll Measure Success" (list of success criteria), "What You’re Great At" (list), "Requirements" (list), maybe "Role Guardrails" (list). We'll need to decide.
We also need to keep prose for sections that are not lists: maybe introductory paragraphs.
We must not repeat the job title as heading. The job title is likely "Customer Success Manager". Not present as heading.
We must not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Let's structure:
Why This Role Matters
... paragraph ...
What You’ll Own
- Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer.
- Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes.
- Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals.
- Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules.
- Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity.
- Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility.
Then maybe a subheading for Monthly Customer Operating Rhythm etc. Could combine under same "What You’ll Own"? But they are separate subsections. Could create separate headings for each: "Monthly Customer Operating Rhythm", "Customer Enablement and Scaled Adoption", "Relationship, Health, and Renewal Readiness", "Cross-Functional Partnership". That would be many sections but each has substantive content. The instruction: prefer a few substantive sections over many thin ones. However these are distinct responsibilities; maybe we can group them under "What You’ll Own" as a list with sub-items? But they'd be long. Could keep as separate headings but that may be many sections. However the instruction says prefer a few substantive sections over many thin ones. But we need to include all content. Could combine all responsibilities into one big list under "What You’ll Own". That would lose the subheadings but still preserve all content. The subheadings are not required; we can embed the content as list items. That would be fewer sections. Let's do that: Under "What You’ll Own", we list all duties as list items, covering the bullet points from each subsection.
Similarly for "How We’ll Measure Success": list items.
For "What You’re Great At": list items.
For "Requirements": list items (Necessary Qualifications and Competencies, Preferred Qualifications). Could separate necessary vs preferred but could combine.
For "Pay, Benefits & Total Rewards": paragraph.
We also have "Role Guardrails": could be list items under maybe "Role Guardrails" heading. Could be its own section.
We need to decide headings: Use for section headings. We'll have:
- Why This Role Matters
- What You’ll Own
- How We’ll Measure Success
- What You’re Great At
- Requirements
- Pay, Benefits & Total Rewards
- Role Guardrails
That's 7 sections. Might be okay.
Now we need to extract the exact text for each.
Let's copy sections from posting.
**Why This Role Matters** paragraph:
"Kinective Data Intelligence brings together data from core banking systems, lending platforms, digital banking, contact centers, marketing systems, cards, and other business applications. It then helps financial institutions visualize and activate that data through reporting, dashboards, workflows, predictive analytics, and role-specific business use cases. The platform only creates value when customers use it consistently to make better decisions and take action. We are seeking a Customer Success Manager who can help execute and continuously improve that adoption and value-realization motion. You will help customers move from implementation to sustained usage. You will establish success measures, lead monthly progress and prioritization meetings, coordinate customer priorities with Professional Services capacity, and help customer teams build the habits and capabilities required to realize value from Data Intelligence. For a customer that owns only Data Intelligence, you will serve as the primary Client Success Manager. For a customer that owns multiple Kinective products, you will serve as the Data Intelligence overlay, partnering with the primary CSM who owns the broader relationship and overall account coordination. This role is best suited for someone who has driven adoption of a complex data, analytics, business intelligence, workflow, or SaaS platform. Banking experience is valuable, but the ability to change customer behavior and demonstrate measurable value is more important."
We'll put that in
.
**What You’ll Own** includes multiple subsections; we will combine all bullet-like sentences into list items.
Let's extract each sentence:
From "Data Intelligence Adoption and Value Realization":
- Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer.
- Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes.
- Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals.
- Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules.
- Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity.
- Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility.
From "Monthly Customer Operating Rhythm":
- Lead a monthly customer meeting that reviews progress from the prior month, confirms adoption and delivery status, identifies risks and decisions, and aligns on priorities for the next month.
- Convert monthly discussions into a clear action plan with owners, dates, dependencies, and customer commitments.
- Coordinate with the Project Manager and Professional Services team to confirm that proposed priorities fit within purchased or approved PS capacity.
- Surface remaining-hours, out-of-scope, sequencing, change-control, or delivery-capacity risks before commitments are made to the customer.
- Keep the monthly cadence forward-looking and action-oriented rather than allowing it to become a status-only meeting.
From "Customer Enablement and Scaled Adoption":
- Hold office hours, webinars, workshops, and role-based enablement sessions that help customers apply Data Intelligence to real business questions and workflows.
- Develop repeatable enablement plays for common personas, use cases, and adoption barriers.
- Help customers establish internal champions, super-users, data owners, and executive sponsors who can sustain adoption between Kinective interactions.
- Use train-the-trainer approaches when customers have limited internal resources or need to scale knowledge across departments.
- Partner with Product, Professional Services, Support, and internal subject-matter experts to improve documentation, training, and customer-facing resources.
From "Relationship, Health, and Renewal Readiness":
- Serve as a trusted post-sale advisor to both technical stakeholders and business executives.
- Maintain an accurate customer health assessment based on adoption, delivery progress, usage signals, engagement, sentiment, unresolved issues, renewal readiness, and expansion signals.
- Identify risk early and lead coordinated recovery plans when customers are not receiving expected value or are not progressing against agreed milestones.
- Own renewal readiness for Data Intelligence-only customers and provide the Data Intelligence perspective for multi-product customers.
- Prepare and lead value reviews, business reviews, and executive conversations that demonstrate progress, outcomes, open decisions, and the next phase of the customer roadmap.
From "Cross-Functional Partnership":
- Partner closely with Data Intelligence Project Managers and Professional Services leads to maintain a shared view of delivery status, adoption priorities, dependencies, remaining hours, and customer commitments.
- Partner with Sales on handoff quality, account planning, renewal readiness, and expansion strategy. Sales owns pricing, commercial negotiation, and close.
- Work with Support and Product to route issues, close communication loops, and distinguish product defects from configuration, training, data, or process gaps.
- Surface qualified expansion opportunities, including additional modules, integrations, workflows, analytics use cases, users, or Professional Services capacity.
- Bring customer insights into internal prioritization without overpromising unapproved scope, hours, pricing, or roadmap commitments.
- Help mature Kinective’s Data Intelligence customer-success playbook, health model, adoption metrics, and value-review standards.
Now "How We’ll Measure Success" section:
Paragraph: "Success Here Is Measured By Sustained Customer Value And Operating Discipline, Not Meeting Volume Alone. You Will Know You Are Winning When"
Then bullet list (actually sentences):
- Assigned customers have documented success criteria, adoption baselines, monthly priorities, owners, and next milestones.
- Customers progress from implementation into recurring usage of purchased capabilities and intended workflows.
- Customers can articulate the business outcomes, decisions, or efficiency gains enabled by Data Intelligence.
- Adoption and value trends improve over time,
- for any list of duties/requirements/benefits, and
for prose. We need to identify lists: In "What You’ll Own" there are bullet-like sentences but not explicit bullet list. However we can treat each sentence as a list item? The instruction: Use
- for any list of duties/requirements/benefits. The posting includes bullet-like items but not marked with bullets. We could still wrap each duty in
- if we consider them a list. But we need to decide: Are they a list? The text: "Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer. Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes. Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals. Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules. Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity. Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility." These are separate sentences describing duties. Could be considered a list. Safer to wrap each sentence in
- within a
- . Similarly for "Monthly Customer Operating Rhythm", "Customer Enablement and Scaled Adoption", "Relationship, Health, and Renewal Readiness", "Cross-Functional Partnership", "How We’ll Measure Success" (list of success criteria), "What You’re Great At" (list), "Requirements" (list), maybe "Role Guardrails" (list). We'll need to decide.
We also need to keep prose for sections that are not lists: maybe introductory paragraphs.
We must not repeat the job title as heading. The job title is likely "Customer Success Manager". Not present as heading.
We must not include Job ID etc.
We must output only HTML fragment, no /, no markdown fences.
Let's structure:
- Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer.
- Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes.
- Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals.
- Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules.
- Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity.
- Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility.
Why This Role Matters
... paragraph ...
What You’ll Own
for section headings. We'll have: - Why This Role Matters - What You’ll Own - How We’ll Measure Success - What You’re Great At - Requirements - Pay, Benefits & Total Rewards - Role Guardrails That's 7 sections. Might be okay. Now we need to extract the exact text for each. Let's copy sections from posting. **Why This Role Matters** paragraph: "Kinective Data Intelligence brings together data from core banking systems, lending platforms, digital banking, contact centers, marketing systems, cards, and other business applications. It then helps financial institutions visualize and activate that data through reporting, dashboards, workflows, predictive analytics, and role-specific business use cases. The platform only creates value when customers use it consistently to make better decisions and take action. We are seeking a Customer Success Manager who can help execute and continuously improve that adoption and value-realization motion. You will help customers move from implementation to sustained usage. You will establish success measures, lead monthly progress and prioritization meetings, coordinate customer priorities with Professional Services capacity, and help customer teams build the habits and capabilities required to realize value from Data Intelligence. For a customer that owns only Data Intelligence, you will serve as the primary Client Success Manager. For a customer that owns multiple Kinective products, you will serve as the Data Intelligence overlay, partnering with the primary CSM who owns the broader relationship and overall account coordination. This role is best suited for someone who has driven adoption of a complex data, analytics, business intelligence, workflow, or SaaS platform. Banking experience is valuable, but the ability to change customer behavior and demonstrate measurable value is more important." We'll put that in
. **What You’ll Own** includes multiple subsections; we will combine all bullet-like sentences into list items. Let's extract each sentence: From "Data Intelligence Adoption and Value Realization": - Build and maintain a measurable adoption and value-realization plan for each assigned Data Intelligence customer. - Translate customer business priorities into target use cases, users, milestones, owners, and measurable outcomes. - Establish adoption baselines and monitor usage, engagement, workflow activity, dashboard utilization, recurring reporting, and other available product signals. - Help customers sequence adoption across Data Intelligence capabilities, including the data lakehouse, Business Intelligence, reporting, dashboards, workflows, predictive analytics, and other applicable modules. - Identify adoption barriers such as unclear ownership, insufficient training, weak executive sponsorship, data-quality concerns, competing priorities, or limited client capacity. - Connect product usage to business outcomes such as growth, operational efficiency, member experience, risk management, profitability, or executive visibility. From "Monthly Customer Operating Rhythm": - Lead a monthly customer meeting that reviews progress from the prior month, confirms adoption and delivery status, identifies risks and decisions, and aligns on priorities for the next month. - Convert monthly discussions into a clear action plan with owners, dates, dependencies, and customer commitments. - Coordinate with the Project Manager and Professional Services team to confirm that proposed priorities fit within purchased or approved PS capacity. - Surface remaining-hours, out-of-scope, sequencing, change-control, or delivery-capacity risks before commitments are made to the customer. - Keep the monthly cadence forward-looking and action-oriented rather than allowing it to become a status-only meeting. From "Customer Enablement and Scaled Adoption": - Hold office hours, webinars, workshops, and role-based enablement sessions that help customers apply Data Intelligence to real business questions and workflows. - Develop repeatable enablement plays for common personas, use cases, and adoption barriers. - Help customers establish internal champions, super-users, data owners, and executive sponsors who can sustain adoption between Kinective interactions. - Use train-the-trainer approaches when customers have limited internal resources or need to scale knowledge across departments. - Partner with Product, Professional Services, Support, and internal subject-matter experts to improve documentation, training, and customer-facing resources. From "Relationship, Health, and Renewal Readiness": - Serve as a trusted post-sale advisor to both technical stakeholders and business executives. - Maintain an accurate customer health assessment based on adoption, delivery progress, usage signals, engagement, sentiment, unresolved issues, renewal readiness, and expansion signals. - Identify risk early and lead coordinated recovery plans when customers are not receiving expected value or are not progressing against agreed milestones. - Own renewal readiness for Data Intelligence-only customers and provide the Data Intelligence perspective for multi-product customers. - Prepare and lead value reviews, business reviews, and executive conversations that demonstrate progress, outcomes, open decisions, and the next phase of the customer roadmap. From "Cross-Functional Partnership": - Partner closely with Data Intelligence Project Managers and Professional Services leads to maintain a shared view of delivery status, adoption priorities, dependencies, remaining hours, and customer commitments. - Partner with Sales on handoff quality, account planning, renewal readiness, and expansion strategy. Sales owns pricing, commercial negotiation, and close. - Work with Support and Product to route issues, close communication loops, and distinguish product defects from configuration, training, data, or process gaps. - Surface qualified expansion opportunities, including additional modules, integrations, workflows, analytics use cases, users, or Professional Services capacity. - Bring customer insights into internal prioritization without overpromising unapproved scope, hours, pricing, or roadmap commitments. - Help mature Kinective’s Data Intelligence customer-success playbook, health model, adoption metrics, and value-review standards. Now "How We’ll Measure Success" section: Paragraph: "Success Here Is Measured By Sustained Customer Value And Operating Discipline, Not Meeting Volume Alone. You Will Know You Are Winning When" Then bullet list (actually sentences): - Assigned customers have documented success criteria, adoption baselines, monthly priorities, owners, and next milestones. - Customers progress from implementation into recurring usage of purchased capabilities and intended workflows. - Customers can articulate the business outcomes, decisions, or efficiency gains enabled by Data Intelligence. - Adoption and value trends improve over time,