Pomelli Photoshoot: Fast studio-quality assets

Start from a single image of your product and easily create high quality, customized product shots to elevate your marketing.

A jar in your hand. A whole shoot in your CMS

Start with the most ordinary thing in e-commerce. A single product photo, shot on a desk, held in a hand, good enough for internal approval but nowhere near “campaign-ready”. Then imagine turning that one image into a set of studio and lifestyle shots that look like you planned the lighting, the surface, the props, and the framing.

That is the pitch behind Photoshoot, a feature inside Pomelli from Google Labs: take a basic product image and generate professional-grade marketing imagery fast, without booking a studio for every new variant. “Studio-grade” here means assets that can sit on a PDP or paid social without instantly looking like “placeholder content”.

How Photoshoot turns one product photo into usable marketing imagery

Photoshoot is not just “generate me a nicer background”. It is a guided flow designed to keep output consistent.

  1. Pick a product photo. The input can be imperfect. The tool is explicitly designed to handle “don’t worry about polish”.
  2. Choose a template. Templates are pre-built shot styles (for example studio or lifestyle) that constrain composition so results do not drift into random aesthetics.
  3. Generate. Pomelli applies your brand aesthetic via its Business DNA, then generates new shots. Business DNA is Pomelli’s saved brand profile derived from your website (voice, fonts, imagery, color palette).
  4. Refine. You iterate with finishing touches, then download assets or store them back into Business DNA for reuse in later campaigns.

Under the hood, Google describes this as combining business context (Business DNA) with Nano Banana image generation to produce the final scenes.

In high-velocity retail and FMCG e-commerce teams shipping new SKUs (Stock Keeping Units) and promos weekly across many markets, this is the shortest path from “we have a product” to “we have compliant, channel-ready variants”.

The real question is whether one approved product shot can produce enough on-brand variants to increase throughput without increasing review drag.

Why it lands. Because it cuts the real friction, not the fun part

Most teams are not blocked on “having ideas”. They are blocked on throughput with consistency: getting enough variants, in enough formats, that still look on-brand, pass review, and do not trigger rework across design, legal, and local markets.

This is why the mechanism matters. Because Photoshoot grounds outputs in Business DNA and constrains composition via templates, the results tend to feel brand-consistent faster, which reduces review churn and makes variant production scalable.

Extractable takeaway: If you want generative creative to survive enterprise review, do not start with infinite freedom. Start with constraints that encode your brand (a reusable brand profile) and your channel rules (shot templates), then let the model fill in the pixels inside that box.

The business intent is blunt. Production leverage for asset variants

“Production leverage” is the multiplier you get when one person-hour produces many more usable assets without multiplying headcount or agency spend. For e-commerce teams, Photoshoot is essentially a variant engine.

  • More PDP (Product Detail Pages) imagery coverage without re-shooting every pack change.
  • More paid social iterations without waiting on design queues.
  • Faster seasonal refreshes when the same SKU needs a new context (spring, gifting, back-to-work).
  • A tighter loop between merchandising and creative because the cost of “try another angle” collapses.

Important reality check: you still need governance. Treat outputs like any other marketing asset. Rights, claims, pack accuracy, and local compliance do not disappear just because generation is fast.

Where to try it?

The Pomelli app on Google Labs is where you can access the experience.

However availability is currently limited. Pomelli has been launched as a public beta experiment in the United States, Canada, Australia, and New Zealand (English).

What to steal for your next asset sprint if the app is available in your region

  • Codify brand constraints first. Build a reusable “brand profile” (fonts, tone, visual rules) before you chase more generations.
  • Template your shots like you template layouts. Decide the 6 to 10 shot types you actually need (hero studio, detail crop, lifestyle context, ingredient cue) and standardize them.
  • Design for review speed. Define what “acceptable” means (pack legibility, logo integrity, claims, background rules), then generate inside those rails.
  • Run a SKU ladder test. Start with 10 SKUs across easy and hard surfaces (glass, reflective, metallic). If it fails there, it will fail at scale.
  • Instrument the pipeline. Track time-to-first-usable, approval rate, and rework causes. That is how you prove leverage, not by “wow, looks nice”.

A few fast answers before you act

What is Pomelli Photoshoot, in one sentence?

Pomelli Photoshoot is a feature inside Google Labs’ Pomelli that turns a single product photo into professional-style studio and lifestyle marketing images using brand context and image generation.

What is the mechanic marketers should care about?

You choose a product image, select a curated template (studio or lifestyle), generate variants grounded in your Business DNA, then refine and download or reuse those assets in future campaigns.

What does “Business DNA” actually mean here?

Business DNA is Pomelli’s saved brand profile derived from your website, such as tone of voice, fonts, imagery, and color palette, which Pomelli uses to keep generated outputs consistent.

