Catalog

Use case: Product teaser (template 1)

| Element | Value |
|---|---|
| Subject | A matte black ceramic pour-over coffee dripper with a thin polished copper rim, sitting on a clear glass carafe |
| Action | 1) A thin stream of dark coffee trickles from the dripper into the carafe while soft steam curls up from the rim; 2) the dripper and carafe turn a slow quarter turn; 3) the final second holds still on the dripper's front, copper rim catching the light |
| Scene | A walnut kitchen counter by a window, early morning just after sunrise, a faint haze of steam in the air, uncluttered background |
| Angle / Move | Vertical close-up at counter height, slightly above eye level / slow dolly in |
| Lens | 85mm-style telephoto feel, shallow depth of field, kitchen background in soft bokeh |
| Light / Palette / Mood | Soft low-angle morning sunlight from a window on the left with gentle fill and a warm rim on the copper / matte black, warm copper, honey-brown walnut, soft cream highlights / calm, quiet, unhurried |
| Style / Time | Premium commercial look, photorealistic / real-time pace, steady trickle throughout, still hold in the last second |
| Audio | Close, clear coffee trickling into glass, a faint soft drip, quiet low morning room tone, no music |
| Negative | text, logos, letters, labels, hands, people, clutter, reflections of people, plastic look |

Final prompt (paste into Veo / Gemini / Flow):

Premium commercial look, photorealistic, vertical close-up at counter height of a matte black ceramic pour-over coffee dripper with a thin polished copper rim, sitting on a clear glass carafe on a walnut kitchen counter by a window in the early morning just after sunrise. A thin stream of dark coffee trickles from the dripper into the carafe while soft steam curls up from the rim, and the dripper and carafe turn a slow quarter turn. Slow dolly in, 85mm-style telephoto feel, shallow depth of field with the kitchen background in soft bokeh. Soft low-angle morning sunlight from a window on the left with gentle fill and a warm rim light catching the copper, palette of matte black, warm copper, honey-brown walnut and soft cream highlights, calm and quiet mood. Real-time pace; the final second holds still on the dripper's front.
Audio: close, clear sound of coffee trickling into a glass carafe, a faint soft drip, quiet low morning room tone, no music.
Negative prompt: text, logos, letters, labels, hands, people, clutter, reflections of people, plastic look

Settings: 9:16, 8 seconds, audio on.

Beat sheet

| Beat | Purpose | What the viewer must get | Seconds |
|---|---|---|---|
| 1 | Hook | A reporter in the rain, recording a source who is trusting him with something | 4 |
| 2 | Problem / stakes | The recording is precious and private; the small device in his wet hand is what holds it | 4 |
| 3 | Reveal | Later that night, at home, he sets Fieldnote down and starts it working | 4 |
| 4 | Proof | The words appear on its own e-ink screen: transcribed on the device, no laptop, no cloud | 8 |
| 5 | Payoff + CTA | He has every word, privately; music enters; end line | 4 |

Storyboard table (shots 1–3 of 6)

| # | Sec (gen → use) | Framing | Camera move | Subject action | Dialogue / on-screen text | Audio / ambience | Continuity notes |
|---|---|---|---|---|---|---|---|
| 1 | 4 → 4 | Medium shot, eye level, over the source's shoulder (her back soft in frame-left foreground); he stands under the awning facing screen left | Slow handheld push-in | Holds Fieldnote out toward her at chest height; listens; gives one small nod | Source (on camera, from behind): "They said it would stay between us." | Location A bed; her voice close; rain on the awning | Location A. Faces screen left. Recorder in his right hand, red light on. Jacket zipped halfway, wet shoulders. |
| 2 | 4 → 4 | Extreme close-up on his right hand holding Fieldnote, the source's coat a soft blur beyond | Static | Rain beads on the graphite body; the red light glows steadily; his thumb shifts once on the edge | VO: "What they tell me stays with me." | Location A bed, close rain ticks on the device | Location A. Recorder points screen left. Screen pale grey and blank. Ends with recorder centred, for a match cut. |
| 3 | 4 → 4 | Medium close-up on the kitchen table under the pendant lamp | Static | His right hand enters from frame right and sets Fieldnote down, centred; his thumb presses the round button; hand withdraws | none | Location B bed; soft tap of the recorder on wood; one button click | Location and lighting change (B). Match cut from shot 2 on recorder position. Device dry now, red light off. |

