When I started showing LowFlow more, a new problem appeared. Building the product takes time. Getting it known takes time too. And the two can easily compete with each other.
A site to maintain. A blog to feed. Posts to prepare. Videos to film. Search engines to feed. Messages to answer. Users to support. All of that can turn into a second full-time job.
And when you build almost everything yourself, you have to be careful not to spend more time talking about the product than improving it.
So I started applying the same logic to visibility as to development: keep it simple. Reuse what already exists.
A blog episode can become a Facebook post. That same post can later serve on LinkedIn. A demo of the journal can become a short video. A new feature can become an article. An answer to a real user question can become useful content for the next ones.
The goal isn't to be everywhere. The goal is for each piece of work to serve several times.
Because LowFlow is first of all a product. Visibility should help it grow, not slow down its construction.
It's probably one of the most important lessons of this stage: building an audience has to become a system too. Not a new mountain of work.