Editor’s note · Internal strategy memo
Daylogue PR Direction Memo
To: Investment Strategist (press release drafts) From: Marketing Strategy Re: PR narrative architecture, 6-month direction Date: April 22, 2026
1. Strategic Diagnosis: Why Our PR Lacks Direction
The core problem is that we are announcing features when we should be announcing moments and we are burying the only thing no competitor has.
Three specific failures:
We have no category name. Every other AI journaling app (Rosebud, Reflection, Mindsera, Rocket Health's voice journal) is fighting for the phrase "AI-powered journaling." That is a feature war we cannot win by describing features. Daylogue does something categorically different. It writes your emotional story back to you across time, with continuity and narrative arc. That is not a journal. That is not a chatbot. We have not given journalists a word for it, so they reach for the nearest available cliche and we blend in.
The patent is buried. A patent-pending serialized narrative AI engine, filed March 2026, is the single most press-worthy technical asset we have. It signals category creation. It signals defensibility. It gives a journalist something to anchor a story to that isn't "another journaling app." We are treating it as a footnote.
We are announcing existence instead of announcing stakes. "App is live" is not a story. "Solo founder files patent on technology that turns your daily check-ins into a continuous self-narrative, and no one else is doing this" is a story. Every release to date has announced what we built. None have announced what we've changed.
2. The Central Narrative
Every press release Daylogue issues for the next 18 months should ladder up to one story: a solo technical founder identified a gap in how humans understand themselves over time, not in a single session, but across weeks and months, and built the first app that writes your emotional story back to you as it unfolds, in real time, with memory. That is the category we are creating: not AI journaling, not mood tracking, not a therapy supplement. Call it narrative self-intelligence. The line that stops a tired health-tech journalist: *"You've seen a hundred journaling apps. This one reads you back to yourself."*
3. Six Press Release Angles, Next Six Months
Angle 1: Patent-Pending Category Creation
- Hook/headline direction: "Daylogue Files Patent on AI Engine That Writes Users' Emotional Lives Back to Them as Serialized Narratives, A New Category in Mental Wellness"
- Moment: Patent filing (March 2026, announce now, the filing is the news hook, release timing is your choice)
- Target outlet tier: Tier 1, TechCrunch, Wired, The Verge, Fast Company. Secondary: MobiHealthNews, Rock Health coverage
- Exec quote lanes: Brandon on the invention's origin (therapy frustration, the problem of discontinuous self-knowledge); Marcus on the market gap (why no competitor has attempted narrative continuity at scale)
Angle 2: Cross-Platform Launch
- Hook/headline direction: "Daylogue Launches Simultaneously on iOS, Web, and Android, Bringing Narrative Self-Intelligence to Every Device Without Compromising Zero-Knowledge Privacy"
- Moment: Android launch (peg the announcement to Android GA, position the three-platform moment as infrastructure maturity, not feature completion)
- Target outlet tier: Tier 2, VentureBeat, 9to5Mac, Android Authority, digital health newsletters (Axios Pro Rata, CB Insights Health)
- Exec quote lanes: Brandon on the engineering decision (privacy-preserving unified backend, solo build); LaShawn on the user acquisition thesis (meeting people where they already live)
Angle 3: Enterprise / School Pilot Announcement
- Hook/headline direction: "Daylogue Launches Institutional Tier for Schools and Employers, K-Anonymity Architecture Ensures Individual Entries Stay Private While Surfacing Population Wellness Signals"
- Moment: First signed institutional pilot (school district, university wellness office, or employer). Do not issue this release without a named partner willing to be quoted.
- Target outlet tier: Tier 2, EdSurge, EdTech Magazine, HR Executive, Employee Benefit News; Tier 1 pitch to WSJ Health if the partner has name recognition
- Exec quote lanes: Marcus on the enterprise thesis (wellness data that protects the individual); partner-org wellness director on what problem this solves for them (the quote that gives this release its legs)
Angle 4: "Daylogue Wrapped" Data Story
- Hook/headline direction: "Daylogue Releases First Aggregate Emotional Pattern Report, What 90 Days of Daily Check-Ins Reveal About How People Actually Feel vs. How They Think They Feel"
- Moment: First data drop from anonymized, aggregated beta user patterns (Spotify Wrapped mechanics applied to population-level emotional insight)
- Target outlet tier: Tier 1 consumer, New York Times Well, TIME Health, Vox; Tier 2, Behavioral Scientist, Greater Good Science Center coverage. This is the outlet-broadening angle that gets Daylogue outside tech press.
- Exec quote lanes: Brandon on what the data surprised him with; third-party mental health professional (advisory or quoted expert, not an employee) contextualizing the findings. This is where we build credibility with a single well-chosen external voice
Angle 5: Safety and Ethics Stance
- Hook/headline direction: "Daylogue Publishes Crisis Detection Architecture, How a Journaling App Handles Mental Health Emergencies Without Pretending to Be Therapy"
- Moment: Voluntary transparency publication of our 3-tier crisis detection system and 55+ resource library. No regulatory requirement triggers this, we publish it because we chose to.
- Target outlet tier: Tier 2, MobiHealthNews, STAT News, The Markup (privacy angle); strong blogger/newsletter play with therapist-influencer community on Substack and LinkedIn
- Exec quote lanes: Brandon on the design philosophy (we built this to know its lane); LaShawn on why this matters to users who are in regulated-adjacent spaces. Consider sourcing a quote from a licensed therapist who reviewed the system, even one external professional validator changes the credibility weight of this release significantly.
Angle 6: Founder Origin / Ship Day Story
- Hook/headline direction: "He Kept Forgetting His Own Life. So He Built the App That Remembers It For You." (feature pitch, not standard wire release)
- Moment: This is a profile pitch, not a press release. It is the 2-minute narrative made into a first-person or journalist-written feature. Anchor it to a tangible milestone (App Store launch, first 1,000 users, patent filing).
- Target outlet tier: Tier 1 long-form, Wired, Fast Company "Most Creative People," MIT Technology Review. These are relationship pitches, not wire submissions. Requires a warm intro or direct journalist relationship.
- Exec quote lanes: This is Brandon's story entirely. Marcus adds the market context in the body of the piece. The journalist does the framing.
4. The Calm/LifeStance Structure Translated for Daylogue
- Headline: Names a specific, defensible moment, a patent, a platform launch, a partnership, a data release. Not "Daylogue Announces New Features." Names what changed in the world.
- Subhead: States the user benefit in plain language, what the person on the other end can now do or understand that they couldn't before.
- Lede: Two sentences max. Who, what, when, and the single most compelling proof point available (patent-pending, cross-platform, first in category).
- Problem statement: The gap in how people understand themselves over time, not "journaling is hard" but "you walk into therapy not knowing what happened to you in the last two weeks." Specific, human, non-clinical.
- Solution: How Daylogue's serialized narrative engine works in plain language. Mention conversational check-in → pgvector memory → episodic narrative output. Do not say "AI-powered" without saying what the AI actually does. Do not mention Claude by name in consumer releases without Anthropic approval, frame it as the underlying model stack.
- Quotes: Two. Quote 1 (Brandon): the human origin story compressed to two sentences, plus the vision. Quote 2 (Marcus or LaShawn, or an external partner/validator): the market or user angle, what this means for the person downloading it, or for the institution piloting it. The two quotes should answer different questions.
- Proof/capability details: Specific, not vague. AES-256-GCM zero-knowledge encryption (name it). 172+ database migrations (signals engineering maturity, use it for tech press). iOS App Store live, web live, Android in development. Patent pending, filed March 2026. These are the credibility anchors.
- Boilerplate: One tight paragraph. Daylogue is the company that created narrative self-intelligence, conversational daily check-ins that surface patterns and write users' emotional lives back to them as episodic, continuity-aware narratives. Privacy-first. Not therapy. Daylogue.io.
5. The Credibility Trap to Avoid
Do not let any release imply scale or clinical authority we do not have.
The specific failure mode: pre-revenue, solo-founded wellness apps in regulated-adjacent categories routinely destroy their own credibility by using language that implies either user volume ("millions of people struggle with...") or clinical validation ("proven to improve...") before either exists. Journalists who cover health tech are trained to spot this. A single overclaim, even phrasing like "helps users achieve better mental wellness outcomes", signals that we do not know the difference between a marketing assertion and an evidence claim. In a space where Calm Health cites 26 million covered lives and LifeStance cites 7,700 clinicians and HIPAA/HITRUST compliance, our credibility cannot come from scale or clinical proof. It must come from intellectual honesty about what we are, technical specificity about how we built it, and a clear, principled line between what Daylogue does and what therapy does. Every release should stay inside that lane. The moment we blur it, we are a liability story, not a tech story.