Start with an audit

Let’s talk.

Tell us what you’re working on. A person from the team replies to every enquiry, with a time for a 30-minute call.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.
Specialist service · product discovery workshop

Product discovery workshop

You receive a user story map, a prioritised MVP backlog, a clickable Figma prototype of key flows, an architecture and integration note, and an estimate with stated assumptions, usable with any development team.

Product Engineering practice: abstract red and ink artwork from the Red Balloon reel

Teams that skip discovery usually pay for it later in rework, scope arguments and features nobody uses. A product discovery workshop gives founders, product owners and business heads a structured few weeks to agree what to build first, for whom and why, before committing a development budget. Red Balloon runs workshops for freight, legal, healthcare and SaaS ventures, combining stakeholder sessions, user interviews and quick prototype tests with the people who will pay. Disagreements are settled with evidence rather than seniority. Senior product and engineering people run the sessions, so the plan reflects what can realistically be built and maintained, not just what everyone would like to have.

What sets the length and cost of a discovery engagement

A product discovery workshop is short by design, but its length still varies. The main drivers are how many user groups the product serves, how hard those users are to reach, and how settled the idea already is. A tool for one type of user in one city needs fewer interviews than a two-sided marketplace serving truckers and shippers across several states. Interviews in Hindi or regional languages need the right researcher, and field visits take longer than video calls.

Regulated sectors add time, because legal, healthcare and financial products need their rules checked before scope is fixed. So do integrations, when an estimate depends on what a third-party system can actually do. We scope these factors in the first conversation and give a fixed fee before the workshop starts, so discovery never becomes an open-ended cost.

The four outcomes discovery can lead to

Discovery ends with a decision, and it is not always build as planned. Sometimes the evidence supports the original idea, and the output is a tested scope and estimate. More often it narrows the idea: one user group, two core journeys and a list of features deliberately left for later. A narrower first release costs less, ships sooner and gives cleaner evidence about what to build next.

The other two outcomes are harder to hear. Research may show that a different buyer has the stronger need, so the product changes direction before any code is written. Or it may show that the problem is real but people will not pay to solve it this way, and the honest recommendation is to stop. Each outcome comes with the interview notes and test results behind it, so you can check the reasoning yourself.

From workshop output to the first sprint

The gap between a discovery report and a working build is where momentum often dies. We close it by turning the prioritised backlog into tickets in Jira or Linear, with acceptance criteria written from the research, and by naming the technical spikes that must run first, such as testing a payment gateway or a third-party API. The Figma prototype becomes the starting point for the design system rather than a throwaway.

If you build with us, the same people move into the MVP team, so nothing is lost in a handover. If the product needs a market plan alongside the build, our Launch & Go-to-Market practice can use the same research to shape positioning, pricing tests and the first acquisition channels. If you take the work to another vendor, every file is handed over in editable form.

Running discovery on a product that already exists

Discovery is not only for new ideas. Established products use it before adding a major module, entering a new customer segment, or rescuing a feature that launched and was ignored. In these cases there is more evidence to start from: product analytics, support tickets, sales call notes and churn reasons. We review that material first, so interviews focus on the questions the data cannot answer.

The output looks similar, with a tested prototype, ranked scope and an estimate, but it also covers how the change fits the existing architecture and what it means for current users. That stops a new module from being designed as if the rest of the product did not exist, which is a common reason additions feel bolted on.

Where this works

Real-world situations we're built for

Illustrative · not a client
Freight / logistics

Gurugram freight broker wants a trucker app but the team can't agree what to build first

What we'd do
Two-week discovery: interviews with 10 truckers and 5 shippers, journey maps, ranked assumptions, prototype test
What moves
Estimate spread down, MVP feature count down; tracked as estimate spread before and after discovery
Legal services

Delhi law firm wants to productise contract review for small businesses

What we'd do
Workshop to define the buyer, test willingness to pay with a landing page and prototype, review Bar Council of India advertising limits
What moves
Waitlist sign-up rate up, time to a go/no-go decision down
How a project runs

4 phases, each with a deliverable

What happens, how long it takes, what you get and what we need from you.

Prepare

2–3 days

Stakeholder interviews, review existing data, recruit users; most common delay: recruiting real users, so screeners go out on day one

You get: Workshop agenda and research plan

We need: Stakeholder list and user contacts

Workshop

1–2 days

Goals, assumption mapping, journey mapping, prioritisation

You get: Ranked assumptions and draft scope

We need: Decision-makers in the room

Research and prototype

1–2 weeks

Interviews, prototype, usability tests

You get: Tested prototype and insights

We need: Feedback within 48 hours

Plan

3–5 days

Architecture, estimate, roadmap, risks

You get: Discovery report and estimate

We need: Final review meeting

A typical engagement

From first call to result

Illustrative · not a client

Chandigarh dental chain, 14 clinics, wants a patient app; owners disagree on features

Week 1Workshop daysGoals, constraints, stakeholder map and assumption mapping with owners and clinic managersRanked assumption list
Weeks 1–2User research8 patient interviews and 4 front-desk shadowing sessions across 2 clinics, with recorded consentInsights summary; recall reminders emerge as the top need
Week 2Prototype and testFigma prototype of booking and recall reminders tested with 6 patients; rework any task fewer than 5 of 6 complete unaided (rule of thumb)Validated flows; 40 items cut to 9
Week 3Plan and estimateArchitecture outline, integration check with the clinic software, phased roadmapScope, estimate and success metric: recall visit rate
Where it starts40-item feature wishlist, a ₹30 lakh budget in mind, no user research, recall visits tracked on paper
Where it endsA tested scope, roadmap and estimate both owners agree on. They will track recall visit rate, online booking share and no-show rate.
What we measure

