Customer Success Manager
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It says include a section ONLY when the posting has real, specific content for it. So we can include "About The Role" (they have that heading). Also "What You'll Do" corresponds to Responsibilities. "Qualifications" is present. Also maybe "Who We Are" could be considered "About the company" but not in list; but we could include as a section maybe not required. The instruction says prefer a few substantive sections over many thin ones. We could include About the role, Responsibilities, Qualifications. Possibly also "Who We Are" as a brief intro but not required. The instruction: "Do NOT repeat the job title as a heading (the page already shows it)". No job title given. So fine.
We need to preserve all substantive information; do not invent or summarize away detail. So we need to include the content from "Who We Are", "About The Role", "What You'll Do", "Qualifications". Must not include boilerplate like cookie/navigation/legal/EEO etc. There's none.
We need to use - for any list of duties/requirements/benefits. The responsibilities are paragraphs with bullet-like sentences but not explicit list. We could convert each sentence into
- under a
. However the instruction: "Use - for any list of duties/requirements/benefits". If the posting does not already have list formatting, we need to decide whether to treat as list. The responsibilities section contains multiple distinct duties; we could format as
- . That seems appropriate. Similarly qualifications could be list.
We need to keep prose in
. So we could have an introductory paragraph for each section then a list.
We must not add sections like Benefits, Pay, Schedule if not present.
Let's extract content.
Who We Are paragraph: "TrueComp partners with over 1,000 public sector agencies to modernize workforce planning, compensation, and benefits analysis. Its intuitive platform and expert consulting empower HR and finance leaders with transparency, efficiency, and equity to make smarter decisions in recruitment, retention, and budgeting. TrueComp provides instant and actionable insights to help government organizations attract top talent, optimize labor strategies, and achieve long-term fiscal sustainability. Dedicated to simplifying workforce challenges, TrueComp’s solutions enable data-driven decisions that improve organizational performance and drive meaningful outcomes. TrueComp was recognized among the Top 100 Government Services companies on the 2024 Inc. 5000."
That's substantive; we could put as a
maybe under a heading "About TrueComp" but not required. Since instruction only mentions certain headings, but we can still include other headings? It 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 those are typical. Safer to stick to those. However "Who We Are" could be considered "About the role"? No. Might be better to omit it? But we must preserve ALL substantive information. If we omit the Who We Are paragraph, we lose info. So we need to include it somewhere. Could we include it as a
before the first heading without a heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't require every piece to be under a heading. So we can have a leading
for Who We Are, then headings for About the role, Responsibilities, Qualifications.
Thus structure:
Who We Are content...
About the role
... (the About The Role paragraph)
Responsibilities
- ...
...
Qualifications
- ...
...
We need to ensure we don't repeat job title as heading (none). No Job ID.
Now extract About The Role paragraph: It starts after "About The Role". The text:
"The Customer Success Manager owns a book of 50-75 public agency accounts from the point a customer has produced real work in the platform through renewal. They are accountable for retention and adoption across that book. Our customers are HR directors, finance directors, and the analysts who support them. They use TrueComp to price union proposals, build salary schedules, and defend numbers in front of elected officials. Success in this role depends on being credible in those conversations, not just responsive to them. Roughly 15-20 accounts are named accounts managed on a set cadence. The remainder are covered through scheduled check-ins and usage-based triggers. Every account renews annually and the Customer Success Manager owns that conversation start to finish. This role reports to the Chief Operations Officer and works closely with sales, support, and product."
We'll put that as a .
Now Responsibilities: "What You'll Do" section includes multiple paragraphs. We'll break into list items.
Let's list each bullet:
- Retention and Renewal Own the renewal conversation for every account in your book, from early positioning through signed agreement.
- Run a renewal calendar that starts 120 days out, not 30. In public sector, the paperwork takes longer than the decision.
- Negotiate pricing and terms within your approved authority, and bring anything outside that band to the COO with a recommendation.
- Manage the mechanics — purchase orders, fiscal year timing, contract amendments, and re-bid requirements where they apply.
- Forecast renewals accurately and identify risk early enough to change the outcome.
- Maintain an account health view you can defend in a forecast review.
- Customer Relationships Build working relationships with HR and finance leadership at each agency, not just your day-to-day contact.
- Understand each customer's operating calendar — budget adoption, bargaining cycles, council meetings — and plan engagement around it.
- Run a consistent cadence with named accounts covering usage, upcoming budget and negotiation cycles, and open issues.
- Own escalations end to end, pulling in support, product, or executive help when the situation calls for it.
- Identify and qualify expansion opportunities across additional modules, added agencies, and consulting engagements, and hand them to sales with the context needed to run them.
- Collaboration and Product Input Route customer feedback and feature requests into the roadmap process with enough context and evidence for product and engineering to act.
- Work alongside the Onboarding Specialist from kickoff forward so the transition to your ownership is a handoff, not a reintroduction.
- Share patterns you see across your book with the broader team — recurring friction, competitive pressure, emerging use cases.
- Process and Tools Track account activity, renewal forecasts, and escalations in Salesforce and keep records current.
- Contribute to building the customer success playbook.
- We are a 30-person company and you will help define process, not just follow it.
We need to ensure we keep the content exactly; some sentences have em dashes etc. We'll keep them.
Now Qualifications: list items.
Paragraph after "Qualifications": It's a block of text with multiple sentences. We'll split into list items.
Let's extract:
- Direct experience inside or alongside public sector HR or finance. That may be working at an agency, or working with agency HR and finance teams in a vendor, consulting, or advisory capacity.
- Working knowledge of compensation benchmarking, labor costing, or actuarial analysis. You do not need to be an actuary. You do need to hold your own in a conversation with a compensation analyst.
- Direct ownership of renewal outcomes in a prior role, including pricing conversations and negotiation.
- Working knowledge of public sector procurement — purchase orders, fiscal year cycles, contract amendments, and when a renewal becomes a competitive re-bid.
- 3-5 years managing customer relationships with direct retention and renewal accountability.
- SaaS experience preferred, not required.
- Demonstrated ability to manage a book of this size independently, prioritizing across accounts without close supervision.
- Written communication clear and concise enough that an HR director will actually read it.
- Preferred: Salesforce experience, prior work at a company under 100 employees, data literacy strong enough to read a usage report and know what it means.
We need to keep the "Preferred:" line as part of list item maybe.
Now we need to ensure we don't include any boilerplate like EEO etc. There's none.
Now produce HTML.
We'll start with
for Who We Are.
Make sure to escape any HTML special characters? The text includes em dashes, apostrophes, etc. They are fine as plain text.
We'll output:
TrueComp partners with over 1,000 public sector agencies to modernize workforce planning, compensation, and benefits analysis. Its intuitive platform and expert consulting empower HR and finance leaders with transparency, efficiency, and equity to make smarter decisions in recruitment, retention, and budgeting. TrueComp provides instant and actionable insights to help government organizations attract top talent, optimize labor strategies, and achieve long-term fiscal sustainability. Dedicated to simplifying workforce challenges, TrueComp’s solutions enable data-driven decisions that improve organizational performance and drive meaningful outcomes. TrueComp was recognized among the Top 100 Government Services companies on the 2024 Inc. 5000.
About the role
The Customer Success Manager owns a book of 50-75 public agency accounts from the point a customer has produced real work in the platform through renewal. They are accountable for retention and adoption across that book. Our customers are HR directors, finance directors, and the analysts who support them. They use TrueComp to price union proposals, build salary schedules, and defend numbers in front of elected officials. Success in this role depends on being credible in those conversations, not just responsive to them. Roughly 15-20 accounts are named accounts managed on a set cadence. The remainder are covered through scheduled check-ins and usage-based triggers. Every account renews annually and the Customer Success Manager owns that conversation start to finish. This role reports to the Chief Operations Officer and works closely with sales, support, and product.
Responsibilities
- Retention and Renewal Own the renewal conversation for every account in your book, from early positioning through signed agreement.
- Run a renewal calendar that starts 120 days out, not 30. In public sector, the paperwork takes longer than the decision.
- Negotiate pricing and terms within your approved authority, and bring anything outside that band to the COO with a recommendation.
- Manage the mechanics — purchase orders, fiscal year timing, contract amendments, and re-bid requirements where they apply.
- Forecast renewals accurately and identify risk early enough to change the outcome.
- Maintain an account health view you can defend in a forecast review.
- Customer Relationships Build working relationships with HR and finance leadership at each agency, not just your day-to-day contact.
- Understand each customer's operating calendar — budget adoption, bargaining cycles, council meetings — and plan engagement around it.
- Run a consistent cadence with named accounts covering usage, upcoming budget and negotiation cycles, and open issues.
- Own escalations end to end, pulling in support, product, or executive help when the situation calls for it.
- Identify and qualify expansion opportunities across additional modules, added agencies, and consulting engagements, and hand them to sales with the context needed to run them.
- Collaboration and Product Input Route customer feedback and feature requests into the roadmap process with enough context and evidence for product and engineering to act
- . However the instruction: "Use
- for any list of duties/requirements/benefits". If the posting does not already have list formatting, we need to decide whether to treat as list. The responsibilities section contains multiple distinct duties; we could format as
- . That seems appropriate. Similarly qualifications could be list.
We need to keep prose in
. So we could have an introductory paragraph for each section then a list. We must not add sections like Benefits, Pay, Schedule if not present. Let's extract content. Who We Are paragraph: "TrueComp partners with over 1,000 public sector agencies to modernize workforce planning, compensation, and benefits analysis. Its intuitive platform and expert consulting empower HR and finance leaders with transparency, efficiency, and equity to make smarter decisions in recruitment, retention, and budgeting. TrueComp provides instant and actionable insights to help government organizations attract top talent, optimize labor strategies, and achieve long-term fiscal sustainability. Dedicated to simplifying workforce challenges, TrueComp’s solutions enable data-driven decisions that improve organizational performance and drive meaningful outcomes. TrueComp was recognized among the Top 100 Government Services companies on the 2024 Inc. 5000." That's substantive; we could put as a
maybe under a heading "About TrueComp" but not required. Since instruction only mentions certain headings, but we can still include other headings? It 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 those are typical. Safer to stick to those. However "Who We Are" could be considered "About the role"? No. Might be better to omit it? But we must preserve ALL substantive information. If we omit the Who We Are paragraph, we lose info. So we need to include it somewhere. Could we include it as a
before the first heading without a heading? The instruction: "Output ONLY the HTML fragment — no /, no markdown code fences." It doesn't require every piece to be under a heading. So we can have a leading
for Who We Are, then headings for About the role, Responsibilities, Qualifications. Thus structure:
Who We Are content...
About the role
... (the About The Role paragraph)
Responsibilities
- ... ...
Qualifications
- ... ...
. Now Responsibilities: "What You'll Do" section includes multiple paragraphs. We'll break into list items. Let's list each bullet: - Retention and Renewal Own the renewal conversation for every account in your book, from early positioning through signed agreement. - Run a renewal calendar that starts 120 days out, not 30. In public sector, the paperwork takes longer than the decision. - Negotiate pricing and terms within your approved authority, and bring anything outside that band to the COO with a recommendation. - Manage the mechanics — purchase orders, fiscal year timing, contract amendments, and re-bid requirements where they apply. - Forecast renewals accurately and identify risk early enough to change the outcome. - Maintain an account health view you can defend in a forecast review. - Customer Relationships Build working relationships with HR and finance leadership at each agency, not just your day-to-day contact. - Understand each customer's operating calendar — budget adoption, bargaining cycles, council meetings — and plan engagement around it. - Run a consistent cadence with named accounts covering usage, upcoming budget and negotiation cycles, and open issues. - Own escalations end to end, pulling in support, product, or executive help when the situation calls for it. - Identify and qualify expansion opportunities across additional modules, added agencies, and consulting engagements, and hand them to sales with the context needed to run them. - Collaboration and Product Input Route customer feedback and feature requests into the roadmap process with enough context and evidence for product and engineering to act. - Work alongside the Onboarding Specialist from kickoff forward so the transition to your ownership is a handoff, not a reintroduction. - Share patterns you see across your book with the broader team — recurring friction, competitive pressure, emerging use cases. - Process and Tools Track account activity, renewal forecasts, and escalations in Salesforce and keep records current. - Contribute to building the customer success playbook. - We are a 30-person company and you will help define process, not just follow it. We need to ensure we keep the content exactly; some sentences have em dashes etc. We'll keep them. Now Qualifications: list items. Paragraph after "Qualifications": It's a block of text with multiple sentences. We'll split into list items. Let's extract: - Direct experience inside or alongside public sector HR or finance. That may be working at an agency, or working with agency HR and finance teams in a vendor, consulting, or advisory capacity. - Working knowledge of compensation benchmarking, labor costing, or actuarial analysis. You do not need to be an actuary. You do need to hold your own in a conversation with a compensation analyst. - Direct ownership of renewal outcomes in a prior role, including pricing conversations and negotiation. - Working knowledge of public sector procurement — purchase orders, fiscal year cycles, contract amendments, and when a renewal becomes a competitive re-bid. - 3-5 years managing customer relationships with direct retention and renewal accountability. - SaaS experience preferred, not required. - Demonstrated ability to manage a book of this size independently, prioritizing across accounts without close supervision. - Written communication clear and concise enough that an HR director will actually read it. - Preferred: Salesforce experience, prior work at a company under 100 employees, data literacy strong enough to read a usage report and know what it means. We need to keep the "Preferred:" line as part of list item maybe. Now we need to ensure we don't include any boilerplate like EEO etc. There's none. Now produce HTML. We'll start with
for Who We Are. Make sure to escape any HTML special characters? The text includes em dashes, apostrophes, etc. They are fine as plain text. We'll output:
TrueComp partners with over 1,000 public sector agencies to modernize workforce planning, compensation, and benefits analysis. Its intuitive platform and expert consulting empower HR and finance leaders with transparency, efficiency, and equity to make smarter decisions in recruitment, retention, and budgeting. TrueComp provides instant and actionable insights to help government organizations attract top talent, optimize labor strategies, and achieve long-term fiscal sustainability. Dedicated to simplifying workforce challenges, TrueComp’s solutions enable data-driven decisions that improve organizational performance and drive meaningful outcomes. TrueComp was recognized among the Top 100 Government Services companies on the 2024 Inc. 5000.
About the role
The Customer Success Manager owns a book of 50-75 public agency accounts from the point a customer has produced real work in the platform through renewal. They are accountable for retention and adoption across that book. Our customers are HR directors, finance directors, and the analysts who support them. They use TrueComp to price union proposals, build salary schedules, and defend numbers in front of elected officials. Success in this role depends on being credible in those conversations, not just responsive to them. Roughly 15-20 accounts are named accounts managed on a set cadence. The remainder are covered through scheduled check-ins and usage-based triggers. Every account renews annually and the Customer Success Manager owns that conversation start to finish. This role reports to the Chief Operations Officer and works closely with sales, support, and product.
Responsibilities
- Retention and Renewal Own the renewal conversation for every account in your book, from early positioning through signed agreement.
- Run a renewal calendar that starts 120 days out, not 30. In public sector, the paperwork takes longer than the decision.
- Negotiate pricing and terms within your approved authority, and bring anything outside that band to the COO with a recommendation.
- Manage the mechanics — purchase orders, fiscal year timing, contract amendments, and re-bid requirements where they apply.
- Forecast renewals accurately and identify risk early enough to change the outcome.
- Maintain an account health view you can defend in a forecast review.
- Customer Relationships Build working relationships with HR and finance leadership at each agency, not just your day-to-day contact.
- Understand each customer's operating calendar — budget adoption, bargaining cycles, council meetings — and plan engagement around it.
- Run a consistent cadence with named accounts covering usage, upcoming budget and negotiation cycles, and open issues.
- Own escalations end to end, pulling in support, product, or executive help when the situation calls for it.
- Identify and qualify expansion opportunities across additional modules, added agencies, and consulting engagements, and hand them to sales with the context needed to run them.
- Collaboration and Product Input Route customer feedback and feature requests into the roadmap process with enough context and evidence for product and engineering to act
- . That seems appropriate. Similarly qualifications could be list.
We need to keep prose in