Just Sayin' Growth System

Periscal's Dating ID Post Generation + Testing Guide

Chiara is building the Dating ID Quiz video funnel to the book. Periscal's role is to build the content engine that feeds it: stronger hooks, stronger post structures, clearer calls to action, disciplined testing, and a weekly learning loop that improves what gets made next.

Core rule: We do not just track posts. We test parts of posts - hook, body, CTA, format, and funnel bridge - so we know what actually moved the audience.

1. What each part of a post is supposed to do

Post PartJobHow We Know It WorkedLikely Failure Signal
HookStop the scroll and earn the next few seconds.3-second hold rate, early retention, viewed-vs-swiped where available.Low early retention means the opening did not compel attention.
BodyKeep attention, create recognition, and pay off the hook.Average % watched, completion rate, saves, shares, self-identifying comments.People stayed briefly, then left because the message did not deepen or land.
CTAMove the viewer to the next action.Profile visits, link clicks, quiz starts.People liked the post but did not know or feel compelled to act.
Funnel BridgeConvert traffic into quiz progress and book interest.Quiz starts, completions, email capture, book clicks.Post promise and page experience are not matching well enough.

2. Why the banks exist

The banks are reusable libraries of approved message parts. They let Periscal move faster, keep the Just Sayin' voice consistent, test deliberately, and avoid starting from scratch every day.

Topic Bank Hook Bank Body Bank CTA Bank Caption Bank Format Bank Learning Bank

3. The testing discipline

Do not change everything at once. When testing hooks, hold the body and CTA steady. When testing CTAs, hold the hook and body steady. That is how we learn what caused the result.

Example

Same topic: Some people call anxiety chemistry.
Variable: Hook.
Hold steady: Body, CTA, format.
Judge by: 3-second hold and early retention.

4. Workflow: banks to final product

Open each step below. Periscal should use this sequence every time he turns a banked idea into a finished post, production brief, or testing decision.

1Choose the goal. Decide what this post is supposed to accomplish.

Purpose: Before choosing a hook or format, classify the post by its job. A post cannot be judged fairly unless we know what it was meant to do.

  • Awareness: Make new people stop, relate, share, save, or remember the Just Sayin' voice.
  • Quiz Traffic: Drive viewers to the Dating ID Quiz.
  • Quiz Result Education: Explain a Dating ID pattern so people recognize themselves and want to take or revisit the quiz.
  • Book Bridge: Move from the dating insight or quiz result into interest in Just Sayin'.

Periscal's output: Enter one clear goal in the tracker before building the post.

2Choose the topic. Pull one strong theme from the Topic Bank.

Purpose: The topic is the actual idea the post is about. It should be specific enough to create one focused message, not a broad category like “dating.”

  • Good topic: “You confuse anxiety with chemistry.”
  • Good topic: “You need to know who you become when you like somebody.”
  • Too broad: “Red flags.”

Periscal's output: Select one topic, assign it a Post ID, and keep the post focused on that single insight.

3Declare the variable being tested. Name what we are trying to learn.

Purpose: We do not learn much from a post if every part changes at once. Periscal must name the primary variable being tested before content is produced.

  • Hook Test: Change the opening line or first visual; keep body and CTA steady.
  • Body Test: Keep the hook and CTA steady; change the explanation, structure, scene, or message style.
  • CTA Test: Keep the hook and body steady; test which next-step language gets clicks or quiz starts.
  • Format Test: Keep the message substantially the same; compare reel, carousel, quote graphic, scene, or talking head.
  • Funnel Bridge Test: Examine whether the post promise lines up with quiz starts, quiz completions, and book clicks.

Periscal's output: Enter the variable in the tracker and state what remains constant.

4Build the message. Pull the post parts from the appropriate banks.

Purpose: This is where the banks become a complete post package. Periscal should assemble the message intentionally, not randomly.

  • Hook Bank: Choose the opening line or scroll-stopping statement.
  • Body Bank: Choose the teaching point, scene beat, Big Brother Talk frame, or explanation pattern.
  • CTA Bank: Choose the action language based on the goal: quiz click, book click, comment, save, or share.
  • Caption Bank: Choose or adapt the social caption that extends the message without repeating the video word-for-word.
  • Format Bank: Choose the best container: talking head, carousel, animation, quote graphic, text-on-screen reel, or book bridge asset.

