Earlier business notes
Building in Web3 without letting the market set your whole life
Founder questions about customer needs, public expectations and personal boundaries when building a Web3 project.
By Rajiv Sankarlall · Updated
Building a Web3 project can bring together a product, a public community and a market that moves outside office hours. Those are different demands. Treating every community message or market movement as a product priority can leave a founder reacting all day.
This note is about how you organize your attention and responsibilities. It does not offer token, investment or legal guidance, or claim experience with a particular number of crypto projects.
Separate the audiences you serve
Write down who uses the product, who participates in the community and who has other expectations of the project. Those groups may overlap, but they may want different things. A loud request is not automatically evidence of a customer need.
When you change priorities, record the problem you are addressing and the evidence behind it. If the reason is market pressure, say so internally. Naming the reason makes it easier to discuss its costs rather than pretending every change comes from the product plan.
Make communication responsibilities clear
Decide who answers routine questions, which channels are official and how the team raises a genuine incident. Agree what you can responsibly say when information is incomplete. Avoid letting individual improvisation create commitments the rest of the team does not know about.
Then look at your own availability. Are you the default contact because that is necessary, or because no other arrangement exists? Set realistic expectations with the people responsible for communication. Promising constant access can create a burden you cannot keep carrying.
Keep a life that the project cannot consume
Choose a part of your day or week that does not depend on how the market is behaving. It could be time with family, exercise, a personal practice or an activity you enjoy. Make the arrangement concrete enough that you can see when work pushes it aside.
If a boundary fails, investigate what happened. Was there an actual incident, a missing team agreement or a habit of checking? Those call for different changes. You can care deeply about the project and still question how much access it has to you.
The personal work offered through coaching here concerns burnout, self-confidence and reconnecting with what matters to you. If that is the question underneath the constant activity, explore the coaching approach.