Show the product promise before the user reads a single paragraph.
This large visual slot works for a product collage, an app-in-kitchen shot, or a polished mockup that explains Palate’s value in one glance.
Palate reads your pantry, learns your taste, and gives you 3 grounded recipe decisions — not 300 options. Calm. Fast. Yours.
Join the waitlist. We're rolling out to a small group first — people who actually cook.
No spam. No noise. Just Palate, when it's ready.
Confirm your spot from the link we just sent.
Then we'll reach
out when access opens up.
Palate is designed to disappear. The judgment stays; the friction doesn't.
Scan a receipt, photograph your fridge, or add items manually. Palate builds a live picture of what you actually have.
Not a scrolling list. Three dishes — chosen for your pantry, your household, your time, and your taste. Ranked, not random.
Cook Mode walks you through it. When you're done, Palate updates your pantry automatically. No manual tracking required.
These are intentionally replaceable marketing blocks. They make the landing page feel complete now, while leaving room for your final screenshots and brand photography later.
This large visual slot works for a product collage, an app-in-kitchen shot, or a polished mockup that explains Palate’s value in one glance.
Use this panel for a real app screenshot showing the ranked meal suggestions flow.
Use this panel for either pantry understanding, onboarding, or a polished confirmation state.
Every interaction in Palate is designed to reduce load, not add it.
Palate builds a flavor profile from what you actually cook — without questionnaires or explicit ratings.
Recipes only surface if you genuinely have the key ingredients. No phantom grocery runs.
Context matters. Palate reads time of day, day of week, and household size to calibrate effort and ambition.
Your data lives on your device. The cloud is for sync and smarts — never for selling your dinner to an ad network.
Palate is asking for your email and your attention. This section makes the default concerns clear before the user has to go looking.
The site can explicitly state what gets collected at waitlist time, what does not, and where users can read the full policy.
Early access is framed as deliberate and limited, which makes the signup feel credible rather than artificially urgent.
The page keeps returning to concrete utility: fewer decisions, less waste, and a calmer path from pantry to dinner.
The problem isn't knowing how to cook.
It's deciding what.
A landing page for a waitlist should remove friction. These questions are the minimum set for clarity and trust.
That should be easy. A landing page that asks for trust should make contact obvious.
[email protected]Join the waitlist. Palate is rolling out slowly and deliberately — to the people who'll use it most.
No spam. No noise. Just Palate, when it's ready.