Technical Account Manager (API Platform

Responsibilities

• The Synchronizer API is the strategic core of Nex Health. Hundreds of health-tech companies, from innovative venture-backed AI startups to established healthcare enterprises, are in production on it today
• The foundational work is done. What determines the revenue trajectory from here is how deeply those companies expand
• This role owns that problem. The Technical Account Manager is the primary commercial and technical relationship for the existing customer base
• The mandate is straightforward: understand what each customer is building, identify where they can go further with the API, and drive the expansion that follows. This is not a support function. It is a revenue role
• The customers you will manage span a broad spectrum of healthcare technology, including Voice AI platforms, Revenue Cycle Management tools, patient engagement products, dental and medical practice intelligence software, and practice automation companies
• The common thread is that they are all building on Nex Health infrastructure, and the depth of that relationship is largely untapped. Some key responsibilities for this role include:
• Own revenue expansion for the existing customer base. Your primary metric is net revenue retention. You are accountable for growing the book, not just protecting it
• Drive multi-location growth. The largest expansion lever in the business is moving customers from one or two locations to ten, fifty, or more. You understand each customer’s footprint, their growth trajectory, and the conversation that closes the next tier
• Identify and close upsell and cross-sell opportunities. Customers using one part of the API are often a fit for more. You know the product well enough to recognize the gap and make the case
• Serve as the primary technical relationship for your accounts. You are the person customers call when something is not working, when they are planning a new integration, or when they want to understand what is possible. You do not replace engineering support, but you own the relationship that makes it productive
• Surface expansion-blocking issues and resolve them. Churn starts before it shows up in the data. You identify accounts where usage has plateaued, engagement has dropped, or a technical blocker is preventing growth, and you act before it becomes a loss
• Manage a named account portfolio. You own a defined set of active customers. You know their integration depth, their business model, their growth plans, and the decision-makers on their team
• Run regular business reviews. Structured check-ins that cover usage trends, expansion opportunities, and roadmap alignment. These are revenue conversations with a technical backbone
• Build and execute expansion plans by account. For each account, you maintain a view of current ARR, potential ARR, and the specific actions required to close the gap
• Work closely with Engineering and Solutions Engineering on complex technical questions. When a customer needs architectural guidance, you facilitate it. You stay in the commercial driver’s seat
• Coordinate handoffs with the sales team. When an existing customer has a need that looks like a new logo opportunity (a subsidiary, a new product line, a partnership), you connect the right people
• Keep the CRM current and the forecast accurate. Expansion pipeline, renewal risk, and account health are tracked and reported. The business makes investment decisions based on what you report
• You are the continuity in the customer relationship. Sales closes the initial deal. You own everything after that, including the next three
• You operate at the intersection of commercial and technical. You are not an engineer, but you are fluent enough to have a real conversation about an API integration, a webhook architecture, or a production issue. You know when to bring in deeper technical resources and how to translate between them and the customer
• You work proactively, not reactively. Expansion does not happen because customers ask for it. It happens because you identified the opportunity, built the case, and ran the conversation
• You build, not just manage. The playbook for technical account management in this business does not fully…