Sales Development and Executive Outreach Specialist

We need to output HTML fragment with sections: About the role? Actually the posting includes "About PlanITROI" intro, then role description. We need headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections where there is real specific content. We need to parse content: There's a description about PlanITROI (company overview) maybe "About the role"? Actually "About PlanITROI" is company description, not role. The role description includes responsibilities, qualifications, etc. There's also "Why Join PlanITROI?" which could be Benefits? It mentions benefits package: health insurance, 401(k) with company match, paid time off, and more. So we can create Benefits section with those specifics. Pay: Not mentioned. Schedule: It says remote role, based in USA in Eastern Standard Time. That's schedule info? It's location/timezone. Could be considered Schedule? Might be considered "Schedule" but not explicit hours. Probably we can include Schedule section with "Remote role, based in the USA, Eastern Standard Time." That's specific. We need to avoid boilerplate: EEO, Equal Opportunity Employer, etc. Remove that. We need to preserve all substantive info. Let's extract: Company overview: Could be placed under "About the role"? Actually "About the role" heading is for role description, not company. But we could put company overview under "About the role"? Might be okay. However instructions: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we can have About the role section containing role summary and maybe company overview? Usually About the role includes brief description of role. We'll include role summary: "Sales Development and Executive Outreach Specialist ... work directly with CEO and CSO ...". That's from posting. Responsibilities: list from "Key Responsibilities". We'll put each bullet as

. Requirements: maybe combine Qualifications? The posting has "Qualifications" section. We'll treat that as Requirements? Actually they have Qualifications heading. We'll output Requirements section with those bullet points? But we also have a separate "Qualifications" heading allowed. We could output both Requirements and Qualifications if content distinct. However the posting only has one Qualifications section. Could map that to Requirements. But we also have Skills maybe from qualifications? Might be redundant. Better to follow headings: Use Qualifications section for the qualifications list. Use Responsibilities for responsibilities. Use Benefits for benefits. Use Schedule for remote/EST. Possibly Skills not needed if covered. We must not repeat job title as heading. So no heading for "Sales Development and Executive Outreach Specialist". Good. We need to include About the role section: maybe a paragraph summarizing role. Let's craft:

About the role

Sales Development and Executive Outreach Specialist works directly with the CEO and Chief Strategy Officer to drive outbound sales activity, activate executive relationships, follow up on qualified leads, and ensure new business appointments are scheduled weekly. The role uses Apollo.io, Salesforce, LinkedIn, email, phone, and AI-enabled tools to research prospects, engage B2B contacts, manage outreach, document activity, and complete follow‑up. This is a remote position based in the USA, operating in Eastern Standard Time.

Then Responsibilities:

Responsibilities

• Work directly with the CEO and CSO to organize, prioritize, and execute outbound sales outreach.
• Research companies, decision‑makers, executives, referral sources, and relationship paths.
• Keep all active prospects, B2B contacts and accounts, and follow‑up items organized and current.
• Use Apollo.io to identify, enrich, organize, and prioritize leads.
• Use Salesforce to track every call, email, LinkedIn touch, task, note, meeting outcome, and follow‑up.
• Send polished, personalized outbound emails.
• Make professional calls to schedule appointments and advance conversations.
• Use LinkedIn for prospect research, direct outreach, engagement, and thought leadership support.
• Follow up on PlanITROI’s executive network, warm relationships, referrals, inbound leads, and lead generation team leads.
• Coordinate meeting scheduling, confirmations, reminders, and next‑step communication.
• Take meeting notes when needed and follow through until next steps are completed.
• Prepare prospect briefs, account research, call summaries, and meeting notes.
• Track opportunities through appointment setting, post‑meeting follow‑up, proposal support, contract progress, and handoff to Client Success.
• Partner with sales, marketing, lead generation, and Client Success to keep opportunities moving.
• Maintain confidentiality and professionalism with executive relationships and strategic opportunities.

Qualifications:

Qualifications

• 5+ years of experience in outbound sales support, appointment setting, lead follow‑up, business development, sales research, executive outreach, B2B contact management, or executive sales assistance.
• Strong experience with email, phone, LinkedIn, and CRM‑based follow‑up.
• Experience using Apollo.io or similar prospecting tools for research, contact identification, lead enrichment, and list building.
• Strong Salesforce proficiency, including activity logging, task management, account updates, contact updates, notes, and follow‑up tracking.
• Excellent written and verbal communication skills with the ability to communicate professionally with U.S. and global executives.
• Strong business writing skills with the ability to write clear, concise, personalized emails.
• Professional phone presence and confidence calling executives, decision‑makers, referral partners, and prospects.
• Strong research skills and ability to quickly understand companies, contacts, industries, and business opportunities.
• Expert experience using LinkedIn for sales outreach, research, direct communication, and relationship development.
• Strong organization, attention to detail, ownership, and follow‑through.
• Experience working directly with executives, founders, business owners, or senior sales leaders preferred.
• Proficiency in Microsoft Office and related productivity tools.
• Familiarity with AI tools for research, writing, prospecting, and workflow efficiency preferred.