The numbers we report on

Every metric has a formula, a target, a source and a reporting rhythm.

MetricHow it's calculatedTargetSourceCadence
Riskiest assumptions testedTop assumptions with evidence ÷ top assumptions listedAll top three tested before build startsAssumption board in Miro or FigJamEnd of discovery
Prototype task successParticipants completing a task unaided ÷ participantsSet a target per task before testing; rework tasks below itModerated sessions, Maze or LyssnaEach test round
Scope reductionFeatures in MVP scope ÷ features on the original wishlistAgreed in the workshop; most items should move to later phasesBacklog in Jira, Linear or NotionEnd of discovery
Estimate spreadHigh estimate ÷ low estimateNarrower after discovery than before itEstimate sheetStart and end of discovery
Automated by default

What runs itself after launch

The manual work we take out of this service, and the tools we use.

When: Participant agrees to take partInterview schedulingCalendly or Cal.com with a consent form and remindersRemoves: Back-and-forth messages and no-shows
When: After each interviewTranscription and taggingDovetail or Otter.ai with tags, under recorded consentRemoves: Hours of note-taking and lost quotes
When: Prototype readyUnmoderated prototype testsMaze or Lyssna importing the Figma prototype, reporting task success, misclick rate and time on taskRemoves: Slow recruiting and manual scoring
Rules we work to

Standards and regulations

ISOISO 9241-210 (human-centred design for interactive systems)

Grounds discovery in research with real users, iteration and evaluation

MeitYDPDP Act 2023 and DPDP Rules 2025

Interview recordings are personal data: take consent, state purpose, store securely and delete on schedule; main duties apply from 13 May 2027

What's changing

Platform and policy updates that affect this work

We track: Figma release notes, Nielsen Norman Group articles.

FigmaFigma Make (prompt-to-prototype) and Figma Sites launched at Config

Test prototypes can be produced faster; check them against real technical constraints

MeitYDPDP Rules 2025 notified; main duties apply from 13 May 2027

Research consent and recording retention need a documented process

Before you hire anyone

Questions to ask any agency, including us

Will you tell us not to build if the evidence says so?

Why ask

Discovery only has value if stopping is a possible answer

A good answer

Examples of discovery work that ended in a pivot or a no-build decision

Who runs the user interviews, and how are they trained?

Why ask

Leading questions produce false confidence

A good answer

A named researcher, a sample interview guide and how bias is avoided

Can we take the discovery output to another build vendor?

Why ask

You should own the outcome, not be locked in

A good answer

Yes: scope, prototype, estimate assumptions and research handed over in editable formats

FAQ

Questions buyers ask us

Straight answers from the practice lead. Highlighted text marks Red Balloon figures we confirm before publishing.

Who from our side needs to attend the discovery workshop, and for how long?

Plan for the decision-maker, a domain expert and whoever will run the product, across 3–5 half-day sessions over one to two weeks, in person or remotely on Miro and Figma.

  • The decision-maker must attend the scoping session; scope reopened by someone who missed it is the most common source of delay.
  • Bring existing spreadsheets, current tools, competitor examples and known compliance requirements; async prototype reviews between sessions keep meeting time short.
Do you test the idea with real users during discovery?

Where possible, we interview five to eight target users and run the clickable prototype past them, so the backlog reflects what users struggled with rather than only what the team assumed.

  • Nielsen Norman Group's research found that about five users reveal most usability problems in a single test round.
  • Users are recruited from your customer base or a panel, with incentives sized to the audience.
  • Sessions are recorded only with each participant's clear, recorded consent, which the DPDP Act requires from May 2027.
  • Watch for workarounds, not opinions: a user who switches to WhatsApp mid-task to ask a colleague is the finding that changes scope.
Can a product discovery workshop in India include users in other cities?

Yes. Most user interviews and prototype tests run well over video, so users anywhere in India, or abroad, can take part. When the product depends on how people work on site, such as in warehouses, clinics or shops, we plan field visits. Workshop days with your team can run at our Gurugram or New Delhi offices, at your premises or remotely on Miro and Figma.

  • Remote interviews reach any city
  • Field visits when context matters
  • Workshop days in person or remote
Do we need discovery if we already have a detailed requirements document?

Often a shorter version, yes. A requirements document records what the team believes users need; discovery checks whether users agree and whether the scope is the smallest one worth building. We start from your document rather than ignoring it, test its riskiest assumptions with users, and usually return a narrower first release with a firmer estimate.

  • Your document is the starting point
  • Riskiest assumptions tested with users
  • Usually a narrower, firmer scope
Back to the service

MVP development →

Start with an audit

Ready for
lift?

A paid two-week Growth Audit covers your funnel, ads, site, tracking and automation gaps, and ends with a 90-day plan you can run with or without us. The fee is credited against your next engagement.

Prefer to talk? Call +91 97114 48083, or email info@redballoon.in.

A person from the team replies to every enquiry.

What do you need?
Your details are sent over a secure, encrypted connection and only used to reply to you.