Inside Sales Support Specialist

We need to output HTML fragment with sections only if real content. Use

for headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to map content. From posting: There's a description: "West Coast Based | Reports to Head of Sales | Regional Scope Build. Lead. Transform. If you thrive on responsiveness, accountability, and disciplined execution, this role is for you. Quickparts is hiring an Inside Sales Support Specialist to own the RFQ-to-order sales cycle for a portfolio of small-to-mid-sized accounts and to support day-to-day activity on Key Accounts. Reporting to the Head of Sales, with daily direction and prioritization from the Regional Sales Director, you will drive pipeline velocity through disciplined follow-up, convert quotes to orders, and grow wallet share within our existing customer base across CNC machining, injection molding, additive manufacturing, and sheet metal fabrication programs." That's about the role. Could be "About the role" heading. Then "Why This Role Matters" bullet list: could be part of responsibilities? Might be under Responsibilities. Then sections: "What You'll Do" with subheadings: Pipeline & Quote Management, Customer Growth & Relationship Management, Strategic Account Support, CRM & Process Discipline. Those are responsibilities. Then "What We're Looking For": requirements and preferred experience. Then "Key Performance Indicators": maybe not a standard heading; could be under Qualifications? But we only have set headings. Could treat as "Requirements" maybe? Actually KPIs are metrics for performance; could be part of "Qualifications"? But we should not invent sections unless content. We could include a section "Qualifications" for KPIs? Might be better to put KPIs under "Requirements" as they are expectations. However we need to preserve all substantive info; we can include them under a heading like "Qualifications" or "Key Performance Indicators" but only allowed headings are the listed ones. The instruction: "use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., meaning those are examples; we can use those headings. It doesn't forbid other headings? It says use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Likely they expect us to use those headings only. So we must map content to those headings. Thus we need sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include if we have real content. We have: - About the role: intro paragraph. - Responsibilities: the "What You'll Do" bullet points and subpoints. - Requirements: "What We're Looking For" includes 3+ years experience, proven track record, strong skills, proficiency with CRM and MS Office, self-motivated etc. Also preferred experience. - Qualifications: maybe the preferred experience? Could treat as Qualifications. - Skills: maybe list of skills: customer relationship, communication, organizational, CRM proficiency, MS Office, self-motivated, results oriented, etc. Could also include familiarity with HubSpot, RFQ management, manufacturing environment. - Benefits: "Why You'll Love It Here" includes: Direct collaboration with Sales leadership, Real ownership, High-growth dynamic org, Fast-paced high-volume, Strong culture of accountability and collaboration, Flexible work environment, Competitive compensation, 401K Employer match, Excellent health and wellness benefits, Generous Paid Time Off. - Pay: Not explicitly stated; only "Competitive compensation" but no numbers. The instruction: never create Pay/Schedule/Benefits sections unless posting actually states them. "Competitive compensation" is vague but still states compensation exists. However they said never create Pay section unless posting actually states them. Does "Competitive compensation" count as stating? It's a statement but not specific. The instruction: "never create Pay/Schedule/Benefits sections unless the posting actually states them." It says "states them" meaning actual mention of pay/schedule/benefits. Benefits we have explicit list, so we can include Benefits. Pay: "Competitive compensation" is a statement about pay but not specific; could be considered stating that compensation is competitive. Might be okay to include Pay section with that statement? However they said "never create Pay/Schedule/Benefits sections unless the posting actually states them." It does state "Competitive compensation". So we could include Pay with that phrase. But we also have Benefits separate. Might be okay. - Schedule: Not mentioned; no schedule info. So omit Schedule. We must not include boilerplate like EEO, application instructions, etc. Remove the behavioral assessment link and related text. Also remove "About Quickparts" description? That's company overview; might be considered boilerplate? It's substantive about company but not required? The instruction: preserve ALL substantive information; do NOT invent or summarize away detail. So we should keep company overview? It's not a standard heading but could be included under "About the role"? Might be better to include as part of "About the role" or maybe a separate section? Not in allowed headings. Could incorporate into About the role. We must remove duplicated lines, cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. The behavioral assessment link and instructions are application instructions; remove them. Also remove hashtags at end. Now craft HTML. Structure:

About the role

West Coast Based | Reports to Head of Sales | Regional Scope Build. Lead. Transform. If you thrive on responsiveness, accountability, and disciplined execution, this role is for you. Quickparts is hiring an Inside Sales Support Specialist to own the RFQ-to-order sales cycle for a portfolio of small-to-mid-sized accounts and to support day-to-day activity on Key Accounts. Reporting to the Head of Sales, with daily direction and prioritization from the Regional Sales Director, you will drive pipeline velocity through disciplined follow-up, convert quotes to orders, and grow wallet share within our existing customer base across CNC machining, injection molding, additive manufacturing, and sheet metal fabrication programs. Quickparts is a global leader in on-demand manufacturing with over 25 years of experience. We deliver advanced manufacturing solutions including metal & plastic 3D printing, CNC machining, injection molding, and casting patterns. With facilities across the US and Europe and more than 4,000 customers worldwide, we serve industries including aerospace, defense, automotive, medical, energy, and industrial equipment. Our team of application engineers and project managers average 10+ years of experience — ensuring customers receive expert guidance from prototype to production. Quickparts is ISO 9001 certified and ITAR registered, and we are continuously expanding our quality capabilities to support regulated industries.

