Renewals Manager - North America

We need to output HTML fragment with sections: About the role? Actually the posting includes intro paragraphs about company and mission. Should we include an "About the role" heading? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We need to include sections only when posting has real specific content. We have content: role description (Your role:...), what you will own (list), requirements (Your profile:...), benefits (Benefits Perks & Benefits...). Also maybe "About the role" could be the intro paragraphs about company and mission? But they said do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID etc. The intro about company could be considered "About the role" or maybe "About the company". But they gave example headings; we can use "About the role" for the introductory description of the role and company. However we need to ensure we have substantive content. The intro includes: "Do you want to dive in the fast-growing industry of drones... Joining Flyability is not just taking on a new job; it is seizing the opportunity..." That's about company and mission. Could be placed under

About the role

with paragraphs. Then "Your role:" and "What you will own:" could be under Responsibilities? Actually "Your role:" describes mission; "What you will own:" lists specific ownership items. Could combine under Responsibilities. Or we could have separate sections: Responsibilities (Your role) and maybe "What you will own" as part of Responsibilities. Requirements section: "Your profile:" with bullet list. Benefits section: "Benefits Perks & Benefits You'll Love:" with list. Pay: they gave salary range etc. That's pay info. Should we create a Pay section? The instruction: never create Pay/Schedule/Benefits sections unless the posting actually states them. They do state salary range, variable, uncapped commission, etc. So we should include a Pay section with that info. Schedule: they mention hybrid work model: 2 days remote, 3 days in office. That's schedule info. So we can include Schedule section. We should not include sections like Qualifications, Skills unless present. Requirements covers qualifications. Could also have Skills but not needed. We must remove boilerplate: EEO, equal opportunity, automated screening notice, etc. Also remove application instructions like "Ready to join?..." and "Please don't hesitate to apply". Also remove "Flyability is an Equal Opportunity Employer..." etc. Also remove "Automated Screening Notice". Also remove "Benefits Perks & Benefits You'll Love:" heading? We'll keep benefits content but not the heading; we'll use

Benefits

. We need to preserve all substantive information: company intro, role mission, what you will own list, requirements list, benefits list, pay info, schedule info. We must not invent or summarize away detail. Keep specifics like numbers. We need to use

