Audio and podcasting decision
Scrybecast
A competent developer can assemble a useful podcast-repurposing tool using existing transcription and LLM APIs in multi-week effort, but reproducing the polished product, billing/credits, speaker-diarization quality and customer-facing polish is nontrivial so keeping the paid product may make sense for many users.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off120 h to build
$40/mo6 h/mo upkeep
No published price to break even against.
No open-source build does this yet
Nothing published replaces this one, so a replacement starts from an empty file. Here is what it would have to cover.
What a replacement has to do
- 1) upload and store audio files and RSS ingestion; 2) run speech-to-text + speaker diarization; 3) run LLM prompts to produce summaries, chapters, social posts and blog ideas; 4) persist transcripts/outputs and provide an editor UI for post-editing; 5) background job orchestration and simple billing/limits for minutes/credits.
What it still won’t have
- Polished multi-language UX and onboarding
- Integrated credit/usage billing and subscription management
- Customer support, QA and product polish
- Any proprietary fine-tuning or unseen French-specific model improvements
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Scrybecast 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
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
Build a minimal SaaS to repurpose podcast episodes (stack: Next.js + Postgres + S3, background workers with Bull/Redis, deploy on Vercel/ Rail/Render). Core features: (1) user accounts and RSS podcast ingestion, (2) upload audio (up to 1GB) and store originals in S3, (3) background job that calls a speech-to-text API (or Whisper) with speaker diarization and stores transcripts and SRT, (4) LLM-based generation of summaries, chapters, social media posts and a blog idea using prompt templates, (5) simple editor UI for each generated artifact and export (copy, download SRT/text), (6) quota enforcement per-month minutes and credits. Out of scope: team management UI, advanced analytics, polished marketing site, native mobile apps. Include error handling for failed transcriptions/generation, retries, and unit/integration tests for worker flows and API endpoints.
How we checked
How the score was reached
- Partly verdict base52
- Evidence score52
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 · 1
Every page the run actually retrieved.
- official productScrybecast - official product
Integrity checks
What held up, and what did not.
