Jobs · Business Development · Tennessee

Live Corporate Events, Account Manager

Production Resource Group · Antioch, TN · 4 wk ago
Business DevelopmentFull-time
We need to output HTML fragment with sections: About the role? Actually the posting includes description about PRG and role. We need to use

for section headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections when there is real specific content. We must not repeat job title as heading. Must not include Job ID etc. Remove boilerplate like EEO, legal, scam warnings, etc. Also remove navigation/cookie etc. Keep substantive info. We need to parse the posting: It includes company description, role description, responsibilities list, qualifications & skills, education & experience required, preferred, physical & travel requirements, role development, etc. We need to decide sections: Possibly "About the role" (overview), "Responsibilities", "Qualifications", "Skills", "Education & Experience", "Physical & Travel Requirements", "Role Development". But we must only use allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we cannot add custom headings like Education & Experience or Physical & Travel Requirements unless they map to one of allowed headings. The allowed headings are limited. We can put education/experience under "Qualifications" maybe. Skills under "Skills". Responsibilities under "Responsibilities". About the role under "About the role". Benefits, Pay, Schedule only if present. The posting does not mention benefits, pay, schedule specifics. So we should not include those sections. "Requirements" heading could be used for mandatory qualifications? The posting has "Qualifications & Skills" and "Education & Experience Required". We could treat "Requirements" as the mandatory qualifications (education & experience). Then "Qualifications" could be for preferred? But we have both Qualifications and Skills headings allowed. We need to decide mapping. We have allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We can use: - About the role: overview of PRG and role description (first paragraphs). - Responsibilities: list of key responsibilities (the bullet list). - Requirements: mandatory qualifications (Education & Experience Required, plus maybe foundational knowledge etc? Actually those are qualifications/skills). But we can put mandatory experience/education here. - Qualifications: maybe preferred qualifications? Or we could put "Qualifications & Skills" under Qualifications heading, and Skills under Skills heading? But we have both Qualifications and Skills headings; we could split: Qualifications for education/experience, Skills for skills/competencies. However we already used Requirements for education/experience. Might be overlapping. Better: Use: - About the role: overview. - Responsibilities: responsibilities list. - Qualifications: mandatory qualifications (education & experience, foundational knowledge, etc.) - Skills: skills list (communication, organizational, CRM, etc.) - Possibly Requirements: maybe physical & travel requirements? But we have Physical & Travel Requirements section in posting. Could map to Requirements heading (makes sense). However we already used Qualifications for mandatory qualifications. Could use Requirements for physical & travel requirements. But we also have "Requirements" heading allowed; we can use it for physical & travel requirements. Then we need another heading for mandatory qualifications? Could use "Qualifications" for mandatory qualifications, and "Skills" for skills. That seems plausible. Thus: About the role: company description + role overview. Responsibilities: list of responsibilities. Qualifications: Education & Experience Required + maybe foundational knowledge? Actually foundational knowledge is more of a qualification. We'll include Education & Experience Required and maybe "Foundational knowledge of live events..." as part of qualifications. Skills: list of skills (communication, organizational, CRM, etc.) Requirements: Physical & Travel Requirements (ability to lift, travel, etc.) We should not include Benefits, Pay, Schedule. We must preserve all substantive information, not invent or summarize away detail. Must not include boilerplate like EEO, legal, scam warnings, etc. Also remove duplicated lines. We need to output only HTML fragment, no /, no markdown fences. We'll need to wrap content in appropriate tags:

About the role

then

... maybe multiple paragraphs. For lists,

  • ...
