\\n\\n\\n \\n \\n AI Readiness Assessment — Green Mountain Mutual Insurance | Vermont AI Systems\\n \\n \\n \\n \\n \\n \\n \\n \\n\\n\\n \\n\\n
\\n
Sample AI Readiness Assessment
\\n

Green Mountain Mutual Insurance

\\n
180 employees · $240M annual premiums · Regional P&C · Vermont-based
\\n
\\n\\n
\\n\\n \\n
\\n

Executive Summary

\\n

Assessment completed for: Green Mountain Mutual Insurance (fictional profile — illustrative only)

\\n \\n

Top 3 Risks Identified:

\\n
    \\n
  1. PII in claims notes hitting public LLMs. Claims handlers are using personal ChatGPT and free AI accounts to draft summaries, review coverage, and respond to customer inquiries. Claims notes contain names, addresses, medical history, vehicle identification numbers, and financial account data — all flowing to consumer AI systems with no data governance controls.
  2. \\n
  3. GLBA exposure on consumer financial data. The Gramm-Leach-Bliley Act requires financial institutions to protect non-public personal information. Current AI usage — including AI tools processing policy applications and claims data — has not been mapped to GLBA compliance requirements. No vendor BAAs exist. No data flow documentation has been created for the compliance team.
  4. \\n
  5. NAIC Model Law 668 compliance gaps. The NAIC's AI Model Law (668), adopted in substantial part by Vermont's Department of Financial Regulation, requires carriers to document AI system usage, maintain transparency on AI decisions affecting coverage, and provide appeal mechanisms for AI-assisted outcomes. The carrier has no AI governance program and no documentation of existing AI tool usage as required by the model law.
  6. \\n
\\n

Recommended Path:

\\n

Private AI infrastructure — VPC-isolated deployment with claims triage assistant and underwriting research agent. Estimated project: $42K build + $4.2K/mo operations retainer.

\\n
\\n\\n
\\n
$240M+
Annual premium exposure if GLBA violation surfaces
\\n
180
Employees — most using personal AI tools daily
\\n
$42K
Recommended build investment
\\n
12 wks
Phase 1 implementation timeline
\\n
\\n\\n
\\n\\n \\n

Section 1 — Company Profile & Scope

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
FieldDetail
CompanyGreen Mountain Mutual Insurance (fictional profile)
Headcount180 employees across: underwriting (22), claims handling (38), field agents (45), IT & operations (15), sales & distribution (28), finance & compliance (12), executive (8), HR & admin (12)
Annual Premium Volume$240M across regional P&C lines
Product LinesPersonal lines (homeowners, auto) ~55%; Small commercial (BOP, workers comp) ~30%; Farm & ranch ~10%; Specialty/excess ~5%
Geographic FocusVermont primary; expanded into NH and upstate NY since 2018
DistributionIndependent agent network (~85 agents); 3 direct sales staff; no captive captive agents
Current IT InfrastructureOn-premise core policy and claims system (PolicyPen v4); Azure-hosted file servers; Microsoft 365 E3; Salesforce for agent management; IBM Watson Assistant for customer service chatbot (pilot)
Current AI UsageChatGPT personal accounts (widespread); IBM Watson Assistant pilot; Microsoft 365 Copilot trial (12 users); no formal AI governance program
Decision-MakersCEO, COO, VP Underwriting, VP Claims, CIO, Director of Compliance, Director of Agent Relations
\\n\\n
\\n

Scope note: This fictional profile is based on a composite of real mid-size regional P&C carriers in Vermont. The data sensitivity findings, risk patterns, and architecture recommendations are directly applicable to actual carriers of this size and product mix.

\\n
\\n\\n
\\n\\n \\n

Section 2 — Current State Inventory

\\n

