Back to corpus
proposalexperiment writeup candidatescore 38

CognitiveHire Content Strategy

**What exists:** - Grand Diomande consulting brand (granddiomande.com) — active, Vercel-hosted - 50+ iOS apps shipped (39 on TestFlight) - 112K+ AI interactions across 11 domains in Supabase - Technical blog posts drafted but not published (cognitive twin, CALC, Vantage) - Strong technical credibility: ML, distributed systems, multi-agent coordination, iOS, creative production - Guinean-American heritage + N'Ko language AI work — authentic differentiator - No dedicated CognitiveHire content presence yet

Open full HTMLDownload HTMLCorpus JSONPaper schema

Full HTML reader

Read the full artifact

Open in new tab

Extracted abstract or opening context

**What exists:** - Grand Diomande consulting brand (granddiomande.com) — active, Vercel-hosted - 50+ iOS apps shipped (39 on TestFlight) - 112K+ AI interactions across 11 domains in Supabase - Technical blog posts drafted but not published (cognitive twin, CALC, Vantage) - Strong technical credibility: ML, distributed systems, multi-agent coordination, iOS, creative production - Guinean-American heritage + N'Ko language AI work — authentic differentiator - No dedicated CognitiveHire content presence yet **What's missing:** - Platform-specific content presence for CognitiveHire - A consistent publishing cadence - Demo content (video, interactive twin interface) - An audience that knows this product exists **Assessment:** This is a greenfield launch with strong underlying credibility. The asset gap is distribution, not substance. Mohamed has proof. The work is to make that proof visible to the right people. ### Path A: Educational **Premise:** "Here's what your AI usage data actually reveals about you" Teaches the audience something they didn't know. Positions Mohamed as the person who figured this out first. Low defensiveness from the audience. Works well for cold traffic who don't know CognitiveHire yet.

Promotion decision

What has to happen next

Attach run IDs, datasets, metrics, and reproduction commands.

Why this is not always a full paper yet

Corpus pages are public-safe readers for discovered workspace artifacts. They are not automatically final papers. A corpus item becomes a polished paper only after the editable source, evidence checkpoints, references, figures, render path, and release status are attached through the paper schema.