Every plan includes configuration, testing, monitoring, human support, and a monthly conversation allowance. You see the rate before signing and receive alerts before any overage.
Hands-on beta access for the first five qualified businesses.
Reliable lead coverage for a growing small business.
More channels, locations, and workflows for established teams.
One customer conversation can require many behind-the-scenes model calls. We group that work into a unit a business owner can understand and verify.
Your plan covers the AI employee, support, integrations, and an included monthly allowance.
A conversation is one continuous customer interaction about one request within the agreed session window.
We alert you at 75%, 90%, and 100% of the allowance so volume never becomes a surprise.
Keep the published overage, set a review threshold, upgrade, or move to Stable Bill after a normal usage baseline.
Estimate complete digital conversations—not messages, tokens, or hidden API calls. Adjust this anytime as your business grows.
After we measure two normal months, we can quote a fixed monthly allowance with a planning buffer. At this volume, we would size that allowance near 1,700 conversations, then review it quarterly with you.
Estimate excludes one-time implementation, carrier SMS, voice minutes, premium model requests, taxes, and paid third-party software. Those costs are approved before activation.
Compare the recurring Standard plan with the estimated monthly cost of an employee assigned to the same workload.
This is a planning tool, not a claim that AI replaces every responsibility of an employee. Adjust the inputs to match the role and costs in your business.
The employee-cost calculator shows the staffing side. The opportunity calculator estimates delayed inquiries and repetitive administrative time using your own assumptions.
Your monthly service covers the operational work required to keep an AI employee useful, safe, and aligned with your business.
Responsibilities, outcomes, boundaries, and escalation paths documented before launch.
Your services, FAQs, policies, tone, and examples organized into a working knowledge base.
Normal, unusual, and adversarial conversations tested before customers can reach the agent.
Clear reporting on work completed, outcomes, escalations, and improvement opportunities.
Prompts, knowledge, and workflows refined as your business and customer needs change.
A real person remains accountable for setup, performance review, and issue resolution.
The implementation fee is invoiced after fit and scope are confirmed. Monthly service begins when your AI employee is approved for production—not when you first submit the order request.
Yes. Standard language-model and automation API usage is included within the published digital conversation allowance. Carrier SMS fees, voice minutes, premium model requests, and paid third-party software are confirmed separately when applicable.
A single customer request can require several model and software calls, so a raw hit count is difficult to predict and does not reflect the value delivered. Staff Right AI bills digital conversations: a clear, customer-facing unit defined in your agreement.
A continuous customer or employee interaction about one request within the configured session window. The final agreement defines the session window and reporting method before billing begins.
Your portal shows current usage. We alert you near 75%, 90%, and 100% of the monthly allowance. Published overages are billed after the month closes; you can also request a review threshold instead of automatic overage.
After two representative months, we can quote a fixed allowance based on your measured average plus a planning buffer. The allowance is reviewed quarterly so your bill stays predictable without forcing you into an oversized plan.
Your exact initial term, renewal, pause, and cancellation rules appear in the service agreement before payment. Founding partners receive preferred terms in exchange for regular feedback and close collaboration.
Volume, channels, locations, workflows, voice usage, and business-system integrations affect scope. We identify those factors in the fit review so there are no surprises.
Yes. A narrow first deployment is usually faster and safer. Additional responsibilities or coordinated roles can be added after the first workflow is stable.