{"id":1152,"date":"2026-05-12T07:07:37","date_gmt":"2026-05-12T07:07:37","guid":{"rendered":"https:\/\/fisgroup.mastersofbrands.co.uk\/?post_type=service&p=1152"},"modified":"2026-05-29T18:09:05","modified_gmt":"2026-05-29T18:09:05","slug":"product-testing-ihut-clts-in-restaurant","status":"publish","type":"service","link":"https:\/\/fisgroup.mastersofbrands.co.uk\/service\/build-test-and-refine-what-wins\/product-testing-ihut-clts-in-restaurant","title":{"rendered":"Product Testing (IHUT, CLTs, in-restaurant)"},"content":{"rendered":"\n
\n\n
\n\n

Product Testing<\/p>\n \n

Product Testing for food and drink, consumer evaluation that closes the decision gate before launch<\/h1>\n \n

Specialist consumer product testing for food and drink innovation. Three formats: IHUT (in-home use testing for home-consumed products), CLT (central location testing for controlled tasting and comparative work), and in-restaurant testing (for menu items in real foodservice context). Food and drink-specific metrics framework throughout, senior interpretation alongside the quantitative work. The decision gate before commercial launch.<\/p>\n \n \n <\/div>\n\n

\n \"\" <\/div>\n \n <\/div>\n<\/section>\n\n
\n
\n\n
\n

What Product Testing is actually for<\/h2>\n

Most product launches fail at the same point. The product passed concept screening, the development team built it credibly, the leadership team committed to the launch. But the product underperforms with consumers in real consumption context: the in-context experience did not match the concept performance, the operational reality changed the consumer experience, the multi-use experience exposed issues a single-trial test could not capture. The launch was approved against concept evidence and concept testing, not against the consumer reality the product itself will be evaluated on.<\/p>\n

The structural problem is that concept testing and product testing answer different questions. Concept testing evaluates whether the concept idea appeals (will the proposition land); product testing evaluates whether the actual product delivers when consumers use it (does the product perform on the proposition). The two are complementary at different stages of the innovation flow. Concept testing closes the development gate; product testing closes the launch gate. Skipping the product testing layer means committing real launch investment against concept evidence rather than against product evidence, which is structurally why product launches fail even when concept testing predicted success.<\/p>\n<\/div>\n <\/div>\n\n

\n

Product Testing is the structured consumer evaluation methodology for actual products in the context consumers will use them. Three formats scoped against the brief: IHUT for products consumed at home (real-life use over multiple occasions), CLT for products requiring controlled tasting conditions (sensory work, comparative testing, blind tests), in-restaurant testing for menu items where the foodservice context is part of the product experience. Senior food and drink specialists run the work, food and drink-specific metrics framework throughout, output structured for the commercial decision the testing has to support.<\/p>\n

It is not the right tool for every brief. If the brief is concept testing (testing the proposition or idea rather than the actual product), Concept Screening is the right tool. If the brief is qualitative consumer evaluation rather than decision-grade quantitative testing, Qualitative Product Testing is the more proportionate alternative. If the brief is exploratory product feedback rather than pre-launch validation, focus groups or Concept Labs may be more appropriate. Product Testing sits specifically when developed products need decision-grade consumer evaluation in the context consumers will use them.<\/p>\n<\/div>\n

\n \"\" <\/div>\n <\/div>\n\n <\/div>\n<\/section>\n\n
\n
\n
\n\n
\n

What we do differently<\/h2>\n <\/div>\n \n \n <\/div>\n <\/div>\n<\/section>\n\n
\n
\n\n
    \n\n \n
  1. \n Step 1<\/span>\n
    Three formats scoped against the consumer reality the product faces<\/h6>\n

    The structural flexibility. Different products face different consumer realities and need different testing methodologies. Home-consumed FMCG products need IHUT to evaluate real-use experience across multiple occasions. Products requiring controlled comparison (sensory work, blind tests, comparative tasting) need CLT methodology. Menu items in foodservice need in-restaurant testing to evaluate the integrated dining experience alongside the operational reality. We scope the right format at the start of each brief against the consumer reality the product will face, rather than defaulting to one methodology regardless of product type.<\/p>\n <\/li>\n

  2. \n Step 2<\/span>\n
    Food and drink-specific metrics framework, not generic FMCG product testing<\/h6>\n

    Most product testing applies generic metrics: liking, purchase intent, satisfaction. Useful but incomplete. Our metrics framework is built around food and drink-specific commercial reality: in-context performance (does the product deliver on the occasion it was designed for), repeat appeal (does the product hold up across multiple uses or just at first trial), distinctive ownership in use (does the product earn its place against alternatives in real consumption), purchase intent in context (intent measured at the actual purchase moment), and category-specific dimensions where they predict commercial performance. The framework is what makes the testing results commercially decisive rather than just descriptively informative.<\/p>\n <\/li>\n

  3. \n Step 3<\/span>\n
    Senior food and drink interpretation throughout<\/h6>\n

    The technical difficulty of product testing is reading what the scores actually mean for commercial decisions rather than taking the scores at face value. A product that scores well in IHUT might fail at scale for operational reasons the testing did not capture. A menu item that scores well in restaurant testing might not translate to other foodservice contexts or operator types. Senior food and drink specialists interpret the testing data against the real commercial reality of the launch, which is the layer that separates useful product testing from a chart pack of scores. We do not deliver decks of numbers without the interpretation that translates them into commercial direction.<\/p>\n <\/li>\n

  4. \n Step 4<\/span>\n
    Designed to feed forward into commercial launch decisions<\/h6>\n

    Every Product Testing project closes with output scoped for the launch decision the work has to support: confidence assessment for go\/no-go launch decisions, sizing implications grounded in product performance, audience and channel recommendations based on test cuts, identification of product issues that need addressing before scale launch. The deliverable is built for board, investment committee, NPD committee and brand leadership scrutiny rather than for analytical internal consumption. The work pays for itself in the launch decision, not in the testing evidence.<\/p>\n <\/li>\n \n <\/ol>\n \n <\/div>\n<\/section>\n\n

    \n
    \n
    \n\n
    \n

    What we use Product Testing for<\/h2>\n <\/div>\n \n \n <\/div>\n <\/div>\n<\/section>\n\n
    \n
    \n
    \n
    \n
    \n

    Pre-launch product validation for FMCG launches<\/h4>\n

    You have developed FMCG products (typically from R&D Sprints or internal NPD work) that need consumer validation before commercial launch. IHUT methodology evaluates the products in real home-consumption context across multiple uses, with sample sizes scoped against board and investment committee scrutiny. Output is launch-ready evidence base, with the prioritisation logic transparent and the product performance defensible against retailer or commercial committee scrutiny.<\/p>\n <\/div>\n <\/div>\n

    \n
    \n

    Menu item validation in real foodservice context<\/h4>\n

    You have developed menu items (typically from Menu Development) that need consumer evaluation in real foodservice context rather than just in development kitchens or controlled testing. In-restaurant testing evaluates the integrated dining experience: the menu item alongside the service, the operational reality, the actual consumption context. Output is operational-pilot-ready validation, with the menu item performance grounded in real foodservice rather than in controlled conditions.<\/p>\n <\/div>\n <\/div>\n

    \n
    \n

    Comparative testing for product range decisions<\/h4>\n

    You have multiple product options (range alternatives, reformulation options, variant choices) and need comparative consumer evidence to decide which goes to launch. CLT methodology runs the comparative tasting in controlled conditions, with the methodology scoped to surface the comparative consumer preference reliably. Output supports range decisions defensibly when the inevitable “why did we choose this option” question gets asked.<\/p>\n <\/div>\n <\/div>\n

    \n
    \n

    Reformulation validation before scale rollout<\/h4>\n

    You are reformulating an existing product (cost reduction, recipe simplification, ingredient change, dietary positioning) and need consumer validation that the reformulation does not compromise the consumer experience. Product Testing methodology evaluates the reformulation against the current product, with the methodology scoped to surface any consumer detection or preference shift reliably. Critical for cost-reduction reformulation where consumer detection would undermine the commercial case.<\/p>\n <\/div>\n <\/div>\n

    \n
    \n

    Sensory and tasting work for premium tier products<\/h4>\n

    You have premium tier products (premium FMCG, premium menu items, premium ingredient applications) where sensory performance matters disproportionately to commercial success. CLT methodology with food and drink-specific sensory framework evaluates the products at the depth premium positioning requires. Output supports premium pricing decisions, premium tier communication and premium quality positioning with consumer-validated evidence.<\/p>\n <\/div>\n <\/div>\n

    \n
    \n

    Pre-launch testing for retailer presentation evidence<\/h4>\n

    You are presenting products to retailers and need pre-launch consumer testing evidence to support the listing case. Product Testing provides retailer-ready evidence: defensible methodology, decision-grade samples, food and drink-specific metrics, output structured for retailer commercial conversations. Often commissioned alongside the broader Challenge 05 launch services (Retailer Pitch Support, Briefing Pack Creation) as part of the integrated retailer presentation work.<\/p>\n <\/div>\n <\/div>\n <\/div>\n <\/div>\n<\/section>\n\n

    \n
    \n\n
      \n\n
    1. \n

      How a Product Testing project runs<\/h2>\n

      From developed product to launch-ready evidence<\/h5>\n <\/li>\n \n
    2. \n Step 1<\/span>\n
      Scoping call.<\/h6>\n

      Twenty minutes on a call. You tell us the products to test, where they came from (R&D Sprints, Menu Development, internal NPD, reformulation work), the consumer reality the product faces (home consumption, controlled comparison, foodservice context), the launch decision the testing has to support, the audience for the deliverable (board, NPD committee, brand leadership, retailer) and the timeline. We tell you which format is right for the brief (IHUT, CLT, in-restaurant), what sample size makes sense, what metrics the brief implies, and roughly what it will cost. Where the brief would be better served by Concept Screening (proposition testing rather than product testing), by Qualitative Product Testing (qualitative rather than quantitative), or by Menu Testing (menu architecture rather than item-level), we will recommend the right alternative honestly.<\/p>\n <\/li>\n

    3. \n Step 2<\/span>\n
      Testing design.<\/h6>\n

      The senior team designs the testing methodology specifically against the decision the work has to support: format choice (IHUT, CLT, in-restaurant), sample sizes and audience profiles, the food and drink-specific metric framework calibrated for the product type, the cuts and the analytical approach. Design signed off by the client before fieldwork starts so the methodology is transparent and the analytical structure is agreed against the launch decision the work feeds.<\/p>\n <\/li>\n

    4. \n Step 3<\/span>\n
      Fieldwork.<\/h6>\n

      Quantitative research through specialist food and drink panels, IHUT logistics partners, CLT venues, or in-restaurant testing in real foodservice context (depending on format). Sample sizes scoped to deliver decision-grade evidence for the launch context. Product stimulus presented at appropriate fidelity for the testing format (real consumption for IHUT, controlled tasting for CLT, real foodservice context for in-restaurant). Full quality checks throughout.<\/p>\n <\/li>\n

    5. \n Step 4<\/span>\n
      Senior synthesis and interpretation.<\/h6>\n

      The senior team runs the analytical work and develops the interpretive layer: how the product performs against the food and drink-specific metrics, what the performance predicts for commercial outcomes, what the cuts reveal about audience and channel performance, what issues need addressing before scale launch. The interpretation is what makes the testing commercially decisive rather than just analytically complete, and is led by senior specialists who can read what the scores actually mean for the launch.<\/p>\n <\/li>\n

    6. \n Step 5<\/span>\n
      Decision-ready readout.<\/h6>\n

      A working readout session walking the team through the testing results and the launch implications, followed by the full deliverable: product performance assessment, go\/no-go launch confidence rating, sizing and channel implications, audience and operational recommendations, transparent flagging of any issues that need addressing before scale launch. The deliverable is built for the decision audience (board, investment committee, NPD committee, brand leadership, retailer presentation) and lands within three weeks of fieldwork completion.<\/p>\n <\/li>\n \n <\/ol>\n \n <\/div>\n<\/section>\n\n

      \n
      \n
      \n\n
      \n

      Three formats. Scoped to the consumer reality your product faces.<\/h2>\n

      Different products face different consumer realities. The three Product Testing formats below are the methodologies we apply against those different realities, with the format selected at scoping rather than assumed. Home-consumed products need IHUT to evaluate real-use experience; comparative or controlled testing needs CLT; menu items in foodservice context need in-restaurant testing. Some briefs use a single format; others combine two or three for multi-format launch evidence.<\/p>\n <\/div>\n \n \n <\/div>\n <\/div>\n<\/section>\n\n

      \n\n
      \n\n
      \n
      \n

      IHUT (In-Home Use Testing)<\/h2>\n

      Products distributed to consumers for use in their own homes across multiple occasions, evaluated through structured methodology that captures real-life consumption experience. Used when the product is consumed at home and the multi-use experience matters: FMCG food, drinks, household-consumed products, products where repeat appeal or in-context performance predicts commercial success. The methodology surfaces what controlled testing cannot: actual storage, preparation, consumption rhythm, integration with daily life. Typically delivers decision-grade evidence within eight to twelve weeks.<\/p>\n<\/div>\n <\/div>\n <\/div>\n\n

      \n \"\" <\/div>\n\n <\/div>\n\n<\/section>\n\n
      \n\n
      \n\n
      \n
      \n

      CLT (Central Location Testing)<\/h2>\n

      Consumers come to a central location to test products in controlled conditions, evaluated through structured methodology designed for comparative or sensory work. Used when controlled comparison is critical (range option testing, reformulation validation, comparative tasting, sensory work), when the product requires controlled preparation (chilled, hot, freshly-prepared), or when the central location matches the consumption context (some foodservice items). The methodology surfaces what IHUT cannot: controlled comparative judgement, sensory detail, blind testing reliability. Typically delivers within six to ten weeks.<\/p>\n<\/div>\n <\/div>\n <\/div>\n\n

      \n \"\" <\/div>\n\n <\/div>\n\n<\/section>\n\n
      \n\n
      \n\n
      \n
      \n

      In-restaurant Testing<\/h2>\n

      Menu items tested in real foodservice context (restaurants, QSR, hospitality venues, pubs, contract catering operations), evaluated through structured methodology designed for the integrated dining experience. Used when the menu item depends on real foodservice context for credible evaluation: service quality, ambience, operational reality, integrated dining experience. The methodology surfaces what kitchen-only or central-location testing cannot: how the menu item performs alongside the service, what the operational reality does to the consumer experience, how the item integrates into the broader menu. Typically delivers within eight to twelve weeks.<\/p>\n<\/div>\n <\/div>\n <\/div>\n\n

      \n
      <\/div>\n \"\" <\/div>\n\n <\/div>\n\n<\/section>\n\n
      \n
      \n
      \n\n
      \n

      Food and drink is all we do<\/h2>\n

      We are not a generalist research agency that takes the occasional food brief. Food and drink is the only sector we work in. Our senior team knows specifically how product testing correlates with commercial performance in this sector, which categories the standard FMCG metrics work for and which they miss, where the interpretation needs to push against the surface scores. Our IHUT operations are scoped for food and drink-specific home consumption reality; our CLT methodology integrates food and drink-specific sensory frameworks; our in-restaurant capability runs through real foodservice partnerships rather than approximated test venues. Generic product testing can deliver scores; sector specialists can read what the scores predict for commercial launch decisions.<\/p>\n

      That focus is why we work with 11 of the UK’s top 40 food and drink brands.<\/p>\n <\/div>\n \n

      \n Meet the Team<\/a>\n <\/div>\n \n <\/div>\n <\/div>\n<\/section>\n\n
      \n
      \n
      \n\n
      \n

      Other ways to build, test and refine what wins<\/h2>\n

      Product Testing is one tool in the broader Build, Test & Refine What Wins toolkit. Depending on the brief, one of these might be a better fit, or a stronger partner alongside the Product Testing work.<\/p>\n <\/div>\n \n \n <\/div>\n <\/div>\n<\/section>\n\n