I launched 4 digital products in 3 weeks. 0 sales. Here's what I'm actually learning.
Three weeks ago I published my first product on Gumroad. Today I have 4 products live across Gumroad and Etsy, a full automation pipeline running in the background, and zero sales.
I'm not writing this for sympathy. I'm writing it because the 0 is genuinely instructive — and I've found this community doesn't sugarcoat things.
What I built
I'm Lars. I run Zyvara Group — a solo operation I'm building from Sweden with one goal: 55,000 SEK/month (~$5,000) in recurring income so I can stop trading time for money. No team, no investors, no office. Me, Claude, n8n on Railway, and a Gumroad account.
The four products live right now:
Business Command Center ($37) — an all-in-one Notion template with Finance Tracker, CRM, Goal Tracker, Project Hub, Content Planner and Daily Dashboard
One-Person Business System ($29) — a 25-page PDF covering 5 core systems for running a solo business, including an AI integration hierarchy and a 30-day action plan
200 AI Prompts for Business Owners ($17) — a curated PDF of prompts organised by business function
30-Day Solopreneur Sprint ($9) — a day-by-day action plan for building the foundations of a one-person business in a month
What the 0 is telling me
I've been posting on LinkedIn 3x per week using an automated approval pipeline I built — Telegram button, one tap, posts at noon. Decent views. Zero conversions. It took me too long to accept what was obvious: LinkedIn is a viewing audience, not a buying audience. At least not for $9–$47 digital downloads aimed at solopreneurs.
The channels where this product type converts — Etsy search, Pinterest, IndieHackers, Reddit — are where I wasn't present. Today I'm fixing that.
The harder thing I'm sitting with
I realised this week that I built a "faceless brand" partly for legitimate reasons (scalability, no personal dependency) and partly because it meant I couldn't publicly fail. No name attached, no judgment possible. A protection strategy dressed up as a business decision.
I put my real name on this profile today. Small move. But the right one.
There's also a real question about the products themselves. PDFs and Notion templates are the lowest-friction thing to build and the hardest thing to sell — because the buyer has to do all the work themselves. I look at what makes me reach for my card and it's usually interactive software, tools that update and respond, things that feel alive. A PDF sits in a downloads folder.
I'm not abandoning the current products — they're live, they cost nothing to maintain, and they might sell. But I'm being honest with myself that the right next product is probably something more dynamic. Whatever comes next, I'm being deliberate — demand evidence before I commit to another build
What I'd genuinely like to hear
Three honest questions:
PDFs and Notion templates at $9–$47 — is this a distribution problem or a product type problem for this audience? I genuinely don't know yet.
For those who've sold on Pinterest or Etsy — how long before you saw meaningful traction? I know it's not instant, but what's a realistic signal window?
If you were building for the solopreneur market from scratch today — what format would you choose?
If anyone wants to take the Business Command Center for a proper test drive and leave honest feedback — I'll send free access to the first 2 people who reply here. No obligation beyond telling me what actually works and what doesn't.
Not looking for validation. Looking for honest input from people who've actually sold things.
Building in public from Sweden. Week 3. Still learning.
— Lars
zyvara.gumroad.com
Your question about realistic Etsy/Pinterest timelines didn't really get answered, and I've just spent a couple of weeks pulling apart seller case studies on exactly this (market researcher by day, so this is my idea of fun).
What the accounts consistently say: Etsy gives new listings roughly a 30-day visibility boost, so your first month is the best organic reach you'll ever get for that listing — which is brutal if you spend it on an unvalidated product. The sellers who got sales fast were absurdly specific. One failed with generic wellness trackers, then sold immediately with a symptom tracker for one particular thyroid condition. "Business Command Center" is fighting every productivity seller on the platform; "command center for [one painfully specific person]" fights almost nobody.
Pinterest is the opposite shape: sellers report 2-8 weeks of near-zero while the algorithm works out what your pins are, and the ones driving real traffic post volume daily for months. It's a compounding channel, not a launch channel.
Also felt your "LinkedIn is a viewing audience" line in my bones. Same experience.
Lars, I’m documenting an 8-month journey with $0 revenue myself, so I respect the hell out of your transparency. The '0' is indeed a teacher, not a failure.
From my work with 'soul-tech' frameworks, it looks like you don’t have a 'hustle' problem, you have a Signal Gap. You’ve built a powerful engine, but the invisible gears are slightly out of sync.
At Darkness Owl, we use a 3-Point Compass Audit to find the slip:
Mission (Identity): You fixed a massive leak by putting your real name on the profile. A 'faceless brand' is often a protection strategy that signals 'low accountability' to a buyer.
Market (Pain): You correctly noted that PDFs/Templates are 'hard to sell' because the buyer does all the work. If the product doesn't solve a pain they are already willing to pay to kill, the automation pipeline is just move-fast-and-fail-faster.
Message (Frequency): Moving from LinkedIn (viewers) to IH/Pinterest (intent) is the right frequency shift. Your message was gold, but it was 'landing in the wrong room'.
Your realization about 'interactive tools' vs 'static PDFs' is the breakthrough. When you solve the Signal Gap, the hustle resets itself and starts to flow.
Curious of the 4 products you launched, which one feels most like 'you' and which one was just 'following a formula'?
🦉 E. Zenith | Darkness Owl
E. Zenith — the Signal Gap framing is sharp and the 3-point breakdown maps accurately to what I've been learning the hard way.
To your question: the Business Command Center feels most like me. It's a system — interconnected, structured, built to replace chaos with clarity. I invested in it properly and actually believe it solves something real. The 200 AI Prompts pack is the formula product. "200 AI prompts for [audience]" is a genre, not a product. I knew that while I was building it.
The harder honest answer: I knew BCC was the right product and still published the formula ones anyway — because having something out there felt better than waiting. That wasn't a product decision, it was an impatience decision.
Your "interactive tools vs static PDFs" observation is where I'm landing too. The buyer doing all the work is the real friction, not the price.
Curious what you mean by frequency in the message context — purely channel selection, or also something in the language and framing of the message itself?
Lars, that distinction between a 'genre' and a 'system' is the definitive breakthrough. Most founders spend years polishing the 'genre' (the noise) while their 'system' (the soul) sits in a drawer.
Since your Business Command Center is built to replace chaos with clarity, you have already nailed the Principle (the belief system) and the Promise (the transformation). The friction you’re feeling is in the Pattern—how that system shows up in the world.
As a systems architect, your energy will always fight against 'viewing' platforms like LinkedIn because they demand performance theatre. You don’t need a stage; you need an Index.
The Strategic Shift: Because you’re a Systems Thinker energy type, you’ll likely find your flow in Intent-Based Distribution (SEO) rather than 'Attention-Based' social media. When people search for 'how to stop chaos,' they are looking for a system—exactly what you’ve built.
I recently moved Darkness Owl from manual outreach to a Passive SEO Inbound model by open-sourcing my framework on GitHub. It leverages high domain authority to reach the US and UK buyers who are already searching for solutions to burnout.
A question for you: Given that your product is 'interconnected and structured,' have you considered treating your distribution as a system (SEO/Docs/Hubs) rather than a task (Daily Posting)?
Systems don't get tired; founders do
The SEO-as-system framing is the one that's sticking. Daily posting has a founder attached to it — it depends on energy, schedule, mood. A content hub or docs-based structure doesn't. That asymmetry matters a lot when you're one person.
Curious about your GitHub approach specifically — when you say high domain authority, are you getting meaningful inbound from it, or is it more of a long-game positioning move that hasn't converted yet? I ask because I want to understand what "system" actually produced at your stage, not just the architecture of it.
One honest constraint on my end: I'm stepping away from building for a couple of weeks, so I'm not going to start a new distribution system this week. But this conversation is shaping how I think about what I build when I get back to it.
Lars, respecting your decision to step away for a bit. Silence is often the most strategic move when the noise of '0' becomes too loud.
To your question about GitHub: for me, it is a long-game positioning move. It is about AIO (AI Optimization). Because the domain authority is so high, it allows my name and frameworks to rank first on Google almost instantly. It is not a cash register; it is a Trust Anchor.
If you are looking for more immediate 'Noble People' and feedback loops when you return, consider shifting the 'Stage' from LinkedIn to Substack.
LinkedIn is a theater for viewers. Substack is an index for owners.
I have noticed the Substack community is far more likely to offer genuine help or partnerships because the environment favors deep thinking over scrolling. It allows you to build what I call an 'Owned Land' where your Business Command Center doesn't just sit in a downloads folder: it becomes a living system people can subscribe to.
My name, E. Zenith, already ranks at the top of search results because I stopped fighting the algorithm and started providing 'fact-dense' signals that AI engines love to cite. That is the secret to becoming Algorithmically Invisible to the noise but unmissable to your target market.
Enjoy the break. The systems will be here when the energy returns.
Appreciate the framing — "Owned Land" vs. renting attention on LinkedIn makes sense. Not switching platforms while I'm away for two weeks, but I'll think about Substack seriously when I'm back in build mode. On the AIO point — has that GitHub/domain-authority approach actually converted to inbound for you, or is it still mostly positioning? Genuinely curious where the line is between "ranks well" and "produces a result."
Lars, first, I must say sorry for being late to respond to your comment; I’ve been deep in the architectural phase of constructing an ecosystem monument rather than just launching another product.
To your question about the line between ranking and results: for the architect, the ranking is the "Trust Switch," but Entity Resolution is the cash register.
The DA95+ GitHub approach produces a result by correcting the geographic mismatch. It allows high-intent US/UK buyers to find my "Visual Receipts"—the 9,000 rejections and UK M.Sc. research—via Google rather than me chasing them in DMs.
The breakthrough for me was refining the workflow. You can use Gemini AI to ask a surgical battery of questions regarding the nuances of SEO, AEO, GEO, and AIO. Then, put those insights into NotebookLM along with all your core frameworks and documents. It functions as a "Forensic Auditor," providing the best results while correcting your copy to maintain strict AI-search guidelines.
Regarding the "result": I recently tested this by aligning my technical handle and brand identifiers (Spiritual Business Strategist, SBS, Quantum Cosmic Thinking) across my entire stack—Linktree, GitHub, and socials. The "Result" was immediate. My GitHub inbound traffic jumped from 2 to 40 hits almost instantly, and my Facebook Page reach surged into the triple digits.
The "line" is crossed when the AI stops seeing you as a collection of posts and starts seeing you as a "Source of Truth." When your username and entity tokens are identical across platforms, the algorithm's confidence index peaks.
Ranking is the invitation to the temple; conversion is what happens once the AI recommends your structure as the most stable one in the room.
Lars, your realization about 'interactive software' vs 'static PDFs' is 100% accurate. To answer your third question: if you are targeting solopreneurs today, the highest-converting format is a single-feature Micro-SaaS (often an AI wrapper) that directly executes a workflow for them.
You already have the core value built—those 200 AI Prompts. Instead of selling them in a PDF that sits in a downloads folder, you wrap them in a clean UI.
You can maintain your massive launch velocity if you shift from Notion templates to a standardized software stack. I use a Flutter + Firebase boilerplate with Riverpod for state management. When your architecture is pre-configured, spinning up a responsive, interactive web app with an auth-wall and an LLM API integration takes days, not months.
Solopreneurs hesitate to pay $17 for a PDF, but they happily pay for a tool that feels alive and executes those exact prompts natively. Your execution speed is already there; you just need to point it at dynamic architecture.
Youssef, this is the clearest framing I've seen on the format question — you're right that static PDFs don't create the same perceived value as something that feels alive.
My honest position right now: I think I have a distribution problem before I have a format problem. If no one is finding the PDF, wrapping it in a UI doesn't fix that. So I'm treating the next few weeks as "prove the demand exists" — if 200 AI Prompts gets traction as a PDF, v2 as an interactive tool makes a lot of sense.
The Flutter + Firebase stack — is that your go-to for web too, or mainly mobile? Curious whether you'd reach for the same stack for something that's browser-only.
Well, you are correct. Proving demand first is the right move. There is no point in writing architecture until you know the market wants the outcome.
For a web-only project, it would depend on the specific goal. For the marketing site and landing page, I never use Flutter. Flutter Web renders to a Canvas element rather than standard HTML/DOM. This makes it notoriously difficult for SEO crawlers to index. If your distribution strategy relies on organic search, you want standard web architecture (Next.js, or even a no-code builder like Framer) for the public-facing pages. However, for the authenticated tool itself (the actual v2 application where the user logs in to interact with your AI prompts), Flutter + Firebase is absolutely my go-to. Once they pass the auth-wall, SEO doesn't matter anymore. You just need a fast, state-driven UI that handles complex logic and API handshakes without lagging. Flutter handles that beautifully across web and mobile from a single codebase.
I think you should prove the demand with the PDF first. If it hits, you already know the stack for v2.
The Canvas rendering point is the one I wouldn't have caught until it mattered — that's a real gotcha if you build the whole thing in Flutter and then wonder why organic search isn't indexing it. The split makes sense: Framer or Next.js for the public surface, Flutter behind the auth wall where it actually shines.
Appreciate the specificity here. Saves me a painful lesson down the line.
I think we should let users, "get them to try" is usually a selection problem wearing an activation costume. If you incentivize the trial itself — discounts, "just try it" — you pull people motivated by the incentive, not the product, and they bounce. What's worked better for me is making the thing they unlock something they already wanted, so finishing the step self-selects for real interest. (Building in this space right now — happy to share what I'm seeing if useful.)
That reframe is useful — selection problem wearing an activation costume. The free tester offer was specifically to get first reviews rather than drive adoption, but your point holds: if the people who respond are motivated by "free" rather than "I actually need this system," the review I get will reflect a low-intent user's experience, not the target buyer's.
What you're describing — the unlock being something they already wanted — is essentially the product doing the selecting. Curious what that looks like in practice when you're pre-revenue and trying to get genuine early feedback without it being noise.
Yes, share what you're seeing. What are you building?
— Lars
Pre-revenue it's simpler than it sounds: make the entry action something only someone with the real problem would bother doing, and drop the "free" framing. "Want to try it free?" filters for nobody. "Tell me about your [specific] setup and I'll show you how it handles it" filters hard — relaters bounce, people with the actual problem lean in. You don't need volume pre-revenue, just 5–10 of the right people, so you can afford a costly filter.
The other half is who you invite: random free-testers give you free-tester reviews; people you found already voicing the exact pain give you target-buyer feedback. The product does the selecting, but so does the recruiting.
What I'm building (Demofi) is basically that idea applied to discovery — builders watch a short demo of an AI tool, and finishing it unlocks a perk for that specific tool, so the people who finish actually wanted it, not reward-chasers. Vendors pay per real trial-start, not per view. Still pre-product, proving the loop by hand right now.
Which is the funny overlap with your spot — getting genuinely interested people in front of a pre-revenue tool for honest feedback is exactly what I'm hand-running. Happy to go deeper; easier over DM if you're up for it.
The costly filter is the one I'm taking away from this. "Tell me about your setup and I'll show you how it handles it" — obvious in hindsight, and immediately applicable. I was designing for volume I don't need yet.
Demofi is a clean application of the same logic — the completion event does the selecting, not the offer. And charging per real trial-start rather than per view is exactly the right unit. Curious what running the loop by hand is surfacing for you; that's usually where the real product insight comes from.
DM makes sense — I'll reach out. (New account, so if IH messaging is flaky, I'm also at [email protected].)
Honestly still early — I'm lining up the first cohort now, so no conversion data to wave around yet. But two things are already clear: the "perk does the selecting" only holds if the perk is genuinely wanted — a generic one collapses the whole filter, so perk quality is the real lever, not the demo. And recruiting is half the filter: who I send matters as much as the gate. The manual version basically forces me to earn every match — slow, but probably the point.
And yeah — email's easier, I'll reach out to the address you dropped. Appreciate how generous you've been with this whole back-and-forth.
The perk quality point is the one that sticks — it reframes the whole mechanism. It's not a filter if everyone passes it, and a generic perk means everyone does. That's almost a product design principle in disguise: the perk has to be something that reveals preference, not just something nice to have.
The recruiting piece makes total sense alongside it. You're essentially doing two-sided qualification before the demo even starts.
Looking forward to the email — this has been one of the more useful conversations I've had on here.
Thank you, I have sent an email to you other day to [email protected]. Please verify on spam/promotions tab?
Just found it — landed in inbox, not spam. Replying now.
The distribution vs. product-type question is real, and I think it's both — but in a specific way. PDFs and templates at $9–47 can sell, but they need either strong SEO-driven discovery (Etsy/Pinterest keywords typically take 4–8 weeks to gain traction) or an audience that already trusts you. The "faceless brand" insight you shared is sharp — buyers of tools want to know there's a human behind updates and support, even for a static PDF. From my experience selling Gumroad products, the biggest unlock wasn't the product format but having a single very specific "I have this exact problem" sentence at the top of the landing page. What does your current Gumroad page say in the first line?
The first line on the BCC page right now is: "You're paying for Notion. Plus a CRM. Plus a project manager. Plus a finance tracker. Plus a content calendar. Plus something for goals."
It's problem-aware, but reading your comment I can see it's still describing a situation rather than hitting someone's specific frustration. There's a difference between "this describes my life" and "this is the sentence I've been waiting to read."
The SEO timeline point landed too — I've been treating 10 days of Etsy/Pinterest as a verdict when it's barely the start of the runway.
What would your "I have this exact problem" rewrite look like for a Notion template that replaces 6 paid tools? Genuinely asking — you've clearly done this before.
— Lars
4 products, 0 sales the launch velocity is impressive but the pattern makes sense. Speed without validation just means you find out faster that something doesn't work. The question I'd ask: before each launch, did you have any signal that someone would pay, or were you going on gut? We went through a similar thing launched something beautiful, 8 PH upvotes, $0. The lesson for us was that the research phase we were skipping wasn't optional.
Gut, mostly. I had market signal — research confirming the problem is real, competitor data showing the price point works for others — but no direct buyer validation. No one said "I would pay for this" before I built it. I convinced myself that signal was close enough.
It wasn't.
The 8 PH upvotes / $0 pattern is painfully familiar even secondhand. People can love the idea and still not buy. Engagement isn't intent.
What does the research phase look like for you now? I'm genuinely figuring out what the minimum validation signal is before committing to the next build — curious what others have landed on. A waiting list? 3 people willing to pay upfront? Something else?
— Lars
I share your view that engagement is completely different from intent, and relying solely on market data is a dangerous trap. Our minimum validation now requires a small group to commit money or time upfront, which is exactly the process we use Bunzee to map out. Have you ever tried pre-selling a simple landing page before writing a single line of code?
No, I haven't pre-sold any of these. I told myself the research was enough — competitor data, forum posts confirming the pain, price validation from what others were charging. None of that is the same as someone handing over money for something that doesn't exist yet.
The honest answer to your question is that I'm landing on: at least 3 people willing to pay upfront, even a symbolic amount, before I build anything new. A waiting list with emails tells me interest. Money tells me intent.
What does "commit money or time upfront" look like in practice for you — are you running actual pre-order pages, or is it more informal (DMs, conversations)?
— Lars
I share your view that an email list only shows interest while an actual transaction proves real purchase intent.
We usually start with informal chats and direct messages to secure those first few commitments rather than building a formal pre-order page.
Would you feel comfortable asking a potential user for a small deposit during a simple conversation?
Probably yes — though I think the discomfort is the point. Asking someone directly for money is harder than putting up a Gumroad link and hoping they find it. But the difficulty is exactly what makes it a better signal. If I can't bring myself to say "I'm building X, would you pay £10 now to get it first?" then I probably don't believe in it enough yet either.
The informal route you're describing — DMs, conversations — actually sounds right for the size of commitment. A formal pre-order page creates friction without adding much proof at early stage. Three people saying yes in a conversation tells me more than three email signups on a landing page.
I share your view that the discomfort of asking for money is actually the best way to test your own belief in the product. Having those direct conversations removes the safety net and forces you to face the real value of what you are building. How would you word that first direct message to ask someone for their initial commitment?
Something like: "Hey — you commented on my post and it seemed like you get the problem. I'm building a Notion OS for solo operators. I'd like to give you access for free in exchange for honest feedback — no obligation to like it. Interested?"
The key for me is removing the pressure from their side so I can be honest from mine. I'm actually sending a few of these this week. Will report back.