3am, 4 holders, one plush moth holding a lamp that won't turn off.
No roadmap. No exit plan. Holder rewards on, dev bag locked in by choice.
The quiet ones are still awake when it sends. 🪽
coin: https://pump.fun/coin/EFjt7giEDHExkN2rLrxHz7S6nzPWSW946d8bGBJEpump
Hello everyone, I developed B2C projects for a long time. I reached a monthly income of $5,000, but with the development of artificial intelligence, the people I worked with turned to different solutions.
During this process, since I couldn’t prevent the decline of my income, I turned to new projects.
Knoku indexes DevTool companies’ documentation, GitHub, Notion/Confluence, OpenAPI spec, and old support tickets, and instantly answers developers’ questions by citing sources.
The answer appears in a site widget, on Slack, on Discord, and in the support form; any question it can’t solve goes to the support team. On top of that, there is an analytics panel that shows which questions are frequently asked and where the gaps are in the documentation.
My mistakes:
1) I started developing the product without defining an ICP and doing market research.
Actually, I tried to develop the product a few times and quit because I couldn’t bring the cost & output quality to the level I wanted. The question I asked myself while developing the product was quite clear: “Would I pay for a product of this quality?” and for a long time the answer to this question was “No.”
One night around two o’clock I came up with a different approach, got out of bed, and started developing. In the end, I had reached the quality I wanted; it was a satisfying result in terms of both price and quality. At that moment I thought I should keep building and for months I spoke to no one, did no market research, and focused only on the product and the engineering side. When no one was using my product yet, I spent days trying to reduce my cost from $0.025 to $0.018 and increase my correct result rate from 92% to 98.6% across multiple documents.
At the end of the day, I had a product with zero users that was well thought out from an engineering perspective.
2) Market research and a chain of wrong decisions..
After doing market research, I realized that the space I positioned myself in was very crowded.
I had developed a documentation‑first product (a chat widget added to documentation), but (most) chatbot products could already do this.
So I decided I needed to differentiate and started integrating tools used by DevTool/SaaS/IT companies.
3) I got trapped in the development cycle
Because I changed the ICP, the months-long development process (while already live) continued intensively. In the span of a month, development and testing processes were completed, and I kept developing for my project with zero customers without getting any feedback.
4) The ICP change dragged me onto a road of no return.
The ICP change dragged me to a level where enterprise meetings were being held. The new position I placed myself in (I realized later) was the level where companies closed sales through enterprise meetings. For a solo founder like me, this was like signing a death warrant.
5) Not having a B2B marketing background..
With B2C businesses I reached up to 5K$ MRR; I worked on setups where freelancers or solo founders could just pull out a card and buy. But in B2B, people don’t buy saying “Oh this looks nice,” it requires approval from accounting or a purchasing manager. Even if many people see and try it, they don’t want to present a product they don’t trust to upper management.
6) OSS Projects and Discord, Twitter..
I thought of making OSS projects my distribution channel. I contacted many project developers but got no response. I offered our annual $1,188.00 package for free use (as a sponsor), but no one got back to me.
7) Email marketing
The email marketing process was a complete disaster.. There is no other way to reach the purchasing managers of companies that need this product. These people don’t respond to cold emails; even with highly targeted lists, the response rate stays below 2%.
In short, my first B2B product development and marketing process taught me many things. I have not given up on my product Knoku; I am continuing to look for different distribution channels and I think I will change the pricing and lower the entry level.
Also, if you have any advice, I would like to hear it.
✨ Looking for a flexible online job? Work from the comfort of your home! ✨
✅ Must be 18 years old and above
✅ No Experience Required
✅ Flexible Schedule
✅ Training & Support Provided
✅ Mobile Phone & Internet Only
✅ Friendly Working Environment
✅ Weekly Payouts
💰 Earn up to $100–$300+ per week depending on your activity, consistency, and performance.
📱 Main Responsibilities:
• Answer incoming calls
• Engage in friendly conversations with callers
• Maintain an active and welcoming presence on the platform
🌸 Perfect For:
• Students (18+)
• Stay-at-home moms
• Part-time job seekers
• Anyone looking for extra income
🚀 Start your online earning journey today!
📩 Interested? Send me a direct message (DM) for more details and application information. 💖
✨ Looking for a flexible online job? Work from the comfort of your home! ✨
✅ Must be 18 years old and above
✅ No Experience Required
✅ Flexible Schedule
✅ Training & Support Provided
✅ Mobile Phone & Internet Only
✅ Friendly Working Environment
✅ Weekly Payouts
💰 Earn up to $100–$300+ per week depending on your activity, consistency, and performance.
📱 Main Responsibilities:
• Answer incoming calls
• Engage in friendly conversations with callers
• Maintain an active and welcoming presence on the platform
🌸 Perfect For:
• Students (18+)
• Stay-at-home moms
• Part-time job seekers
• Anyone looking for extra income
🚀 Start your online earning journey today!
📩 Interested? Send me a direct message (DM) for more details and application information. 💖
Hello everyone, after the outbid(.)lol website went viral on Twitter, I had an idea.
People can add their projects and publish them for between $1 and $9.95. When projects are published, the amount paid shouldn’t be visible to others. Until the board closes (50 projects), the amount paid will remain hidden, and the list will be sorted randomly.
My goal is to change the logic where others get traffic from those who pay the most.
After the board closes, the top 10 projects with the highest payments will be revealed first. The entire list will be visible in the board section.
You can't choose how much you'll pay; it's up to chance.
I went first with my own project: payluck(.)lol
I look forward to your feedback.
I’m building a tool for teams that already have docs, help pages, PDFs, internal notes, or community answers spread across different places.
The idea is not just “add an AI chatbot”.
It indexes those sources, answers questions with citations, and shows which questions could not be answered clearly so the team can see where their knowledge base is weak.
I’m trying to understand the real pain before pushing it further:
Do teams actually want to know what users or teammates failed to find?
Would cited AI answers reduce support or repeated internal questions?
Or does this still feel like another AI wrapper nobody really needs?
Not sharing a link because I’m mainly looking for honest feedback.
If you're signing up for Cursor for the first time, my referral code gets you 50% off the first month on Pro, Pro+, or Ultra:
https://cursor.com/referral?code=0RSCVODXC4JV
Valid for new accounts / first-time paid subscriptions only. Full disclosure: I get $25 in credits when the code is used.
For SaaS/devtool teams with public docs:
When the same support questions keep coming up, how do you decide what should become a docs update?
Do you tag tickets manually, review search logs, use product analytics, or just rely on support/product teams noticing patterns?
I’m trying to understand how teams handle this in practice.
