Partner revenue is up more than tenfold in two years and Suki is hiring a Platform AE and a head of platform products to grow it. Yet a builder who clicks "Request API Access" on the For Partners page lands on a docs overview; the docs then say credentials cannot be self-provisioned and link to the general contact page, whose form promises a call from "our Sales team". The best-documented part of Suki (503 doc pages, llms.txt, MCP) ends in the least specific form on the site.
First action
Repoint both "Request access" buttons and the docs onboarding link to a dedicated partner form.
How to measure it
Partner access requests routed to the Platform AE
- Now
- –
- Target
- 25 a month
- By
- 90 days
Steps
Map the path
Click every partner call to action on www and the docs and record where each lands.
Senior Director, Platform Products 1 day
Write the form
Use the onboarding inputs: product type, use case, platforms, auth method, volume.
Senior Director, Platform Products 2 days
Build and route
Form on /partners; requests go to the Platform AE and partnerships, not the general queue.
Marketing Operations 3 days
Relink the docs
Partner Onboarding and quickstart pages point to the new form.
Developer documentation owner 1 day
Auto-reply
Send the onboarding checklist and the quickstart that matches the use case.
Marketing Operations 1 day
Speed target
First human reply within one business day.
Senior Platform Account Executive ongoing
Measure
Requests, meetings and signed partners by source page.
Marketing Operations monthly
Why it works
Build one partner access form that both "Request access" buttons and the docs onboarding page point to. Ask what the partner integrators need for onboarding anyway: product type (EHR, telehealth, care management, revenue cycle), use case (ambient, dictation, form filling), target platforms and expected users. Route it straight to the Platform AE and partnerships, send an automatic reply with the onboarding checklist and the right quickstart, and add a "Talk to a platform engineer" option for teams already reading the docs.
Developers who have read the docs are the warmest partner leads Suki gets; asking the right questions up front shortens onboarding and gives the Platform AE qualified meetings instead of generic inquiries.
Ready to use
ChecklistPartner access form fields
[ ] Company and product type (EHR, telehealth, care management, revenue cycle, other) [ ] Use case: ambient, dictation, form filling, patient summary [ ] Platforms: web, mobile, backend [ ] Identity provider and auth method (OAuth 2.0 / OIDC with JWKS) [ ] Expected clinician users in year one [ ] Timeline to launch [ ] Technical contact [ ] Routed to Platform AE within one business day
Risks and how to handle them
More unqualified requests
Qualifying questions on the form and a short review by Sales Development.
Clinicians use the partner form by mistake
A clear line pointing practices and health systems to the main contact form.
Evidence
- Your websiteFor Partners page: two developer options with buttons "Request SDK Access" and "Request API Access"; both buttons link to overview pages on developer.suki.ai rather than to a request form. The page names HealthEdge, Zoom, Sevocity and WellSky partnerships and quotes Azalea Health and MEDENT.Source
- Developer docsdeveloper.suki.ai has 503 pages in its sitemap, an llms.txt index, an AI docs assistant and an MCP reference. Its Partner Onboarding page says: "You cannot self-provision credentials. To get started, contact the Suki Partnerships team", and links to the general www.suki.ai/contact-us/ page.Source
- Your websiteContact page: one form for everyone, introduced with "Complete the form, and someone from our Sales team will get back to you shortly."; existing customers are pointed to 24-hour support and the Help Center.Source
- HiringSenior Platform Account Executive (remote US, posted October 14, 2026): grows the Suki Platform business with "strategic partners who can leverage Suki's powerful AI platform"; works "closely with Marketing & Sales Development on campaigns to target new potential partners"; experience selling into "Care/Case Management/Delivery or Revenue Cycle Management/Payer organizations" is preferred. The post says Suki has "raised $255M to date".Source
- HiringSenior Director, Platform Products (posted October 5, 2026): owns "the developer platform and partner integration strategy, including APIs, SDKs, documentation, and developer experience", EHR integrations (Athena and others), FHIR/HL7 standards, and "a platform ecosystem that creates compounding value for Suki and its partners".Source
- Press releaseOctober 13, 2026: Suki announced $90 million in Series E financing. Suki "now serves more than 450 healthcare organizations" and "works with more than 30 technology partners"; encounters supported grew "more than 190% year over year in 2026"; revenue doubled in 2025; partner revenue "increased more than tenfold over the past two years".Source