mail_kbanc_com
/
nice-gee
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Transform FAQ into AI Adoption FAQ derived from claims data 

Completely rewrote the FAQ page to focus on practical AI adoption questions answered with evidence from the claims library. This optimizes for search discovery and provides immediate value to visitors.

New Questions (Evidence-Based):
1. Why do 95% of companies see zero ROI from AI?
   - BCG data on 1,250 companies
   - Top 5% strategy: Focus on revenue functions

2. What's the typical ROI from AI adoption?
   - Department-specific data: 70% product teams report revenue increases
   - Real examples: Nike $11.8B→$23B, Voice AI 30% cost cuts

3. How long does AI implementation take?
   - Build vs buy timeframes (18-36 months vs quarters)
   - Specific examples from claims

4. What's the biggest mistake companies make?
   - Training vs workflow redesign
   - Thomson Reuters 100% adoption case
   - Costly mistakes: 99% cause losses, 42% abandoned

5. Which department should adopt AI first?
   - Revenue-driving functions with specific ROI data

6. Should we build custom AI or use existing tools?
   - Decision framework with timing/cost data
   - Calabrio 80% satisfaction increase case

7. What makes a good AI prompt?
   - 4-element framework with examples
   - Links to structured prompt approach

8. How big is the AI market opportunity?
   - Voice AI: $3.14B→$47.5B projection
   - Enterprise adoption: 78% of firms

9. How do I measure AI success?
   - Track dollars not hours
   - Specific metrics from top 5%

SEO/GEO Benefits:
✓ Answers actual search queries ("AI ROI", "AI implementation time")
✓ Every answer links to specific claim pages for evidence
✓ Question-based structure helps LLMs extract and cite
✓ Uses data from 24 articles across 120 claims
✓ Demonstrates expertise through evidence, not opinions

Old FAQ content (technical library usage) can be moved to /how-i-built-this page.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
This commit is contained in:
kbanc85 2025-11-09 16:24:02 -05:00
parent 0052ad1855
commit 76ac16b988
2 changed files with 146 additions and 198 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
public/feed.xml
View File

@ -5,7 +5,7 @@
<link>https://kbanc.com</link>
<description>Evidence-based claims about AI implementation, optimized for LLM extraction and research citation.</description>
<language>en-us</language>
<lastBuildDate>Sun, 09 Nov 2025 21:17:04 GMT</lastBuildDate>
<lastBuildDate>Sun, 09 Nov 2025 21:23:29 GMT</lastBuildDate>
<atom:link href="https://kbanc.com/feed.xml" rel="self" type="application/rss+xml"/>
<item>

342
src/app/faq/page.tsx
View File

