Competitive Gap Analysis: Visyble vs Peec + Profound

Last generated: 2026-03-06 14:44 UTC
Coverage: 175 scraped pages (Peec Blog + Peec Docs + Profound Research + Profound Blog + Profound Engineering)

Direct links

• Product app: app.visyble.ai
• Backend API base: api.visyble.ai
• Frontend Main Sections: docs.visyble.ai/generated/frontend-main-sections
• Frontend API Usage Reference: docs.visyble.ai/generated/frontend-api-usage-reference
• API Endpoint Details: docs.visyble.ai/generated/api-endpoint-details

Scope and Methodology

• Source corpus is the mirrored content under downloads/competitor_content_20260306_152408 from: peec.ai/blog, docs.peec.ai, tryprofound.com/research, tryprofound.com/blog, and tryprofound.com/engineering.
• Visyble baseline uses existing internal docs (architecture, generated/frontend-main-sections, endpoint docs) in this VitePress repo.
• Signal extraction is performed one page at a time using full-page text parsing, then rolled up into capability clusters.
• Full one-by-one source inventory is available at Article-by-Article Inventory.
• Full coverage proof and traceability checks are documented in Coverage Audit and Traceability.

Current Visyble Capability Baseline (from existing docs)

• Existing surfaces: Answer Engine Insights, Prompt Volumes, Agent Analytics, Sources, Actions, Suggestions, Agents, Knowledge Bases, Brands, Settings.
• Existing backend contract is broad, but docs currently emphasize internal architecture over external product positioning and benchmark narratives.
• Several areas appear under-documented from generated docs perspective (for example Content has no discovered API flow).

Coverage Confirmation (Third Pass)

Source	Scraped HTML Pages	Processed Rows	Coverage
Peec Blog	22	22	100.0%
Peec Docs	34	34	100.0%
Profound Research	1	1	100.0%
Profound Blog	116	116	100.0%
Profound Engineering	2	2	100.0%

All scraped pages are now processed and used in evidence weighting for the missing-feature conclusions below.

Missing or Under-Documented Features in Visyble

1) Query Fanouts + Prompt Intent Layer

• Competitor signals: Profound repeatedly highlights query fanouts, prompt intent, and prompt recommendation intelligence.
• Visyble gap: current docs do not show a first-class fanout decomposition workflow or intent taxonomy exposed in the product.
• Recommended addition: Prompt Diagnostics module with fanout trees, intent labels, and source overlap traces.

2) Citation Category Intelligence + Benchmarks

• Competitor signals: both platforms invest heavily in citation, source gap, mention gap, and citation-rate benchmarks.
• Visyble gap: Sources exists, but docs do not yet define category taxonomy, benchmark baselines, or source-quality scoring.
• Recommended addition: source categories + benchmark dashboard + source-priority score model.

3) Hierarchical Entity Modeling (Brand -> Product -> Feature)

• Competitor signals: Profound publishes and ships asset hierarchy features for sub-asset tracking.
• Visyble gap: docs show Brands and Knowledge Bases, but no documented rollup hierarchy model.
• Recommended addition: entity hierarchy data model, rollup analytics, and hierarchy-aware filters across insights pages.

4) Content Optimization Workflow + CMS Connectors

• Competitor signals: content scoring, optimization products, and CMS integration loops are prominent.
• Visyble gap: Content section appears in navigation but generated docs currently discover no direct API surface.
• Recommended addition: measurable content score framework + API-backed workflow + connector roadmap.

5) Verticalized Commerce/Shopping Intelligence

• Competitor signals: dedicated shopping analyses and commerce-focused product narratives are frequent.
• Visyble gap: no explicit commerce package is documented (shopping trigger rates, product recommendation share, merchant visibility).
• Recommended addition: commerce intelligence template with shopping-specific KPIs and model-specific behavior tracking.

6) Enterprise Trust and Compliance Story in Docs UX

• Competitor signals: frequent SOC2/HIPAA/enterprise trust messaging appears in customer-facing materials.
• Visyble gap: enterprise trust posture is not yet a prominent docs section.
• Recommended addition: trust center docs area with compliance matrix, data handling, and access controls documentation.

7) Recurring Benchmark Publications and Index Artifacts

• Competitor signals: recurring benchmark and index-style reports shape category authority and buyer perception.
• Visyble gap: no dedicated benchmark hub or public methodology section in docs.
• Recommended addition: recurring benchmark program (monthly/quarterly) and docs section for methodology + archived reports.

Prioritized 90-Day Delivery Plan

Priority	Initiative	Why It Matters	Suggested Output
P0	Prompt Diagnostics (Fanouts + Intent)	Closes largest analytics differentiation gap	New APIs + dedicated UI pages + docs walkthrough
P0	Source Intelligence v2 (Categories + Benchmarks)	Turns source data into strategy levers	Taxonomy + benchmark panels + alerting
P1	Asset Hierarchies	Enables enterprise multi-entity analysis	Hierarchy model + rollup cards + filters
P1	Content Optimization Workbench	Creates closed loop from insight to action	Content score + recommendation execution flow
P2	Commerce Intelligence Pack	Expands vertical GTM relevance	Shopping KPI pack + model behavior reports
P2	Trust + Benchmark Center	Supports enterprise sales cycles	Trust center docs + recurring benchmark publication process

Detailed Reference

• Master Matteo + Peec + Profound consolidated feature catalog: Complete Reference and Feature Catalog
• Matteo + competitor + current-product consolidated status map: Product Features Roadmap Status
• Backend + frontend implementation execution roadmap: Backend Frontend Execution Roadmap
• Curated implementation-ready gap breakdown: Feature Gap Deep Dive
• Full one-by-one page inventory with extracted signals: Article-by-Article Inventory