Founder Persona Extraction
Build a complete, sourced public-record persona dossier for a founder or executive before ghostwriting, running their LinkedIn, a high-stakes interview, or a collaboration. Use when asked to scour what a person has said, map their positions and stories, or brief someone to write accurately in their name. Produces an identity timeline, voice fingerprint, opinion map, story bank, world bible, relationship graph, red zone, and gaps list. Not for private-data investigation, generic company research, or publishing without the person’s agreed mandate.
Sample result
Run live demo
Build an executive persona dossierAnton, Here is your synthesized 8-layer persona dossier derived from your public podcasts, keynote transcripts, and published articles across Umbra Systems and your previous work at Kestrel Field Solutions. • Identity & Timeline: 12-year trajectory in field-service automation verified across official bios and industry coverage. • Voice Fingerprint: Concise, operations-first tone; relies on concrete metrics over jargon and favors active voice. • Core Opinions: Consistent stance on dispatch automation vs. manual scheduling (emphasized across 5 appearances in the last 24 months). • Story Bank: The dispatch blackout recovery story and the early customer onboarding breakthrough at Kestrel. • Red Zone: Avoids commentary on competitor pricing wars; legacy hardware compatibility remains a sensitive topic. • Intake Agenda: 3 timeline nuances regarding product pivots to resolve during our kickoff call. Please review this briefing and let me know if any positioning needs adjustment before we begin drafting.
Example run
“Can you extract a complete 8-layer persona dossier and intake agenda for Anton Lindqvist, Founder & CEO at Umbra Systems, so we can prepare our executive messaging and ghostwriting strategy?”
Located 18 public sources including 5 podcast interviews, keynote transcript at FieldService Tech, and Kestrel Field Solutions press releases.
Extracted 12-year trajectory, operations-first voice style, 2 core story bank entries, red zone topic constraints, and 3 pivot timeline gaps.
Sourced Persona Dossier & Intake Briefing for Anton Lindqvist
More in Operations & Other
- Sample result
Email deliverability audit scorecardAudit Category Grade Technical Findings DNS & Authentication Pass (A) SPF and DKIM active on get-hospitastaff.com; DMARC policy set to p=none. Inbox Daily Capacity Fail (D) Google Workspace inbox sending 45 cold emails/day (hard ceiling is 15/day). Security Gateway Route Warning (C) Glint Systems MX record points to Mimecast; tracking pixels triggering gateway flags. Warm-up Pool Rotation Pass (B+) 70/30 active-to-warmup ratio maintained across 4 secondary sending domains. Copy Safety & Links Fail (F) Outreach template contains 2 open-tracking links and 1 external booking URL. Set up, audit, rescue, or pre-send-check cold-email deliverability as a guided step-by-step process. Walks the nine practices in order, domains (age, TLDs, registrar spread, SPF/DKIM/DMARC), inbox providers and daily capacities, the 70/30 warm-up pool rotation, sequencer choice and fingerprinting, email security gateways (Mimecast, Proofpoint, Barracuda) and how to route around them, inbox placement testing without open tracking, burn-detection metrics with corrective actions, deliverability-safe copywriting, and email verification. Each step is do-this, here's-why, then a checkpoint before the next. Works with any provider and sequencer. Trigger when the user mentions deliverability, spam placement, bounce rates, inbox warm-up, domain reputation, blacklists, email landing in spam, reply rates dropping, warm-up scores, security gateways, or setting up cold-email infrastructure.
- Sample resultGTM automation roadmap
Automation Workflow Recommended Tools Priority 1. Intent Campaigns at Scale Unify + Octave + Smartlead Phase 1 (Immediate) 2. Site Visitor Deanonymization RB2B + Clay + Slack Phase 1 (Immediate) 3. Slack Rep Approval Routing Clay + Slack Interactive Phase 2 (Week 2) 4. Permit Database Scrapers Apify + Serper + n8n Phase 2 (Week 3) 5. Domain Infrastructure Setup Zapmail + Instantly + Smartlead Phase 3 (Week 4) Pick and build the highest-leverage GTM automations for a go-to-market team, from a catalog of eleven that repeatedly move productivity. Covers intent-based campaigns at scale, human-in-the-loop outreach off website deanonymization, Slack approval notifications, no-code social listening, local-business scraping workflows, AI-agent orchestration, the LLM upgrade, AI note-taking, prompt-based list building, domain and inbox infrastructure at scale, and AI-native workflows inside the CRM. Names the actual tools for each (Clay, Unify, BirdDog, Common Room, Kwanzoo, RB2B, Octave, Twain, Outbond, Amplemarket, Valley, HeyReach, Instantly, Email Bison, Smartlead, Trigify, Apify, Serper, n8n, Zapier, Make, Claude, OpenAI, Grok, Fireflies, Fathom, Exa, Landbase, Zapmail, ScaledMail, Mailreef, Luella, Hypertide, Premium Inboxes, Attio, HubSpot, Slack). Trigger when the user wants GTM or sales automations, no-code workflows, AI agents for outbound, to automate prospecting or outreach or research, a tool stack recommendation, or ideas to improve GTM productivity.
- Sample result
ExpertiseApp9:15 AMOutbound Alert: 2 Senders DisconnectedAccount Sequence:Indigo Dynamics Q3 ExpansionTarget Contact:Idris Voss, VP Plant OperationsSender Health:2 of 6 inboxes offline (Instantly)Lead Flow Status:Idle (0 leads processed in 48h)Deliverability Risk:Bounce rate spiked to 12.8%21Design and build a read-only bird's-eye analytics and health dashboard for an AI-automated outbound system, from intent finding and enrichment through to email deliverability. Covers architecture health, source-to-CRM funnel cuts, channel and reply analytics, sender monitoring, and alert rules. Trigger when the user wants an outbound or GTM dashboard, command center, pipeline analytics, automation-stack health monitor, lead-volume or funnel reporting, channel performance, reply analytics, deliverability monitoring, or to find what is connected, idle, broken, or working. Not for changing tools, sending outreach, tagging records, or other write actions.
