Account Manager (SMB)
for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include sections only if posting has real specific content. The posting includes: About the role (the intro paragraphs), Responsibilities (Key Responsibilities etc), Requirements (What We're Looking For Requirements), Qualifications (Bonus Qualifications), Skills maybe not explicit separate; but we can combine? The instruction: Use headings for those categories if content exists. We have content for About the role (intro), Responsibilities (Key Responsibilities), Requirements (What We're Looking For Requirements), Qualifications (Bonus Qualifications). Benefits: there is a Benefits section with details. Pay: there is Compensation section. Schedule: there is Logistics (Hybrid role, travel etc) which includes schedule info; we can treat as Schedule. Also maybe we could include a Skills section? Not explicit separate; but we could put skills under Requirements or Qualifications. Better to follow headings only if we have content.
We must not repeat job title as heading. No Job ID. Remove boilerplate: EQUAL OPPORTUNITY etc. Also remove navigation, cookie, legal, EEO, scam-warning, duplicated lines, application instructions. The posting includes interview process details etc; those are application instructions? Probably we should remove interview process details as they are application instructions. The instruction: remove application instructions. So we should cut out "Interview process: 30-min recruiter screen Up to three 30-45-min video or onsite interviews Offer pending references.Total estimated time: ~3 hours". Also remove "Background and reference checks required as part of onboarding". Also maybe remove "LogisticsHybrid role - report to our Denver office at least 3 days per weekFirst 60 days are 4 days per week for onboarding/trainingExpected travel 4x/year for customer visits or conferences". That's schedule info, we keep as Schedule section.
We need to preserve all substantive information. So we need to include details about role, responsibilities, requirements, qualifications, benefits, pay, schedule.
We must not invent or summarize away detail. So we need to keep specifics like numbers, percentages, etc.
Let's extract content.
About the role: The first paragraphs: "THE OPPORTUNITYJoin a team that’s changing financial servicesZocks is the #1 AI assistant for financial advisors. We help advisors automate their operational work and grow their business. 5,000+ firms use Zocks to turn client conversations into completed work.We're a venture-backed team, building something that changes how financial advisors serve their clients every day. Every role here is an opportunity to shape the product, the company, and the way an entire industry works. We hire sharp, curious, and kind people who want to do meaningful work and build something from the ground up, together."
Then "WHO YOU AREThe SHARC in the roomAt Zocks, we hire for SHARC - five qualities that define how our best people work and win together.S - SharpYou move fast without cutting corners. Quick decisions, thoughtful execution - you know when to act independently and when to loop in leadership.H - HungryYou're a self-starter who celebrates teammates as loudly as your own wins. Humble hustle is your default mode.A - AdaptableStartup life means things shift fast. You lean into change, pivot gracefully, and genuinely enjoy figuring out what's next.R - ResilientBuilding something new isn't always smooth. You bounce back stronger, see obstacles as puzzles, and never lose sight of the bigger picture.C - CuriousYou ask the questions others miss. You explore for fun, not just for work - and it shows in the quality of your thinking."
That could be part of About the role or maybe a separate section like "Who you are". But we only have headings list; we could put that under About the role as prose.
Then "What You’ll DoOur Denver team is growing! The Account Manager is responsible for owning the full post-sale lifecycle for a set of customers from the moment they sign through their renewal. This role blends onboarding ownership with long-term account management. You will guide customers through setup, launch, early adoption, and ongoing success, ensuring they achieve fast time-to-value and remain successful and retained customers.You will run structured onboarding for the first 60 days, then continue as the primary relationship manager responsible for adoption, sentiment, value realization, renewal readiness, and churn prevention. You will identify risks early, build multi-threaded relationships, run health reviews, and execute a consistent renewal playbook. This is a hands-on role for someone who loves helping customers win, shaping process, and driving measurable retention outcomes."
That could be part of About the role or Responsibilities. But we have a separate Responsibilities heading; we can put the detailed responsibilities under that.
Key Responsibilities section includes bullet points: Adoption and Value Realization, Churn Prevention and Account Health, Renewal Management (120 days leading up to renewal), Cross-Functional Alignment, Operational Excellence. Each with sub-bullets.
We need to use - for any list of duties/requirements/benefits. So we will create
with - for each responsibility heading? Actually each heading is a section; we could make
for each responsibility category? But instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings. Within those sections we can use - for lists.
Thus under
Responsibilities
we will have a with each responsibility as - containing the description (maybe with further
for subpoints?). But we can just put the description as text inside - . If we need to preserve sub-bullets, we could nest
. That's okay.
Similarly for Requirements: list of requirements.
Qualifications: bonus qualifications.
Benefits: list of benefits.
Pay: compensation details.
Schedule: logistics details.
We must not include sections with filler like "commensurate with experience". We have actual content.
Now we need to strip out boilerplate: EQUAL OPPORTUNITY paragraph, also maybe "We may use AI tools..." etc. Remove.
Also remove "Interview process..." etc.
Also remove "Background and reference checks required as part of onboarding". That's part of logistics? It's a requirement but we can keep maybe under Requirements? It's a procedural step; but it's not a substantive requirement for candidate; it's part of onboarding. Might be considered boilerplate; but it's not exactly equal opportunity. Safer to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Background check is part of onboarding, not application instruction. Might keep but could be considered procedural. I'd keep it under Requirements maybe as a bullet? But it's not a skill. I'd rather omit it as it's not substantive about candidate qualifications. However it's part of the posting; but instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is background check substantive? It's a condition of employment; could be considered substantive. But it's also typical boilerplate. I'd lean to keep it under Requirements as a bullet: "Background and reference checks required as part of onboarding". However it's not a qualification; but we can still list under Requirements.
Similarly "Expected travel 4x/year for customer visits or conferences" is schedule.
Now let's craft HTML.
We'll start with About the role
then with the combined intro paragraphs (including SHARC). We'll need to ensure we don't duplicate lines. We'll combine into coherent prose.
Let's extract the About the role text:
"The OPPORTUNITYJoin a team that’s changing financial servicesZocks is the #1 AI assistant for financial advisors. We help advisors automate their operational work and grow their business. 5,000+ firms use Zocks to turn client conversations into completed work.We're a venture-backed team, building something that changes how financial advisors serve their clients every day. Every role here is an opportunity to shape the product, the company, and the way an entire industry works. We hire sharp, curious, and kind people who want to do meaningful work and build something from the ground up, together."
Then WHO YOU ARE section: "The SHARC in the roomAt Zocks, we hire for SHARC - five qualities that define how our best people work and win together.S - SharpYou move fast without cutting corners. Quick decisions, thoughtful execution - you know when to act independently and when to loop in leadership.H - HungryYou're a self-starter who celebrates teammates as loudly as your own wins. Humble hustle is your default mode.A - AdaptableStartup life means things shift fast. You lean into change, pivot gracefully, and genuinely enjoy figuring out what's next.R - ResilientBuilding something new isn't always smooth. You bounce back stronger, see obstacles as puzzles, and never lose sight of the bigger picture.C - CuriousYou ask the questions others miss. You explore for fun, not just for work - and it shows in the quality of your thinking."
Then "What You’ll DoOur Denver team is growing! The Account Manager is responsible for owning the full post-sale lifecycle for a set of customers from the moment they sign through their renewal. This role blends onboarding ownership with long-term account management. You will guide customers through setup, launch, early adoption, and ongoing success, ensuring they achieve fast time-to-value and remain successful and retained customers.You will run structured onboarding for the first 60 days, then continue as the primary relationship manager responsible for adoption, sentiment, value realization, renewal readiness, and churn prevention. You will identify risks early, build multi-threaded relationships, run health reviews, and execute a consistent renewal playbook. This is a hands-on role for someone who loves helping customers win, shaping process, and driving measurable retention outcomes."
We could keep that as part of About the role or Responsibilities. Since we have a Responsibilities section, maybe we put the "What You’ll Do" under Responsibilities. But the "What You’ll Do" is more of a summary; the detailed responsibilities follow. We could put the summary under About the role and then detailed under Responsibilities. That seems fine.
Thus About the role paragraph will include the opportunity description and SHARC qualities. We'll not include the "What You’ll Do" there; we will put that under Responsibilities as a summary bullet maybe.
Now Responsibilities: we need to include the summary plus the detailed bullet points.
Let's list responsibilities as per posting:
- Adoption and Value Realization
* Drive user activation and usage across key product features.
* Monitor customer engagement signals including meeting volume, utilization, integration completion, and workflow setup.
* Run scheduled check-ins to reinforce value, highlight wins, and review progress.
* Build repeatable playbooks for increasing adoption and correcting early usage gaps.
* Partner with Product and RevOps to share insights on customer needs and feature impact.
- Churn Prevention and Account Health
* Own Gross ARR Retention and renewal outcomes for your book of business.
* Maintain clear visibility into account health using dashboards, health scores, and engagement metrics.
* Identify churn risks early and execute save plays including sentiment resets, retraining, and workflow redesign.
* Document risks and escalate where necessary with clear recommended actions.
* Ensure ongoing alignment with customer goals and continuously reinforce ROI.
- Renewal Management (120 days leading up to renewal)
* Own renewal preparation, forecasting accuracy, and timely execution.
* Run structured renewal processes including usage reviews, performance summaries, and value recap meetings.
* Confirm contract terms, seat counts, and pricing ahead of renewal cycles.
* Manage renewal negotiations directly with customers and ensure renewal approval happens on time.
* Maintain renewal documentation in Salesforce with clean, complete data.
- Cross-Functional Alignment
* Partner with Sales to ensure a smooth handoff at contract signature and clarity on success outcomes.
* Work with Product
- with
- for each responsibility heading? Actually each heading is a section; we could make
for each responsibility category? But instruction says use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So only those top-level headings. Within those sections we can use
- for lists.
Thus under
Responsibilities
we will have a- with each responsibility as
- containing the description (maybe with further
- for subpoints?). But we can just put the description as text inside
- . If we need to preserve sub-bullets, we could nest
- . That's okay.
Similarly for Requirements: list of requirements.
Qualifications: bonus qualifications.
Benefits: list of benefits.
Pay: compensation details.
Schedule: logistics details.
We must not include sections with filler like "commensurate with experience". We have actual content.
Now we need to strip out boilerplate: EQUAL OPPORTUNITY paragraph, also maybe "We may use AI tools..." etc. Remove.
Also remove "Interview process..." etc.
Also remove "Background and reference checks required as part of onboarding". That's part of logistics? It's a requirement but we can keep maybe under Requirements? It's a procedural step; but it's not a substantive requirement for candidate; it's part of onboarding. Might be considered boilerplate; but it's not exactly equal opportunity. Safer to keep? The instruction: remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. Background check is part of onboarding, not application instruction. Might keep but could be considered procedural. I'd keep it under Requirements maybe as a bullet? But it's not a skill. I'd rather omit it as it's not substantive about candidate qualifications. However it's part of the posting; but instruction says preserve ALL substantive information; do NOT invent or summarize away detail. Is background check substantive? It's a condition of employment; could be considered substantive. But it's also typical boilerplate. I'd lean to keep it under Requirements as a bullet: "Background and reference checks required as part of onboarding". However it's not a qualification; but we can still list under Requirements.
Similarly "Expected travel 4x/year for customer visits or conferences" is schedule.
Now let's craft HTML.
We'll start with
About the role
thenwith the combined intro paragraphs (including SHARC). We'll need to ensure we don't duplicate lines. We'll combine into coherent prose. Let's extract the About the role text: "The OPPORTUNITYJoin a team that’s changing financial servicesZocks is the #1 AI assistant for financial advisors. We help advisors automate their operational work and grow their business. 5,000+ firms use Zocks to turn client conversations into completed work.We're a venture-backed team, building something that changes how financial advisors serve their clients every day. Every role here is an opportunity to shape the product, the company, and the way an entire industry works. We hire sharp, curious, and kind people who want to do meaningful work and build something from the ground up, together." Then WHO YOU ARE section: "The SHARC in the roomAt Zocks, we hire for SHARC - five qualities that define how our best people work and win together.S - SharpYou move fast without cutting corners. Quick decisions, thoughtful execution - you know when to act independently and when to loop in leadership.H - HungryYou're a self-starter who celebrates teammates as loudly as your own wins. Humble hustle is your default mode.A - AdaptableStartup life means things shift fast. You lean into change, pivot gracefully, and genuinely enjoy figuring out what's next.R - ResilientBuilding something new isn't always smooth. You bounce back stronger, see obstacles as puzzles, and never lose sight of the bigger picture.C - CuriousYou ask the questions others miss. You explore for fun, not just for work - and it shows in the quality of your thinking." Then "What You’ll DoOur Denver team is growing! The Account Manager is responsible for owning the full post-sale lifecycle for a set of customers from the moment they sign through their renewal. This role blends onboarding ownership with long-term account management. You will guide customers through setup, launch, early adoption, and ongoing success, ensuring they achieve fast time-to-value and remain successful and retained customers.You will run structured onboarding for the first 60 days, then continue as the primary relationship manager responsible for adoption, sentiment, value realization, renewal readiness, and churn prevention. You will identify risks early, build multi-threaded relationships, run health reviews, and execute a consistent renewal playbook. This is a hands-on role for someone who loves helping customers win, shaping process, and driving measurable retention outcomes." We could keep that as part of About the role or Responsibilities. Since we have a Responsibilities section, maybe we put the "What You’ll Do" under Responsibilities. But the "What You’ll Do" is more of a summary; the detailed responsibilities follow. We could put the summary under About the role and then detailed under Responsibilities. That seems fine. Thus About the role paragraph will include the opportunity description and SHARC qualities. We'll not include the "What You’ll Do" there; we will put that under Responsibilities as a summary bullet maybe. Now Responsibilities: we need to include the summary plus the detailed bullet points. Let's list responsibilities as per posting: - Adoption and Value Realization * Drive user activation and usage across key product features. * Monitor customer engagement signals including meeting volume, utilization, integration completion, and workflow setup. * Run scheduled check-ins to reinforce value, highlight wins, and review progress. * Build repeatable playbooks for increasing adoption and correcting early usage gaps. * Partner with Product and RevOps to share insights on customer needs and feature impact. - Churn Prevention and Account Health * Own Gross ARR Retention and renewal outcomes for your book of business. * Maintain clear visibility into account health using dashboards, health scores, and engagement metrics. * Identify churn risks early and execute save plays including sentiment resets, retraining, and workflow redesign. * Document risks and escalate where necessary with clear recommended actions. * Ensure ongoing alignment with customer goals and continuously reinforce ROI. - Renewal Management (120 days leading up to renewal) * Own renewal preparation, forecasting accuracy, and timely execution. * Run structured renewal processes including usage reviews, performance summaries, and value recap meetings. * Confirm contract terms, seat counts, and pricing ahead of renewal cycles. * Manage renewal negotiations directly with customers and ensure renewal approval happens on time. * Maintain renewal documentation in Salesforce with clean, complete data. - Cross-Functional Alignment * Partner with Sales to ensure a smooth handoff at contract signature and clarity on success outcomes. * Work with Product
- . If we need to preserve sub-bullets, we could nest
- containing the description (maybe with further
- for lists.
Thus under