The public journal as a business asset: build your audience before your product

Image: Rawpixel Ltd — Openverse (by)

In short — Building an audience as a solo starts with publicly documenting your process: the public journal is the most underused distribution asset in France. Starting to write before you have a finished product isn’t optional — it’s the strategy.

---

You spend six months building a product. You launch. Nobody replies. No bug, no bad pricing — just silence. That’s the most common scenario for solos who build in the dark. Not because their product is bad. Because nobody was waiting for them.

Distribution isn’t a problem you fix after launch. It’s an asset you build beforehand. And the public journal is the most concrete, durable, and underused tool to get there — especially in French-speaking markets.

Why most solos build in the dark — and pay for it at launch

The logic of stealth mode is seductive. You don’t want to show something unfinished. You’re afraid of being copied. You think the product will speak for itself once it’s ready.

Those three reasons are understandable. They’re also the three surest shortcuts to a failed launch.

The problem isn’t product quality. It’s the lack of warmup. A launch with no audience is a shop that opens with no sign, on a street with no foot traffic. You can have the best product in your niche — if nobody knows you, nobody shows up on day one. And day one matters: algorithms, Product Hunt, partner newsletters — everything favors launches that start strong.

The solopreneur economy has exploded in recent years. According to MBO Partners in their State of Independence report, the number of full-time independent workers in the United States exceeded 17 million in 2024, and the trend is the same in Europe. The cost of building a software product has collapsed with AI. But the cost of acquiring an audience hasn’t budged: you pay it in time, in consistency, in trust built week after week. For more on the underlying numbers, the article solopreneur & AI statistics 2026 is a solid starting point.

Building in the dark means choosing to pay that cost all at once, at the worst possible moment — launch day — instead of spreading it across six months of useful documentation.

The journal as proof of work: trust, authority, long-term SEO

A public journal isn’t just another blog. It’s proof of work.

Every article, every thread, every progress note says the same thing without saying it: I actually build, I actually learn, I’ve been here a long time. That’s exactly what a potential buyer looks for before pulling out a credit card for a stranger’s tool.

Trust isn’t declared. It accumulates. And it accumulates much faster when you document your process than when you wait until you have something to sell.

There are three concrete effects worth measuring:

1. The authority effect. Someone who reads ten of your articles on building a SaaS tool solo lands on your sales page with a level of trust no landing page can create on its own. They already know you. They’ve seen your reasoning, your corrected mistakes, your technical choices explained. They’re not buying a product from a stranger — they’re buying the tool of someone they’ve been following for months.

2. The long-term SEO effect. A well-written journal article on a specific problem — “how I cut my app’s build time from 8 minutes to 90 seconds” — captures organic traffic for years. Not generic traffic: traffic from people who have exactly that problem. It’s the best distribution funnel that exists for a solo with no ad budget.

3. The passive network effect. Articles circulate. A thread on X summarizing a long-form piece attracts people who would never have found you otherwise. An article shared in a partner newsletter brings you qualified subscribers without you asking for anything. Public documentation creates multiple entry points into your world — each article is a different door to the same place.

That’s why distribution isn’t the code anymore. AI commoditized building. What’s still scarce is the voice, the audience, the accumulated trust. A public journal is one of the few assets nobody can copy quickly.

What you document — and what you keep to yourself

The question that stalls most solos: how far should transparency go?

The short answer: document the process, not the sensitive data.

What’s worth making public:

• Design decisions and the reasons behind them (why this stack, why this pricing model, why this niche)
• Mistakes and what they taught you — this is by far the most shared content
• Aggregated usage metrics when they tell something useful (number of beta users, overall retention rate)
• Technical, marketing, and business lessons — anything that can help someone else in the same situation
• Real struggles: a bug that cost you three days, a dropped feature, a positioning that missed and got corrected

What you keep to yourself:

• Identifiable customer data (names, emails, individual behaviors)
• Pricing currently under negotiation with partners
• Conflicts or tensions with contractors, clients, or competitors — even anonymized, it comes back to bite you
• Pure introspection with no lesson for the reader — a business journal is not a personal diary

