# Zuporta content selections · October 27, 2026 · 22:00 · hook-v3

Research-first correction: 16 LinkedIn + 16 Substack options. Proposed language for author review; no social publication is performed. Original collection remains available separately.

## Substack

### Sheila

#### Option 01 · Your fastest reply can still leave a customer waiting · Note

<!-- COPY START -->
A quick acknowledgment can leave a customer doing all the waiting.

They know their message arrived. They still do not know whether someone is handling it, what information is missing, or when to check back.

Here is a small test for a service-business owner: read your first reply without using anything you already know about your business.

Can you name the person or team handling the request? Find the next action? Tell when an update is realistic?

If an answer is missing, improve that sentence before adding another automated message. A clear reply is a promise someone can keep. That is the standard I want Zuporta to help businesses work toward.
<!-- COPY END -->

Hook basis: Contrast an easy visible output with the customer outcome it may fail to deliver.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · The founder should not be the forwarding button · Note

<!-- COPY START -->
A team can grow while the founder remains its forwarding button.

More people receive the work. Every decision still comes back to one desk.

Before adding another handoff, map one ordinary request. An appointment change is enough. Who sees it first? What can that person confirm? What information do they need? Which exception should come back to the owner?

Then ask the person doing the work to explain the route back to you. A document that only makes sense to its author will not carry the handoff.

At Zuporta, I want people support and operating clarity discussed together. Extra capacity becomes more useful when someone can use it without asking the founder to translate every step.
<!-- COPY END -->

Hook basis: Replace the usual request for more help with a concrete routing bottleneck.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · A beautiful website can hide an unfinished handoff · Note

<!-- COPY START -->
A polished page can pass the design review and still leave a customer wondering what happened.

Try a task instead of a tour. Use your phone to find out how a customer would ask a question, change an appointment, or follow up on an existing request.

Look at the words around the button. “Prepare a message,” “send a request,” and “confirm an appointment” describe different outcomes. The page should use the one it can actually deliver.

Then check the next screen. Is there evidence the action completed? Is help available when it does not?

This is how I want us to approach a website conversation at Zuporta: begin with the customer’s job, then decide what design and connected support that job needs.
<!-- COPY END -->

Hook basis: Contrast a polished artifact with the ordinary job the customer needs to complete.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · The customer is standing between two systems · Newsletter

<!-- COPY START -->
The customer is standing between two systems
Follow one inquiry before buying another tool.

The customer is standing between two systems.

On one side, a website says the request was sent. On the other, a team has a queue, a calendar, an inbox, and other work to finish. Somewhere between them, somebody has to own what happens next.

For a service-business owner, this is a useful place to inspect before buying more software.

Choose one recent inquiry that you are allowed to review. Trace its route. Record where it arrived, who picked it up, what information was missing, and what the customer was told. Keep the record small enough that the person doing the work can correct it.

Now look for a gap in ownership. Did two people think the other one had replied? Could the team find the original request? Was a request for a new time mistaken for a confirmed appointment?

Those questions point to different fixes. A clearer message might solve one problem. A named owner might solve another. A connected workflow may be useful when information is repeatedly re-entered. An exception may need a person’s judgment.

At Zuporta, I want Diagnostic → Action Plan → Execution to stay grounded in this kind of specific work. The plan should say what will change, who will be responsible, and how we will check it.

Start with one inquiry. Make the next handoff clear before expanding the system.
<!-- COPY END -->

Hook basis: Make an invisible handoff visible as a person caught between two tools.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Egelyn

#### Option 01 · My inbox should not be my second memory · Note

<!-- COPY START -->
An inbox is a difficult place to keep a promise.

A message arrives. Another one pushes it down. The next step exists only because someone remembers it.

As an administrator and a single mother of four, I want less of that work living in my head. Our team has helped automate repetitive work, but a useful process also needs a clear place for the requests that still require attention.

For me, three details matter: who owns the request, what should happen next, and when it needs review.