Where is Pomelli available right now?

Pomelli is in public beta in English in the United States, Canada, Australia, and New Zealand. It is not currently available in Germany.

What is the first safe way to pilot this in an enterprise team?

Pilot it on a small SKU set with strict shot templates and review criteria, then measure approval rate and rework reasons before scaling variant production.

From AI Tool List to Working AI Tech Stack

From “pick 20 tools” to “run a working stack”

I recently came across the below video from Dan Martell which frames “zero-code million-dollar business” as a tool-selection problem. That framing is useful. However the right conclusion for marketers and brands watching is not “go pick 20 tools”. The right conclusion is “stop shopping. Start stacking”. In 2026, you should start focusing more on the ability to pick, connect, and operationalize capabilities.

By “working AI tech stack” I mean a small, repeatable set of tools that moves work from input to output with the least friction. It is not a folder of bookmarks. It is a production line.

The useful takeaway isn’t the list. It’s the operating model.

Most people consume AI content and walk away with a shopping list. That is the wrong takeaway. The useful takeaway is operational. Arrange capabilities into a workflow that consistently produces outputs. Briefs, assets, approvals, launches, responses, and measurable improvements.

A list creates options. A stack creates throughput. Throughput is how reliably your team converts intent into shipped work, week after week, without rebuilding the process every time.

The mechanism: a stack is just clean handoffs

A working AI tech stack is a sequence with explicit handoffs:

Inputs → Synthesis → Creation → Automation → Distribution → Measurement

Each step has one job. Each step produces an artifact someone else can use. Each handoff is defined so the work does not stall in Slack, email, or “waiting for approval”.

In global FMCG and retail marketing organizations, the bottleneck is rarely ideas but the handoffs between people, tools, and approvals.

Why this lands with leaders

Tool lists feel like progress because they are concrete and low-commitment. You can bookmark them and feel “covered”. Stacks feel harder because they force decisions: what is the workflow, who owns each step, where do we enforce quality and risk controls.

Extractable takeaway: If you cannot name the exact step a tool owns in a repeatable workflow (input → transformation → handoff → output), it is not part of your stack yet. It is just potential.

The business intent: less software. More shipped outcomes

For marketers and brands, the goal is not “using AI”. The goal is operational leverage:

The real question is not how many AI tools you can name, but whether your team can move work through a repeatable line with clear ownership and handoffs.

  • Faster cycle time from brief to asset.
  • Fewer revision loops because synthesis and constraints are done upfront.
  • Fewer dropped balls because handoffs are automated.
  • More reuse of institutional knowledge because answers are captured once and searchable.
  • Higher output without lowering standards.

This is also where governance belongs. A stack needs rules about what data can go where, who can approve what, and which steps require a human decision.

The working stack blueprint: tools mapped from Inputs to Measurement

Below are the 20 tools referenced in the video, placed where they most naturally fit in the production line. You can use fewer than 20. The point is the flow.

Inputs: capture raw material without losing signal

Manus

Manus is designed to act more like a task runner than a chatbot. You give it a goal and it works through steps to deliver outputs, not just advice. Example: collect competitor screenshots, extract claims, summarize patterns, and deliver a brief plus a slide outline.

SocialSweep

SocialSweep is positioned as a way to search your network and relationship graph with context. It helps you identify who you know, why they are relevant, and what to say. Example: find warm paths to retail media decision-makers, then draft an intro message that references shared context.

HireAlli

HireAlli is positioned around capturing commercial intent from website traffic so teams can follow up faster. Example: flag repeat visits to pricing pages, then route the lead to sales with a summary of pages viewed and a recommended next message.

Synthesis: turn messy inputs into a usable brief and plan

NotebookLM

NotebookLM is useful when you want answers grounded in the sources you provide. It helps you summarize, compare, and extract structure from documents. Example: upload research PDFs and prior campaign docs, then generate a launch FAQ and a messaging hierarchy that stays consistent with those materials.

Claude

Claude is a general assistant that excels at drafting, rewriting, and structuring thinking. Use it to turn raw notes into clear decisions and action plans. Example: paste a workshop transcript and request a decision log, assumptions, risks, and a one-page brief for stakeholders.

ChatGPT

ChatGPT is a general-purpose assistant for ideation, drafting, analysis, and reusable workflows. It is especially useful when you iterate toward a spec. Example: ask clarifying questions for a campaign brief, then output a structured creative and media spec the team can execute.

Creation: produce assets that are actually shippable

Gamma

Gamma helps turn rough thinking into a structured deck or document quickly. It is strong when the bottleneck is narrative structure, not visual polish. Example: paste the brief, generate a 10-slide storyline, then refine the argument and flow before design.

