Zuporta Content Studio · exact-hook-v4

Start with the problem your buyer already feels.

Eight new drafts for Sheila, Egelyn, Angelo and Jed. Each keeps its selected source opening exactly, then uses an original body: 70% problem, 20% solution, 10% call to action.

Substack comes first. These are options for author review. Publishing this collection does not publish a social post. Anyone with this link can read the collection.

Sheila · LinkedIn · Post

Urgency in closing your leads is more important than you think 🚨

Imagine a customer asks your service business, “Can you help me this Friday?” The message arrives. Someone reads it. Everyone assumes someone else will answer. Your team is busy doing good work. The customer only sees silence. They still need Friday sorted. They keep looking. By the time your reply arrives, you may be competing with a business that already explained the next step. That is a painful way to lose a conversation: before your expertise, care, or price ever enters that buying decision. As a founder, I care about what our promises feel like from the other side. “We care about our customers” becomes hard to believe when the customer has to chase the first answer. A message marked read can still be a request nobody owns. Give each inquiry one owner, a realistic reply window, and a backup. Acknowledge the actual request. State the next step. Use automation for clearly agreed routing or reminders, with a human responsible for exceptions. Check that the handoff was accepted. Open your last five inquiries today. Find the first unanswered next step, then give that request a named owner now.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Alex Hormozi’s source post (2026-04-07). The body is original proposed language for Sheila.

140 words problem · 40 solution · 20 call to action. Total 200. The hook counts toward the problem.

1408 source reactions · 266 source comments. These are source-post counters, not results for this draft.

This is the source’s written post-caption opening, preserved for text. It is not represented as the spoken video opener.

Egelyn · LinkedIn · Post

A business that owns your calendar ultimately owns you.

As an administrator and a mother of four, I cannot plan every responsibility around being available for the next notification. Yet picture a service business where one person alone remembers every pending client message, appointment change, and promised follow-up. The inbox looks organized while that person is online. Then their connection drops. Someone else sees the message, but cannot tell what was promised or who should act. The customer sends another message. The original administrator returns to both the request and the work of reconstructing it. Being dependable has quietly become being permanently reachable. That is a fragile arrangement for the customer and the person carrying it. A color-coded calendar cannot reveal the decisions still trapped in someone's memory. The business has coverage only while one person supplies the missing context. Choose one recurring request. Record its owner, next action, due time, and backup where the team can access it. Automate suitable repetition only after those rules are clear. Test one handoff while the usual owner is unavailable, then review gaps. Choose one appointment change today. Could your backup complete the next step using the record alone? Fix whatever is missing.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Justin Welsh’s source post (2026-09-23). The body is original proposed language for Egelyn.

140 words problem · 40 solution · 20 call to action. Total 200. The hook counts toward the problem.

2248 source reactions · 984 source comments. These are source-post counters, not results for this draft.

Angelo · LinkedIn · Post

Everyone says the CEO needs to delegate more.

Picture a capable team member who owns appointment changes for the business on paper. They still ask the founder to approve an ordinary reschedule. Last time, their decision was reversed without a clear rule. Asking first now feels safer than using their judgment. Multiply that pattern across client updates, routine coordination, and small operating decisions. The founder gets a day full of approvals. The specialist gets responsibility without room to practice. The customer waits for a decision the team should already be equipped to make. I want to develop people who can outperform me in their fields. That purpose becomes harder when my preferences keep replacing their judgment. Technology can route the question faster. It cannot repair an agreement nobody trusts. More delegated tasks can still leave one person holding every decision. Choose one routine decision. Agree on the outcome, limits, resources, and exceptions. Let a suitably prepared person make it within those limits. Review the reasoning afterward. Change the rule clearly when needed, and provide coaching when a skill needs development. Ask one specialist which routine decision still needs your permission. Clarify that boundary together before adding another task to delegate.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Shirley Braun , Ph.D., PCC’s source post (2026-09-01). The body is original proposed language for Angelo.

140 words problem · 40 solution · 20 call to action. Total 200. The hook counts toward the problem.

121 source reactions · 152 source comments. These are source-post counters, not results for this draft.

Jed · LinkedIn · Post

ChatGPT will not miraculously grow your audience or business.