The dividing line is simple: does this content help someone solve a problem or make a better decision? If yes, publish. If it’s just for you, keep it in Notion.

A struggle documented honestly — with the context, the mistake, the fix — is worth ten times more than a success presented with no friction. It’s counterintuitive, but that’s what builds trust. People know building is hard. When you show it unfiltered, you become credible.

Format, frequency, platform: the choices that actually matter

You don’t need to do it all. You need to pick and stick with it.

Frequency first. One post a week is the minimum threshold to stay in your readers’ minds. Below that, you get forgotten between articles. Above three a week as a solo, quality drops and the pace becomes unsustainable — especially if you’re building a product at the same time. Once a week, held for six months, beats any content burst followed by three months of silence.

Format next. Two formats work well for a solo:

• The long-form article (800 to 1,500 words) on a specific topic, grounded in your lived experience of building. That’s the SEO format, the one that lasts. It takes two to three hours a week — less if you use AI for structure and proofreading, which is reasonable.
• The short note (200 to 400 words) or the thread: one decision, one observation, one number. Fast format, ideal for keeping cadence between long-form pieces.

The two complement each other. The long-form article builds authority and SEO. The short note maintains presence and generates immediate engagement.

Platform last. In French-speaking markets, three realistic choices:

• Your own site: absolute priority. It’s the only place where you own the audience. Every article published here is a permanent asset. Algorithms change, platforms shut down — your domain stays.
• LinkedIn: useful if your target is B2B or if you want to reach decision-makers. Organic reach there is still decent in 2025-2026, especially for long-form content on entrepreneurship.
• X (Twitter): useful for real-time build in public, technical threads, the indie community. More volatile reach, but a very active network in the maker ecosystem.

The rule: publish on your site first, redistribute elsewhere. Never the other way around. If you only publish on LinkedIn and tomorrow their algorithm changes or your account gets suspended, you lose everything. Your site is your land. Platforms are a rental.

That’s exactly what we do with this journal: every article lives on sek.re/blog/ first, then circulates. The asset stays here.

How to monetize the audience before you even have a finished product

This is the part most solos don’t see coming — because they think monetization starts at product launch.

It starts well before.

Step 1: the email list from the first article. A simple signup form, a clear promise (“I document the building of [product], you get the lessons every week”), and you start building a list of people who actively chose to follow you. Those people are your first potential buyers. Not anonymous visitors — people who raised their hand.

Step 2: pre-launch and validation by intent. Before the product is finished, you can offer early-adopter access at a reduced price. Not a vague promise — a sales page with a price, a clear scope, and a button. If nobody buys at this stage, that’s valuable information that costs you zero. If people buy, you’ve validated demand AND funded part of the development.

Step 3: services as a bridge. An audience that trusts you can pay you for your expertise before your product exists. An audit, a get-unstuck session, a consultation — that’s what /unstuck/ or /audit/ offer here. These services aren’t an end in themselves: they’re a bridge between “I’m building” and “my product generates recurring revenue”. They let you stay afloat without raising funds or chasing cold clients.

Step 4: the community as product. In some niches, the audience itself becomes the product. A private space, a peer group, access to your notes and resources — all of that can be monetized before a single line of code is in production. It’s not a fit for every topic, but if you document something people want to learn, it’s a real option.

The overall logic is simple: an audience built before the product turns the launch into an awaited event rather than a shout into the void. People who’ve been following you for six months don’t need to be convinced — they’re just waiting for you to open the door.

---

Building your audience as a solo isn’t a side activity next to building the product. It’s an integral part of the strategy. The public journal is the most honest, durable, and accessible tool to get there — no ad budget, no marketing team, no bullshit.

The solo constraint — little time, few resources — is actually an advantage here. You don’t need to produce volume. You need to produce consistency and sincerity. One honest note a week on what you’re building beats any industrial content strategy.

The real risk isn’t publishing too early. It’s never starting — and arriving at launch with nobody there to listen.

---

If you’re building solo and looking for a developer to unblock a technical bottleneck or take stock of your distribution, Sébastien de Bollivier is available.

Got an idea to ship? A website, a SaaS, an AI automation — built with you.

Talk about your project