Descript

Descript lets you edit audio and video through text. You edit the transcript like a document and the media follows. Example: clean up a leadership video by removing filler words, tightening sections, and exporting both a long version and short clips.

ElevenLabs

ElevenLabs generates natural-sounding speech from text and supports scalable voice workflows. It is useful for narration, localization, and voiceovers. Example: create a consistent “brand voice” narration for product explainers, then generate localized voiceovers without re-recording.

Lovable

Lovable is positioned as an AI-assisted way to build apps or web experiences without traditional engineering. Think prototypes, internal tools, and simple customer experiences. Example: describe an internal campaign intake tool, generate a prototype, then iterate requirements until it is usable.

Automation: make the handoffs run without nagging humans

Make

Make connects apps into workflows using triggers and actions. It is the plumbing that turns “good tools” into “a working line”. Example: when a brief is approved, create tasks, notify stakeholders, generate a first draft, and route it to review automatically.

ChatAid

ChatAid is positioned as an AI support layer that can answer recurring questions and route issues. It fits both internal enablement and customer-facing support when designed with escalation rules. Example: answer “where is the latest asset” or “what is the policy”, and escalate to a human when confidence is low.

Distribution: move outputs into channels that drive outcomes

Revio

Revio is positioned around managing inbound conversations across social channels in one place. It helps teams respond consistently and not miss high-intent messages. Example: unify DMs so customer questions and sales inquiries do not get lost across platforms.

YourAtlas

YourAtlas is positioned around AI agents that can handle inbound qualification and booking. This matters in service businesses and lead-driven funnels. Example: handle inbound calls or requests 24/7, capture required details, then hand off qualified appointments to humans.

Membership.io

Membership.io supports structured memberships and gated content experiences. It is a distribution layer for expertise and ongoing value, not just content hosting. Example: package a learning path for partners or teams, with searchable resources and a community layer to reduce repeated questions.

BuddyPro

BuddyPro is positioned around turning your content and methods into an always-on assistant people can query. It is a distribution mechanism for expertise at scale. Example: clients query your “playbook assistant” for next steps between calls, and you control what it can and cannot answer.

Measurement: close the loop so the stack improves every cycle

Hiro Finance

Hiro Finance is positioned around cash-flow visibility and planning. It helps decision-makers see financial reality without spreadsheet archaeology. Example: run a weekly check on runway, recurring costs, and upcoming risk points before you scale spend.

HelloFrank

HelloFrank is positioned around deeper business-context finance insights. It can help detect spend anomalies and surface what changed month-over-month. Example: find subscription creep and cost spikes, then turn it into a prioritized cleanup plan.

Revaly

Revaly is positioned around payment performance and reducing failed transactions that create involuntary churn. It matters most where recurring revenue is sensitive to declines. Example: identify where legitimate payments fail and improve recovery rates without harming customer trust.

Precision

Precision is positioned around turning KPIs into a practical operating rhythm. It helps teams focus attention on what moved and what to do next. Example: generate a weekly performance brief. These metrics shifted, here are likely drivers, here is what we should test or fix this week.

How to build a working stack without buying 20 subscriptions

  • Start with one workflow you ship weekly. Brief → assets → approvals → publish → measure.
  • Assign ownership per step. Tools without owners become clutter.
  • Build the handoffs before you add more tools. Automation is what turns tools into a line.
  • Define where humans must decide. Brand-sensitive, compliance-sensitive, and customer-sensitive steps need a review point.
  • Run a monthly keep-or-kill review. If a tool is not improving cycle time or quality, remove it.

A few fast answers before you act

What is the single biggest mistake teams make with AI tools right now?

They treat AI as a chat window to copy and paste from, instead of an execution layer connected to a workflow that ships outputs.

What is a “working AI tech stack” in one sentence?

A working AI tech stack is a small set of connected tools that reliably turns inputs like notes and briefs into shippable outputs, with minimal friction and clear handoffs.

How do I decide if a tool belongs in my stack?

If you cannot name the exact step it owns and the handoff it triggers, it is not part of the stack yet.

What should a marketing leader implement first?

One throughput line, end to end. Inputs → Synthesis → Creation → Automation → Distribution → Measurement. Then automate handoffs before adding new tools.

How do I avoid tool sprawl?

Set constraints: one tool per job, a clear owner, and a monthly keep-or-kill review tied to measured outcomes.

T-Mobile ‘Tell Me Why’: The Live-Retail Play

A boy-band button in Times Square. And a very deliberate question

