Project Management & Delivery
• Own project plans, timelines, and trackers across multiple concurrent workstreams, holding the single source of truth on what is happening, who owns it, and when it is due
• Run the operating cadence that keeps work moving: status updates, check-ins, risk flags, and dependency management, so nothing stalls quietly
• Keep cross-functional projects coordinated and unblocked across Clinical Operations, Finance, IT, People Operations, and external vendors
• Build repeatable playbooks for recurring project types (new-market launch, center buildout, clinic integration, vendor onboarding) so each one runs faster and cleaner than the last
• Be the person leadership trusts with ambiguous, time-bounded asks: the kind of project where someone says “can you figure this out by Friday” and it actually gets figured out
New-Market Launch & Market Operations
• Serve as the execution arm for the Implementation Director who owns a market’s P&L and operations: turn their priorities into tracked workstreams and drive the tactical work to done
• Help bring the first center in a new market online by coordinating real estate and buildout operations: landlord and contractor coordination, permits and occupancy, furniture and equipment procurement, signage, IT, phones, internet, and supplies, so the center is ready for kids on schedule
• Support hiring the first clinicians and clinic leadership in a new market: post roles, coordinate interview scheduling and candidate communications, manage offer logistics, and run a clean onboarding, including license and credentialing setup
• Round out the contracts and vendor agreements a new market needs but does not yet have in place, and keep them organized, tracked, and renewed
• For acquisitions, own the integration mechanics: EMR migration, HRIS and ATS setup, Microsoft 365 and email provisioning, credentialing and payer transitions, state-specific compliance filings, and harmonizing the acquired team’s policies and SOPs to ANNA’s
• Support the ongoing operations of live markets: keep licensing and credentialing current, manage vendor and contract renewals, track operational metrics, and chase the long tail of recurring items so nothing slips through the cracks
The Broad Bucket of Operations
• Take on operational projects that do not yet have a clear owner: vendor onboarding and license tracking, internal comms support, document and SOP cleanup, ad-hoc research, and similar connective-tissue work that keeps a fast-growing, multi-state company running
• Partner with Clinical Operations, Finance, IT, and external vendors so operational processes plug cleanly into adjacent systems and do not create downstream rework
• Pull together clean research, analysis, and options when leadership needs a decision supported quickly
Executive Leverage (Right Hand to the CEO)
• Translate the CEO’s priorities into tracked, driven workstreams with clear owners, dates, and status, then own the follow-through until they close
• Prep the CEO and the Implementation Director for the week and key meetings: pre-reads pulled together, materials in the right place at the right time, action items captured and chased to done
• Build the trackers, dashboards, and lightweight reporting that let leadership see status at a glance instead of asking
• Provide light coordination and scheduling support on the projects you own, with the judgment to know what to handle, what to surface, and what to deflect
AI-Native Workflow Building
• Use Claude daily as your primary thinking, drafting, and execution partner: project plans, status updates, research, summaries, comms, and data cleanup
• Build Claude Projects, Cowork workspaces, and reusable prompts and skills that codify how recurring execution work gets done at ANNA: launch playbooks, center-opening checklists, integration playbooks, vendor tracking, and project reporting
• Identify manual or repetitive steps in our processes and replace them with well-scoped automations using Claude, MCP servers, Asana, SharePoint, and our other systems
• Document every workflow you build so anyone on the team can run it; treat the workflow library as a product you own and improve over time