AD Competitive Intelligence intent
internal prototype · canonical JSON + Dreamborn Forge HTML
internal generated
intent · supabase_json

AD Competitive Intelligence intent

AD needs a sellable competitive intelligence capability for its leadership and members. Public signals about large industrial distributors are available but fragmented across careers pages, service pages, press, investor material, filings, and trade coverage. AD needs those signals collected continuously, reviewed, and translated into credible actions before market pressure reaches members.

Planning Surface

Use this to decide what happens next.

Status

draft

problem

AD needs a sellable competitive intelligence capability for its leadership and members. Public signals about large industrial distributors are available but fragmented across careers pages, service pages, press, investor material, filings, and trade coverage. AD needs those signals collected continuously, reviewed, and translated into credible actions before market pressure reaches members.

success metrics
metrictarget
evidence_traceability100 percent of published insights include source_refs and source authority.
production_scopeGrainger and Fastenal monitored across careers, service/website pages, and at least one press/news/investor source family.
brief_qualityEach approved brief has 3 to 7 signals, each with observed fact, inference, implication, watch item, confidence, and source links.
operational_reliabilityScheduled collectors record run success/failure and stale-source status.
ask_ad_readinessAsk AD can answer at least five competitive-intelligence prompts from approved, cited context.
first_screen_clarityA first-time AD executive can state what the tool does, why Grainger/Fastenal were monitored, and why it matters to AD after the first viewport.
Agent Handoff
Start Here

AD needs a sellable competitive intelligence capability for its leadership and members. Public signals about large industrial distributors are available but fragmented across careers pages, service pages, press, investor material, filings, and trade coverage. AD needs those signals collected continuously, reviewed, and translated into credible actions before market pressure reaches members.

Completion Evidence
metrictarget
evidence_traceability100 percent of published insights include source_refs and source authority.
production_scopeGrainger and Fastenal monitored across careers, service/website pages, and at least one press/news/investor source family.
brief_qualityEach approved brief has 3 to 7 signals, each with observed fact, inference, implication, watch item, confidence, and source links.
operational_reliabilityScheduled collectors record run success/failure and stale-source status.
ask_ad_readinessAsk AD can answer at least five competitive-intelligence prompts from approved, cited context.
first_screen_clarityA first-time AD executive can state what the tool does, why Grainger/Fastenal were monitored, and why it matters to AD after the first viewport.
Problem

AD needs a sellable competitive intelligence capability for its leadership and members. Public signals about large industrial distributors are available but fragmented across careers pages, service pages, press, investor material, filings, and trade coverage. AD needs those signals collected continuously, reviewed, and translated into credible actions before market pressure reaches members.

Goal

Build the standalone KnowledgeVault AD suite as a production product AD can buy and use: KnowledgeVault core, the production KV app, Executive SEO, AD Competitive Intelligence analytics, and Ask AD context.

Success Metrics
  • item: metric: string, target: string
  • item: metric: string, target: string
  • item: metric: string, target: string
  • item: metric: string, target: string
  • item: metric: string, target: string
  • item: metric: string, target: string
Structured Payload

Machine-readable source fields

goal

Build the standalone KnowledgeVault AD suite as a production product AD can buy and use: KnowledgeVault core, the production KV app, Executive SEO, AD Competitive Intelligence analytics, and Ask AD context.

repo
name

KnowledgeVault

ownership

Standalone production AD suite repo. It should contain KnowledgeVault core, the production KV app, Executive SEO, AD Competitive Intelligence/analytics, and Ask AD integration. RedKey remains platform/orchestration, not the product implementation home.

local path

/Users/justinking/Vaults/Projects/KnowledgeVault

relationship to redkey

RedKey stores Studio artifacts, agent orchestration, and shared platform infrastructure; product code should graduate into this standalone KnowledgeVault repo.

users
typesuccessdescription
AD executiveCan read a short briefing and understand what Grainger, Fastenal, or MSC appears to be investing in and why AD members should care.Evaluates whether BezelIQ can create strategic intelligence products for AD and its members.
AD member distributor leaderCan see competitor moves connected to concrete opportunities such as AI search, VMI, supplier strategy, service model, or ecommerce execution.Runs an independent distributor and needs market moves translated into local actions.
BezelIQ operatorCan trace every insight back to source evidence and rerun collection without hand assembly.Maintains the intelligence pipeline and validates evidence before it becomes a customer-facing insight.
problem

AD needs a sellable competitive intelligence capability for its leadership and members. Public signals about large industrial distributors are available but fragmented across careers pages, service pages, press, investor material, filings, and trade coverage. AD needs those signals collected continuously, reviewed, and translated into credible actions before market pressure reaches members.

brand voice
tone
  • direct
  • strategic
  • evidence-led
off brand
  • alarmist threat language
  • generic BI jargon
  • claims that a job posting proves a corporate initiative by itself
language rules
  • Use plain English for implications.
  • Say observed when a source says it.
  • Say inferred when the system is interpreting a pattern.
project name

AD Competitive Intelligence

product suite
name

KnowledgeVault AD Suite