AI tools currently in use across the carrier, mapped by deployment type, user volume, and risk classification.

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
ToolDeployment TypeUsersVolume EstimateRisk Flag
ChatGPT (free, personal accounts)Consumer web — no enterprise controls~65 employees (underwriting, claims, agents)150–280 queries/day estimatedCRITICAL — No firm visibility, no data controls, GLBA exposure
Microsoft 365 CopilotM365 E3 tenant — pilot phase12 underwriters (trial)Unknown — no reporting configuredHIGH — Consumer financial data in M365 tenant, no RBAC configured for AI access
IBM Watson AssistantCloud SaaS — customer service chatbotCustomer-facing (live to policyholders)~800 conversations/monthMODERATE — Policyholder PII in Watson; carrier reviewing BAAs
PolicyPen AI featuresLicensed on-premise system22 underwriters, 8 processorsHigh — daily useLOW — Vendor-controlled, on-premise
Salesforce Einstein AICloud SaaS — agent management28 sales staffModerate — lead scoring, email draftingHIGH — Agent contact data, commission structures, agent PII in Salesforce cloud
Google Gemini (personal accounts)Consumer web~20 employeesLow — occasional useCRITICAL — Same as ChatGPT free tier; no visibility
CLAIMS FRAUD MODEL (internal)On-premise — legacy statistical modelClaims adjusters (required)Used on ~40% of claimsMODERATE — Not AI/LLM; needs documentation for NAIC 668
\\n\\n
\\n

Key finding: An estimated 60–70% of AI usage is outside IT visibility. The compliance team has no documentation of which AI tools are processing policyholder data — a direct gap against GLBA Safeguards Rule requirements and NAIC Model Law 668.

\\n
\\n\\n
\\n\\n \\n

Section 3 — Data Sensitivity Map

\\n

Classification of data types by department, with AI tools currently touching each classification. This map forms the basis for GLBA and NAIC compliance documentation.

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
DepartmentData TypesAI Tools Touching This DataClassificationVolume/Month
Claims HandlingClaim forms, medical reports (auto accident), police reports, body shop estimates, witness statements, bank account info for claim paymentsChatGPT (personal), Gemini (personal), M365 Copilot (trial)CRITICAL — PII + PHI + financial data / GLBA / HIPAA adjacency~1,400 claims/month; avg 8–12 documents/claim
UnderwritingPolicy applications (SSN, DOB, financial disclosures), loss history reports, credit-based insurance scores, inspections, property recordsChatGPT (personal), M365 Copilot (trial), PolicyPen AICRITICAL — Non-public personal financial data / GLBA / NAIC regulated~850 new policies/month; 400+ renewals/month
Field AgentsCustomer contact info, policy documents, claims status inquiries, coverage questions, producer commission recordsChatGPT (personal), Salesforce Einstein, Gemini (personal)HIGH — Agent PII, commission data, policyholder contacts / GLBA~85 agents, avg 25 customer interactions/day
Customer Service (Watson)Policy numbers, claim numbers, coverage questions, payment info, contact historyIBM Watson Assistant (live)MODERATE — PII in third-party cloud / GLBA / contract review needed~800 conversations/month
Sales & DistributionLead data, commission structures, agent performance metrics, competitive quote dataSalesforce Einstein, ChatGPT (personal)HIGH — Agent PII, competitive data / GLBA~200 new leads/month; 85 agent records
Finance & CompliancePremium reports, loss ratio data, reserves, regulatory filings, audit workpapersChatGPT (personal), M365 Copilot (trial)HIGH — Regulatory filings, financial data / SOX adjacencyQuarterly regulatory cycle; monthly financial reporting
\\n\\n

GLBA Safeguards Rule Compliance Gap

\\n

The GLBA Safeguards Rule (16 CFR Part 314), as updated in 2023, requires carriers to:

\\n \\n
\\n

Compliance finding: Green Mountain Mutual is not in compliance with the GLBA Safeguards Rule as it relates to AI tool usage. The carrier cannot certify compliance without documenting the AI tools in use, the data they access, and the controls in place. NAIC Model Law 668 adds additional documentation requirements specific to AI-assisted decisions in underwriting and claims.

\\n
\\n\\n
\\n\\n \\n

Section 4 — Exposure Scenarios

\\n