Responsibilities

• Own the RFQ-to-order sales cycle for assigned accounts
• Drive quote-to-order conversion and re-order growth
• Grow wallet share within the existing customer base
• Support Key Account initiatives and strategic planning
• Maintain disciplined CRM management and forecasting
• Pipeline & Quote Management: Own the sales cycle end-to-end: RFQ intake, quoting, follow-up, order conversion, and re-orders; track opportunities by stage — Quote Request, Quote Submitted, Quote Issued, Order Conversion, Re-Order, and Quote Revision; partner with Program Management to deliver accurate, on-time quotes for new and repeat business; monitor quote aging and lead times; flag stalled opportunities and drive actions to improve close rates; maintain accurate pipeline visibility and forecasting in the CRM
• Customer Growth & Relationship Management: Proactively reach out on upcoming projects, forecasted demand, and re-order opportunities; follow up on open quotes and gather the specs, drawings, and DFM feedback needed to advance them; re-engage dormant accounts to win back lapsed business
• Strategic Account Support: Partner with the Director of Sales on Key Account initiatives, account reviews, and growth planning; surface customer insights, market intelligence, and competitive activity to inform account strategy
• CRM & Process Discipline: Keep customer interactions, quotes, and pipeline data current and accurate in the CRM (HubSpot); use CRM data to prioritize opportunities and sharpen sales effectiveness; act as a proactive problem-solver for customers and internal stakeholders — Program Management, Engineering, and Operations — resolving issues with urgency and clear communication

But we have duplicated bullet points; we could combine. However we must preserve all substantive info; we can keep them as separate list items but avoid redundancy. Might be okay to have a hierarchical list? Not required. Simplify: Use the bullet list from "Why This Role Matters" and then the detailed responsibilities as sub-items? Could flatten. Better: Provide a single

with items covering all responsibilities, maybe grouping. Let's extract all responsibilities statements: - Own the RFQ-to-order sales cycle for assigned accounts - Drive quote-to-order conversion and re-order growth - Grow wallet share within the existing customer base - Support Key Account initiatives and strategic planning - Maintain disciplined CRM management and forecasting - Pipeline & Quote Management: Own the sales cycle end-to-end: RFQ intake, quoting, follow-up, order conversion, and re-orders - Track opportunities by stage — Quote Request, Quote Submitted, Quote Issued, Order Conversion, Re-Order, and Quote Revision - Partner with Program Management to deliver accurate, on-time quotes for new and repeat business - Monitor quote aging and lead times; flag stalled opportunities and drive actions to improve close rates - Maintain accurate pipeline visibility and forecasting in the CRM - Customer Growth & Relationship Management: Proactively reach out on upcoming projects, forecasted demand, and re-order opportunities - Follow up on open quotes and gather the specs, drawings, and DFM feedback needed to advance them - Re-engage dormant accounts to win back lapsed business - Strategic Account Support: Partner with the Director of Sales on Key Account initiatives, account reviews, and growth planning - Surface customer insights, market intelligence, and competitive activity to inform account strategy - CRM & Process Discipline: Keep customer interactions, quotes, and pipeline data current and accurate in the CRM (HubSpot) - Use CRM data to prioritize opportunities and sharpen sales effectiveness - Act as a proactive problem-solver for customers and internal stakeholders — Program Management, Engineering, and Operations — resolving issues with urgency and clear communication We can list each as
• . That's a lot but okay. Now Requirements:

  Requirements

  • 3+ years in Inside Sales, Account Management, or Business Development
  • Proven track record managing a sales pipeline and driving quote-to-order conversion in a fast-paced, high-volume environment
  • Strong customer relationship, communication, and organizational skills
  • Proficiency with CRM systems and Microsoft Office
  • Self-motivated, highly organized, and results oriented
  Qualifications (preferred experience):

  Qualifications

  • Experience in contract manufacturing — CNC machining, injection molding, additive manufacturing, sheet metal fabrication, or industrial services
  • Familiarity with HubSpot, RFQ management, and processes in a manufacturing environment
  Skills: Could list skills like customer relationship, communication, organizational, CRM proficiency, MS Office, self-motivated, results oriented, etc. But we already covered many in Requirements. Might combine Skills with Requirements? But we need separate section if we have content. Could list skills like: Relationship building, communication, organization, CRM, MS Office, analytical, problem-solving, etc. However we risk duplication. Perhaps we can omit Skills section if content overlaps heavily; but instruction: prefer a few substantive sections over many thin ones. Could omit Skills and put skills under Requirements/Qualifications. But we need to follow allowed headings; we can omit Skills if not needed. Benefits:

  Benef