Case study · Consumer AI · Mobile

Anne: privacy-first AI that earned 1M+ downloads

A privacy-first AI assistant built for an underserved community — low CAC, strong retention, and a seed story I owned.

Anne: privacy-first AI that earned 1M+ downloads
Product Manager2026 – Present

At a glance

The numbers

1M+

downloads

Low CAC

efficient acquisition

Strong

retention vs. novelty

The story

What happened, why, and what moved

Context

I own Anne end-to-end — a privacy-first AI assistant built for an underserved community. Consumer AI is crowded; Anne's wedge is trust and cultural fit, not generic chatbot capabilities. My mandate covers product wedge, growth efficiency, and the retention story in the data room. Downloads are vanity if retention and CAC don't hold.

The trap

Mainstream AI assistants treat privacy as a settings page and community as a marketing line. Users who need culturally aware, privacy-respecting AI had no product that felt built for them — only adapted from products built for everyone else. The trap was chasing feature parity with general assistants. We'd lose on breadth and win nowhere on trust.

The bet

I bet on privacy-first architecture and community-specific design as the product wedge — not feature parity with general assistants. Retention and acquisition efficiency would prove the wedge; download count alone wouldn't. Every data collection decision went through: does this earn trust or spend it?

The fight

[NEEDS YOUR INPUT: Add the specific trade-off — e.g., what data you chose not to collect, or a feature cut that preserved privacy/retention.] Until then: the fight was resisting general-purpose AI feature creep that would have diluted Anne's trust positioning. Growth teams wanted viral loops; I wanted retention loops.

The proof

Anne reached 1M+ downloads with low CAC and strong retention. I owned the growth and retention story for the seed-stage data room — metrics, narrative, and proof that community-specific AI can acquire and retain at consumer scale. Trust showed up in the numbers, not just the positioning doc.

What I'd do again

I'd publish a plain-language privacy promise users can audit, not legalese they ignore. I'd gate viral features behind retention milestones — novelty spikes downloads; trust keeps them.

Product calls

Key decisions

Privacy as product wedge, not compliance checkbox

Scoped architecture and UX around privacy-first design — not bolt-on settings after the fact.

[NEEDS YOUR INPUT: Community-specific design decision]

Replace with the specific cultural or community design choice that differentiated Anne from generic assistants.

Retention over novelty features

Held back general-assistant features that didn't strengthen trust or return usage.

Outcomes

Measured impact

  • 1M+ downloads

    Consumer scale with community-specific positioning

  • Low CAC

    Efficient acquisition without paid-growth dependency

  • Strong retention

    Trust and fit drove return usage over novelty

  • Seed data room narrative

    Growth and retention story owned end-to-end

Takeaways

What I learned

  • 1In consumer AI, trust is the retention loop — not model benchmarks.
  • 2Community-specific beats general-purpose when general-purpose feels generic.
  • 3If you can't explain your privacy model in one sentence, users won't trust you.
Technical appendix

Architecture

Privacy-First Data Architecture
On-Device Processing Layer
Community-Tuned Model Pipeline
Consumer Mobile Platform

Technologies

React NativeNode.jsPostgreSQLOpenAI APIFirebase

Want the full portfolio? More case studies on the homepage.