Build an Audio to Text Converter with Claude Code

Build an Audio to Text Converter web app. People search for "audio to text converter" about 69,000 times a month, plus related searches like "transcribe audio to text", "speech to text converter", "audio transcription online". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build an audio to text converter web app. Create a homepage with upload options for audio/video files or microphone recording. When users upload a file, show processing progress with estimated completion time. Display the transcribed text in an editable text area with speaker identification and timestamps. Add download options (TXT, DOCX, SRT subtitles) and playback controls synced with text highlighting. Include language selection and accuracy confidence scores. Use a professional design with green and blue accents. Focus on the upload and transcription flow first.

How to build it:
1. Read this folder first. If it is empty, set up Next.js (App Router, TypeScript, Tailwind). Write a short PLAN.md with the pages, components, any library or API you need, and what you are leaving for later. Then build.
2. Put the tool itself on the homepage so a visitor can use it within seconds, with no sign-up. Do the processing in the browser where you can, so it is fast and cheap to run. Look at how Otter.ai, Rev, Trint do it and make ours simpler and faster.
3. Make it rank. Use "audio to text converter" in the title tag, H1 and meta description. Under the tool, add a short how-to and an FAQ with FAQPage schema, and add a sitemap and robots.txt. Scaffold these programmatic pages from one template and a data file: /transcribe-[audio-format]-to-text, /audio-to-text-for-[profession], /speech-to-text-[language].
4. Monetisation: Freemium: 30min/month, $10/mo unlimited + speaker ID. Add a pricing page and the free usage limit, and leave Stripe checkout as a clearly marked stub with the environment variables it needs.
5. Run it locally and test the main flow end to end, including edge cases like empty input and very large files. Fix what breaks, then finish with a summary of what works, what is stubbed and how to deploy it to Vercel.

Paste it into Claude Code in an empty folder. It plans first, so read PLAN.md and steer before it starts building.