Build a Text to Speech Generator with Claude Code

Build a Text to Speech Generator web app. People search for "text to speech generator" about 8,900 times a month, plus related searches like "text to voice converter", "speech synthesis online", "voice generator from text". The goal is a tool that ranks for those searches and makes money.

What it should do:
Build a text to speech generator web app. Create a homepage with a large text input area and voice selection dropdown (male, female, different accents). Add controls for speech speed, pitch, and volume. When users generate speech, show an audio player with waveform visualization and download options (MP3, WAV). Include text highlighting that follows the speech playback. Add batch processing for multiple texts and SSML support for advanced control. Use a voice-focused design with blue and purple gradients. Focus on the text input and voice generation 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 ElevenLabs, Amazon Polly, Google Text-to-Speech do it and make ours simpler and faster.
3. Make it rank. Use "text to speech generator" 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: /text-to-speech-[voice-type], /tts-generator-[language], /voice-synthesis-[accent].
4. Monetisation: Freemium: 1000 characters/day, $9/mo unlimited + premium voices. 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.