10 Personas — Tech-Knowledge Spectrum

Date: 2026-05-28 Grounding rule: workflow-reality-check — each persona's traces live where their REAL workflow puts them, not invented. Maps to competing tools they currently use.

Personas are ordered from least → most technical. Each is a target user Waggle wants to convert to "this is the one AI tool I need."

P1 · Greta (67) — Retired teacher, uses iPad daily

Tech knowledge: Sends WhatsApp, reads news in browser, uses ChatGPT free maybe once a week
Real workflow / where traces live: WhatsApp threads with family + a Notes app + sometimes Gmail. NO code, NO file system organization, NO API keys.
Top JTBD: "Help me write a thank-you note to the doctor / draft a complaint letter to my bank."
Current default: ChatGPT free tier in browser; sometimes asks her son.
Waggle hook moment if we win: she says "good morning Waggle, can you read what I wrote yesterday?" and Waggle DOES remember.
"One tool" criterion: all letter-writing + remembering-conversations work happens in Waggle, not in ChatGPT.
Competitor she'd notice: Claude Cowork (if she ever upgrades) — but its desktop-only / Pro+ blocks her.

P2 · Hassan (29) — Café owner, side-business operator

Tech knowledge: Instagram + Stripe dashboard + Gmail + a Google Sheet for inventory. Has tried ChatGPT and Gemini for writing menus.
Real workflow: Instagram DMs, Gmail, Sheets, Canva. No IDE. iPhone-first.
Top JTBD: "Reply to 30 customer DMs in my voice + draft this week's specials post + decide which supplier to call back."
Current default: ChatGPT free, Canva AI, Gmail Smart Compose.
Hook moment: Waggle drafts a reply in HIS voice on the second message because it learned from the first.
"One tool" criterion: all customer-comms drafting + supplier decisions live in Waggle.

P3 · Sarah (38) — Marketing manager at a 50-person SaaS

Tech knowledge: Notion power user, Linear viewer, uses ChatGPT Plus + Gemini + maybe Claude. Never opens a terminal.
Real workflow: Slack + Notion + Google Docs + Figma comments + ChatGPT in browser.
Top JTBD: "Turn 4 customer-interview transcripts into 3 campaign messages + a launch brief + a deck outline."
Current default: ChatGPT Plus + Notion AI + Gamma.
Hook moment: drops 4 transcripts in, gets a draft brief that cites which transcript said what + retains the campaign decision in memory next week.
"One tool" criterion: all transcript → artifact synthesis flows happen in Waggle.
Competitor she'd consider: Claude Cowork for the docx output, ChatGPT for the chat.

P4 · Imran (44) — Independent consultant, frameworks-first

Tech knowledge: Reads Substack on AI, has Claude Pro + ChatGPT Plus subscriptions, no API keys.
Real workflow: Apple Notes + Calendly + Gmail + Keynote + 4 Claude/ChatGPT threads pinned per client.
Top JTBD: "Synthesize last week's client call into a 2x2 + a 1-slide framework + a follow-up email."
Current default: Claude Pro (one thread per client) + Gamma for slides.
Hook moment: he asks "what did we decide for client X last call" — Waggle pulls the exact decision + lists the framework he applied + offers to extend it.
"One tool" criterion: all client-engagement memory + framework synthesis + decks happen in Waggle.

P5 · Lucas (31) — Investigative journalist

Tech knowledge: Spreadsheet-fluent, uses Datawrapper / Pinpoint / OSINT tools, no code.
Real workflow: Signal + Otter.ai transcripts + Drive folders + Pinpoint for source docs + lots of browser tabs.
Top JTBD: "Across 80 court filings + 20 interview transcripts + 6 months of email leaks, find every mention of , cluster decisions, output a chronology."
Current default: ChatGPT Plus + Pinpoint + manual grep.
Hook moment: he imports a PDF dump, asks "show me every time X said Y", Waggle surfaces it WITH source-frame citations he can audit.
"One tool" criterion: all corpus-ingest + entity-recall + chronology work happens in Waggle.
Competitor: OpenClaw self-hosted (for sovereignty / source protection).

P6 · Daniel (41) — BI / finance ops analyst

Tech knowledge: SQL-fluent, lives in Excel + Looker + dbt. No web-dev. Cautious about cloud AI for finance data.
Real workflow: Looker + Excel + Outlook + Teams + occasional Python notebooks.
Top JTBD: "Drop in this CSV, flag outliers, write the variance commentary I'll paste into the monthly board pack."
Current default: Excel Copilot + ChatGPT Plus for prose, manual for data.
Hook moment: CSV drag-drop → structured outlier table + a draft commentary in his prior month's voice → he edits, ships.
"One tool" criterion: all data-summary + commentary + monthly-board-pack prep happens in Waggle.

P7 · Anya (28) — Content strategist / writer

Tech knowledge: Notion + Substack + Figma, uses ChatGPT Plus + Claude Pro for voice training.
Real workflow: Notion + Substack + Docs + ChatGPT thread bookmarks for "my voice".
Top JTBD: "Draft 600 words in my voice for the Wednesday newsletter, riffing on this week's industry headline."
Current default: ChatGPT Plus (custom GPT trained on her voice) + Claude for editing.
Hook moment: Waggle's writer-persona produces text indistinguishable from her hand on the FIRST try because it loaded her brand-voice file.
"One tool" criterion: all newsletter drafting + voice-tuning + research-into-draft work in Waggle.

