Senior Practice Launch Manager

About the job Level: Senior Manager / Director-level individual contributor Reports to: Foundry Leadership Location: Remote Employment type: Full-time People management: None initially; leads cross-functional launch teams and may help build the future launch organization About Bioscope Foundry Bioscope Foundry helps physicians create and operate independent medical practices. Foundry combines practice design and launch support, business and technology infrastructure, vendor coordination, operational services, and FoundryOS—the platform used to coordinate launch work and support clinical and administrative operations. The Role The Senior Practice Launch Manager is the single-threaded owner of each assigned physician-practice launch. The role takes an approved practice plan from commercial and compliance clearance through legal formation, operational setup, technical provisioning, launch readiness, go-live, and early stabilization. This is not a status-reporting or PMO-only role. It is a senior, hands-on individual-contributor position for someone who can manage physicians, vendors, internal specialists, and complex dependencies while also configuring systems, testing workflows, resolving operational problems, and producing the documentation needed to launch safely. The right person can move comfortably between a physician strategy discussion, a licensing or credentialing blocker, a vendor escalation, a DNS or Google Workspace configuration, a FoundryOS workflow, and an end-to-end patient-journey test. Approximately 50–60% of the role should be direct execution and troubleshooting rather than meetings and coordination. Core Responsibilities 1. Own the Practice Launch from Plan to Go-Live Serve as the accountable launch owner for each assigned practice from handoff through go-live and the initial stabilization period. Convert the physician’s approved practice plan into an executable launch plan with milestones, dependencies, owners, target dates, evidence requirements, and escalation paths. Maintain the critical path across legal, compliance, finance, marketing, technology, clinical operations, vendors, and physician-owned actions. Operate the Launch Ops workspace in FoundryOS/Conductor, including workstreams, tasks, blockers, evidence, vendor inventory, account custody, action items, readiness status, timelines, and launch records. Manage multiple practice launches concurrently without losing task ownership, documentation quality, or physician responsiveness. 2. Guide Physicians Through Practice Design and Entrepreneurial Decisions Translate the physician’s clinical vision into an actionable operating model, including virtual, hybrid, or in-person delivery; service mix; membership, cash-pay, or hybrid economics; panel assumptions; hours; staffing; patient access; and operating workflows. Help physicians make timely decisions about practice name, brand, patient experience, services, pricing inputs, technology, vendors, and launch sequence. Set clear expectations for physician-owned actions, deadlines, document requests, approvals, and account custody. 3. Coordinate Legal Formation, Licensing, Credentialing, and Compliance Coordinate physician-practice entity formation through approved legal and formation partners, including formation filings, EIN acquisition, and required supporting records. Coordinate the approved PC/PLLC, MSO, ownership, contracting, and practice-formation workflow without independently providing legal advice. Track NPI, state licensure, DEA, controlled-substance posture, sanctions and exclusion checks, credentialing, payer or vendor enrollment where applicable, laboratory account requirements, and other launch-critical approvals. 4. Set Up Financial and Commercial Infrastructure Coordinate business bank-account setup and confirm authorized ownership and custody. Set up or coordinate accounting software, payment rails, Stripe, and other approved financial systems. Track startup costs, vendor commitments, deposits, recurring expenses, and practice-specific commercial assumptions against the approved plan. 5. Build the Practice’s Core Technology and Digital Infrastructure Register or transfer domains and configure Cloudflare DNS and related account controls. Configure Google Workspace, users, groups, administrative roles, security settings, and clinician sign-on. Configure SPF, DKIM, DMARC, and related email-deliverability controls. Set up or coordinate 1Password vaults, credential custody, least-privilege access, multifactor authentication, and secure handoff of doctor-owned assets. Configure Slack, phone, fax, secure messaging, and other communications systems. Set up the approved website, social profiles, local listings, analytics, and foundational SEO. Use AI-native design and development tools, including Claude Design/Claude Code or comparable tools, to create or modify lightweight practice websites and operational assets when appropriate; coordinate engineering review for anything production-critical. Understand APIs, webhooks, SSO, DNS, role-based access, data flows, and system integrations well enough to test, diagnose, document, and escalate problems. 6. Implement the Clinical and Practice-Operations Stack Provision the practice and physician in FoundryOS and the clinician workspace. Configure the approved EMR or clinical system, scheduling, telehealth, patient portal, secure messaging, phone, fax, record import, e-prescribing/EPCS, laboratory ordering and results, clinical documentation, AI scribe, and payment workflows. Coordinate vendor and internal integration setup, including account creation, credentialing, test environments, production enablement, and support escalation. Reproduce technical issues, collect non-sensitive diagnostic evidence, distinguish configuration problems from software defects, and work directly with Product and Engineering through resolution. 7. Own Readiness, Dry Runs, Cutover, and Go-Live Maintain an evidence-based launch-readiness record rather than relying on verbal confirmation. Verify all required legal, compliance, security, identity, storage, integration, vendor, clinical, and patient-facing gates. Confirm account custody, access recovery, auditability, backups, rollback procedures, incident contacts, and manual fallback workflows. Schedule and lead the launch-day command center or war room, assign escalation coverage, and maintain a current issue log. 8. Stabilize the Practice After Launch Remain accountable through the initial post-launch stabilization period Monitor onboarding, scheduling, communications, clinical workflows, billing and payment issues, vendor performance, and physician or staff support needs. Triage launch-related incidents and coordinate resolution across Foundry Operations, Product, Engineering, vendors, Legal, Compliance, and clinical leadership. 9. Build a Repeatable Launch System Convert each launch into improved templates, SOPs, checklists, decision guides, training materials, and automations. Identify where the operating process should remain human-controlled and where FoundryOS or an AI workflow can safely reduce manual work. Submit clear product requirements and structured software issues based on real launch friction. Track recurring vendor, physician, configuration, and system failure patterns and remove root causes. Improve launch speed without weakening compliance, evidence, security, physician ownership, or patient safety. Required Qualifications 7+ years of experience in healthcare operations, implementation, practice management, consulting, customer launch, program management, or a comparable operational role. At least 3 years working directly with physician practices, healthcare technology, an MSO, a medical group, or another regulated healthcare operating environment. Direct responsibility for opening, converting, implementing, or materially scaling multiple medical practices, clinics, or complex healthcare customers. Strong working knowledge of physician-practice operations, including patient access, scheduling, communications, documentation, prescribing, labs, payments, staffing, and support. Practical familiarity with HIPAA-sensitive operations, BAAs, user access, credential handling, audit requirements, licensing, NPI/DEA workflows, credentialing, and healthcare-vendor onboarding. Demonstrated technical fluency across SaaS administration, Google Workspace, DNS and email configuration, identity and access, payment systems, communications platforms, and integrated software workflows. Strong critical-path management, written communication, documentation, risk management, and executive-level stakeholder skills. Willingness to perform detailed individual-contributor work and remain accountable for the final result rather than only coordinating others.

Preferred Qualifications

Experience launching or managing concierge medicine, direct primary care, membership medicine, cash-pay, or hybrid independent practices. Experience in an MSO, practice-launch company, physician enablement platform, health-system implementation team, or healthcare startup. Experience with practice formation, credentialing, professional liability, lab onboarding, e-prescribing/EPCS, telehealth, patient portals, clinical integrations, revenue-cycle workflows, or physician benefits. Familiarity with platforms such as AWS, Cloudflare, Google Workspace, Stripe, 1Password, Slack, phone/fax systems, telehealth platforms, lab networks, e-prescribing vendors, and modern EMR/EHR systems. Comfort using AI tools for research, documentation, workflow automation, design, technical troubleshooting, and lightweight software or website work. Ability to read structured data, API documentation, logs, configuration files, or basic SQL queries. Software engineering experience is helpful but not required. Experience in an early-stage company where operating processes and software are being built at the same time.