An owner can use that same check without buying anything first. Ask the person handling client messages to show how they know what is still open. Where they rely on memory is a useful place to improve together.
<!-- COPY END -->

Hook basis: Make a familiar tool into an unexpected burden, then connect personal reality to buyer relevance.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · A dropped connection should not erase the next step · Note

<!-- COPY START -->
“Did that actually send?” is a work question worth designing for.

With an unreliable connection, I need to be able to tell the difference between a draft, an attempted action, and a confirmed result.

I am not describing an offline feature. I am describing what I want to know when I get back online: what is done, what is waiting, and what I should check before trying again.

An owner can make this part of an ordinary workflow review. Ask the person doing the admin work to explain how they confirm that an appointment request, message, or update completed.

Clear recovery steps belong in the plan. So does knowing whom to ask when the status is uncertain.
<!-- COPY END -->

Hook basis: Start with a specific constraint and turn it into a concrete system requirement.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · A client DM needs somewhere to go · Note

<!-- COPY START -->
A client DM needs a route after somebody reads it.

As an administrator, I want to know what I can handle, what needs review, and who can take over when I am unavailable. Those decisions help me more than being told to keep checking.

Start with one message type. An appointment-change request is a useful example. Agree on what information is needed, who can confirm availability, and when the request must go to someone else.

Then decide how the next person will see the original context. A handoff that loses the question creates more work for everyone.

This is the kind of practical support I value from our team: making the route clearer around the repetitive work technology can help with.
<!-- COPY END -->

Hook basis: Show that asking someone to monitor harder does not establish ownership.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · What I want to see when I come back online · Newsletter

<!-- COPY START -->
What I want to see when I come back online
Four questions for admin work interrupted by real life.

I do not want to spend my first few minutes back online working out what happened while I was away.

I want to see what is finished, what is still waiting, and what another person has taken over.

As an administrator and a single mother of four, I value the repetitive work our team has helped automate. I also want the remaining work to be clear enough to return to without holding every detail in my head.

Here is the small checklist I would bring to a workflow review.

First, can I recognize the request? A client name or task label should lead to the original context, within the access I am allowed to have.

Second, can I tell its status? A draft should look different from a sent message. A requested appointment should look different from a confirmed one. If an action was interrupted, the uncertainty should be visible.

Third, who owns the next step? If another person is handling it, I need to avoid doing the same work again. If it is mine, I need to know what is expected.

Finally, where do I ask for help? Some situations will not fit the ordinary route.

These are requirements to check, not features I assume every tool has. A business owner can use them to review one recurring task with the administrator who actually does it.

Make returning to work clearer before making the workflow bigger.
<!-- COPY END -->

Hook basis: Promise a specific, relatable end state and provide a usable checklist.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Angelo

#### Option 01 · The team should not need a smaller version of me · Note

<!-- COPY START -->
If every specialist has to work exactly like me, I have made my own ability the ceiling.

The work I love is developing people who can outperform me in their specific fields. That is a purpose I am working toward, not a result I can simply declare.

One useful distinction is between the outcome we need and the method I happen to prefer. A specialist may find a stronger route if the expectations and boundaries are clear.

For an owner, try reviewing one delegated task. Which requirements protect the result? Which instructions merely preserve your habit?

Keep the first group explicit. Be willing to discuss the second. Development needs responsibility and a chance to exercise judgment.
<!-- COPY END -->

Hook basis: Use an unexpected identity contrast to make specialist development concrete.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · A task can leave your desk and keep your attention · Note

<!-- COPY START -->
A task has not fully left my attention if every small choice returns to me.

As a people leader, I want routine work handled by suitable people or technology within clear responsibilities. That gives me more room for the high-value decisions and people development I care about.

Here is a useful check for a business owner. Choose one delegated task and list the decisions inside it. Mark the ordinary choices the assigned person can make. Identify the exceptions that change a commitment or need different authority.

