How to ask for your first 10 supporters
A seven-day plan for choosing a specific ask, sharing it with people who know your work, and following up.

Ten supporters is a useful number to aim for because you can keep track of what you tried and still have real conversations. It is a planning goal. You might get there quickly, take months or decide the ask needs to change first. The point of this first week is to publish a clear page, put it in front of people who have a reason to care and learn where it is working.
Use the seven days as a sequence rather than a deadline. If you publish work once a month, fit the sharing steps around the day people already hear from you. If you are waiting for a page to go live, use the time to tighten the explanation and prepare the first message.
Day 1. Write down what someone would help you do
Start with something real: a piece of work you can show, a deadline you have confirmed or a task you have already started. Write one sentence that names the work and one that explains what support would change. If you cannot fill in the second sentence, do the research you still need before asking for money. An honest “I’m working out the next step” can be a useful update on its own.
Choose whether this is a request for one specific thing or an ongoing invitation. Both can work, but people should be able to tell which they are reading. If you set a target, keep a private note of how you arrived at it. If the need changes, you will have something to refer back to when you explain why. Leave the target off if a fixed total would imply a promise you are not making.
Day 2. Let someone see the page before you explain it
Publish when the page and receiving details are ready. Copy the public link and open it in a private browser window on your phone. Check who is named on the first screen, what you say support will help with and where a visitor would go to contribute. If an optional video opens, see how the page looks when it is closed as well.
Ask someone to open the page without telling them what to expect. Ask them to describe the request back to you. Pay attention to what they leave out and where they stop reading. If they identify the owner but miss the purpose, move your most useful sentence closer to the top. If they recognise the project but cannot see how to help, look at the layout and link. Fix the thing you saw, then ask someone else to check the revised version if you can.
Day 3. Choose who will hear about it first
Think of people who already read, listen, attend or ask questions about your work. Choose a few you have a genuine reason to contact. You can note how each person knows the work, but there is no need to collect extra information about them. If the only thing you know is that their number is in your phone, share through a public update they can choose to read instead.
Write each direct note around the actual relationship. Refer to something the recipient really said or did only if it makes the link relevant. If you cannot remember the details, say you are sharing an update on your work rather than guessing. Let them open it when they want. Avoid sending the same request over several channels or asking people to explain why they did not respond.
Days 4 and 5. Share the same ask in two useful places
Pick one place where people already look for the work and one where there is room for a reply. Put a short sentence about the work with the link. If a channel needs a different format, change how you present it while keeping the purpose the same. Someone who sees both versions should reach the same page and understand that it is the same request.
Open each post after you publish it. Check the link from the version people will see, including a group post or a link in your profile. If the link requires several taps, say which one to take first and use the same label people will see on the screen. If a group has rules about money requests or links, get permission or use a different channel.
Keep a small record with the date, the place and the wording you used. Record a question in your own words if someone raises one. That gives you enough information to make an edit without keeping a list of every person who saw the request.
Day 6. Follow up when you have a reason
Send an update when there is news you can share: a step you finished, a correction to the original post or the answer to a question several readers asked. If there is no news, leave the link where you put it. A reminder without context can make a personal request feel like a demand. People who were interested can still come back to it.
Thank people who helped in ways you can verify. If someone shared your page, say thanks for sharing. If a contribution is confirmed and you have an appropriate way to respond, thank them for giving. Keep names and payment details private unless the person has agreed to have them shared. An update for the whole audience can thank everyone together and keep the focus on the work.
Day 7. Review what happened without guessing why
Look at what you can count: how many places you posted, what questions people asked and which contributions are confirmed. Treat those as different things. A visit is not a contribution and silence is not a reason to assume people saw or understood the ask. If a reader says they could not find the link, that is a specific problem you can fix. If someone asks what support changes, work on the page description.
Choose one change for the next week. Fix a link that was hard to find, replace a vague opening line, or share with a group that is closer to the work. If the first ask brought in no support, decide whether the project can continue as planned and whether you should leave the page open. Be frank about where it stands. If you reach ten, thank the people who helped and tell them what happens next.
Decide when to stop asking
Set a point to review whether the same request is still useful. That might be after your next publication or once a decision about the work is due. Look at what you can report, whether the need remains and whether your next message would add anything new. If you stop sharing the request, review the public page too. A person with an older link should know what happened and whether the request is still open.
The work is not over when you post the first link. A page is most useful when you can keep its purpose accurate and answer reasonable questions about it. A short first week gives you a record you can use to do that, whether you meet your planning goal or discover that your community wants a different way to help.