Vice President of Corporate Development & Strategic Partnerships

We need to output HTML fragment with sections: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. Only include sections that have real specific content. The posting includes "About Us", "About The Role", "What You'll Do", "What You Bring", "How Success Is Measured", "Why Join STACK?" plus compensation info. We need to map to headings: About the role (maybe combine About Us and About The Role? The instruction: use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should have headings like About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. We need to include only sections with real content. We have content for About the role: we can put the "About Us" and "About The Role" paragraphs under About the role heading. Responsibilities: from "What You'll Do" (Corporate Development & M&A and Strategic Partnerships). That's responsibilities. Requirements: maybe from "What You Bring" (experience, track record, etc.) Could be Requirements. Qualifications: maybe overlapping with Requirements; but we need to decide. Could treat "What You Bring" as Requirements, and maybe "How Success Is Measured" as Qualifications? Or maybe Qualifications could be education? Not present. Better to not create Qualifications if no specific content. The instruction: include a section ONLY when the posting has real, specific content for it — never emit a heading followed by filler/placeholder text. So we should only include sections where we have substantive content. We have: - About the role: yes. - Responsibilities: yes (What You'll Do). - Requirements: yes (What You Bring). - Qualifications: maybe we could treat "How Success Is Measured" as Qualifications? But that's more about success metrics. Could be considered Qualifications? Not exactly. Safer to omit Qualifications if no explicit qualifications like degree, certifications. - Skills: maybe we could extract skills from What You Bring (financial and analytical capabilities, executive communication, etc.) Could be a Skills section. But we already have Requirements covering experience; we could split. However instruction: prefer a few substantive sections over many thin ones. So maybe combine Requirements and Skills into one? But we need to follow headings list; we can omit Skills if not distinct. - Benefits: we have benefits info: health insurance, life insurance, 401(k) & paid time off. Also remote-first, async-friendly, etc. So we can include Benefits. - Pay: we have compensation range: $165k-200k USD + commission/bonus. So include Pay. - Schedule: we have remote-first, async-friendly environment. Could be schedule info: remote-first, async-friendly. That's schedule. So include Schedule. Thus sections: About the role, Responsibilities, Requirements, Benefits, Pay, Schedule. Possibly also Qualifications? Not needed. We must not repeat job title as heading. No Job ID. We must preserve all substantive information; do not invent or summarize away detail. Must keep details. We need to format using

for each section heading, then content: use

for prose,

