Suki does not publish a current US rate card. Its public site directs prospective buyers to sales, while its terms place subscriptions and pricing in a written order form or statement of work.
A July 2025 response from Suki published by the American Psychiatric Association described per-user and consumption-based models. It did not publish dollar amounts. Buyers must confirm which model applies today.
You may see `$299` for Suki Compose and `$399` for Suki Assistant in search results. Those numbers come from dated external materials. They are not a current Suki price list or a dependable quote for today's product scope.
This guide separates verified facts from older observations. It also gives a practical way to compare subscription, usage, EHR, implementation, support, governance, and exit costs.
For switching and shortlist questions, read our Suki alternatives guide. For broader category economics, see medical scribe cost.
Suki AI Pricing at a Glance
| Question | Current public answer | What the buyer needs |
|---|---|---|
| Current list price | No public US rate card found | Written quote with product, scope, unit, and term |
| Pricing models | A July 2025 Suki response named per-user and consumption-based models | Confirm the model and denominator offered today |
| Suki Compose | Current product page describes ambient notes, dictation, commands, and coding | Price, usage, support, and transfer path in writing |
| Integrated clinician assistant | Current materials describe broader EHR-connected workflow capabilities | Included features, EHR environments, interfaces, and services |
| Trial or pilot | No standard public trial price or length found | Pilot fee, success criteria, data terms, and conversion rules |
| Contract terms | Current terms defer key commercial details to the order form or SOW | Payment, renewal, cancellation, ramp, and termination language |
This table was checked on September 19, 2026. Suki's current home page asks buyers to contact sales. Its sales form asks about the organization, clinician count, and EHR.
Those fields suggest likely scoping dimensions. They do not prove how Suki calculates price. The executed quote and incorporated documents control the commercial offer.
Why Suki Has No Single Public Price
Suki currently presents several ways to buy or deploy its technology. They range from a clinical documentation app to deep EHR workflows and developer tools. One inherited monthly figure cannot describe every path.
The current clinician product page describes pre-charting, ambient documentation, order staging, coding, patient summaries, chart questions, instructions, and voice editing.
The Suki Compose page describes an app that creates notes from ambient capture or dictation. It also describes coding support, broad EHR compatibility, and a copy-and-paste path.
Suki also markets EHR-integrated dictation separately and offers APIs and SDKs to technology partners. A buyer should identify the required product before discussing a price.
Product names alone are not enough. The same product can require different EHR environments, interfaces, clinician populations, support levels, training, and rollout services.
| Purchase surface | Publicly described job | Cost questions |
|---|---|---|
| Suki Compose | Ambient notes, dictation, commands, coding, app workflow, and EHR transfer | User price, usage, device access, templates, support, and transfer method |
| Suki for Clinicians | Documentation, reasoning, coding, orders, summaries, and EHR-connected work | Enabled capabilities, licensed roles, EHR scope, services, and support |
| Suki Dictation | Dictation inside supported EHR workflows and supported hardware | Separate or bundled license, devices, EHR build, commands, and maintenance |
| Suki for Partners | APIs and SDKs embedded in another healthcare application | Usage unit, development, support, environments, service levels, and resale terms |
Do not assume every row is available as a separate package. Ask Suki to identify the product, SKU, included capabilities, exclusions, dependencies, and commercial unit for your organization.
What the $299 and $399 Suki Figures Mean
Two numbers dominate Suki pricing results. A Health Management Academy vendor snapshot lists Suki Compose at `$299` per physician monthly and Suki Assistant at `$399`, with enterprise volume discounts.
The same Academy snapshot describes one Epic capability as coming in Q4 2024. That dates the commercial context and limits its use as current evidence.
A February 2026 University of Colorado training deck lists Suki at `$299` monthly per user. Its footnote says prices are often customized by organization, user count, and included features.
| Public reference | Displayed amount or model | How to use it |
|---|---|---|
| Current Suki site and terms | No rate card. Price belongs in the order form or SOW | Authoritative current path to a buyer-specific price |
| July 2025 Suki response published by APA | Per-user and consumption-based models, no amounts | Dated vendor statement that requires current confirmation |
| Health Management Academy snapshot | $299 Compose and $399 Assistant per physician monthly | Dated external budget context, not a current rate card |
| February 2026 training deck | $299 per user monthly with customization caveat | External educational estimate, not a seller quote |
The safest conclusion is narrow. Public historical references show that a per-clinician subscription once circulated around those amounts. They do not establish today's products, minimums, discounts, services, or contract terms.
Do not multiply `$299` or `$399` by headcount and call the result a Suki budget. Use those figures only to create a broad planning range before receiving a current written quote.
Per-User and Consumption Pricing Need Different Math
In July 2025, the APA published Suki's response to a vendor questionnaire. Suki said it offered per-user and consumption-based pricing for solo clinicians and large systems.
APA warned that vendor responses were not independently verified and might not remain current. That warning matters. Confirm availability, units, minimums, and amounts before using either model.
A per-user model needs a precise user definition. Eligible, licensed, enabled, active, concurrent, and credentialed clinicians are different denominators. Ask how part-time, temporary, trainee, support, and departing users are counted.
A consumption model needs an equally precise event definition. An encounter, ambient session, minute, note, dictation, API call, or completed submission can produce very different bills.
Ask how retries, abandoned sessions, repeated recordings, test environments, long visits, multiple notes, and regenerated outputs affect usage. Also ask whether unused commitments expire or pool across users.
For either model, calculate the base case and two stress cases. Vary adoption, encounter volume, specialty mix, seasonality, staffing, and rollout speed. A budget should survive ordinary operational changes.
Build the Total Annual Suki Cost
The recurring vendor fee is only one layer. A realistic budget includes the work required to deploy, govern, operate, renew, and eventually replace the service.
- Subscription or committed usage: products, licensed roles, minimum users, included volume, overages, environments, and term.
- Pilot: fee, participants, workflows, duration, success measures, support, data handling, and conversion credit.
- Implementation: identity, devices, EHR work, interfaces, configuration, testing, security review, training, and launch support.
- Operation: administration, template changes, support, monitoring, quality review, governance meetings, and incident response.
- Expansion: added clinicians, sites, specialties, products, environments, integrations, and premium support.
- Renewal and exit: price changes, true-ups, data return, deletion evidence, interface removal, transition support, and replacement training.
Internal labor belongs in the model. Clinical, IT, informatics, security, privacy, legal, procurement, records, billing, finance, and support teams may all contribute time.
Suki's current integration page describes bidirectional EHR work and note return. Confirm the exact interface, environments, partner fees, testing, maintenance, and customer responsibilities.
A broad integrated product may remove manual work that a cheaper subscription leaves behind. It may also require more implementation and governance. Measure both effects instead of assuming one from the price.
Normalize a Suki Quote Before Comparing Vendors
Quote comparison fails when the denominators differ. Build one comparison sheet and require every seller to use the same population, workflows, environments, term, and service assumptions.
| Dimension | Suki quote field | Comparable measure |
|---|---|---|
| Population | Eligible, licensed, enabled, active, or concurrent users | Same people, roles, locations, and ramp |
| Usage | Session, encounter, minute, note, dictation, API call, or another event | Same event definition, volume, overage, and retry treatment |
| Product scope | Compose, assistant, dictation, coding, reasoning, API, or SDK capabilities | Same required workflows with exclusions named |
| EHR scope | Named EHR, environments, interfaces, devices, and maintenance | Same production, test, transfer, and support paths |
| Services | Pilot, configuration, training, launch, support, and change management | Same implementation work and service level |
| Term | Start, ramp, renewal, increases, cancellation, and termination | Same evaluation horizon and renewal assumptions |
| Measured result | Adoption, correction, transfer, support, failures, and completion | Same representative cases and definitions |
Convert each proposal to first-year and steady-state annual cost. Then calculate cost per eligible user, enabled user, active user, completed encounter, and accepted final note where those measures apply.
Low adoption can make a discounted seat expensive. High consumption can make a low unit rate expensive. A strong workflow can justify a higher rate if the measured local work is lower.
Twelve Questions for a Suki Quote
- Which named product, SKU, capabilities, care settings, and user roles are included?
- What pricing unit applies, and how is an eligible user or consumption event defined?
- What minimum seats, committed usage, ramp, pooling, true-up, and unused-volume rules apply?
- Which ambient, dictation, editing, coding, ordering, summary, reasoning, and API functions are enabled?
- Which EHRs, versions, environments, interfaces, devices, partner licenses, and test work are included?
- What pilot fee, implementation fee, configuration, training, travel, and launch support sit outside subscription?
- What response times, service levels, named support, escalation, downtime, credits, and change services apply?
- How do added users, sites, specialties, products, languages, and care settings change price during the term?
- What renewal notice, automatic renewal, price increase, term reduction, cancellation, and early-exit conditions apply?
- What agreements govern PHI, retention, deletion, data location, subprocessors, human access, model use, incidents, and audit evidence?
- What data return, pending-note submission, account closure, interface removal, and transition assistance occur at exit?
- Which internal, EHR, partner, network, identity, device, security, records, and support costs remain the customer's responsibility?
Put the answers in the order form, SOW, or incorporated documents. Sales notes can clarify intent, but the signed agreement should control price and service.
Read Suki's Current Payment and Renewal Terms
Suki's current Terms of Service define an order form as the document setting subscriptions and pricing. A SOW can set professional services and related fees.
Unless the order says otherwise, the terms state that payments are non-cancelable, not prorated for partial months, and non-refundable. Taxes are generally outside the displayed fees.
The initial subscription term belongs in the order form. The general terms say an order renews for a matching term unless either party gives written notice at least 30 days before the current term ends.
These are material buying terms. Ask for the precise initial term, ramp, invoice schedule, renewal baseline, price adjustment, notice route, and reduction rights.
The terms also address wind-down and pending post-processed data. Confirm what happens to draft notes, account data, PHI, interfaces, and retained materials when the relationship ends.
Privacy, Security, and BAA Review Affect Cost
Suki's terms say the parties will execute a BAA when Suki acts as a business associate. Suki also publishes a BAA form.
A public BAA is useful evidence. It does not prove that one deployment, data flow, EHR connection, user group, or downstream system meets the buyer's duties.
Suki's Privacy Policy says customer instructions, service agreements, and BAAs govern practice data. It also assigns customers responsibility for permissions and their own policies.
HHS cloud guidance says regulated organizations need the appropriate agreement and their own risk analysis when a cloud provider handles ePHI. HHS does not certify products.
Security and privacy review can create legal, technical, monitoring, and renewal work. Include that work in the cost model. Our AI scribe BAA guide provides a practical starting checklist.
Clinical Responsibility Remains With the Professional
Suki's terms say the customer is responsible for verifying generated transcripts, clinical notes, orders, diagnoses, and other clinical documentation. The terms do not guarantee AI output accuracy or completeness.
That boundary belongs in the pilot and staffing model. Measure corrections that change meaning, missing content, unsupported content, attribution, medication details, negation, risk statements, codes, orders, and EHR transfer.
CMS states that, for applicable Medicare documentation, a practitioner using a scribe, including AI, must sign the entry to authenticate the documentation and care. See the CMS signature fact sheet.
Payer, profession, service, organization, and state rules can differ. A pricing tier does not transfer clinical judgment, coding accountability, record approval, or signature responsibility to software.
Use our AI medical scribe accuracy framework to create a local test set and correction taxonomy before evaluating vendor claims.
Suki and ClinicFrame Serve Different Buying Motions
ClinicFrame publishes this guide, so the comparison needs the same caveats for both vendors. ClinicFrame's current pricing page lists `$34.99` per user monthly or `$335.88` annually.
ClinicFrame has a Free plan with weekly limits, and Starter includes unlimited sessions.
ClinicFrame is a focused, self-serve AI medical scribe. It supports note generation, templates, records, and note chat. It does not offer Suki's deep enterprise EHR and partner-platform scope.
Suki may fit a health system that needs bidirectional EHR workflows, broader clinician functions, and organization deployment. ClinicFrame may fit an individual or small practice that accepts a narrower workflow and published subscription.
Neither fit statement proves note quality. Compare both with the same authorized or simulated cases, correction rules, transfer steps, privacy review, and total-cost horizon.
For other public-price options, use our AI scribe price comparison. Do not treat a lower price as proof of safety, quality, or workflow fit.
A Nine-Step Suki Buying Workflow
- Define the job. Name the clinicians, settings, note types, dictation tasks, codes, orders, summaries, languages, and EHR actions required.
- Choose the product surface. Map the job to Compose, the integrated clinician assistant, dictation, partner tools, or a documented combination.
- Map the current workflow. Record capture, drafting, review, correction, transfer, reconciliation, signature, support, and failure steps.
- Collect baseline data. Measure current documentation time, correction work, transfer work, delays, support, volume, and variation.
- Request a complete quote. Require the pricing unit, minimums, products, EHR scope, services, term, renewal, governance, and exit terms.
- Normalize the budget. Calculate first-year, steady-state, stress-case, per-eligible-user, per-active-user, and per-completed-encounter costs.
- Run a controlled pilot. Use representative authorized or simulated cases, defined success thresholds, fallback paths, and documented reviewers.
- Score total work. Compare adoption, correction, transfer, support, downtime, governance, and failure handling, not only draft speed.
- Decide and monitor. Record the reason, owner, review date, renewal threshold, quality measures, usage measures, and exit trigger.
Our AI medical scribe selection guide gives a broader product checklist. Keep the Suki quote attached to the local scoring record so future reviewers can reconstruct the decision.
Review status: Clinical, compliance, legal, competitor, and human editorial review of this guide remains pending.