T-Mobile’s Super Bowl LX spot opens inside its Times Square Signature Store, surrounded by real customers, with a plain prompt on-screen: “Why is it better over here?” Then someone hits a big red button, the Backstreet Boys appear, and the “answer” arrives as a reimagined performance of I Want It That Way, with cameos from Druski, mgk (Machine Gun Kelly: Colson Baker) and Pierson Fodé. The commercial is credited to Panay Films and was slated to run as a :60 in the second quarter of the February 8, 2026 Big Game broadcast.

What matters is not the celebrity stack. It is the structural move: a telecom brand turning a comparison claim into a moment people can watch happening to other people.

How “Tell me why” turns a service claim into a stageable event

The core mechanic is simple on purpose. A single question frames the ad like a customer challenge, not a brand monologue. A physical trigger, the button, converts messaging into cause and effect. A live performance inside a real retail space supplies social proof because the audience is already there and reacting in-frame.

You can call this retail-as-stage. By retail-as-stage, I mean a physical store that functions as content set, event venue, and credibility engine at the same time.

When you turn a service comparison into a witnessed moment in a real store, with real reactions, belief shifts from “do I trust this claim?” to “I just saw why it’s true.”

The real question is how you make an invisible network promise feel provable in the moment, not just plausible in a chart.

The fastest path to belief is to turn an invisible network promise into a shared, watchable moment.

In telecom marketing, most value is felt after purchase, so “proof” has to be engineered before the contract is signed.

Why the nostalgia remix works, and why it is not just “a pop-culture hook”

Yes, it is familiar. But the stronger psychological play is fluency. A chorus people can finish in their head reduces processing effort, then that freed-up attention gets spent on the new lyric payload. The button adds perceived transparency. When a brand invites “why,” then stages an immediate “answer,” it signals it can withstand scrutiny.

Extractable takeaway: If your offering is hard to evaluate because it is invisible, abstract, or overloaded with fine print, stop trying to explain it better. Engineer a moment where the audience can watch someone else receive the answer in real time, because observed reactions become the credibility layer your claims cannot earn on their own.

Rewritten lyrics are inherently risky because they can feel like a jingle wearing a costume. This spot reduces that risk by grounding the musical in a real place, with real customers, and a visible trigger that creates a story arc worth retelling.

What T-Mobile is really trying to shift in 60 seconds

Look past the network line and you see a category-level repositioning attempt.

  • From coverage to a value stack. The ad frames the carrier choice as network plus bundled value plus experience, not just bars and price.
  • From switching pain to switching ease. The broader message is “make it easy to reconsider,” while the spot’s job is to create emotional permission to do so.
  • From brand assertion to customer interrogation. Opening with “why” signals the brand is answering scrutiny, which is a more credible posture in a high-skepticism category.

The Europe echo: making a network promise watchable

It should feel familiar. This “make connection visible” move has shown up before, by turning a network promise into a shared public moment you can actually witness.

Back in 2011, Deutsche Telekom executed a multi-city Christmas activation where Mariah Carey appeared as a hologram simultaneously across five European countries, with audiences linked across cities to experience the same performance at once.

The shared mechanic across both campaigns is consistent.

  • Make the promise tangible by creating a collective moment that can only exist because connection exists.
  • Use a universally recognizable song layer to synchronize emotion across audiences.
  • Build a reveal structure so the audience has a story arc worth retelling.

For the full Germany case, see Deutsche Telekom’s hologram Christmas surprise.

Steal the retail-as-stage pattern for “invisible products”

  • Start with a question the customer would actually ask. Not a tagline. A test.
  • Build one physical trigger. Buttons, switches, taps, scans. One action that says “watch this.”
  • Make the audience part of the evidence. Real reactions often land harder than any graphic.
  • Use music as memory infrastructure, not decoration. A familiar melody can carry new meaning fast.
  • Design for retellability. If it is easy to summarize, it is easier to spread.

A few fast answers before you act

What is the big idea behind “Tell Me Why” in one line?

It turns a telecom comparison claim into a witnessed moment in a real retail setting, using a familiar chorus and real-customer reactions to make “why” feel observed rather than asserted.

What is the core mechanic that makes it work?

A single customer-style question plus a physical trigger, the button, that immediately produces the “answer” as a performance, with the crowd reaction acting as the credibility layer.

Why does the Backstreet Boys remix outperform a normal benefits list?

Because audiences already encode the melody automatically. The rewritten chorus becomes a fast memory container for new information, and the live-style staging reduces skepticism.

What is the strategic intent beyond awareness?

To shift evaluation from “coverage and price” toward “network plus value plus experience,” and to lower switching resistance by making reconsideration feel emotionally safe.

What is the transferable lesson from the Deutsche Telekom hologram example?

If your product promise is invisible, create a synchronized public moment that can only exist because your promise exists, then let the shared reaction do the persuasion work.