Senior Account Executive – Salesforce Alliances & New Business (US)
mindZvue · United States · 1 mo ago
RemoteRemoteSalesFull-time
We need to output HTML fragment with sections: headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Include only sections with real specific content. No filler like "commensurate with experience". We need to parse the posting.
Let's extract content:
- Location: remote/hybrid, but location not a section; we can maybe put in a short paragraph under "About the role"? The instruction: Use
for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We must not repeat job title as heading. No Job ID etc. Include only sections with real specific content. No filler like "commensurate with experience". We need to parse the posting.
Let's extract content:
- Location: remote/hybrid, but location not a section; we can maybe put in a short paragraph under "About the role"? The instruction: Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have sections: About the role, Responsibilities, Requirements, Skills, Benefits. Possibly also "Qualifications" if distinct from Requirements. The posting has "Requirements" with subheadings: What You'll Do (responsibilities), What We're Looking For (experience & track record), Skills & Knowledge, Logistics, Our Ideal Candidate. Also "Benefits" section.
We need to decide mapping.
We can treat "About the role" as a brief intro paragraph summarizing the role (the opening paragraphs). Then "Responsibilities" from "What You'll Do". Then "Requirements" maybe combine experience & track record and logistics? Or separate "Qualifications" for experience & track record, and "Skills" for skills & knowledge. "Benefits" as given.
We must not create Pay or Schedule sections because not specified.
We must not include boilerplate like EEO etc. Not present.
We must preserve all substantive info.
Let's extract substantive paragraphs.
Opening:
"This is a remote position.Location: Plano, TX (Hybrid) or Remote – USA (preference for candidates near Atlanta, Austin, Chicago, Denver, or Washington D.C.) Employment Type: Full-Time Experience: 6+ Years Travel: :2-3 trips per month to Salesforce offices — primarily Atlanta, Chicago, Denver, Austin and Washington D.C. Reports To: Chief Growth Officer / Co-Founder Own the Territory. Win with Salesforce. Deliver More—Together. This is a partner-led, relationship-driven sales role at a Salesforce Summit (Platinum) Partner — not a cold-call quota seat. Your pipeline will be built the way the best Salesforce SI sellers build it: inside Salesforce offices, standing next to Salesforce AEs, co-selling into their accounts and becoming the SI they call first. At mindZvue, you'll own a U.S. territory for one of the ecosystem's fastest-moving AI-native Salesforce consultancies — selling Agentforce, Revenue Cloud, Data Cloud, and GenAI-powered transformation to small and mid-market enterprises who need a partner that actually delivers. If you know how to turn an AE relationship into a referral engine, this is your territory to own."
We need to preserve all that info. We'll put in About the role paragraph.
Now Responsibilities: Under "What You'll Do" there are sub-sections: Salesforce Alliance & Co-Selling (Your Superpower), New Business & Revenue Ownership, Strategy & Cross-Functional Leadership. Each with bullet-like paragraphs. We'll convert each bullet point into - . The text includes sentences; we can break into list items per sentence or per bullet. The posting uses paragraphs; we can treat each paragraph as a list item.
Let's extract:
Salesforce Alliance & Co-Selling (Your Superpower)
- Build and nurture deep relationships with Salesforce Account Executives, RMs, VPs, and Partner Account Managers across your assigned regions.
- Spend real time on the ground in Salesforce offices — Atlanta, Chicago, Denver, Austin and Washington D.C. — with roughly 2-3 travel trips per month to stay top-of-mind with AE teams.
- Drive co-selling motions and joint go-to-market initiatives, including account-mapping sessions, lunch-and-learns, webinars, enablement sessions, joint pitches, and the development of partner-sourced and partner-influenced pipelines.
- Position mindZvue as the go-to Summit Partner for Agentforce, Revenue Cloud, and AI-led Salesforce transformation.
New Business & Revenue Ownership
- Own and deliver against a U.S. revenue and pipeline target, with accurate forecasting and disciplined CRM hygiene.
- Identify and close new business with small to mid-sized enterprises (under 2,000 employees) — the segment where mindZvue wins.
- Run the full cycle: prospecting, discovery, solution positioning, proposal, negotiation, and close.
- Deliver compelling pitches and proposals that translate technical capability into business outcomes and ROI.
Strategy & Cross-Functional Leadership
- Develop and execute a U.S. sales strategy tailored to the Salesforce SI/ISV partnership model.
- Partner with marketing, delivery, and the Salesforce alliance team to align GTM campaigns, case studies, and client success stories.
- Feed market signals back into the business — what's selling, what's stalling, where we should invest next.
- Represent mindZvue at Dreamforce, TrailblazerDX, World Tours, and regional Salesforce events.
Now Requirements/Qualifications: Under "What We're Looking For" there are subheadings: Experience & Track Record, Skills & Knowledge, Logistics, Our Ideal Candidate.
We need to decide sections: Requirements (maybe experience & track record + logistics?), Qualifications (maybe skills & knowledge?), Skills (maybe skills & knowledge). But we have overlapping.
Better: Use sections: Requirements (Experience & Track Record), Qualifications (Skills & Knowledge), Skills (maybe same as Qualifications? but we need distinct). However instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements, Qualifications, Skills each distinct.
We need to map content without duplication.
Let's extract:
Experience & Track Record:
- 7+ years in technology sales, with meaningful time inside the Salesforce ecosystem.
- Proven, referenceable success co-selling with Salesforce AEs — you can name the AEs who would take your call tomorrow.
- Prior experience at a Salesforce SI (System Integrator) or ISV Partner.
- Demonstrated success selling into SMB and mid-market accounts (under 2,000 employees).
- Consistent history of meeting or exceeding quota in a services or consulting sales environment.
Skills & Knowledge:
- Strong working knowledge of Salesforce products — Sales Cloud, Service Cloud, Experience Cloud, and ideally Agentforce, Data Cloud, and Revenue Cloud.
- Fluency in services selling — scoping, SOW shaping, T&M vs. fixed-fee, and margin awareness.
- Excellent relationship management, executive communication, and negotiation skills.
- Disciplined pipeline and forecast management in a CRM.
- Genuine curiosity about AI and Agentforce — our differentiation is AI-native delivery, and you'll need to sell it credibly.
Logistics:
- Based in the U.S. and authorized to work in the U.S.
- Able and willing to travel roughly twice or thrice per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C.
- Candidates based near Atlanta, Chicago, Denver, D.C., Austin or Plano (TX) are strongly preferred — but we will consider exceptional remote candidates anywhere in the U.S.
Our Ideal Candidate:
- A proactive, high-energy seller with a growth mindset and a customer-first approach.
- Thrives in a fast-paced, founder-led environment — comfortable helping build the playbook, not just running it.
- Strong business acumen and a genuine passion for driving measurable client impact.
Now Benefits section: Already present.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment with
headings and
for prose,
- for lists.
We must not repeat job title as heading. Not needed.
We should not include metadata like "Location: ..." as a heading; we can embed location info in About the role paragraph.
Now decide which content goes to which section.
About the role: Intro paragraph(s) up to before "Requirements". Let's craft a paragraph that includes location, employment type, travel, reports to, role description.
Responsibilities: list items from What You'll Do.
Requirements: maybe Experience & Track Record.
Qualifications: maybe Skills & Knowledge.
Skills: maybe Logistics + Our Ideal Candidate? But Skills heading expects skills; maybe we can put Skills & Knowledge there, and Qualifications for Experience & Track Record. But we already used Qualifications for Skills & Knowledge. Let's think.
Better: Use Requirements for Experience & Track Record, Qualifications for Skills & Knowledge, Skills for Logistics + Ideal Candidate (since those are more about logistics and personal traits). However Skills heading might be odd for logistics. But we can still include.
Alternatively, we could combine Logistics and Ideal Candidate under Requirements as additional requirements. But we need to avoid thin sections. Perhaps better to have:
- About the role
- Responsibilities
- Requirements (Experience & Track Record)
- Qualifications (Skills & Knowledge)
- Benefits
And omit Skills section because we already have Qualifications covering skills. But instruction says we can include sections only when posting has real specific content. It's okay to omit Skills.
But we have also Logistics and Ideal Candidate content; we could fold them into Requirements or Qualifications as additional list items. That would preserve all info.
Let's incorporate Logistics and Ideal Candidate into Requirements (or Qualifications). Since Requirements already about experience, we could add extra items under Requirements for logistics and ideal candidate. That would keep sections fewer.
Thus sections: About the role, Responsibilities, Requirements, Benefits.
But we also have Qualifications content (Skills & Knowledge) which is distinct; we could make a Qualifications section.
Thus final sections: About the role, Responsibilities, Requirements (Experience & Track Record + Logistics + Ideal Candidate), Qualifications (Skills & Knowledge), Benefits.
Check if any content left: The "Our Ideal Candidate" is more about personal traits; could go under Requirements as well.
Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present.
Now produce HTML.
We'll need to escape any special characters? Not needed.
Let's craft.
About the role paragraph:
"This is a remote position with a preference for candidates near Atlanta, Austin, Chicago, Denver, or Washington D.C.; hybrid option available in Plano, TX. Employment type is full‑time with approximately 2‑3 trips per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C. Reporting to the Chief Growth Officer / Co‑Founder, you will own a U.S. territory for mindZvue, a Salesforce Summit (Platinum) Partner, selling Agentforce, Revenue Cloud, Data Cloud and GenAI‑powered transformation to small and mid‑market enterprises. The role is partner‑led and relationship‑driven — you will build pipelines by co‑selling alongside Salesforce AEs and become the SI they call first."
Make sure to include all details: location, hybrid, remote, preference, employment type, travel, reports to, role description.
Now Responsibilities: list items as extracted.
Now Requirements: combine Experience & Track Record, Logistics, Our Ideal Candidate.
We'll create list items:
- 7+ years in technology sales, with meaningful time inside the Salesforce ecosystem.
- Proven, referenceable success co‑selling with Salesforce Account Executives — you can name the AEs who would take your call tomorrow.
- Prior experience at a Salesforce SI (System Integrator) or ISV Partner.
- Demonstrated success selling into SMB and mid‑market accounts (under 2,000 employees).
- Consistent history of meeting or exceeding quota in a services or consulting sales environment.
- Based in the U.S. and authorized to work in the U.S.
- Able and willing to travel roughly twice or thrice per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C.
- Candidates based near Atlanta, Chicago, Denver, D.C., Austin or Plano (TX) are strongly preferred — exceptional remote candidates anywhere in the U.S. will be considered.
- A proactive, high‑energy seller with a growth mindset and a customer‑first approach.
- . The text includes sentences; we can break into list items per sentence or per bullet. The posting uses paragraphs; we can treat each paragraph as a list item.
Let's extract:
Salesforce Alliance & Co-Selling (Your Superpower)
- Build and nurture deep relationships with Salesforce Account Executives, RMs, VPs, and Partner Account Managers across your assigned regions.
- Spend real time on the ground in Salesforce offices — Atlanta, Chicago, Denver, Austin and Washington D.C. — with roughly 2-3 travel trips per month to stay top-of-mind with AE teams.
- Drive co-selling motions and joint go-to-market initiatives, including account-mapping sessions, lunch-and-learns, webinars, enablement sessions, joint pitches, and the development of partner-sourced and partner-influenced pipelines.
- Position mindZvue as the go-to Summit Partner for Agentforce, Revenue Cloud, and AI-led Salesforce transformation.
New Business & Revenue Ownership
- Own and deliver against a U.S. revenue and pipeline target, with accurate forecasting and disciplined CRM hygiene.
- Identify and close new business with small to mid-sized enterprises (under 2,000 employees) — the segment where mindZvue wins.
- Run the full cycle: prospecting, discovery, solution positioning, proposal, negotiation, and close.
- Deliver compelling pitches and proposals that translate technical capability into business outcomes and ROI.
Strategy & Cross-Functional Leadership
- Develop and execute a U.S. sales strategy tailored to the Salesforce SI/ISV partnership model.
- Partner with marketing, delivery, and the Salesforce alliance team to align GTM campaigns, case studies, and client success stories.
- Feed market signals back into the business — what's selling, what's stalling, where we should invest next.
- Represent mindZvue at Dreamforce, TrailblazerDX, World Tours, and regional Salesforce events.
Now Requirements/Qualifications: Under "What We're Looking For" there are subheadings: Experience & Track Record, Skills & Knowledge, Logistics, Our Ideal Candidate.
We need to decide sections: Requirements (maybe experience & track record + logistics?), Qualifications (maybe skills & knowledge?), Skills (maybe skills & knowledge). But we have overlapping.
Better: Use sections: Requirements (Experience & Track Record), Qualifications (Skills & Knowledge), Skills (maybe same as Qualifications? but we need distinct). However instruction: Use headings for sections like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we can have Requirements, Qualifications, Skills each distinct.
We need to map content without duplication.
Let's extract:
Experience & Track Record:
- 7+ years in technology sales, with meaningful time inside the Salesforce ecosystem.
- Proven, referenceable success co-selling with Salesforce AEs — you can name the AEs who would take your call tomorrow.
- Prior experience at a Salesforce SI (System Integrator) or ISV Partner.
- Demonstrated success selling into SMB and mid-market accounts (under 2,000 employees).
- Consistent history of meeting or exceeding quota in a services or consulting sales environment.
Skills & Knowledge:
- Strong working knowledge of Salesforce products — Sales Cloud, Service Cloud, Experience Cloud, and ideally Agentforce, Data Cloud, and Revenue Cloud.
- Fluency in services selling — scoping, SOW shaping, T&M vs. fixed-fee, and margin awareness.
- Excellent relationship management, executive communication, and negotiation skills.
- Disciplined pipeline and forecast management in a CRM.
- Genuine curiosity about AI and Agentforce — our differentiation is AI-native delivery, and you'll need to sell it credibly.
Logistics:
- Based in the U.S. and authorized to work in the U.S.
- Able and willing to travel roughly twice or thrice per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C.
- Candidates based near Atlanta, Chicago, Denver, D.C., Austin or Plano (TX) are strongly preferred — but we will consider exceptional remote candidates anywhere in the U.S.
Our Ideal Candidate:
- A proactive, high-energy seller with a growth mindset and a customer-first approach.
- Thrives in a fast-paced, founder-led environment — comfortable helping build the playbook, not just running it.
- Strong business acumen and a genuine passion for driving measurable client impact.
Now Benefits section: Already present.
We need to avoid filler like "commensurate with experience". Not present.
Now we need to output HTML fragment with
headings and
for prose,
- for lists. We must not repeat job title as heading. Not needed. We should not include metadata like "Location: ..." as a heading; we can embed location info in About the role paragraph. Now decide which content goes to which section. About the role: Intro paragraph(s) up to before "Requirements". Let's craft a paragraph that includes location, employment type, travel, reports to, role description. Responsibilities: list items from What You'll Do. Requirements: maybe Experience & Track Record. Qualifications: maybe Skills & Knowledge. Skills: maybe Logistics + Our Ideal Candidate? But Skills heading expects skills; maybe we can put Skills & Knowledge there, and Qualifications for Experience & Track Record. But we already used Qualifications for Skills & Knowledge. Let's think. Better: Use Requirements for Experience & Track Record, Qualifications for Skills & Knowledge, Skills for Logistics + Ideal Candidate (since those are more about logistics and personal traits). However Skills heading might be odd for logistics. But we can still include. Alternatively, we could combine Logistics and Ideal Candidate under Requirements as additional requirements. But we need to avoid thin sections. Perhaps better to have: - About the role - Responsibilities - Requirements (Experience & Track Record) - Qualifications (Skills & Knowledge) - Benefits And omit Skills section because we already have Qualifications covering skills. But instruction says we can include sections only when posting has real specific content. It's okay to omit Skills. But we have also Logistics and Ideal Candidate content; we could fold them into Requirements or Qualifications as additional list items. That would preserve all info. Let's incorporate Logistics and Ideal Candidate into Requirements (or Qualifications). Since Requirements already about experience, we could add extra items under Requirements for logistics and ideal candidate. That would keep sections fewer. Thus sections: About the role, Responsibilities, Requirements, Benefits. But we also have Qualifications content (Skills & Knowledge) which is distinct; we could make a Qualifications section. Thus final sections: About the role, Responsibilities, Requirements (Experience & Track Record + Logistics + Ideal Candidate), Qualifications (Skills & Knowledge), Benefits. Check if any content left: The "Our Ideal Candidate" is more about personal traits; could go under Requirements as well. Now we need to ensure we don't create sections with filler like "commensurate with experience". Not present. Now produce HTML. We'll need to escape any special characters? Not needed. Let's craft. About the role paragraph: "This is a remote position with a preference for candidates near Atlanta, Austin, Chicago, Denver, or Washington D.C.; hybrid option available in Plano, TX. Employment type is full‑time with approximately 2‑3 trips per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C. Reporting to the Chief Growth Officer / Co‑Founder, you will own a U.S. territory for mindZvue, a Salesforce Summit (Platinum) Partner, selling Agentforce, Revenue Cloud, Data Cloud and GenAI‑powered transformation to small and mid‑market enterprises. The role is partner‑led and relationship‑driven — you will build pipelines by co‑selling alongside Salesforce AEs and become the SI they call first." Make sure to include all details: location, hybrid, remote, preference, employment type, travel, reports to, role description. Now Responsibilities: list items as extracted. Now Requirements: combine Experience & Track Record, Logistics, Our Ideal Candidate. We'll create list items: - 7+ years in technology sales, with meaningful time inside the Salesforce ecosystem. - Proven, referenceable success co‑selling with Salesforce Account Executives — you can name the AEs who would take your call tomorrow. - Prior experience at a Salesforce SI (System Integrator) or ISV Partner. - Demonstrated success selling into SMB and mid‑market accounts (under 2,000 employees). - Consistent history of meeting or exceeding quota in a services or consulting sales environment. - Based in the U.S. and authorized to work in the U.S. - Able and willing to travel roughly twice or thrice per month to Salesforce offices in Atlanta, Chicago, Denver, Austin and Washington D.C. - Candidates based near Atlanta, Chicago, Denver, D.C., Austin or Plano (TX) are strongly preferred — exceptional remote candidates anywhere in the U.S. will be considered. - A proactive, high‑energy seller with a growth mindset and a customer‑first approach.