{ "version": "3.0", "updated": "2026-07-22", "context": { "service": "", "industry": "", "audience": "", "objective": "", "brand": "" }, "scoring": { "maximum_display_score": 99, "minimum_display_score": 35, "weights": { "primary_service_match": 38, "secondary_service_match": 22, "industry_match": 14, "audience_match": 10, "objective_match": 12, "brand_match": 4 }, "notes": [ "Scores rank presentation relevance; they do not rate project quality, commercial success, or guaranteed results.", "When no reader context is supplied, projects use a controlled editorial base score but the public card is labeled as a featured case study.", "Service matches carry the greatest weight because the reader’s stated business need is the primary personalization input." ] }, "projects": [ { "slug": "crevox-outcome-delivery-platform", "title": "CREVOX Outcome Delivery Platform", "short_title": "CREVOX Platform", "brand": "crevox", "client_display": "CREVOX", "industry": "technology-ai", "year": "2026", "status": "active", "record_type": "Internal product-platform case study", "confidentiality": "Controlled product strategy", "editorial_base_score": 90, "primary_services": [ "product-platform", "agentic-ai", "ai-governance" ], "secondary_services": [ "website-bxp", "workflow-automation", "data-architecture", "crm-revops", "client-portal" ], "audiences": [ "owner-founder", "executive", "operations", "technology-data" ], "objectives": [ "launch-product", "reduce-manual-work", "govern-ai", "improve-client-experience", "organize-knowledge" ], "technologies": [ "Agentic workflows", "Structured prompts", "Private data architecture", "Human approval gates", "Subscription product models", "API integrations" ], "summary": "CREVOX is an outcome-delivery platform and service ecosystem designed to combine AI intake, reusable capabilities, specialist workflows, tools, verification, and human review around finished business results.", "direct_answer": "CREVOX is designed to sell and deliver defined business outcomes rather than isolated prompts or unmanaged access to AI tools. The client receives a controlled service, workflow, or product with clear inputs, outputs, review, and accountability.", "challenge": "Many customers want completed results, not prompt files or another software tool they must learn. Selling raw prompts also creates weak protection, limited differentiation, inconsistent execution, and low accountability for output quality.", "constraints": [ "Protect reusable intellectual property without creating opaque or unreviewable systems.", "Support multiple delivery models: managed service, hosted tool, licensed capability, and subscription.", "Keep human review and client-specific context inside the process.", "Separate reusable core capabilities from confidential client data." ], "approach": [ "Define outcome categories and the workflows required to produce them.", "Break capabilities into governed prompts, tools, data requirements, agents, review gates, and output schemas.", "Create product tiers based on delivered outcome, user control, integration depth, and service level.", "Use shared registries for versions, ownership, quality, evidence, and permitted use." ], "solution": [ "A capability-driven AI product architecture.", "Managed outcome delivery instead of prompt-only commerce.", "Reusable workflow and agent components with client-specific context layers.", "Subscription, hosted, and service-based commercialization paths." ], "deliverables": [ "Business model and tier architecture", "Capability registry concepts", "Outcome delivery workflow", "Protection and licensing strategy", "Productization roadmap", "Governance and quality requirements" ], "outcomes": [ "CREVOX has a clearer strategic role as HCG's AI product and capability ecosystem.", "The model supports higher-value finished outcomes while protecting the underlying methods.", "Product development can now be organized around reusable capabilities, quality gates, and measurable delivery standards." ], "proof_assets": [ "CREVOX business strategy", "Tiered commercial model", "Capability and registry concepts", "Outcome-delivery workflow", "Related agent and platform specifications" ], "lessons": [ "Customers generally value reliable outcomes more than access to underlying prompts.", "Reusable intelligence becomes defensible when it includes data models, workflow, evaluation, governance, and integration.", "Human review is a product feature, not an implementation inconvenience." ], "next_stage": "Define the first three commercially packaged outcome products, build the shared capability registry, and validate delivery economics with controlled clients.", "hero_theme": "crevox", "seo_title": "Governed AI Outcome Delivery Platform Case Study | CREVOX", "meta_description": "How CREVOX packages AI intake, workflows, tools, human review, and delivery around finished business outcomes instead of isolated prompts.", "primary_query": "How can a business receive governed AI outcomes without managing prompts, models, agents, and technical infrastructure?", "reader_value": "This case study helps leaders evaluate an AI delivery model that reduces the need for internal prompt management, model selection, agent orchestration, and quality control.", "business_value": [ "Connects AI investment to a defined business outcome, owner, input, output, acceptance standard, and review process.", "Allows reusable AI capabilities to improve over time without exposing clients to unnecessary orchestration complexity.", "Supports productized, hosted, private, and human-reviewed delivery models according to the use case and risk." ], "authority_basis": "CREVOX builds on HCG’s work in business systems, process design, content, research, data, integrations, private and cloud AI, prompt governance, agent specifications, and human-reviewed client delivery.", "search_questions": [ { "question": "What business problem does CREVOX Platform address?", "answer": "CREVOX is designed to sell and deliver defined business outcomes rather than isolated prompts or unmanaged access to AI tools. The client receives a controlled service, workflow, or product with clear inputs, outputs, review, and accountability." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A capability-driven AI product architecture; Managed outcome delivery instead of prompt-only commerce; Reusable workflow and agent components with client-specific context layers." }, { "question": "What is the current status of CREVOX Platform?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. CREVOX has a clearer strategic role as HCG's AI product and capability ecosystem. The model supports higher-value finished outcomes while protecting the underlying methods." } ], "_relevance": 90 }, { "slug": "crevox-ffe-digital-twin", "title": "CREVOX AI-Native FF&E Digital Twin", "short_title": "CREVOX FF&E Digital Twin", "brand": "crevox", "client_display": "CREVOX / SHERPA ecosystem", "industry": "ffe-design", "year": "2026", "status": "active", "record_type": "Product development case study", "confidentiality": "Controlled product development", "editorial_base_score": 89, "primary_services": [ "product-platform", "agentic-ai", "data-architecture" ], "secondary_services": [ "workflow-automation", "client-portal", "ai-governance", "analytics-reporting", "integration-api" ], "audiences": [ "owner-founder", "operations", "technology-data", "client-service" ], "objectives": [ "launch-product", "support-decisions", "improve-data-trust", "reduce-manual-work", "improve-client-experience" ], "technologies": [ "Digital-twin data model", "PHP application", "Structured FF&E records", "AI assistance", "Role-based access", "VPS deployment" ], "summary": "The CREVOX FF&E Digital Twin extends SHERPA into an AI-native platform connecting project objects, specifications, decisions, quotes, vendors, logistics, installation, evidence, and status.", "direct_answer": "The CREVOX digital twin gives AI and project users a governed FF&E object model instead of asking them to interpret disconnected spreadsheets, PDFs, emails, drawings, quotes, and vendor portals without reliable relationships or context.", "challenge": "FF&E execution information is frequently scattered across spreadsheets, PDFs, emails, vendor portals, drawings, quotes, and project-management tools. That fragmentation weakens traceability and makes AI assistance unreliable because the system lacks a controlled project model.", "constraints": [ "Start with a focused first release rather than attempting a complete enterprise platform.", "Preserve the SHERPA source-of-truth definitions.", "Support role-based views without duplicating project data.", "Prevent AI suggestions from changing approved project facts without review." ], "approach": [ "Define the core FF&E entities, relationships, statuses, evidence, and approval states.", "Prioritize a small number of high-value workflows for the first release.", "Create AI assistance around approved project context rather than open-ended generation.", "Plan modular deployment on a controlled VPS environment." ], "solution": [ "A structured digital-twin model for FF&E projects.", "Role-based project and object views.", "Controlled AI support for search, summarization, exception identification, and next-action guidance.", "Foundation for quotes, specifications, approvals, logistics, installation, and warranty records." ], "deliverables": [ "Initial product definition", "Data and workflow model", "Application architecture", "Role and permission concepts", "AI-governance requirements", "Deployment plan" ], "outcomes": [ "The SHERPA operating model now has a defined path into a software platform.", "The product concept focuses on governed project objects and relationships rather than adding AI to unstructured files.", "The first release can validate high-value workflows before broader platform investment." ], "proof_assets": [ "Product specification", "Digital-twin model", "Deployment package concept", "Role-based workflow definitions" ], "lessons": [ "AI becomes more useful when project objects, statuses, evidence, and ownership are structured first.", "A digital twin should represent decision state and responsibility, not only product attributes.", "Platform scope should expand from validated workflows rather than from a complete feature wish list." ], "next_stage": "Deploy the focused first release, validate the core FF&E object model with live project scenarios, and prioritize the next workflow based on operational value.", "hero_theme": "twin", "seo_title": "AI-Native FF&E Digital Twin Case Study | CREVOX", "meta_description": "How the CREVOX digital twin connects FF&E products, specifications, decisions, quotes, vendors, logistics, installation, evidence, and project status.", "primary_query": "How can an AI-native FF&E digital twin connect products, specifications, decisions, logistics, installation evidence, and project status?", "reader_value": "This case study helps hospitality, design, procurement, and technology leaders evaluate why an AI-enabled FF&E platform must begin with a controlled project and data model.", "business_value": [ "Improves traceability between products, specifications, decisions, documents, vendors, logistics, installation, evidence, and status.", "Creates more reliable context for AI assistance, search, reporting, exception detection, and project communication.", "Allows the first release to validate high-value FF&E workflows before broader platform investment." ], "authority_basis": "The platform combines SHERPA’s FF&E governance model with CREVOX product architecture, structured data, digital-twin relationships, AI-assisted workflows, project evidence, and role-based experience design.", "search_questions": [ { "question": "What business problem does the CREVOX FF&E Digital Twin address?", "answer": "The CREVOX digital twin gives AI and project users a governed FF&E object model instead of asking them to interpret disconnected spreadsheets, PDFs, emails, drawings, quotes, and vendor portals without reliable relationships or context." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A structured digital-twin model for FF&E projects; Role-based project and object views; Controlled AI support for search, summarization, exception identification, and next-action guidance." }, { "question": "What is the current status of the CREVOX FF&E Digital Twin?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. The SHERPA operating model now has a defined path into a software platform. The product concept focuses on governed project objects and relationships rather than adding AI to unstructured files." } ], "_relevance": 89 }, { "slug": "sherpa-ffe-governance-system", "title": "SHERPA FF&E Governance + Execution System", "short_title": "SHERPA", "brand": "hcg-crevox", "client_display": "SHERPA FF&E", "industry": "ffe-design", "year": "2026", "status": "active", "record_type": "Client platform case study", "confidentiality": "Public and controlled materials", "editorial_base_score": 88, "primary_services": [ "product-platform", "workflow-automation", "data-architecture" ], "secondary_services": [ "website-bxp", "content-authority", "client-portal", "ai-governance", "research-diligence", "analytics-reporting" ], "audiences": [ "owner-founder", "executive", "operations", "client-service" ], "objectives": [ "reduce-manual-work", "support-decisions", "improve-client-experience", "organize-knowledge", "govern-ai" ], "technologies": [ "Google Workspace", "Structured SSOT documents", "PHP/JSON website architecture", "Specification workflows", "Role-based content", "AI-assisted research" ], "summary": "HCG and CREVOX developed SHERPA as a governed FF&E execution system that connects design intent, sourcing, procurement, logistics, installation, evidence, budget, schedule, and accountable decisions.", "direct_answer": "SHERPA converts fragmented FF&E handoffs into a governed operating model with defined roles, controlled decisions, source-of-truth project information, proof-backed communication, and role-specific visibility for owners, operators, designers, and project managers.", "challenge": "FF&E projects often distribute responsibility across design, sourcing, procurement, warehousing, logistics, installation, and project management. That fragmentation makes it difficult to identify who owns a decision, whether intent is being preserved, and where schedule, budget, or quality risk is accumulating.", "constraints": [ "Preserve the controlled SHERPA definition and prevent marketing copy from changing the operating model.", "Represent optional service spokes without redefining the core system.", "Support several audiences with different responsibilities and decision pressures.", "Do not make savings, performance, or outcome claims that are not supported by approved evidence." ], "approach": [ "Create and maintain a controlled single source of truth for the system, spokes, terminology, claims, and audience positions.", "Translate the operating model into public website pages, presentation structures, articles, and sales tools.", "Define governed spokes for procurement, warehousing and logistics, design, and related execution services.", "Structure future dashboards, quote/spec workflows, approvals, and role-based client access around shared project data." ], "solution": [ "A governance-centered market position for FF&E execution.", "Audience-specific pathways for owners, operators, designers, and project managers.", "Controlled service-spoke definitions that can expand scope without diluting the core.", "An evolving digital system for content, specifications, quotes, decisions, evidence, and client communication." ], "deliverables": [ "SHERPA SSOT and controlled definitions", "Website architecture and audience pages", "Design, procurement, and logistics spoke content", "Sales presentation research and structure", "Article authority system", "Dashboard and specification workflow concepts" ], "outcomes": [ "SHERPA now has a clearer category position centered on governance rather than vendor coordination.", "Core language, spoke definitions, and audience value can be reused across the website, sales materials, articles, and presentations.", "The project has established the foundation for a governed FF&E platform rather than a collection of disconnected marketing assets." ], "proof_assets": [ "Controlled SSOT", "Website and audience-page system", "Spoke definitions", "Sales presentation structure", "Quote/spec and dashboard concepts" ], "lessons": [ "Governance is a stronger and more defensible category than coordination when responsibility is fragmented.", "Every public claim must remain subordinate to the controlled source of truth.", "Role-specific framing improves relevance without changing the underlying operating model." ], "next_stage": "Complete the full public site, formalize proof and claims governance, and connect project data to role-based dashboards and client deliverables.", "hero_theme": "governance", "seo_title": "FF&E Governance and Execution System Case Study | SHERPA", "meta_description": "How HCG and CREVOX structured SHERPA to govern FF&E decisions, design intent, budget, logistics, evidence, and accountability.", "primary_query": "How can hotel and hospitality FF&E projects improve governance, accountability, design control, and execution?", "reader_value": "This case study helps hospitality and development leaders understand how FF&E risk accumulates across disconnected vendors, documents, approvals, logistics, and ownership gaps.", "business_value": [ "Protects design intent and product performance by linking decisions to accountable owners and supporting evidence.", "Improves visibility into budget, schedule, procurement, logistics, installation, and unresolved risk.", "Creates a repeatable operating model that can support services, content, dashboards, client deliverables, and future software capabilities." ], "authority_basis": "SHERPA combines HCG business-system design with CREVOX structured intelligence and governed workflow concepts. The work includes role-based website architecture, FF&E process governance, claims control, project data, content systems, and platform planning.", "search_questions": [ { "question": "What business problem does SHERPA address?", "answer": "SHERPA converts fragmented FF&E handoffs into a governed operating model with defined roles, controlled decisions, source-of-truth project information, proof-backed communication, and role-specific visibility for owners, operators, designers, and project managers." }, { "question": "What did HCG and CREVOX create or define?", "answer": "The defined solution includes the following components: A governance-centered market position for FF&E execution; Audience-specific pathways for owners, operators, designers, and project managers; Controlled service-spoke definitions that can expand scope without diluting the core." }, { "question": "What is the current status of SHERPA?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. SHERPA now has a clearer category position centered on governance rather than vendor coordination. Core language, spoke definitions, and audience value can be reused across the website, sales materials, articles, and presentations." } ], "_relevance": 88 }, { "slug": "crevox-financial-ops-sync", "title": "CREVOX Financial Ops Sync", "short_title": "Financial Ops Sync", "brand": "crevox", "client_display": "The Swimming Hole", "industry": "membership-nonprofit", "year": "2026", "status": "operational", "record_type": "Client automation platform case study", "confidentiality": "Client financial data remains private", "editorial_base_score": 87, "primary_services": [ "integration-api", "workflow-automation", "analytics-reporting" ], "secondary_services": [ "data-architecture", "ecommerce" ], "audiences": [ "executive", "operations", "technology-data" ], "objectives": [ "reduce-manual-work", "improve-data-trust", "support-decisions" ], "technologies": [ "Google Apps Script", "Google Sheets", "Square API", "QuickBooks Online API", "Amazon Business purchase parsing", "Scheduled jobs with checkpoint recovery" ], "summary": "CREVOX Financial Ops Sync is a self-healing financial operations platform that unifies Square sales, Amazon and QuickBooks purchases, inventory conversion, stock alerts, reordering, expense verification, and weekly profitability reporting for a seasonal member organization.", "direct_answer": "Financial Ops Sync assigns each system one source of truth — Square for what sold, purchase records for what came in — and bridges them through a governed product master, an append-only inventory ledger, guided conversion review, and scheduled reconciliation against QuickBooks Online.", "challenge": "Concession sales, Amazon and vendor purchases, inventory counts, bookkeeping, and profitability reporting lived in separate systems connected only by manual effort, making stock levels, unit costs, margins, and reorder timing difficult to trust.", "constraints": [ "Operate inside the organization's existing Google Workspace, Square, and QuickBooks Online environment.", "Require roughly ten minutes of owner attention per week rather than daily data entry.", "Never overwrite booked costs, corrections, or bookkeeper decisions with automated data.", "Keep financially sensitive push operations gated behind explicit human decisions." ], "approach": [ "Define one source of truth per record type, with a product master bridging every product across Square, QuickBooks, and Amazon listings.", "Automate the pipeline with eight scheduled jobs covering sales sync, inventory rebuilds, purchase imports, email parsing, verification sweeps, and reconciliation.", "Route ambiguous purchase conversions into a guided review queue with suggested mappings, variety-pack splits, and permanently learned rules.", "Build self-healing behavior with checkpointed resumes, recapture sweeps, exception logs, and failure alerting." ], "solution": [ "A governed inventory ledger that nets purchases against sales into live estimated stock, valuation, and cost of goods.", "Automated low-stock alerts, a standing reorder queue, and one-click stock pushes back to the Square register.", "QuickBooks Online reconciliation, quantity-adjustment worksheets, and concession expense verification with miscoding review.", "A weekly profitability report covering per-item units, revenue, weighted-average cost, gross profit, and margin." ], "deliverables": [ "Eight-trigger automation pipeline with checkpoint recovery", "Product master and variety-pack conversion engine", "Guided purchase-conversion review workflow", "Low-stock alerting and reorder queue", "QuickBooks reconciliation and expense verification tooling", "Weekly profitability reporting", "Versioned operations manual" ], "outcomes": [ "Sales, purchases, inventory, and accounting now reconcile through one governed pipeline instead of manual spreadsheet work.", "The owner's recurring workload dropped to roughly ten minutes of guided review per week.", "Profitability, stock health, and expense coding are reported automatically and are ready before board reporting." ], "proof_assets": [ "Live automation pipeline", "Versioned operations manual", "Conversion review workflow", "Profitability and reconciliation reports" ], "lessons": [ "Assigning one source of truth per record type prevents systems from silently competing over the same numbers.", "Automation should learn permanent rules from human review instead of asking the same question twice.", "Negative stock is a bug detector; flooring it without diagnosis hides mapping errors.", "High-impact financial pushes belong behind explicit human gates even when the code is ready." ], "next_stage": "Decide the gated QuickBooks posting model, extend receiving workflows, and continue consolidating operational tables toward a database-backed source of truth.", "hero_theme": "finance", "seo_title": "Financial Operations Automation Case Study | CREVOX", "meta_description": "How CREVOX Financial Ops Sync unifies Square sales, Amazon and QuickBooks purchases, inventory, alerts, reconciliation, and profitability reporting.", "primary_query": "How can a small organization automate inventory, purchasing, sales, and profitability reporting across Square, Amazon, and QuickBooks?", "reader_value": "This case study shows how a lean organization can run reconciled, self-healing financial operations across point-of-sale, purchasing, and accounting systems without hiring dedicated data staff.", "business_value": [ "Replaces hours of weekly manual reconciliation with a governed, self-healing automation pipeline.", "Makes stock levels, unit costs, margins, and reorder timing trustworthy enough to act on.", "Keeps bookkeeping, inventory, and point-of-sale systems aligned with visible exceptions instead of silent drift." ], "authority_basis": "HCG and CREVOX designed, built, and operate the full pipeline across Square, QuickBooks Online, Amazon Business, Gmail parsing, and Google Workspace, including conversion logic, reconciliation, alerting, and documented operating procedures.", "search_questions": [ { "question": "What business problem does CREVOX Financial Ops Sync address?", "answer": "Financial Ops Sync connects point-of-sale sales, purchase records, inventory, accounting, and reporting that previously required manual reconciliation, giving a seasonal organization trustworthy stock, cost, and margin data." }, { "question": "What did CREVOX create or define?", "answer": "The delivered system includes an eight-trigger automation pipeline, a product master and conversion engine, a guided purchase review workflow, low-stock alerts and a reorder queue, QuickBooks reconciliation tooling, and weekly profitability reporting." }, { "question": "What is the current status of CREVOX Financial Ops Sync?", "answer": "Operational. The platform runs in production with self-healing scheduled jobs, a versioned operations manual, and defined weekly and monthly operating rhythms for the owner and bookkeeper." } ], "_relevance": 87 }, { "slug": "crevox-prompt-capability-registry", "title": "CREVOX Prompt + Capability Registry", "short_title": "Prompt Registry", "brand": "crevox", "client_display": "CREVOX", "industry": "technology-ai", "year": "2026", "status": "defined", "record_type": "Internal governance case study", "confidentiality": "Controlled intellectual property", "editorial_base_score": 87, "primary_services": [ "ai-governance", "data-architecture" ], "secondary_services": [ "agentic-ai", "product-platform", "workflow-automation", "content-authority" ], "audiences": [ "technology-data", "operations", "executive" ], "objectives": [ "govern-ai", "organize-knowledge", "improve-data-trust", "launch-product" ], "technologies": [ "CSV/JSON registry", "Version control", "Prompt metadata", "Capability taxonomy", "Evaluation records", "Access rules" ], "summary": "CREVOX defined a prompt and capability registry that organizes reusable AI instructions, purpose, inputs, outputs, models, tools, versions, evaluations, ownership, risk, and execution interfaces.", "direct_answer": "The CREVOX registry converts an informal prompt library into a governed capability system. Each capability can be discovered, versioned, tested, approved, reused, monitored, and connected to broader workflows without exposing protected instructions unnecessarily.", "challenge": "As prompt and agent assets multiply, filenames and folders no longer provide enough control. Teams can lose track of versions, dependencies, permitted data, expected outputs, and whether a capability remains valid.", "constraints": [ "Support both simple prompts and multi-agent workflow specifications.", "Preserve human-readable short codes while enabling machine-readable execution.", "Track sensitive capabilities without exposing protected prompt text publicly.", "Allow phased migration from CSV to JSON and database-backed management." ], "approach": [ "Define a canonical metadata schema for prompts, workflows, agents, output types, and dependencies.", "Assign stable identifiers and human-friendly invocation codes.", "Separate public descriptions from protected instructions and credentials.", "Track versions, status, evaluations, owners, source documents, and deployment targets." ], "solution": [ "A reusable capability registry schema.", "CSV-to-JSON migration path.", "Version and status controls.", "Search, filtering, dependency, and evaluation fields.", "Foundation for future managed execution and APIs." ], "deliverables": [ "Registry schema", "Short-code structure", "CSV and JSON conversion model", "Governance phases", "Evaluation and ownership fields", "Deployment roadmap" ], "outcomes": [ "CREVOX capabilities can be treated as managed assets rather than scattered prompt documents.", "The registry creates a base for productization, agent orchestration, permissions, and quality reporting.", "Reusable instructions can remain protected while their purpose and interfaces remain discoverable." ], "proof_assets": [ "Prompt registry specification", "Short-code examples", "CSV-to-JSON structure", "Phased governance plan" ], "lessons": [ "A prompt library becomes operational only when version, ownership, inputs, outputs, and evaluations are controlled.", "Machine-readable metadata is required for reliable orchestration.", "Public capability descriptions and protected execution instructions should be separate records." ], "next_stage": "Implement the registry as a database-backed service with a controlled admin interface, evaluation history, and execution endpoints.", "hero_theme": "registry", "seo_title": "AI Prompt and Capability Registry Case Study | CREVOX", "meta_description": "How CREVOX turns prompts into versioned, searchable, testable, governed business capabilities with metadata, evaluation, and reuse.", "primary_query": "How can an organization manage prompts as versioned, testable, reusable, and governed AI capabilities?", "reader_value": "This case study is relevant to organizations whose prompts are scattered across chats, documents, individuals, and projects with no reliable version, ownership, evaluation, or reuse model.", "business_value": [ "Protects institutional AI knowledge from being lost inside individual accounts or undocumented conversations.", "Improves consistency and quality by connecting capabilities to versions, tests, approved models, tools, inputs, and outputs.", "Creates the foundation for reusable agents, services, applications, audits, and controlled AI delivery." ], "authority_basis": "CREVOX applies HCG’s experience with prompt libraries, reusable shortcodes, output standards, workflow specifications, private knowledge, model routing, and productized AI services to a formal capability-governance model.", "search_questions": [ { "question": "What business problem does Prompt Registry address?", "answer": "The CREVOX registry converts an informal prompt library into a governed capability system. Each capability can be discovered, versioned, tested, approved, reused, monitored, and connected to broader workflows without exposing protected instructions unnecessarily." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A reusable capability registry schema; CSV-to-JSON migration path; Version and status controls." }, { "question": "What is the current status of Prompt Registry?", "answer": "Defined specification. The project has a defined specification or framework and is not presented as a fully deployed production system. CREVOX capabilities can be treated as managed assets rather than scattered prompt documents. The registry creates a base for productization, agent orchestration, permissions, and quality reporting." } ], "_relevance": 87 }, { "slug": "sherpa-governance-portal", "title": "SHERPA Governance Portal + Service Spokes", "short_title": "SHERPA Governance Portal", "brand": "hcg-crevox", "client_display": "SHERPA FF&E", "industry": "ffe-design", "year": "2026", "status": "active", "record_type": "Client platform case study", "confidentiality": "Controlled client system", "editorial_base_score": 87, "primary_services": [ "client-portal", "product-platform", "workflow-automation" ], "secondary_services": [ "data-architecture", "analytics-reporting", "ai-governance", "integration-api" ], "audiences": [ "owner-founder", "executive", "operations", "client-service" ], "objectives": [ "improve-client-experience", "support-decisions", "reduce-manual-work", "launch-product" ], "technologies": [ "Role-based access", "Structured project data", "Decision and approval workflows", "Evidence records", "Dashboard views", "PHP/JSON application architecture" ], "summary": "HCG and CREVOX are building the SHERPA Governance Portal: a full client-facing system for FF&E project governance — decisions, approvals, evidence, budget, and schedule visibility — with service spokes that scope the portal to individual offerings such as Procurement.", "direct_answer": "The portal gives owners, operators, designers, and project managers role-based visibility into governed project state — who owns each decision, what evidence supports it, and where budget, schedule, or quality risk is accumulating — and can be adopted as the full system or as a single service spoke such as Procurement.", "challenge": "FF&E clients experience their projects through scattered emails, spreadsheets, and vendor portals, so governance value stays invisible; SHERPA needed a client-facing system that exposes decisions, evidence, and status without forcing every client into the full platform on day one.", "constraints": [ "Preserve the controlled SHERPA operating model as the portal's single source of truth.", "Support full-platform clients and single-spoke clients on one underlying architecture.", "Give each role visibility appropriate to its responsibilities without duplicating project data.", "Keep decision ownership, approvals, and evidence auditable." ], "approach": [ "Model FF&E projects as governed objects: decisions, approvals, specifications, quotes, evidence, budget, and schedule.", "Define role-based views for owners, operators, designers, and project managers.", "Design service spokes — starting with Procurement — that expose a scoped slice of the same architecture.", "Stage delivery so dashboards, approvals, and client communication build on shared project data." ], "solution": [ "A governance portal architecture with role-based project visibility.", "Decision, approval, and evidence workflows tied to accountable owners.", "Budget, schedule, and risk dashboards built on shared project data.", "Spoke-scoped portal experiences for individual services such as Procurement." ], "deliverables": [ "Portal architecture and role model", "Decision and approval workflow design", "Evidence and status data structures", "Procurement spoke definition", "Dashboard and client-communication concepts" ], "outcomes": [ "SHERPA's governance model now has a defined client-facing product rather than existing only in documents and process.", "Spokes let clients adopt a single service with a portal experience that can expand to the full system.", "Portal requirements are shaping how project data, evidence, and decisions are captured across the SHERPA ecosystem." ], "proof_assets": [ "Portal and role architecture", "Spoke definitions", "Workflow and dashboard concepts", "Shared project data structures" ], "lessons": [ "A governance operating model becomes commercially tangible when clients can see decisions, evidence, and status directly.", "Spokes expand adoption without diluting the core system definition.", "Role-based views must draw from one project record, or the portal recreates the fragmentation it exists to solve." ], "next_stage": "Expand spoke coverage, connect live project data to role-based dashboards, and formalize client onboarding for full-portal and single-spoke engagements.", "hero_theme": "portal", "seo_title": "FF&E Client Governance Portal Case Study | SHERPA", "meta_description": "How HCG and CREVOX are building SHERPA's role-based governance portal with decision, evidence, budget, and schedule visibility, plus service spokes.", "primary_query": "How can an FF&E execution company give clients role-based visibility into project decisions, evidence, budget, and schedule?", "reader_value": "This case study helps hospitality and project leaders evaluate what a client-facing governance portal requires — shared project data, accountable decisions, evidence, and role-based views — before buying or building one.", "business_value": [ "Makes governance visible and billable by exposing decisions, evidence, and status to clients directly.", "Lets clients start with one service spoke, such as Procurement, and expand into the full system.", "Reduces status meetings, email archaeology, and duplicated reporting through shared project data." ], "authority_basis": "The portal extends the SHERPA source-of-truth system, HCG's business-architecture and client-experience work, and CREVOX structured data and workflow design into a client-facing governance product for FF&E execution.", "search_questions": [ { "question": "What business problem does the SHERPA Governance Portal address?", "answer": "It replaces scattered emails, spreadsheets, and vendor portals with role-based client visibility into governed FF&E project state: decision ownership, supporting evidence, approvals, budget, schedule, and accumulating risk." }, { "question": "What did HCG and CREVOX create or define?", "answer": "A portal architecture with role-based views, decision and approval workflows, evidence and status structures, dashboards on shared project data, and service spokes — beginning with Procurement — that scope the portal to individual offerings." }, { "question": "What is the current status of the SHERPA Governance Portal?", "answer": "Active development. The architecture, role model, workflows, and Procurement spoke are defined and being built on the SHERPA platform, with dashboards and client onboarding staged next." } ], "_relevance": 87 }, { "slug": "crevox-agentic-spec-framework", "title": "CREVOX Agentic Delivery Framework", "short_title": "Agentic Delivery Framework", "brand": "crevox", "client_display": "CREVOX", "industry": "technology-ai", "year": "2026", "status": "defined", "record_type": "Internal delivery-framework case study", "confidentiality": "Controlled methodology", "editorial_base_score": 86, "primary_services": [ "agentic-ai", "ai-governance" ], "secondary_services": [ "business-strategy", "workflow-automation", "data-architecture", "product-platform" ], "audiences": [ "technology-data", "operations", "executive" ], "objectives": [ "govern-ai", "launch-product", "reduce-manual-work", "improve-data-trust" ], "technologies": [ "Agent specifications", "Role definitions", "Verification plans", "Human gates", "JSON intake", "Reusable skills" ], "summary": "The CREVOX Agentic Delivery Framework is a structured method for defining agent roles, data, tools, stages, verification, human approvals, risks, acceptance criteria, implementation, and reusable outputs before execution.", "direct_answer": "The framework prevents complex AI work from beginning as unstructured agent activity. CREVOX requires the business purpose, roles, inputs, tools, stages, quality gates, escalation, human ownership, and implementation handoff to be explicit.", "challenge": "Multi-agent and AI-assisted projects can generate impressive activity without clear ownership, deterministic inputs, quality standards, or a usable implementation handoff.", "constraints": [ "Remain model- and platform-flexible.", "Support both research and software implementation projects.", "Make human decision gates explicit.", "Produce artifacts usable by strategists, developers, operators, and reviewers." ], "approach": [ "Frame the problem and required business outcome.", "Define agents or roles and their responsibilities.", "Create a specification document, execution plan, and verification plan.", "Separate implementation stages with human review and acceptance gates.", "Evaluate which components should become reusable skills or registry capabilities." ], "solution": [ "A standard intake and scoping method.", "Role and responsibility architecture.", "Verification-first delivery planning.", "Human-gated implementation sequence.", "Skill and reuse assessment." ], "deliverables": [ "Framework specification v1.0", "JSON intake model", "Specification document structure", "Verification-plan template", "Implementation and QA gates", "Reuse assessment" ], "outcomes": [ "Complex agentic work has a reusable governance and handoff structure.", "The framework reduces ambiguity between research, specification, implementation, and approval.", "It creates a direct path from one-off project work into reusable CREVOX capabilities." ], "proof_assets": [ "Framework specification", "Role model", "Verification plan", "JSON intake structure", "Human-gate requirements" ], "lessons": [ "Agent count is not a measure of system quality.", "Verification and acceptance criteria should be designed before autonomous execution.", "Reusable skills emerge from controlled delivery, not from prematurely generalizing every task." ], "next_stage": "Apply the framework to selected CREVOX products and measure whether it improves delivery consistency, review time, and reuse.", "hero_theme": "agentic", "seo_title": "Agentic AI Workflow Specification Case Study | CREVOX", "meta_description": "How CREVOX specifies agent roles, tools, stages, verification, human approvals, quality gates, risks, and implementation handoffs.", "primary_query": "How should multi-agent and agentic AI workflows be specified, governed, verified, and handed off for implementation?", "reader_value": "This case study helps technical and business leaders distinguish a governed agentic workflow from a collection of loosely coordinated prompts and tool calls.", "business_value": [ "Reduces ambiguity between research, specification, implementation, verification, approval, and ongoing ownership.", "Creates auditable quality gates and human intervention points for multi-step AI-supported work.", "Converts one-off agent projects into reusable, maintainable capabilities and implementation assets." ], "authority_basis": "The framework formalizes CREVOX experience designing multi-stage AI workflows, specialist roles, prompt systems, tools, verification, output standards, human review, and reusable delivery frameworks.", "search_questions": [ { "question": "What business problem does the Agentic Delivery Framework address?", "answer": "The framework prevents complex AI work from beginning as unstructured agent activity. CREVOX requires the business purpose, roles, inputs, tools, stages, quality gates, escalation, human ownership, and implementation handoff to be explicit." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A standard intake and scoping method; Role and responsibility architecture; Verification-first delivery planning." }, { "question": "What is the current status of the Agentic Delivery Framework?", "answer": "Defined specification. The project has a defined specification or framework and is not presented as a fully deployed production system. Complex agentic work has a reusable governance and handoff structure. The framework reduces ambiguity between research, specification, implementation, and approval." } ], "_relevance": 86 }, { "slug": "golden-eagle-diligence-investor-platform", "title": "Golden Eagle Diligence + Investor Platform", "short_title": "Golden Eagle Platform", "brand": "hcg", "client_display": "Golden Eagle Golf Club initiative", "industry": "hospitality-golf", "year": "2026", "status": "active", "record_type": "Client diligence case study", "confidentiality": "Controlled and investor-specific materials", "editorial_base_score": 86, "primary_services": [ "research-diligence", "website-bxp", "analytics-reporting" ], "secondary_services": [ "data-architecture", "client-portal", "business-strategy", "ai-governance", "content-authority" ], "audiences": [ "owner-founder", "executive", "investor-advisor" ], "objectives": [ "support-decisions", "organize-knowledge", "improve-data-trust", "improve-client-experience" ], "technologies": [ "Controlled websites", "Google Workspace", "Structured assumptions register", "Scenario models", "Role-based access concepts", "AI-assisted research validation" ], "summary": "HCG created a controlled diligence and investor-communication platform for a destination private-club thesis, separating verified facts, assumptions, risks, scenarios, prohibited claims, and next-stage validation.", "direct_answer": "HCG organized market research, membership logic, asset and control questions, financial assumptions, development scenarios, evidence, and investor materials into one governed decision system that protects credibility while diligence remains incomplete.", "challenge": "A complex acquisition and development thesis needed to be credible enough to support next-stage diligence and investor conversations while substantial facts, rights, budgets, and operating assumptions remained unresolved.", "constraints": [ "Do not present directional scenarios as final investment returns or binding transaction terms.", "Distinguish active operations evidence from proof of future demand or development rights.", "Maintain alignment across business plan, pro forma, assumptions register, investor materials, and websites.", "Support different information rights for principals, advisors, investors, and diligence reviewers." ], "approach": [ "Define gate-specific decision standards and prohibited claims.", "Build modular research packets covering market, tourism, membership, asset control, hospitality alignment, financial logic, and risk.", "Create an assumptions register and scenario-builder logic tied to source evidence and validation needs.", "Translate the controlled thesis into executive, investor, diligence, and reference views." ], "solution": [ "A gate-controlled business-planning and diligence environment.", "Structured investor materials supported by a controlled evidence base.", "Scenario and assumption architecture that distinguishes evidence, management input, and unresolved validation.", "Role-based access design for decision-specific views." ], "deliverables": [ "Gate 1 business-plan website", "Research packets and research library", "Executive summary and investor presentation structures", "Assumptions register", "Scenario-builder logic", "Role-based access-control specification" ], "outcomes": [ "The project established a defensible path from thesis validation to deeper diligence and investor preparation.", "Research, assumptions, scenarios, and narrative were organized into one controlled decision architecture.", "The system reduces the risk of different documents presenting conflicting claims or unsupported certainty." ], "proof_assets": [ "Controlled Gate 1 website", "Assumptions register", "Research packet architecture", "Investor-support document set", "Role-based information model" ], "lessons": [ "Investor confidence depends as much on disciplined uncertainty as it does on a compelling vision.", "Assumptions must be visible, sourced, versioned, and connected to the documents that use them.", "Role-based presentation can simplify the experience without creating separate facts for separate audiences." ], "next_stage": "Complete Gate 2 diligence, validate transaction and development assumptions, and connect controlled investor views to updated financial and evidence registries.", "hero_theme": "diligence", "seo_title": "Golf Club Diligence and Investor Platform Case Study | HCG", "meta_description": "How HCG organized private-club market research, assumptions, risks, scenarios, evidence, and investor communication into a controlled system.", "primary_query": "How can a private golf club development organize diligence and investor communication without overstating unresolved assumptions?", "reader_value": "This case study shows how complex development and investment narratives can remain useful and persuasive without presenting unresolved facts or scenarios as certainty.", "business_value": [ "Creates a shared source of truth for research, assumptions, scenarios, risk, evidence, and investor-facing language.", "Reduces contradictions and unsupported claims across presentations, websites, financial summaries, diligence files, and executive decisions.", "Provides a gated path from initial thesis evaluation to deeper diligence, investor preparation, and controlled data-room delivery." ], "authority_basis": "HCG structured the project across market research, membership strategy, asset and control diligence, financial logic, risk, investor communication, websites, scenario tools, and document governance. The work demonstrates HCG’s ability to manage complex, assumption-sensitive business planning.", "search_questions": [ { "question": "What business problem does Golden Eagle Platform address?", "answer": "HCG organized market research, membership logic, asset and control questions, financial assumptions, development scenarios, evidence, and investor materials into one governed decision system that protects credibility while diligence remains incomplete." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: A gate-controlled business-planning and diligence environment; Structured investor materials supported by a controlled evidence base; Scenario and assumption architecture that distinguishes evidence, management input, and unresolved validation." }, { "question": "What is the current status of Golden Eagle Platform?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. The project established a defensible path from thesis validation to deeper diligence and investor preparation. Research, assumptions, scenarios, and narrative were organized into one controlled decision architecture." } ], "_relevance": 86 }, { "slug": "crevox-content-output-engine", "title": "CREVOX Governed Content Output Engine", "short_title": "Content Output Engine", "brand": "crevox", "client_display": "HCG, SHERPA, and related brands", "industry": "multi-industry", "year": "2026", "status": "active", "record_type": "Internal content-system case study", "confidentiality": "Controlled prompts and brand sources", "editorial_base_score": 85, "primary_services": [ "content-authority", "agentic-ai", "ai-governance" ], "secondary_services": [ "ai-visibility", "workflow-automation", "data-architecture", "product-platform" ], "audiences": [ "marketing-growth", "executive", "technology-data" ], "objectives": [ "increase-visibility", "organize-knowledge", "govern-ai", "reduce-manual-work" ], "technologies": [ "Structured prompts", "Brand voice systems", "SSOT documents", "Markdown/JSON output", "Citation controls", "Multi-stage validation" ], "summary": "CREVOX created a governed content-production system that converts approved sources, research, voice rules, templates, metadata, verification, and human review into website, Markdown, audio, social, presentation, and structured outputs.", "direct_answer": "The CREVOX content engine separates research, source validation, narrative, claims, formatting, metadata, quality review, and export so AI-assisted publishing remains consistent, reusable, and aligned with the approved source of truth.", "challenge": "AI-generated content often sounds generic, loses source-of-truth alignment, changes claims, uses repetitive structure, and produces formats that do not match the publishing system.", "constraints": [ "Preserve brand-specific voice without allowing style to override facts.", "Keep Word, Markdown, JSON, audio, and presentation structures distinct.", "Require citation and evidence controls where claims need support.", "Allow controlled reuse without exposing protected prompts." ], "approach": [ "Separate research and evidence collection from article composition.", "Use controlled source documents, claim rules, voice guidance, and output schemas.", "Validate the draft for factual alignment, repetition, structure, tone, and conversion role.", "Export the same governed content into channel-specific formats." ], "solution": [ "A multi-stage content workflow.", "Brand voice and source-of-truth controls.", "Format-specific templates and metadata.", "Research, citation, and quality gates.", "Reusable repurposing outputs." ], "deliverables": [ "SHERPA article-generation system", "Brand-voice-controlled outputs", "Markdown and JSON metadata templates", "Research prompt system", "Audio and social repurposing rules" ], "outcomes": [ "Content can be created with stronger consistency across brands and channels.", "Research, source control, narrative, and export are treated as separate responsibilities.", "The system creates a foundation for scalable authority publishing without relying on ungoverned one-shot generation." ], "proof_assets": [ "Article prompt system", "Markdown templates", "Metadata schemas", "Voice and validation rules", "Research and claims workflow" ], "lessons": [ "Voice is not a substitute for evidence.", "Different publishing formats require different structures even when they share the same source material.", "Organic paragraph rhythm and narrative flow require explicit quality review." ], "next_stage": "Connect the content engine to the capability registry, source libraries, editorial calendar, website CMS, and AI visibility measurement.", "hero_theme": "content", "seo_title": "Governed AI Content Production System Case Study | CREVOX", "meta_description": "How CREVOX turns approved sources, research, voice rules, templates, metadata, and review into reusable multi-format content.", "primary_query": "How can a business use AI to produce consistent, source-backed, multi-format content without generic output or claim drift?", "reader_value": "This case study helps brands evaluate how to scale content production without accepting generic language, unsupported claims, lost citations, inconsistent voice, or formats that do not match the publishing system.", "business_value": [ "Increases content reuse across website, articles, metadata, audio, social, sales, and presentation formats.", "Reduces claim drift and generic output by separating sources, research, writing, verification, formatting, and approval.", "Creates a scalable authority-publishing foundation that can connect to editorial calendars, CMS workflows, and AI visibility measurement." ], "authority_basis": "The content engine consolidates HCG and CREVOX work in research, source validation, brand-voice standards, article templates, structured metadata, Markdown and JSON outputs, audio scripts, social repurposing, and human-reviewed publishing.", "search_questions": [ { "question": "What business problem does Content Output Engine address?", "answer": "The CREVOX content engine separates research, source validation, narrative, claims, formatting, metadata, quality review, and export so AI-assisted publishing remains consistent, reusable, and aligned with the approved source of truth." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A multi-stage content workflow; Brand voice and source-of-truth controls; Format-specific templates and metadata." }, { "question": "What is the current status of Content Output Engine?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. Content can be created with stronger consistency across brands and channels. Research, source control, narrative, and export are treated as separate responsibilities." } ], "_relevance": 85 }, { "slug": "sherpa-public-website-platform", "title": "SHERPA Public Website + Content Platform", "short_title": "SHERPA Website Platform", "brand": "hcg-crevox", "client_display": "SHERPA FF&E", "industry": "ffe-design", "year": "2026", "status": "active", "record_type": "Client platform case study", "confidentiality": "Public site with controlled source materials", "editorial_base_score": 85, "primary_services": [ "website-bxp", "product-platform", "content-authority" ], "secondary_services": [ "ai-visibility", "workflow-automation", "data-architecture", "agentic-ai" ], "audiences": [ "owner-founder", "executive", "marketing-growth", "operations" ], "objectives": [ "modernize-website", "increase-visibility", "improve-client-experience", "organize-knowledge" ], "technologies": [ "Custom PHP framework", "Structured JSON content models", "Role-based page architecture", "AI-assisted content pipeline", "Schema.org structured data", "Content management tooling" ], "summary": "HCG and CREVOX built SHERPA's public-facing website on a custom framework with structured content management — a dynamic, AI-driven platform that turns the governed SHERPA operating model into audience-specific pages, service spokes, articles, and proof.", "direct_answer": "The SHERPA website is a custom-framework platform, not a brochure template. Pages, audiences, services, spokes, articles, and claims are generated from controlled structured content, so the public experience stays aligned with the governed source of truth and can be extended through AI-assisted workflows.", "challenge": "SHERPA's governance-centered positioning depends on precise, controlled language across several audiences and service spokes — a conventional CMS template could not keep marketing pages, definitions, and claims aligned with the operating model as the system grew.", "constraints": [ "Every public claim must remain subordinate to the controlled SHERPA source of truth.", "Serve owners, operators, designers, and project managers with role-specific paths on one content model.", "Support AI-assisted content generation without allowing style to change approved definitions.", "Remain fast, crawlable, and AI-readable for search and generative discovery." ], "approach": [ "Build a custom PHP framework with structured JSON content models for pages, services, spokes, audiences, and articles.", "Generate audience and service-spoke pages dynamically from the governed content registry.", "Connect an AI-assisted article and content pipeline governed by source-of-truth and voice controls.", "Add structured data, internal linking, and direct-answer formats for search and AI visibility." ], "solution": [ "A dynamic public website driven by structured, governed content.", "Role-based audience pathways and service-spoke pages.", "An article authority system fed by the governed content pipeline.", "Management tooling for updating content without breaking controlled definitions." ], "deliverables": [ "Custom website framework and content architecture", "Audience and service-spoke page system", "AI-assisted article production pipeline", "Structured data and AI-visibility layer", "Content management and update tooling" ], "outcomes": [ "SHERPA's public presence runs on the same governed definitions as its sales and operating materials.", "New audience pages, spokes, and articles can be added from structured content without redesign.", "The platform provides the foundation for the governance portal and client-facing systems." ], "proof_assets": [ "Live website architecture", "Structured content models", "Article production system", "Audience and spoke page templates" ], "lessons": [ "A governed brand needs a governed website; template CMS workflows quietly erode controlled language.", "Structured content is what lets AI assist publishing without changing approved claims.", "Role-specific pathways increase relevance without fragmenting the underlying content model." ], "next_stage": "Complete remaining spoke and audience pages, expand the article program, and connect the platform to the governance portal and client dashboards.", "hero_theme": "sherpa-web", "seo_title": "Dynamic AI-Driven Website Platform Case Study | SHERPA", "meta_description": "How HCG and CREVOX built SHERPA's public website on a custom framework with structured governed content, role-based pages, and AI-assisted publishing.", "primary_query": "How can a brand build a dynamic, AI-driven website that keeps marketing pages aligned with a governed operating model?", "reader_value": "This case study is relevant to leaders whose positioning depends on precise language and who need a website that scales content, audiences, and services without eroding controlled definitions.", "business_value": [ "Keeps public marketing, definitions, and claims aligned with the governed source of truth.", "Reduces the cost of adding audiences, services, spokes, and articles through structured content.", "Improves search and AI-assisted discovery with structured data and direct-answer formats." ], "authority_basis": "HCG and CREVOX designed and built the framework, content models, audience architecture, AI-assisted publishing pipeline, and governance controls, extending the SHERPA source-of-truth system into a live public platform.", "search_questions": [ { "question": "What business problem does the SHERPA Website Platform address?", "answer": "It keeps a governance-centered brand's public website aligned with its controlled operating model while supporting multiple audiences, service spokes, and an AI-assisted article program from one structured content system." }, { "question": "What did HCG and CREVOX create or define?", "answer": "A custom PHP framework with structured JSON content models, role-based audience pathways, dynamically generated service-spoke pages, an AI-assisted content pipeline, and structured data for search and AI visibility." }, { "question": "What is the current status of the SHERPA Website Platform?", "answer": "Active development. The platform and core architecture are built, with audience pages, spokes, and the article program expanding, and integration planned with the SHERPA Governance Portal." } ], "_relevance": 85 }, { "slug": "southend-reclaimed-digital-operations", "title": "Southend Reclaimed Digital Commerce + Operations System", "short_title": "Southend Reclaimed", "brand": "hcg", "client_display": "Southend Reclaimed", "industry": "ecommerce-retail", "year": "2026", "status": "active", "record_type": "Client modernization case study", "confidentiality": "Mixed public and internal workflows", "editorial_base_score": 85, "primary_services": [ "ecommerce", "data-architecture", "workflow-automation" ], "secondary_services": [ "website-bxp", "ai-visibility", "content-authority", "integration-api", "crm-revops" ], "audiences": [ "owner-founder", "marketing-growth", "operations", "technology-data" ], "objectives": [ "modernize-website", "increase-visibility", "reduce-manual-work", "improve-data-trust", "grow-qualified-pipeline" ], "technologies": [ "PHP", "JSON content", "Google Drive", "Google Sheets", "Google Apps Script", "Product enrichment workflows", "Google Ads", "CRM concepts" ], "summary": "HCG designed a connected digital commerce and operations system for Southend Reclaimed spanning website architecture, product authority, trade experience, campaign support, intake, product data, order information, and file automation.", "direct_answer": "HCG replaced isolated website, advertising, product, spreadsheet, and file-management tasks with a shared architecture that supports customer discovery, trade engagement, product configuration, lead attribution, and more reliable operational data.", "challenge": "The business needed stronger digital merchandising and lead pathways while product data, manufacturer exports, shipment records, intake details, and marketing content were distributed across systems and manual processes.", "constraints": [ "Represent complex custom and configurable products accurately.", "Preserve source data while creating usable public and internal views.", "Support consumer, trade, designer, and commercial buyer paths.", "Build incrementally within practical hosting and operational limits." ], "approach": [ "Plan a modular PHP/JSON website with AI-readable product and authority content.", "Define product-intake and enrichment structures for URLs, SKUs, finishes, fabrics, and configuration options.", "Automate selected Google Drive and Google Sheets workflows such as shipped-item tracking and manufacturer exports.", "Align campaigns, landing pages, product education, and future trade-portal functions." ], "solution": [ "A structured content and product architecture for a rebuilt website.", "Campaign-specific landing and authority pathways.", "Controlled intake and enrichment models for products and specifications.", "Scheduled operational exports and append-only record workflows." ], "deliverables": [ "Website rebuild architecture", "Advertising and landing-page strategy", "Trade-portal concept", "Product intake and enrichment model", "Manufacturer export automation", "Shipped-item file tracking workflow" ], "outcomes": [ "The modernization work now connects marketing requirements to the underlying product and operational data needed to support them.", "Repeated file and spreadsheet processes have defined automation paths and verification rules.", "The website plan can expand into trade, portal, and product-configuration functions without rebuilding the content model." ], "proof_assets": [ "Website specification", "Campaign and landing-page structures", "Apps Script workflows", "Product intake schemas", "Trade experience plan" ], "lessons": [ "Product authority depends on reliable product data, not only better copy.", "Marketing and operations should share identifiers, statuses, and source records.", "Append-only logs and explicit verification make automation safer in shared-drive environments." ], "next_stage": "Complete the website and trade architecture, consolidate product data, and connect lead intake, campaign attribution, and internal fulfillment records.", "hero_theme": "commerce", "seo_title": "Digital Commerce and Operations Modernization Case Study | HCG", "meta_description": "How HCG connected website strategy, product authority, trade leads, advertising, product data, files, orders, and internal automation.", "primary_query": "How can a reclaimed wood business connect its website, product data, trade leads, campaigns, orders, and operations?", "reader_value": "This case study is relevant to product businesses whose marketing, e-commerce, manufacturer data, order records, files, and reporting have evolved as separate systems.", "business_value": [ "Connects product authority and lead generation to the product, customer, order, and fulfillment data needed to support them.", "Reduces repetitive file handling, spreadsheet processing, and hidden reconciliation work through defined automation and validation.", "Creates a scalable foundation for trade portals, product configuration, campaign landing pages, and operational reporting." ], "authority_basis": "HCG’s work combines e-commerce strategy, digital merchandising, SEO and AI visibility, paid campaign support, custom PHP architecture, product data, Google Workspace automation, order systems, QuickBooks and HubSpot integration, and source-of-truth planning.", "search_questions": [ { "question": "What business problem does Southend Reclaimed address?", "answer": "HCG replaced isolated website, advertising, product, spreadsheet, and file-management tasks with a shared architecture that supports customer discovery, trade engagement, product configuration, lead attribution, and more reliable operational data." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: A structured content and product architecture for a rebuilt website; Campaign-specific landing and authority pathways; Controlled intake and enrichment models for products and specifications." }, { "question": "What is the current status of Southend Reclaimed?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. The modernization work now connects marketing requirements to the underlying product and operational data needed to support them. Repeated file and spreadsheet processes have defined automation paths and verification rules." } ], "_relevance": 85 }, { "slug": "custom-wordpress-plugin-suite", "title": "Custom WordPress Plugin Suite", "short_title": "WordPress Plugin Suite", "brand": "hcg", "client_display": "The Swimming Hole", "industry": "membership-nonprofit", "year": "2026", "status": "operational", "record_type": "Client product delivery case study", "confidentiality": "Licensed client software with documentation", "editorial_base_score": 84, "primary_services": [ "product-platform", "integration-api" ], "secondary_services": [ "workflow-automation", "ai-governance", "website-bxp" ], "audiences": [ "operations", "marketing-growth", "technology-data", "client-service" ], "objectives": [ "improve-client-experience", "reduce-manual-work", "launch-product" ], "technologies": [ "WordPress plugin development (PHP)", "National Weather Service API", "Twilio SMS", "Google Gemini retrieval-augmented answering", "Google Calendar integration", "Gutenberg blocks, shortcodes, and widgets" ], "summary": "HCG built a suite of custom WordPress plugins for a member organization: live weather with severe-alert email and SMS notifications, an AI-powered FAQ grounded entirely in site content, and a Google Calendar events and homepage alert system.", "direct_answer": "Instead of stitching together third-party subscriptions, HCG delivered licensed, documented plugins that run inside the client's own WordPress hosting: live National Weather Service conditions with gated staff notifications, a self-contained AI FAQ that answers only from indexed site content, and calendar-driven event and alert displays.", "challenge": "The organization needed timely weather and closure communication, self-service answers to member questions, and event visibility, without SaaS subscriptions, external databases, or unattended AI behavior on a public website.", "constraints": [ "Run entirely within the client's WordPress hosting with no external SaaS dependencies.", "Ground AI answers exclusively in the site's own content, with a no-answer fallback instead of guessing.", "Throttle, deduplicate, and gate staff notifications so alerts stay useful rather than noisy.", "Deliver each plugin with documentation, settings screens, test tools, and clean uninstall behavior." ], "approach": [ "Build the weather plugin on the National Weather Service API with layout options for full pages, sidebars, and header strips.", "Dispatch severe-alert email and Twilio SMS notifications with deduplication, severity thresholds, frequency limits, and operating-hours gating.", "Implement the AI FAQ as retrieval-augmented generation over indexed site content, with semantic caching, rate limits, and daily budget caps.", "Drive event listings and homepage alert strips from the organization's Google Calendar." ], "solution": [ "A weather plugin with live conditions, forecasts, alert banners, and gated email and SMS staff notifications.", "A grounded AI FAQ with source citations, visitor feedback, admin analytics, and a content-gap report.", "A calendar events plugin with reusable shortcodes for event pages and homepage alerts.", "Shared delivery standards: encrypted credentials, capability checks, caching, and documented licensing." ], "deliverables": [ "Weather plugin with alerts, Twilio SMS, and operating-hours gating", "AI-powered FAQ plugin with grounded retrieval and cost controls", "Google Calendar events and alerts plugin", "Settings screens, test tools, and admin analytics", "Installation, operations, and licensing documentation" ], "outcomes": [ "Members and staff see live conditions, alerts, events, and answers directly on the organization's own website.", "Severe-weather notifications reach staff by email and SMS only when relevant, with deduplication and operating-hours gating.", "Visitor questions are answered from approved site content with citations, and unanswered questions surface as a content-gap report." ], "proof_assets": [ "Three production plugins on the live site", "Plugin documentation and settings references", "Notification logs and admin analytics", "Testing checklists" ], "lessons": [ "Well-scoped custom plugins can replace multiple SaaS subscriptions and keep data on infrastructure the client controls.", "Notification systems need deduplication, throttling, and operating-hours context to stay trusted.", "Grounded retrieval with an explicit no-answer fallback is what makes an AI FAQ safe for a public website." ], "next_stage": "Extend the FAQ with curated answers and streaming responses, and package the plugins as reusable capabilities for other member organizations.", "hero_theme": "plugins", "seo_title": "Custom WordPress Plugin Suite Case Study | HCG", "meta_description": "How HCG built weather, alert, SMS, AI FAQ, and calendar plugins that run inside a member organization's own WordPress site with no SaaS dependencies.", "primary_query": "How can an organization add weather alerts, SMS notifications, an AI FAQ, and event calendars to WordPress without SaaS subscriptions?", "reader_value": "This case study is relevant to organizations that want owned, documented website capabilities — alerts, AI answers, and events — instead of accumulating third-party subscriptions and data-sharing risk.", "business_value": [ "Replaces multiple SaaS subscriptions with owned, licensed software running on existing hosting.", "Improves member communication with timely weather, closure, event, and alert information.", "Adds AI self-service that answers only from approved content, protecting accuracy and trust." ], "authority_basis": "HCG designed, developed, documented, and licensed all three plugins, including National Weather Service and Twilio integrations, retrieval-augmented AI answering with cost controls, Google Calendar integration, and WordPress block, shortcode, and widget delivery.", "search_questions": [ { "question": "What business problem does the WordPress Plugin Suite address?", "answer": "The plugins give a member organization live weather with gated alert notifications, AI answers grounded in its own content, and calendar-driven events and alerts, all running inside its own WordPress hosting without SaaS subscriptions." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "HCG delivered three licensed plugins: a weather plugin with email and Twilio SMS alerting and operating-hours gating, a grounded AI FAQ with caching, analytics, and cost controls, and a Google Calendar events and homepage alert plugin." }, { "question": "What is the current status of the WordPress Plugin Suite?", "answer": "Operational. All three plugins run in production on the client's website with settings screens, test tools, notification logs, documentation, and defined licensing and support boundaries." } ], "_relevance": 84 }, { "slug": "newtie-growth-revenue-operations", "title": "NewTie Growth Marketing + Revenue Operations System", "short_title": "NewTie RevOps", "brand": "hcg", "client_display": "NewTie", "industry": "corporate-gifting", "year": "2026", "status": "active", "record_type": "Growth and revenue case study", "confidentiality": "Controlled sales data", "editorial_base_score": 84, "primary_services": [ "crm-revops", "content-authority", "website-bxp" ], "secondary_services": [ "ai-visibility", "workflow-automation", "ecommerce", "analytics-reporting", "ai-governance" ], "audiences": [ "owner-founder", "marketing-growth", "sales-revenue", "operations" ], "objectives": [ "grow-qualified-pipeline", "modernize-website", "increase-visibility", "reduce-manual-work", "support-decisions" ], "technologies": [ "Google Workspace", "CRM architecture", "LinkedIn", "Structured lead research", "PHP/JSON website planning", "AI-assisted content workflows" ], "summary": "HCG designed a 90-day growth and revenue-operations system for NewTie that connects target-account research, buyer roles, content, website proof, intake forms, CRM discipline, outreach readiness, and weekly execution reporting.", "direct_answer": "HCG converted relationship-led business development into a governed revenue workflow with defined target accounts, role-based research, prepared outreach, authority content, proof, lead capture, follow-up ownership, and executive visibility.", "challenge": "NewTie needed to move from relationship-led opportunity generation toward a repeatable premium corporate gifting and apparel growth system without reducing the brand to commodity e-commerce.", "constraints": [ "Maintain a premium, consultative market position.", "Support a small team with clear weekly tasks and accountability.", "Build qualified outreach rather than high-volume generic prospecting.", "Rebuild the website around examples and consultation rather than a large transactional catalog." ], "approach": [ "Define a 90-day growth marketing and revenue-operations plan with weekly tasks.", "Create target-company, role, event, and opportunity research structures.", "Plan a custom website emphasizing examples, use cases, hospitality, and corporate programs.", "Connect content, social activity, lead qualification, CRM fields, and follow-up status." ], "solution": [ "A target-account and lead-research system.", "A weekly revenue-operations cadence and status summary.", "A consultation-led website and content architecture.", "Defined spec-sheet and product-example formats supporting sales conversations." ], "deliverables": [ "90-day growth plan", "Weekly task and status structures", "Lead-targeting framework", "Website rebuild plan", "CRM and outreach workflow", "Product/spec-sheet templates", "LinkedIn and X content system" ], "outcomes": [ "Growth activity is now organized around qualified accounts, evidence, readiness, and follow-up rather than undifferentiated posting.", "The website, content, lead research, and sales workflow have a shared commercial purpose.", "Executive and team reporting can focus on blockers, decisions, and actions tied to pipeline movement." ], "proof_assets": [ "90-day plan", "Lead research system", "Weekly status model", "Website architecture", "Spec-sheet templates", "Content calendar review" ], "lessons": [ "Premium corporate gifting is sold through relevance, context, and trust, not only product breadth.", "Content should support target-account conversations and proof rather than operate as an isolated social calendar.", "Weekly reporting is useful only when it clarifies decisions, ownership, and movement toward qualified sales." ], "next_stage": "Complete the website build, establish CRM operating discipline, launch controlled outreach, and measure opportunity progression by target segment.", "hero_theme": "revenue", "seo_title": "Corporate Gifting Growth and Revenue Operations Case Study | HCG", "meta_description": "How HCG connected target-account research, content, website proof, lead intake, CRM, outreach, and weekly execution for NewTie.", "primary_query": "How can a premium corporate gifting company build a repeatable lead-generation and revenue-operations system?", "reader_value": "This case study shows how a premium service brand can create repeatable demand without reducing its offer to commodity e-commerce or undifferentiated social posting.", "business_value": [ "Aligns website content, target-account research, outreach, lead forms, and CRM around qualified commercial opportunities.", "Improves executive visibility into readiness, blockers, follow-up, ownership, and pipeline movement.", "Creates reusable campaigns and content assets for corporate gifting, branded apparel, hospitality, events, and relationship-driven buying." ], "authority_basis": "HCG combined B2B positioning, target-account research, content strategy, website architecture, lead intake, CRM and revenue operations, campaign sequencing, and weekly execution governance into one commercial system.", "search_questions": [ { "question": "What business problem does NewTie RevOps address?", "answer": "HCG converted relationship-led business development into a governed revenue workflow with defined target accounts, role-based research, prepared outreach, authority content, proof, lead capture, follow-up ownership, and executive visibility." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: A target-account and lead-research system; A weekly revenue-operations cadence and status summary; A consultation-led website and content architecture." }, { "question": "What is the current status of NewTie RevOps?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. Growth activity is now organized around qualified accounts, evidence, readiness, and follow-up rather than undifferentiated posting. The website, content, lead research, and sales workflow have a shared commercial purpose." } ], "_relevance": 84 }, { "slug": "crevox-hybrid-private-ai-routing", "title": "CREVOX Hybrid + Private AI Routing System", "short_title": "Hybrid AI Routing", "brand": "crevox", "client_display": "CREVOX infrastructure", "industry": "technology-ai", "year": "2026", "status": "active", "record_type": "Internal infrastructure case study", "confidentiality": "Controlled technical configuration", "editorial_base_score": 83, "primary_services": [ "agentic-ai", "integration-api", "ai-governance" ], "secondary_services": [ "data-architecture", "workflow-automation", "product-platform" ], "audiences": [ "technology-data", "operations", "executive" ], "objectives": [ "govern-ai", "reduce-manual-work", "improve-data-trust", "launch-product" ], "technologies": [ "OpenAI cloud models", "Ollama", "LM Studio", "Hermes Agent", "Local models", "Google Workspace OAuth", "Task routing" ], "summary": "CREVOX designed a hybrid AI routing strategy that selects cloud models, local models, private systems, tools, or specialist agents according to data sensitivity, capability, context, cost, latency, and verification requirements.", "direct_answer": "CREVOX avoids treating one model or provider as the correct answer for every task. The routing system evaluates the business and technical requirements, selects an appropriate execution path, and preserves logs, controls, and human review.", "challenge": "HCG and CREVOX use several cloud and local AI systems, but unmanaged tool proliferation increases cost, context fragmentation, privacy uncertainty, and inconsistent output quality.", "constraints": [ "Some local models have limited context windows and hardware capacity.", "Connected tools require secure authentication and scoped permissions.", "Sensitive data should not be sent to unnecessary providers.", "Routing decisions must remain observable and overridable." ], "approach": [ "Inventory models, context limits, costs, privacy characteristics, and tool access.", "Define task classes and routing rules.", "Use cloud models for high-complexity reasoning where appropriate and local models for controlled specialist tasks.", "Add verification, fallback, logging, and human approval requirements by risk class." ], "solution": [ "A model and tool capability matrix.", "Privacy- and risk-aware routing rules.", "Fallback and escalation paths.", "Shared authentication and connector strategy.", "Usage and quality monitoring concepts." ], "deliverables": [ "Hybrid routing architecture", "Model capability matrix", "Privacy and task classification", "Fallback strategy", "Connector and authentication requirements" ], "outcomes": [ "CREVOX has a clearer infrastructure direction for combining cloud quality with local control.", "Routing decisions can be based on business requirements rather than brand preference.", "The strategy supports future cost, privacy, and quality optimization across product workflows." ], "proof_assets": [ "Routing requirements", "Local and cloud model evaluations", "Context-window and hardware findings", "Connector setup plans" ], "lessons": [ "Local AI is not automatically private or useful; deployment, permissions, logs, and context still require governance.", "The best model is task-dependent.", "Routing systems need observable quality and cost data before automation can be trusted." ], "next_stage": "Implement a small routing gateway for selected task classes, log quality and cost, and validate privacy controls before broader adoption.", "hero_theme": "routing", "seo_title": "Hybrid and Private AI Model Routing Case Study | CREVOX", "meta_description": "How CREVOX routes work between cloud, local, private models, tools, and agents by privacy, capability, cost, context, and verification.", "primary_query": "How should a business route AI work between cloud models, local models, private systems, tools, and specialist agents?", "reader_value": "This case study helps organizations evaluate model choice as an operating architecture decision rather than a brand preference or one-time benchmark result.", "business_value": [ "Balances cloud-model capability with local or private control for sensitive, repetitive, or cost-sensitive work.", "Reduces tool sprawl and inconsistent output by applying explicit routing and verification rules.", "Creates a measurable path for optimizing quality, privacy, cost, latency, and maintainability across AI workflows." ], "authority_basis": "CREVOX routing work is grounded in HCG’s active use of cloud and local models, Ollama, LM Studio, private hardware, tools, APIs, prompt systems, specialist agents, and client privacy requirements.", "search_questions": [ { "question": "What business problem does Hybrid AI Routing address?", "answer": "CREVOX avoids treating one model or provider as the correct answer for every task. The routing system evaluates the business and technical requirements, selects an appropriate execution path, and preserves logs, controls, and human review." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A model and tool capability matrix; Privacy- and risk-aware routing rules; Fallback and escalation paths." }, { "question": "What is the current status of Hybrid AI Routing?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. CREVOX has a clearer infrastructure direction for combining cloud quality with local control. Routing decisions can be based on business requirements rather than brand preference." } ], "_relevance": 83 }, { "slug": "swimming-hole-operations-data-system", "title": "The Swimming Hole Operations + Member Data System", "short_title": "The Swimming Hole", "brand": "hcg", "client_display": "The Swimming Hole", "industry": "membership-nonprofit", "year": "2026", "status": "operational", "record_type": "Client operations case study", "confidentiality": "Member data remains private", "editorial_base_score": 83, "primary_services": [ "workflow-automation", "data-architecture", "analytics-reporting" ], "secondary_services": [ "integration-api", "client-portal", "ai-governance" ], "audiences": [ "executive", "operations", "technology-data", "client-service" ], "objectives": [ "reduce-manual-work", "improve-data-trust", "support-decisions", "improve-client-experience" ], "technologies": [ "Google Sheets", "Google Apps Script", "QuickBooks Online", "Square", "Amazon Business", "Scheduled jobs", "CSV integration" ], "summary": "HCG built an operational data and reporting system for The Swimming Hole that connects member and family records, check-in activity, guests, schedules, financial workflows, inventory inputs, exports, and recurring management reports.", "direct_answer": "HCG reduced dependence on manual reconciliation by defining shared identifiers, append-only records, scheduled exports, controlled caches, exception handling, API connections, and recurring operational reports across membership and business systems.", "challenge": "A volunteer-led seasonal organization relied on several data sources and repeated manual tasks for membership, gate activity, schedules, sales, expenses, inventory, and management communication.", "constraints": [ "Operate within a limited seasonal budget and volunteer governance structure.", "Protect member and family data.", "Work with existing Google Workspace, Square, QuickBooks, and Amazon Business processes.", "Keep workflows understandable and recoverable when staff or board roles change." ], "approach": [ "Define member, family, guest, and status relationships in controlled caches and exports.", "Automate recurring CSV generation, file cleanup, and summary reporting.", "Design accounting and inventory workflows around source transactions and periodic verification.", "Add locks, append-only records, exception handling, and clear scheduled-task ownership." ], "solution": [ "Automated member and family association workflows.", "Recurring operational and performance reporting.", "Defined Square, QBO, and Amazon Business integration logic.", "Inventory and cost-of-goods workflow design with verification points." ], "deliverables": [ "Member/family data automation", "Scheduled CSV exports", "Daily and weekly reporting logic", "QBO/Square accounting workflow", "Amazon Business purchasing flow", "Inventory conversion and reconciliation plan" ], "outcomes": [ "Core recurring data and reporting processes have been made more repeatable and visible.", "Shared identifiers and append-only records reduce the chance of silent overwrites or lost status changes.", "The organization has a clearer roadmap for connecting sales, expenses, inventory, membership, and executive reporting." ], "proof_assets": [ "Apps Script automations", "Scheduled export logic", "Reporting structures", "Accounting workflow specifications", "Exception and lock-handling updates" ], "lessons": [ "Small organizations need governance and recoverability as much as large organizations do.", "Automation should expose exceptions instead of concealing them.", "Seasonal operations benefit from documented reset, archive, and handoff procedures." ], "next_stage": "Consolidate the core operational tables in a database, keep Google Sheets as governed views, and complete accounting and inventory reconciliation automation.", "hero_theme": "operations", "seo_title": "Membership Operations and Data Automation Case Study | HCG", "meta_description": "How HCG connected membership, family records, check-in, guest activity, finance, inventory, schedules, and recurring reporting.", "primary_query": "How can a seasonal member organization connect membership, check-in, finance, inventory, schedules, and management reporting?", "reader_value": "This case study helps member organizations and small operating teams evaluate how to modernize complex workflows without replacing every familiar tool at once.", "business_value": [ "Makes recurring member, attendance, guest, schedule, sales, expense, and reporting processes more repeatable and visible.", "Reduces silent overwrites and mismatched records through shared identifiers, append-only history, validation, and controlled data movement.", "Creates a practical path from spreadsheet-driven operations toward a database-backed source of truth while preserving usable staff views." ], "authority_basis": "HCG designed and maintained the connected workflows across Google Sheets, web applications, scheduled files, HubSpot, QuickBooks Online, Square, Amazon Business, reporting, and member operations. The project demonstrates hands-on integration and governance in a live seasonal environment.", "search_questions": [ { "question": "What business problem does The Swimming Hole address?", "answer": "HCG reduced dependence on manual reconciliation by defining shared identifiers, append-only records, scheduled exports, controlled caches, exception handling, API connections, and recurring operational reports across membership and business systems." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: Automated member and family association workflows; Recurring operational and performance reporting; Defined Square, QBO, and Amazon Business integration logic." }, { "question": "What is the current status of The Swimming Hole?", "answer": "Operational. The project is operational and the case study reports the current controlled system state. Core recurring data and reporting processes have been made more repeatable and visible. Shared identifiers and append-only records reduce the chance of silent overwrites or lost status changes." } ], "_relevance": 83 }, { "slug": "crevox-ai-intake-definition-system", "title": "CREVOX AI Opportunity Intake System", "short_title": "AI Opportunity Intake", "brand": "crevox", "client_display": "CREVOX / HCG delivery", "industry": "multi-industry", "year": "2026", "status": "defined", "record_type": "Internal service-system case study", "confidentiality": "Controlled methodology", "editorial_base_score": 82, "primary_services": [ "ai-governance", "business-strategy" ], "secondary_services": [ "agentic-ai", "workflow-automation", "data-architecture", "product-platform" ], "audiences": [ "owner-founder", "executive", "operations", "technology-data" ], "objectives": [ "govern-ai", "reduce-manual-work", "support-decisions", "launch-product" ], "technologies": [ "Structured intake", "Use-case scoring", "Risk classification", "Data inventory", "Human-gate planning", "Implementation roadmap" ], "summary": "The CREVOX AI Opportunity Intake System is a diagnostic and scoping method that defines the business problem, users, data, workflow, ownership, risk, feasibility, success criteria, pilot gates, and implementation path before AI solution design.", "direct_answer": "The intake system converts vague interest in AI into a controlled use-case definition and readiness decision. It determines whether AI is appropriate, what evidence and data are required, who owns the process, and what must be true before implementation.", "challenge": "Organizations often begin with a model, tool, or executive mandate instead of a defined operating problem. That leads to pilots without ownership, data readiness, adoption, evaluation, or measurable business value.", "constraints": [ "Remain vendor-neutral.", "Distinguish automation, analytics, search, generative AI, and agentic needs.", "Expose legal, privacy, security, and human-impact concerns early.", "Produce a practical next action even when AI is not the correct solution." ], "approach": [ "Capture the business pressure, current process, people, data, systems, frequency, cost, and failure modes.", "Classify the use case by value, feasibility, risk, data readiness, integration need, and governance burden.", "Identify the smallest test that can produce decision-quality evidence.", "Define ownership, human review, acceptance criteria, and stop conditions." ], "solution": [ "A structured AI opportunity intake.", "Readiness and risk scoring.", "Vendor-neutral solution classification.", "Pilot and implementation decision gates.", "Reusable output for proposals, specifications, and governance records." ], "deliverables": [ "Intake questionnaire", "Scoring model", "Risk and readiness classification", "Recommendation output", "Pilot gate structure" ], "outcomes": [ "HCG and CREVOX have a consistent method for qualifying AI opportunities before solution design.", "The system reduces pressure to force every problem into a generative-AI implementation.", "It creates better inputs for agentic workflow specification, product development, and client proposals." ], "proof_assets": [ "Intake methodology", "Question and scoring structure", "Output and recommendation model", "Connection to downstream specifications" ], "lessons": [ "The first AI decision is often whether AI is needed at all.", "Good intake prevents expensive technical debate around poorly defined problems.", "Risk, ownership, and evaluation should be first-class project inputs." ], "next_stage": "Implement the intake as a web diagnostic connected to the project registry, CRM, and the agentic delivery workflow.", "hero_theme": "intake", "seo_title": "AI Use-Case Readiness and Intake System Case Study | CREVOX", "meta_description": "How the CREVOX intake system evaluates business value, data, workflow, ownership, risk, governance, feasibility, and pilot readiness before AI buildout.", "primary_query": "How should a business evaluate whether an AI use case is valuable, feasible, and governable before building it?", "reader_value": "This case study is relevant to leaders who want to prevent AI pilots from beginning with a model, vendor, or executive mandate instead of a validated business problem.", "business_value": [ "Prevents poorly defined AI investments from advancing without value, ownership, data, workflow, risk, and acceptance criteria.", "Creates consistent inputs for solution design, agentic workflow specification, product development, budgeting, governance, and proposals.", "Allows HCG and CREVOX to recommend non-AI process or system changes when AI is not the proportionate solution." ], "authority_basis": "The intake system formalizes HCG and CREVOX experience defining AI projects, business requirements, source-of-truth maturity, workflow readiness, risk tiers, pilot gates, tool boundaries, maintenance, and executive go/no-go decisions.", "search_questions": [ { "question": "What business problem does the AI Opportunity Intake System address?", "answer": "The intake system converts vague interest in AI into a controlled use-case definition and readiness decision. It determines whether AI is appropriate, what evidence and data are required, who owns the process, and what must be true before implementation." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A structured AI opportunity intake; Readiness and risk scoring; Vendor-neutral solution classification." }, { "question": "What is the current status of the AI Opportunity Intake System?", "answer": "Defined specification. The project has a defined specification or framework and is not presented as a fully deployed production system. HCG and CREVOX have a consistent method for qualifying AI opportunities before solution design. The system reduces pressure to force every problem into a generative-AI implementation." } ], "_relevance": 82 }, { "slug": "hcg-ai-visibility-authority-system", "title": "HCG AI Visibility + Authority System", "short_title": "AI Visibility Authority System", "brand": "hcg", "client_display": "Hinson Consulting Group", "industry": "professional-services", "year": "2026", "status": "active", "record_type": "Internal authority-building case study", "confidentiality": "Public strategy", "editorial_base_score": 82, "primary_services": [ "ai-visibility", "content-authority" ], "secondary_services": [ "website-bxp", "analytics-reporting", "ai-governance", "research-diligence" ], "audiences": [ "owner-founder", "executive", "marketing-growth" ], "objectives": [ "increase-visibility", "organize-knowledge", "grow-qualified-pipeline", "modernize-website" ], "technologies": [ "Structured content", "JSON-LD", "Search Console", "GA4/GTM", "Prompt-query tracking", "Research governance" ], "summary": "HCG created an AI visibility and authority system that makes the company, services, frameworks, evidence, and expertise easier for search engines, AI assistants, and buyers to identify and understand.", "direct_answer": "HCG treats AI visibility as a combined search, entity, content, evidence, and measurement discipline. The system aligns technical SEO, clear business definitions, original expertise, proof, internal links, structured data, and conversion paths.", "challenge": "HCG had broad expertise across AI, websites, operations, data, marketing, and technology, but breadth can weaken market clarity. As discovery shifts toward AI-assisted research, unclear entity relationships and disconnected content make it harder for systems and buyers to understand what the company is authoritative about.", "constraints": [ "Avoid unsupported promises about ranking or inclusion in AI answers.", "Separate HCG authority from the identities of internal products and client initiatives.", "Keep content useful to executives while retaining technical credibility.", "Build a repeatable publishing system that does not depend on daily manual restructuring." ], "approach": [ "Define HCG's primary entities, services, frameworks, industries, projects, and leadership relationships.", "Create pillar, comparison, glossary, research, tool, and case-study content types.", "Structure each page around direct answers, definitions, proof, limitations, and next actions.", "Track AI referral traffic, prompt visibility, cited sources, branded demand, and qualified conversion." ], "solution": [ "A topic-cluster map focused on AI visibility, BXP, workflow intelligence, CRM/RevOps, and governed AI.", "Entity-consistent content and structured data templates.", "A proof library connected to specific claims and services.", "A publishing workflow that converts research into long-form, short-form, presentation, and AI-readable formats." ], "deliverables": [ "AI visibility strategy", "Content authority map", "Article and resource templates", "Entity and schema model", "AI visibility audit offer", "Measurement framework" ], "outcomes": [ "AI visibility is now positioned as a flagship HCG authority and lead-generation category.", "The system provides a controlled path for turning ongoing research and client work into reusable public authority.", "The strategy avoids separating GEO from technical SEO, content quality, entity clarity, and real-world proof." ], "proof_assets": [ "AI visibility research agenda", "Website architecture and page templates", "Structured resource model", "Audit and readiness-assessment concepts" ], "lessons": [ "AI visibility cannot compensate for a business that is difficult to describe or prove.", "Original frameworks and real artifacts create stronger authority than high-volume generic publishing.", "Measurement must distinguish visibility, referral, engagement, lead quality, and actual revenue influence." ], "next_stage": "Publish the first pillar cluster, establish an AI visibility baseline, and connect prompt monitoring to the website content registry.", "hero_theme": "visibility", "seo_title": "AI Visibility and GEO Authority System Case Study | HCG", "meta_description": "How HCG structures entities, expert content, proof, schema, internal links, and measurement to improve AI search and generative discovery.", "primary_query": "How can a business improve its visibility in AI search results, generative answers, and buyer research?", "reader_value": "This case study shows why AI visibility cannot be separated from technical search eligibility, useful content, clear entity relationships, real expertise, and evidence-backed brand authority.", "business_value": [ "Improves the chance that accurate HCG information enters AI-assisted research and vendor-comparison journeys.", "Creates a controlled way to convert research and client experience into reusable authority content.", "Connects visibility metrics to qualified traffic, lead quality, and commercial decision paths instead of treating citations as the only outcome." ], "authority_basis": "The system combines HCG experience in SEO, content strategy, website architecture, analytics, structured data, AI workflows, and real client implementation. It is continuously tested through HCG’s own website, content, projects, and AI visibility research.", "search_questions": [ { "question": "What business problem does AI Visibility Authority System address?", "answer": "HCG treats AI visibility as a combined search, entity, content, evidence, and measurement discipline. The system aligns technical SEO, clear business definitions, original expertise, proof, internal links, structured data, and conversion paths." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: A topic-cluster map focused on AI visibility, BXP, workflow intelligence, CRM/RevOps, and governed AI; Entity-consistent content and structured data templates; A proof library connected to specific claims and services." }, { "question": "What is the current status of AI Visibility Authority System?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. AI visibility is now positioned as a flagship HCG authority and lead-generation category. The system provides a controlled path for turning ongoing research and client work into reusable public authority." } ], "_relevance": 82 }, { "slug": "business-planning-research-portfolio", "title": "Business Plan + Feasibility Research Portfolio", "short_title": "Business Planning Portfolio", "brand": "hcg", "client_display": "Multiple clients (anonymized)", "industry": "multi-industry", "year": "2026", "status": "operational", "record_type": "Cross-client portfolio case study", "confidentiality": "Anonymized", "editorial_base_score": 81, "primary_services": [ "business-strategy", "research-diligence" ], "secondary_services": [ "analytics-reporting", "content-authority" ], "audiences": [ "owner-founder", "executive", "investor-advisor" ], "objectives": [ "support-decisions", "organize-knowledge" ], "technologies": [ "Market and competitive research", "Financial modeling", "Assumptions registers", "Scenario analysis", "Controlled document systems", "AI-assisted research validation" ], "summary": "HCG has completed business plans across a range of engagement levels — from lean internal validation plans to investor- and lender-ready packages — each matched to the decision, audience, research depth, and preparation requirements involved.", "direct_answer": "HCG scales business planning to the decision being made: a concept screen, an internal operating plan, a bank or lender package, or an investor-grade plan with market research, financial modeling, assumptions registers, risk analysis, and presentation materials.", "challenge": "Business plans are often written as one-size-fits-all documents that overstate certainty, mix evidence with assumption, and fail to match the level of research their audience actually requires.", "constraints": [ "Match research depth and document rigor to the audience and decision, not to a template.", "Keep facts, management input, assumptions, and unresolved questions visibly separate.", "Avoid presenting directional projections as guaranteed outcomes.", "Protect client confidentiality across all published examples." ], "approach": [ "Define the decision, audience, and evidence standard before outlining the plan.", "Conduct market, competitor, customer, regulatory, and operational research at the required depth.", "Build financial models with explicit assumptions, scenarios, and validation needs.", "Package the plan for its audience: executive summaries, lender documents, investor materials, or operating roadmaps." ], "solution": [ "A tiered planning methodology spanning concept validation through investor-grade documentation.", "Research packets, assumptions registers, and scenario models reused across engagements.", "Financial models connected to sourced evidence and stated uncertainty.", "Audience-specific deliverables that stay consistent with one controlled set of facts." ], "deliverables": [ "Business plans at multiple depth levels", "Market and competitive research packets", "Financial models and scenario analyses", "Assumptions and risk registers", "Executive, lender, and investor presentation materials" ], "outcomes": [ "Clients receive planning documents proportionate to their decision instead of overbuilt or under-evidenced templates.", "Research, assumptions, and financial logic stay aligned across every document a stakeholder sees.", "The portfolio methodology now underpins larger diligence systems such as the Golden Eagle investor platform." ], "proof_assets": [ "Anonymized plan structures", "Research packet architecture", "Assumptions register model", "Scenario model frameworks" ], "lessons": [ "The audience and decision define the plan; research depth is a scoping decision, not a default.", "Credibility comes from disciplined uncertainty as much as from a compelling narrative.", "Reusable research and assumption structures make each successive plan faster and more consistent." ], "next_stage": "Continue productizing the tiered planning offer with defined research levels, timelines, and evidence standards for each engagement type.", "hero_theme": "plans", "seo_title": "Business Plan and Feasibility Research Case Studies | HCG", "meta_description": "How HCG delivers business plans at multiple research depths — internal validation, lender packages, and investor-grade plans with models and risk registers.", "primary_query": "What level of research and preparation does a business plan need for internal, lender, or investor audiences?", "reader_value": "This case study helps founders and executives decide how much research, financial modeling, and documentation their planning decision actually requires before committing to a full engagement.", "business_value": [ "Matches planning investment to the decision, avoiding overbuilt documents and under-researched commitments.", "Keeps research, assumptions, financials, and narrative consistent across every stakeholder-facing document.", "Creates reusable research and modeling assets that accelerate later diligence and investor preparation." ], "authority_basis": "HCG has produced business plans, feasibility research, financial models, assumptions registers, and investor materials across hospitality, e-commerce, services, membership, and technology initiatives, including the gate-controlled Golden Eagle diligence platform.", "search_questions": [ { "question": "What business problem does the Business Planning Portfolio address?", "answer": "It matches business-plan research depth and preparation to the actual decision and audience — internal validation, lender review, or investor diligence — instead of producing one-size-fits-all documents that overstate certainty." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "HCG defined a tiered planning methodology with reusable research packets, assumptions registers, scenario models, and audience-specific deliverables spanning concept validation through investor-grade plans." }, { "question": "What is the current status of the Business Planning Portfolio?", "answer": "Operational. Multiple plans have been completed across engagement levels, and the methodology continues to be applied and productized across new client planning and diligence work." } ], "_relevance": 81 }, { "slug": "echoi-ai-boardroom-simulator", "title": "ECHOI AI Boardroom Simulator", "short_title": "ECHOI", "brand": "crevox", "client_display": "ECHOI", "industry": "technology-ai", "year": "2026", "status": "defined", "record_type": "Internal product concept case study", "confidentiality": "Controlled product strategy", "editorial_base_score": 81, "primary_services": [ "agentic-ai", "product-platform" ], "secondary_services": [ "business-strategy", "ai-governance", "analytics-reporting", "research-diligence" ], "audiences": [ "owner-founder", "executive", "investor-advisor" ], "objectives": [ "support-decisions", "launch-product", "govern-ai", "organize-knowledge" ], "technologies": [ "Multi-perspective agents", "Scenario analysis", "Decision records", "Evidence controls", "Human facilitation" ], "summary": "ECHOI is a CREVOX executive decision-support concept that uses controlled AI perspectives, evidence, assumptions, counterarguments, scenarios, and recorded judgments to challenge a decision before human approval.", "direct_answer": "ECHOI is designed to broaden and structure executive analysis without pretending that AI agents are directors, fiduciaries, or accountable human experts. The system surfaces missing evidence, dissent, risk, and alternative interpretations for human review.", "challenge": "Executives often need broader perspective and structured challenge, but informal AI chats can reinforce the user's framing, overlook missing evidence, or produce confident but unsupported recommendations.", "constraints": [ "Do not represent simulated roles as real licensed, fiduciary, or accountable professionals.", "Keep evidence, assumptions, inferences, and recommendations visibly separate.", "Require the human decision-maker to own final judgment.", "Support confidential business context without mixing it into public training or unrelated sessions." ], "approach": [ "Define boardroom roles by decision lens rather than personality imitation.", "Provide each role with controlled evidence, scope, and challenge responsibilities.", "Run staged analysis covering framing, evidence, alternatives, risks, dissent, and decision criteria.", "Produce a decision record that shows assumptions, unresolved questions, and final human action." ], "solution": [ "A multi-perspective executive simulation framework.", "Evidence and assumption controls.", "Structured dissent and pre-mortem stages.", "Human-owned decision record and follow-up plan." ], "deliverables": [ "Product concept", "Role architecture", "Decision-session workflow", "Evidence and assumption model", "Governance requirements", "Output format" ], "outcomes": [ "ECHOI has a defined role within CREVOX as a decision-support product rather than an autonomous decision-maker.", "The concept creates a repeatable method for surfacing blind spots, dissent, and unresolved evidence.", "It can share capabilities with research, diligence, strategy, and risk-analysis systems." ], "proof_assets": [ "Product definition", "Role and session architecture", "Decision-record concept", "Governance constraints" ], "lessons": [ "Simulated expertise must never be confused with accountable professional judgment.", "Useful executive challenge requires controlled disagreement, not a collection of agreeable summaries.", "Decision quality improves when assumptions and unresolved evidence remain visible." ], "next_stage": "Build a narrow prototype for one executive decision type and evaluate whether the process surfaces material issues that ordinary AI chat misses.", "hero_theme": "boardroom", "seo_title": "AI Boardroom Decision Simulator Case Study | ECHOI", "meta_description": "How ECHOI uses controlled AI roles, evidence, assumptions, counterarguments, and scenarios to pressure-test executive decisions.", "primary_query": "How can executives use AI to pressure-test decisions without treating AI as a fiduciary or final decision-maker?", "reader_value": "This case study is relevant to executives who want more rigorous AI-supported decision analysis without outsourcing responsibility or accepting confident output as evidence.", "business_value": [ "Creates a repeatable process for surfacing blind spots, counterarguments, assumptions, and unresolved evidence.", "Records how a decision was challenged and which issues remain subject to human judgment.", "Reuses governed research, risk, strategy, and scenario capabilities across executive decision types." ], "authority_basis": "ECHOI draws on HCG strategy, diligence, executive reporting, governance, and scenario work together with CREVOX role design, evidence controls, confidence handling, and human-in-the-loop AI methods.", "search_questions": [ { "question": "What business problem does ECHOI address?", "answer": "ECHOI is designed to broaden and structure executive analysis without pretending that AI agents are directors, fiduciaries, or accountable human experts. The system surfaces missing evidence, dissent, risk, and alternative interpretations for human review." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A multi-perspective executive simulation framework; Evidence and assumption controls; Structured dissent and pre-mortem stages." }, { "question": "What is the current status of ECHOI?", "answer": "Defined specification. The project has a defined specification or framework and is not presented as a fully deployed production system. ECHOI has a defined role within CREVOX as a decision-support product rather than an autonomous decision-maker. The concept creates a repeatable method for surfacing blind spots, dissent, and unresolved evidence." } ], "_relevance": 81 }, { "slug": "enterprise-data-migration-source-of-truth", "title": "Enterprise Data Migration + Source-of-Truth Architecture", "short_title": "Data Migration Architecture", "brand": "hcg", "client_display": "Confidential client", "industry": "multi-industry", "year": "2026", "status": "active", "record_type": "Anonymized technical case study", "confidentiality": "Anonymized", "editorial_base_score": 80, "primary_services": [ "data-architecture", "integration-api" ], "secondary_services": [ "workflow-automation", "analytics-reporting", "crm-revops", "ai-governance" ], "audiences": [ "executive", "operations", "technology-data" ], "objectives": [ "improve-data-trust", "reduce-manual-work", "support-decisions", "organize-knowledge" ], "technologies": [ "Google Sheets", "Relational database planning", "QuickBooks Online API", "HubSpot API", "Data dictionaries", "Migration staging" ], "summary": "HCG defined a source-of-truth and migration architecture that separates wholesale, retail, and order records from spreadsheet views, calculations, API references, temporary imports, and reporting logic.", "direct_answer": "HCG established which tables own business records, which spreadsheets remain governed views, how QuickBooks Online and HubSpot data connect, and what validation, history, and reconciliation are required before database migration.", "challenge": "Operational spreadsheets had evolved into a mixture of source records, derived views, assembly logic, and external references. That made migration risky because the visible workbook structure did not clearly reveal which data was authoritative.", "constraints": [ "Preserve business continuity while data models are redesigned.", "Separate core records from calculated or presentation-only tabs.", "Reconcile identifiers across QBO, HubSpot, orders, wholesale, and retail data.", "Create instructions detailed enough for later implementation in a coding environment." ], "approach": [ "Classify each table as source, derived view, assembly, or external reference.", "Define canonical records and relationships for wholesale, retail, and orders.", "Inventory API-sourced fields and synchronization responsibility.", "Stage migration through data dictionary, validation, schema, test import, reconciliation, and cutover gates." ], "solution": [ "A target relational data model and migration sequence.", "Clear ownership rules for records and derived views.", "Integration boundaries for QBO and HubSpot.", "Validation and reconciliation requirements before production cutover." ], "deliverables": [ "Migration planning document", "Source-system classification", "Target schema concepts", "Data dictionary requirements", "Validation and cutover sequence", "Implementation instructions" ], "outcomes": [ "The migration scope now distinguishes the actual database entities from the spreadsheets that display or assemble them.", "External API data is treated as governed integration input rather than copied spreadsheet content.", "The project has a staged path for moving from planning into coded implementation." ], "proof_assets": [ "Source classification", "Target architecture", "Migration phases", "Validation queue", "Implementation handoff instructions" ], "lessons": [ "A workbook is a user interface, not necessarily a data model.", "Migration begins with ownership and definitions, not with copying cells into tables.", "External-system records require identifier, refresh, error, and reconciliation rules." ], "next_stage": "Finalize the field-level data dictionary, create the database schema and staging scripts, and run a reconciled test migration before cutover.", "hero_theme": "data", "seo_title": "Spreadsheet to Database Migration Case Study | HCG", "meta_description": "How HCG defined source-of-truth tables, spreadsheet views, validation, APIs, and migration controls for wholesale, retail, and order data.", "primary_query": "How should a business move operational records from spreadsheets into a controlled source-of-truth database?", "reader_value": "This case study helps businesses distinguish a simple spreadsheet cleanup from a true data-ownership, migration, integration, and reporting architecture problem.", "business_value": [ "Clarifies which system owns each core record and prevents multiple files from silently competing as the source of truth.", "Preserves validation, identifiers, calculations, history, and external-system relationships during migration.", "Allows spreadsheets to remain useful analysis and operating views without carrying the full risk of database, workflow, and integration responsibilities." ], "authority_basis": "HCG applies practical experience with operational spreadsheets, relational data, APIs, QuickBooks Online, HubSpot, custom databases, migration validation, reporting, and staff-facing views. The approach balances control with the client’s actual maintenance capacity.", "search_questions": [ { "question": "What business problem does Data Migration Architecture address?", "answer": "HCG established which tables own business records, which spreadsheets remain governed views, how QuickBooks Online and HubSpot data connect, and what validation, history, and reconciliation are required before database migration." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: A target relational data model and migration sequence; Clear ownership rules for records and derived views; Integration boundaries for QBO and HubSpot." }, { "question": "What is the current status of Data Migration Architecture?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. The migration scope now distinguishes the actual database entities from the spreadsheets that display or assemble them. External API data is treated as governed integration input rather than copied spreadsheet content." } ], "_relevance": 80 }, { "slug": "accounting-commerce-api-automation", "title": "Accounting + Commerce API Automation", "short_title": "QBO + Commerce Automation", "brand": "hcg", "client_display": "Anonymized operating environments", "industry": "multi-industry", "year": "2026", "status": "operational", "record_type": "Cross-client technical case study", "confidentiality": "Anonymized", "editorial_base_score": 79, "primary_services": [ "integration-api", "workflow-automation" ], "secondary_services": [ "data-architecture", "analytics-reporting", "ecommerce" ], "audiences": [ "operations", "technology-data", "executive" ], "objectives": [ "reduce-manual-work", "improve-data-trust", "support-decisions" ], "technologies": [ "QuickBooks Online API", "Square", "Google Apps Script", "Scheduled jobs", "Pagination handling", "Reconciliation logic" ], "summary": "HCG developed governed integration patterns for QuickBooks Online, e-commerce, orders, payments, inventory, COGS, purchase records, and reporting so incomplete data and reconciliation exceptions remain visible.", "direct_answer": "HCG structures accounting and commerce automation around complete API retrieval, stable identifiers, explicit transaction rules, validation, exception queues, reconciliation, human review, and management reporting rather than assuming that a successful sync equals accurate accounting.", "challenge": "API-connected workflows can appear successful while silently missing pages, duplicating transactions, mishandling returns, or posting incomplete accounting data.", "constraints": [ "Prevent partial retrieval from being treated as complete data.", "Maintain a traceable connection between source transaction and accounting entry.", "Handle returns, adjustments, and periodic inventory checks.", "Keep retry and failure behavior visible to administrators." ], "approach": [ "Review API pagination, filters, date ranges, and record-count verification.", "Define source identifiers and idempotent processing rules.", "Map sales, cost of goods, refunds, and inventory adjustments to accounting actions.", "Create exception queues and reconciliation checks instead of relying only on successful job completion." ], "solution": [ "Complete paginated retrieval patterns.", "Transaction and accounting mapping rules.", "Append-only processing and verification logs.", "Exception and reconciliation reporting." ], "deliverables": [ "API correction", "Record-count verification", "Accounting workflow specification", "Return and inventory handling plan", "Exception-management logic" ], "outcomes": [ "Previously fragile integration points have explicit completeness and verification controls.", "Accounting automation is framed as a reconciled workflow, not a one-way data push.", "The patterns can be reused across HCG client integrations involving commerce, accounting, and reporting." ], "proof_assets": [ "Pagination correction", "Sync and retry logic", "Verification plan", "Accounting mapping workflow" ], "lessons": [ "A successful API response does not prove a complete dataset.", "Financial automation requires reconciliation and exception ownership.", "Idempotency and source identifiers should be designed before scheduled processing begins." ], "next_stage": "Package the integration controls into reusable connectors with centralized logs, alerts, and client-specific mapping configurations.", "hero_theme": "integration", "seo_title": "Accounting and E-commerce API Automation Case Study | HCG", "meta_description": "How HCG connects QBO, e-commerce, orders, payments, inventory, COGS, reconciliation, and reporting through governed API workflows.", "primary_query": "How can QuickBooks Online, e-commerce, orders, payments, inventory, and reporting be integrated without hidden reconciliation errors?", "reader_value": "This case study is relevant to businesses whose order-management, commerce, purchasing, inventory, payment, and accounting systems appear connected but still produce mismatched reports.", "business_value": [ "Reduces duplicate entry and repeated reconciliation work across commerce, order, purchasing, inventory, and accounting systems.", "Exposes missing, duplicated, unmatched, or incorrectly classified transactions before they distort management reporting.", "Creates repeatable integration patterns that can be monitored, corrected, and maintained instead of relying on opaque third-party sync behavior." ], "authority_basis": "HCG has worked directly with QuickBooks Online APIs, Square, Amazon Business, order-management spreadsheets, HubSpot, purchase orders, invoices, payments, journal entries, COGS, inventory, and reconciliation reporting across active client environments.", "search_questions": [ { "question": "What business problem does QBO + Commerce Automation address?", "answer": "HCG structures accounting and commerce automation around complete API retrieval, stable identifiers, explicit transaction rules, validation, exception queues, reconciliation, human review, and management reporting rather than assuming that a successful sync equals accurate accounting." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: Complete paginated retrieval patterns; Transaction and accounting mapping rules; Append-only processing and verification logs." }, { "question": "What is the current status of QBO + Commerce Automation?", "answer": "Operational. The project is operational and the case study reports the current controlled system state. Previously fragile integration points have explicit completeness and verification controls. Accounting automation is framed as a reconciled workflow, not a one-way data push." } ], "_relevance": 79 }, { "slug": "hcg-business-experience-platform-framework", "title": "HCG Business Experience Platform™ Framework", "short_title": "HCG BXP Framework", "brand": "hcg", "client_display": "Hinson Consulting Group", "industry": "professional-services", "year": "2026", "status": "active", "record_type": "Internal framework case study", "confidentiality": "Public methodology", "editorial_base_score": 78, "primary_services": [ "website-bxp", "business-strategy" ], "secondary_services": [ "ai-visibility", "workflow-automation", "crm-revops", "analytics-reporting", "client-portal" ], "audiences": [ "owner-founder", "executive", "marketing-growth", "operations" ], "objectives": [ "modernize-website", "improve-client-experience", "support-decisions", "grow-qualified-pipeline" ], "technologies": [ "PHP", "Structured JSON content", "CRM integrations", "GA4/GTM", "Schema.org", "Modular front-end components" ], "summary": "Hinson Consulting Group developed the Business Experience Platform™ Framework to turn a static website into a governed system for discovery, proof, conversion, CRM, automation, reporting, and client experience.", "direct_answer": "Hinson Consulting Group created BXPF to help businesses connect what buyers see on the website with the content, proof, intake, data, CRM, automation, reporting, and human-owned processes responsible for execution.", "challenge": "Traditional websites separate marketing pages from the operating systems that handle intake, qualification, delivery, reporting, and client communication. That separation creates inconsistent messaging, weak conversion paths, duplicated data, and limited visibility into what the site contributes to the business.", "constraints": [ "Keep the framework understandable to non-technical business leaders.", "Support lightweight PHP deployments as well as larger CMS or application architectures.", "Allow phased implementation without forcing every client into the same technology stack.", "Preserve accessibility, speed, maintainability, and human accountability." ], "approach": [ "Define the buyer questions and decision paths before selecting page layouts.", "Model content, proof, forms, services, projects, and calls to action as structured data.", "Connect public experience layers to CRM, automation, analytics, and client workflows.", "Use implementation gates so strategy, content, proof, build, and optimization are reviewed separately." ], "solution": [ "An experience architecture covering visibility, understanding, proof, conversion, delivery, and retention.", "Reusable page and component models driven by structured content.", "A measurement layer that connects page behavior to lead quality and downstream opportunity.", "A governance layer defining approved claims, content ownership, review dates, AI use, and system responsibility." ], "deliverables": [ "BXPF methodology and terminology", "Website source-of-truth structure", "Page, content, proof, and CTA models", "Phased implementation blueprint", "Analytics and CRM event architecture" ], "outcomes": [ "The framework now serves as HCG's primary method for planning modern websites and digital business systems.", "It creates a common language for strategists, designers, developers, content owners, and business leadership.", "It supports productized assessments, audits, implementations, and ongoing optimization without reducing the work to generic web design." ], "proof_assets": [ "Framework architecture", "Working website built from the framework", "Structured project and resource content models", "Readiness assessment and guided intake patterns" ], "lessons": [ "A website becomes strategically valuable only when content, proof, data, action, and follow-up operate as one system.", "Introducing the BXP term should follow a clear explanation of the buyer problem; the acronym should never lead the conversation.", "Structured content is necessary for reuse across websites, AI assistants, presentations, CRM, and future applications." ], "next_stage": "Complete the HCG website source of truth, connect the project system to CRM and analytics, and package BXPF as a defined client engagement.", "hero_theme": "system", "seo_title": "Business Experience Platform Framework Case Study | HCG", "meta_description": "How HCG connects websites, authority content, proof, intake, CRM, automation, reporting, and client experience through the BXPF framework.", "primary_query": "What is a Business Experience Platform, and how does it connect a website to CRM, automation, reporting, and client delivery?", "reader_value": "This case study helps business leaders evaluate whether a website problem is actually a broader content, conversion, data, workflow, or client-experience problem.", "business_value": [ "Creates a direct connection between marketing activity, lead capture, operational follow-up, and measurable business outcomes.", "Reduces duplicated content, fragmented intake, inconsistent proof, and disconnected system decisions.", "Provides a reusable architecture that can expand from an initial website into tools, portals, reporting, and controlled automation." ], "authority_basis": "HCG developed BXPF from cross-functional work spanning website strategy, e-commerce, marketing, CRM, APIs, data architecture, automation, reporting, client portals, and AI governance. The framework formalizes patterns already used across HCG client and internal systems.", "search_questions": [ { "question": "What business problem does HCG BXP Framework address?", "answer": "Hinson Consulting Group created BXPF to help businesses connect what buyers see on the website with the content, proof, intake, data, CRM, automation, reporting, and human-owned processes responsible for execution." }, { "question": "What did Hinson Consulting Group create or define?", "answer": "The defined solution includes the following components: An experience architecture covering visibility, understanding, proof, conversion, delivery, and retention; Reusable page and component models driven by structured content; A measurement layer that connects page behavior to lead quality and downstream opportunity." }, { "question": "What is the current status of HCG BXP Framework?", "answer": "Active development. The project is in active development; implemented and planned elements are distinguished in the documented current state. The framework now serves as HCG's primary method for planning modern websites and digital business systems. It creates a common language for strategists, designers, developers, content owners, and business leadership." } ], "_relevance": 78 }, { "slug": "crevox-developmental-intelligence-platform", "title": "CREVOX Developmental Intelligence Platform", "short_title": "Developmental Intelligence", "brand": "crevox", "client_display": "CREVOX research initiative", "industry": "technology-ai", "year": "2026", "status": "concept", "record_type": "Research and concept case study", "confidentiality": "Controlled research concept", "editorial_base_score": 77, "primary_services": [ "agentic-ai", "data-architecture", "research-diligence" ], "secondary_services": [ "ai-governance", "product-platform", "analytics-reporting" ], "audiences": [ "technology-data", "executive", "owner-founder" ], "objectives": [ "organize-knowledge", "govern-ai", "launch-product", "support-decisions" ], "technologies": [ "Evolving memory", "Association graphs", "Confidence scoring", "Context and intent models", "Sequence optimization" ], "summary": "CREVOX is researching a developmental intelligence layer that builds, scores, revises, and sequences evidence-backed associations across memory, context, intent, confidence, feedback, and repeated business use.", "direct_answer": "The concept explores how an AI system could maintain a governed model of relationships and learning over time instead of treating every interaction as an isolated prompt or relying on unexamined memory retrieval.", "challenge": "Conventional AI workflows often depend on fixed prompts and short-lived context. They can retrieve information, but they do not consistently maintain a governed model of how concepts relate, which associations are reliable, or how past outcomes should change future reasoning.", "constraints": [ "The underlying developmental theory remains exploratory and should not be presented as established neuroscience.", "Memory changes must be traceable, reversible, and permission-aware.", "Association strength cannot substitute for factual evidence.", "The system must distinguish user preference, hypothesis, inference, and validated fact." ], "approach": [ "Model concepts, experiences, evidence, and outcomes as associations with type, confidence, source, and recency.", "Continuously evaluate which associations improve task outcomes and which create error.", "Use context and intent to determine which memory paths should influence a given task.", "Require governance rules for promotion, decay, correction, privacy, and human review." ], "solution": [ "An evolving memory and association architecture.", "Confidence and evidence levels for knowledge relationships.", "Context-sensitive retrieval and sequencing.", "Continuous evaluation and correction loops.", "Governed distinction between fact, inference, theory, and preference." ], "deliverables": [ "Concept strategy", "Memory and association model", "Confidence and priority framework", "Governance principles", "Prototype research agenda" ], "outcomes": [ "The concept extends CREVOX beyond prompt execution toward persistent, evaluated organizational intelligence.", "It identifies memory governance and association quality as primary product requirements.", "It creates research questions that can be tested through narrow prototypes rather than asserted as finished science." ], "proof_assets": [ "Concept strategy", "Association and memory model", "Governance requirements", "Prototype roadmap" ], "lessons": [ "Persistent memory is valuable only when provenance, confidence, correction, and permission are controlled.", "Associative strength and factual truth are different dimensions.", "Developmental metaphors can guide product research but should not be overstated as scientific proof." ], "next_stage": "Build a small prototype that tracks evidence-backed associations for one business domain and measure retrieval quality, correction behavior, and decision usefulness.", "hero_theme": "intelligence", "seo_title": "Developmental AI Memory and Intelligence Concept | CREVOX", "meta_description": "A CREVOX research concept for governed associative memory, context, confidence, correction, and developmental learning across business interactions.", "primary_query": "How can AI systems develop governed associative memory and learning across repeated business interactions?", "reader_value": "This concept is relevant to organizations exploring persistent AI memory, institutional learning, correction, confidence, and context beyond one-session chat experiences.", "business_value": [ "Frames memory quality, evidence, association strength, correction, and governance as explicit product requirements.", "Creates testable research questions for narrow business prototypes instead of presenting an unvalidated concept as finished intelligence.", "Could improve continuity and reuse of organizational knowledge if the approach demonstrates measurable retrieval and decision value." ], "authority_basis": "The concept extends CREVOX work in hybrid memory, structured preferences, prompt registries, source control, confidence, reusable capabilities, and governed AI workflows. It remains a research concept until narrow prototypes validate the assumptions.", "search_questions": [ { "question": "What business problem does Developmental Intelligence address?", "answer": "The concept explores how an AI system could maintain a governed model of relationships and learning over time instead of treating every interaction as an isolated prompt or relying on unexamined memory retrieval." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: An evolving memory and association architecture; Confidence and evidence levels for knowledge relationships; Context-sensitive retrieval and sequencing." }, { "question": "What is the current status of Developmental Intelligence?", "answer": "Concept development. The project remains a research or concept-stage initiative and is presented as a testable direction rather than a completed product. The concept extends CREVOX beyond prompt execution toward persistent, evaluated organizational intelligence. It identifies memory governance and association quality as primary product requirements." } ], "_relevance": 77 }, { "slug": "hinson-trade-research-agent", "title": "Investment Research + Decision Support Agent", "short_title": "Investment Research Agent", "brand": "crevox", "client_display": "CREVOX / HCG internal use", "industry": "technology-ai", "year": "2026", "status": "defined", "record_type": "Internal agent specification case study", "confidentiality": "Private financial research workflow", "editorial_base_score": 74, "primary_services": [ "agentic-ai", "research-diligence" ], "secondary_services": [ "analytics-reporting", "ai-governance", "data-architecture" ], "audiences": [ "owner-founder", "executive", "technology-data" ], "objectives": [ "support-decisions", "organize-knowledge", "govern-ai" ], "technologies": [ "Market data inputs", "Research prompts", "Portfolio context", "Risk controls", "Structured reports", "Human decision gates" ], "summary": "This CREVOX research-agent specification structures market, company, sector, valuation, catalyst, risk, confidence, thesis, and watch-list analysis under human investment control.", "direct_answer": "The agent is designed as an evidence and decision-support workflow, not an autonomous trader. It requires current sources, explicit uncertainty, thesis history, risk, confidence, and human approval before any investment decision.", "challenge": "Market research is fast-changing and easy to distort through confirmation bias, stale information, unsupported predictions, or action-oriented language that exceeds the evidence.", "constraints": [ "Use current sources for market-sensitive information.", "Do not autonomously execute trades.", "Separate observation, analysis, scenario, and recommendation.", "Keep risk tolerance, time horizon, position size, and portfolio context explicit." ], "approach": [ "Define a repeatable research sequence for macro, sector, company, valuation, catalysts, risks, and technical context.", "Require source freshness and confidence labels.", "Generate clear buy, hold, avoid, watch, or sell research language only within stated assumptions.", "Track prior theses and update what changed rather than rewriting history." ], "solution": [ "A controlled research workflow.", "Structured research and watch-list outputs.", "Confidence, risk, and source-freshness fields.", "Human approval and no-execution boundaries." ], "deliverables": [ "Research agent specification v1.0", "Research-output schema", "Risk and confidence controls", "Learning and update prompts", "Implementation roadmap" ], "outcomes": [ "The project defines a reusable format for disciplined investment research.", "It positions the agent as an evidence and decision-support system rather than an autonomous trader.", "The specification can support future private dashboards and recurring research workflows." ], "proof_assets": [ "Agent specification", "README and output requirements", "Learning prompt concepts", "Risk controls" ], "lessons": [ "Fast-changing financial information requires explicit freshness and sourcing rules.", "An agent should preserve previous thesis history to expose drift and error.", "Decision support is safer and more useful than opaque autonomous action." ], "next_stage": "Implement a private prototype with current market-data connectors, thesis history, and a human-reviewed research dashboard.", "hero_theme": "trade", "seo_title": "Governed AI Investment Research Agent Case Study | CREVOX", "meta_description": "How the CREVOX research agent structures current market evidence, thesis, risk, confidence, catalysts, and watch lists without executing trades.", "primary_query": "How can an AI agent support investment research without executing trades or presenting uncertain information as financial certainty?", "reader_value": "This case study demonstrates how a high-stakes AI research workflow can preserve source freshness, uncertainty, human control, and repeatable decision structure.", "business_value": [ "Organizes fast-changing research into a repeatable evidence, thesis, risk, catalyst, and next-action format.", "Reduces confirmation bias by requiring counterevidence, confidence, and unresolved questions.", "Creates a specification for private dashboards and recurring research without allowing autonomous trade execution." ], "authority_basis": "The agent specification combines CREVOX agent specification, current-source research, confidence and risk controls, structured reporting, private workflow planning, and explicit human decision ownership.", "search_questions": [ { "question": "What business problem does the Investment Research Agent address?", "answer": "The agent is designed as an evidence and decision-support workflow, not an autonomous trader. It requires current sources, explicit uncertainty, thesis history, risk, confidence, and human approval before any investment decision." }, { "question": "What did CREVOX create or define?", "answer": "The defined solution includes the following components: A controlled research workflow; Structured research and watch-list outputs; Confidence, risk, and source-freshness fields." }, { "question": "What is the current status of the Investment Research Agent?", "answer": "Defined specification. The project has a defined specification or framework and is not presented as a fully deployed production system. The project defines a reusable format for disciplined investment research. It positions the agent as an evidence and decision-support system rather than an autonomous trader." } ], "_relevance": 74 } ] }