How do you choose a design thinking consultancy in India?

In March 2026, Commerce and Industry Minister Piyush Goyal told an industry audience that India should treat design as "a strategic national capability rather than cosmetic", pointing to a median age of about 28.5 and nearly 2.3 million STEM graduates a year as the raw material (Construction World, 16 March 2026). The market has heard him. Almost every UX studio, IT services firm and management consultancy in India now lists "design thinking" on its services page. For a founder or product head with a real problem and a limited budget, that abundance is the difficulty: the label tells you nothing about whether the firm will change what you build.

We run design thinking engagements at Qodequay, so we are not neutral. But we have also sat on the buying side, and the questions below are the ones we would ask of ourselves. Use them to separate practitioners from workshop vendors.

What should a design thinking consultancy actually deliver?

Strip away the sticky notes and a design thinking engagement produces four things: primary research with the people who will use the product, a synthesis that turns that research into a small number of defensible problem statements, prototypes that real users have tried, and a decision. The decision is the point. A good engagement ends with your team knowing what to build next, what not to build, and why, with the evidence attached.

If a proposal describes a two-day workshop, an "ideation session" and a deck of personas, and nothing in it mentions recruiting users, interviewing them or testing something with them, it is a facilitation service, not design thinking. Facilitation has its place, but it is priced and bought differently. Our earlier piece on whether design thinking delivers ROI for Indian product teams sets out what measurable outcomes to expect.

Which seven questions separate real practitioners from workshop vendors?

Put these in your RFP or ask them on the first call. The answers are more revealing than the credentials slide.

1. Show me two engagements from the last 18 months with before-and-after numbers. Activation rate, task completion time, support tickets, conversion, adoption in a pilot district. Vague "improved experience" claims are a warning sign.
2. Who will recruit and interview our users, and how many? Expect a named researcher, a recruitment plan for your segment (a Tier-2 MSME owner is not a Bengaluru product manager) and a number: five to eight interviews per segment per round is a reasonable floor.
3. Send a sample timeline from a comparable project. A July 2026 comparison of design consultancies makes the same point: the sample timeline shows whether the firm's default process fits your stage, and whether a six-week discovery phase is going to burn runway you do not have (Parallel, 2 July 2026).
4. What will we hold at the end that an engineer can build from? Tested prototype, prioritised backlog, research repository, decision log. If the answer is "a strategy deck", ask who turns it into a product.
5. Who is in the room on day one, and who is in the room in week six? Partner-led pitches followed by junior-led delivery are a common complaint from Indian buyers. Get names in the SOW.
6. How do you use AI in research and synthesis, and where do you refuse to? Transcription and clustering are fair game; synthetic users standing in for real customers are not. We explained the line in Can AI replace user research?
7. What happens to our users' interview data? Interview recordings and transcripts are personal data. Ask for consent scripts, retention periods and whether recordings leave India. A consultancy that cannot answer this in 2026 is a risk you will inherit.

How much should you expect to pay in India?

Indian pricing has settled into recognisable bands. The numbers below combine our own quoting experience with the ranges we published in How much does a design thinking workshop cost in India? Treat them as planning figures for a mid-size company, not quotes.

Engagement	Typical duration	Typical India fee	What you should receive
Facilitated workshop	1–2 days	₹30,000–1.5 lakh per facilitator-day	Framed problem, aligned stakeholders, prioritised hypotheses; no user evidence yet
Design sprint	5 working days	₹1.5–7.5 lakh	One prototype tested with 5–8 users, decision memo
Discovery engagement	4–8 weeks	₹8–25 lakh	Research across 2–3 segments, journey maps, 2–3 tested prototypes, build-ready backlog
Embedded design partner	3–6 months	₹3–8 lakh per month	Research and design capacity inside your squad; usually only worth it once a build is funded

Two observations. First, international benchmarks are higher: the same July 2026 comparison puts the product-design work that "moves the needle" for a SaaS company in a US$30,000–60,000 band, with enterprise consultancies starting at US$50,000 and 3–6-month timelines. An Indian team with equivalent research rigour typically lands at a third to a half of that. Second, the cheapest day rate is rarely the cheapest engagement. A firm that misreads your users costs you the build that follows, which is usually ten to twenty times the research budget.

What are the red flags?

• The deliverable is a workshop. No recruitment, no interviews, no test sessions in the plan.
• Personas arrive before research. If the firm already "knows" your user on the first call, it is selling templates.
• No Indian field experience in your segment. Researching farmers in Vidarbha, ZP school teachers or NBFC collection agents is different work from researching urban app users, and the firm should be able to show it has done the former.
• Sprint theatre. A five-day sprint that ends on Friday with a clickable prototype nobody outside the room has used.
• Ownership gaps. IP in the prototypes, research data and design system is not assigned to you in writing.
• Hand-off cliff. The firm has no engineers and no relationship with the team that will build, so the backlog decays within a quarter.

Global firm, Indian boutique or a product company's design practice?

Three kinds of supplier now compete for the same Indian briefs. None is universally right; the fit depends on what happens after the research.

Supplier type	Strength	Watch for	Best when
Global innovation consultancy	Brand credibility with boards; mature methods	Premium pricing; partner-led sales, associate-led delivery; thin Tier-2/3 field presence	Board-level transformation with a seven-figure (US$) budget
Indian design boutique	Craft, speed, local recruiting networks, honest pricing	Small bench; may stop at hand-off; variable research rigour	Focused product problems, 5-day sprints, early-stage startups
Product company with a design practice (Qodequay's model)	Research is tied to a build; the same team ships the outcome	Check that research is independent of the sales motion	You want evidence, then a working product, from one accountable team

Our own bias is the third row. Qodequay runs design thinking consulting alongside product engineering and immersive learning; our Abhigyaan VR platform, now deployed in 1,350 Maharashtra Zilla Parishad schools and reaching 1.5 million-plus students, came out of that combined team. The argument for the model is simple: the research is only as valuable as the thing that gets built from it. Our note on running design thinking before an MVP shows what that sequence looks like in practice.

How do you run a low-risk pilot before signing?

Whatever the supplier type, the safest purchase is a paid pilot with a hard stop. It costs ₹2–5 lakh and ten working days, and it tells you more than three rounds of proposals.

1. Pick one real problem that your team currently disagrees about, not a toy brief.
2. Agree the success test in writing: for example, "five to eight interviews with Tier-2 MSME owners, one tested prototype, a decision memo the CEO signs off".
3. Name the people on both sides, and keep the consultancy's named researcher in the pilot.
4. Give data access on your terms: consent scripts approved by you, recordings stored in India, deleted on an agreed date.
5. Hold a go/no-go review on day 10 against the test you wrote on day one, and only then negotiate the larger engagement.

If the pilot produces a decision your team would not have reached on its own, you have found your partner. If it produces a deck, you have saved yourself a much larger invoice.

Talk to us about a pilot

We are happy to be evaluated on exactly the questions above. Bring one problem your product team is stuck on and we will scope a ten-day pilot with named researchers, a recruitment plan for your Indian user segment and a decision memo at the end. Book a 30-minute scoping call.

This article is for general information and is not legal, procurement or financial advice. Fee ranges are planning estimates based on Qodequay's experience and published market comparisons; confirm scope, pricing and contract terms with the firms you shortlist.