# Made In turned Instagram DMs into a product development engine, sourcing cookware ideas at zero acquisition cost *The brand monitors direct messages for feature requests and material preferences, feeding R&D without surveys or panels.* By **Jenny Huang Goodman MPA MSc MHSA, Principal** — The Stash Edge, Hako Shikin LLC. Published 2026-09-09. Canonical: https://www.pops4.com/stash/articles/made-in-2026-09-09t21-3 Subject: Made In Tags: community play, product development, instagram, customer feedback, owned channels --- Made In, the Austin-based cookware brand, treats its Instagram direct messages as an unfiltered product development channel, according to Modern Retail. The company monitors inbound DMs for recurring feature requests, material preferences, and complaints about existing products, then routes that intelligence directly to its design and sourcing teams. The result: new SKUs informed by customer language, not consultant decks. The mechanic is simple. Made In's social team flags messages that mention specific product gaps—"do you make a 10-inch nonstick?" or "I wish this pan had a helper handle." When the same request appears repeatedly, it goes into a tracking document shared with product managers. Modern Retail notes that brands like Plainspeak and Springrose use the same approach, treating DMs as a real-time focus group that costs nothing to convene and reflects actual purchase intent, not hypothetical survey answers. This works because Instagram DMs carry selection bias in the right direction. The people messaging a cookware brand are already bought in—they follow the account, they've probably purchased, and they're motivated enough to type out a specific request. That's a higher-signal audience than a paid panel or a pop-up survey that interrupts checkout. The messages also arrive in natural language, so the brand hears how customers actually describe a problem, not how a market research firm frames the question. When Made In later launches that 10-inch nonstick, it can use the exact phrasing from DMs in the product copy, creating instant resonance with the segment that asked for it. The other advantage: speed. A traditional product development cycle might start with a brand hypothesizing a gap, commissioning research, analyzing results, then building a prototype. DM-driven development flips that. The gap announces itself, often with volume data—"we've had 40 messages about this in two weeks." The brand can move to prototyping immediately, or even reply to those 40 people with a prototype image and ask if they'd buy it. That turns the DM thread into a pre-launch validation loop, reducing the risk that the new SKU launches to silence. A small physical-product brand runs this play with one founder and no social team. Set up a dedicated folder in your email or a Slack channel where you manually forward every DM that mentions a product request, a missing feature, or a workaround the customer invented. Do this for 30 days. At the end, sort by keyword—handle, size, color, material. If the same request appears five times or more, you have a validated product idea from people who already know your brand. Draft a reply template: "We're considering a [product]. If we made it, would you buy one at [price]?" Send that to everyone who mentioned it. If half say yes, prototype it. If ten say yes and you're making it anyway, offer them a pre-order discount for the feedback. Cost: your time. Payoff: a product launch with built-in demand and copy written by your customers. The broader pattern is using owned channels as R&D infrastructure. Email replies, customer service transcripts, and DMs all contain the same intelligence that brands used to pay research firms to extract. The difference now is speed and cost. A brand that treats every inbound message as a potential product signal can iterate faster than a competitor still running annual surveys, and it builds products using the exact words that will convert the next customer who has the same need. ## The takeaway Route Instagram DMs into a product request tracker; launch features that appear five or more times using customer language. --- ## Publisher **Hako Shikin LLC** — Virginia Beach, Virginia. Founded 1997. ASI 217876 · DUNS 18-204-6339. Principal and author: **Jenny Huang Goodman MPA MSc MHSA**. - Author: https://www.huanggoodman.com/about - LLM context: https://www.pops4.com/stash/llms.txt - MCP endpoint, for AI agents: https://mcp.pops4.com/mcp - Client dashboard: https://dashboard.pops4.com/ - Catalogue: 70,000+ products, 200+ brands