Head of Partnerships

We need to output HTML fragment with sections: About the role (already present), Responsibilities (What You Will Do), Requirements/Qualifications/Skills (Who You Are), Benefits, Pay, Schedule (if present). The posting includes "Compensation And Benefits" with details: On-target earnings: $220,000 (base salary plus variable), Base salary: $150,000, Full-time, on-site role in New York with heavy travel, Benefits list. Thus we have Pay (compensation) and Benefits sections. Schedule? Not explicit schedule beyond full-time, on-site, heavy travel. Could infer schedule: Full-time, on-site, heavy travel. But we should only create Schedule section if posting actually states schedule details. It says "Full-time, on-site role in New York with heavy travel". That's schedule info. Could put under Schedule section. However guidelines: only include section when posting has real, specific content for it. It does have schedule info. So we can include Schedule. We must not repeat job title as heading. No Job ID. Remove boilerplate. We need to preserve all substantive information. So we need to include About Revin? The instruction: "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." The "About Revin" is introductory company description. Should we include it? It's substantive. The instruction says we should reformat a job posting into clean HTML. Likely we should include About Revin as a section? The allowed headings list includes About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule. It does not list "About the company". But we could treat "About Revin" as part of About the role? Not exactly. However we could include it as a

before sections, not as a heading. The instruction: "Use

for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule)." It gives examples but not exhaustive. It says "include a section ONLY when the posting has real, specific content for it". So we could have a heading like "About Revin" if we want, but not in the list. Safer to follow the given examples; maybe we should not create a heading for About Revin, but we can include that content in a

before the first heading. The instruction: "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." So we can put About Revin as a

(or maybe as a

"About Revin"? Not in list). I'd treat it as a

preceding sections. Thus output:

About Revin ...

Then

About the role

with paragraph. Then

Responsibilities

with

