How a founder turned a voice note into 112 developer-ready prompts

Maxim K. had an idea for a travel app. Not a spec, not a wireframe — a voice note. He talked for a few minutes about affiliate monetization, budget splitting among friends, and trip planning features. Then he sent it to Ooih in Telegram and went to make coffee.

When he came back, Ooih had turned that voice note into 112 structured, copy-paste-ready prompts — organized into groups, ready for implementation.

What happened

Maxim is the kind of founder who thinks faster than he types. He runs multiple projects, jumps between ideas, and doesn't have time to write formal briefs. The traditional path from "idea in my head" to "something a developer can build" usually takes days: meetings, documents, revisions, more meetings.

His voice note was messy by design. He rambled about affiliate models, mentioned a feature for splitting trip costs, described how he imagined the booking flow, and threw in thoughts about testing. It was a brain dump — the kind of thing you'd normally need a product manager to unpack over a week.

Ooih listened, identified the structure underneath the chaos, and produced:

• 50 feature-build prompts — each one a self-contained instruction for building a specific feature, from the affiliate suggestion engine to the budget-splitting UI
• 12 affiliate monetization prompts — covering the deals hub, click tracking, admin dashboard, and revenue attribution
• 18 testing prompts — end-to-end test scenarios for every major user flow
• 32 supporting prompts — setup instructions, database schemas, API integrations, and a master orchestration prompt that ties everything together

Each prompt was written so a developer (or another AI tool) could pick it up and start building immediately — no interpretation needed.

Why this matters

The gap between "I have an idea" and "someone can build this" is where most projects stall. Founders sit on ideas because the effort of specifying them feels overwhelming. Product managers spend weeks translating business intent into technical requirements. Developers get vague briefs and build the wrong thing.

Maxim skipped all of that. He spent three minutes talking into his phone. Ooih spent a few minutes structuring. The result was more thorough than most product requirement documents — because Ooih didn't just transcribe, it organized.

It identified the natural categories in Maxim's stream of thought. It separated features from monetization from testing. It wrote each prompt in a format that could be directly used, not a summary that needs further breakdown.

The reaction

Maxim's response when he saw the output:

"You are a machine!"

He later used the same approach for his automotive catalog project, his marketing strategy, and his DNS setup. The pattern works the same way every time: describe what you want in your own words, get back structured work you can act on immediately.

What this shows about Ooih

Most AI tools can summarize a voice note. Ooih doesn't summarize — it structures for execution. The difference matters:

• A summary tells you what was said. Ooih tells you what to build.
• A transcript preserves the chaos. Ooih finds the architecture inside it.
• A chatbot waits for you to ask the right questions. Ooih figures out what you need without being asked.

There was no prompt engineering involved. Maxim didn't say "create 50 feature prompts organized by category." He talked about his app like he was describing it to a friend. Ooih did the product management work automatically.

Try it yourself

If you have an idea sitting in your head — a product, a marketing plan, a project structure — try saying it out loud. Send the voice note to Ooih. The gap between thought and execution might be shorter than you think.

One chat. Every task. No setup. $99/mo flat — start in Telegram.