Picture an owner who asks AI for thirty posts about automation. The drafts arrive quickly. They are polished, consistent, and full of benefits. But the buyer worrying about tomorrow's unconfirmed appointments cannot see their situation in any of them. The posts explain what AI can do. They never show the moment a request gets lost, the uncertainty it creates, or the decision that would change it. More publishing then repeats the same missed connection. In marketing and business development, I want technology to improve commercial preparation. A much larger stack of finished drafts does not tell me whether the right person recognizes a useful reason to respond. Likes, replies, qualified conversations, and sales answer different questions. Treating them as one result can make busy marketing look healthier than the evidence supports. Start with one buyer problem supported by actual buyer questions or permitted research. Keep the selected source hook unchanged. Build the body around a concrete situation, one usable solution, and one next step. Track relevant responses separately from publishing volume. Read your next draft as the buyer. Underline their problem and the action they can take. Rewrite anything still missing.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Justin Welsh’s source post (2023-01-20). The body is original proposed language for Jed.

140 words problem · 40 solution · 20 call to action. Total 200. The hook counts toward the problem.

887 source reactions · 401 source comments. These are source-post counters, not results for this draft.

Sheila · Substack · Newsletter

Urgency in closing your leads is more important than you think 🚨

Picture this inquiry to an appointment-based service business: “Can you help me this Friday?” Three people inside the business are working. One person sees the message between tasks. Another assumes the first person answered. A third can confirm availability, but never receives the question. Outside the business, there is only a customer waiting. They do not know your team is busy. They do not know someone meant to reply. They cannot distinguish a thoughtful business with a weak handoff from a business that simply does not care. And Friday is getting closer. They might ask someone else. They might change their plans. They might return later, uncertain about trusting you with the appointment. None of those outcomes tells you whether your actual service would have been a good fit. The conversation stalled before you reached that decision together. As a founder, that matters to me. We can spend hours choosing the right words for a promise and still leave the first customer question without an owner. There is another cost inside the team. When the customer follows up, someone has to reconstruct what happened. Who saw it? Was availability checked? Did anyone reply somewhere else? The same request creates more work because the handoff was unclear. A fast acknowledgment can make this harder to notice. The system has responded, but the customer still does not know whether Friday is possible. The record says activity happened. The customer's problem remains open. This is an illustrative situation, but the question it raises is practical: what does a customer experience between making a request and receiving an answer they can use? Start with one inquiry route. Assign a person to the next action and agree on a reply window. Name a backup who can see the necessary context. An acknowledgment should reflect the request and explain what happens next. If availability needs checking, say who will check and when the customer can expect an update. Use suitable automation to support routing and reminders, then inspect the human handoff. A notification is useful only if someone accepts responsibility for the next step. Review five recent inquiries with your team. For each, find the request, the responsible person, and the next promised update. Choose the first unclear handoff and repair it today, before spending more effort bringing new people into the same gap.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Alex Hormozi’s source post (2026-04-07). The body is original proposed language for Sheila.

280 words problem · 80 solution · 40 call to action. Total 400. The hook counts toward the problem.

1408 source reactions · 266 source comments. These are source-post counters, not results for this draft.

This is the source’s written post-caption opening, preserved for text. It is not represented as the spoken video opener.

Egelyn · Substack · Newsletter

A business that owns your calendar ultimately owns you.

I am an administrator and a mother of four. My time matters, and my internet connection is not always reliable. That makes one business assumption worth questioning: the assumption that a dependable person can always be reached. Imagine an appointment-based business where one administrator knows every unfinished detail. A client asked to move a visit. A message needs a reply. Someone promised to confirm a time after speaking with another team member. The administrator remembers all of it. While they are online, the arrangement can look efficient. Questions get answered. People know whom to ask. The calendar appears current. But the business is relying on more than someone's effort. It is relying on that person being present whenever someone needs missing context. When their connection drops, a colleague may see the client message without knowing what was already promised. They wait to avoid giving the wrong answer. The client waits too. When the administrator returns, they inherit the original request, the extra messages, and the work of explaining everything again. That is the trap: being reliable starts to mean being the only person allowed to disconnect last. The owner may respond by adding reminders. But a reminder cannot tell a backup what they are allowed to decide. A shared calendar cannot explain an agreement nobody recorded. More notifications can simply make the same dependence louder. I value the repetitive work our team has helped automate. I still want each workflow to answer a human question: can someone suitable carry the next step without needing the original person to rebuild the whole story? That question matters to owners as much as administrators. Choose one recurring appointment change and document the minimum another person needs: the request, current status, next action, due time, and responsible person. Agree on a backup and the decisions they can make. Check that they have the access and context the task requires. Then test a handoff while the usual owner is unavailable. Use suitable automation for repeated steps after the rules are clear. Keep exceptions visible, and review what the backup could not complete without asking for help. Pick one appointment or client message from today. Ask a suitable teammate to explain its next step using the record alone. Add the missing context together. Start with that single handoff, then see whether it works when you step away.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Justin Welsh’s source post (2026-09-23). The body is original proposed language for Egelyn.