• for any list of duties/requirements/benefits. We need to extract lists. Let's parse content. About the role: combine About Us and About The Role paragraphs. About Us: "STACK is a leading provider of cloud-based construction estimating and takeoff software solutions, committed to helping businesses transform through innovative solutions. We pride ourselves on fostering a collaborative, dynamic environment where team members have the opportunity to grow and make a real impact." About The Role: "STACK is hiring a Vice President of Corporate Development & Strategic Partnerships to lead the company’s growth strategy, with a primary focus on M&A, strategic partnerships, and corporate development. This leader will own the full corporate development lifecycle—from defining STACK’s acquisition strategy and building a pipeline of potential targets to evaluating opportunities, leading diligence, structuring transactions, and supporting post-acquisition integration. You’ll work closely with STACK’s executive team, Board, Product, Engineering, Finance, and Legal teams to determine where acquisitions can accelerate the company’s product roadmap, expand into adjacent markets, add strategic capabilities, or strengthen STACK’s position within the construction technology ecosystem. Strategic partnerships will remain an important part of the role, particularly where partnerships can serve as an alternative to acquisition, create strategic optionality, or deepen STACK’s presence across the contractor workflow. However, corporate development and M&A will be the primary focus and the primary measure of success." We'll put that as prose under About the role. Responsibilities: from "What You'll Do". It has two subheadings: Corporate Development & M&A and Strategic Partnerships, each with bullet-like sentences. We need to turn into
  • . We'll preserve each sentence as list item. Let's list them: Corporate Development & M&A: - Develop and own STACK’s corporate development and M&A strategy, identifying where acquisitions and strategic investments can accelerate the company’s long-term growth. - Build and continuously manage a pipeline of acquisition targets across construction technology, vertical SaaS, workflow software, AI, data, and adjacent markets. - Proactively source opportunities through relationships with founders, executives, investors, private equity and venture firms, bankers, and industry leaders. - Lead the end-to-end M&A process, including target identification, initial evaluation, financial modeling, valuation, business cases, diligence, negotiation, transaction structuring, and closing. - Develop investment theses and present acquisition recommendations, risks, valuation considerations, and strategic rationale to STACK’s executive leadership and Board. - Lead build-vs-partner-vs-buy analysis for new products, capabilities, technologies, and market expansion opportunities. - Coordinate cross-functional diligence across Product, Engineering, Finance, Legal, Sales, Customer Success, and other stakeholders. - Partner with Product and Engineering leadership to assess technology, product fit, intellectual property, talent, and integration considerations. - Develop integration strategies and success metrics before transactions close, ensuring acquisitions translate into measurable product, financial, customer, and organizational outcomes. - Maintain a strong understanding of the competitive landscape and emerging companies that could represent future acquisition, investment, or strategic opportunities. Strategic Partnerships: - Identify strategic partnerships that complement STACK’s M&A strategy and extend the company’s position within the construction technology ecosystem. - Develop relationships with construction software platforms, ERP and accounting providers, financial technology companies, materials and equipment providers, and other strategic players. - Evaluate when STACK should build, partner, invest, or acquire to address a strategic opportunity. - Structure and negotiate strategic agreements, integrations, commercial relationships, and other transactions that create long-term value for STACK. - Develop relationships with executives across the construction and technology ecosystem that can create future partnership, investment, or acquisition opportunities. We'll combine into one list maybe, but could separate with subheadings? Not required; just list. Requirements: from "What You Bring". It's a list of bullet points preceded by numbers. We'll turn each into
  • . List: - 10+ years of experience in corporate development, M&A, strategic investments, private equity, venture capital, management consulting, or a combination of these areas. - A demonstrated track record of sourcing, evaluating, negotiating, and executing acquisitions or strategic investments, specifically within the construction technology space. - Experience owning or playing a significant role across the full transaction lifecycle, including valuation, financial modeling, diligence, negotiation, transaction structuring, and integration planning. - Strong financial and analytical capabilities, with the ability to independently build and defend acquisition models, valuations, business cases, and investment recommendations. - Experience developing acquisition theses, evaluating markets, and identifying targets proactively rather than relying solely on banker-led processes. - Strong understanding of SaaS business models and the strategic and financial drivers behind software acquisitions. - Experience partnering with Product and Engineering teams to evaluate technology businesses and determine product and technical fit. - Excellent executive communication skills, with the ability to present complex transactions and strategic recommendations clearly to executives and Board members. - A builder’s mindset—you’re comfortable establishing STACK’s corporate development strategy, processes, pipeline, and operating cadence from the ground up. We could also include "How Success Is Measured" as maybe Requirements? But it's about success metrics; we could treat as Qualifications? But we already have Requirements; we could add a Qualifications section for success metrics? However instruction: prefer few sections. Might combine Success metrics into Requirements? But they are not requirements; they are how success measured. Could be separate section Qualifications? Not sure. Let's keep Requirements as above, and maybe add a Qualifications section for "How Success Is Measured"? But that seems like metrics not qualifications. However we could treat as Qualifications (what qualifies for success). But the instruction says only include if real specific content. We have content for How Success Is Measured. Could make a section Qualifications (or maybe "Success Metrics") but not in allowed headings list. Allowed headings: About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. So we could put How Success Is Measured under Qualifications. That seems plausible: qualifications for success. Let's do that. Thus Qualifications section content: list of success metrics. List: - A clearly defined and executive-aligned M&A strategy and acquisition thesis tied to STACK’s product and company growth priorities. - A strong, continuously developing pipeline of qualified acquisition and strategic investment opportunities. - Successful execution of acquisition processes from sourcing through diligence, negotiation, closing, and integration planning. - High-quality financial models, valuation analyses, investment cases, and recommendations that support executive and Board decision-making. - A documented build-vs-partner-vs-buy framework for key adjacent markets and product opportunities. - Successful post-acquisition integration with measurable product, customer, revenue, and organizational outcomes. - Strategic relationships across construction technology, vertical SaaS, private equity, venture capital, investment banking, and the broader M&A ecosystem. We'll put as
    • . Skills: we could extract skills from What You Bring that are not already covered? But we already have Requirements covering experience and capabilities. Skills could be things like financial modeling, valuation, negotiation, communication, etc. But to avoid thin sections, maybe we omit Skills. Benefits: from "Why Join STACK?" and compensation bullet: "This role is eligible for health insurance (medical, dental & vision), life insurance, 401(k) & paid time off." Also the values and culture: remote-first, async-friendly, etc. Those could be benefits or schedule. We'll put benefits: health insurance, dental, vision, life insurance, 401(k), paid time off. Also maybe mention "Opportunity to work in a fast-paced, growth-oriented, remote-first environment. Async-friendly environment with a focus on ownership and deep work. Be part of a dynamic, supportive team where your contributions are valued." Those are more about work environment; could be benefits or schedule. We'll keep them under Benefits as prose maybe. Pay: compensation range: "$165k-200k USD + commission/bonus." Also note about discretion. Schedule: remote-first, async-friendly environment. Could be schedule. We'll output HTML fragment with sections in order: About the role, Responsibilities, Requirements, Qualifications, Benefits, Pay, Schedule. Each section:

      Heading

      then content. For lists:
      • ...
      . For prose:

      ...

      . We must not include any extra text like explanations. Let's craft. About the role: combine two paragraphs into one

      maybe two

      s? Could be one

      with both sentences. We'll do two

      for readability. Responsibilities:

      with items. Requirements:
      with items. Qualifications:
      with items. Benefits: we have prose about culture and list of benefits. Could do

      for culture then

      for benefits. Pay:

      with compensation range and note. Schedule: <