P8 · Marko (51) — Product owner / business strategist (real user)

Tech knowledge: Uses Claude Code + ChatGPT + Gemini exports in parallel. API keys, multiple models, comfortable with CLI for power features but doesn't want CLI-only.
Real workflow: Strategy work lives in head + LLM sessions (per feedback_workflow_reality_check). Mail/Calendar/Drive are downstream artefacts of other people tracking his decisions, not parallel traces of his thinking.
Top JTBD: "Across my 12 weeks of conversations, what's the strategy thread for , and where did we land on ?"
Current default: Claude Code + manual harvest pipeline + Waggle's harvest adapters.
Hook moment: asks the recall question, gets the canonical answer + citation chain across Claude/ChatGPT/Gemini sources — beating the cross-LLM unified graph problem (per his own rule).
"One tool" criterion: all cross-LLM strategy memory + decision recall happens in Waggle.

P9 · Priya (35) — Senior product engineer (Claude Code daily user)

Tech knowledge: Claude Code daily for coding, MCP-curious, builds custom plugins.
Real workflow: Claude Code + Linear + GitHub + Slack. Wants the NON-CODING half of her week (docs, RFCs, decisions, planning) in something better than chat.
Top JTBD: "Turn this 90-min architecture meeting transcript into an ADR draft + Linear stories + a follow-up message to the team."
Current default: Claude Code + Notion + Linear (juggled manually).
Hook moment: the persona switcher to "Project Manager" or "Planner" produces work that integrates with her Claude Code session because Waggle exposes the same Skills marketplace.
"One tool" criterion: all PM/RFC/planning work happens in Waggle (Claude Code keeps her coding).
Competitor: Claude Cowork (Anthropic-native), Hermes (open-source allure).

P10 · Tomás (39) — Builder / agent-curious technologist

Tech knowledge: Builds with Cursor + Hermes + custom MCP servers, runs Ollama locally, wants self-hosted.
Real workflow: Terminal-first, Hermes scripts, Telegram for outbound notifications from his agents, Discord for agent community.
Top JTBD: "Compose a workflow that schedules a daily competitive-intel scrape, summarises it, and DMs me the top 3 findings on Telegram at 8am."
Current default: Hermes Agent + custom Python + cron.
Hook moment: the same workflow takes him 4 clicks in Waggle's Launcher + ScheduledJobs + Connector, no Python, AND the result includes provenance + can be shared with non-technical teammates.
"One tool" criterion: even his agentic workflows are easier to author + maintain + share in Waggle than in Hermes.
Competitor: Hermes (his current default), OpenClaw (for marketplace), Claude Code Routines (for cloud cron).

Spectrum coverage matrix

Dim	P1	P2	P3	P4	P5	P6	P7	P8	P9	P10
Tech literacy (1-10)	1	3	5	5	6	7	6	8	9	10
Has API keys	N	N	N	N	N	maybe	maybe	Y	Y	Y
Pays for ChatGPT/Claude today	N	N	Y	Y	Y	Y	Y	Y	Y	Y
Uses CLI tools	N	N	N	N	N	sometimes	N	Y	Y	Y
Workflow lives mostly in chat	Y	Y	Y	Y	mixed	mixed	mixed	mixed	mixed	mixed
Wants self-hosted	N	N	N	N	yes (sources)	yes (data)	N	yes	maybe	Y

Workflow-reality-check pre-validation

For each persona I've asked: where does the trace of their work ACTUALLY live today? (Per saved feedback rule.)

P1-P4: chat tools and basic productivity apps. Tests assume only chat-side workflow. ✓ epistemic gate clears.
P5: corpus-heavy investigative work, sources matter. Cross-platform (Signal + Drive + Pinpoint) is a REAL pattern for journalists. ✓
P6: Excel + Looker. Audit assumes ability to ingest CSV / tabular data — Waggle's drag-drop addresses this. ✓
P7: bookmarked chat threads + voice files. Real for content creators. ✓
P8: cross-LLM strategy memory. Per Marko's own rule, this is the REAL test profile. ✓
P9: Claude Code daily user, wants non-coding half elsewhere. Real adoption pattern for engineers in 2026. ✓
P10: terminal + Hermes + Telegram outbound. Real for the agent-builder segment. ✓

No persona has an invented "let's pretend they use Slack" assumption. Each maps to verified workflow patterns.

Anti-patterns we will NOT score against

"Waggle should integrate Outlook" without a concrete persona triggering it — generic segment expansion. Per the rule, that doesn't clear the epistemic gate. Outlook integration appears for P6 (Excel + Outlook) — that's the concrete trigger.
"Build a browser extension" — would help P1/P2/P3 external-trigger problem. Concrete trigger: P3 lives in Notion + browser. Worth listing in FEATURE-REQUESTS.md, not implemented in this audit.

10 KiB Raw Blame History