@ -3,8 +3,8 @@ import Link from "next/link";
import { ArrowLeft } from "lucide-react";
export const metadata: Metadata = {
title: "FAQ | Kamil Banc",
description: "Frequently asked questions about the Claims Library and how to use atomic claims for AI-friendly content.",
title: "AI Adoption FAQ | Kamil Banc",
description: "Answers to the most common questions about AI implementation, ROI, adoption strategies, and avoiding costly mistakes. Evidence-based insights from real implementations.",
};
export default function FAQPage() {
@ -20,268 +20,216 @@ export default function FAQPage() {
Back to Home
</Link>
<h1 className="text-4xl font-bold mb-2 text-foreground">
Frequently Asked Questions
AI Adoption FAQ
</h1>
<p className="text-muted-foreground">
Everything you need to know about the Claims Library
Evidence-based answers to your AI implementation questions
</p>
</div>
</header>
<main className="container max-w-3xl mx-auto px-6 pb-12">
<div className="space-y-12">
{/* What is this? */}
{/* Strategy & ROI */}
<section>
<h2 className="text-2xl font-semibold mb-4">What is the Claims Library?</h2>
<h2 className="text-2xl font-semibold mb-4">Why do 95% of companies see zero ROI from AI?</h2>
<p className="text-foreground mb-4">
The Claims Library is a structured database of atomic, verifiable claims extracted from AI implementation research. Each claim is independently citable, making it perfect for LLMs to reference with precision.
BCG studied 1,250 companies and found 95% see zero measurable ROI despite high AI usage. The problem isn't adoption—it's selection.
</p>
<p className="text-foreground mb-4">
<strong>The mistake:</strong> Most companies automate busy work (email, scheduling, internal coordination) instead of revenue-generating functions.
</p>
<p className="text-foreground mb-4">
<strong>What works:</strong> The top 5% concentrate 70% of AI investment in five areas: R&D, sales, digital marketing, manufacturing, and IT infrastructure—functions that directly drive revenue or cut significant costs.
</p>
<p className="text-foreground">
Instead of vague summaries, you get specific, evidence-backed statements that can be verified, cited, and used in your own work.
<Link href="/claims-library/your-team-uses-ai-daily-and-you-still-see-no-roi" className="text-accent hover:underline">
Read the full evidence →
</Link>
</p>
</section>
{/* Why atomic claims? */}
<section>
<h2 className="text-2xl font-semibold mb-4">Why atomic claims instead of full articles?</h2>
<h2 className="text-2xl font-semibold mb-4">What's the typical ROI from AI adoption?</h2>
<p className="text-foreground mb-4">
<strong>Traditional content problem:</strong> Articles mix opinions, evidence, and filler. AI assistants struggle to extract and cite specific facts accurately.
</p>
<p className="text-foreground mb-4">
<strong>Atomic claims solution:</strong> Each claim is a single, verifiable statement with:
It varies by department, but here's what the data shows:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li>One specific assertion</li>
<li>Supporting evidence</li>
<li>Direct citation link</li>
<li>No ambiguity</li>
<li><strong>Product teams:</strong> 70% report revenue increases</li>
<li><strong>Supply chain:</strong> 20%+ cost reductions</li>
<li><strong>Voice AI:</strong> 20-30% more calls handled with 30-40% fewer agents, cutting costs 30%</li>
<li><strong>Marketing:</strong> ChatGPT file upload reduced weekly report prep from 3 hours to 20 minutes (89% time savings)</li>
<li><strong>Direct sales (Nike):</strong> Growth from $11.8B to $23B powered by AI</li>
</ul>
<p className="text-foreground">
This makes content AI-friendly while remaining human-readable.
The pattern: Revenue-generating and cost-heavy functions show measurable returns. Administrative functions don't.
</p>
</section>
{/* How to use */}
<section>
<h2 className="text-2xl font-semibold mb-4">How do I use these claims?</h2>
<div className="space-y-4">
<div className="bg-muted rounded-lg p-6">
<h3 className="font-semibold mb-2">1. Browse by Topic</h3>
<p className="text-foreground">
Use topic tags (Strategy, Tools, Business, Implementation, Measurement) to find relevant claims for your needs.
</p>
</div>
<div className="bg-muted rounded-lg p-6">
<h3 className="font-semibold mb-2">2. Copy Individual Claims</h3>
<p className="text-foreground">
Click the copy button next to any claim to get a properly formatted citation including author, year, and URL.
</p>
</div>
<div className="bg-muted rounded-lg p-6">
<h3 className="font-semibold mb-2">3. Reference in Your Work</h3>
<p className="text-foreground">
Use claims in presentations, reports, or give them to AI assistants as verified facts to work with.
</p>
</div>
<div className="bg-muted rounded-lg p-6">
<h3 className="font-semibold mb-2">4. Check Original Context</h3>
<p className="text-foreground">
Every claim links back to the full article for complete context and supporting research.
</p>
</div>
</div>
</section>
{/* Citation */}
<section>
<h2 className="text-2xl font-semibold mb-4">How do I cite these claims?</h2>
<h2 className="text-2xl font-semibold mb-4">How long does AI implementation take?</h2>
<p className="text-foreground mb-4">
Each claim page includes multiple citation formats:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4">
<li><strong>APA:</strong> For academic papers and research</li>
<li><strong>MLA:</strong> For essays and humanities work</li>
<li><strong>Chicago:</strong> For professional publications</li>
<li><strong>BibTeX:</strong> For LaTeX documents</li>
<li><strong>Plain text:</strong> For quick references</li>
</ul>
<p className="text-foreground mt-4">
The copy button next to each claim automatically formats it with proper attribution.
</p>
</section>
{/* Updates */}
<section>
<h2 className="text-2xl font-semibold mb-4">How often is the library updated?</h2>
<p className="text-foreground mb-4">
The Claims Library is automatically updated every 6 hours by checking the AI Adopters Club RSS feed for new articles.
</p>
<p className="text-foreground mb-4">
<strong>Automated process:</strong>
Depends on your approach:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li>Monitors RSS feed for new content</li>
<li>Filters out short posts and office hours</li>
<li>Extracts 5 atomic claims per article using AI</li>
<li>Validates claims for accuracy and specificity</li>
<li>Publishes with proper citations and metadata</li>
<li><strong>Build custom speech recognition:</strong> 18-36 months, millions in budget</li>
<li><strong>API integration:</strong> Ship features within quarters</li>
<li><strong>Acquire AI startups (Nike approach):</strong> 36 months vs typical 5 years to build capability</li>
<li><strong>Skill gap analysis with AI:</strong> 15 minutes per employee vs traditional weeks-long assessments</li>
</ul>
<p className="text-foreground">
Currently contains <strong>30 articles</strong> with <strong>150+ atomic claims</strong>.
<strong>Key insight:</strong> Buy vs build decisions determine whether you ship this quarter or spend years debugging.
</p>
</section>
{/* Source */}
{/* Common Mistakes */}
<section>
<h2 className="text-2xl font-semibold mb-4">Where do the claims come from?</h2>
<h2 className="text-2xl font-semibold mb-4">What's the biggest mistake companies make with AI?</h2>
<p className="text-foreground mb-4">
All claims are extracted from articles published on{" "}
<a
href="https://aiadopters.club"
target="_blank"
rel="noopener noreferrer"
className="text-primary hover:underline"
>
AI Adopters Club
</a>
, written by Kamil Banc.
<strong>Training instead of redesigning workflows.</strong>
</p>
<p className="text-foreground mb-4">
<strong>Content focus:</strong>
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4">
<li>Practical AI implementation strategies</li>
<li>Real-world case studies with measurable results</li>
<li>Enterprise AI adoption frameworks</li>
<li>ROI measurement and business impact</li>
<li>Tools and techniques that actually work</li>
</ul>
</section>
{/* License */}
<section>
<h2 className="text-2xl font-semibold mb-4">Can I use these claims in my work?</h2>
<p className="text-foreground mb-4">
Yes! All content is licensed under{" "}
<a
href="https://creativecommons.org/licenses/by/4.0/"
target="_blank"
rel="noopener noreferrer"
className="text-primary hover:underline"
>
Creative Commons Attribution 4.0 (CC BY 4.0)
</a>
.
Research shows employees already use AI 3x more than managers think. The capability exists—the environment doesn't support it.
</p>
<p className="text-foreground mb-4">
<strong>You can:</strong>
<strong>What doesn't work:</strong> Sending teams to training, creating AI guidelines, hoping people change habits through willpower.
</p>
<p className="text-foreground mb-4">
<strong>What works:</strong> Thomson Reuters hit 100% AI adoption by redesigning workflows to make AI the easiest path, not training people.
</p>
<p className="text-foreground mb-4">
Other costly mistakes:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li>Use claims in commercial and non-commercial projects</li>
<li>Adapt and build upon the content</li>
<li>Share and redistribute</li>
<li>99% of AI implementations cause financial losses (64% lose over $1M)</li>
<li>42% of AI initiatives abandoned in 2025 (up from 17%)</li>
<li>Companies waste $18M annually on unused software (only 47% of SaaS licenses actively used)</li>
</ul>
<p className="text-foreground">
<strong>You must:</strong> Provide attribution to "Kamil Banc, AI Adopters Club" with a link to the specific claim page.
<Link href="/claims-library/ai-adoption-isnt-a-training-problem-its-a-habit-problem" className="text-accent hover:underline">
Learn how to engineer adoption →
</Link>
</p>
</section>
{/* AI Training */}
{/* Which department */}
<section>
<h2 className="text-2xl font-semibold mb-4">Can I use this to train AI models?</h2>
<h2 className="text-2xl font-semibold mb-4">Which department should adopt AI first?</h2>
<p className="text-foreground mb-4">
Yes, with proper attribution. The structured format is specifically designed to be AI-friendly.
</p>
<p className="text-foreground mb-4">
<strong>Best practices:</strong>
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4">
<li>Include claim URLs in your training data</li>
<li>Maintain the claim-evidence structure</li>
<li>Preserve attribution metadata</li>
<li>Link back to original sources</li>
</ul>
</section>
{/* Contact */}
<section>
<h2 className="text-2xl font-semibold mb-4">How do I report an error or suggest improvements?</h2>
<p className="text-foreground mb-4">
Found something inaccurate? Have suggestions for better claims extraction?
</p>
<p className="text-foreground">
Contact Kamil Banc via{" "}
<a
href="https://www.linkedin.com/in/kbanc/"
target="_blank"
rel="noopener noreferrer"
className="text-primary hover:underline"
>
LinkedIn
</a>
{" "}or through{" "}
<a
href="https://aiadopters.club"
target="_blank"
rel="noopener noreferrer"
className="text-primary hover:underline"
>
AI Adopters Club
</a>
.
</p>
</section>
{/* Technical */}
<section>
<h2 className="text-2xl font-semibold mb-4">What technology powers this?</h2>
<p className="text-foreground mb-4">
The Claims Library uses a two-tier AI extraction system:
Focus on revenue-driving and cost-heavy functions:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li><strong>Claude Haiku:</strong> Fast metadata extraction (title, topics, key points)</li>
<li><strong>Claude Sonnet:</strong> High-quality claim extraction and validation</li>
<li><strong>R&D:</strong> Product teams using AI report 70% revenue increases</li>
<li><strong>Sales:</strong> Direct-to-consumer AI (like Nike) drove $11.2B growth</li>
<li><strong>Digital Marketing:</strong> Top 5% concentrate investment here</li>
<li><strong>Manufacturing/Supply Chain:</strong> 20%+ cost reductions</li>
<li><strong>Customer Support (Voice AI):</strong> 30% cost cuts, handle 20-30% more volume</li>
</ul>
<p className="text-foreground mb-4">
This hybrid approach optimizes for both speed (2-3x faster) and cost (19% savings) while maintaining quality.
</p>
<p className="text-foreground">
Built with Next.js, deployed on Netlify, fully static and fast.
<strong>Avoid starting with:</strong> Administrative functions, internal tools, email management—these show minimal ROI despite high usage.
</p>
</section>
{/* Tools vs Custom */}
<section>
<h2 className="text-2xl font-semibold mb-4">Should we build custom AI or use existing tools?</h2>
<p className="text-foreground mb-4">
<strong>Default to buying unless you have strategic reasons to build.</strong>
</p>
<p className="text-foreground mb-4">
The data is clear:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li><strong>Custom builds:</strong> 18-36 months, millions in budget (speech recognition example)</li>
<li><strong>API integration:</strong> Ship within quarters</li>
<li><strong>Calabrio case:</strong> Switched to specialist provider, increased satisfaction 80%, reduced developer time 62.5%</li>
</ul>
<p className="text-foreground mb-4">
<strong>When to build:</strong> Core competitive advantage (Rockstar's game AI), proprietary data moat, or specific capability unavailable in market.
</p>
<p className="text-foreground mb-4">
<strong>When to buy:</strong> Everything else. Especially transcription, voice AI, standard workflow automation.
</p>
</section>
{/* Prompt Engineering */}
<section>
<h2 className="text-2xl font-semibold mb-4">What makes a good AI prompt?</h2>
<p className="text-foreground mb-4">
Effective prompts specify four elements:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li><strong>Context:</strong> Background information and constraints</li>
<li><strong>Constraints:</strong> Budget limits, time limits, scope boundaries</li>
<li><strong>Output format:</strong> Exactly what you want delivered</li>
<li><strong>Exclusions:</strong> What to skip (as important as what to include)</li>
</ul>
<p className="text-foreground mb-4">
<strong>Bad prompt:</strong> "Analyze employee skills and recommend training."
</p>
<p className="text-foreground mb-4">
<strong>Good prompt:</strong> Interview-style prompt that collects complete information across 6 categories before generating recommendations—prevents AI from making costly assumptions.
</p>
<p className="text-foreground">
<Link href="/claims-library/ai-prompt-maps-employee-skill-gaps-one-session" className="text-accent hover:underline">
See the structured prompt approach →
</Link>
</p>
</section>
{/* Market Size */}
<section>
<h2 className="text-2xl font-semibold mb-4">How big is the AI market opportunity?</h2>
<p className="text-foreground mb-4">
Selected market projections:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li><strong>Voice AI:</strong> $3.14B (2024) → $47.5B (2034) — 34.8% annual growth</li>
<li><strong>Enterprise adoption:</strong> 78% of firms now using AI</li>
<li><strong>In-game AI (gaming):</strong> Microtransactions powered by AI drive 75% of Take-Two's net bookings</li>
</ul>
<p className="text-foreground">
But remember: 95% see zero ROI. Market size doesn't equal your returns—execution does.
</p>
</section>
{/* Measurement */}
<section>
<h2 className="text-2xl font-semibold mb-4">How do I measure AI success?</h2>
<p className="text-foreground mb-4">
<strong>Track dollars, not hours.</strong>
</p>
<p className="text-foreground mb-4">
Top 5% of companies measure:
</p>
<ul className="list-disc list-inside space-y-2 text-foreground ml-4 mb-4">
<li><strong>Revenue impact:</strong> Direct sales growth, customer lifetime value increase</li>
<li><strong>Cost reduction:</strong> Actual dollars saved (not time saved)</li>
<li><strong>Customer metrics:</strong> Satisfaction scores, retention rates</li>
<li><strong>Operational efficiency:</strong> Volume handled with fewer resources</li>
</ul>
<p className="text-foreground mb-4">
<strong>Don't measure:</strong> Time saved on emails, AI usage rates, training completion percentages. These correlate with zero ROI.
</p>
</section>
</div>
{/* CTA */}
<div className="mt-16 bg-accent/10 border-2 border-accent rounded-lg p-8 text-center">
<h2 className="text-2xl font-semibold mb-4">Ready to explore the claims?</h2>
<h2 className="text-2xl font-semibold mb-4">Want evidence-backed AI insights?</h2>
<p className="text-foreground mb-6">
Browse 30 articles with 150+ atomic, verifiable claims about AI implementation.
Explore 24 articles with 120 atomic claims about AI implementation, all derived from real case studies.
</p>
<Link
href="/claims-library"
href="/"
className="inline-flex items-center justify-center gap-2 whitespace-nowrap rounded-md text-sm font-medium ring-offset-background transition-colors focus-visible:outline-none focus-visible:ring-2 focus-visible:ring-ring focus-visible:ring-offset-2 h-10 px-6 py-2 bg-accent hover:bg-accent/90 text-accent-foreground"
>
Browse Claims Library
</Link>
</div>
</main>
{/* Footer */}
<footer className="bg-muted border-t-2 border-border py-8 mt-12 text-center">
<div className="container max-w-3xl mx-auto px-6">
<p className="text-sm text-muted-foreground">
© {new Date().getFullYear()} Kamil Banc. Licensed under{" "}
<a
href="https://creativecommons.org/licenses/by/4.0/"
target="_blank"
rel="noopener noreferrer"
className="text-primary hover:underline"
>
CC BY 4.0
</a>
</p>
</div>
</footer>
</div>
);
}