Three plausible incident scenarios based on observed carrier behavior and current AI usage patterns.

\\n\\n \\n
\\n
Scenario 1 of 3
\\n

Claims Notes with Medical Records Sent to Personal ChatGPT

\\n
Trigger: A claims handler uses their personal ChatGPT account to summarize a 15-page medical records request for an auto accident claim. The document contains claimant medical history, diagnostic codes, and physician notes. It is transmitted to OpenAI's servers under ChatGPT free tier terms of service.
\\n

How it happens: ChatGPT free accounts are personal accounts — there's no technical or procedural control preventing an employee from using one for work. The handler is trying to work faster. The medical records are PHI-adjacent (auto insurance is a common HIPAA secondary use context). OpenAI's privacy policy does not include HIPAA BAA coverage. The carrier has no visibility into this interaction.

\\n
Estimated impact: Vermont DFR notification requirement (9 V.S.A. § 2435); possible regulatory inquiry under GLBA; potential class action exposure if multiple claimants affected. Remediation cost: $150K–$400K depending on scope of exposure.
\\n
\\n\\n \\n
\\n
Scenario 2 of 3
\\n

Underwriting Decision Surface During M365 Copilot Pilot

\\n
Trigger: Underwriters in the 12-user M365 Copilot pilot are working with policy application data including SSN, financial disclosures, loss history, and credit-based insurance scores. M365 Copilot is not configured with any AI-specific access controls — it has access to the same M365 tenant data as the underwriters themselves.
\\n

How it happens: M365 Copilot can surface content from emails, SharePoint, and Teams within the tenant. An underwriter asks Copilot to \\\"find all the loss history patterns for this agent's book.\\\" Copilot surfaces loss history from emails that included sensitive information. The underwriter uses this in their underwriting decision — without realizing Copilot surfaced information outside the formal policy file.

\\n
Estimated impact: NAIC 668 requires carriers to be able to explain AI-assisted decisions and provide appeal mechanisms. If an underwriting decision is challenged, the carrier cannot document what data Copilot used. DFR inquiry and potential market conduct examination findings. Remediation: $100K–$350K.
\\n
\\n\\n \\n
\\n
Scenario 3 of 3
\\n

Agent Commission Data + Customer Contact Info in Salesforce Einstein

\\n
Trigger: Salesforce Einstein is being used for lead scoring and email drafting for the 85-agent distribution network. Agent commission records and customer contact data are in Salesforce. Einstein's AI features process this data to score leads and draft outreach emails. Salesforce's data processing terms and AI training policies have not been reviewed by the carrier's legal team.
\\n

How it happens: Many SaaS AI features include provisions allowing the vendor to use customer data to improve their AI models. If Salesforce is using carrier data to train Einstein, the agent commission structure and customer contact data may be used in ways the carrier hasn't authorized. The carrier has no BAA with Salesforce covering AI-specific data use.

\\n
Estimated impact: Agent commission data is sensitive competitive information. Customer contact data is GLBA-regulated. Without a vendor BAA covering AI training data use, the carrier is exposed to claims of unauthorized data sharing. Remediation: $75K–$250K in legal costs, potential regulatory action under GLBA.
\\n
\\n\\n
\\n\\n \\n

Section 5 — Recommended Architecture

\\n

Two AI capabilities are recommended for Phase 2 deployment: a claims triage assistant and an underwriting research agent. Both are deployed in a VPC-isolated environment with no data leaving the carrier's private infrastructure.

\\n\\n
\\n

Green Mountain Mutual Insurance — Private AI Architecture

