Portfolio case study

Vox: Voice-to-Text AI Strategy MVP Engine

Vox AI StartupB2B SaaS / Voice AI

Project overview

We developed a real-time web application using Next.js App Router, React Server Actions, and API integrations with speech-to-text engines and OpenAI. Implemented responsive layout structures and client-side markdown rendering to ensure instant visual feedback.

Outcome

A fast, validation-first product demonstration that helped the startup founders secure early user feedback and pitch to investors with a production-ready application.

Client & context

Client
Vox AI Startup
Industry
B2B SaaS / Voice AI

Services provided

  • Web app development
  • Voice AI Integration

Technologies used

Next.jsTypeScriptTailwind CSS

Business challenge

The founders needed to prove their Voice AI concept with an interactive MVP. The application had to process spoken startup ideas, transcribe them instantly, query LLMs to generate detailed markdown roadmaps, and support exports to Notion with minimal latency.

Technical audit

  • Performance review
  • Accessibility review
  • Content and SEO audit

Strategy

  • Rebuild the experience with a faster front-end foundation
  • Clarify conversion paths
  • Improve messaging and performance together

Technical implementation

  • Modern component architecture
  • Responsive layout system
  • Performance-aligned implementation

Performance optimization

  • Image optimization
  • Asset reduction
  • Faster rendering on mobile

SEO improvements

  • Metadata and crawlability improvements
  • Improved semantic structure
  • Internal linking and schema

Business impact

  • A stronger first impression
  • Better trust and clarity
  • Improved lead-generation foundation

Lessons learned

  • Performance and content clarity compound each other
  • A better experience makes the business story easier to trust

Why Next.js

  • Fast rendering and modern architecture
  • Better SEO and performance fundamentals
  • A strong foundation for scalable growth

Why the previous website was slow

  • Heavier front-end structure
  • Legacy delivery patterns
  • Weaker mobile performance and content hierarchy

Frequently asked questions

Practical answers around the strategy, build process, and performance outcomes behind this project.

The project needed a faster, more trustworthy experience that also supported stronger conversion behavior.
The rebuild reduced friction, improved perceived quality, and created a stronger technical foundation.