Workflow scope
Which modules, queues, and human-review paths are included in the pilot.
Pilot scope
Pricing should follow a defined operating scope—not a fictional tier table.
MyAIPOS does not currently publish public subscription plans or prices. Pilot discussions begin with the workflows, integrations, people, and controls the practice actually needs.
Integration readiness
Mailbox providers, existing systems, external contracts, and least-privilege setup requirements.
Security and governance
Roles, data boundaries, evidence requirements, and deployment-specific compliance obligations.
Implementation effort
Configuration, validation, training, and support required to move from review to a safe operating pilot.
What a pilot conversation covers
Fit, boundaries, and the next verifiable step.
- Current practice workflow and highest-cost administrative friction
- Systems and inboxes in scope, with clear provider and credential ownership
- Human roles, review responsibilities, and exception handling
- Activation gates, validation evidence, and what remains deliberately inactive
Pilot discussion
Define the right pilot before discussing price.
Public subscription pricing is not yet published. A pilot discussion can evaluate workflow fit, security boundaries, and implementation scope without collecting patient information.