VP, Client Strategy & Success
SMArtX Advisory Solutions · West Palm Beach, FL · 1 mo ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes "About SMArtX Advisory Solutions". Also there is "Opportunity SMArtX Advisory Solutions..." which is intro. We need to use for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes responsibilities, requirements (position requirements), about SMArtX (company description). It does not mention Benefits, Pay, Schedule explicitly. Travel up to 10-20% is mentioned; that could be considered schedule? It's travel, not schedule. No explicit pay or benefits. So we should not create Benefits, Pay, Schedule sections. Also we might have "Qualifications" maybe same as Requirements? The posting has "Position Requirements" and also "Bachelor’s degree required." etc. Could treat that as Requirements. Also there is "Proficiency communicating the value..." etc. That's also requirements. So we can have a Requirements section.
We also have "About SMArtX Advisory Solutions" which could be "About the role"? Actually "About the role" is generic; but we have a company description. Could use "About SMArtX Advisory Solutions" as heading? The instruction says use
for section headings: e.g., About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must include sections only when posting has real specific content. The posting includes responsibilities, requirements (position requirements), about SMArtX (company description). It does not mention Benefits, Pay, Schedule explicitly. Travel up to 10-20% is mentioned; that could be considered schedule? It's travel, not schedule. No explicit pay or benefits. So we should not create Benefits, Pay, Schedule sections. Also we might have "Qualifications" maybe same as Requirements? The posting has "Position Requirements" and also "Bachelor’s degree required." etc. Could treat that as Requirements. Also there is "Proficiency communicating the value..." etc. That's also requirements. So we can have a Requirements section.
We also have "About SMArtX Advisory Solutions" which could be "About the role"? Actually "About the role" is generic; but we have a company description. Could use "About SMArtX Advisory Solutions" as heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict list; we can use those exact headings. Probably we should use those headings if content matches. For company description, maybe "About the role" is not appropriate; but we could use "About SMArtX Advisory Solutions" as a heading? The instruction says use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings. However they say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but not limited to them? It says "use for section headings (e.g. ...)" meaning those are examples of headings we should use. Likely they want us to use those exact headings when applicable. For company description, maybe we can put under "About the role"? But that seems odd. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. The examples are just examples; we can use other headings if appropriate, but they gave a list of typical sections. I'd stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role? Could treat the introductory paragraph as about the role. The first paragraph: "Opportunity SMArtX Advisory Solutions, a rapidly growing financial services technology company based in West Palm Beach, Florida, is seeking a leader with the drive and expertise to advance SMArtX’s strategic relationship management, engagement, and adoption goals across our client channels—including Enterprise and Independent RIA firms, FinTech companies, Asset Managers, TAMPs, and Custodians. The team’s objective is to help customers solve key challenges, scale their businesses, and maximize the value of SMArtX solutions. As part of the Client Success team, you’ll be tech-savvy and knowledgeable about Managed Accounts, TAMPs, UMAs, and the broader FinTech ecosystem. Passion for our platform’s capabilities—and for driving client outcomes—is essential. In this role, you will manage critical relationships and coordinate efforts across SMArtX and third-party partners. The ideal candidate can navigate large, complex organizations, build trusted executive relationships, and drive platform adoption and usage." That's about the role. So we can put that under About the role
.
Then Responsibilities section: list of responsibilities.
Then Requirements section: list of position requirements.
Qualifications? Could be same as Requirements; but we could split: Requirements (experience, skills) and Qualifications (education, certifications). The posting includes Bachelor’s degree required, proficiency communicating value of UMAs etc., 10+ years experience. Those could be qualifications. But we already have requirements list includes many items. To avoid duplication, we could treat the bullet list as Requirements, and then have Qualifications for education and experience? However the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section that includes both. But we have separate headings for Requirements and Qualifications; we could use Requirements for the skill/experience list, and Qualifications for education and years experience. But that may be thin. Better to have one Requirements section that includes all. Then we can omit Qualifications.
Skills: we could extract skills from responsibilities? But we already have skills in requirements. Could create Skills section but might be thin. Better to not create Skills if not distinct.
Thus we will output:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It seems they expect those headings. However they say "use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we can use those headings, but not limited to them? It says "use for section headings (e.g. ...)" meaning those are examples of headings we should use. Likely they want us to use those exact headings when applicable. For company description, maybe we can put under "About the role"? But that seems odd. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. The examples are just examples; we can use other headings if appropriate, but they gave a list of typical sections. I'd stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role? Could treat the introductory paragraph as about the role. The first paragraph: "Opportunity SMArtX Advisory Solutions, a rapidly growing financial services technology company based in West Palm Beach, Florida, is seeking a leader with the drive and expertise to advance SMArtX’s strategic relationship management, engagement, and adoption goals across our client channels—including Enterprise and Independent RIA firms, FinTech companies, Asset Managers, TAMPs, and Custodians. The team’s objective is to help customers solve key challenges, scale their businesses, and maximize the value of SMArtX solutions. As part of the Client Success team, you’ll be tech-savvy and knowledgeable about Managed Accounts, TAMPs, UMAs, and the broader FinTech ecosystem. Passion for our platform’s capabilities—and for driving client outcomes—is essential. In this role, you will manage critical relationships and coordinate efforts across SMArtX and third-party partners. The ideal candidate can navigate large, complex organizations, build trusted executive relationships, and drive platform adoption and usage." That's about the role. So we can put that under About the role
.
Then Responsibilities section: list of responsibilities.
Then Requirements section: list of position requirements.
Qualifications? Could be same as Requirements; but we could split: Requirements (experience, skills) and Qualifications (education, certifications). The posting includes Bachelor’s degree required, proficiency communicating value of UMAs etc., 10+ years experience. Those could be qualifications. But we already have requirements list includes many items. To avoid duplication, we could treat the bullet list as Requirements, and then have Qualifications for education and experience? However the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section that includes both. But we have separate headings for Requirements and Qualifications; we could use Requirements for the skill/experience list, and Qualifications for education and years experience. But that may be thin. Better to have one Requirements section that includes all. Then we can omit Qualifications.
Skills: we could extract skills from responsibilities? But we already have skills in requirements. Could create Skills section but might be thin. Better to not create Skills if not distinct.
Thus we will output:
About the role
for section headings (e.g. ...)" meaning those are examples of headings we should use. Likely they want us to use those exact headings when applicable. For company description, maybe we can put under "About the role"? But that seems odd. However the instruction says "Do NOT repeat the job title as a heading (the page already shows it)". It doesn't forbid other headings. The examples are just examples; we can use other headings if appropriate, but they gave a list of typical sections. I'd stick to those headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We have content for About the role? Could treat the introductory paragraph as about the role. The first paragraph: "Opportunity SMArtX Advisory Solutions, a rapidly growing financial services technology company based in West Palm Beach, Florida, is seeking a leader with the drive and expertise to advance SMArtX’s strategic relationship management, engagement, and adoption goals across our client channels—including Enterprise and Independent RIA firms, FinTech companies, Asset Managers, TAMPs, and Custodians. The team’s objective is to help customers solve key challenges, scale their businesses, and maximize the value of SMArtX solutions. As part of the Client Success team, you’ll be tech-savvy and knowledgeable about Managed Accounts, TAMPs, UMAs, and the broader FinTech ecosystem. Passion for our platform’s capabilities—and for driving client outcomes—is essential. In this role, you will manage critical relationships and coordinate efforts across SMArtX and third-party partners. The ideal candidate can navigate large, complex organizations, build trusted executive relationships, and drive platform adoption and usage." That's about the role. So we can put that under About the role
.
Then Responsibilities section: list of responsibilities.
Then Requirements section: list of position requirements.
Qualifications? Could be same as Requirements; but we could split: Requirements (experience, skills) and Qualifications (education, certifications). The posting includes Bachelor’s degree required, proficiency communicating value of UMAs etc., 10+ years experience. Those could be qualifications. But we already have requirements list includes many items. To avoid duplication, we could treat the bullet list as Requirements, and then have Qualifications for education and experience? However the instruction says prefer a few substantive sections over many thin ones. So maybe combine into one Requirements section that includes both. But we have separate headings for Requirements and Qualifications; we could use Requirements for the skill/experience list, and Qualifications for education and years experience. But that may be thin. Better to have one Requirements section that includes all. Then we can omit Qualifications.
Skills: we could extract skills from responsibilities? But we already have skills in requirements. Could create Skills section but might be thin. Better to not create Skills if not distinct.
Thus we will output:
About the role
... (the intro paragraph)
Responsibilities
- ... each responsibility
Requirements
- ... each requirement
About the role
Opportunity SMArtX Advisory Solutions, a rapidly growing financial services technology company based in West Palm Beach, Florida, is seeking a leader with the drive and expertise to advance SMArtX’s strategic relationship management, engagement, and adoption goals across our client channels—including Enterprise and Independent RIA firms, FinTech companies, Asset Managers, TAMPs, and Custodians. The team’s objective is to help customers solve key challenges, scale their businesses, and maximize the value of SMArtX solutions. As part of the Client Success team, you’ll be tech-savvy and knowledgeable about Managed Accounts, TAMPs, UMAs, and the broader FinTech ecosystem. Passion for our platform’s capabilities—and for driving client outcomes—is essential. In this role, you will manage critical relationships and coordinate efforts across SMArtX and third-party partners. The ideal candidate can navigate large, complex organizations, build trusted executive relationships, and drive platform adoption and usage.
Responsibilities
- Cultivate and maintain strong, long-term relationships across strategic and enterprise accounts.
- Become a subject matter expert on SMArtX’s platform, capabilities, and workflows; serve as a trusted advisor to clients.
- Lead executive-level interactions, presentations, and business reviews with decision-makers and key stakeholders.
- Develop, execute, and maintain strategic account plans, including account mapping, opportunity identification, and long-term partnership strategies.
- Oversee client health metrics, proactively monitoring adoption, engagement, risk indicators, and client satisfaction.
- Define, track, and report KPIs and shared client-success goals aligned with retention, expansion, and platform utilization.
- Guide clients on best practices and optimize their use of SMArtX’s platform and workflows.
- Collaborate cross-functionally on contract terms, business agreements, and renewal/expansion opportunities.
- Educate clients on new and upcoming capabilities, product enhancements, and workflow optimizations.
- Deliver platform and technology demonstrations tailored to client needs and strategic objectives.
- Report on pipeline, account health, and client activity using CRM tools; maintain accurate documentation and executive visibility.
- Partner with Product, Operations, and Service teams to escalate and resolve issues, driving continuous improvement.
- Travel up to 10–20% as needed.
Requirements
- Demonstrated ability to identify, develop, and proactively pursue opportunities within strategic and enterprise client accounts.
- Strong ability to quickly assess client and prospect needs and map them to SMArtX’s value proposition, platform capabilities, and workflow solutions.
- Proven success managing complex client relationships and influencing stakeholders at all levels, including executives and decision-makers.
- Experience developing strategic account plans, including account mapping, goal setting, and multi-year growth strategies.
- Familiarity with client health metrics, KPI tracking, and data-driven approaches to monitoring risk, adoption, engagement, and satisfaction.
- Ability to lead business reviews, present insights, and translate client goals into measurable success outcomes.
- Strong organizational skills and attention to detail, with the ability to manage timelines, cross-functional deliverables, and competing priorities.
- Excellent communication skills—written, verbal, and presentation—with the ability