Skip to content
Palate-IQ®

Palate-IQ®

For wineries

Evaluate Palate-IQ with a focused winery pilot

A pilot is a scoped evaluation conversation—not a fixed commercial package. Together we decide what to test, how to measure it, and what your team needs in place before any broader rollout.

1. What is being tested

Typical pilots focus on consumer onboarding into a branded experience, Will I Like It? palate-fit guidance, Open Tonight when eligible bottles exist in My Cellar, and, when useful, an optional operator-insight flow on opted-in members. Exact experiences are agreed for your audience; we do not claim every winery runs the same package.

2. Winery inputs and dependencies

Scope, branding, catalog, invite list, consent, and connectivity are agreed jointly. A pilot usually needs a usable demo catalog, brand presentation, a defined invited group, privacy and consent choices, an operator contact, and any storefront or partner connection required for the flows you want to evaluate. Nothing here assumes automatic or zero-effort integration.

3. Evaluation method

Before launch we align on a baseline, comparison approach, and denominators (for example who counts as invited versus activated). Opted-in participants can introduce selection bias; sample size and comparison-group design are documented up front so results stay interpretable. Recommendation clicks, cart handoffs, orders, and incremental sales are treated as separate events—not the same metric.

4. Metrics

Some measures can be supported from Palate-IQ usage. Purchases, AOV, cross-sell, and longer-window retention are discussed only if the winery supplies commerce data and agrees an attribution method. No lift is promised.

Supportable from Palate-IQ usage

Example measureWhy a winery might track it
Activation rateShare of invited members who start using the experience
Return visitsWhether activated members come back in a defined window
Recommendations viewedEngagement with personalized fit guidance such as Will I Like It?
Handoff clicksClicks that continue into the winery storefront or cart path

Only with winery commerce data and agreed attribution

Example measureCondition
PurchasesOrders attributed only if commerce data and a method are agreed
Average order value (AOV)Comparable only with a shared baseline and attribution rules
Cross-sellNew varietal or wine purchases when order lines are available
Longer-window retentionCancel or renewal patterns over a period the winery defines

5. Scope and responsibilities

Responsibilities for setup, invites, operator follow-up, and measurement are set together. This page does not publish price, timeline, headcount, or guaranteed results. Palate-IQ does not own checkout; cart handoff stays with your storefront tools.

6. Request an evaluation discussion

Use the homepage form with pilot intent selected. A person will follow up to confirm a time and scope the conversation.

Back to Palate-IQ