\\n
\\n
Claims/Underwriting Data
Policy files, claim notes, medical records (anonymized), agent communications
\\n
\\n
Secure Document Pipeline
Encrypted ingestion · RBAC by role · Anonymization layer for PHI
\\n
\\n
VPC-Isolated AI Layer
Private LLM (Llama 3.1 70B or Mistral) · No external API calls · Fully encrypted
\\n
\\n
Claims Triage Assistant
First-pass claim review, coverage check, reserve recommendation, fraud flag
\\n
\\n
Underwriting Research Agent
Policy portfolio Q&A, rate manual lookup, coverage comparison, risk notes
\\n
\\n
\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
ComponentDescriptionImplementation
Claims Triage AssistantFirst-pass review of incoming claims — coverage verification, reserve range recommendation, fraud indicator flag, medical record summarization. Trained on the carrier's claims history, coverage forms, and claims handling SOPs.VPC-isolated; Llama 3.1 70B fine-tuned on claims corpus; RAG pipeline against claims document store; output is draft recommendation — handler reviews and approves
Underwriting Research AgentNatural language Q&A against the full policy portfolio, rate manuals, underwriting guidelines, and agent communications. Underwriter asks: \\\"What's the exposure profile for this class code in Chittenden County?\\\" — gets answer from the carrier's own data, not from public sources.VPC-isolated; Mistral fine-tuned on policy corpus; RAG against rate manual PDF library and agent email archive; audit log of every query and response
PHI Anonymization LayerMedical records and other PHI-adjacent data is anonymized (not just redacted) before ingestion into the training corpus. The model learns from claim patterns, not from individual claimant identity.HIPAA-adjacent design; de-identification pipeline before vector embedding; no raw PII in training data
Role-Based Access ControlsUnderwriters see policy and rate data. Claims handlers see claim documents. Agents see customer contact data for their own book. No cross-role data surfacing without explicit access grant.RBAC layer above document store; each AI query checks user role before returning data; principle of least privilege enforced
Immutable Audit LogEvery query and response is logged — user ID, timestamp, data sources accessed, output. Required for NAIC 668 documentation and GLBA compliance reporting.Append-only log to separate audit store; SHA-256 integrity verification; exportable to compliance dashboard
\\n\\n
\\n

IT/Compliance note: The Watson Assistant chatbot (currently in customer service) should be evaluated for replacement with a private AI deployment in Phase 3. The existing Watson contract should not be renewed without a comprehensive BAA covering AI training data use and a data retention audit.

\\n
\\n\\n
\\n\\n \\n

Section 6 — Phased Roadmap

\\n\\n \\n
\\n
Phase 1 — Foundation
\\n

90-Day Plan — Governance, Compliance, and Immediate Risk Reduction

\\n

Assessment: included ($7,500) · Internal resource: ~30 hrs IT, ~15 hrs compliance team

\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
MilestoneDeliverableOwnerTarget
AI tool inventoryComplete list of all AI tools in use by department, with data types touchedCIO + Compliance DirectorWeek 2
Data classification auditGLBA data map — all customer information flows, classified by sensitivityCompliance Director + CIOWeek 4
Immediate policy deploymentInterim policy: no customer data (PII, claims, policy info) in personal AI accounts; employee acknowledgment requiredCEO + HRWeek 3
M365 Copilot configuration reviewAI-specific access controls configured; Copilot usage reporting enabled; scope limited to approved data setsCIO + IT DirectorWeek 5
Vendor BAA reviewBAAs requested from all AI vendors (IBM Watson, Salesforce Einstein, Microsoft). Legal review of AI training data use clauses.Compliance Director + outside counselWeek 6
NAIC 668 gap analysisDocument current AI usage against NAIC Model Law 668 requirements; identify documentation gaps and appeal mechanism requirementsCompliance DirectorWeek 7
Phase 1 deliverableAI Governance Framework document: policies, data map, vendor inventory, GLBA compliance status, NAIC 668 documentationVermont AI Systems + CIOWeek 9
\\n
\\n\\n \\n
\\n
Phase 2 — Build
\\n

180-Day Plan — Private AI Deployment

\\n

Build investment: $42K · Internal resource: ~100 hrs IT, ~40 hrs claims/underwriting team