[The full answer continues with shots 4–6 and a coverage alternate, the ten-line continuity block pasted word for word into all seven shot prompts, each prompt's first and last frame, and the stitch plan with voice-over script, caption placement and export settings.]

Settings: model `sora-2` · size `1280x720` · seconds `8` · characters: none

Before

A cool cinematic shot of a woman drinking coffee in a nice cafe, make it 10 seconds.

After

Style: Contemporary 35 mm film look, natural and understated, soft contrast, fine grain, warm-neutral grade.

A small neighbourhood cafe on a quiet weekday morning. A woman in her early 30s with shoulder-length dark hair tied loosely back, wearing an oatmeal knit sweater, sits alone at a round marble table by a large street-facing window. In front of her: a white ceramic cup of black coffee on a matching saucer and a folded paper napkin. Behind her, out of focus, a wooden counter with an espresso machine and a barista moving between shelves of cups. Thin steam rises from the cup and catches the window light.

Cinematography:
Camera: medium close-up, eye level, from across the table at a slight angle; slow dolly-in
Lens: 50 mm feel; shallow depth of field, sharp on her face and the cup, background soft
Lighting: soft morning daylight through the window from camera left as key; warm tungsten pendant glow from the counter as background fill
Palette anchors: cream, warm walnut brown, soft white, muted sage, coffee black
Mood: calm, quiet, unhurried

Actions:
- She wraps both hands around the cup and lifts it slowly (first two seconds).
- She blows lightly across the surface, then takes one small sip.
- She lowers the cup to the saucer and looks out the window with a faint, relaxed smile (final two seconds).

Background Sound:
Low hiss of the espresso machine, soft clink of cups at the counter, muffled murmur of a few voices; no score.

What changed and why

- Removed "make it 10 seconds". Duration is an API parameter, not prose, and 10 is not a supported value (4, 8, 12, 16, 20). Set `seconds: 8` in the call; the prompt now fits 8 seconds of action.
- "Cool cinematic shot" became a named style. A specific aesthetic instead of a vague adjective, set first so it frames everything else.
- "Drinking coffee" became three timed beats. Lift, blow and sip, lower and look out. Beats with timing cues are far more reliable than a single vague verb.

[five more changes in the full answer: subject anchors, concrete nouns, one camera move, named light sources, background sound]

Pack: `references/pack-product-shots.md`.

Three options

1. PS-09 Strawberry Milkshake Product and Infographic. A ready-made premium cold-drink hero shot: seamless pastel backdrop, realistic condensation droplets and "premium café advertisement" styling, which is exactly the look a chilled cold-brew can needs.
Prompt by @Strength04_X (𝐌), source: https://x.com/Strength04_X/status/2090665058980462697, via awesome-nano-banana-pro-prompts, CC-BY-4.0.

2. PS-02 Luxury Chocolate Ad Still Life. The only prompt in the pack that is a full ad layout with on-image copy, but you would have to delete its placeholder copy and invented logos and rebuild most of the props.
Prompt by @AiwithLucas_ (Lucas AI), source: https://x.com/AiwithLucas_/status/2089231817916420518, via awesome-nano-banana-pro-prompts, CC-BY-4.0.

3. PS-01 Premium Beverage Advertising Photography. Written for a beverage-brand hero ad and works from your attached references, but the prompt is only one line long, so lighting and composition would come from what you attach.
Prompt by @exywuu (Exywuu), source: https://x.com/exywuu/status/2092222318084788564, via awesome-nano-banana-pro-prompts, CC-BY-4.0.

Pick: PS-09

What to attach. Image 1: a clear, front-on photo of your real Northbound can, logo facing the camera.

Adapted prompt (4:5 Instagram ad)

Image 1: product photo of the Northbound cold-brew coffee can. Use this exact can.

A vertical 4:5 Instagram feed ad. A high-quality professional product photograph of a premium cold-brew coffee can, the 330 ml matte navy aluminium can from Image 1 with its white logo, standing upright and centered against a soft pastel pink seamless studio background. Preserve the can's exact shape, proportions, matte navy finish, white logo and label from Image 1; do not redesign it, recolour it or add any new graphics to it. The can sits on the same seamless surface with a few clear ice cubes and a small scatter of dark roasted coffee beans at its base. Realistic condensation droplets cover the can with soft reflections from the studio lights. Elegant soft lighting creates subtle natural shadows beneath the can. The can fills about 55% of the frame height in the lower two thirds of the image, logo facing the camera.

Text: the headline "Cold. Bold. Northbound." across the top third of the image, centered, in a bold clean white sans-serif with generous letter spacing, large enough to read on a phone. Render this headline exactly once, spelled exactly as written. Apart from the can's own logo from Image 1, no other text, no prices, no taglines, no extra logos, no watermark.

Ultra-sharp focus, DSLR macro beverage photography, premium café advertisement style, hyper realistic, clean commercial composition, 8K.

Tool settings: aspect ratio 4:5; in AI Studio or the API also set the output resolution to 2K so the headline stays sharp.

Prompt by @Strength04_X (𝐌), source: https://x.com/Strength04_X/status/2090665058980462697, via awesome-nano-banana-pro-prompts, CC-BY-4.0. Adapted: subject swapped from a strawberry milkshake in a glass to the Northbound can, Image 1 reference and preserve-the-product line added, 4:5 aspect ratio and headline added, the original's second (infographic) paragraph removed.

[The full answer ends with a one-fix-per-turn table for headline contrast, product drift, garbled text and framing.]

Short answer: ChatGPT can't recommend Ledgerly, because nothing it can retrieve says Ledgerly exists. Even after launch, a single landing page is not enough. A "best X for Y" shortlist comes from web-wide consensus (reviews, roundups, forums, press), not from your own site.

Visibility ladder (retrieved → cited → mentioned → recommended)
| Rung | Ledgerly today | What governs it |
|---|---|---|
| 1. Retrieved | No: not live, not in Bing's index (ChatGPT search draws from a Bing-based index) | Being indexed and crawlable |
| 2. Cited | No | Extractable, factual, fresh pages |
| 3. Mentioned | No | Entity recognition; the web talking about you |
| 4. Recommended | No | Aggregate third-party consensus, largely independent of your own content |

Source pool (one web search for the exact query, 2026-11-07; not a ChatGPT answer): only third-party roundups and affiliate lists (NerdWallet, business.org, Zapier, Fueler, Techjockey, Aspire). The same five apps recur: Wave, Zoho Books, FreshBooks, QuickBooks, Xero. I did not run ChatGPT, so I'm not reporting what ChatGPT says; run the query list yourself.

Extractability check on site/index.html: clear definition in the first paragraph, partial (the H1 is a slogan); self-contained answer blocks, fail; statistics with sources, fail; comparison table for "vs" queries, fail; FAQ, partial (good answers hidden in collapsed <details>, none answers "Is Ledgerly good for freelancers?"); schema markup, fail; author or founder, fail; freshness date, fail; query-shaped headings, fail.

Top fixes, by impact against effort
1. Launch, then get indexed in Bing and Google. robots.txt with a wildcard allow plus explicit allows for OAI-SearchBot, PerplexityBot, Claude-SearchBot and Bingbot; decide training crawlers (GPTBot, ClaudeBot) separately.
2. Seed third-party consensus: G2 and Capterra listings with the first 20–30 real reviews; pitch the roundups that already rank for the query with a specific angle ("$12/month, no per-transaction fees, automatic invoice chasing"). Test: if a model ignored your own domain, would the web still put you on the list? Today, no.
3. Rewrite the hero into an extractable definition (below).
4. Add /vs/freshbooks, then QuickBooks and Wave, in the "fair source" pattern. Do not publish a self-ranked "best bookkeeping apps" listicle: in the skill's data 69% of such citations recommended competitors.
5. Publish /pricing.md and /llms.txt; fix the Studio button ("Talk to us" on a plan with a public price reads as a sales wall to an agent).
6. JSON-LD: Organization, SoftwareApplication with Offer per plan, FAQPage.
7. Buyer-intent FAQs rendered open in the HTML. 8. Named founder, "Last updated", one dated sourced number. 9. Measure monthly: 8 queries, 3–5 runs per engine, log rung and framing.

Hero answer block (57 words, every fact from the existing page):
> Ledgerly is a bookkeeping app for freelancers and two-person studios. It connects to your bank through Plaid or TrueLayer (US, UK, EU), auto-categorises each transaction by category and client, chases unpaid invoices on day 3, 7 and 14, and exports tax-ready P&L, VAT and quarterly estimates. Free plan available; Pro is $12/month with no per-transaction fees. […]

Style anchor locked: cream #F6F1E7 background, royal blue #1E40AF primary, coral #F26B5B accent, soft diffused window light from the left, rule of thirds, calm, subtle 35mm grain, matte. --sref https://…/anchor.png --sw 200.

Result library after one session (8 prompts queued, same anchor):
- hero-01 (16:9): founder at standing desk, headline space right — usable
- hero-02 (16:9): two colleagues, window behind — light blown out, rerun with "window to the left"
- social-01…04 (4:5): four learners in four rooms, same cream and blue — all usable as a set
- og-bg-01 (1.91:1): abstract blue and coral blocks on cream — usable
- character-01 (1:1): the recurring founder character, front-facing — becomes the --cref portrait

Fix pass: hero-01 has a six-fingered hand on the mug. Vary Region on the hand only with "hand holding a ceramic mug, five fingers, natural grip". Upscale Subtle. Ship.

HERO HEADLINE VARIANTS — current: "Smart plant care, powered by AI"

1. Pain framing — "Your fiddle leaf is not dying. It is asking for one thing." (lever: pain)
2. After-state — "Know what your plant needs before the next leaf drops." (lever: outcome)
3. Specificity — "Diagnose yellow leaves in 2 minutes from one photo." (lever: specificity)
4. Contrast — "Every blog says something different. Your plant says one thing." (lever: pain)
5. Number — "4 days. That is how long you have after the first leaf drops." (lever: specificity)
6. Confession — "We built this after killing nine plants in one apartment." (lever: proof)
7. Command — "Stop watering on a schedule. Start reading the leaves." (lever: after-state)
8. Reader quote — "I did not do anything wrong — I just was not told." (lever: voice)
9. Question-free curiosity — "The third thing nobody mentions about overwatering." (lever: specificity)
10. Promise — "Your next plant survives. This one might too." (lever: outcome)

Test first: #2 against #3 — same lever family, different specificity; the winner tells you whether the audience wants reassurance or precision.

Validation page — "Stop reinventing your client kickoff every Monday."

Promise bullets:
- 12 Figma templates that map to the briefs clients actually send
- A Notion brief generator: 4 questions in, a fillable scope out
- A 9-question client questionnaire that ends the "can you just tweak this?" loop

Objection handler: "Not a course. Not a community. Just the four files you wish someone had given you in year one."
CTA: "Pre-order for $49 — ships in 14 days. Refund if you don't use it."

Red team (as an investor who watched ten of these fail): the failure mode you are underestimating is not demand, it is the second purchase. Templates sell once; the Notion generator is the only piece with a reason to come back. Measure: of the first 50 buyers, how many open the generator twice in 30 days. If under 20%, the next product is a generator, not more templates.

Milestone 1 — validation page live · acceptance: 25 pre-orders in 7 days from $100 of ads and 20 DMs.

BRAND BRIEF — Northwood Beard Oil

1. Positioning
We help men 28–45 with full beards stop smelling like drugstore musk. We can do this because a third-generation perfumer blends 14 natural notes other beard brands will not pay for.

2. Audience snapshot
- Situation: has worn the same $9 oil for years; wife or colleague has commented on the smell
- Trigger: a wedding, a new job, or the bottle running out
- Tried: "premium" brands that still lean on synthetic musk
- Fears: smelling like a teenager's locker; paying $40 for marketing

3. Promise
A scent people ask about, not one they step away from — within the first week.

4. Voice rules
Do: short declaratives ("Three notes. Zero musk.") / Don't: "elevate your grooming ritual"
...
6. Instruction for future prompts
Use this brief. Never use "elevate", "curated", "ritual". Always name a specific scent note.

Skeptic re-read: "Third-generation perfumer" is doing all the work — if it is not provable on the site, the positioning collapses to "nice smell". Holds only with proof.

PILLAR — "The async standup playbook: how 14 distributed teams dropped the 9 AM call"
Keyword: async standup (~1,900/mo) · Intent: informational, late-stage
Gap in current top results: none give a template by team size; all assume 5–8 people.
H2s: Why the sync standup breaks past 3 time zones / The 3 formats by team size / Slack + Notion templates / What to do when nobody posts / Daily vs weekly / Tools compared honestly

Supporting articles
1. "Async standup template (Slack and Notion versions)" — async standup template (~720) · transactional · links to H2 #3
2. "Why your async standup is being ignored — and the 3-line fix" — async standup not working (~210) · informational · H2 #4
3. "Daily or weekly async standup for a 6-person team?" — daily vs weekly standup (~140) · comparison · H2 #5
4. "Async standup across 5+ time zones: what actually works" — async standup timezone (~95) · informational · H2 #1
...
Publishing order: 1, 2, 4 first (quick wins, low competition), pillar in week 3, remaining support weeks 4–6.

Scene 2 of 4 in a continuous short film. Use the attached character reference image.

Character (repeat verbatim in every scene prompt): a woman in her thirties, shoulder-length brown hair, navy blazer over a white shirt, warm intelligent expression — same face, same hair, same outfit, same build as the reference. No changes to wardrobe or hairstyle between scenes.
This scene: she pushes open the glass door of an empty office and walks in, slowing as she takes in the space, in a sunlit open-plan office at sunrise.
Camera: wide shot that begins a slow push-in as she enters.
Lighting: low golden sunrise through floor-to-ceiling windows — keep the colour temperature consistent with scene 1.
Ends on: her hand resting flat on a desk, centre frame — hold this frame for the final second so scene 3 can match-cut from it.
Audio: footsteps on hard floor and quiet office ambience; no music; no dialogue.
Avoid: additional people, mirrors, reflective surfaces, text, logos, any object she did not carry in scene 1.

Continuity check against scene 1: same blazer, same hair length, same warm temperature. Scene 3 will open on a hand on a different surface.

Top 5 unmet needs (67 interviews)

1. Onboarding takes too long — 41 customers
   "I gave up before my first usable result." (I-12) · "Two evenings to set up something I wanted to try in ten minutes." (I-38)
   Trigger: trying the product between meetings, on a phone.
2. Sharing with the team is friction — 33
   "I ended up screenshotting the dashboard into Slack." (I-05)
3. Integration with the existing stack — 29
4. Pricing surprise in month two — 24
5. Progress does not sync between devices — 18

Early signals
- Offline mode — I-12, I-38, I-51: "I'd pay for it to just work on the train." Unprompted in three separate interviews; not noise.
- Public API — I-22 only.

Contradictions
- 14 customers want fewer notifications; 9 want a daily nudge. Both groups are under 30 days in.

Say vs. want
- Say: "more features." Want, from behaviour: the three they already use to be faster. (I-07, I-44)

Follow-ups for next round
1. "What did you expect to have working within ten minutes?"
2. "Who else looks at this, and how do they see it today?"

Ranked causes

1. Creative launch pushed spend into a worse-converting audience (fit: HIGH)
Mechanism: three new creatives entered learning Monday; Meta over-delivers early impressions to cheap, low-intent placements.
Supports: spike begins the same day; recovery by Sunday matches a 5–7 day learning window.
Contradicts: nothing in the inputs — but you have not split CAC by creative yet.

2. Competitor promo raised auction prices Tue–Thu (fit: MEDIUM)
Supports: Tuesday start; CPM data would show it.
Contradicts: the spike started Monday, a day before the promo.

3. +30% budget scale on the top campaign reset learning (fit: MEDIUM-LOW)
Supports: scaling same day. Contradicts: a 30% step rarely resets learning on its own.

Next data cut: CAC and CPM by creative, by day, Mon–Sun. If the three new creatives carry a CAC over $90 on Mon–Wed while legacy creatives stay near $48, cause 1 is confirmed.

Not considered: a tracking gap — check whether the pixel fired normally Mon–Wed before trusting any of this.
Do not: pause the new creatives today. You would destroy the data that tells you which of them is fine.

Subject: Launch moves to the 28th — plan attached

Jamie — I am moving the launch from the 14th to the 28th.

Two reasons. The security review surfaced one issue we want to fix properly rather than patch, and the marketing site needs one more full week of build. The rest of the timeline holds; the partner webinar on the 30th is unaffected.

Already handled: the fix is scoped and owned by Priya; the new site copy is in legal review. I need two things from you — approval of the new date, and a release of the email send that is booked for the 14th.

I will post a five-minute pulse in #launch every morning until the 28th.

— Alex

Questions you will get back:
- "Why didn't we catch the security issue earlier?" → It was found by the external review we scheduled for exactly this reason; that is the process working.
- "What else could slip?" → Nothing on the critical path; the only open risk is legal turnaround on copy, which has a Friday deadline.