Documents and notes decision

Risenote

A single competent developer can build a useful replacement (web service with transcription + LLM extraction) in ~32 hours; no durable moats were evidenced on the product page, so self-building is realistic and likely cheaper over time.

View on the App Store
You pay

Not priced

No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.

You’d pay instead

$100one-off32 h to build

$50/mo6 h/mo upkeep

No published price to break even against.

Open-source builds that already do this

Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Risenote alternatives, with the arithmetic →

What a replacement has to do

  • Record meeting audio → transcribe → extract summaries & action items → store transcript and metadata → present searchable UI and export/share

What it still won’t have

  • Native iOS polish and App Store Live Activity integration (Lock Screen Live Activity)
  • Apple-hosted subscription/managed in‑app purchase flow
  • Any proprietary on-device optimizations or claimed 98%+ speech accuracy
  • Pre-built calendar suggestions and calendar integrations as shipped

What remains hard

  • Product polish and ongoing maintenance
Read the build prompt

First-year cost

No published price

Risenote does not publish a price we could read, so there is nothing to compare against. What building costs is below.

Money you would actually spend

Keep paying
—

Subscription price × seats × 12

Build it
—

AI build —APIs + hosting —

Time you would spend

—

—

What you would spend

What we assumed

The verdict above measures whether you could build it. This one is only about money.

Runnable build prompt

Not run yet
Build a minimal AI meeting-notes web service using Next.js + Node (Express) backend, Postgres for storage, and S3-compatible object storage for audio. Implement: 1) client audio recorder and upload endpoint; 2) transcription pipeline calling a cloud speech-to-text API; 3) LLM-based endpoint that produces meeting summary, action items, decisions, and timestamps from the transcript; 4) CRUD storage of transcripts, summaries, and metadata with full-text search; 5) web UI to play audio with synced transcript, view summary and action items, search past meetings, and export notes as text. Out of scope: native iOS app, offline/local transcription, billing/subscription integration. Include error handling, input validation, and automated tests for API endpoints and critical parsing logic.
How we checked3 sources · 2/3 runs agreed · evidence score 86

How the score was reached

  • Build verdict base78
  • An open-source build was found+5
  • 3 cited sources+3
  • Evidence score86

The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.

How scoring works →

Cited sources · 3

Every page the run actually retrieved.

Integrity checks

What held up, and what did not.

! 2 of 3 runs agreed; the verdict is the majority✓ Citations limited to fetched pages! 1 moat recorded