Benefits:

Benefits

• Health insurance
• 401(k) with company match
• Paid time off
• More (comprehensive benefits package)

Schedule:

Schedule

Remote role based in the USA, operating in Eastern Standard Time.

We should not include Pay section because not mentioned. We must not include any boilerplate like EEO, Equal Opportunity Employer, etc. We removed that. Check for any duplicated lines: we have not. Make sure we preserve all substantive info: we included company overview? We included some in About the role but not the full PlanITROI description. The posting had a long "About PlanITROI" paragraph before role. That is substantive info about company. Should we preserve it? The instruction: Preserve ALL substantive information; do NOT invent or summarize away detail. So we need to include that company overview somewhere. Where? Could be in About the role section as a preamble. But we already used About the role for role summary. Could add a separate section? Not allowed headings beyond those listed. Could we put company overview in About the role as well? That would mix role and company info but still substantive. However we might lose some detail if we summarize. We need to preserve all detail, not summarize away. So we need to include the full company overview text verbatim (or close) without summarizing. Let's extract the company overview: "About PlanITROI For more than 25 years, PlanITROI has helped organizations maximize the value of their retired technology through secure IT Asset Disposition (ITAD), lifecycle management, reverse logistics, refurbishment, repair, redeployment, and re-marketing services. Every device we recover creates financial value for our clients while extending the life of technology and helping provide affordable devices to individuals, schools, nonprofits, and businesses around the world. PlanITROI is a recognized leader in sustainable IT lifecycle solutions, helping enterprise organizations improve financial performance, strengthen security, and advance ESG initiatives through our circular economy model. Today, we are building something even greater! The world’s greatest Repair, Refurbishment, and Lifecycle Services organization! At the center of that vision is our state-of-the-art Center of Excellence in Youngsville, North Carolina. A high-performance operation where technology, automation, engineering, compliance, and people come together to transform retired and underutilized IT devices into enterprise-grade, re-certified technology solutions. But PlanITROI is more than an ITAD company. We are redefining how the world’s largest channel organizations, OEMs, GSIs, MSPs, VARs, and enterprises think about lifecycle value, sustainability, circularity, risk reduction, and technology access. Our work strengthens ESG outcomes, recovers value, reduces operational and data-security risk, and creates new revenue opportunities across the IT lifecycle. As we continue scaling globally, we are investing heavily in strategic partnerships, alliance ecosystems, executive engagement, and category leadership. We are seeking visionary, execution-driven leaders who want to help shape the future of lifecycle services, circular technology, and enterprise channel transformation. If you are energized by building strategic partnerships, influencing enterprise ecosystems, creating category-defining messaging, and driving growth through world-class channel and alliance marketing, we invite you to help build that future with us." That's a lot. We need to include it. Where? Could be a separate section but not in allowed headings. However we could treat it as part of "About the role" but that would be mixing. The instruction: Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It doesn't forbid other headings, but says use those for those sections. It says "include a section ONLY when the posting has real, specific content for it". It doesn't say we cannot have other headings, but likely they expect only those headings. However we need to preserve all substantive info; we could put the company overview in a

before any headings, as introductory paragraph. That's allowed: we can have prose

not under a heading. The instruction: Use

for prose. So we can put the company overview as a

before the headings. That would preserve all detail without summarizing. Good. Thus output: first a

containing the company overview text exactly (maybe preserve line breaks? We'll just make a single paragraph). Then

About the role

with role summary. Then responsibilities, qualifications, benefits, schedule. Check that we didn't miss any substantive info: The "What Success Looks Like" section also contains substantive info about metrics. Should we preserve that? It's part of the posting. It describes success metrics: 5-10 qualified new business appointments scheduled every week, etc. That is substantive. We need to include it somewhere. Could be part of About the role or Responsibilities? It's not a responsibility but success metrics. Could be its own section? Not in allowed headings. Could be included under About the role as additional prose. Or we could add a

About the role

and include both role summary and success metrics. That would preserve. Also there is "Why Join PlanITROI?" section which includes motivational text and benefits mention. We already captured benefits but also there is motivational prose: "You will work directly with professional direct and very accountable CEO and Chief Strategy Officer on business development that matters. While your friends, family and significant others have a job that pays the bills, you will be helping PlanITROI create new relationships, expand its sales pipeline, grow strategic accounts