Then ask whether the person has the information to use that boundary.

Delegation becomes more useful when the next decision has a clear home, not just the task itself.
<!-- COPY END -->

Hook basis: Challenge the appearance of delegation with the observable flow of decisions.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · Some work deserves to disappear before it gets an owner · Note

<!-- COPY START -->
The fastest version of an unnecessary task is still work someone has to maintain.

Before deciding whether a person or technology should take it over, I want to understand its purpose.

For a recurring report, ask who reads it and what decision it supports. For a reminder, ask why the original handoff did not make the next action clear. For repeated data entry, ask which record people should trust.

Some tasks protect real commitments and should stay. Others may be simplified once the people affected agree.

This fits the way I want to use my attention: focus on what matters, make routine responsibility clearer, and leave room to develop people rather than simply redistribute every existing task.
<!-- COPY END -->

Hook basis: Use subtraction before optimization as the hook and provide a bounded review.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · My top 4% question starts with one list · Newsletter

<!-- COPY START -->
My top 4% question starts with one list
A personal filter for choosing work, not a promise about results.

A full calendar does not tell me whether I have chosen the right work.

I use a “top 4%” lens to challenge where my attention goes. I look for the highest-value fifth of the work, then the highest-value fifth within that group. The arithmetic is twenty percent times twenty percent.

This is a prioritization heuristic. It is not a measured claim about how my effort produces results.

Here is a practical way an owner could test the idea. Write down the work asking for your attention this week. For each item, ask what decision or outcome changes if you do it well. Separate genuine urgency from a task that simply arrived loudly.

Next, identify what needs your judgment because of a commitment, an important uncertainty, or a responsibility you hold. Identify the routine work a suitable person or technology could handle under agreed rules.

Do not treat the second group as work you can ignore. It still needs a clear owner, the right information, and a way to review exceptions. Some responsibilities also need training before the handoff is sensible.

The work I especially want to protect is developing people who can become stronger than me in their own fields. That requires time to listen, challenge, and support them.

The useful result of the exercise is a better decision about one task—not a percentage to put on a success graphic.
<!-- COPY END -->

Hook basis: Turn a distinctive personal heuristic into a concrete decision rather than a performance claim.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Jed

#### Option 01 · A longer lead list can be a larger research problem · Note

<!-- COPY START -->
A list of businesses is not yet a reason to contact them.

AI helps me prepare research, but I want the output to make the next decision clearer. For each potential fit, I want an observed fact, a reason it could matter, and the question we still need to answer.

An example: a public website offers appointments. That tells me something about the customer path. It does not tell me the business is losing bookings or wants our help.

Keeping that distinction visible improves the research conversation.

For an owner reviewing AI-supported lead generation, ask to see the reason behind a few records. A shorter list with clearer reasoning may be a better starting point for your team.
<!-- COPY END -->

Hook basis: Contrast easy output volume with the commercial decision it fails to answer.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · The most useful line in research may be a question · Note

<!-- COPY START -->
A confident paragraph can hide a missing fact.

That is why I want AI-supported research to tell me what we still need to ask.

For a service business, an online inquiry form is observable. The business’s response time, staffing situation, and willingness to change are different questions. I cannot infer those from the form alone.

I use three distinctions when thinking about the next step: what the source shows, what I think it might mean, and what remains unknown.

Then I check whether the recommendation needs information from the third group.

This keeps research useful without pretending a public observation is a complete diagnosis. It is also a clearer starting point for a relevant conversation.
<!-- COPY END -->

Hook basis: Challenge the polished output with an uncertainty that changes the next action.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · Sixty-four drafts still need one reason to be read · Note

<!-- COPY START -->
Content volume is easy to see. A useful buyer takeaway takes more thought.

When I use AI to prepare content, I want a clear answer to one question: what can a business decision-maker understand or do better after reading this?

That answer helps me choose the opening, the example, and the next step. A post about an appointment handoff should give the reader a way to inspect one. A post about research should explain what evidence is missing.

