VERN AI Partner Hub
Everything you need to position, sell, implement, and support VERN — from first prospect to live deployment.
About VERN
The behavioral governance and emotional intelligence layer for any AI interface — deployed as a drop-in API.
What VERN Does
VERN is a drop-in governance layer — not a chatbot, not an LLM replacement, and not a prompt. It sits between any AI model and any output channel (text, voice, video avatar) and deterministically controls how the AI behaves in emotionally sensitive, high-stakes, or regulated conversations.
- Deterministic emotion detection — not probabilistic, not a filter
- 63 purpose-built Behavioral Control Modules (BCMs)
- Full conversation analytics and audit trail
- Works with any LLM, any input modality, any output channel
- Stateless — no client data stored, PII stripped before processing, encrypted end-to-end
Target Verticals
Crisis-aware intake, patient support, regulated conversations where an AI mistake carries real liability.
Compliance-sensitive conversations, fraud/risk signal detection, audit-ready interaction logs.
Escalation handling at scale, 24/7/365 coverage across any channel without added headcount.
Why It's Not Prompt Engineering
Prompts are probabilistic — they drift over time, and the same input can produce different outputs on different runs. VERN's emotion engine is deterministic: the same input reliably produces the same governed behavior, every time, with a full audit trail. That's the difference between hoping your AI behaves and being able to prove it does.
Case Study: Mentavi Health / ADHD Online
24/7/365 AI-powered patient support with no added staffing. VERN turned their support function into an active intake and lead pipeline — zero incidents across thousands of conversations, full crisis-aware handling, complete auditability.
Partner Onboarding Checklist
Four phases from signed agreement to first live deal. Owner column indicates who is responsible for each item.
Partner Battlecard
For internal partner use only — not client-facing. Register a qualified opportunity before looping in VERN for a joint call or demo.
💼 Economic Buyer
COO / Head of CX / Head of Support
Cares about cost avoidance, coverage expansion, and scaling 24/7 support without headcount growth.
🔧 Technical Buyer
CTO / VP Engineering
Cares about integration effort, API architecture fit, and avoiding a rip-and-replace of the existing stack.
⚖️ Risk Buyer
Compliance / Legal / Risk Officer
Cares about liability, auditability, and what happens when the AI mishandles a sensitive situation.
Company Signals to Look For
- Already running or actively building an AI chatbot, voice agent, or avatar for customer-facing interactions
- Operates in a regulated or high-compliance environment where an AI mistake carries real liability
- Has had, or is worried about, an AI incident — hallucination, off-brand response, mishandled crisis
- Wants to scale support coverage (24/7/365) without adding headcount
- Currently has little or no visibility into what their AI agents are saying in live conversations
Qualifying Questions
- Do you currently have, or are you building, an AI-driven chatbot, voice agent, or avatar for customers?
- What LLM or platform is it built on today?
- Has your AI ever gone off-script, hallucinated, or said something it shouldn't have?
- Do you have visibility into what your AI is actually saying, turn by turn, in real conversations?
- Is there compliance, legal, or reputational risk if the AI handles a sensitive situation poorly?
- How do you currently measure whether the AI is performing well or poorly?
Proof Points to Lead With
- 0 hallucinations, drift, or character breaks across 50,000+ live conversations in 26 countries
- 88.5% graceful conversation-exit rate vs. a 70% industry-leader benchmark
- 708 independently audited sessions
- 3 patents pending on the core deterministic emotion engine
- 63 Behavioral Control Modules in the library, and growing
- Case study: Mentavi Health / ADHD Online — 24/7/365 coverage with no added staffing, turning support into an active intake and lead pipeline
Objection Handling
Those are generic safety filters, not a behavioral governance layer. VERN adds deterministic emotion detection, 63 purpose-built Behavioral Control Modules, and full conversation analytics — none of which come from a base LLM's built-in moderation.
No. Prompts are probabilistic and drift over time. VERN's emotion engine is deterministic (3 patents pending), so the same input reliably produces the same governed behavior, with a full audit trail to prove it.
VERN is a drop-in layer via API — works with any LLM, any input (voice/text/video), any output (chat/voice/avatar). No migration required. If they're already running an AI, VERN wraps it.
Plans start at $49/mo and scale with usage. Most engagements begin with a small implementation fee — not a large upfront contract. See the Pricing section of this portal for full tier-by-tier detail.
VERN is stateless — no client data is stored. PII is stripped before processing, and everything is encrypted end-to-end.
50K+ live conversations across 26 countries with zero hallucinations, drift, or character breaks. 708 independently audited sessions. An 88.5% graceful conversation-exit rate vs. a 70% industry-leader benchmark. Full research results linked in the Resources section.
Competitive Positioning
| Alternative | How VERN Wins |
|---|---|
| DIY prompt engineering | Not deterministic, no audit trail, drifts over time, no analytics layer. Every model update can break behavior silently. |
| Generic guardrail / moderation tools | Built for topic/content filtering — not emotional intelligence or behavioral governance. No ROI or insight reporting. |
| Building it in-house | Faster to deploy (implementation fee vs. a build team + timeline), already patent-pending and proven at scale, works across every modality from day one. |
Partner Pricing
FDE partner pricing reflects a 30% discount off retail. Partners resell to clients at any price they determine. Current as of August 2026.
Plans
| Plan | Retail / mo | Partner Price | Token Pool | Overage | Deployments | Modalities |
|---|---|---|---|---|---|---|
| Creator | $49 | $34 | 16M | $6 / 1M | Unlimited — Marketplace library | Text · Voice · Avatar |
| Studio | $149 | $104 | 49M | $6 / 1M | Unlimited — Marketplace library | Text · Voice · Avatar |
| Operator | $499 | $349 | 166M | $5 / 1M | Unlimited — built AI Humans | Text · Voice · Avatar |
| Business OS | $1,500 | $1,050 | 500M | $3.50 / 1M | Unlimited — built AI Humans | Text · Voice · Avatar |
| Enterprise OS | $5,000 | $3,500 | 1.67B | $3 / 1M | Unlimited — built AI Humans | Text · Voice · Avatar |
Onboarding & Implementation
| Plan | Onboarding Fee (Retail) | AI Humans Included | Additional AI Humans | Scope |
|---|---|---|---|---|
| Creator / Studio | None | Marketplace library only — no custom builds | — | Self-serve, Marketplace personas |
| Operator | $7,500 FDE: Waived | 1 custom AI Human — 1 persona, 1 use case | $5,005 each | Self-serve, Marketplace personas |
| Business OS | $15,000 FDE: Waived | 4 custom AI Humans — up to 2 personas each, 1 use case each | $3,500 each | 1 integration + go-live support. 3–4 weeks |
| Enterprise OS | $30,000 FDE: Waived | 10 custom AI Humans — up to 3 personas each, up to 2 use cases each | $2,500 each | Discovery workshop + up to 2 integrations. 4–6 weeks |
Overage Rates
| Plan | Rate / 1M tokens | Effective / min | 5-min session | 10-min session |
|---|---|---|---|---|
| Creator / Studio | $6 | $1.20 | $6 | $12 |
| Operator | $5 | $1.00 | $5 | $10 |
| Business OS | $3.50 | $0.70 | $3.50 | $7 |
| Enterprise OS | $3 | $0.60 | $3 | $6 |
| Scale (25k+ min/mo) | $2.50 | $0.50 | $2.50 | $5 |
| Custom (100k+ min/mo) | $2 | $0.40 | $2 | $4 |
Token Burn Rates by Modality
| Modality | What it Covers | Approx. Usage |
|---|---|---|
| Avatar AI Human | Video + voice + intelligence | 200K tokens/min — ~1M per 5-min session, ~2M per 10-min session |
| Voice AI Human | Audio + intelligence layer | 175K tokens/session |
| Text AI Human | Text + intelligence layer | 15K tokens/exchange |
Important Notes
Implementation fees are waived for FDE-led deployments at Operator, Business OS, and Enterprise OS tiers. FDE partners bill clients independently for implementation services — that's your margin to structure as you see fit. Enterprise or custom volume deals outside these tiers must be routed to Craig for approval before quoting.
Deal Registration
Register as soon as you have a named contact and a real reason to believe there's an opportunity — don't wait for a scheduled meeting. Email [email protected] to submit.
Submit a Registration
Email [email protected] with the following. Each submission is logged in the Deal Registration Log as the source of truth.
- Partner name — who gets credit and protection
- Prospect company + contact name, title, email — confirms it's a real, named opportunity
- Vertical / use case — helps VERN route the right technical support
- How the lead originated — existing relationship, inbound, event, etc.
- Estimated deal size / plan tier (if known) — helps prioritize and forecast
- Target timeline — rough close date or urgency
VERN Review & Confirmation (within 2 business days)
VERN responds with one of three outcomes:
- Approved — no conflict, protection window starts from the original submission date.
- Flagged — VERN has an existing relationship with this account. Both sides work out sourcing credit directly.
- Needs More Info — missing a named contact or real signal of interest.
Every approved registration gets a registration ID you can use to check status at any time.
Protection Window & Exclusivity
Approved registrations protect your right to work the deal for 90 days from submission. Protection is active, not passive — it requires visible activity.
- Renews automatically in 90-day increments with active deal movement (a logged call, stage change, or update within the last 30 days)
- If a deal goes quiet for 45 days, VERN will reach out once before the registration is put at risk
- Two partners register the same account — the earlier timestamped submission wins
- Disputes that can't be resolved between partner and VERN's commercial contact escalate to Craig
Deal Stages
| Stage | Definition |
|---|---|
| Registered | Submission approved, protection window active, no meeting held yet |
| Discovery | Initial call(s) held to confirm need and fit |
| Demo / Pilot | Joint technical demo delivered, or a paid pilot underway |
| Proposal Sent | Pricing/scope proposal delivered to the prospect |
| Closed Won | Contract signed — moves to onboarding |
| Closed Lost | Prospect passed, or went with an alternative |
| Expired | Protection window lapsed with no qualifying activity — can be re-registered at any time |
Submit as soon as you have a named contact and a real reason to believe there's an opportunity. VERN reviews within 2 business days.
Registration Submitted
Your registration has been sent to the VERN sales team. You'll receive a confirmation copy at the email address you provided. VERN will review within 2 business days and reply with a registration ID.
← Register another deal
FDE Discovery & Scoping Guide
As an FDE partner, you own the discovery and scoping session with the client — this is one of the four minimum deliverables under the implementation fee waiver. Use this as a working checklist during the call.
- What's driving this project right now — why is this a priority this quarter?
- Who is the economic buyer for this deal (e.g. COO, Head of CX/Support)?
- Who is the technical buyer, and who owns the integration on their side (e.g. CTO, VP Engineering)?
- Is there a compliance, legal, or risk stakeholder who needs to sign off before go-live?
- What's the target go-live date, and what's driving that timeline?
- What does their procurement / budget approval process look like?
- Do they currently have, or are they building, an AI chatbot, voice agent, or avatar for customers?
- What LLM or platform is it built on today, if anything?
- What channels are in play — chat, voice, video avatar, or a combination?
- Has their AI ever gone off-script, hallucinated, or handled a sensitive situation poorly?
- Do they currently have visibility into what the AI is actually saying, turn by turn, in live conversations?
- How do they measure whether the AI is performing well today (if at all)?
- What's the primary use case — support deflection, crisis-aware intake, compliance-sensitive conversations, sales, something else?
- What's the expected conversation volume (per day/month)?
- What persona, tone, and behavior does the AI need to project? Any hard constraints (e.g. must never do X)?
- What does success look like for this deployment — specific KPIs (containment rate, escalation reduction, CSAT, graceful-exit rate)?
- Is there a past AI incident or near-miss they're specifically trying to avoid repeating?
⚠️ Regulated industries materially affect scope, price, and timeline — flag these early rather than discovering them mid-build.
- Does this deployment touch PHI, PII, or financial data?
- Are they in a regulated industry (healthcare, financial services) with specific compliance requirements?
- Do they require a BAA? If video avatars are in scope, are they aware that video/voice-avatar features route through a sub-processor and may need their own BAA with that vendor?
- Do they have data residency requirements?
- Do they require SOC 2 or other vendor security documentation as part of procurement?
- What systems need to be integrated — CRM, ticketing, scheduling, other internal tools?
- Do they have a preference between API integration and a portable embed?
- What authentication or access requirements apply (SSO, IP allowlisting, VPN)?
- If voice is in scope, what telephony infrastructure do they currently use?
- How many distinct systems/environments will need to be touched? (This is a primary driver of implementation cost.)
As a reference: an enterprise-scale regulated deployment routinely warrants a $150,000 services engagement. This reflects real scope, not a premium.
- Which VERN OS tier fits this deployment (Operator, Business OS, Enterprise OS)?
- What internal resources can the client dedicate (engineering contact, project owner, QA/testing support)?
- How much testing and compliance validation will this deployment require?
- Is this a single use case to start with expansion planned, or a full rollout from day one?
- Has this opportunity been registered in the VERN Partner Portal yet?
After Discovery
Once discovery is complete, scope the integration build, BCM/persona configuration, and go-live plan (minimum 5 business days of post-deployment support), then price the engagement using the FDE Partner Pricing Sheet and implementation guidance in the Commercial Terms.
Support & SLA
Standard support hours: Mon–Fri, 9:00 AM – 5:00 PM ET, excluding US federal holidays. VERN AI targets 99.9% monthly uptime for the core platform.
Part A — VERN AI's Commitment to FDE Partners
| Severity | Level | Definition | Initial Response | Resolution Target |
|---|---|---|---|---|
| P1 | Critical | Platform completely unavailable or core AI Human functionality broken — clients cannot use the product at all. | 1 hour | 4 hours |
| P2 | High | Significant feature degradation — core functionality impaired but partial workaround exists. Affects production client environments. | 4 hours | 1 business day |
| P3 | Medium | Non-critical feature issue or intermittent problem. Client workflows inconvenienced but not blocked. Workaround available. | 1 business day | 3 business days |
| P4 | Low | Minor bug, cosmetic issue, documentation gap, or general question. No production impact. | 2 business days | Best effort |
Support Channels
| Channel | Use For | Notes |
|---|---|---|
| Partner Slack Channel | P1, P2 | Dedicated VERN Partner Support channel. P1/P2 issues must be opened here for fastest triage. |
| P2, P3, P4 | [email protected] — include severity tag in subject line (e.g., [P3]). | |
| Partner Portal | P3, P4 | Ticket submission and tracking. Recommended for non-urgent issues. |
| Emergency Phone | P1 only | Provided to active partners upon agreement execution. For platform-down situations only. |
Escalation Path
FDE Partner — Immediately
Attempt to isolate the issue. Open a Slack thread or ticket with: (1) severity, (2) affected client accounts, (3) steps to reproduce, (4) any error messages or logs, (5) what's already been attempted.
VERN AI Partner Support — Per SLA Response Times
Triage and initial diagnosis. Confirms severity. Provides workaround if available.
VERN AI Engineering — If Unresolved at S2
Engineering escalation for P1/P2. Partner notified of escalation status and ETA. FDE partners may request escalation to S3 at any time for production-impacting issues.
VERN AI VP Engineering — P1 > 2 Hours Unresolved
Executive escalation for critical outages. Direct communication with FDE partner. VERN will not unreasonably deny an escalation request for a production-impacting issue.
SLA Breach Credits
If VERN AI fails to meet a P1 or P2 response time commitment in a given calendar month, the affected FDE partner is entitled to a service credit equal to 10% of that month's subscription invoice for the affected account. Credits apply to the following month's invoice. To claim: submit a written request to [email protected] within 15 days of the breach.
Part B — Regulated Industry Client SLA Template
Use the following tiers as a basis for your own client SLA commitments in healthcare (HIPAA), fintech (SOC 2/PCI-DSS), and other regulated environments. Do not promise clients P1 response times shorter than 1 hour, as this creates expectations you cannot meet if the issue requires VERN escalation.
| Severity | Response (Regulated) | Resolution Target | Additional Obligation |
|---|---|---|---|
| P1 Critical | 30 min | 2 hours | Incident log opened immediately; client notified within 15 min of identification |
| P2 High | 2 hours | 8 hours | Compliance team notified if PHI/PFI potentially affected |
| P3 Medium | 4 hours | 2 business days | Issue logged with full audit trail |
| P4 Low | 1 business day | Best effort | Standard ticket process |
Regulated-industry SLA commitments are a primary reason enterprise implementations in healthcare and fintech are priced at $100,000–$150,000. The documentation, audit trail, and compliance overhead is real — price accordingly. Healthcare clients: retain all incident logs for 6 years (HIPAA). Fintech clients: layer PCI-DSS card brand notification rules on top of these tiers.
Resources & Links
Quick-reference links to public resources, demos, and technical documentation.
Questions or Escalations?
For deal registration, pricing approvals, joint calls, or general partner questions, reach the VERN operations team. Enterprise/custom deals outside standard tiers need Craig's approval before quoting.
[email protected]