\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
MilestoneDeliverableTarget
Architecture designVPC network design, security controls, vendor selection for private cloud or on-premise deploymentMonth 4
Data pipeline developmentSecure document ingestion pipeline with PHI anonymization, RBAC enforcement, encryption at restMonth 5
Claims triage assistant deploymentPrivate LLM fine-tuned on carrier claims history; RAG pipeline; handler review interface; audit logMonth 5–6
Underwriting research agent deploymentPrivate LLM fine-tuned on policy portfolio; RAG against rate manuals; agent-facing Q&A interface; audit logMonth 6
NAIC 668 documentation packageComplete AI decision documentation for underwriting and claims; appeal mechanism implemented in systemMonth 6
Staff trainingClaims handlers and underwriters trained on private AI usage, audit trail understanding, and escalation proceduresMonth 6
Phase 2 deliverableTwo private AI capabilities in production; full GLBA documentation package; NAIC 668 compliance documentationMonth 6
\\n
\\n\\n \\n
\\n
Phase 3 — Optimize
\\n

365-Day Plan — Scale and Continuous Compliance

\\n

Included in operations retainer ($4.2K/mo) · Internal resource: ~20 hrs/quarter IT, ~8 hrs/quarter compliance

\\n \\n \\n \\n \\n \\n \\n \\n \\n
MilestoneDeliverableTarget
Agent network AI assistantAI assistant for field agents — policy lookup, coverage questions, claims status — trained on agent handbook and carrier communicationsMonth 9
Watson Assistant replacement evaluationReplace or renegotiate IBM Watson contract; evaluate private AI chatbot alternative for customer serviceMonth 9
Quarterly model retrainingClaims triage model retrained on new claims data; underwriting model updated with new rate manual versionsMonthly (retainer)
GLBA annual reviewAnnual Safeguards Rule compliance review, data flow documentation update, AI tool re-inventoryMonth 12
DFR market conduct preparationDocumentation package prepared for potential DFR market conduct examination of AI usage in underwriting and claimsMonth 12
Phase 3 deliverableOngoing compliance posture, operational AI system, annual review cycle establishedMonth 12
\\n
\\n\\n
\\n\\n \\n

Section 7 — Investment Estimate

\\n\\n

AI Readiness Assessment

\\n

Already completed for this fictional firm profile as part of the sample illustration.

\\n \\n \\n \\n \\n
ItemAmount
AI Readiness Assessment — full engagement$7,500
Total Assessment$7,500
\\n\\n

Private AI Build — Itemized Estimate

\\n

The $42K fixed-price covers two AI capabilities (claims triage assistant + underwriting research agent) deployed in VPC-isolated infrastructure. A fixed-price engagement can be scoped in a 60-minute discovery call.

\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
ComponentAmountNotes
Architecture design & security spec$6,500VPC design, RBAC schema, compliance framework alignment
Data pipeline development (PHI anonymization + RBAC)$9,000Encrypted document ingestion, de-identification layer, role-based access
Claims triage assistant — model fine-tuning + RAG$10,000Fine-tune on claims history; RAG against claims SOPs and coverage forms
Underwriting research agent — model + Q&A interface$8,500Rate manual RAG, policy portfolio Q&A, agent-facing interface
Immutable audit log system$4,500NAIC 668 documentation, GLBA compliance logs, compliance dashboard
NAIC 668 compliance documentation package$3,500Decision documentation, appeal mechanism, DFR-ready filing
Testing, QA, security review$5,000Penetration testing, GLBA compliance validation, handler review workflow testing
Project management & staff training$4,000Claims handler + underwriter training, policy documentation, change management
Net Build Cost$51,000
Discount (assessment credit + volume)($9,000)
Final Build Cost$42,000
\\n\\n

Operations Retainer

\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
ItemMonthlyAnnual
System monitoring and uptime management$1,400$16,800
Security patch management and vulnerability scanning$700$8,400
Quarterly model retraining (claims + underwriting)$800$9,600
Audit log review and GLBA/NAIC compliance reporting$500$6,000
Quarterly governance committee support$300$3,600
Direct support line for claims/underwriting team questions$500$6,000
Operations Retainer$4,200$50,400
\\n\\n
\\n

Year 1 Total

\\n

$99,900

\\n

