Enterprise Account Executive - North America
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). Use - for any list of duties/requirements/benefits, and
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences.
Thus we need to decide which sections to include based on content.
We have:
- About Abacum (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Abacum" describing company. Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if appropriate. "About Abacum" is more about company; maybe we can put under "About the role"? But that heading expects description of role. However we have description of responsibilities later. Could combine company description into a short paragraph under "About the role"? Might be okay. But we need to preserve all substantive info. Could create a section "About the role" containing both company overview and role overview? The instruction says use those headings for section headings; we can also add other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use those headings. Probably we should stick to those headings where applicable. So we can have:
About the role
- include company description and role overview (maybe first paragraph "We are looking for...").
Responsibilities
- list of duties.
Requirements
- "What We Need..." bullet list.
Skills
- maybe "Bonus points if you have..." could be skills.
Benefits
- "What You Get" and "Benefits" list.
We might also have Pay? Not explicitly stated; they mention "Competitive base, uncapped commission, and equity". That is compensation/pay. So we could include a Pay section with that info. However instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. They do state compensation: "Competitive base, uncapped commission, and equity". So we can include Pay section.
Schedule? Not mentioned (remote in North America, with hubs). Could infer remote work but not explicit schedule. Probably not include Schedule.
We need to avoid duplication. Also need to remove EEO boilerplate at end.
We need to preserve all substantive info: company description, mission, etc. Also "Why sell Abacum" section includes product selling points; is that substantive for the job? It's more about product; could be included under "About the role" or maybe as its own section like "Why Abacum"? But not in allowed headings. Could we add a custom heading? The instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? Safer to stick to those. So we can incorporate "Why sell Abacum" content into "About the role" or maybe "Responsibilities"? Probably better to put under "About the role" as it describes why the product is good to sell.
Also "Our Values" is substantive; could be included under a section? Not in list. Could we add a section "Values"? Not in allowed headings. Might be considered boilerplate? It's not EEO but still values. Might be okay to include as a section with heading "Our Values"? The instruction didn't forbid other headings, but said use those headings for section headings (e.g...). It might be okay to add other headings if needed, but better to follow guidance: Prefer a few substantive sections over many thin ones. Could incorporate values into "About the role" or maybe as a separate section with heading "Our Values". I'd lean to include as its own section because it's substantive and not covered elsewhere. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, just gives examples. So we can use other headings if needed. But to be safe, maybe we can incorporate values into "About the role" as a paragraph.
We need to avoid duplication: The "Benefits" list appears twice: "What You Get" includes bullet list: Competitive compensation including equity package, Competitive vacation policy, Medical Insurance, L&D budget, Access to Meditopia, Language courses. Then later a separate "Benefits" heading with same list? Actually after "What You Get" they list: Competitive base, uncapped commission, and equity Remote in North America, with hubs in New York, Toronto and Barcelona Direct access to leadership and a real say in how we sell to enterprise Benefits Competitive compensation including equity packageCompetitive vacation policyMedical InsuranceL&DBudgetAccess to Meditopia (wellbeing platform)Language courses (English / Spanish). It seems duplicated. We'll combine into one Benefits section.
We need to output only HTML fragment.
Let's craft:
About the role
Abacum is the leading Business Planning solution for finance teams to drive performance. By automating reporting, enabling collaboration, and simplifying planning and forecasting, we help finance teams shift from number crunching to driving strategic decisions. Founded in 2020 by two former CFOs, we’ve grown into a global team of 100+ people across 30+ nationalities. Headquartered in New York, we have offices in Toronto and Barcelona. We’re trusted by industry leaders such as Dish Networks, Strava, BetterUp, Kajabi, JG Wentworth, Abridge, Cortex, and hundreds more. We have raised over $100m, closing in June 2025 our $60M Series B, led by Scale Venture Partners, with the strong participation of Cathay Innovation, Y Combinator, Atomico, Creandum, and angel operators from Adyen, Zapier, and Twitch. Our mission is ambitious and we can’t do it alone - join Abacum as we build the future of Business Planning! We are looking for an enterprise seller who already knows the Office of the CFO. You've carried a number selling planning, EPM, FP&A or finance software. You know how a CFO buys, how a steering committee stalls, and how to get a multi-stakeholder deal signed. At Abacum you'll own a named territory of enterprise and upper mid-market accounts across North America. Many of them run legacy planning tools or spreadsheets that can't keep up with the business. Your job is to show them a better foundation, and win.
Then responsibilities:
Responsibilities
- Own the full sales cycle for a named book of enterprise accounts, from first meeting to signed contract
- Build and run your own pipeline through targeted outbound, events, and partner co-selling with ERP vendors and implementation partners
- Sell to CFOs, VPs of Finance and Heads of FP&A, and bring IT, procurement, security and legal along the way
- Run complex evaluations: discovery, business cases, proofs of concept, and competitive displacements
- Forecast with discipline and keep a clean pipeline in CRM
- Work with Solutions Engineering, Product and Leadership to shape deals, and feed what you hear in the market back into the roadmap
Requirements:
Requirements
- 6+ years of quota-carrying B2B SaaS sales, with at least 3 years closing enterprise deals
- Experience selling EPM, FP&A, planning, or other Office-of-the-CFO software (finance, ERP, spend, or data platforms)
- A track record of closing six-figure ARR deals with 3–6 month cycles and hitting or beating quota
- Comfort leading multi-stakeholder deals with finance, IT, procurement and security at the table
- Experience displacing an incumbent, whether a legacy system or a spreadsheet-based process
- A consultative, value-based approach: you build a business case in a CFO's language
- The drive to build your own pipeline, not wait for inbound
- Clear, sharp written and verbal communication, including running demos with senior buyers
- Based in North America, with the ability to travel to customers and events
Skills (Bonus points):
Skills
- Sold with or through ERP ecosystems (NetSuite, Sage Intacct, Microsoft Dynamics) or implementation partners
- Worked in finance, or you're comfortable talking models, drivers and variances with an FP&A team
- Used a structured sales method (MEDDPICC, Command of the Message, or similar)
- Been an early seller at a scaling company and helped build the enterprise playbook
Pay:
Pay
Competitive base, uncapped commission, and equity.
Benefits:
Benefits
- Remote in North America, with hubs in New York, Toronto and Barcelona
- Direct access to leadership and a real say in how we sell to enterprise
- Competitive compensation including equity package
- Competitive vacation policy
- Medical Insurance
- L&D budget
- Access to Meditopia (wellbeing platform)
- Language courses (English / Spanish)
We could also include "Why sell Abacum" content maybe under About the role or as a separate section "Why Abacum"? But we already covered product strengths in About the role? Not yet. We could add a paragraph after company description about why sell Abacum. Let's incorporate that into About the role after the initial description: maybe a separate paragraph.
Add after company description: "
for prose. Do NOT repeat the job title as a heading (the page already shows it) and do NOT put Job ID / requisition numbers as headings — fold minor metadata into a short
or drop it. Preserve ALL substantive information; do NOT invent or summarize away detail. Remove cookie/navigation/legal/EEO/equal-opportunity/scam-warning boilerplate, duplicated lines, and application instructions. IMPORTANT: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text (e.g. "commensurate with experience", "not specified", "N/A", "varies", "TBD") and never create Pay/Schedule/Benefits sections unless the posting actually states them. Prefer a few substantive sections over many thin ones. Output ONLY the HTML fragment — no /, no markdown code fences. Thus we need to decide which sections to include based on content. We have: - About Abacum (company description) - could be "About the role"? Actually "About the role" is typical heading for role description. But we have "About Abacum" describing company. Could map to "About the role"? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we should map content to those headings if appropriate. "About Abacum" is more about company; maybe we can put under "About the role"? But that heading expects description of role. However we have description of responsibilities later. Could combine company description into a short paragraph under "About the role"? Might be okay. But we need to preserve all substantive info. Could create a section "About the role" containing both company overview and role overview? The instruction says use those headings for section headings; we can also add other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies those are examples; we can use those headings. Probably we should stick to those headings where applicable. So we can have:
About the role
- include company description and role overview (maybe first paragraph "We are looking for...").
Responsibilities
- list of duties.
Requirements
- "What We Need..." bullet list.
Skills
- maybe "Bonus points if you have..." could be skills.
Benefits
- "What You Get" and "Benefits" list.
We might also have Pay? Not explicitly stated; they mention "Competitive base, uncapped commission, and equity". That is compensation/pay. So we could include a Pay section with that info. However instruction says never create Pay/Schedule/Benefits sections unless posting actually states them. They do state compensation: "Competitive base, uncapped commission, and equity". So we can include Pay section.
Schedule? Not mentioned (remote in North America, with hubs). Could infer remote work but not explicit schedule. Probably not include Schedule.
We need to avoid duplication. Also need to remove EEO boilerplate at end.
We need to preserve all substantive info: company description, mission, etc. Also "Why sell Abacum" section includes product selling points; is that substantive for the job? It's more about product; could be included under "About the role" or maybe as its own section like "Why Abacum"? But not in allowed headings. Could we add a custom heading? The instruction says use those headings for section headings (e.g...). It doesn't forbid other headings, but says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It implies we should use those headings; but we could also add other headings if needed? Safer to stick to those. So we can incorporate "Why sell Abacum" content into "About the role" or maybe "Responsibilities"? Probably better to put under "About the role" as it describes why the product is good to sell.
Also "Our Values" is substantive; could be included under a section? Not in list. Could we add a section "Values"? Not in allowed headings. Might be considered boilerplate? It's not EEO but still values. Might be okay to include as a section with heading "Our Values"? The instruction didn't forbid other headings, but said use those headings for section headings (e.g...). It might be okay to add other headings if needed, but better to follow guidance: Prefer a few substantive sections over many thin ones. Could incorporate values into "About the role" or maybe as a separate section with heading "Our Values". I'd lean to include as its own section because it's substantive and not covered elsewhere. However the instruction says "Use for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, just gives examples. So we can use other headings if needed. But to be safe, maybe we can incorporate values into "About the role" as a paragraph.
We need to avoid duplication: The "Benefits" list appears twice: "What You Get" includes bullet list: Competitive compensation including equity package, Competitive vacation policy, Medical Insurance, L&D budget, Access to Meditopia, Language courses. Then later a separate "Benefits" heading with same list? Actually after "What You Get" they list: Competitive base, uncapped commission, and equity Remote in North America, with hubs in New York, Toronto and Barcelona Direct access to leadership and a real say in how we sell to enterprise Benefits Competitive compensation including equity packageCompetitive vacation policyMedical InsuranceL&DBudgetAccess to Meditopia (wellbeing platform)Language courses (English / Spanish). It seems duplicated. We'll combine into one Benefits section.
We need to output only HTML fragment.
Let's craft:
About the role
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It doesn't say you cannot use other headings, just gives examples. So we can use other headings if needed. But to be safe, maybe we can incorporate values into "About the role" as a paragraph.
We need to avoid duplication: The "Benefits" list appears twice: "What You Get" includes bullet list: Competitive compensation including equity package, Competitive vacation policy, Medical Insurance, L&D budget, Access to Meditopia, Language courses. Then later a separate "Benefits" heading with same list? Actually after "What You Get" they list: Competitive base, uncapped commission, and equity Remote in North America, with hubs in New York, Toronto and Barcelona Direct access to leadership and a real say in how we sell to enterprise Benefits Competitive compensation including equity packageCompetitive vacation policyMedical InsuranceL&DBudgetAccess to Meditopia (wellbeing platform)Language courses (English / Spanish). It seems duplicated. We'll combine into one Benefits section.
We need to output only HTML fragment.
Let's craft:
About the role
Abacum is the leading Business Planning solution for finance teams to drive performance. By automating reporting, enabling collaboration, and simplifying planning and forecasting, we help finance teams shift from number crunching to driving strategic decisions. Founded in 2020 by two former CFOs, we’ve grown into a global team of 100+ people across 30+ nationalities. Headquartered in New York, we have offices in Toronto and Barcelona. We’re trusted by industry leaders such as Dish Networks, Strava, BetterUp, Kajabi, JG Wentworth, Abridge, Cortex, and hundreds more. We have raised over $100m, closing in June 2025 our $60M Series B, led by Scale Venture Partners, with the strong participation of Cathay Innovation, Y Combinator, Atomico, Creandum, and angel operators from Adyen, Zapier, and Twitch. Our mission is ambitious and we can’t do it alone - join Abacum as we build the future of Business Planning! We are looking for an enterprise seller who already knows the Office of the CFO. You've carried a number selling planning, EPM, FP&A or finance software. You know how a CFO buys, how a steering committee stalls, and how to get a multi-stakeholder deal signed. At Abacum you'll own a named territory of enterprise and upper mid-market accounts across North America. Many of them run legacy planning tools or spreadsheets that can't keep up with the business. Your job is to show them a better foundation, and win.
Then responsibilities:Responsibilities
- Own the full sales cycle for a named book of enterprise accounts, from first meeting to signed contract
- Build and run your own pipeline through targeted outbound, events, and partner co-selling with ERP vendors and implementation partners
- Sell to CFOs, VPs of Finance and Heads of FP&A, and bring IT, procurement, security and legal along the way
- Run complex evaluations: discovery, business cases, proofs of concept, and competitive displacements
- Forecast with discipline and keep a clean pipeline in CRM
- Work with Solutions Engineering, Product and Leadership to shape deals, and feed what you hear in the market back into the roadmap
Requirements
- 6+ years of quota-carrying B2B SaaS sales, with at least 3 years closing enterprise deals
- Experience selling EPM, FP&A, planning, or other Office-of-the-CFO software (finance, ERP, spend, or data platforms)
- A track record of closing six-figure ARR deals with 3–6 month cycles and hitting or beating quota
- Comfort leading multi-stakeholder deals with finance, IT, procurement and security at the table
- Experience displacing an incumbent, whether a legacy system or a spreadsheet-based process
- A consultative, value-based approach: you build a business case in a CFO's language
- The drive to build your own pipeline, not wait for inbound
- Clear, sharp written and verbal communication, including running demos with senior buyers
- Based in North America, with the ability to travel to customers and events
Skills
- Sold with or through ERP ecosystems (NetSuite, Sage Intacct, Microsoft Dynamics) or implementation partners
- Worked in finance, or you're comfortable talking models, drivers and variances with an FP&A team
- Used a structured sales method (MEDDPICC, Command of the Message, or similar)
- Been an early seller at a scaling company and helped build the enterprise playbook
Pay
Competitive base, uncapped commission, and equity.
Benefits:Benefits
- Remote in North America, with hubs in New York, Toronto and Barcelona
- Direct access to leadership and a real say in how we sell to enterprise
- Competitive compensation including equity package
- Competitive vacation policy
- Medical Insurance
- L&D budget
- Access to Meditopia (wellbeing platform)
- Language courses (English / Spanish)