The Substack version can explore the idea. The LinkedIn version should work as a focused professional post in its own right.

One useful idea, adapted carefully, gives me a better starting point than repeating the same body everywhere.
<!-- COPY END -->

Hook basis: Use a concrete volume number to expose the missing buyer payoff.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · Before you scale lead generation, inspect five records · Newsletter

<!-- COPY START -->
Before you scale lead generation, inspect five records
A small quality check before multiplying the output.

Five records can tell you what your lead-generation process is leaving out.

Before expanding an AI-supported list, inspect a small set closely. The point is to find the quality problem while it is still easy to correct.

Start with the source. Can you open it and find the fact the research claims to have observed? Is the information current enough for the decision? If the page only shows an inquiry form, keep the observation at that level.

Next, examine the reason for fit. Does it connect a real business need you can discuss with the service you actually offer? Or does it jump from an industry label to an unsupported conclusion about workload, missed revenue, or intent to buy?

Then mark the unknowns. Some information belongs in a conversation with the business. A good research record should make those questions easier to ask rather than silently answer them.

Finally, decide what happens next. More verification may be appropriate. So may excluding the record. If outreach is authorized, the message should be relevant and grounded in what is known.

This is how I want technology and data to support my business-development work at Zuporta. They help with preparation, while fit, replies, opportunities, and sales remain distinct.

A generated lead is the start of an investigation. Review the process before multiplying its output.
<!-- COPY END -->

Hook basis: Promise a small, specific test that exposes a larger quality problem.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world). These sources inform the hook structure; their engagement is not a result achieved by this draft.

## LinkedIn

### Sheila

#### Option 01 · Your fastest reply can still leave a customer waiting · Post

<!-- COPY START -->
“Thanks for reaching out” can be the fastest reply a customer receives—and the last useful thing they hear.

An acknowledgment tells someone a message arrived. It still leaves three questions:
Who owns my request?
What happens next?
When should I expect an update?

As Zuporta’s founder, I want those questions to shape the support we help businesses design.

Try this: open your standard first reply. If a new customer cannot find a next step in it, add one you can actually honor.
<!-- COPY END -->

Hook basis: Contrast an easy visible output with the customer outcome it may fail to deliver.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · The founder should not be the forwarding button · Post

<!-- COPY START -->
Your next hire may still need you to forward every message.

That is a warning to review the route before adding more people.

Choose one recurring request. Write down who receives it, who can handle the ordinary case, and what needs your decision. Give that person the information to act.

An appointment change inside agreed availability is different from a request to change a contract.

The founder’s job is to make that boundary clear enough to use. Where does a simple request get stuck waiting for you?
<!-- COPY END -->

Hook basis: Replace the usual request for more help with a concrete routing bottleneck.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · A beautiful website can hide an unfinished handoff · Post

<!-- COPY START -->
Your website can look finished while the customer’s next step is still missing.

Open it on your phone. Pretend you need to move an appointment.

Can you find the right route? Does it explain whether you are sending a request or confirming a change? Can you ask a person for help?

Those details affect whether the page is useful after the first impression.

Before a redesign, follow one real task from the customer’s side. Write down the first point where you have to guess. That is a useful place to begin.
<!-- COPY END -->

Hook basis: Contrast a polished artifact with the ordinary job the customer needs to complete.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · The customer is standing between two systems · Post

<!-- COPY START -->
Your customer should not have to connect your website to your team.

Yet that is what happens when the form says “sent” and nobody knows who follows up.

Review one inquiry with four questions:
Where did it arrive?
Who owns the next action?
What did the customer get told?
What happens if the usual person is unavailable?

A new tool can help once that route is clear. Until then, you may be giving the customer another place to wait.

This is the operating conversation I want a Zuporta diagnostic to start.
<!-- COPY END -->

Hook basis: Make an invisible handoff visible as a person caught between two tools.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Egelyn

