Skip to content
Developer toolsNew techTop 27% of today's analysed ideas

Voice-taught custom vocabulary for speech-to-text

Build a cross-platform SaaS or API layer that lets users teach speech-to-text tools proper nouns and jargon by recording each word once, aimed at podcasters, call centers, and legal or medical dictation users who need names and invented terms spelled correctly without Mac-only or local-only limits. Wrap it around existing STT engines (Whisper, Deepgram, AssemblyAI) or the open LoRA adapter shown here, and sell it as a plugin or API add-on.

Original post

What to build

A lightweight API/SDK that wraps existing speech-to-text engines (Whisper, Deepgram, AssemblyAI) and lets users 'teach' it a proper noun or invented term by recording it once, then auto-corrects future transcripts for that term — sold to podcasters, call centers, and legal/medical dictation users who need names spelled right every time.

A Mac-only hobbyist demo shows a LoRA adapter can teach a speech model a new name from a single utterance; the real opportunity is packaging that trick as a cross-platform API layer for anyone whose transcripts keep mangling proper nouns and jargon.

Demand

Podcasters, call-center QA teams, and legal/medical transcriptionists repeatedly hit the same wall — STT engines butcher names, drug names, and invented terms — and currently have to maintain manual find-and-replace glossaries after the fact.

  • Hacker NewsDiscussion

    Show HN: Teach a speech model (en) a name by saying it once, on your Mac — 3 points, 0 comments on HN.

  • DeepgramProduct

    Already sells 'keyword boosting' and custom vocabulary as a paid feature on top of its STT API, showing vendors see commercial value in solving this exact mis-transcription problem.

  • AssemblyAIProduct

    Offers a 'word boost' custom vocabulary parameter in its transcription API, indicating existing paying demand for proper-noun accuracy fixes.

Stack

  • OpenAI Whisper (local or API)
  • LoRA fine-tuning (PEFT/Hugging Face)
  • Deepgram or AssemblyAI API (fallback/comparison engine)
  • FastAPI backend
  • Supabase (user accounts, glossary storage)
  • Stripe (usage-based billing)

Solo + AI difficulty

The hard part is making one-shot adaptation generalize reliably across accents, background noise, and multiple simultaneous custom terms — that's real ML engineering, not glue code; the easy part is the API wrapper, glossary storage, and billing layer, which AI coding tools can scaffold quickly. Realistic MVP (single-term correction via post-processing + basic LoRA fine-tune pipeline) is 3-5 weeks solo; a robust multi-term, multi-accent version is a much longer effort.

Entry threshold
Low capital barrier since it can be built on open-source adapters and existing STT APIs, letting a solo developer ship a prototype in a few weeks, but matching the accuracy of incumbents like Deepgram and AssemblyAI keyterm boosting takes real benchmarking work.
Window
6-12 months

Where to find first users

  • Show HN / Product Hunt launch targeting the original post's audience
  • Podcasting tool communities (r/podcasting, Descript/Riverside user forums)
  • Legal and medical transcription software marketplaces and add-on directories
  • Cold outreach to call-center QA and workforce-management vendors needing custom vocabulary

Competitors

Counter-signals & risks

  • The demonstrated technique is a local, Mac-only hobbyist tool; turning it into a reliable cross-platform SaaS requires significant engineering work and may not generalize across accents, noisy audio, or multiple custom terms at once.

  • Established STT vendors (Deepgram, AssemblyAI, OpenAI) already offer custom vocabulary, keyword boosting, or fine-tuning, which could make a thin wrapper product easily commoditized.

  • Legal and medical dictation are regulated verticals with strict data privacy and accuracy certification requirements, raising the adoption barrier for a new, unproven add-on layer.

Original title: Show HN: Teach a speech model (en) a name by saying it once, on your Mac

  • Developer tools#4

    MCP Connector Library for AI Coding Agents

    Build a ready-made MCP (Model Context Protocol) server or toolkit that connects Claude, Cursor, and Codex to popular third-party APIs and services, enabling AI coding agents to automate integrations without manual glue code. Package it as a hosted service or CLI tool targeting solo developers and small teams who use AI-first IDEs. Monetize via subscription access to a growing library of pre-built MCP connectors.

    Demand
    7/10
    est.
    Buildability
    7/10
    est.
    Competition
    7/10
    est.
    via Product Hunt
    22 competitors
  • Developer tools#7

    Plan State Persistence Layer for Claude Code Re-Runs

    Build a lightweight plan persistence and idempotency layer for Claude Code that tracks executed plan steps, stores state between runs, and prevents duplicate actions on re-runs. Target solo developers and small teams using Claude Code for multi-step agentic workflows who lose progress when sessions restart or plans re-execute from scratch.

    Demand
    6/10
    est.
    Buildability
    8/10
    est.
    Competition
    8/10
    est.
    via Product Hunt
    11 competitor
  • Developer tools#8

    Developer Context Save and Restore Tool as Micro-SaaS

    Build a lightweight SaaS or CLI-plus-web-app called something like Park that lets developers save and restore full work context — open files, terminal state, branch, notes, clipboard snippets — across multiple repos and machines. Sell it as a subscription to solo developers and small teams who constantly context-switch and lose their train of thought. Integrate with VS Code and JetBrains as a plugin for frictionless adoption.

    Demand
    1/10
    measured
    Buildability
    7/10
    est.
    Competition
    6/10
    est.
    via Hacker News
    33 competitors
Voice-taught custom vocabulary for speech-to-text — Nichr