Client Partner
for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones.
We need to parse the posting.
Content:
- "A little about us…" paragraph describing company. Could be "About the role"? Actually "About the role" heading is for description of role? Usually "About the role" is a short overview. The posting includes "Overview" then description of role. So we can put that under
About the role
with paragraph(s). Also there is "Overview" heading but we can treat as part of About the role.
- Responsibilities: there is a list under "Responsibilities | What you will own..." with bullet points (though not bullet characters but sentences separated by periods). We need to extract each duty as list items.
- Required Skills & Experiences: list of required items. Could be under Requirements or Qualifications or Skills. The instruction: use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content.
We have:
- About the role: we have overview paragraph.
- Responsibilities: we have list.
- Requirements: maybe "Required Skills & Experiences" includes required experience, etc. Could be under Requirements.
- Qualifications: maybe not separate; we could combine with Requirements.
- Skills: maybe we could extract skills from required list (consultative, discovery-led approach, etc.) but we already have required list. Could put under Skills.
- Benefits: we have benefits paragraph.
- Pay: we have salary range and OTE.
- Schedule: not mentioned (no schedule info). So we should NOT include Schedule section.
We must not include sections with filler/placeholder text. So we include only those with real content.
We need to avoid duplicating lines. Also remove boilerplate like "Our Company Values", "Knit Privacy Policy here.", "CCPA disclosure here.", duplicate salary range lines, etc.
We need to preserve all substantive information: company description, overview, responsibilities, required skills/experiences, benefits, salary range.
We must not invent or summarize away detail. Must preserve all substantive information; but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the information, not omit details. However we can format as list items; we must keep the meaning. We can keep the sentences as is, maybe split into list items.
We need to ensure we don't lose any detail. Let's extract.
Company description paragraph:
"A little about us… Knit is the AI-native consumer research platform helping brands automate and accelerate primary research. With our Researcher-Driven AI, we’ve condensed the entire quant + qual research process from weeks into days (sometimes hours!) for 50+ enterprise brands — including Amazon, T-Mobile, Mars, NASCAR, and more. We’re on a mission to scale and democratize world-class research. From survey generation to stakeholder-ready reports, our platform is redefining how insights teams operate — and we need your help to push the limits of what’s possible."
That's substantive.
Overview / role description:
"Overview The Client Partner will play a critical role in driving Knit’s growth by managing and expanding our largest enterprise partnerships while also building relationships with new high-potential accounts. You’ll own a portfolio of 10–20 enterprise accounts—some existing, some new—with the mandate to retain, grow, and strategically expand them across business units and markets. Acting as the commercial quarterback, you’ll lead renewals, upsells, and cross-sells while prospecting into new divisions and organizations to grow your book of business. You’ll join a team that’s building something category-defining—and you’ll help shape how some of the world’s most respected brands uncover and activate insights through AI-native research. This is a high-impact, consultative sales role that blends strategic relationship management with commercial ownership. You’ll collaborate closely with Customer Success, Research, and Product to ensure clients are realizing value while uncovering new ways Knit can help them succeed."
We can keep as paragraph(s).
Responsibilities list: The bullet points after "Responsibilities | What you will own...":
- Own and grow a portfolio of 10–20 enterprise accounts, including both existing clients and targeted net-new logos.
- Drive renewals and expansion, ensuring every partnership grows in scope, scale, and value year over year.
- Uncover and pursue new opportunities within existing and prospective accounts—identifying new business units, teams, and use cases where Knit’s platform can deliver value
- Act as a strategic advisor to senior Insights, Analytics, and Marketing leaders, helping them expand how they use Knit’s AI-native platform across teams and business challenges.
- Develop and execute account plans that identify whitespace, prioritize client goals, map key stakeholders, and drive consistent revenue growth.
- Lead commercial negotiations—owning renewals, upsells, and cross-sells in collaboration with Sales Leadership
- Collaborate deeply with Customer Success, Research, and Product to ensure clients realize full value from Knit today - and evolve alongside our platform as new capabilities emerge
- Represent Knit externally at conferences, client summits, and industry events, strengthening brand visibility and deepening client relationships.
- Maintain high standards for pipeline integrity, forecasting accuracy, and documentation across every stage of the renewal and expansion process.
We need to keep each as - .
Required Skills & Experiences list:
- 7+ years of experience in enterprise account management, client partnerships, or strategic sales in the research and insights industry
- Experience autonomously owning and leading customer relationships and entering new buying centers within existing Enterprise accounts
- We are specifically looking for individuals who have supported clients at Fortune 500 companies, with Insights titles (including but not limited to Chief Research/Insights Officers, VP, director-level and above)
- Experience selling $100K+ contracts to clients at Fortune 500 companies and managing $1M+ Enterprise relationships
- Proven success managing Fortune 500 clients with multi-business-unit complexity.
- Consistent track record of hitting or exceeding growth, renewal, or NRR targets.
- Experience leading commercial negotiations for six- and seven-figure contracts.
- Consultative, discovery-led approach with exceptional listening and problem-solving skills.
- Highly organized, with disciplined pipeline and account management.
- Strong collaboration skills—adept at leading cross-functional teams across Customer Success, Research, and Product.
- A builder’s mindset—comfortable navigating ambiguity and energized by shaping processes as we scale.
Nice to Haves (optional): we could include under Skills or maybe separate but we have limited headings. Could put under Skills as additional nice-to-haves. But we must not create sections with filler. Nice to Haves is substantive; we could include under Skills as a list.
Benefits: paragraph:
"If US: Upon joining the Knit team, you will receive a competitive salary + commission plan if applicable to role, Equity Options, Healthcare (medical, dental, and vision), and Additional Coverage, a company laptop and one-time, onboarding Technology Stipend, a 401(k) with company match, flexible time-off, hybrid working, and more!"
We need to keep that.
Pay: Salary range and OTE:
"In accordance with New York pay transparency requirements, the salary range for this role is $150,000 - $170,000 with an OTE (Base + Commission) of $300,000 - $340,000 annually. Final compensation will be determined based on the candidate’s level, experience, and qualifications upon joining Knit."
There is duplicate later: "In accordance with New York pay transparency requirements, the salary range for this role is listed below. Final compensation will be determined based on the candidate’s level, experience, and qualifications upon joining Knit. Salary Range: $150,000 USD - $170,000 USD"
We need to preserve all substantive information but avoid duplication. We should include the salary range and OTE once. The duplicate lines are redundant; we should not repeat same info. So we include one statement: salary range $150,000 - $170,000, OTE $300,000 - $340,000.
We should not include the repeated "In accordance with New York pay transparency requirements" twice; we can keep one mention.
Schedule: none, so omit.
Now we need to decide which headings to use.
We have:
- About the role: includes company description and overview? Could split: About the role could be overview of role; About the company could be separate but we don't have a heading for About the company. The instruction only lists those headings; we can put company description under About the role as well (makes sense). Or we could put under About the role the overview paragraph, and maybe add a separate
for company description before that. But we need to keep all substantive info; we can include both paragraphs under About the role.
- Responsibilities: as list.
- Requirements: could contain the required skills & experiences list.
- Skills: could contain nice-to-haves and maybe some skill attributes like consultative, discovery-led approach etc. But those are already in required list. To avoid duplication, we could put required list under Requirements, and nice-to-haves under Skills.
- Benefits: as paragraph.
- Pay: as paragraph with salary range and OTE.
We must not create sections with filler. Ensure each heading has real content.
Now produce HTML fragment:
About the role
... company description ...
... overview ...
Responsibilities
- ...
...
Requirements
- ...
...
Skills
- Nice-to-have: Background in SaaS, AI, or technology-enabled services that drive strategic business decisions.
- Nice-to-have: Experience managing global or multi-market client portfolios.
- Nice-to-have: History of success in high-growth or startup environments where playbooks are still being written.
But we need to preserve the exact phrasing? The nice-to-haves list: "Background in SaaS, AI, or technology-enabled services that drive strategic business decisions." "Experience managing global or multi-market client portfolios." "History of success in high-growth or startup environments where playbooks are still being written."
We should keep them as list items.
Alternatively we could put them under Requirements as well, but we already have required list. It's okay to have Skills section for nice-to-haves.
Now Benefits:
Benefits
If US: Upon joining the Knit team, you will receive a competitive salary + commission plan if applicable to role, Equity Options, Healthcare (medical, dental, and vision), and Additional Coverage, a company laptop and one-time, onboarding Technology Stipend, a 401(k) with company match, flexible time-off, hybrid working, and more!
Pay:
Pay
In accordance with New York pay transparency requirements, the salary range for this role is $150,000 - $170,000 with an OTE (Base + Commission) of $300,000 - $340,000 annually. Final compensation will be determined based on the
for prose. Do NOT repeat job title as heading. Do NOT put Job ID/requisition numbers as headings. Remove boilerplate, navigation, legal, EEO, equal-opportunity, scam-warning, duplicated lines, application instructions. Include a section ONLY when posting has real, specific content for it — never emit heading followed by filler/placeholder text. Prefer few substantive sections over many thin ones. We need to parse the posting. Content: - "A little about us…" paragraph describing company. Could be "About the role"? Actually "About the role" heading is for description of role? Usually "About the role" is a short overview. The posting includes "Overview" then description of role. So we can put that under
About the role
with paragraph(s). Also there is "Overview" heading but we can treat as part of About the role. - Responsibilities: there is a list under "Responsibilities | What you will own..." with bullet points (though not bullet characters but sentences separated by periods). We need to extract each duty as list items. - Required Skills & Experiences: list of required items. Could be under Requirements or Qualifications or Skills. The instruction: use headings for sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to decide which sections to include based on content. We have: - About the role: we have overview paragraph. - Responsibilities: we have list. - Requirements: maybe "Required Skills & Experiences" includes required experience, etc. Could be under Requirements. - Qualifications: maybe not separate; we could combine with Requirements. - Skills: maybe we could extract skills from required list (consultative, discovery-led approach, etc.) but we already have required list. Could put under Skills. - Benefits: we have benefits paragraph. - Pay: we have salary range and OTE. - Schedule: not mentioned (no schedule info). So we should NOT include Schedule section. We must not include sections with filler/placeholder text. So we include only those with real content. We need to avoid duplicating lines. Also remove boilerplate like "Our Company Values", "Knit Privacy Policy here.", "CCPA disclosure here.", duplicate salary range lines, etc. We need to preserve all substantive information: company description, overview, responsibilities, required skills/experiences, benefits, salary range. We must not invent or summarize away detail. Must preserve all substantive information; but we can rephrase? The instruction: "Preserve ALL substantive information; do NOT invent or summarize away detail." Means we should keep the information, not omit details. However we can format as list items; we must keep the meaning. We can keep the sentences as is, maybe split into list items. We need to ensure we don't lose any detail. Let's extract. Company description paragraph: "A little about us… Knit is the AI-native consumer research platform helping brands automate and accelerate primary research. With our Researcher-Driven AI, we’ve condensed the entire quant + qual research process from weeks into days (sometimes hours!) for 50+ enterprise brands — including Amazon, T-Mobile, Mars, NASCAR, and more. We’re on a mission to scale and democratize world-class research. From survey generation to stakeholder-ready reports, our platform is redefining how insights teams operate — and we need your help to push the limits of what’s possible." That's substantive. Overview / role description: "Overview The Client Partner will play a critical role in driving Knit’s growth by managing and expanding our largest enterprise partnerships while also building relationships with new high-potential accounts. You’ll own a portfolio of 10–20 enterprise accounts—some existing, some new—with the mandate to retain, grow, and strategically expand them across business units and markets. Acting as the commercial quarterback, you’ll lead renewals, upsells, and cross-sells while prospecting into new divisions and organizations to grow your book of business. You’ll join a team that’s building something category-defining—and you’ll help shape how some of the world’s most respected brands uncover and activate insights through AI-native research. This is a high-impact, consultative sales role that blends strategic relationship management with commercial ownership. You’ll collaborate closely with Customer Success, Research, and Product to ensure clients are realizing value while uncovering new ways Knit can help them succeed." We can keep as paragraph(s). Responsibilities list: The bullet points after "Responsibilities | What you will own...": - Own and grow a portfolio of 10–20 enterprise accounts, including both existing clients and targeted net-new logos. - Drive renewals and expansion, ensuring every partnership grows in scope, scale, and value year over year. - Uncover and pursue new opportunities within existing and prospective accounts—identifying new business units, teams, and use cases where Knit’s platform can deliver value - Act as a strategic advisor to senior Insights, Analytics, and Marketing leaders, helping them expand how they use Knit’s AI-native platform across teams and business challenges. - Develop and execute account plans that identify whitespace, prioritize client goals, map key stakeholders, and drive consistent revenue growth. - Lead commercial negotiations—owning renewals, upsells, and cross-sells in collaboration with Sales Leadership - Collaborate deeply with Customer Success, Research, and Product to ensure clients realize full value from Knit today - and evolve alongside our platform as new capabilities emerge - Represent Knit externally at conferences, client summits, and industry events, strengthening brand visibility and deepening client relationships. - Maintain high standards for pipeline integrity, forecasting accuracy, and documentation across every stage of the renewal and expansion process. We need to keep each asfor company description before that. But we need to keep all substantive info; we can include both paragraphs under About the role. - Responsibilities: as list. - Requirements: could contain the required skills & experiences list. - Skills: could contain nice-to-haves and maybe some skill attributes like consultative, discovery-led approach etc. But those are already in required list. To avoid duplication, we could put required list under Requirements, and nice-to-haves under Skills. - Benefits: as paragraph. - Pay: as paragraph with salary range and OTE. We must not create sections with filler. Ensure each heading has real content. Now produce HTML fragment:
About the role
... company description ...
... overview ...
Responsibilities
- ... ...
Requirements
- ... ...
Skills
- Nice-to-have: Background in SaaS, AI, or technology-enabled services that drive strategic business decisions.
- Nice-to-have: Experience managing global or multi-market client portfolios.
- Nice-to-have: History of success in high-growth or startup environments where playbooks are still being written.
Benefits
If US: Upon joining the Knit team, you will receive a competitive salary + commission plan if applicable to role, Equity Options, Healthcare (medical, dental, and vision), and Additional Coverage, a company laptop and one-time, onboarding Technology Stipend, a 401(k) with company match, flexible time-off, hybrid working, and more!
Pay:Pay
In accordance with New York pay transparency requirements, the salary range for this role is $150,000 - $170,000 with an OTE (Base + Commission) of $300,000 - $340,000 annually. Final compensation will be determined based on the