#### Option 01 · My inbox should not be my second memory · Post

<!-- COPY START -->
My inbox should not be my second memory.

As an administrator and a single mother of four, I do not want every client message to depend on me remembering to reopen it later.

The team’s help with repetitive work matters to me. So does being clear about what still needs a person.

For each open request, I want to see the owner, the next action, and when it needs attention.

If you run a service business, ask your administrator which reminders they are carrying in their head. Start there.
<!-- COPY END -->

Hook basis: Make a familiar tool into an unexpected burden, then connect personal reality to buyer relevance.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · A dropped connection should not erase the next step · Post

<!-- COPY START -->
My internet connection is unreliable. That changes the questions I ask about work.

When I reconnect, can I tell what was completed, what is still waiting, and what needs another attempt?

That is different from assuming every tool works offline. I want a clear way to recover when the connection interrupts me.

For a service-business owner, this is worth discussing with your administrator before choosing software.

Ask them to show you how they check whether an interrupted action actually finished.
<!-- COPY END -->

Hook basis: Start with a specific constraint and turn it into a concrete system requirement.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · A client DM needs somewhere to go · Post

<!-- COPY START -->
“Keep an eye on the DMs” leaves a lot for one person to remember.

Who takes over when I am unavailable? What can I answer? Which requests need another person’s decision?

I want clients to get a clear next step without relying on me checking every moment.

Try mapping one kind of DM: a new inquiry, an appointment change, or a follow-up. Agree on the owner and the point where help is needed.

That is a more useful instruction to an administrator than “please don’t miss anything.”
<!-- COPY END -->

Hook basis: Show that asking someone to monitor harder does not establish ownership.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · What I want to see when I come back online · Post

<!-- COPY START -->
When I come back online, I want a clear work list—not a guessing game.

Show me what finished, what needs attention, and what somebody else is handling.

As an administrator with limited time and an unreliable connection, that is the question I bring to a workflow review.

Choose one interrupted task in your business. Can the person returning to it find its status and next owner without rereading an entire conversation?

That is a useful requirement to write down before adding automation.
<!-- COPY END -->

Hook basis: Promise a specific, relatable end state and provide a usable checklist.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Angelo

#### Option 01 · The team should not need a smaller version of me · Post

<!-- COPY START -->
I do not want a team of smaller versions of me.

I want people who become better than me in their own fields.

That changes what I should hand over: a clear outcome, the information to judge it, and room to choose a better method. It also changes how I review the work. Am I checking the result, or pulling everything back toward my preferences?

As a people leader, that is a question I want to keep asking.

Who on your team needs more room to develop their own judgment?
<!-- COPY END -->

Hook basis: Use an unexpected identity contrast to make specialist development concrete.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · A task can leave your desk and keep your attention · Post

<!-- COPY START -->
You can delegate a task and still attend every decision inside it.

Then your calendar fills with checks instead of execution.

For routine work, I want suitable people and technology to handle what is already within agreed rules. My attention should go where judgment changes the outcome.

Review one recurring task. Which decisions can the owner make? Which exceptions need me? Is that boundary visible to both of us?

If the answer is unclear, the handoff is not finished.
<!-- COPY END -->

Hook basis: Challenge the appearance of delegation with the observable flow of decisions.

