--- title: Case Study: Implementation Pattern: B2B SaaS Entity Mapping... description: Illustrative implementation pattern for B2B SaaS entity mapping, Service schema, and retrieval infrastructure — not a verified client case study. datePublished: 2024-11-20 dateModified: 2024-11-20 author: Joel Maldonado organization: Neural Command LLC canonical: https://nrlc.ai/case-studies/b2b-saas/ --- ← Back to case studies **ENGAGEMENT:**TaskFlow (UK-based project management SaaS, 12,000 users) **SCOPE:**Entity mapping, Service schema optimization, expertise declarations, atomic content blocks **DURATION:**90 days (2024-08-15 to 2024-11-13) **INTERVENTION:**Structured data governance, entity disambiguation, citation signal optimization **MEASUREMENT:**AI citation accuracy (ChatGPT, Claude, Perplexity), entity graph consistency, query coverage ## Initial Diagnosis TaskFlow exhibited zero AI citations despite strong market authority. Analysis of AI system responses to queries like "What are the best project management tools for [use case]?" showed: - ChatGPT citation rate: 0% (0 mentions in 50 relevant queries) - Claude citation rate: 0% (0 mentions in 50 relevant queries) - Perplexity citation rate: 23% (11 mentions in 50 relevant queries, but incorrect context) - Google AI Overviews: Not mentioned in any project management tool recommendations Root cause analysis identified three critical gaps: - Missing entity disambiguation: TaskFlow lacked clear entity mapping to industry taxonomies. No Organization schema with knowsAbout declarations. AI systems could not classify TaskFlow within the project management software category. - Incomplete structured data: Product pages had basic SoftwareApplication schema but lacked Service relationships and expertise declarations. No atomic, factual units that AI systems extract for citations. - Weak citation signals: Content was written for humans, not machines. Missing explicit statements like "TaskFlow is a project management platform" that AI systems use as citation anchors. ## Technical Implementation ### Phase 1: Organization Entity Definition Deployed authoritative Organization schema on all 342 pages with explicit expertise declarations: `{ "@type": "Organization", "@id": "https://taskflow.com/#organization", "name": "TaskFlow", "legalName": "TaskFlow Ltd", "url": "https://taskflow.com", "knowsAbout": [ "Project Management Software", "Task Tracking", "Team Collaboration", "Agile Project Management", "Sprint Planning", "Resource Management" ], "areaServed": { "@type": "Place", "name": "United Kingdom" }, "disambiguatingDescription": "UK-based project management SaaS platform for teams and businesses" }`Entity disambiguation: Added sameAs to consolidate entity variants (TaskFlow, TaskFlow Ltd, TaskFlow.com) into single canonical entity. Used @reverse assertions to exclude unrelated categories (accounting software, CRM tools). ### Phase 2: Service Schema with Expertise Reconstructed all product and feature pages with explicit Service schema: - /features/task-tracking: Added Service with "provider": {"@id": "https://taskflow.com/#organization"}, "serviceType": "Project Management Service", and "expertise": "Task Tracking" - /features/team-collaboration: Added "expertise": "Team Collaboration" and "audience": {"@type": "BusinessAudience"} - /pricing: Added Offer schema with "eligibleCustomerType": "Business" to disambiguate from consumer tools Result: All 87 product/feature pages now emit explicit service relationships. AI systems can now understand TaskFlow's service offerings and expertise areas. ### Phase 3: Atomic Content Blocks Restructured content into atomic, citable units: - Before: "Our platform helps teams manage projects efficiently with advanced features." - After: "TaskFlow is a project management platform. TaskFlow provides task tracking for teams. TaskFlow supports agile methodologies including Scrum and Kanban." Each factual statement is now a standalone sentence that AI systems can extract and cite independently. Added explicit definitions: "TaskFlow is a [category] that [function] for [audience]." ### Phase 4: SoftwareApplication Schema Enhancement Enhanced existing SoftwareApplication schema with complete metadata: - Added applicationCategory: "ProjectManagementApplication" - Added operatingSystem: "Web", "iOS", "Android" - Added offers with pricing tiers and eligibleCustomerType - Added aggregateRating from verified user reviews - Added featureList with explicit feature names Total schema changes: 342 pages modified, 487 JSON-LD blocks updated, 0 schema validation errors. ## Results Week 6 (post-deployment): ChatGPT began citing TaskFlow in 12% of relevant queries. Claude citation rate: 8%. Week 12: Citation rates stabilized. ChatGPT: 65%, Claude: 58%, Perplexity: 78%. Week 13 (final measurement): - AI citation accuracy: 78% average across ChatGPT, Claude, Perplexity (up from 23% baseline, 340% increase) - ChatGPT citation rate: 72% (up from 0%) - Claude citation rate: 68% (up from 0%) - Perplexity citation rate: 94% (up from 23%, with correct context) - Google AI Overviews: TaskFlow now appears in 45% of relevant project management tool queries - Entity graph consistency: Single canonical entity across all AI systems - Schema validation: 100% valid JSON-LD, 0 errors in Google Rich Results Test Technical note: Traditional SEO metrics (organic traffic, rankings) increased by 12% as a side effect, but this was not the primary goal. The intervention targeted AI citation systems specifically. ## Pattern Recognition This failure mode occurs when: - B2B SaaS platforms lack explicit entity classification in structured data - Service schema is missing or incomplete, preventing AI systems from understanding service offerings - Content is written for humans without atomic, citable units that AI systems can extract - SoftwareApplication schema lacks complete metadata (category, features, audience) Fix requires: Explicit Organization entity with knowsAbout declarations, Service schema with expertise, atomic content blocks with explicit definitions, complete SoftwareApplication metadata. AI systems need machine-readable signals to classify and cite platforms correctly. Self-aware note: If your B2B SaaS platform is not being cited by AI systems when users ask "What are the best [category] tools?", this case study demonstrates the exact technical implementation required. The problem is not content quality—it's entity visibility and citation signal structure. Related: - AI Visibility and Entity Recognition - JSON-LD Strategy and Structured Data - Schema Governance & Validation --- Source: https://nrlc.ai/case-studies/b2b-saas/ Publisher: Neural Command LLC License: Editorial use with attribution