• items from "What You Will Do". Then

  Requirements

  (or Qualifications/Skills) with "Who You Are" bullet points. We could combine Requirements and Qualifications into one section? The instruction says prefer few substantive sections over many thin ones. Could make a single "Qualifications" section with bullet points. But we have separate headings list: Requirements, Qualifications, Skills. We could choose one heading that best fits. Since the content is about experience, traits, etc., we could use "Qualifications". Let's use

  Qualifications

  . Then Benefits:

  Benefits

  with
  . Pay:

  Pay

  with

  containing compensation details. Schedule:

  Schedule

  with

  containing full-time, on-site, heavy travel. Make sure not to include filler like "commensurate with experience". Not present. We must preserve all substantive information: include details about Revin's mission, customers, revenue, investors, etc. That's in About Revin paragraph. Also include details about the role: "We are hiring a Head of Partnerships..." etc. Responsibilities list: Build Revin's presence inside private equity..., Own the industry-group and association map..., Run the mastermind and peer-group circuit..., Own our conference strategy..., Generate qualified pipeline..., Carry and hit a pipeline and influenced-revenue quota..., Be the connective tissue..., Represent Revin as a face... We need to capture each bullet as

  • . Qualifications list: 5+ years..., A genuine connector..., A natural relationship-builder..., Quota-carrying..., A strong communicator..., Willing to travel heavily..., An entrepreneurial builder..., Excited about applying AI..., Don't Work Here If... (these are negative statements). Should we include the "Don't Work Here If" as part of qualifications? It's more about disqualifiers. Could include as a separate
    maybe under "Who You Are" but we can incorporate as bullet points as well. The instruction: preserve ALL substantive information. So we should include those disqualifier bullets as part of qualifications section (maybe as a separate list titled "Not a fit if"?). But we can just include them as bullet points under Qualifications as well, but maybe better to separate as "Not a fit". However we only have headings list; we could add another heading like "Not a fit" but not in list. Safer to include them as part of Qualifications but maybe label them? Could add a

    preceding them: "Not a fit if you:" then list. That preserves info. We must not invent or summarize away detail. So keep exact phrasing where possible. Let's extract exact text. About Revin paragraph: "About Revin At Revin, our mission is to bring super intelligence to the built world. Millions of operators across Home Services, Construction, and Remodeling have been overlooked by the last wave of technology. We believe AI is the most transformational platform change in history, but the hard work lies in thoughtful, context-aware applications of this technology to the real world. Revin provides operators with an end-to-end system of intelligence to automate and scale revenue. Our modular suite of products includes Scheduling, Appointment Management, Membership Management, Inside Sales, Revenue Capture, Marketing, and Funnel Optimization. Today, over $2.3B in revenue runs on Revin, making us the number one AI partner for enterprise operators. Our customers include Sears Home Services ($800M), Astara Capital ($700M), Del Air ($150M), Long Home Remodeling ($150M), ImproveIt Remodeling ($100M), Sage Home ($80M), and more. We have raised $10M from top investors including Stellation Capital, 1Sharpe, Gokul Rajaram, Russ Heddleston, Michael Werner, Tandem, Max Branzburg, and Marc Bhargava." We need to keep that as a paragraph. About The Role heading: we will not repeat job title; we will have

    About the role

    then paragraph: "We are hiring a Head of Partnerships to own the top of our funnel through relationships. This is not a technical or integrations role. You will not be wiring up software. You will be opening doors, into private equity firms and their portfolio companies, industry trade associations, executive peer and mastermind groups, and the conference circuit that our enterprise operators live in. Home Services is a relationship business. The best operators trust the people in their networks far more than any ad or cold email. Your job is to make Revin the name that gets passed around those rooms, and to turn that trust into a durable, compounding pipeline of enterprise opportunities. This is a senior individual-contributor seat for a natural rainmaker. You win by being genuinely connected and genuinely helpful, not by dialing for dollars. If you are the person others call when they want an introduction, this is your role." Responsibilities: "What You Will Do" bullet points: - Build Revin's presence inside private equity. Develop relationships with PE firms investing in Home Services, HVAC, Roofing, Home Improvement and become the AI partner they point their portfolio companies to. - Own the industry-group and association map. Get Revin into the trade associations, franchise networks, and buying groups where our operators gather, and turn those affiliations into a warm-intro engine. - Run the mastermind and peer-group circuit. Embed in the executive mastermind and peer groups where operators trade advice, and make Revin a trusted, recurring part of those conversations. - Own our conference strategy. Decide which events matter, show up where our buyers are, and turn every conference into a pipeline of qualified relationships, not a stack of business cards. - Generate qualified pipeline. Convert relationships into sourced, sales-qualified opportunities and hand them to our closing team with the context and trust already built. - Carry and hit a pipeline and influenced-revenue quota. - Be the connective tissue of our go-to-market. Feed the market intelligence you gather back into product, marketing, and sales so the whole company gets smarter about who we sell to and how. - Represent Revin as a face of the company. You will often be the first impression an operator, investor, or industry leader has of us. You carry the brand with credibility and warmth. We need to keep each as
    • . Qualifications: "Who You Are" bullet points: - 5+ years in a relationship-driven go-to-market, business development, or strategic partnerships role, ideally selling into or partnering with enterprise operators, PE-backed businesses, or a specific industry vertical - A genuine connector with an existing network. You already know people in private equity, industry associations, or the Home Services / Roofing / Home Improvement / HVAC world, or you have a proven track record of building networks like this from scratch. - A natural relationship-builder who is trusted quickly and remembered warmly. People take your call and take your intro. - Quota-carrying and accountable. You are comfortable owning a number and being measured on the pipeline and revenue your relationships create. - A strong communicator and presence in a room. Polished on a conference stage, credible across the table from a PE partner, and warm one-on-one at a dinner. - Willing to travel heavily. You will be on the road at conferences, PE offices, and industry events as much as you are in New York. - An entrepreneurial builder who wants to define a function, not inherit a playbook - Excited about applying AI to the built world and able to tell that story with conviction to a non-technical audience Then "Don't Work Here If You are a technical or integrations-partnerships person looking to manage software alliances. This is a relationship and pipeline role. You wait for leads to be handed to you instead of building your ownYou want a safe, predictable 9-5. Expect long days, heavy travel, and a fast pace. We are looking for fanatics who do not turn off. We are constantly chasing excellence, if that is not your goal, please do not apply. You are not excited about being part of a team applying AI into the built world. There will be no playbook, if you want a well-trodden path, this is not the role for you." We need to preserve that as well. Could be a separate

      Not a fit

      but not in list. Maybe we can incorporate as a

      under Qualifications with a note "Not a fit if:" then list. But the instruction says prefer few substantive sections over many thin ones. Could add a

      Not a fit

      but that's not in the examples; risk of being considered invented heading. Safer to include as a

      after Qualifications, maybe with a heading like

      Not a fit

      but risk. However the instruction says "Use

      for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay,