Jobs · Business Development · California

Co-Founder & CEO - AI Healthcare Revenue Recovery

FutureSight · San Francisco, CA · 1 mo ago
Business Development$50k–$300k/yrPart-time
We need to output HTML fragment with sections: h3 headings for sections present. We must not repeat job title. No Job ID. Remove boilerplate like application instructions, EEO, etc. Must preserve substantive info. We need to identify sections: About the role? The posting includes "The Opportunity" description, "Market Context", "About FutureSight", "The Partnership", "What You’ll Own As Co-Founder & CEO", "Co-Founder Profile". Also maybe "How to Apply" but we should drop application instructions. Also "FutureSight is committed to diversity..." is EEO boilerplate, drop. We need to use

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

    for prose. We need to include sections only when posting has real specific content. We need to preserve all substantive info, not invent or summarize away detail. So we need to keep details like market size, numbers, quotes, etc. We need to format content accordingly. Let's parse sections: - The Opportunity (intro): description of venture, co-founder partnership, market size, problem stats, Reclaim AI solution, etc. Could be a section "About the role" maybe? But we have no explicit heading; we can create a heading like "About the role" if content fits. The instruction: use

    for section headings (e.g. About the role, Responsibilities, Requirements, Qualifications, Skills, Benefits, Pay, Schedule). So we should map content to these standard headings where appropriate. However we should only include a heading if the posting has real specific content for it. So we need to decide which standard headings match. We have content about the role: description of what you'll own, responsibilities, etc. That could go under "About the role" or "Responsibilities". The "What You’ll Own As Co-Founder & CEO" section lists responsibilities: Strategy, Customer Development, Product, Capital, Team. That's basically responsibilities. So we could put that under

    Responsibilities

    with a
    • list. We also have "Co-Founder Profile" which is qualifications/requirements/skills. Could be under

      Requirements

      or

      Qualifications

      or

      Skills

      . The list includes domain experience, founding experience, B2B AI/SaaS go-to-market, fundraising fluency, talent attraction, understanding risks. That's qualifications. So we can put under

      Qualifications

      with a
        . We have "About FutureSight" describing the venture builder. That could be under

        About the role

        ? Actually "About the role" is about the role, not about the company. But we have no standard heading for "About the company". However we could put under

        About the role

        maybe not ideal. The instruction says use those headings for section headings (e.g. 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). Likely they expect us to use those headings where appropriate. For company description, maybe we can put under

        About the role

        but that seems odd. Alternatively we could omit that section if not matching any heading? But we must preserve ALL substantive information; we cannot drop company description. So we need to fit it into one of the allowed headings. Perhaps we can treat it as "About the role" (the role includes working with FutureSight). Or we could create a custom heading? The instruction says use those headings for section headings (e.g. ...). It doesn't explicitly 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 for sections. Probably we should map content to those headings as best as possible. Thus we could have:

        About the role

        containing description of the opportunity, market context, FutureSight description, partnership details.

        Responsibilities

        containing the bullet list of what you'll own.

        Qualifications

        containing the co-founder profile bullet list. We should not include Benefits, Pay, Schedule because not specified. We need to ensure we don't include filler like "commensurate with experience". Not present. We need to preserve all substantive info: numbers, quotes, etc. We need to format lists with
        • . For prose, use

          . We need to drop application instructions and EEO. Let's extract substantive paragraphs: From "The Opportunity FutureSight is seeking a Co-Founder & CEO to lead Reclaim, an AI-native denial management and revenue recovery venture. This is a co-founder partnership with meaningful founder equity, not a salaried executive role. We are entering a $16B+ Total Addressable Market with a gaping $ 7.5B–$10B whitespace, targeting the highly underserved mid-market segment. Currently, 30–40% of denied medical claims go uncontested because practices lack the staff and capital to contest them. This systemic failure leaves between $50,000 and $300,000 in legally earned revenue permanently abandoned at each practice every year. Reclaim AI resolves denied and aged claims end-to-end, embedding outcome-based contingency pricing—meaning practices pay zero upfront, and we only take a cut of the dollars we successfully recover, for our target ideal customer profile (practices with $80K+ in annual recoverable claims)." Then "Market Context We Didn’t Just Read Market Reports; We Spent Weeks Interviewing Billing Managers, Practice Owners, Revenue Cycle Leaders At Health Systems, And Even Digital Operations Leaders At Major Insurance Companies. The Dysfunction We Uncovered Is Staggering, Creating a Massive Opportunity For a Disruptor The pain is so severe, practices are building their own tech: The frustration of payer opacity is so deep that medical billers are hiring part-time software engineers to build in-house robotic process automation (RPA) scrapers just to check claim statuses.Massive, emotional write-offs: Staff carry immense guilt over these administrative losses. One small-practice assistant admitted, "I feel like we probably had to write off probably close to a million dollars" simply because they couldn't keep up with the manual follow-ups.The "Payer-Side Inversion" Opportunity: We discovered that insurance companies are drowning in the exact same claims dysfunction they generate. One major payer we interviewed reported a backlog of 31,000 contested claims that consumed 80% of their staff's operational capacity, forcing emergency hires just to manage the disputes.The Competition is Distracted: Well-funded Tier-1 competitors are charging $15K+ upfront licensing fees and fighting over enterprise health systems. The competitive window to capture the mid-market with a contingency-priced autonomous agent is wide open." Then "About FutureSight FutureSight is a leading venture builder that co-creates world-class software companies with values-driven entrepreneurs from inception to exit. We are a team of founders, operators and designers with experience successfully bringing software to market at scale. You’ll co-create with a proven studio team, led by John Carbrey (4x entrepreneur, $100M ARR), Krista LaRiviere (3x exited, E&Y Top Women Entrepreneur), Alan Smith (Strategyzer co-founder, $120M in products built), Prathna Ramesh (former MD of Maple Leaf Angels, $275M in follow-on capital), and Johnny Tong (0-to-1 builder, acquired by SAP and Stripe) bring a rare combination of operator exits, institutional investing, and AI product depth." Then "The Partnership Founder equity with meaningful ownership from inceptionPre-seed capital committed by FutureSight for early hires and MVP development, with potential for follow-on fundingVenture building resources, including embedded design, engineering, growth, and fundraising support from day oneInvestor and advisor network across vertical AI and early-stage capital marketsA true co-creation model in which you operate as CEO with FutureSight's cross-functional team as your partner" Then "What You’ll Own As Co-Founder & CEO, you will set the venture's direction and lead its execution. Strategy — Refine the ICP, pricing model, and product positioningCustomer Development — Lead pilots with practice owners and revenue cycle leaders, convert them to paid engagements, and build the go-to-market motionProduct — Partner with the FutureSight product and engineering team to ship V1 and iterate on user feedbackCapital — Lead the seed raise, supported by FutureSight's network and tractionTeam — Recruit and lead the founding team, and establish the cultural foundation of the company" Then "Co-Founder Profile Domain & Workflow Depth: You have direct exposure to healthcare revenue cycle, medical billing, or denial management. You understand the nuanced differences in denial codes, know why administrative denials (like credentialing gaps) are uniquely painful, and intuitively understand the fragmented systems (e.g., Tebra, eClinicalWorks, Availity) that billers are forced to usePrevious founding experience at a venture-backed companyDemonstrated success in B2B AI or B2B SaaS go-to-market, including sales and customer engagementFundraising fluency, with the ability to develop investor narratives and close capitalProven ability to attract, develop, and retain top talentClear-eyed understanding of the risks and demands of co-founding a venture-backed company" We need to turn these into HTML. We'll have:

          About the role

          ... (combined opportunity, market context, about FutureSight, the partnership) ...

          But we might split into multiple

          paragraphs for readability. We need to preserve all details, so we can keep them as separate paragraphs. We must not include application instructions or EEO. Let's craft. First paragraph: The Opportunity description. Second paragraph: Market Context. Third paragraph: About FutureSight. Fourth paragraph: The Partnership. Then Responsibilities: list. Then Qualifications: list. Make sure to not duplicate lines. Let's write. Check for any boilerplate: "FutureSight is committed to diversity, equity, and inclusion. We welcome applicants of all backgrounds and experiences." Drop. Also "How to Apply Please submit your resume, LinkedIn profile, and a brief note on why this venture aligns with your goals as a founder. We will move quickly for the right candidate." Drop. Now produce HTML. Be careful to escape any internal quotes? The quoted statement includes double quotes inside. We can keep as is; HTML can handle. We'll output:

          About the role

          The Opportunity FutureSight is seeking a Co-Founder & CEO to lead Reclaim, an AI-native denial management and revenue recovery venture. This is a co-founder partnership with meaningful founder equity, not a salaried executive role. We are entering a $16B+ Total Addressable Market with a gaping $ 7.5B–$10B whitespace, targeting the highly underserved mid-market segment. Currently, 30–40% of denied medical claims go uncontested because practices lack the staff and capital to contest them. This systemic failure leaves between $50,000 and $300,000 in legally earned revenue permanently abandoned at each practice every year. Reclaim AI resolves denied and aged claims end-to-end, embedding outcome-based contingency pricing—meaning practices pay zero upfront, and we only take a cut of the dollars we successfully recover, for our target ideal customer profile (practices with $80K+ in annual recoverable claims).

          Market Context We Didn’t Just Read Market Reports; We Spent Weeks Interviewing Billing Managers, Practice Owners, Revenue Cycle Leaders At Health Systems

Similar jobs