Designing the First Week Inside Your Hub
A new member joins, sees six open spaces, and closes the tab. The first seven days decide whether they come back, and a narrow path beats a full tour every time.
Someone joins on a Tuesday night. They pay, the confirmation lands, and they click through while the kettle boils. The screen shows six spaces: community, courses, live sessions, content, resources, and members. Everything is open. Everything is theirs. They look at it for about forty seconds, decide to come back when they have more time, and close the tab.
They are not lost. But the week that follows decides more than any sales page did. A hub is a destination, and destinations are judged by what happens after people arrive.
Access is not orientation
The instinct after a sale is to hand over everything at once. You built six spaces, so you show six spaces. It feels generous, and it is the fastest way to make a new member freeze.
Choice costs energy. A person who just paid has a small amount of attention left and one quiet question behind it: did I do the right thing? Six equally weighted doors do not answer that question. One clear next step does.
So the first week is not a tour of your hub. It is a short, deliberately narrow path through it.
Day one: one action, finished
Pick a single action a new member can complete in under fifteen minutes, alone, without waiting for anyone. It should leave something behind that they can see.
The shape depends on what you teach. A first lesson with a worksheet they fill in. A template they copy and adapt to their own numbers. A short exercise that ends with a written answer. What matters is that it closes. An unfinished tour leaves nothing; a finished small thing leaves proof.
Say it in one sentence on the screen they land on after joining. Not a menu. A sentence: start here, it takes fifteen minutes.
Name the action after the result, not after the format. "Set up your first week of posts" tells a member what they will walk away with. "Module 1, Lesson 1" tells them where they are in your filing system, which is your problem to solve, not theirs.
Days two to four: proof that the path continues
The second visit is the fragile one. Day one still had the momentum of the purchase behind it. Day three has nothing but your invitation.
So send it. A short message on day two that points at exactly one thing, and a second on day four that points at the next. Two lines each. No newsletter, no digest, no list of everything they could be doing instead.
The point is not really the content of those messages. It is the pattern: something small, something specific, something that continues. Members learn the rhythm of a space in the first few days, and they learn it from what you actually do, not from what your welcome page promised.
Days five to seven: the first time they meet people
Learning alone is fine for a week. It rarely holds for a month.
Before the first week ends, a new member should have one low cost interaction with another human being in your community. Low cost means it does not require them to be interesting. "Introduce yourself" asks a nervous person to perform in front of strangers. "Answer this one question in a sentence" does not.
Give them a question they already know the answer to: what are you working on right now, what brought you here, what is the one thing you want handled by the end of the month. Then reply to every single answer for as long as you possibly can. Early replies from you are the strongest signal a young space can send.
What to keep closed
Some of what you built should not be visible in week one.
Your full resource library helps a member in month three and buries them on day two. Deep archives, advanced paths, and the corner of the community where experienced members talk shop are all worth having, and none of them belong on the first screen. Keep them one click away rather than in the way.
The same goes for live sessions. A calendar with nine upcoming events reads as pressure to someone who has not finished their first lesson. One session, named, with a date, reads as an invitation.
How to tell whether it worked
You do not need much to read a first week. Three signals carry most of it.
Did they come back at least twice after joining? Did they finish the one action you pointed at? Did they say anything to anyone?
Two out of three is a working first week. Zero out of three, repeated across several members, is not a motivation problem on their side. It is a design problem on yours, and it usually sits in the first screen they saw.
Watch the pattern across members rather than any single person. One quiet member is someone having a busy week. Six quiet members in a row is a path that does not lead anywhere obvious.
Write it before you automate it
There is a strong temptation to build the welcome sequence first, with branches and conditions and tags. Leave that for later.
Write the week out as plain text on one page: the first action, the day two message, the day four message, the question you will ask in the community, and the one thing you will keep closed. Then send those messages by hand to your next ten members. You will rewrite half of it after the first three, which is the whole point. Rewriting a page costs nothing. Rewriting an automation costs an afternoon.
Once the words stop changing, automate them.
Start here
Open the screen a new member sees the moment they join, and read it as if you had paid ten minutes ago. Count how many things it asks you to choose between. If the answer is more than one, you have found this week's work: cut it down to a single sentence, one action, and a time estimate you can honor.