Periscal's output: Produce a complete post packet: hook, body, CTA, caption, format, cover text, and test variable.

5Create Ralph's production brief. Turn the post packet into instructions a creator can execute.

Purpose: Ralph should never have to guess what the message is, what the opening text should say, or what CTA belongs at the end.

  • Post ID and campaign goal
  • Primary variable being tested
  • Approved hook and opening on-screen text
  • Body/script/scene direction
  • CTA and end-card wording
  • Caption and pinned-comment copy
  • Cover text and visual style notes
  • Platform needs and due date

Periscal's output: A clean production brief Ralph can build from without rewriting the strategy.

6Publish and track. Log the asset before judging it.

Purpose: The tracker must capture the creative choices before the numbers come in. That way the team can connect results to what was actually tested.

  • Enter the date, platform, Post ID, goal, topic, format, hook, body type, CTA, and variable tested.
  • Use the approved caption, cover text, and CTA consistently.
  • Record the post link once published.

Periscal's output: A live post with its strategic DNA properly logged in the tracker.

7Review the correct metrics. Diagnose the tested variable, not just overall popularity.

Purpose: Views alone do not tell us what worked. Periscal should read the metrics based on the part of the post being tested.

  • Hook: 3-second hold, early retention, viewed-vs-swiped where available.
  • Body: average watch percentage, completion rate, saves, shares, self-identifying comments.
  • CTA: profile visits, link clicks, quiz starts.
  • Funnel Bridge: quiz starts, quiz completions, email captures, book clicks.

Periscal's output: A specific diagnosis, such as “strong hook, weak CTA” or “good clicks, weak quiz completion suggests funnel friction.”

8Update the banks. Turn performance data into the next round of smarter content.

Purpose: The banks are living assets. They should get sharper as the team learns what audiences respond to.

  • Promote: Mark high-performing hooks, bodies, CTAs, and formats as winners.
  • Retest: Flag ideas that may deserve another shot with a stronger hook or CTA.
  • Retire: Note patterns that consistently underperform.
  • Remake: Send Ralph exact notes on which winner deserves a new version.
  • Funnel Feedback: Send Chiara any page, quiz, or book-bridge mismatch that appears in the data.

Periscal's output: Updated banks, weekly findings, and clear next-production recommendations.

5. 7-day, 14-day, 30-day execution plan

Days 1-7: Build + Hook Test
  • Finalize banks and tracker.
  • Select 5-7 core topics.
  • Generate first 10-14 post briefs.
  • Test multiple hooks with stable body and CTA.
  • Deliver first mini-review.
Days 8-14: Refine + CTA Test
  • Promote early hook winners.
  • Test 2-3 CTA variants on strongest topics.
  • Track clicks, quiz starts, and quiz completions.
  • Send remake notes to Ralph.
  • Flag funnel friction for Chiara.
Days 15-30: Scale + Learn
  • Scale top topic/hook/CTA combinations.
  • Test body and format variations.
  • Evaluate quiz-to-book bridge language.
  • Build a Learning Bank.
  • Recommend the next 30-day production plan.

6. Daily production packet fields

  • Post ID
  • Goal
  • Variable Tested
  • Topic
  • Hook
  • Body / script / scene beat
  • CTA
  • Caption and pinned comment
  • Visual direction and cover text
  • Links and references

7. How Periscal should report

Do not say: "This post did well."

Say: "This post had a strong hook, average body retention, and weak click-through. Reuse the opening, tighten the middle, and test a sharper CTA."

The tracker is built to support that level of analysis.

8. Coordination lanes

PersonPrimary LaneConnection Point
ChiaraQuiz funnel, follow-up flow, lead capture, quiz-to-book bridge.Receives conversion observations when clicks do or do not turn into quiz progress.
PeriscalPost generation, testing, analytics, performance learning.Sends Ralph briefs and Chiara funnel insights.
RalphVideo, carousel, quote card, and post asset production.Executes the brief and remakes assets based on what data suggests.
Dr. AndrewsVoice, strategy, and high-level positioning.Reviews weekly conclusions and greenlights major changes.

Final instruction to Periscal

Build the content like a marketer, test it like a scientist, write it like Just Sayin', and report it like every post is teaching us how to sell the next one better.

Open the Tracker
en_USEnglish
en_USEnglish
Scroll to Top