# Divya Subramaniam, Senior Qualitative Research Lead at Ipsos India — read of Interview Researcher, June 22 2026 > 9 years in qual research, currently managing 4-person team running consumer insight projects for FMCG and fintech clients across Maharashtra, Tamil Nadu, and Karnataka. My tool stack is Zoom, Rev.ai, NVivo, and way too many Google Sheets. I have a 6-year-old who goes to bed at 8:30, so I do most of my tool research on the 45-minute Metro ride to Andheri. --- ## How I got here I Googled "qualitative research software Indian languages transcription" after our NVivo license came up for renewal and I started doing the math. We pay per seat and half our analysts barely touch it between project cycles. Found this on page 2 of results, clicked through because the title was unusually direct. No one in this space names their product what it actually does. --- ## What I clicked first "Pay Per Interview, Not Per Seat" stopped me. That's the right framing. I've had exactly this argument with procurement three times. The math they give -- "Conduct 10 interviews a year? You'll spend $5" -- is clean enough that I actually stopped and re-read it. No asterisks visible. That's rare. The Indian language list also made me pause. Hindi, Tamil, Telugu, Kannada, Malayalam, Marathi. That's not a throwaway line. Someone thought about this. "Built natively, not translated. Maintains cultural nuance and context that machine translation loses" is a claim I want to test, not one I believe yet. --- ## Where I paused The testimonial from Priya Sharma. "We were spending three weeks on analysis per round of research. With Interview Researcher, we have themes by day three." That's a specific claim. Three weeks to three days is not incremental, that's a different process. I wanted to click through and find more about the Bangalore EdTech company. There's no link. No company name. No follow-up quote about what they actually do with the extra two weeks. I read it twice. It's one quote. One person. One company category. For a product centered on research methodology, that's thin. --- ## What I distrusted The footer broke the frame completely. "Resources for this product: FAQ, Email drip, Outreach pack, Skeptic memos (3), More ideas like this one." Then: "Adopt this idea. Browse free. Unlock for $5. Adopt for $99." Then: "Honest disclosure: we don't have live customers on this idea yet. We shipped the strategy package; you ship the customer conversations." So Priya Sharma is... what exactly? A projected persona? A beta user who tried a prototype? The page doesn't say. The testimonial reads like real customer data. The footer says no live customers exist yet. That's not a tension I can resolve in the buyer's favor. The whole page shifts from "product you can buy and use" to "idea you can adopt and build." Those are different things. One is a tool I'm evaluating for my team. The other is a business concept I'd be taking on as an operator. I came here as a researcher looking for software. I'm now reading a pitch deck in disguise. Also: "More ideas like this one -- Demand Gen AI, Afterhours, Signal Digest." This is a concept factory. That doesn't mean the idea is bad. It means the product doesn't exist yet in the form the hero implies. --- ## What would convince me If this were a real product: I want to see a 10-minute unedited screen recording of someone uploading a Tamil interview and walking through what the theme synthesis actually looks like. Not a demo video with a voiceover. The actual UI, actual output, the edge cases where it gets the sentiment wrong. On the native language claim specifically: show me a side-by-side of the same interview run through machine translation versus your native pipeline on something linguistically tricky, like code-switching between Hindi and English the way urban respondents actually talk. That would do more work than any testimonial. And if this is an "adopt this idea" product: I want to understand what the $0.50 actually covers on the cost side, because at that price point either the transcription is outsourced to a low-cost provider with quality tradeoffs, or the founders haven't done the unit economics yet. --- ## What I'd ask in an email reply 1. The page says "built natively, not translated" for Indian languages. What does natively mean technically? Is this a fine-tuned model, a partnership with an Indian ASR provider, or something else? Who built the language pipeline? 2. Priya Sharma's quote is compelling but the disclosure says no live customers yet. What was Priya's context -- early beta, internal test, hypothetical projection? I'm not trying to catch anyone out, I just need to know what category of evidence that is before I share it upward. 3. What happens when a respondent switches mid-interview between Tamil and English? That's not an edge case in our work, it's the norm. Does the system handle it, flag it, or fall apart? --- ## Verdict: on-the-fence The pricing model is genuinely smart and the language focus is a real gap in this market. But the page is doing two different jobs -- selling a product and selling an idea -- and it doesn't pick one. If this is a live tool I can start using tomorrow, I want to see that clearly. If it's a concept I'd be building, I need a different conversation. --- *Memo by skeptic persona, generated 2026-06-22. Studio breaks own self-grading loop.*