## Signet marketing voice — lessons from Nicholai

- write like a person, not a robot. no bulleted list cadence, no "it's real", no "make a dent", no AI slop phrases
- when someone has a memory problem, the pitch is "signet is just a better memory system" — NOT "carry your setup to other tools"
- lead with the actual fix to their problem first. mention signet last and briefly.
- no jargon in the plug. "dedicated memory system that handles all this properly" > "portable identity layer separating user identity from session state"
- one sentence + link. don't over-explain signet in a comment reply.
- write like you're talking to the person, not performing helpfulness at them

## Marketing session summary (2026-03-01)

Spent a full session building out the Signet marketing foundation with Nicholai. Key outputs:

**Files created in ~/signet/signetai/marketing/:**
- STRATEGY.md — two-track framework, taglines, Jake's landing page principle, timeline narrative, business model, channels, install behavior
- LANDSCAPE.md — verified memory situation for OpenClaw, Claude Code, Codex, OpenCode (sourced from actual docs)
- REDDIT_STYLE_GUIDE.md — per-subreddit guide based on real top posts with scores
- REDDIT_POSTS_OPENCLAW.md — 10 post variations for r/openclaw, different angles
- REDDIT_REPLY_DRAFTS.md — reply drafts for two live memory threads

**Skill created:** signet-content-strategy (packaged at ~/.agents/signet-content-strategy.skill)

**Key decisions:**
- No paid tiers. Revenue = enterprise installs only.
- Channels: Facebook, Instagram, Reddit, landing page. Not Discord (too noisy).
- No Cursor support. Drop it from all copy.
- Install path is flexible — detects existing OpenClaw workspace, falls back to ~/.agents/. Don't mention the path in non-technical copy.
- The Signet pitch for memory problem threads: "it's just a better memory system" — not the portability angle.

**Next:** Set up Reddit API credentials so I can post/reply directly.