products
idnamepurpose
knowledgevault-coreKnowledgeVault CoreCapture retiring expert and product knowledge into governed, searchable assets.
knowledgevault-appKnowledgeVault AppProduction application surface for capture, search, dashboards, admin, and AD/member workflows.
executive-seoExecutive SEODistributor digital visibility intelligence and CEO-level opportunity prioritization.
competitive-intelligenceAD Competitive IntelligenceMonitor Grainger and Fastenal public signals, produce reviewed analytics/briefs, and feed Ask AD.
ask-adAsk ADSuite-level cited advisor across KnowledgeVault, SEO, and Competitive Intelligence.
repo path

/Users/justinking/Vaults/Projects/KnowledgeVault

migration source
seo app

AD SEO app implementation/artifacts currently live outside this repo and should be migrated or integrated as a product module before production packaging.

knowledgevault app

/Users/justinking/Vaults/Projects/redk3y/apps/knowledgevault

source memory
summary

Monitor Grainger and Fastenal first; pull signals from jobs, press releases, website changes, earnings/investor material, patent filings; synthesize into plain-English actionable insights; position as sellable product and future suite expansion. Justin later raised Fastenal as a stronger second V1 competitor; artifacts now recommend Grainger + Fastenal first, with MSC as V1b/backlog.

bezelbrain note

KnowledgeVault Website - ROI Model & Ask AD Agent (Session 3), 2026-05-02, competitive-intelligence section.

ux philosophy
feel

Executive-grade, immediately legible, and impressive through specificity. The first screen should feel like AD has opened a strategic intelligence command center built for them, not a generic analytics dashboard.

explicitly avoid
  • Uncited speculation
  • Overbroad market-news feeds
  • Fake certainty about hiring intent
  • A wall of raw job listings
non negotiable patterns
  • Every insight links to source evidence.
  • Every brief separates observed fact, inference, and recommended watch item.
  • The surface starts with a few high-signal competitors and sources.
  • First viewport includes a concise What we did / Why we did it / Value to AD frame.
  • First viewport names Grainger and Fastenal, the monitored signal families, and the business implication for AD.
  • The first interaction path is obvious: read current executive brief, inspect competitor signals, or ask AD a question.
schema version

1.0

scope boundary
in v1
  • Grainger and Fastenal production source collection
  • Careers/job posting ingestion
  • Fastenal onsite/vending/service-page monitoring
  • Press/news/investor source ingestion for production breadth
  • Evidence store and collection run logging
  • Signal classification with confidence/source scoring
  • Analyst review and approval workflow
  • AD executive intelligence workspace
  • Brief generation and delivery/export
  • Ask AD cited context export
  • Auth, monitoring, scheduled jobs, and production release checks
  • Standalone repository and deployable product app
  • Standalone KnowledgeVault suite repo packaging
  • Migrate or reconcile the active KV app implementation from redk3y/apps/knowledgevault
  • Include Executive SEO as a suite product surface or linked module
  • Include AD Competitive Intelligence analytics as a production product module
  • Ask AD integration across KV, SEO, and Competitive Intelligence
out v1
  • Credentialed LinkedIn scraping
  • Automated sales outreach
  • Member-specific private benchmarking before AD/member profiles exist
  • Full MSC production monitoring beyond parser investigation
  • Patent monitoring unless added after the first production release
non negotiables
  • This is a production product intended to sell to AD, not a prototype or demo.
  • Production V1 monitors Grainger and Fastenal first; MSC remains V1b unless Justin explicitly expands scope.
  • Every published signal and brief must preserve source URL, source authority, observed timestamp, and evidence text.
  • No insight can appear in an AD-facing surface unless it has at least one approved source reference.
  • The product must include operator review/governance before customer-facing publication.
  • The product must support repeatable scheduled collection, not one-off manual research.
  • The project is part of the AD suite and must connect to KnowledgeVault, Executive SEO, and Ask AD positioning.
  • The AD-facing first screen must immediately state what BezelIQ has done, why it was done, and the value to AD before showing detailed dashboards.
  • The product must create a wow moment through clarity and evidence, not decorative UI: AD should understand the product in under 30 seconds.
  • Build in the standalone KnowledgeVault repository at /Users/justinking/Vaults/Projects/KnowledgeVault, not in redk3y/apps/knowledgevault.
  • The standalone KnowledgeVault repo is the AD suite product repo and must include KV, SEO, KV app, AD analytics/competitive intelligence, and Ask AD integration.
success metrics
metrictarget
evidence_traceability100 percent of published insights include source_refs and source authority.
production_scopeGrainger and Fastenal monitored across careers, service/website pages, and at least one press/news/investor source family.
brief_qualityEach approved brief has 3 to 7 signals, each with observed fact, inference, implication, watch item, confidence, and source links.
operational_reliabilityScheduled collectors record run success/failure and stale-source status.
ask_ad_readinessAsk AD can answer at least five competitive-intelligence prompts from approved, cited context.
first_screen_clarityA first-time AD executive can state what the tool does, why Grainger/Fastenal were monitored, and why it matters to AD after the first viewport.
what wrong looks like
  • The system looks like a static research prototype instead of a repeatable product.
  • The UI shows raw links or job cards without strategic implications for AD.
  • Insights are generated without review, source authority, or citation traceability.
  • Collection is manual and cannot be scheduled or audited.
  • AD-facing output contains draft/low-confidence material.
  • An AD user lands on charts or tables before understanding what BezelIQ built and why it matters.
  • The first screen could belong to any generic analytics SaaS product.