Files
Lumotia/docs/brief/success-metrics.md
Jake 26c7307607
Some checks failed
check / cargo check (macos-latest) (push) Has been cancelled
check / cargo check (ubuntu-22.04) (push) Has been cancelled
check / cargo check (windows-latest) (push) Has been cancelled
check / svelte build + lint (push) Has been cancelled
agent: lumotia-rebrand — docs, scripts, root config, residuals
Phase 9 of the rebrand cascade. Sweep covers everything the Phase 8
frontend pass deliberately skipped: docs/, root markdown, scripts,
Cargo.toml descriptions, code comments that survived earlier
word-boundary sed, plus a handful of identifiers caught on the final
verify pass.

transcription-app changes:
- README.md, HANDOVER.md, KNOWN-ISSUES.md, run.sh — magnotia/Magnotia
  -> lumotia/Lumotia.
- docs/ — sweep across all subdirs except docs/handovers/ (preserved
  as immutable audit trail). Includes architecture-map references
  to magnotia_core::*, magnotia_storage::*, etc. now pointing at
  lumotia_*; dev-setup.md tracing output examples (lumotia_startup
  target); brief/ + superpowers/ + issues/ + whisper-ecosystem/ +
  audit/.
- Cargo.toml descriptions on 9 crates (core, audio, cloud-providers,
  hotkey, llm, mcp, plus referenced others).
- crates/core/src/{error,hardware,recommendation,paths}.rs +
  crates/audio/src/wav.rs + crates/llm/src/model_manager.rs +
  crates/cloud-providers/src/keystore.rs + crates/mcp/src/lib.rs —
  doc comments and a model-manager user-agent string.
- Caught on final pass: BroadcastChannel("magnotia_task_sync") -> ...
  ("lumotia_task_sync"); magnotia_locale i18n localStorage key
  renamed + migration shim added; CSS keyframe names
  magnotiaPulse / magnotiaBar / magnotiaFade renamed in the design-
  system kit; magnotia_viewer_item / magnotia_viewer_mode handoff
  keys renamed in HistoryPage + viewer/+page.svelte; src/assets/
  wordmark.svg text.
- src-tauri/src/lib.rs comment cleanup ("magnotia era" was sed'd
  to "lumotia era" earlier — restored).

Preserved (intentional):
- crates/core/src/paths.rs — keeps "magnotia" / "Magnotia" / ".magnotia"
  legacy detection strings in legacy_and_target_paths() so the
  migration shim can still find user data from the magnotia era.
- src/lib/stores/{page,focusTimer}.svelte.ts + src/lib/i18n/index.ts
  — migration call sites reference the legacy magnotia keys
  deliberately.
- docs/handovers/ — historical audit trail.

cargo build --workspace passes. npm run check: 0 errors / 0 warnings
(3958 files). cargo test --workspace: 339 pass / 0 fail.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-13 12:38:03 +01:00

1.9 KiB
Raw Blame History

9. Success Metrics

Business metrics

Milestone Target
Beta testers recruited 1015
Beta feedback: "same complaints repeating" threshold Signal to stop beta, ship v1.0
Waitlist signups pre-launch 100+
First paid sale Within 2 weeks of public launch
Revenue target (6 months) £2K MRR (mix of lifetime + cloud subscriptions)
Revenue trigger to evaluate CORBEL roll-up £500/month sustained

Neuro-inclusive product metrics

Standard SaaS metrics like Daily Active Users (DAU) or unbroken streaks must be avoided — they encourage the exact shame spiral Lumotia is designed to prevent. Track these instead:

Metric What it measures Why it matters
Time-to-capture Seconds from app open to completed brain dump Measures friction. If this exceeds 10 seconds, the thought is gone. The lower this number, the better Lumotia serves its core purpose.
Grace day recovery rate % of users who return and complete a task after 1+ days of inactivity Proves Lumotia has beaten the abandon-shame cycle. This is the single most important product metric. If users come back after missing days without guilt, the design is working.
Micro-step completion rate Completion rate of AI-decomposed tasks vs. manually entered abstract tasks Validates that micro-stepping actually works. If AI-generated steps have higher completion rates than user-entered tasks, the feature is earning its keep.
Brain dump → task conversion % of voice transcription content that converts into actionable tasks Measures AI quality. Low conversion means the AI isn't parsing well; high conversion means the core loop works.
Return after lapse Median days between last session and next session for users who go inactive Measures stickiness without punishing breaks. A user who returns after 2 weeks is a success, not a failure.