($7,500 assessment + $42K build + $50.4K retainer)

\\n
\\n\\n
\\n\\n \\n

Section 8 — Vendor Comparison

\\n

Three-path analysis: Private AI Build (recommended) vs. IBM watsonx (insurance-focused) vs. Salesforce Einstein for Insurance.

\\n\\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n \\n
CriteriaPrivate AI Build
Recommended
IBM watsonx InsuranceSalesforce Einstein Insurance
Data sovereignty✓ Full — data never leaves carrier VPC✗ IBM-hosted cloud; data processing under IBM terms✗ Salesforce cloud; Einstein training data policy unclear
GLBA Safeguards Rule compliance✓ Architecture designed for it⚠ BAA available but requires negotiation⚠ No specific GLBA BAA for Einstein AI features
NAIC 668 documentation✓ Audit log + decision documentation built in⚠ Limited audit trail; carrier responsible for 668 documentation⚠ Not designed for insurance regulatory compliance
Claims data training (PII/PHI)✓ PHI anonymization layer; no raw PII in training✗ Medical data processing requires HIPAA BAA; not currently in place✗ Not HIPAA-covered; no BAA for medical records
Custom to carrier's own data✓ Fine-tuned on carrier's claims history and guidelines⚠ Pre-built insurance models; carrier data for RAG only⚠ Generic insurance AI; limited carrier-specific customization
Underwriting AI (rate manual Q&A)✓ Trained on carrier's own rate manuals and guidelines✓ Some UW optimization capabilities⚠ Lead scoring and email only; not UW research
Agent network support✓ Agent AI assistant in Phase 3 scope✗ Not focused on independent agent workflow✓ Salesforce-native agent management integration
Year 1 cost (build + ops)$99,900~$85K–$120K/year (SaaS licensing + implementation)~$60K–$90K/year (Einstein licensing + implementation)
Year 2+ ongoing cost$50,400/yr (retainer only)~$60K–$80K/yr (SaaS + support)~$50K–$70K/yr (Einstein licensing)
IP ownership✓ Carrier owns model weights and deployment✗ IBM owns the model; carrier licenses it✗ Salesforce owns Einstein; carrier has no model rights
\\n\\n
\\n

Recommendation: Private AI Build — the only option that provides full data sovereignty (required for GLBA), built-in NAIC 668 documentation, PHI anonymization, and carrier-specific fine-tuning. Year 2+ economics are significantly better than ongoing SaaS licensing with no IP to show for it.

\\n
\\n\\n
\\n\\n \\n

Section 9 — Next Steps

\\n\\n
\\n

This assessment represents the scope of work included in Vermont AI Systems' $7,500 AI Readiness Assessment engagement — already completed for this fictional firm profile.

\\n

What happens next if you engage:

\\n
    \\n
  1. Discovery call (60 minutes): We review your specific product mix, current AI tool inventory, agent network structure, and data flows. Scope is refined against your actual environment.
  2. \\n
  3. On-site or remote assessment (1–2 days): We interview underwriting, claims, compliance, and IT leadership. We map your actual data flows and classify by GLBA/NAIC sensitivity level.
  4. \\n
  5. Delivery (10 business days post-assessment): You receive a full deliverable identical in format to this sample, customized for your carrier — with your specific risks, your actual AI tool inventory, your data flows, and a custom roadmap tied to your regulatory calendar.
  6. \\n
  7. Build engagement (optional): If you choose to proceed with private AI build, we scope and execute the implementation on the timeline above.
  8. \\n
\\n
\\n\\n
\\n

This is a sample. Your assessment will be different.

\\n Start at /book-audit →\\n

\\n Or reach us directly: hello@vermontaisystems.com · (802) 555-0192\\n

\\n
\\n\\n
\\n\\n
\\n

Ready to see what your actual risks look like?

\\n

The discovery call is 30 minutes. We'll tell you what your assessment would cover, what it would find, and what it would cost.

\\n Book a Free 30-Min Discovery Call →\\n
\\n\\n \\n\\n