• for any list of duties/requirements/benefits. Use

  for prose. We must not repeat job title as heading. So no

  Renewals Manager - North America

  . Good. We must not put Job ID etc. We must output only HTML fragment, no /, no markdown fences. Let's craft:

  About the role

  Do you want to dive in the fast-growing industry of drones and get a rewarding experience in a dynamic scale-up environment? At Flyability, we believe that robots should be sent into hazardous places and dangerous environments instead of humans. To support our belief, we created Elios, the world's first collision-tolerant flying robot that can safely enter, survey, and inspect confined spaces so that people don't have to. With more than 130 employees, Flyability is the pioneer in the UAS indoor inspection industry. Joining Flyability is not just taking on a new job; it is seizing the opportunity to improve the lives of millions of people and contribute to the future of robotics.

  Responsibilities

  Your mission is to own the renewal of every subscription-based product in the United States and Canada - and to grow the recurring revenue they represent. Every Elios in the field carries a renewal date. You make sure each one is contacted early, quoted properly, negotiated well and closed on time, whether the customer buys directly or through one of our reseller partners. You will run a structured renewal cadence in Salesforce, keep the pipeline clean enough to forecast from, and use each renewal conversation to surface upsell and cross-sell opportunities for the sales team. You will be the regional subject-matter expert on our software and cloud products. You will work closely with the Key Account Manager, the Area Sales Managers, the Customer Success Manager and our resellers, and with your counterpart who covers renewals for the rest of the world. You will report directly to the Head of Key Accounts & Customer Success, based in Switzerland, and be part of our Denver team.

  What you will own:

  • The North America renewal target and renewal rate for all subscription-based products and services (Premium software licenses, Cloud, Care Packages), through both direct sales and resellers
  • A structured renewal cadence: first contact well ahead of expiry, quote, negotiation, close, with renewals closed before their expiry date
  • Renewal pipeline hygiene in Salesforce: accurate values, dates and stages, and a forecast you can stand behind
  • Proactive engagement with customers, mostly remote: demonstrations of software and cloud features, value conversations, negotiation and closing of renewal contracts
  • Upsell and cross-sell identification on every renewal, handed to the Area Sales Managers and Key Account Manager to maximize revenue at the account
  • Reactivation of lapsed licenses and recovery of at-risk accounts, in coordination with Customer Success
  • Enablement of our reseller partners on the renewal process, and joint work on their renewal base
  • Continuous improvement of the renewal process and tools with Sales Operations
  • Occasional travel to customers as the subscription product expert in larger opportunities, and the software and cloud expert role at reseller events, Flyability events and targeted trade shows

  Requirements

  Your profile:

  • Bachelor's degree in business administration, engineering or a related field
  • 5+ years in B2B sales or account management, with subscription or recurring-revenue models; experience working with resellers or channel partners is an asset; experience in the industrial inspection or surveying industry is a plus
  • Fluent English; any other language a plus
  • Organized and rigorous - runs a cadence and does not let things slip; a confident negotiator, comfortable talking value and price; clear communicator with customers, partners and colleagues; manages multiple priorities without losing the detail
  • Comfortable using CRM tools; Salesforce experience preferred
  • Authorized to work in the United States; based in or willing to relocate to the Denver area; able to travel up to 20% of the time

  Benefits

  • Salary range: USD 85,000 to USD 100,000 base + variable
  • Uncapped commission scheme for over-performance
  • Generous employer contributions for health insurance
  • Vision and supplemental life insurance available
  • 401K matching
  • Short-term and long-term disability
  • Life insurance paid for employee
  • 15 days PTO + 9 federal holidays
  • Additional days off are granted based on your seniority with us, up to 5 days
  • Annual trip to Switzerland
  • Phone allowance for frequent travelers
  • Hybrid work model: 2 days remote work, 3 days in the office
  We might also include Pay section separate from Benefits? The benefits list includes salary range etc. But we could separate Pay and Benefits. However the instruction: prefer a few substantive sections over many thin ones. Could combine Pay and Benefits into one Benefits section as we did. But they gave example headings including Pay and Benefits separate. However we can keep as Benefits because it includes pay. But they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state salary range etc. So we could have a Pay section for salary and commission, and Benefits for other perks. But we already included schedule in benefits list (hybrid work model). Might be better to split: Pay section for salary range and uncapped commission; Benefits section for health insurance, 401K, disability, life insurance, PTO, additional days, annual trip, phone allowance; Schedule section for hybrid work model. However that creates many thin sections. The instruction says prefer a few substantive sections over many thin ones. So maybe combine Pay and Benefits into one Benefits section, and Schedule separate? But schedule is just one line; could be included in Benefits as well. However they said never create Pay/Schedule/Benefits sections unless posting actually states them. It does state hybrid work model, so we could include Schedule section. But we could also include it in Benefits as it's a work arrangement. The instruction says prefer a few substantive sections over many thin ones. So maybe we have three sections: About the role, Responsibilities, Requirements, Benefits (including pay and schedule). That's four sections. That's okay. But we need to ensure we don't create a Pay section with filler like "commensurate with experience". We have actual numbers, so it's fine to have Pay section. However we already put salary in Benefits list; if we create Pay section we would duplicate. Better to have Pay section separate and Benefits separate, but that's two thin sections. Could combine them into one "Compensation & Benefits" but not in example headings. The instruction says use

  for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). It gives examples but not strict requirement to use exactly those; we can use other headings? Probably they expect those headings if applicable. So we could use Pay and Benefits separate. But then we have many sections: About the role, Responsibilities, Requirements, Pay, Benefits, Schedule. That's six sections, some may be thin but each has substantive content. The instruction: "Prefer a few substantive sections over many thin ones." So we should try to minimize number of sections while still covering all info. Could we put Pay and Benefits together under Benefits? That would be one section containing both pay and benefits. That's fewer sections. Schedule could be included under Benefits as well (hybrid work model). That would be three sections: About the role, Responsibilities, Requirements, Benefits (including pay, perks, schedule). That's four sections. That seems reasonable. Thus we will have:

  About the role

  ...

  Responsibilities

  Your mission is ...

  What you will own:

  ...

  Requirements

  Your profile:

  ...

  Benefits

  • Salary range: USD 85,000 to USD 100,000 base + variable
  • Uncapped commission scheme for over-performance
  • Generous employer contributions for health insurance
  • Vision and supplemental life insurance available
  • 401K matching
  • Short-term and long-term disability
  • Life insurance paid for employee
  • 15 days PTO +