Enterprise Account Exec
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). We should map content to appropriate headings. The instructions: Use 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 the job: includes location, hybrid schedule, salary range, OTE. That's about role details: location, schedule, salary. Could map to "About the role" heading (maybe). Also Pay and Schedule sections if we have specifics. The posting states salary: $120-150K base (OTE 240-300K+). Also schedule: hybrid in-office (3 days/week in office, plus 2 months of remote flexibility annually). So we can include Pay and Schedule sections.
- Company overview: description of company. Could be part of About the role? Or maybe separate "About the company"? Not in allowed headings list but we could use "About the role" for role description; company overview could be part of that or maybe we can omit? The instruction: Prefer a few substantive sections over many thin ones. We could combine company overview into About the role section. But we need to preserve all substantive info. Could embed company overview in a paragraph under About the role.
- Position overview: description of role responsibilities. Could go under Responsibilities.
- What you’ll do: list of duties. Could be under Responsibilities as bullet list.
- Who you are: qualifications/requirements/skills. Could be under Requirements, Qualifications, Skills.
- Why join Jones: benefits/perks? Could be under Benefits? Actually "Why join Jones" includes selling into enterprise orgs, team, define sales motion, engage senior leaders, strong earning potential, massive vision. That's more like selling points, could be under Benefits? But we have a separate "Featured benefits" list later: medical, vision, dental, 401(k), paid maternity/paternity leave, commuter benefits, disability insurance. That's benefits.
- Our culture: description of culture. Could be under Benefits? Not exactly. Could be its own section? Not in allowed headings list but we could maybe incorporate into About the role or Benefits? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but we could use others? Probably safer to stick to those. But we need to include culture info; maybe we can put under Benefits? Not ideal. Could put under About the role as a paragraph.
- EEO Statement: boilerplate to remove.
- Featured benefits: list of benefits -> Benefits section.
- Requirements added by the job poster: "6+ years of work experience with Sales" - that's a requirement; could be part of Requirements.
Thus we can structure:
About the role
... include location, hybrid schedule, company overview, position overview summary? Actually we need to preserve all substantive info; we can include paragraphs about location, schedule, company overview, position overview (maybe summarised). But we must not invent or summarize away detail; we can keep the original sentences.
Better: Keep the original text but maybe break into paragraphs.
We need to avoid duplication: The posting has "About the job" then "Company overview" then "Position overview". We'll combine them.
We'll also have:
Responsibilities
- Own and drive a focused pipeline of enterprise opportunities
... etc from "What you’ll do".
Requirements
- 6–8+ years of experience closing enterprise B2B SaaS deals, ideally in ConTech and/or with a track record of selling into general contractors
... etc from "Who you are". Also include the extra requirement "6+ years of work experience with Sales". Might be redundant but we keep.
Qualifications
maybe not needed if we already have Requirements covering qualifications. But we could split: Requirements for experience, Qualifications for skills? However the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But they gave separate examples; we can choose to include both if we have content. We have qualifications like "Proven track record of closing high ACV deals...", "Experience selling into real estate, construction, or adjacent industries...", "Demonstrated ability to navigate complex organizations...", etc. Those are qualifications. Could be under Qualifications.
We also have Skills: "Strong executive presence...", "Highly skilled in consultative and solution-based selling", "Disciplined in pipeline management...", "Comfortable operating in a fast-paced, evolving startup environment", "Self-starter with a strategic mindset and strong ownership mentality". Those could be under Skills.
Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule.
We need to ensure we don't create sections with filler. We have content for each.
Now Pay: we have salary base and OTE. So we can include Pay section with that info.
Schedule: we have hybrid schedule details.
Benefits: we have featured benefits list.
Now we need to remove EEO statement, boilerplate, duplicated lines, application instructions. There's no explicit application instructions besides maybe "Why join Jones" etc. We'll keep that as part of About the role? Actually "Why join Jones" is more like selling points; we could incorporate into About the role or Benefits? But we already have Benefits for tangible benefits; "Why join Jones" includes things like "Be part of a category-defining company...", "Sell into enterprise organizations with meaningful deal sizes...", "Work alongside a team with deep experience...", "Help define and build the enterprise sales motion...", "Engage with senior leaders...", "Strong earning potential tied to meaningful deal sizes", "Be part of a massive vision...". Those are more like selling points, not benefits. Could be part of About the role as a paragraph.
Our culture: also could be part of About the role.
Thus About the role section will contain: location/hybrid schedule, company overview, position overview, why join Jones, our culture. That's a lot but okay.
We must not repeat the job title as heading. The job title is "Enterprise Account Executive". We'll not add that.
Now we need to output only HTML fragment.
Let's craft:
About the role
This role is based in NYC with a hybrid in-office schedule (3 days/week in office, plus 2 months of remote flexibility annually). We strongly prefer candidates who can commit to our in-person culture, but would consider fully remote for an exceptional candidate.
Jones is the emerging leader of Risk and Compliance in real estate and construction management. Our compliance network makes it radically simpler for commercial property managers and tenants to ensure compliance, hire vendors and limit liability. Jones has experienced incredible growth fueled by an urgent need to digitize the archaic risk and compliance process in real estate and construction. Our AI-powered SaaS solution has delivered strong product-market fit across billions of square feet of real estate, major construction portfolios, and enterprise operators. We’re continuing to expand into larger, more complex organizations and are building a sales team capable of winning and scaling those relationships.
As an Enterprise Account Executive, you will own a number of high-value, strategic opportunities from initial engagement through close. You will focus on selling into large, complex organizations where deals require multi-threading across executives in operations, legal, risk, procurement, and finance. This role is less about volume and more about precision—deeply understanding customer workflows, building consensus, and driving large ACV deals to completion. You’ll play a key role in shaping our enterprise sales motion, including deal strategy, stakeholder mapping, and long-term account development.
Why join Jones: Be part of a category-defining company modernizing risk & compliance in real estate and construction; sell into enterprise organizations with meaningful deal sizes and clear ROI; work alongside a team with deep experience from leading PropTech companies; help define and build the enterprise sales motion at a critical stage of growth; engage with senior leaders at some of the largest real estate owners, operators, and construction firms; strong earning potential tied to meaningful deal sizes; be part of a massive vision to build the network powering risk & compliance across the built world.
Our culture: We aim to build a company where people feel ownership of their role and are able to grow and enrich their skills and experience; we want to create an environment where people are challenged and encouraged to be entrepreneurial; we rely on our team to help identify and take action on initiatives that can move our business forward. Elements of our culture that can be seen in every one of our people are: fall in love with problems – we are obsessed with solving customer problems because it’s in our DNA — actively listening to customer challenges and treating them like our own; give help generously – we hire and nurture brilliant people who are generous with their time, skills, and perspectives; this generosity compounds across the company; own the outcome – every day we make vital decisions that shape the future of our company; we hold ourselves accountable to these decisions in order to build a durable, powerful business; take care of yourself – building a category-leading company is hard. It can only be achieved by encouraging and enabling our team’s mental, emotional, and physical well‑being; build trust everywhere – every Jones experience is designed to give our clients, our team, and our industry unshakable confidence in the integrity of the company.
Then Responsibilities:
Responsibilities
- Own and drive a focused pipeline of enterprise opportunities
- Develop strategic account plans and identify key stakeholders across target organizations
- Lead complex discovery processes to uncover operational, financial, and compliance pain points
- Run tailored, high-impact demos and presentations for executive audiences
- Multi-thread deals across departments including operations, legal, risk, procurement, and finance
- Build business cases and ROI narratives aligned to enterprise-level priorities
- Drive deal strategy, including pricing, negotiation, procurement navigation, and contract execution
- Partner closely with SDRs, Marketing, Product, and Customer Success to support deal progression and expansion
- Maintain high-quality pipeline hygiene and accurate forecasting
- Contribute to refining enterprise sales playbooks
- 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 the job: includes location, hybrid schedule, salary range, OTE. That's about role details: location, schedule, salary. Could map to "About the role" heading (maybe). Also Pay and Schedule sections if we have specifics. The posting states salary: $120-150K base (OTE 240-300K+). Also schedule: hybrid in-office (3 days/week in office, plus 2 months of remote flexibility annually). So we can include Pay and Schedule sections. - Company overview: description of company. Could be part of About the role? Or maybe separate "About the company"? Not in allowed headings list but we could use "About the role" for role description; company overview could be part of that or maybe we can omit? The instruction: Prefer a few substantive sections over many thin ones. We could combine company overview into About the role section. But we need to preserve all substantive info. Could embed company overview in a paragraph under About the role. - Position overview: description of role responsibilities. Could go under Responsibilities. - What you’ll do: list of duties. Could be under Responsibilities as bullet list. - Who you are: qualifications/requirements/skills. Could be under Requirements, Qualifications, Skills. - Why join Jones: benefits/perks? Could be under Benefits? Actually "Why join Jones" includes selling into enterprise orgs, team, define sales motion, engage senior leaders, strong earning potential, massive vision. That's more like selling points, could be under Benefits? But we have a separate "Featured benefits" list later: medical, vision, dental, 401(k), paid maternity/paternity leave, commuter benefits, disability insurance. That's benefits. - Our culture: description of culture. Could be under Benefits? Not exactly. Could be its own section? Not in allowed headings list but we could maybe incorporate into About the role or Benefits? The instruction says use headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It doesn't forbid other headings? It says "Use
for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." The e.g. suggests those are examples but we could use others? Probably safer to stick to those. But we need to include culture info; maybe we can put under Benefits? Not ideal. Could put under About the role as a paragraph. - EEO Statement: boilerplate to remove. - Featured benefits: list of benefits -> Benefits section. - Requirements added by the job poster: "6+ years of work experience with Sales" - that's a requirement; could be part of Requirements. Thus we can structure:
About the role
... include location, hybrid schedule, company overview, position overview summary? Actually we need to preserve all substantive info; we can include paragraphs about location, schedule, company overview, position overview (maybe summarised). But we must not invent or summarize away detail; we can keep the original sentences. Better: Keep the original text but maybe break into paragraphs. We need to avoid duplication: The posting has "About the job" then "Company overview" then "Position overview". We'll combine them. We'll also have:
Responsibilities
- Own and drive a focused pipeline of enterprise opportunities ... etc from "What you’ll do".
- 6–8+ years of experience closing enterprise B2B SaaS deals, ideally in ConTech and/or with a track record of selling into general contractors ... etc from "Who you are". Also include the extra requirement "6+ years of work experience with Sales". Might be redundant but we keep.
- Own and drive a focused pipeline of enterprise opportunities
- Develop strategic account plans and identify key stakeholders across target organizations
- Lead complex discovery processes to uncover operational, financial, and compliance pain points
- Run tailored, high-impact demos and presentations for executive audiences
- Multi-thread deals across departments including operations, legal, risk, procurement, and finance
- Build business cases and ROI narratives aligned to enterprise-level priorities
- Drive deal strategy, including pricing, negotiation, procurement navigation, and contract execution
- Partner closely with SDRs, Marketing, Product, and Customer Success to support deal progression and expansion
- Maintain high-quality pipeline hygiene and accurate forecasting
- Contribute to refining enterprise sales playbooks
Requirements
Qualifications
maybe not needed if we already have Requirements covering qualifications. But we could split: Requirements for experience, Qualifications for skills? However the instruction says prefer few substantive sections over many thin ones. So maybe combine Requirements and Qualifications into one section? But they gave separate examples; we can choose to include both if we have content. We have qualifications like "Proven track record of closing high ACV deals...", "Experience selling into real estate, construction, or adjacent industries...", "Demonstrated ability to navigate complex organizations...", etc. Those are qualifications. Could be under Qualifications. We also have Skills: "Strong executive presence...", "Highly skilled in consultative and solution-based selling", "Disciplined in pipeline management...", "Comfortable operating in a fast-paced, evolving startup environment", "Self-starter with a strategic mindset and strong ownership mentality". Those could be under Skills. Thus we could have sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to ensure we don't create sections with filler. We have content for each. Now Pay: we have salary base and OTE. So we can include Pay section with that info. Schedule: we have hybrid schedule details. Benefits: we have featured benefits list. Now we need to remove EEO statement, boilerplate, duplicated lines, application instructions. There's no explicit application instructions besides maybe "Why join Jones" etc. We'll keep that as part of About the role? Actually "Why join Jones" is more like selling points; we could incorporate into About the role or Benefits? But we already have Benefits for tangible benefits; "Why join Jones" includes things like "Be part of a category-defining company...", "Sell into enterprise organizations with meaningful deal sizes...", "Work alongside a team with deep experience...", "Help define and build the enterprise sales motion...", "Engage with senior leaders...", "Strong earning potential tied to meaningful deal sizes", "Be part of a massive vision...". Those are more like selling points, not benefits. Could be part of About the role as a paragraph. Our culture: also could be part of About the role. Thus About the role section will contain: location/hybrid schedule, company overview, position overview, why join Jones, our culture. That's a lot but okay. We must not repeat the job title as heading. The job title is "Enterprise Account Executive". We'll not add that. Now we need to output only HTML fragment. Let's craft:About the role
This role is based in NYC with a hybrid in-office schedule (3 days/week in office, plus 2 months of remote flexibility annually). We strongly prefer candidates who can commit to our in-person culture, but would consider fully remote for an exceptional candidate.
Jones is the emerging leader of Risk and Compliance in real estate and construction management. Our compliance network makes it radically simpler for commercial property managers and tenants to ensure compliance, hire vendors and limit liability. Jones has experienced incredible growth fueled by an urgent need to digitize the archaic risk and compliance process in real estate and construction. Our AI-powered SaaS solution has delivered strong product-market fit across billions of square feet of real estate, major construction portfolios, and enterprise operators. We’re continuing to expand into larger, more complex organizations and are building a sales team capable of winning and scaling those relationships.
As an Enterprise Account Executive, you will own a number of high-value, strategic opportunities from initial engagement through close. You will focus on selling into large, complex organizations where deals require multi-threading across executives in operations, legal, risk, procurement, and finance. This role is less about volume and more about precision—deeply understanding customer workflows, building consensus, and driving large ACV deals to completion. You’ll play a key role in shaping our enterprise sales motion, including deal strategy, stakeholder mapping, and long-term account development.
Why join Jones: Be part of a category-defining company modernizing risk & compliance in real estate and construction; sell into enterprise organizations with meaningful deal sizes and clear ROI; work alongside a team with deep experience from leading PropTech companies; help define and build the enterprise sales motion at a critical stage of growth; engage with senior leaders at some of the largest real estate owners, operators, and construction firms; strong earning potential tied to meaningful deal sizes; be part of a massive vision to build the network powering risk & compliance across the built world.
Our culture: We aim to build a company where people feel ownership of their role and are able to grow and enrich their skills and experience; we want to create an environment where people are challenged and encouraged to be entrepreneurial; we rely on our team to help identify and take action on initiatives that can move our business forward. Elements of our culture that can be seen in every one of our people are: fall in love with problems – we are obsessed with solving customer problems because it’s in our DNA — actively listening to customer challenges and treating them like our own; give help generously – we hire and nurture brilliant people who are generous with their time, skills, and perspectives; this generosity compounds across the company; own the outcome – every day we make vital decisions that shape the future of our company; we hold ourselves accountable to these decisions in order to build a durable, powerful business; take care of yourself – building a category-leading company is hard. It can only be achieved by encouraging and enabling our team’s mental, emotional, and physical well‑being; build trust everywhere – every Jones experience is designed to give our clients, our team, and our industry unshakable confidence in the integrity of the company.
Then Responsibilities:Responsibilities