A situation worth working through
A video creator receives ad revenue from a distribution platform and occasional direct support from viewers. One popular upload brings a spike in reach, but the following week looks normal again. Treating both revenue sources as interchangeable can lead to promises based on attention the creator cannot repeat. Each source needs its own expectations and recordkeeping.
The decision
Use advertising and voluntary support for different planning purposes instead of assuming either is guaranteed.
- Separate reach from commitment
- Keep the invitation near the work
- Plan around observed patterns
They answer different questions
Advertising connects a placement or audience exposure to an advertiser’s goals. Fan support asks whether someone wants to encourage the person making the work. A large audience does not automatically produce gifts, and a loyal small community does not automatically attract advertisers.
Plan for an ordinary month
Write down the commitments you can sustain without a viral week. Separate production costs, time, and uncertain income. When an experiment goes well, ask whether you can repeat it without exhausting yourself or your audience.
A support invitation should name the work and the role people can play. It does not need to turn every update into a sales pitch.
A useful check
Plan your baseline around an ordinary month, rather than your strongest viral week.
| Income source | What to review |
|---|---|
| Advertising | Reach, campaign fit, and sponsor requirements |
| Fan support | The audience relationship and the support invitation |
| Planning | Keep separate records so you can see what each contributes. |
Give Rory a specific role
Use your Rory page for updates and voluntary support while other channels do their jobs. Measure return visits and participation as well as attention. Treat the first month as a relationship test, rather than a forecast of dependable earnings.
Separate reach from commitment
An ad-supported view can come from someone encountering your work for the first time. A gift often reflects a more deliberate decision, although it still does not guarantee future support. Look at the context behind each source. A large audience for one viral topic may not be the audience interested in your next project or willing to keep following it.
Keep the invitation near the work
Let the article, video, or stream provide value before asking for support. Explain what you are currently making and provide a recognizable destination for people who want to respond. Avoid presenting gifts as a rescue from an algorithm unless you are prepared to explain that claim accurately. A specific project update gives viewers more useful context than a broad complaint about reach.
Plan around observed patterns
Keep a simple record of revenue sources and the releases associated with them. Do not treat a single unusually strong week as a stable baseline. When you plan recurring expenses, consider what happens if either source falls. This is a planning exercise, not a prediction of what a platform or an audience will pay next month.
Words you can adapt
The example below illustrates the approach; it is not a customer message or testimonial. Change the details to match the actual situation. Keep the meaning accurate rather than copying a promise that does not fit your work.
The video is free to watch. If you want to help with the next field recording, my Rory page has the project notes and an optional gift link. Watching and sharing the work already matters.
Moving every viewer toward a support ask can damage the experience that attracted them. Give the work room to stand on its own. Likewise, treating supporters as a replacement for discovery can leave a project isolated. Distribution and direct relationships can reinforce each other without every post carrying the same sales pitch.
Try the approach on a real example
Use one real draft, page, or project from your own work for this review. Keep a copy of the original so you can compare it with the revision. The exercise is deliberately small: it should help you make a concrete decision, not turn into a complete redesign or a new obligation to publish every day.
First, write down who is arriving and what they already know. A regular follower and a first-time visitor may interpret the same sentence differently. Give the draft to someone who has not helped create it, or read it after stepping away for a while. Ask what the page appears to offer before explaining what you intended. That difference is often where the useful editing work begins.
Next, identify the one action or understanding the draft is meant to support. Underline the sentence that communicates it. If several unrelated requests compete for attention, decide which one belongs here and move the others elsewhere. Keep any relevant limits close to the invitation. A person should not have to discover a different meaning after following the link or sending a message.
Read every promise literally. Words such as always, immediate, exclusive, free, and guaranteed can create expectations that are broader than you intended. Replace them with a precise description where needed. Check names, dates, destinations, permissions, and any claim about a product against the actual current situation. A warm tone helps, but it cannot repair an inaccurate promise or a link to the wrong page.
Then inspect the material on a phone and without the surrounding conversation. Read the heading, caption, and main action in order. If an image carries an important detail, make sure the text explains it too. If the draft depends on an earlier post, add a short introduction or a relevant link. Someone encountering it through a share should not need a private explanation to understand it.
| Review point | What to write down |
|---|---|
| Separate reach from commitment | The specific fact, decision, or uncertainty you need to resolve before moving on. |
| Keep the invitation near the work | The action you can take through an appropriate, verified route, and the information needed to take it. |
| Plan around observed patterns | The result you will check afterward, including what would make you revise your first interpretation. |
Keep the first version
Save the original wording or notes beside the revision. Comparing the two helps you see whether you clarified the situation or only made the language longer. Remove details that do not help someone understand or act.
What to check afterward
Separate reach, return visits, replies, and gifts when reviewing a release. An increase in views with no increase in returning readers suggests a different issue from a clearly understood support page that few people visit. Change the part of the journey where the evidence points.
Write down the outcome in plain language, including anything that remains uncertain. A useful review can end with a smaller change, a decision to wait, or a question that needs a better source. It does not have to end with a new post, a new tool, or a payment. Keep the lesson specific enough that you can use it the next time a similar situation occurs.
Before you finish
- The example matches the real situation rather than an imagined best case.
- Important claims, names, links, and permissions have been checked.
- Private details and unsupported promises have been removed.
- The next step is clear to someone who did not help write the page.
