To
Product teams, and engineering teams that care about product
From
Uvesh Menpurwala
Re
How I decide what to build
Updated
Oct 2025

Product judgement, with the engineering to ship it.

Taking products from proof of concept to release.

  1. TL;DR 1

    5 case studies

    Products I worked on: the problem, the calls I made, and what changed.

01Start from the journey

From SyncIT. Scrub through it.

  1. Connect
  2. Download
  3. Review
  4. Report
  5. Configure

They

Pairs the instrument over BLE, Wi-Fi/LAN or serial

It hurts

A different app per instrument family

The fix

One app for every supported instrument

02The calls that mattered

What was on the table, what I chose, and why.

    • Maintain each app
    • One cross-platform product(chosen)

    Why: One product is simpler for customers and gives one roadmap instead of several.

    from SyncIT →

03Before and after

From SpeakUp. Drag to compare.

before

Typical language app

  • Needs a connection
  • Account before the first lesson
  • Often a subscription

after

SpeakUp

  • Works fully offline
  • No account
  • Record and play back on the device
← beforeafter →

04All the work

Case studies, teardowns and proposals, newest first.

Want to talk it through?

I’m happy to walk through any of these in more depth, including the parts that didn’t work.

uveshmenpur.03@gmail.com

— Uvesh Menpurwala