Skip to content
Troy Corbitt
← All work

Independent product · 2026 · Private beta

Insight Studio

From customer signals to product decisions.

I designed and developed an AI-powered product intelligence platform that helps teams consolidate customer feedback, investigate trends, compare product experiences, and turn research into evidence-backed product decisions.

Deployed · Private betaExplore live product ↗View product walkthrough ↓

The application is currently in private beta. Existing users can sign in, and synthetic demonstration data is available where supported.

Project type
Independent product · Web application
Status
Deployed · Private beta
My role
Product Strategy, UX Design & Full-Stack Development
Team
Solo
Tools
Figma, Next.js, TypeScript, Supabase, OpenAI API, Recharts, Vercel
Timeline
2026

The result

A deployed private-beta web app connecting feedback, research, opportunities, prioritization and roadmap.

Product StrategyUX ResearchAINext.jsSupabase

The problem

The problem started with fragmented customer feedback.

During my Customer Experience Design internship at Vimeo, I worked with customer feedback, churn cases and product usage information across different systems — consolidating signals, finding recurring problems, and turning observations into recommendations other teams could act on.

Organizations collect plenty of feedback, but it lives on disconnected platforms. Even when valuable patterns exist, finding them, verifying them and communicating them across teams takes a lot of manual effort.

  • Customer reviews
  • Social discussions
  • Support feedback
  • Customer conversations
  • Product usage data
  1. Fragmented evidence
  2. Manual synthesis
  3. Difficult cross-team alignment

→ Insight Studio

Conceptual diagram of the problem — not a list of live integrations.

The opportunity

What if customer research and product planning were connected?

Rather than another AI sentiment dashboard, I wanted a shared workspace where teams consolidate feedback, examine the evidence, and turn findings into product opportunities.

  • What problems are customers repeatedly discussing?
  • Which experiences get praise or criticism?
  • How are those discussions changing over time?
  • What can we learn from competing products?
  • Which findings deserve more research?
  • How should findings inform product decisions?

Primary users

  • Product Managers
  • UX Researchers

Secondary

  • Customer Success
  • Engineering
  • Marketing

Design targets — not segments validated through formal interviews.

Product strategy

Designing a feedback-to-decision workflow.

The key strategic choice: connect feedback analysis with research documentation, opportunity management and planning — so the product is a workflow, not just a dashboard.

Feedback

Discover and organize customer signals.

Feedback Explorer · synthetic demo comments

A closer look

A closer look at Insight Studio.

Bring feedback into a shared workspace, classify customer comments, and monitor changing pain points and preferences.

  • Manual and CSV feedback ingestion
  • AI classification
  • Original feedback inspection
  • Historical trend analysis
Feedback Explorer · synthetic demo comments
Trends · sentiment over time and emerging pain points

Competitive thinking

Finding a differentiated product direction.

I studied existing customer research platforms. Both already offer AI analysis and feedback workflows that overlap with Insight Studio.

Usercall

Emphasizes AI-moderated conversations, research workflows and qualitative insight generation.

Visit site ↗

UserTesting

Supports usability testing, participant feedback and human insight workflows.

Visit site ↗

Insight Studio

A proposed focus on continuous cross-source feedback, feature-level competitive patterns, evidence validation, and links into product planning.

Decisions & tradeoffs

The decisions that shaped the product.

Iteration

Building the product exposed new usability challenges.

These came from my own hands-on testing, not a formal participant study.

  1. 01 · Observed

    The Roadmap showed empty Now, Next and Later columns without explaining how to add an opportunity.

    Design response

    Clearer roadmap descriptions, a visible Add opportunity action, and an explained link between opportunities and stages.

    Current screen · Roadmap
  2. 02 · Observed

    A roadmap card showed “RICE 40” with no explanation of the metric.

    Design response

    RICE explanations, visible assumptions, a worked calculation and prioritization guidance.

    Current screen · Prioritization · RICE explained
  3. 03 · Observed

    The Research Library showed the five-stage workflow, but some steps didn't navigate anywhere.

    Design response

    Made the five-stage workflow a consistent, clickable navigation component on every stage.

  4. 04 · Observed

    Some screens needed too much scrolling or packed too much into one view.

    Design response

    More focused layouts, stronger hierarchy, progressive disclosure and clearer primary actions.

External usability testing with participants is planned for the private beta.

Technical execution

From concept to deployed application.

I implemented the product end to end, with security and data integrity treated as product decisions.

  1. User interface
  2. Secure application logic
  3. Supabase database
  • AI classification
  • Authorized external data access
  • Research & planning workflows

Outcomes & status

What I built and what comes next.

Deployed private beta

Completed

  • A functional customer intelligence web app
  • Feedback ingestion and classification
  • Historical trends and competitive intelligence
  • Research documentation and evidence linking
  • Opportunities, RICE prioritization and roadmapping
  • Cross-functional team insights
  • External integration groundwork with access restrictions
  • Deployment to Vercel
  • Authentication and private-beta registration controls
  • Navigation and usability fixes from testing

Still needs validation

  • Usability with external participants
  • Which workflows give the most value
  • Effectiveness vs. existing tools
  • Adoption and retention
  • Long-term commercial viability
  • Broader third-party platform access

A working deployment is an engineering milestone, not proof of product-market fit.

Reflection

What this project taught me.

Insight Studio connected parts of product development I'd only experienced separately: understanding customer problems, designing experiences, translating insights into requirements, and building working solutions.

My biggest takeaway: implementing features isn't the same as making them understandable. Technically functional workflows were still confusing when the relationships between pages, metrics and actions weren't clear — so navigation, information architecture, evidence quality and usability are product decisions, not finishing touches.

Next, I want to learn from real users and see whether Insight Studio meaningfully improves how teams move from feedback to decisions.

Try it

Explore Insight Studio.

A working product exploring how customer research, competitive intelligence and product planning can come together in one workspace.

Next project

Viewpoint Vault

Creating space for perspectives that go unheard.

Open to Product · Product Design · UX Research · Tech roles

Got a problem worth untangling? Let's talk.