Measured examples: [Shirley Braun](https://www.linkedin.com/posts/shirleybraun_everyone-says-the-ceo-needs-to-delegate-more-activity-7500545706986876928-HIxW). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · Some work deserves to disappear before it gets an owner · Post

<!-- COPY START -->
Some work deserves to disappear before it gets delegated.

A duplicate update, an unused report, or a reminder caused by an unclear instruction may need a different decision from “Who can do this for me?”

I want suitable technology and people handling valuable routine work. I also want to question whether every task belongs in the system.

Choose one recurring task. Who uses the result? What decision changes because of it? What commitment would be affected if it stopped?

The answers tell you what to keep, simplify, or review.
<!-- COPY END -->

Hook basis: Use subtraction before optimization as the hook and provide a bounded review.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · My top 4% question starts with one list · Post

<!-- COPY START -->
My “top 4%” lens starts with a question: which work deserves my attention twice?

I look for a high-value fifth, then the highest-value fifth within it. Twenty percent of twenty percent is four percent.

It is a way to challenge my priorities. It does not prove that four percent of my hours creates a fixed share of results.

The practical question is simpler: what needs my judgment, and what could suitable people or technology handle within clear rules?

Start with this week’s task list.
<!-- COPY END -->

Hook basis: Turn a distinctive personal heuristic into a concrete decision rather than a performance claim.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your). These sources inform the hook structure; their engagement is not a result achieved by this draft.

### Jed

#### Option 01 · A longer lead list can be a larger research problem · Post

<!-- COPY START -->
AI can make the lead list longer before it makes the next conversation better.

In business development, I want to know why each business belongs on the list.

What did I actually observe? Why might it relate to Zuporta’s scope? What would I still need to ask?

That separates a research lead from a verified opportunity. It also gives a human something useful to review before outreach.

Try it with five records. If the only reason for inclusion is “matches our industry,” the research needs another pass.
<!-- COPY END -->

Hook basis: Contrast easy output volume with the commercial decision it fails to answer.

Measured examples: [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 02 · The most useful line in research may be a question · Post

<!-- COPY START -->
The most useful line in an AI research summary may be “we still need to ask.”

A public page can show a booking route. It cannot reveal the team’s workload or the number of customers who abandon it.

I want research to preserve that boundary.

Use three labels before taking the next step: observed, interpreted, and unknown. Check whether the recommended action depends on the unknown part.

That is how I want AI and data to support business development: help me make a better decision, with the missing evidence still visible.
<!-- COPY END -->

Hook basis: Challenge the polished output with an uncertainty that changes the next action.

Measured examples: [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world), [Hamel Husain and Shreya Shankar](https://www.lennysnewsletter.com/p/advanced-evals-how-to-find-and-fix). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 03 · Sixty-four drafts still need one reason to be read · Post

<!-- COPY START -->
Sixty-four drafts still need one reason for the right buyer to read them.

AI helps me create options. My job is to choose the problem, check the evidence, and make the opening earn the reader’s next few seconds.

For a service-business owner, that might be a missed handoff, an unclear appointment status, or admin work that keeps returning.

Before adding another post, finish this sentence: “After reading this, the buyer can ___.”

If the answer is only “know we exist,” I want to strengthen the idea.
<!-- COPY END -->

Hook basis: Use a concrete volume number to expose the missing buyer payoff.

Measured examples: [Tom Orbach](https://www.lennysnewsletter.com/p/60-creative-growth-ideas), [Kristen Lowe](https://www.lennysnewsletter.com/p/how-to-make-people-care-about-your), [Sabrina Ramonov](https://www.sabrina.dev/p/ai-content-multiplication-3-million-followers). These sources inform the hook structure; their engagement is not a result achieved by this draft.

#### Option 04 · Before you scale lead generation, inspect five records · Post

<!-- COPY START -->
Before you scale an AI-generated lead list, inspect five records.

Can you open the source? Identify the relevant fact? Explain why the business might fit? Name what still needs checking?

Then look for an invented conclusion: “They must be losing customers,” “They need automation,” or “They will buy.”

Those statements require evidence the list may not contain.

AI supports my preparation. A fit judgment still needs review, and a real buyer’s response is evidence of something different from a generated record.
<!-- COPY END -->

Hook basis: Promise a small, specific test that exposes a larger quality problem.

Measured examples: [Sabrina Ramonov](https://www.sabrina.dev/p/5-stages-of-ai-mastery), [Anshu Chimala](https://www.lennysnewsletter.com/p/how-to-turn-your-ai-into-a-world). These sources inform the hook structure; their engagement is not a result achieved by this draft.