. We must preserve all substantive information: need to include details like PRG description, role description, responsibilities list (many items), qualifications & skills (foundational knowledge, strong interest, etc.), education & experience required (2+ years experience, some experience in project management, proficiency in Excel, etc.), preferred (previous client-facing experience, familiarity with Salesforce, experience developing estimates, OSHA 30 Certification, Bachelor's Degree), physical & travel requirements (ability to remain stationary, lift up to 20 lbs, work in office/warehouse/venue/event-site, travel, occasional evening/weekend hours), role development (description). Also maybe include "Role Development" section? Not allowed heading; we could incorporate into About the role or Qualifications? But we must preserve all substantive information; we cannot drop role development. We could put it under About the role as a paragraph, or maybe under Qualifications? But better to add a separate section? Not allowed headings. Could we add a

Role Development

? Not allowed per instruction: only use those headings. So we must embed role development content somewhere else, maybe under About the role or Qualifications. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It says e.g., implying those are examples but maybe we can use other headings? It says "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." That suggests we should use those headings for sections; but does it forbid other headings? It says "Use

for section headings (e.g. ...)". It doesn't explicitly say we cannot use other headings, but the examples are given. Safer to stick to those headings only. So we need to fit role development content into one of those sections. Perhaps under About the role (overview) we can include role development as part of role description. Or under Qualifications? Probably About the role is best. We must also include "Role Development" description: it's about progression, long-term objective. We'll embed that in About the role after initial description. Now we need to remove boilerplate: EEO, drug-free work environment, E-Verify, safety, scam warnings, etc. Also remove lines like "PRG is an Equal Opportunity Employer." etc. Also remove duplicated lines: there may be duplicate sentences? We'll just keep unique. Now craft HTML. First, About the role: combine PRG description and role overview and role development. Paragraph 1: PRG is the world’s leading technology provider within the entertainment and events industry. Our mission is to bring together the power of our people with our production and rental expertise to deliver unforgettable events. PRG has the largest inventory of production equipment for hire and offers a complete 360-degree range of services to clients within the live events industry. These include music touring and festivals, TV & Film, Theatre, Sports and E-sports and Corporate live events. Our clients and partners rely on PRG’s innovation, experience and in-depth expertise in video, lighting, rigging, staging, virtual productions, and set & automation systems to bring their creative visions to life. With 38 offices located in North America, South America, Europe, the Middle East, Asia and Australia, PRG offers the ability to provide services worldwide by collaborating with our local partners. Paragraph 2: The Corporate Events (CE) Account Manager is a client-facing sales and account support role within the CE business unit. Working closely with an Account Executive, the Account Manager supports the development, sale, coordination, and commercial management of live event and entertainment projects from initial opportunity through final billing. The Account Manager supports the Account Executive in managing the day-to-day needs of assigned accounts and projects, including developing Scopes of Work (SOWs), building orders, managing show budgets, coordinating change orders, maintaining CRM information, preparing proposals and estimates, and communicating directly with clients and internal teams. While primarily a support role, the Account Manager is also expected to actively participate in the sales process. Through a team-selling approach, the Account Manager works alongside the Account Executive to divide and co-manage opportunities and projects, develop existing accounts, identify new opportunities, and build new client relationships. The Account Manager also works closely with the assigned Project Management team throughout the project lifecycle, helping maintain alignment between the sold scope, client expectations, project execution, and financial objectives. This position is designed as an entry point into production sales and account management, providing hands-on exposure to the complete sales and project lifecycle while developing the commercial, technical, and relationship-management skills necessary for increased account ownership and future growth into an Account Executive role. This is a client-facing position requiring regular interaction with customers, Project Management, production, operations, technical teams, and other internal resources. Travel to client meetings, site visits, events, and industry activities is required based on business and project needs. Paragraph 3 (role development): The CE Account Manager role is intended to provide a foundation for long-term growth within production sales and account management. As experience, technical knowledge, commercial understanding, and client relationships develop, the Account Manager is expected to take on increasing responsibility for individual projects, sales opportunities, client relationships, and revenue generation. Successful development within the position should demonstrate progression from supporting account activity, to co-managing projects and opportunities, to developing and owning client relationships and sales opportunities. The long-term objective of the role is to develop the skills, experience, relationships, and commercial understanding necessary to progress toward an Account Executive position. Now Responsibilities: list all responsibilities bullet points from "Key Responsibilities" section. Need to preserve all items. Let's extract them: - Support the Account Executive in the management, development, and growth of assigned clients, accounts, and projects. - Work alongside the Account Executive in a team-selling environment, helping divide and co-manage opportunities based on account, client, and project needs. - Develop and maintain professional relationships with clients, becoming a trusted and knowledgeable point of contact within assigned accounts. - Participate in client meetings, discovery calls, presentations, site visits, project reviews, and other client-facing activities. - Assist in developing Scopes of Work (SOWs) that clearly define project requirements, deliverables, responsibilities, schedules, and commercial expectations. - Assist with estimating, proposal development, pricing, and preparation of client-facing sales materials. - Build and maintain project orders within company systems, ensuring information is accurate and current throughout the project lifecycle. - Work closely with the assigned Project Management team to manage show budgets, monitor project costs, and maintain alignment between the sold scope, client expectations, and financial objectives. - Review project revenue, costs, margins, and budget changes with the Account Executive and assigned Project Management team, identifying potential financial impacts throughout the project lifecycle. - Partner with the assigned Project Management team to identify changes in scope and develop, document, price, and process change orders for client review and approval. - Support client communication regarding budget updates, scope changes, change orders, and other commercial matters in coordination with the Account Executive and assigned Project Management team. - Participate in the RFP process, including gathering requirements, coordinating internal resources, developing responses, and supporting client presentations. - Maintain accurate client, opportunity, pipeline, activity, and project information within the company's CRM platform. - Conduct client outreach and follow-up, documenting activity, opportunities, and next steps within CRM. - Coordinate with the assigned Project Management team, technical teams, operations, and production resources to ensure sold solutions are clearly communicated and successfully transitioned into execution. - Support project closeout by working with the Account Executive and assigned Project Management team to review final orders, outstanding change orders, project costs, margins, and billing information. - Identify opportunities for additional services and account growth through ongoing client and project engagement. - Develop new relationships within existing client organizations while also supporting outreach and relationship development with prospective customers. - Participate in business development efforts, networking opportunities, industry events, and other activities intended to generate new relationships and sales

Similar jobs