Pricing is structured for clinics and telemedicine teams running TabibAI's AI-powered intake, document-review, and physician-reviewed documentation workflow — built on frontier models from OpenAI, Anthropic, and Google and open-weight models including Llama, DeepSeek, and Qwen. Start free, scale as you grow.
For clinics getting started with AI-assisted intake and documentation. Full access to all 6 modules with guided clinical workflows.
For small clinics running daily intake, document summaries, and physician-ready notes. ROI typically visible within the first 2 weeks.
For telemedicine teams that need custom workflows, environments, and security planning. Scales to 50+ clinicians with enterprise-grade infrastructure.
A clear pricing structure for clinics, with paid plans handled through service agreements and invoices.
| Capability | Starter | Clinic plan | Enterprise plan |
|---|---|---|---|
| Product pages + workspace | Included | Included | Included |
| Sign in with Google (OAuth 2.0) or email + password | Backend verified | Backend verified | Custom auth planning |
| Clinical intake templates | Guided workflows | Clinic-specific | Custom workflows |
| Document processing | Guided summaries | 4+ document types | Cloud architecture scoped |
| AI model access (OpenAI GPT models, Anthropic Claude models, Google Gemini models) | Standard inferences | Full multi-model routing | Custom model configuration |
| Medical knowledge layer (ICD-10, RxNorm, SNOMED-CT) | Reference display | Integrated | Custom integration |
| Staff seats | 1 seat | Up to 5 | 50+ with RBAC |
| Audit logging | Basic view | Timestamped actions | Full compliance logging |
| Deployment environment | Shared environment | Dedicated production environment | Custom cloud (GCP/AWS/Azure) |
| Commercial terms | Free tier | Monthly subscription | Custom agreement |
Medical note: TabibAI is a workflow and documentation assistant. It does not diagnose, prescribe treatment, or replace professional medical judgment.
Straightforward answers for clinics running a controlled healthcare AI workflow.
Yes. Clinics can explore the full product workflow with guided clinical examples before sharing requirements or starting a paid plan. Real patient information should only be used after a proper service agreement and data-handling setup are in place.
Billing starts only after the clinic deployment scope is agreed, including seats, workflow requirements, security expectations, and deployment responsibilities.
Yes. Intake templates, document workflows, seats, and deployment requirements can be adjusted during deployment planning before the clinic's go-live.
Not by default. Export and integration needs vary by clinic and should be scoped explicitly rather than promised as a generic feature.