280 words problem · 80 solution · 40 call to action. Total 400. The hook counts toward the problem.

2248 source reactions · 984 source comments. These are source-post counters, not results for this draft.

Angelo · Substack · Newsletter

Everyone says the CEO needs to delegate more.

I want to develop people who become better than me in their own fields. That requires more than moving tasks away from my calendar. Consider a hypothetical service team. A specialist is responsible for routine client coordination. The owner says they trust the specialist to handle it. Then a decision comes back for approval. The owner sees hesitation. The specialist remembers the last decision that was reversed because it differed from the owner's preference. Both people can sincerely believe they are doing the responsible thing. The owner wants quality. The specialist wants to avoid another correction without a rule they can apply next time. The customer experiences the delay. This pattern can spread quietly. Small choices travel upward. The specialist prepares the options, but the founder still chooses. More work has been assigned, yet the opportunity to practice judgment has barely moved. Eventually the owner is tired of answering. The team is tired of guessing. Everyone agrees there should be more ownership, but the next unclear decision follows the same route. Automation can make that route faster. It can gather the context, send the alert, and place another approval in the queue. The underlying agreement is still weak. There is a development cost too. People cannot become strong decision-makers if they are allowed to execute instructions but rarely make bounded decisions and learn from the result. My people-development purpose asks something uncomfortable of me: when a capable specialist chooses a reasonable approach within our agreement, can I let their judgment stand even when I would have chosen differently? If every difference becomes a correction, the team has a reason to keep asking. Choose one routine decision suited to their preparation. Agree on the intended outcome, available resources, decision limits, and exceptions that require help. Ask the specialist to explain the agreement in their words. Then let them act within it. Review the decision afterward: what information did they use, what happened, and what support would improve the next attempt? If the boundary changes, say so clearly. Develop the skill with affordable practice instead of treating uncertainty as evidence that delegation cannot work. Invite one specialist to identify a routine decision they could own with clearer limits or support. Agree on one boundary and one review point. Give them a real opportunity to exercise judgment, then learn from what actually happens next together.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Shirley Braun , Ph.D., PCC’s source post (2026-09-01). The body is original proposed language for Angelo.

280 words problem · 80 solution · 40 call to action. Total 400. The hook counts toward the problem.

121 source reactions · 152 source comments. These are source-post counters, not results for this draft.

Jed · Substack · Newsletter

ChatGPT will not miraculously grow your audience or business.

Imagine a service-business owner with thirty finished drafts and no clear answer to a much simpler question: why would the right buyer stop to read one? AI has made the production step easier. The sentences are clean. The topics sound sensible. The posts mention productivity, automation, and growth. Meanwhile, the buyer is trying to confirm tomorrow's appointments. A client asked for a change. Two people think the other person replied. The owner is checking messages between meetings. “Unlock efficiency with AI” gives that buyer another phrase to ignore. The gap is specific. The content describes a category; the buyer is living through an unfinished situation. Publishing more can repeat that gap at greater speed. A month of consistent activity may teach you very little if every post avoids the moment your audience actually recognizes. I use technology and research in marketing and business development because preparation matters. But prepared material still needs judgment. An AI-generated lead is not automatically a suitable buyer. A reply is not automatically a qualified conversation. A popular post is not automatically evidence of demand for our work. Those distinctions affect what we improve. If people read but do not recognize their problem, another call to action may not help. If the topic attracts the wrong audience, a stronger hook can amplify the wrong conversation. Even a useful post can lose its purpose when the opening promises one thing and the body turns into a broad service pitch. The reader gave us attention for a reason. The rest of the post needs to give them something they can use before asking them to give us anything else. Start with one buyer situation supported by real questions or permitted research. Find a relevant source with visible post-level attention and preserve the selected opening exactly. Write the body around the buyer's problem, one practical change, and one action. Use AI to organize and refine that substance while checking facts and voice. After publication, separate reach from useful replies, inquiries, qualified conversations, and sales. Compare posts at consistent observation windows. Let actual buyer response inform which idea deserves another version. Take one draft you intended to publish. Write down the buyer's immediate problem beside it. Underline the passage that helps with that problem. If you cannot find it, repair the body before producing another version or adding another publishing channel.
Exact hook · source · 70/20/10 check

The first line is copied exactly from Justin Welsh’s source post (2023-01-20). The body is original proposed language for Jed.

280 words problem · 80 solution · 40 call to action. Total 400. The hook counts toward the problem.

887 source reactions · 401 source comments. These are source-post counters, not results for this draft.

The sources have measurable attention. Virality for these drafts is untested. Older sources are dated in the research. The earlier collection and its browser storage keys are preserved; schedules have not changed.