Creative Queue · through Nov 13, 2026

2026 01 16 product launch messaging


date: 2026-01-16 title: "Ittai + Adrian: debrief Yuval and prototype a successful-product-launch page" products: [creative-queue] attendees: [Adrian, Ittai] duration: 108m grain: https://grain.com/share/recording/f5c09719-a335-472c-bae8-1df4e07c06b0/iWvmjEEqLzOofSG5KUCKPAjWxIin2bg46Zhl92mK tags: [gtm, messaging, positioning, naming]


Ittai + Adrian: debrief Yuval and prototype a successful-product-launch page

Thursday, Jan 16, 2026, 4:45 PM America/New_York, 108 minutes. Immediately after Yuval x Creative Queue.

What they took from Yuval

Ittai: Yuval said, with more clarity, what he had been trying to say — get the story right, and make it much simpler than they have been saying it. "Successful product launches" landed.

They named four things to come back to: message, name, internal structure (including how it works financially), and later "roles and goals." Adrian's view: the mechanics of the product do not have to change much; how they relate to and describe it does. Ittai felt the message itself had to change.

Message they were testing

Adrian sketched three overlapping stories that cover buyers and users without extra explanation: successful product launch, successful campaign launch, and successful brand launch. Ittai wanted them to pick one. His cut: the product is the nucleus, so the line is "successful product launches, period." Adrian agreed that was the correct thing.

Urgency they wanted on the page: if you do not get the launch right, the brand never gets the leverage it needs to survive. Adrian: paint the villain as death of the brand / bad launches kill brand momentum. Later copy he liked in that vein: every missed product launch is ground you never get back; if you cannot keep up you will disappear.

Name

Ittai was more convinced after Yuval that they should talk about the name. Adrian said he had felt for more than a year that the name no longer reflects what they are, and that he had said that to Brandon; some branding people they talked to said the name was fine, and he disagreed. They kicked around domains (including ideas like Product Rocket and liftoff.io) and found the ones they liked were taken. No rename was decided. Adrian treated naming as a bigger exercise than this working session.

Landing-page prototype

Adrian duplicated the current site onto a new yuval branch and used the transcript to rewrite the homepage around "the piece of infrastructure that brands need to drive successful product launches." The old schema, in his words, was closer to "content marketing without the stress."

Working fragments from the session (prototypes, not a public claim):

  • Header should include both "successful" and "product launch." "Operating system" evokes infrastructure, which Adrian wanted, but he thought it belonged in a subhead rather than the lead. Ittai first preferred "solution" (shorter, less likely to elicit the wrong idea); after Adrian's infrastructure point he said he was convinced on the idea, while they kept iterating length.
  • Three value buckets he tried: launch faster, launch better, and avoid expensive mistakes. A later pass he liked: "get there first," "build experiences worth remembering," and "see the gaps before you pay for them."
  • Comparison set: the spreadsheets and documents people use (not smart, not connected); AI tools that help with strategy but do not make the details easy to implement; project-management tools that are not tracking this product-centric problem. He later asked to leave AI tools out of that grid and bring decks in: Creative Queue vs project-management tools vs decks vs spreadsheets.
  • Two "how" stories: better intelligence, and centralized data in one place.
  • He noted that this positioning change would make their existing videos and other media out of date.

He planned to send Ittai something Ittai could forward to Yuval to see how it felt. They did not treat that send as done on this call.

What they scheduled next

  • Come back to name and company structure. The MIKUTA pilot would take a lot of attention in the meantime; they could work on message during that.
  • "Roles and goals" with everyone together, aimed around Friday, Jan 23, 2026 (Ittai's 23rd looked good; Brandon was traveling that week). See the Jan 23 follow-up.

Jorge / Manhattan group — set up for Feb 13

Ittai had put a Feb 13 meeting on the calendar with Jorge (Ittai spelled the last name Cofre). Background he gave: fashion backend optimization, a stretch at an appliance company where they had met, then back into fashion. Grain later titles that call Jorge X Creative Queue. He was described here as Director of Digital Commerce, living in Canada, originally from South America. Ittai thought Jorge had said he had heard of Creative Queue; both were unsure whether that was real. Ittai had already texted him the website.

The opportunity, as they understood it in this room: Jorge sits with Manhattan Inc., a group with many brands (they named Super Dry and G-Star among them). Adrian called it a big deal — the kind of company, other than selling to brands directly, that they need to be talking to. Soft-pitch plan: ask about the current tech stack and how the group works; be very clear about what Creative Queue does; aim for introductions to the people who would actually implement (head of marketing, head of creative operations, or similar). They did not think Jorge himself was the implementation buyer. Adrian wanted a briefing from Michaela (Daniel's partner; senior e-commerce site manager, formerly in the West Elm orbit) so he would not go in cold.

A personal aside at the end of the recording is not filed here.