PROPOSED EDITORIAL DIRECTION · 5 NOVEMBER 2026
One useful change.
One clear next step.
V4 should bring customers back to change the words on an ad. Black Friday makes that useful now. It is the example, rather than a second campaign competing for attention.
Subject: “Same video. Fix the words.”
Headline: “Same video. New words.”
Primary action: Open your videos.
Feedback: one reply invitation at the bottom.
What V3 already gets right
Adeh’s latest version leads with visual proof, uses numbered steps, quotes the real app labels and 50-credit price, includes the company address, and removes the separate PERLA and assistant launches. The blaqpopgod frames are documented as a real customer edit, not placeholders.
What still needs to change
| V3 | V4 recommendation |
|---|---|
| “Better video. New words.” | “Same video. New words.” directly describes what this feature preserves. “Better” suggests the footage itself improved. |
| Fix explained in the hero and again in the letter; “working flat out” returns. | One brief, personal opening. Explain typed text once. Remove the activity report and blanket “every word is right” promise. |
| A shop-name-to-URL edit. | Show a useful offer, a visible type hierarchy, colour and a next step. The current animation uses the user-approved PERLA footage, with clearly labelled illustrative copy. |
| A 1,000-ad research paragraph and a second “Make your Black Friday ad” button. | One short Black Friday tip tied to the example. One app button. Keep the study and new-ad story for later issues. |
| Product-link workshop plus problem-report request. | One recurring “Your turn” section, including an invitation to share what happened with a Black Friday variation. |
| Every account is the stated audience. | Review the actual newsletter audience and suppressions. |
Black Friday: reconcile the two directions
The early feedback says to bring Black Friday up front; the later detailed markup says to keep the product win first. V4 does both: the subject and headline explain the feature, and the first visual demonstrates a Black Friday offer. The date is 27 November, avoiding a “three weeks” line that ages during review.
Media: honest proof, stronger communication
The 4-second GIF and MP4 show the same source time range with two text treatments. They use InstantClips’ shared text compiler, including its fonts, size controls and accent colour. The example discount is not a PERLA promotion, the frames are not an app recording, and no customer result is claimed. The first GIF frame also carries the complete message for clients that do not animate.
For the strongest final send, use an approved brand’s real offer edit and capture the actual editor-to-export flow. This review version is suitable for agreeing the concept; accepting an illustrative example or replacing it with that product capture is an explicit editorial decision. Do not caption a script screen as the text editor.
First issue and community
Keep one sentence setting expectations: useful shortcuts, new features and community examples. Do not promise a frequency before an owner can sustain it. “Clippers” is a naming idea to discuss separately, not needed to launch this issue.
The latest markup prefers replies; earlier feedback asks for a short form. For this issue, retain the one reply invitation and a monitored Mysen reply-to. Move to a form when an owner and review process are ready. A proposed future form is below; it is not a live collection link.
- What are you sharing? A problem / an idea / a Black Friday story.
- What did you try, and what happened? Include a link if useful.
For stories: optional permission to contact the sender about featuring it. Ask separately before publishing their name, creative or results.
Proposed ownership and release sequence
| Step | Proposed owner / acceptance |
|---|---|
| Message and final subject | Mysen accountable; Napoleon editorial review. Freeze the one outcome and feedback approach. |
| Product truth and example | Adeh verifies the live button labels, 50-credit cost and the final media. Nominate the person who captures the real workflow. |
| Sending setup | Name one campaign operator. Nimble remains the working assumption from this brief; a Campaign Monitor note in the discussion does not establish a platform switch. |
| Readback and approval | Operator checks audience, suppressions, sender/reply-to, hosted images, tracking and native footer; renders on mobile, Gmail and Outlook. Show exact recipients, subject and complete message for approval before any send, including tests. |
| After sending | One owner reads replies, triages problems and seeks permission for community examples. Report clicks separately from product use and sales. |
What success means
Primary product outcome: recipients return and successfully create an edited video version. Measure unique returning editors and successful paid text exports over an agreed window, using data already available. Email clicks are a leading signal; a new export is stronger evidence. Sales impact requires the customer’s campaign results and cannot be inferred from the newsletter alone.
Handoff and remaining checks
- HTML is prepared for Nimble with HTTPS media. It has one primary app CTA, plus a secondary link to the same-feature video example.
- Insert the actual sending platform’s unsubscribe and preferences controls. The visible bracketed footer labels are review placeholders, not working merge tags.
- The postal address comes from Adeh’s 5 November source update. Confirm sender and live product facts on the send date.
- Browser layout and media can be verified here; Nimble import and real inbox delivery remain separate checks.
- No email has been sent. No customer record, saved version or credits were changed. No GitLab commit or push was made.
Sources and version naming
This is team-review-v4, 5 November, following Adeh’s V2 and current V3. It replaces the review site’s older draft; the older local “on-screen-text-v4” is a different, archived iteration.
Adeh V2 · 4e7ad87
V3 snapshot reviewed · 7971642
Team discussion: supplied attachment in this chat.
Current public feature and purchase guidance