A website tells people who you are. A Place is where they go to experience the work. The two get treated as the same thing, and that confusion is what produces flat traffic, weak conversion, and the recurring sense that the website “needs a refresh.”
A website is a brochure. It tells a visitor who you are, what you do, and how to reach you. The brochure is useful. The brochure is also not a destination. A website introduces. A Place is where the introducing leads. Most experts ask the website to do both jobs, which is why it keeps feeling like it needs a refresh. It is being asked to do work no website was built to do.
The Place is the environment where an expert’s body of work lives so people can return to it, trust it, and use it over time. A website rarely meets that description, and it was never supposed to.
What a website is for, and what a Place is for
A website does three things well. It introduces you, it points people toward what you offer, and it announces what is current. Someone arrives, reads the bio, sees the offer, gets the contact details, and leaves. The visit is short by design. Once the introduction is made, the website’s job is mostly finished.
A Place does a different job. People arrive, and instead of reading about the work, they enter it. They sample the thinking before being asked for anything. They come back three weeks later for the part that applies to the conversation they are about to have. They return six months later because the work is still useful. A Place should be useful six months later. A website rarely is, because a brochure is not built to be returned to.
This is why the same body of work can feel completely different depending on where it lives. Behind a standard website, a serious framework reads as a service description. Inside a Place, the same framework reads as a body of work someone built deliberately. Nothing about the thinking changed. The environment around it did.
This is the same architectural distinction that separates a Place from a course platform and from a community. A course delivers something a person bought. A community is a conversation space. A website introduces. Each of those is a real job. None of them is the destination the others are supposed to point to.
The refresh loop
Here is the pattern I have watched play out for years. An expert has a website. Traffic is fine, but it does not convert the way it should. The diagnosis is almost always the same: the website needs a refresh. So they rebuild it. New design, new copy, new photography. For a few months it feels better. Then the same flatness returns, and the conversation about another refresh starts again.
The refresh rarely fixes it because the refresh is aimed at the wrong problem. The website is not underperforming because it looks dated. It is underperforming because it is being asked to be a destination, and a brochure cannot be a destination no matter how well it is designed. Most experts have a landing problem, not a visibility problem. The same logic applies to the website. The design is usually fine. What is missing is a destination behind it.
When the work has nowhere durable to live, every channel points back to a page that introduces and then stops. The podcast appearance sends people to the website. The keynote sends people to the website. The newsletter sends people to the website. They read the bio, they see the offer, and unless they are ready to buy the exact thing on offer that day, they leave. The attention arrives and then leaves, because there is nothing built to receive it.
That is the refresh loop. The website is doing exactly what a website does well. It has simply been assigned a second job it was never built for.
What to do instead
The fix is not to throw out the website. A website that knows its job is useful. The fix is to stop asking it to be the destination.
An expert who has a Place has two clean options. The first is to keep the website as the front of house and let the Place be the destination it points to. The website introduces, then routes people to the Place where the actual work lives. The second is to let the Place replace the website entirely and serve as the front door itself. Both work.
What does not work is the middle position, where the website is asked to introduce and to be the destination at the same time. That is the version that always feels like it needs another refresh. Once the website has a real destination to point to, the pressure on it drops, and it can go back to doing the one thing it is good at.
A website tells people what an expert does. A Place is where they go to experience it. When a website keeps feeling like it needs a refresh, the missing piece is usually a destination for it to point to. Once that destination exists, the website can go back to being a good brochure.
Frequently asked questions
Should I get rid of my website if I have a Place?
Not necessarily. A website and a Place can coexist, with the website introducing people and the Place serving as the destination it sends them to.
What should my website do once my Place is where my body of work lives?
The standard brochure jobs: introduce you, point people toward what you offer, and announce what is current. The difference is that it now has a clear destination to route people to instead of trying to be that destination itself.
How do I know if my website is doing too much?
If it feels like it needs a refresh every year or two, and each refresh improves the look without fixing the underlying flatness, the website is probably being asked to be the Place. That recurring dissatisfaction is the signal.
Can a website be designed to be a Place?
Architecturally, yes. But what you would be building at that point is a Place that happens to serve as the front door. Calling it a website undersells what it is doing. If you want the fuller picture of what a Place actually is, that is covered separately.
Leave a Reply