VibeBuilders.ai Logo
VibeBuilders.ai

Evolve

Explore resources related to evolve to help implement AI solutions for your business.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies) (I will not promote)
reddit
LLM Vibe Score0
Human Vibe Score1
Royal_Rest8409This week

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies) (I will not promote)

AI Palette is an AI-driven platform that helps food and beverage companies predict emerging product trends. I had the opportunity recently to sit down with the founder to get his advice on building an AI-first startup, which he'll be going through in this post. (I will not promote) About AI Palette: Co-founders: >!2 (Somsubhra GanChoudhuri, Himanshu Upreti)!!100+!!$12.7M USD!!AI-powered predictive analytics for the CPG (Consumer Packaged Goods) industry!!Signed first paying customer in the first year!!65+ global brands, including Cargill, Diageo, Ajinomoto, Symrise, Mondelez, and L’Oréal, use AI Palette!!Every new product launched has secured a paying client within months!!Expanded into Beauty & Personal Care (BPC), onboarding one of India’s largest BPC companies within weeks!!Launched multiple new product lines in the last two years, creating a unified suite for brand innovation!Identify the pain points in your industry for ideas* When I was working in the flavour and fragrance industry, I noticed a major issue CPG companies faced: launching a product took at least one to two years. For instance, if a company decided today to launch a new juice, it wouldn’t hit the market until 2027. This long timeline made it difficult to stay relevant and on top of trends. Another big problem I noticed was that companies relied heavily on market research to determine what products to launch. While this might work for current consumer preferences, it was highly inefficient since the product wouldn’t actually reach the market for several years. By the time the product launched, the consumer trends had already shifted, making that research outdated. That’s where AI can play a crucial role. Instead of looking at what consumers like today, we realised that companies should use AI to predict what they will want next. This allows businesses to create products that are ahead of the curve. Right now, the failure rate for new product launches is alarmingly high, with 8 out of 10 products failing. By leveraging AI, companies can avoid wasting resources on products that won’t succeed, leading to better, more successful launches. Start by talking to as many industry experts as possible to identify the real problems When we first had the idea for AI Palette, it was just a hunch, a gut feeling—we had no idea whether people would actually pay for it. To validate the idea, we reached out to as many people as we could within the industry. Since our focus area was all about consumer insights, we spoke to professionals in the CPG sector, particularly those in the insights departments of CPG companies. Through these early conversations, we began to see a common pattern emerge and identified the exact problem we wanted to solve. Don’t tell people what you’re building—listen to their frustrations and challenges first. Going into these early customer conversations, our goal was to listen and understand their challenges without telling them what we were trying to build. This is crucial as it ensures that you can gather as much data about the problem to truly understand it and that you aren't biasing their answers by showing your solution. This process helped us in two key ways: First, it validated that there was a real problem in the industry through the number of people who spoke about experiencing the same problem. Second, it allowed us to understand the exact scale and depth of the problem—e.g., how much money companies were spending on consumer research, what kind of tools they were currently using, etc. Narrow down your focus to a small, actionable area to solve initially. Once we were certain that there was a clear problem worth solving, we didn’t try to tackle everything at once. As a small team of two people, we started by focusing on a specific area of the problem—something big enough to matter but small enough for us to handle. Then, we approached customers with a potential solution and asked them for feedback. We learnt that our solution seemed promising, but we wanted to validate it further. If customers are willing to pay you for the solution, it’s a strong validation signal for market demand. One of our early customer interviewees even asked us to deliver the solution, which we did manually at first. We used machine learning models to analyse the data and presented the results in a slide deck. They paid us for the work, which was a critical moment. It meant we had something with real potential, and we had customers willing to pay us before we had even built the full product. This was the key validation that we needed. By the time we were ready to build the product, we had already gathered crucial insights from our early customers. We understood the specific information they wanted and how they wanted the results to be presented. This input was invaluable in shaping the development of our final product. Building & Product Development Start with a simple concept/design to validate with customers before building When we realised the problem and solution, we began by designing the product, but not by jumping straight into coding. Instead, we created wireframes and user interfaces using tools like InVision and Figma. This allowed us to visually represent the product without the need for backend or frontend development at first. The goal was to showcase how the product would look and feel, helping potential customers understand its value before we even started building. We showed these designs to potential customers and asked for feedback. Would they want to buy this product? Would they pay for it? We didn’t dive into actual development until we found a customer willing to pay a significant amount for the solution. This approach helped us ensure we were on the right track and didn’t waste time or resources building something customers didn’t actually want. Deliver your solution using a manual consulting approach before developing an automated product Initially, we solved problems for customers in a more "consulting" manner, delivering insights manually. Recall how I mentioned that when one of our early customer interviewees asked us to deliver the solution, we initially did it manually by using machine learning models to analyse the data and presenting the results to them in a slide deck. This works for the initial stages of validating your solution, as you don't want to invest too much time into building a full-blown MVP before understanding the exact features and functionalities that your users want. However, after confirming that customers were willing to pay for what we provided, we moved forward with actual product development. This shift from a manual service to product development was key to scaling in a sustainable manner, as our building was guided by real-world feedback and insights rather than intuition. Let ongoing customer feedback drive iteration and the product roadmap Once we built the first version of the product, it was basic, solving only one problem. But as we worked closely with customers, they requested additional features and functionalities to make it more useful. As a result, we continued to evolve the product to handle more complex use cases, gradually developing new modules based on customer feedback. Product development is a continuous process. Our early customers pushed us to expand features and modules, from solving just 20% of their problems to tackling 50–60% of their needs. These demands shaped our product roadmap and guided the development of new features, ultimately resulting in a more complete solution. Revenue and user numbers are key metrics for assessing product-market fit. However, critical mass varies across industries Product-market fit (PMF) can often be gauged by looking at the size of your revenue and the number of customers you're serving. Once you've reached a certain critical mass of customers, you can usually tell that you're starting to hit product-market fit. However, this critical mass varies by industry and the type of customers you're targeting. For example, if you're building an app for a broad consumer market, you may need thousands of users. But for enterprise software, product-market fit may be reached with just a few dozen key customers. Compare customer engagement and retention with other available solutions on the market for product-market fit Revenue and the number of customers alone isn't always enough to determine if you're reaching product-market fit. The type of customer and the use case for your product also matter. The level of engagement with your product—how much time users are spending on the platform—is also an important metric to track. The more time they spend, the more likely it is that your product is meeting a crucial need. Another way to evaluate product-market fit is by assessing retention, i.e whether users are returning to your platform and relying on it consistently, as compared to other solutions available. That's another key indication that your solution is gaining traction in the market. Business Model & Monetisation Prioritise scalability Initially, we started with a consulting-type model where we tailor-made specific solutions for each customer use-case we encountered and delivered the CPG insights manually, but we soon realized that this wasn't scalable. The problem with consulting is that you need to do the same work repeatedly for every new project, which requires a large team to handle the workload. That is not how you sustain a high-growth startup. To solve this, we focused on building a product that would address the most common problems faced by our customers. Once built, this product could be sold to thousands of customers without significant overheads, making the business scalable. With this in mind, we decided on a SaaS (Software as a Service) business model. The benefit of SaaS is that once you create the software, you can sell it to many customers without adding extra overhead. This results in a business with higher margins, where the same product can serve many customers simultaneously, making it much more efficient than the consulting model. Adopt a predictable, simplistic business model for efficiency. Look to industry practices for guidance When it came to monetisation, we considered the needs of our CPG customers, who I knew from experience were already accustomed to paying annual subscriptions for sales databases and other software services. We decided to adopt the same model and charge our customers an annual upfront fee. This model worked well for our target market, aligning with industry standards and ensuring stable, recurring revenue. Moreover, our target CPG customers were already used to this business model and didn't have to choose from a huge variety of payment options, making closing sales a straightforward and efficient process. Marketing & Sales Educate the market to position yourself as a thought leader When we started, AI was not widely understood, especially in the CPG industry. We had to create awareness around both AI and its potential value. Our strategy focused on educating potential users and customers about AI, its relevance, and why they should invest in it. This education was crucial to the success of our marketing efforts. To establish credibility, we adopted a thought leadership approach. We wrote blogs on the importance of AI and how it could solve problems for CPG companies. We also participated in events and conferences to demonstrate our expertise in applying AI to the industry. This helped us build our brand and reputation as leaders in the AI space for CPG, and word-of-mouth spread as customers recognized us as the go-to company for AI solutions. It’s tempting for startups to offer products for free in the hopes of gaining early traction with customers, but this approach doesn't work in the long run. Free offerings don’t establish the value of your product, and customers may not take them seriously. You should always charge for pilots, even if the fee is minimal, to ensure that the customer is serious about potentially working with you, and that they are committed and engaged with the product. Pilots/POCs/Demos should aim to give a "flavour" of what you can deliver A paid pilot/POC trial also gives you the opportunity to provide a “flavour” of what your product can deliver, helping to build confidence and trust with the client. It allows customers to experience a detailed preview of what your product can do, which builds anticipation and desire for the full functionality. During this phase, ensure your product is built to give them a taste of the value you can provide, which sets the stage for a broader, more impactful adoption down the line. Fundraising & Financial Management Leverage PR to generate inbound interest from VCs When it comes to fundraising, our approach was fairly traditional—we reached out to VCs and used connections from existing investors to make introductions. However, looking back, one thing that really helped us build momentum during our fundraising process was getting featured in Tech in Asia. This wasn’t planned; it just so happened that Tech in Asia was doing a series on AI startups in Southeast Asia and they reached out to us for an article. During the interview, they asked if we were fundraising, and we mentioned that we were. As a result, several VCs we hadn’t yet contacted reached out to us. This inbound interest was incredibly valuable, and we found it far more effective than our outbound efforts. So, if you can, try to generate some PR attention—it can help create inbound interest from VCs, and that interest is typically much stronger and more promising than any outbound strategies because they've gone out of their way to reach out to you. Be well-prepared and deliberate about fundraising. Keep trying and don't lose heart When pitching to VCs, it’s crucial to be thoroughly prepared, as you typically only get one shot at making an impression. If you mess up, it’s unlikely they’ll give you a second chance. You need to have key metrics at your fingertips, especially if you're running a SaaS company. Be ready to answer questions like: What’s your retention rate? What are your projections for the year? How much will you close? What’s your average contract value? These numbers should be at the top of your mind. Additionally, fundraising should be treated as a structured process, not something you do on the side while juggling other tasks. When you start, create a clear plan: identify 20 VCs to reach out to each week. By planning ahead, you’ll maintain momentum and speed up the process. Fundraising can be exhausting and disheartening, especially when you face multiple rejections. Remember, you just need one investor to say yes to make it all worthwhile. When using funds, prioritise profitability and grow only when necessary. Don't rely on funding to survive. In the past, the common advice for startups was to raise money, burn through it quickly, and use it to boost revenue numbers, even if that meant operating at a loss. The idea was that profitability wasn’t the main focus, and the goal was to show rapid growth for the next funding round. However, times have changed, especially with the shift from “funding summer” to “funding winter.” My advice now is to aim for profitability as soon as possible and grow only when it's truly needed. For example, it’s tempting to hire a large team when you have substantial funds in the bank, but ask yourself: Do you really need 10 new hires, or could you get by with just four? Growing too quickly can lead to unnecessary expenses, so focus on reaching profitability as soon as possible, rather than just inflating your team or burn rate. The key takeaway is to spend your funds wisely and only when absolutely necessary to reach profitability. You want to avoid becoming dependent on future VC investments to keep your company afloat. Instead, prioritize reaching break-even as quickly as you can, so you're not reliant on external funding to survive in the long run. Team-Building & Leadership Look for complementary skill sets in co-founders When choosing a co-founder, it’s important to find someone with a complementary skill set, not just someone you’re close to. For example, I come from a business and commercial background, so I needed someone with technical expertise. That’s when I found my co-founder, Himanshu, who had experience in machine learning and AI. He was a great match because his technical knowledge complemented my business skills, and together we formed a strong team. It might seem natural to choose your best friend as your co-founder, but this can often lead to conflict. Chances are, you and your best friend share similar interests, skills, and backgrounds, which doesn’t bring diversity to the table. If both of you come from the same industry or have the same strengths, you may end up butting heads on how things should be done. Having diverse skill sets helps avoid this and fosters a more collaborative working relationship. Himanshu (left) and Somsubhra (right) co-founded AI Palette in 2018 Define roles clearly to prevent co-founder conflict To avoid conflict, it’s essential that your roles as co-founders are clearly defined from the beginning. If your co-founder and you have distinct responsibilities, there is no room for overlap or disagreement. This ensures that both of you can work without stepping on each other's toes, and there’s mutual respect for each other’s expertise. This is another reason as to why it helps to have a co-founder with a complementary skillset to yours. Not only is having similar industry backgrounds and skillsets not particularly useful when building out your startup, it's also more likely to lead to conflicts since you both have similar subject expertise. On the other hand, if your co-founder is an expert in something that you're not, you're less likely to argue with them about their decisions regarding that aspect of the business and vice versa when it comes to your decisions. Look for employees who are driven by your mission, not salary For early-stage startups, the first hires are crucial. These employees need to be highly motivated and excited about the mission. Since the salary will likely be low and the work demanding, they must be driven by something beyond just the paycheck. The right employees are the swash-buckling pirates and romantics, i.e those who are genuinely passionate about the startup’s vision and want to be part of something impactful beyond material gains. When employees are motivated by the mission, they are more likely to stick around and help take the startup to greater heights. A litmus test for hiring: Would you be excited to work with them on a Sunday? One of the most important rounds in the hiring process is the culture fit round. This is where you assess whether a candidate shares the same values as you and your team. A key question to ask yourself is: "Would I be excited to work with this person on a Sunday?" If there’s any doubt about your answer, it’s likely not a good fit. The idea is that you want employees who align with the company's culture and values and who you would enjoy collaborating with even outside of regular work hours. How we structure the team at AI Palette We have three broad functions in our organization. The first two are the big ones: Technical Team – This is the core of our product and technology. This team is responsible for product development and incorporating customer feedback into improving the technology Commercial Team – This includes sales, marketing, customer service, account managers, and so on, handling everything related to business growth and customer relations. General and Administrative Team – This smaller team supports functions like finance, HR, and administration. As with almost all businesses, we have teams that address the two core tasks of building (technical team) and selling (commercial team), but given the size we're at now, having the administrative team helps smoothen operations. Set broad goals but let your teams decide on execution What I've done is recruit highly skilled people who don't need me to micromanage them on a day-to-day basis. They're experts in their roles, and as Steve Jobs said, when you hire the right person, you don't have to tell them what to do—they understand the purpose and tell you what to do. So, my job as the CEO is to set the broader goals for them, review the plans they have to achieve those goals, and periodically check in on progress. For example, if our broad goal is to meet a certain revenue target, I break it down across teams: For the sales team, I’ll look at how they plan to hit that target—how many customers they need to sell to, how many salespeople they need, and what tactics and strategies they plan to use. For the technical team, I’ll evaluate our product offerings—whether they think we need to build new products to attract more customers, and whether they think it's scalable for the number of customers we plan to serve. This way, the entire organization's tasks are cascaded in alignment with our overarching goals, with me setting the direction and leaving the details of execution to the skilled team members that I hire.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

16 years old and thinking about creating a startup
reddit
LLM Vibe Score0
Human Vibe Score1
NCS001This week

16 years old and thinking about creating a startup

Hi to everyone, this is my first post on Reddit and r/Startups. Sorry in advance if there is any mistake. I'm 16 years old, and I'm already planning to create my startup. Growing up in the digital age has given me both inspiration and doubts. On one side, you hear advice like, “You need connections with powerful people to succeed.” On the other, there are stories of founders coming from poverty and now leading billion-dollar companies.That really sucks. I'm here because I believe this community offers honest and grounded insights. So you can analyze, I leave you my goals. I accept all the advice you have. I’ll finish high school in two years while using my free time to learn about AI, programming, agile methods, and business basics. After that, I plan to pursue a Systems Engineering degree, even though I’ve debated skipping university. My older siblings convinced me it’s worth it for the professional and technical foundation. During college, I aim to freelance, save money, and build connections with entrepreneurs and developers. Beyond that, my 15-year plan includes working in tech companies to gain experience, creating an MVP for my startup, and securing funding through investors or incubators. I want to solve real-world problems using tools that feel future-proof. While I sometimes feel behind, I’m determined to catch up and take advantage of the opportunities ahead. I know the startup journey is uncertain—like a vulnerable animal facing competition, funding issues, and market challenges. But I’m ready to adapt as my vision evolves. Like for example the time. Obviously I would like to keep it exactly but you never know what can happen along the way. I’d love to hear your thoughts or advice. Thanks in advance, and I apologize if anything is unclear

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies) (I will not promote)
reddit
LLM Vibe Score0
Human Vibe Score1
Royal_Rest8409This week

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies) (I will not promote)

AI Palette is an AI-driven platform that helps food and beverage companies predict emerging product trends. I had the opportunity recently to sit down with the founder to get his advice on building an AI-first startup, which he'll be going through in this post. (I will not promote) About AI Palette: Co-founders: >!2 (Somsubhra GanChoudhuri, Himanshu Upreti)!!100+!!$12.7M USD!!AI-powered predictive analytics for the CPG (Consumer Packaged Goods) industry!!Signed first paying customer in the first year!!65+ global brands, including Cargill, Diageo, Ajinomoto, Symrise, Mondelez, and L’Oréal, use AI Palette!!Every new product launched has secured a paying client within months!!Expanded into Beauty & Personal Care (BPC), onboarding one of India’s largest BPC companies within weeks!!Launched multiple new product lines in the last two years, creating a unified suite for brand innovation!Identify the pain points in your industry for ideas* When I was working in the flavour and fragrance industry, I noticed a major issue CPG companies faced: launching a product took at least one to two years. For instance, if a company decided today to launch a new juice, it wouldn’t hit the market until 2027. This long timeline made it difficult to stay relevant and on top of trends. Another big problem I noticed was that companies relied heavily on market research to determine what products to launch. While this might work for current consumer preferences, it was highly inefficient since the product wouldn’t actually reach the market for several years. By the time the product launched, the consumer trends had already shifted, making that research outdated. That’s where AI can play a crucial role. Instead of looking at what consumers like today, we realised that companies should use AI to predict what they will want next. This allows businesses to create products that are ahead of the curve. Right now, the failure rate for new product launches is alarmingly high, with 8 out of 10 products failing. By leveraging AI, companies can avoid wasting resources on products that won’t succeed, leading to better, more successful launches. Start by talking to as many industry experts as possible to identify the real problems When we first had the idea for AI Palette, it was just a hunch, a gut feeling—we had no idea whether people would actually pay for it. To validate the idea, we reached out to as many people as we could within the industry. Since our focus area was all about consumer insights, we spoke to professionals in the CPG sector, particularly those in the insights departments of CPG companies. Through these early conversations, we began to see a common pattern emerge and identified the exact problem we wanted to solve. Don’t tell people what you’re building—listen to their frustrations and challenges first. Going into these early customer conversations, our goal was to listen and understand their challenges without telling them what we were trying to build. This is crucial as it ensures that you can gather as much data about the problem to truly understand it and that you aren't biasing their answers by showing your solution. This process helped us in two key ways: First, it validated that there was a real problem in the industry through the number of people who spoke about experiencing the same problem. Second, it allowed us to understand the exact scale and depth of the problem—e.g., how much money companies were spending on consumer research, what kind of tools they were currently using, etc. Narrow down your focus to a small, actionable area to solve initially. Once we were certain that there was a clear problem worth solving, we didn’t try to tackle everything at once. As a small team of two people, we started by focusing on a specific area of the problem—something big enough to matter but small enough for us to handle. Then, we approached customers with a potential solution and asked them for feedback. We learnt that our solution seemed promising, but we wanted to validate it further. If customers are willing to pay you for the solution, it’s a strong validation signal for market demand. One of our early customer interviewees even asked us to deliver the solution, which we did manually at first. We used machine learning models to analyse the data and presented the results in a slide deck. They paid us for the work, which was a critical moment. It meant we had something with real potential, and we had customers willing to pay us before we had even built the full product. This was the key validation that we needed. By the time we were ready to build the product, we had already gathered crucial insights from our early customers. We understood the specific information they wanted and how they wanted the results to be presented. This input was invaluable in shaping the development of our final product. Building & Product Development Start with a simple concept/design to validate with customers before building When we realised the problem and solution, we began by designing the product, but not by jumping straight into coding. Instead, we created wireframes and user interfaces using tools like InVision and Figma. This allowed us to visually represent the product without the need for backend or frontend development at first. The goal was to showcase how the product would look and feel, helping potential customers understand its value before we even started building. We showed these designs to potential customers and asked for feedback. Would they want to buy this product? Would they pay for it? We didn’t dive into actual development until we found a customer willing to pay a significant amount for the solution. This approach helped us ensure we were on the right track and didn’t waste time or resources building something customers didn’t actually want. Deliver your solution using a manual consulting approach before developing an automated product Initially, we solved problems for customers in a more "consulting" manner, delivering insights manually. Recall how I mentioned that when one of our early customer interviewees asked us to deliver the solution, we initially did it manually by using machine learning models to analyse the data and presenting the results to them in a slide deck. This works for the initial stages of validating your solution, as you don't want to invest too much time into building a full-blown MVP before understanding the exact features and functionalities that your users want. However, after confirming that customers were willing to pay for what we provided, we moved forward with actual product development. This shift from a manual service to product development was key to scaling in a sustainable manner, as our building was guided by real-world feedback and insights rather than intuition. Let ongoing customer feedback drive iteration and the product roadmap Once we built the first version of the product, it was basic, solving only one problem. But as we worked closely with customers, they requested additional features and functionalities to make it more useful. As a result, we continued to evolve the product to handle more complex use cases, gradually developing new modules based on customer feedback. Product development is a continuous process. Our early customers pushed us to expand features and modules, from solving just 20% of their problems to tackling 50–60% of their needs. These demands shaped our product roadmap and guided the development of new features, ultimately resulting in a more complete solution. Revenue and user numbers are key metrics for assessing product-market fit. However, critical mass varies across industries Product-market fit (PMF) can often be gauged by looking at the size of your revenue and the number of customers you're serving. Once you've reached a certain critical mass of customers, you can usually tell that you're starting to hit product-market fit. However, this critical mass varies by industry and the type of customers you're targeting. For example, if you're building an app for a broad consumer market, you may need thousands of users. But for enterprise software, product-market fit may be reached with just a few dozen key customers. Compare customer engagement and retention with other available solutions on the market for product-market fit Revenue and the number of customers alone isn't always enough to determine if you're reaching product-market fit. The type of customer and the use case for your product also matter. The level of engagement with your product—how much time users are spending on the platform—is also an important metric to track. The more time they spend, the more likely it is that your product is meeting a crucial need. Another way to evaluate product-market fit is by assessing retention, i.e whether users are returning to your platform and relying on it consistently, as compared to other solutions available. That's another key indication that your solution is gaining traction in the market. Business Model & Monetisation Prioritise scalability Initially, we started with a consulting-type model where we tailor-made specific solutions for each customer use-case we encountered and delivered the CPG insights manually, but we soon realized that this wasn't scalable. The problem with consulting is that you need to do the same work repeatedly for every new project, which requires a large team to handle the workload. That is not how you sustain a high-growth startup. To solve this, we focused on building a product that would address the most common problems faced by our customers. Once built, this product could be sold to thousands of customers without significant overheads, making the business scalable. With this in mind, we decided on a SaaS (Software as a Service) business model. The benefit of SaaS is that once you create the software, you can sell it to many customers without adding extra overhead. This results in a business with higher margins, where the same product can serve many customers simultaneously, making it much more efficient than the consulting model. Adopt a predictable, simplistic business model for efficiency. Look to industry practices for guidance When it came to monetisation, we considered the needs of our CPG customers, who I knew from experience were already accustomed to paying annual subscriptions for sales databases and other software services. We decided to adopt the same model and charge our customers an annual upfront fee. This model worked well for our target market, aligning with industry standards and ensuring stable, recurring revenue. Moreover, our target CPG customers were already used to this business model and didn't have to choose from a huge variety of payment options, making closing sales a straightforward and efficient process. Marketing & Sales Educate the market to position yourself as a thought leader When we started, AI was not widely understood, especially in the CPG industry. We had to create awareness around both AI and its potential value. Our strategy focused on educating potential users and customers about AI, its relevance, and why they should invest in it. This education was crucial to the success of our marketing efforts. To establish credibility, we adopted a thought leadership approach. We wrote blogs on the importance of AI and how it could solve problems for CPG companies. We also participated in events and conferences to demonstrate our expertise in applying AI to the industry. This helped us build our brand and reputation as leaders in the AI space for CPG, and word-of-mouth spread as customers recognized us as the go-to company for AI solutions. It’s tempting for startups to offer products for free in the hopes of gaining early traction with customers, but this approach doesn't work in the long run. Free offerings don’t establish the value of your product, and customers may not take them seriously. You should always charge for pilots, even if the fee is minimal, to ensure that the customer is serious about potentially working with you, and that they are committed and engaged with the product. Pilots/POCs/Demos should aim to give a "flavour" of what you can deliver A paid pilot/POC trial also gives you the opportunity to provide a “flavour” of what your product can deliver, helping to build confidence and trust with the client. It allows customers to experience a detailed preview of what your product can do, which builds anticipation and desire for the full functionality. During this phase, ensure your product is built to give them a taste of the value you can provide, which sets the stage for a broader, more impactful adoption down the line. Fundraising & Financial Management Leverage PR to generate inbound interest from VCs When it comes to fundraising, our approach was fairly traditional—we reached out to VCs and used connections from existing investors to make introductions. However, looking back, one thing that really helped us build momentum during our fundraising process was getting featured in Tech in Asia. This wasn’t planned; it just so happened that Tech in Asia was doing a series on AI startups in Southeast Asia and they reached out to us for an article. During the interview, they asked if we were fundraising, and we mentioned that we were. As a result, several VCs we hadn’t yet contacted reached out to us. This inbound interest was incredibly valuable, and we found it far more effective than our outbound efforts. So, if you can, try to generate some PR attention—it can help create inbound interest from VCs, and that interest is typically much stronger and more promising than any outbound strategies because they've gone out of their way to reach out to you. Be well-prepared and deliberate about fundraising. Keep trying and don't lose heart When pitching to VCs, it’s crucial to be thoroughly prepared, as you typically only get one shot at making an impression. If you mess up, it’s unlikely they’ll give you a second chance. You need to have key metrics at your fingertips, especially if you're running a SaaS company. Be ready to answer questions like: What’s your retention rate? What are your projections for the year? How much will you close? What’s your average contract value? These numbers should be at the top of your mind. Additionally, fundraising should be treated as a structured process, not something you do on the side while juggling other tasks. When you start, create a clear plan: identify 20 VCs to reach out to each week. By planning ahead, you’ll maintain momentum and speed up the process. Fundraising can be exhausting and disheartening, especially when you face multiple rejections. Remember, you just need one investor to say yes to make it all worthwhile. When using funds, prioritise profitability and grow only when necessary. Don't rely on funding to survive. In the past, the common advice for startups was to raise money, burn through it quickly, and use it to boost revenue numbers, even if that meant operating at a loss. The idea was that profitability wasn’t the main focus, and the goal was to show rapid growth for the next funding round. However, times have changed, especially with the shift from “funding summer” to “funding winter.” My advice now is to aim for profitability as soon as possible and grow only when it's truly needed. For example, it’s tempting to hire a large team when you have substantial funds in the bank, but ask yourself: Do you really need 10 new hires, or could you get by with just four? Growing too quickly can lead to unnecessary expenses, so focus on reaching profitability as soon as possible, rather than just inflating your team or burn rate. The key takeaway is to spend your funds wisely and only when absolutely necessary to reach profitability. You want to avoid becoming dependent on future VC investments to keep your company afloat. Instead, prioritize reaching break-even as quickly as you can, so you're not reliant on external funding to survive in the long run. Team-Building & Leadership Look for complementary skill sets in co-founders When choosing a co-founder, it’s important to find someone with a complementary skill set, not just someone you’re close to. For example, I come from a business and commercial background, so I needed someone with technical expertise. That’s when I found my co-founder, Himanshu, who had experience in machine learning and AI. He was a great match because his technical knowledge complemented my business skills, and together we formed a strong team. It might seem natural to choose your best friend as your co-founder, but this can often lead to conflict. Chances are, you and your best friend share similar interests, skills, and backgrounds, which doesn’t bring diversity to the table. If both of you come from the same industry or have the same strengths, you may end up butting heads on how things should be done. Having diverse skill sets helps avoid this and fosters a more collaborative working relationship. Himanshu (left) and Somsubhra (right) co-founded AI Palette in 2018 Define roles clearly to prevent co-founder conflict To avoid conflict, it’s essential that your roles as co-founders are clearly defined from the beginning. If your co-founder and you have distinct responsibilities, there is no room for overlap or disagreement. This ensures that both of you can work without stepping on each other's toes, and there’s mutual respect for each other’s expertise. This is another reason as to why it helps to have a co-founder with a complementary skillset to yours. Not only is having similar industry backgrounds and skillsets not particularly useful when building out your startup, it's also more likely to lead to conflicts since you both have similar subject expertise. On the other hand, if your co-founder is an expert in something that you're not, you're less likely to argue with them about their decisions regarding that aspect of the business and vice versa when it comes to your decisions. Look for employees who are driven by your mission, not salary For early-stage startups, the first hires are crucial. These employees need to be highly motivated and excited about the mission. Since the salary will likely be low and the work demanding, they must be driven by something beyond just the paycheck. The right employees are the swash-buckling pirates and romantics, i.e those who are genuinely passionate about the startup’s vision and want to be part of something impactful beyond material gains. When employees are motivated by the mission, they are more likely to stick around and help take the startup to greater heights. A litmus test for hiring: Would you be excited to work with them on a Sunday? One of the most important rounds in the hiring process is the culture fit round. This is where you assess whether a candidate shares the same values as you and your team. A key question to ask yourself is: "Would I be excited to work with this person on a Sunday?" If there’s any doubt about your answer, it’s likely not a good fit. The idea is that you want employees who align with the company's culture and values and who you would enjoy collaborating with even outside of regular work hours. How we structure the team at AI Palette We have three broad functions in our organization. The first two are the big ones: Technical Team – This is the core of our product and technology. This team is responsible for product development and incorporating customer feedback into improving the technology Commercial Team – This includes sales, marketing, customer service, account managers, and so on, handling everything related to business growth and customer relations. General and Administrative Team – This smaller team supports functions like finance, HR, and administration. As with almost all businesses, we have teams that address the two core tasks of building (technical team) and selling (commercial team), but given the size we're at now, having the administrative team helps smoothen operations. Set broad goals but let your teams decide on execution What I've done is recruit highly skilled people who don't need me to micromanage them on a day-to-day basis. They're experts in their roles, and as Steve Jobs said, when you hire the right person, you don't have to tell them what to do—they understand the purpose and tell you what to do. So, my job as the CEO is to set the broader goals for them, review the plans they have to achieve those goals, and periodically check in on progress. For example, if our broad goal is to meet a certain revenue target, I break it down across teams: For the sales team, I’ll look at how they plan to hit that target—how many customers they need to sell to, how many salespeople they need, and what tactics and strategies they plan to use. For the technical team, I’ll evaluate our product offerings—whether they think we need to build new products to attract more customers, and whether they think it's scalable for the number of customers we plan to serve. This way, the entire organization's tasks are cascaded in alignment with our overarching goals, with me setting the direction and leaving the details of execution to the skilled team members that I hire.

I spent 6 months on building a tool, and got 0 zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a tool, and got 0 zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product, Summ, that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age
reddit
LLM Vibe Score0
Human Vibe Score1
ExpenectThis week

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age Introduction In an era characterized by rapid technological advancements, the field of finance is undergoing a transformative journey. The emergence of financial technology, or fintech, is reshaping the way businesses manage their finances, and Chartered Accountants (CAs) are at the forefront of this evolution. In this blog post, we'll explore how CAs are embracing fintech and leveraging its potential to enhance financial management, analysis, and advisory services. Fintech's Impact on Financial Services Fintech encompasses a wide range of technologies that leverage data analytics, artificial intelligence, blockchain, and automation to improve financial services. For CAs, this means new tools to streamline processes, enhance decision-making, and offer innovative solutions to clients. Automation of Routine Tasks CAs are increasingly using automation tools to handle repetitive tasks such as data entry, reconciliations, and transaction processing. This not only reduces the risk of human error but also frees up CAs to focus on higher-value tasks like strategic planning and analysis. Advanced Data Analytics Data analytics tools enable CAs to extract meaningful insights from large volumes of financial data. These insights can help businesses identify trends, anticipate risks, and make informed decisions to drive growth. Real-Time Financial Reporting Fintech enables CAs to provide clients with real-time financial reporting, giving businesses immediate access to critical information. This enhances transparency and empowers business owners to respond quickly to changing market conditions. Enhancing Audit Efficiency Fintech tools are revolutionizing the audit process. CAs can use AI-powered algorithms to analyze vast amounts of data, detect anomalies, and identify potential instances of fraud more efficiently. Personalized Financial Planning CAs can leverage fintech to offer personalized financial planning services. With access to detailed financial data, CAs can create tailored strategies that align with a client's unique goals and circumstances. Strengthening Cybersecurity As businesses become more reliant on digital tools, cybersecurity becomes paramount. CAs are playing a critical role in advising clients on cybersecurity measures to protect sensitive financial information. Virtual CFO Services Fintech enables CAs to offer virtual CFO services to startups and small businesses. Through digital platforms, CAs can provide expert financial advice and guidance remotely, making their expertise accessible to a wider range of clients. Embracing Blockchain Technology Blockchain's potential for secure and transparent record-keeping is of interest to CAs. They can explore applications in supply chain finance, smart contracts, and even audit trail verification. Continuous Learning in Fintech CAs recognize the importance of staying updated with fintech trends. Many are investing in continuous learning to master the use of new tools and technologies that can optimize their services. Conclusion The integration of fintech into the realm of finance is reshaping the landscape in profound ways. CAs are embracing these technologies to elevate their roles from traditional number-crunchers to strategic advisors, equipped with tools that enhance efficiency, accuracy, and insight. As fintech continues to evolve, CAs will remain pivotal in guiding businesses through the ever-changing financial landscape, leveraging technology to drive growth, innovation, and success. Find the top verified CA in your City Feel free to let me know if you'd like more blogs on different topics or if you have specific requirements for the content.

The Future of AI in eCommerce Marketing: What to Expect 🚀
reddit
LLM Vibe Score0
Human Vibe Score0
McFlyAdsThis week

The Future of AI in eCommerce Marketing: What to Expect 🚀

Hey Reddit community! As we dive deeper into 2025, the integration of AI in eCommerce marketing is becoming more sophisticated and impactful. Here’s a look at where AI is headed and how it's revolutionizing the industry: Personalized Shopping Experiences: AI is enhancing personalization by analyzing consumer behavior and preferences, allowing retailers to offer tailored recommendations and promotions. This not only boosts customer satisfaction but also increases conversion rates. Chatbots and Virtual Assistants: AI-powered chatbots are becoming more intuitive and capable of handling complex queries, providing 24/7 customer support, and improving overall user experience. They’re a game-changer for eCommerce businesses looking to enhance customer engagement. Predictive Analytics: With AI, businesses can leverage predictive analytics to forecast trends, optimize inventory, and refine marketing strategies. This helps in making data-driven decisions that align with consumer demands and market dynamics. Automated Content Creation: AI tools are being used to generate product descriptions, social media posts, and even ad copy. This automation saves time and ensures consistency across marketing channels. Visual and Voice Search: AI is powering visual and voice search capabilities, making it easier for consumers to find products using images or voice commands. This technology is set to transform how users interact with eCommerce platforms. Fraud Detection: AI algorithms are improving fraud detection by analyzing transaction patterns and identifying anomalies. This is crucial for maintaining trust and security in online shopping. As AI continues to evolve, it will undoubtedly reshape the eCommerce landscape, offering new opportunities for innovation and growth. What are your thoughts on the future of AI in eCommerce marketing? Let's discuss!

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

I spent 6 months on building a web product, and got zero users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on building a web product, and got zero users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I have stuff to post on Reddit very rarely, but I share how my project is going on, random stuff, and memes on X. Just in case few might want to keep in touch 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2C products beats building B2B products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age
reddit
LLM Vibe Score0
Human Vibe Score1
ExpenectThis week

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age

The Evolution of Financial Technology: How CAs Are Embracing the Digital Age Introduction In an era characterized by rapid technological advancements, the field of finance is undergoing a transformative journey. The emergence of financial technology, or fintech, is reshaping the way businesses manage their finances, and Chartered Accountants (CAs) are at the forefront of this evolution. In this blog post, we'll explore how CAs are embracing fintech and leveraging its potential to enhance financial management, analysis, and advisory services. Fintech's Impact on Financial Services Fintech encompasses a wide range of technologies that leverage data analytics, artificial intelligence, blockchain, and automation to improve financial services. For CAs, this means new tools to streamline processes, enhance decision-making, and offer innovative solutions to clients. Automation of Routine Tasks CAs are increasingly using automation tools to handle repetitive tasks such as data entry, reconciliations, and transaction processing. This not only reduces the risk of human error but also frees up CAs to focus on higher-value tasks like strategic planning and analysis. Advanced Data Analytics Data analytics tools enable CAs to extract meaningful insights from large volumes of financial data. These insights can help businesses identify trends, anticipate risks, and make informed decisions to drive growth. Real-Time Financial Reporting Fintech enables CAs to provide clients with real-time financial reporting, giving businesses immediate access to critical information. This enhances transparency and empowers business owners to respond quickly to changing market conditions. Enhancing Audit Efficiency Fintech tools are revolutionizing the audit process. CAs can use AI-powered algorithms to analyze vast amounts of data, detect anomalies, and identify potential instances of fraud more efficiently. Personalized Financial Planning CAs can leverage fintech to offer personalized financial planning services. With access to detailed financial data, CAs can create tailored strategies that align with a client's unique goals and circumstances. Strengthening Cybersecurity As businesses become more reliant on digital tools, cybersecurity becomes paramount. CAs are playing a critical role in advising clients on cybersecurity measures to protect sensitive financial information. Virtual CFO Services Fintech enables CAs to offer virtual CFO services to startups and small businesses. Through digital platforms, CAs can provide expert financial advice and guidance remotely, making their expertise accessible to a wider range of clients. Embracing Blockchain Technology Blockchain's potential for secure and transparent record-keeping is of interest to CAs. They can explore applications in supply chain finance, smart contracts, and even audit trail verification. Continuous Learning in Fintech CAs recognize the importance of staying updated with fintech trends. Many are investing in continuous learning to master the use of new tools and technologies that can optimize their services. Conclusion The integration of fintech into the realm of finance is reshaping the landscape in profound ways. CAs are embracing these technologies to elevate their roles from traditional number-crunchers to strategic advisors, equipped with tools that enhance efficiency, accuracy, and insight. As fintech continues to evolve, CAs will remain pivotal in guiding businesses through the ever-changing financial landscape, leveraging technology to drive growth, innovation, and success. Find the top verified CA in your City Feel free to let me know if you'd like more blogs on different topics or if you have specific requirements for the content.

MMML | Deploy HuggingFace training model rapidly based on MetaSpore
reddit
LLM Vibe Score0
Human Vibe Score1
qazmkoppThis week

MMML | Deploy HuggingFace training model rapidly based on MetaSpore

A few days ago, HuggingFace announced a $100 million Series C funding round, which was big news in open source machine learning and could be a sign of where the industry is headed. Two days before the HuggingFace funding announcement, open-source machine learning platform MetaSpore released a demo based on the HuggingFace Rapid deployment pre-training model. As deep learning technology makes innovative breakthroughs in computer vision, natural language processing, speech understanding, and other fields, more and more unstructured data are perceived, understood, and processed by machines. These advances are mainly due to the powerful learning ability of deep learning. Through pre-training of deep models on massive data, the models can capture the internal data patterns, thus helping many downstream tasks. With the industry and academia investing more and more energy in the research of pre-training technology, the distribution warehouses of pre-training models such as HuggingFace and Timm have emerged one after another. The open-source community release pre-training significant model dividends at an unprecedented speed. In recent years, the data form of machine modeling and understanding has gradually evolved from single-mode to multi-mode, and the semantic gap between different modes is being eliminated, making it possible to retrieve data across modes. Take CLIP, OpenAI’s open-source work, as an example, to pre-train the twin towers of images and texts on a dataset of 400 million pictures and texts and connect the semantics between pictures and texts. Many researchers in the academic world have been solving multimodal problems such as image generation and retrieval based on this technology. Although the frontier technology through the semantic gap between modal data, there is still a heavy and complicated model tuning, offline data processing, high performance online reasoning architecture design, heterogeneous computing, and online algorithm be born multiple processes and challenges, hindering the frontier multimodal retrieval technologies fall to the ground and pratt &whitney. DMetaSoul aims at the above technical pain points, abstracting and uniting many links such as model training optimization, online reasoning, and algorithm experiment, forming a set of solutions that can quickly apply offline pre-training model to online. This paper will introduce how to use the HuggingFace community pre-training model to conduct online reasoning and algorithm experiments based on MetaSpore technology ecology so that the benefits of the pre-training model can be fully released to the specific business or industry and small and medium-sized enterprises. And we will give the text search text and text search graph two multimodal retrieval demonstration examples for your reference. Multimodal semantic retrieval The sample architecture of multimodal retrieval is as follows: Our multimodal retrieval system supports both text search and text search application scenarios, including offline processing, model reasoning, online services, and other core modules: https://preview.redd.it/mdyyv1qmdz291.png?width=1834&format=png&auto=webp&s=e9e10710794c78c64cc05adb75db385aa53aba40 Offline processing, including offline data processing processes for different application scenarios of text search and text search, including model tuning, model export, data index database construction, data push, etc. Model inference. After the offline model training, we deployed our NLP and CV large models based on the MetaSpore Serving framework. MetaSpore Serving helps us conveniently perform online inference, elastic scheduling, load balancing, and resource scheduling in heterogeneous environments. Online services. Based on MetaSpore’s online algorithm application framework, MetaSpore has a complete set of reusable online search services, including Front-end retrieval UI, multimodal data preprocessing, vector recall and sorting algorithm, AB experimental framework, etc. MetaSpore also supports text search by text and image scene search by text and can be migrated to other application scenarios at a low cost. The HuggingFace open source community has provided several excellent baseline models for similar multimodal retrieval problems, which are often the starting point for actual optimization in the industry. MetaSpore also uses the pre-training model of the HuggingFace community in its online services of searching words by words and images by words. Searching words by words is based on the semantic similarity model of the question and answer field optimized by MetaSpore, and searching images by words is based on the community pre-training model. These community open source pre-training models are exported to the general ONNX format and loaded into MetaSpore Serving for online reasoning. The following sections will provide a detailed description of the model export and online retrieval algorithm services. The reasoning part of the model is standardized SAAS services with low coupling with the business. Interested readers can refer to my previous post: The design concept of MetaSpore, a new generation of the one-stop machine learning platform. 1.1 Offline Processing Offline processing mainly involves the export and loading of online models and index building and pushing of the document library. You can follow the step-by-step instructions below to complete the offline processing of text search and image search and see how the offline pre-training model achieves reasoning at MetaSpore. 1.1.1 Search text by text Traditional text retrieval systems are based on literal matching algorithms such as BM25. Due to users’ diverse query words, a semantic gap between query words and documents is often encountered. For example, users misspell “iPhone” as “Phone,” and search terms are incredibly long, such as “1 \~ 3 months old baby autumn small size bag pants”. Traditional text retrieval systems will use spelling correction, synonym expansion, search terms rewriting, and other means to alleviate the semantic gap but fundamentally fail to solve this problem. Only when the retrieval system fully understands users’ query terms and documents can it meet users’ retrieval demands at the semantic level. With the continuous progress of pre-training and representational learning technology, some commercial search engines continue to integrate semantic vector retrieval methods based on symbolic learning into the retrieval ecology. Semantic retrieval model This paper introduces a set of semantic vector retrieval applications. MetaSpore built a set of semantic retrieval systems based on encyclopedia question and answer data. MetaSpore adopted the Sentence-Bert model as the semantic vector representation model, which fine-tunes the twin tower BERT in supervised or unsupervised ways to make the model more suitable for retrieval tasks. The model structure is as follows: The query-Doc symmetric two-tower model is used in text search and question and answer retrieval. The vector representation of online Query and offline DOC share the same vector representation model, so it is necessary to ensure the consistency of the offline DOC library building model and online Query inference model. The case uses MetaSpore’s text representation model Sbert-Chinese-QMC-domain-V1, optimized in the open-source semantically similar data set. This model will express the question and answer data as a vector in offline database construction. The user query will be expressed as a vector by this model in online retrieval, ensuring that query-doc in the same semantic space, users’ semantic retrieval demands can be guaranteed by vector similarity metric calculation. Since the text presentation model does vector encoding for Query online, we need to export the model for use by the online service. Go to the q&A data library code directory and export the model concerning the documentation. In the script, Pytorch Tracing is used to export the model. The models are exported to the “./export “directory. The exported models are mainly ONNX models used for wired reasoning, Tokenizer, and related configuration files. The exported models are loaded into MetaSpore Serving by the online Serving system described below for model reasoning. Since the exported model will be copied to the cloud storage, you need to configure related variables in env.sh. \Build library based on text search \ The retrieval database is built on the million-level encyclopedia question and answer data set. According to the description document, you need to download the data and complete the database construction. The question and answer data will be coded as a vector by the offline model, and then the database construction data will be pushed to the service component. The whole process of database construction is described as follows: Preprocessing, converting the original data into a more general JSonline format for database construction; Build index, use the same model as online “sbert-Chinese-qmc-domain-v1” to index documents (one document object per line); Push inverted (vector) and forward (document field) data to each component server. The following is an example of the database data format. After offline database construction is completed, various data are pushed to corresponding service components, such as Milvus storing vector representation of documents and MongoDB storing summary information of documents. Online retrieval algorithm services will use these service components to obtain relevant data. 1.1.2 Search by text Text and images are easy for humans to relate semantically but difficult for machines. First of all, from the perspective of data form, the text is the discrete ID type of one-dimensional data based on words and words. At the same time, images are continuous two-dimensional or three-dimensional data. Secondly, the text is a subjective creation of human beings, and its expressive ability is vibrant, including various turning points, metaphors, and other expressions, while images are machine representations of the objective world. In short, bridging the semantic gap between text and image data is much more complex than searching text by text. The traditional text search image retrieval technology generally relies on the external text description data of the image or the nearest neighbor retrieval technology and carries out the retrieval through the image associated text, which in essence degrades the problem to text search. However, it will also face many issues, such as obtaining the associated text of pictures and whether the accuracy of text search by text is high enough. The depth model has gradually evolved from single-mode to multi-mode in recent years. Taking the open-source project of OpenAI, CLIP, as an example, train the model through the massive image and text data of the Internet and map the text and image data into the same semantic space, making it possible to implement the text and image search technology based on semantic vector. CLIP graphic model The text search pictures introduced in this paper are implemented based on semantic vector retrieval, and the CLIP pre-training model is used as the two-tower retrieval architecture. Because the CLIP model has trained the semantic alignment of the twin towers’ text and image side models on the massive graphic and text data, it is particularly suitable for the text search graph scene. Due to the different image and text data forms, the Query-Doc asymmetric twin towers model is used for text search image retrieval. The image-side model of the twin towers is used for offline database construction, and the text-side model is used for the online return. In the final online retrieval, the database data of the image side model will be searched after the text side model encodes Query, and the CLIP pre-training model guarantees the semantic correlation between images and texts. The model can draw the graphic pairs closer in vector space by pre-training on a large amount of visual data. Here we need to export the text-side model for online MetaSpore Serving inference. Since the retrieval scene is based on Chinese, the CLIP model supporting Chinese understanding is selected. The exported content includes the ONNX model used for online reasoning and Tokenizer, similar to the text search. MetaSpore Serving can load model reasoning through the exported content. Build library on Image search You need to download the Unsplash Lite library data and complete the construction according to the instructions. The whole process of database construction is described as follows: Preprocessing, specify the image directory, and then generate a more general JSOnline file for library construction; Build index, use OpenAI/Clip-Vit-BASE-Patch32 pre-training model to index the gallery, and output one document object for each line of index data; Push inverted (vector) and forward (document field) data to each component server. Like text search, after offline database construction, relevant data will be pushed to service components, called by online retrieval algorithm services to obtain relevant data. 1.2 Online Services The overall online service architecture diagram is as follows: &#x200B; https://preview.redd.it/nz8zrbbpdz291.png?width=1280&format=png&auto=webp&s=28dae7e031621bc8819519667ed03d8d085d8ace Multi-mode search online service system supports application scenarios such as text search and text search. The whole online service consists of the following parts: Query preprocessing service: encapsulate preprocessing logic (including text/image, etc.) of pre-training model, and provide services through gRPC interface; Retrieval algorithm service: the whole algorithm processing link includes AB experiment tangent flow configuration, MetaSpore Serving call, vector recall, sorting, document summary, etc.; User entry service: provides a Web UI interface for users to debug and track down problems in the retrieval service. From a user request perspective, these services form invocation dependencies from back to front, so to build up a multimodal sample, you need to run each service from front to back first. Before doing this, remember to export the offline model, put it online and build the library first. This article will introduce the various parts of the online service system and make the whole service system step by step according to the following guidance. See the ReadME at the end of this article for more details. 1.2.1 Query preprocessing service Deep learning models tend to be based on tensors, but NLP/CV models often have a preprocessing part that translates raw text and images into tensors that deep learning models can accept. For example, NLP class models often have a pre-tokenizer to transform text data of string type into discrete tensor data. CV class models also have similar processing logic to complete the cropping, scaling, transformation, and other processing of input images through preprocessing. On the one hand, considering that this part of preprocessing logic is decoupled from tensor reasoning of the depth model, on the other hand, the reason of the depth model has an independent technical system based on ONNX, so MetaSpore disassembled this part of preprocessing logic. NLP pretreatment Tokenizer has been integrated into the Query pretreatment service. MetaSpore dismantlement with a relatively general convention. Users only need to provide preprocessing logic files to realize the loading and prediction interface and export the necessary data and configuration files loaded into the preprocessing service. Subsequent CV preprocessing logic will also be integrated in this manner. The preprocessing service currently provides the gRPC interface invocation externally and is dependent on the Query preprocessing (QP) module in the retrieval algorithm service. After the user request reaches the retrieval algorithm service, it will be forwarded to the service to complete the data preprocessing and continue the subsequent processing. The ReadMe provides details on how the preprocessing service is started, how the preprocessing model exported offline to cloud storage enters the service, and how to debug the service. To further improve the efficiency and stability of model reasoning, MetaSpore Serving implements a Python preprocessing submodule. So MetaSpore can provide gRPC services through user-specified preprocessor.py, complete Tokenizer or CV-related preprocessing in NLP, and translate requests into a Tensor that deep models can handle. Finally, the model inference is carried out by MetaSpore, Serving subsequent sub-modules. Presented here on the lot code: https://github.com/meta-soul/MetaSpore/compare/add\python\preprocessor 1.2.2 Retrieval algorithm services Retrieval algorithm service is the core of the whole online service system, which is responsible for the triage of experiments, the assembly of algorithm chains such as preprocessing, recall, sorting, and the invocation of dependent component services. The whole retrieval algorithm service is developed based on the Java Spring framework and supports multi-mode retrieval scenarios of text search and text search graph. Due to good internal abstraction and modular design, it has high flexibility and can be migrated to similar application scenarios at a low cost. Here’s a quick guide to configuring the environment to set up the retrieval algorithm service. See ReadME for more details: Install dependent components. Use Maven to install the online-Serving component Search for service configurations. Copy the template configuration file and replace the MongoDB, Milvus, and other configurations based on the development/production environment. Install and configure Consul. Consul allows you to synchronize the search service configuration in real-time, including cutting the flow of experiments, recall parameters, and sorting parameters. The project’s configuration file shows the current configuration parameters of text search and text search. The parameter modelName in the stage of pretreatment and recall is the corresponding model exported in offline processing. Start the service. Once the above configuration is complete, the retrieval service can be started from the entry script. Once the service is started, you can test it! For example, for a user with userId=10 who wants to query “How to renew ID card,” access the text search service. 1.2.3 User Entry Service Considering that the retrieval algorithm service is in the form of the API interface, it is difficult to locate and trace the problem, especially for the text search image scene can intuitively display the retrieval results to facilitate the iterative optimization of the retrieval algorithm. This paper provides a lightweight Web UI interface for text search and image search, a search input box, and results in a display page for users. Developed by Flask, the service can be easily integrated with other retrieval applications. The service calls the retrieval algorithm service and displays the returned results on the page. It’s also easy to install and start the service. Once you’re done, go to http://127.0.0.1:8090 to see if the search UI service is working correctly. See the ReadME at the end of this article for details. Multimodal system demonstration The multimodal retrieval service can be started when offline processing and online service environment configuration have been completed following the above instructions. Examples of textual searches are shown below. Enter the entry of the text search map application, enter “cat” first, and you can see that the first three digits of the returned result are cats: https://preview.redd.it/d7syq47rdz291.png?width=1280&format=png&auto=webp&s=b43df9abd380b7d9a52e3045dd787f4feeb69635 If you add a color constraint to “cat” to retrieve “black cat,” you can see that it does return a black cat: &#x200B; https://preview.redd.it/aa7pxx8tdz291.png?width=1280&format=png&auto=webp&s=e3727c29d1bde6eea2e1cccf6c46d3cae3f4750e Further, strengthen the constraint on the search term, change it to “black cat on the bed,” and return results containing pictures of a black cat climbing on the bed: &#x200B; https://preview.redd.it/2mw4qpjudz291.png?width=1280&format=png&auto=webp&s=1cf1db667892b9b3a40451993680fbd6980b5520 The cat can still be found through the text search system after the color and scene modification in the above example. Conclusion The cutting-edge pre-training technology can bridge the semantic gap between different modes, and the HuggingFace community can greatly reduce the cost for developers to use the pre-training model. Combined with the technological ecology of MetaSpore online reasoning and online microservices provided by DMetaSpore, the pre-training model is no longer mere offline dabbling. Instead, it can truly achieve end-to-end implementation from cutting-edge technology to industrial scenarios, fully releasing the dividends of the pre-training large model. In the future, DMetaSoul will continue to improve and optimize the MetaSpore technology ecosystem: More automated and wider access to HuggingFace community ecology. MetaSpore will soon release a common model rollout mechanism to make HuggingFace ecologically accessible and will later integrate preprocessing services into online services. Multi-mode retrieval offline algorithm optimization. For multimodal retrieval scenarios, MetaSpore will continuously iteratively optimize offline algorithm components, including text recall/sort model, graphic recall/sort model, etc., to improve the accuracy and efficiency of the retrieval algorithm. For related code and reference documentation in this article, please visit: https://github.com/meta-soul/MetaSpore/tree/main/demo/multimodal/online Some images source: https://github.com/openai/CLIP/raw/main/CLIP.png https://www.sbert.net/examples/training/sts/README.html

Let’s Build One Person Business Using 100% AI
reddit
LLM Vibe Score0
Human Vibe Score1
AssistanceOk2217This week

Let’s Build One Person Business Using 100% AI

AI made it possible for 9-to-5 workers to start a one-person business without quitting their jobs. Full Article https://preview.redd.it/tynb9y6z695d1.png?width=1309&format=png&auto=webp&s=b490d3676a63adcc01faff8c476056cb7d420022 https://i.redd.it/9x3okti0795d1.gif The Opportunities for Starting a Business ○ There are huge opportunities to start your own business by leveraging valuable skills to attract paying audiences. ○ New software and AI platforms make it easier to distribute products/services and automate tasks that were previously time-consuming. Our One Person Book Publication House ○ This article explores building a one-person AI-powered business focused on publishing books. ○ Users input data on a topic, and AI generates a comprehensive book structure and content based on that. ○ The generated content can be formatted, designed, and published digitally or in print easily. Why Read This Article? ○ It presents an innovative AI-powered approach to streamline the book publishing process. ○ It provides technical implementation details using LLM, Python and the Streamlit library as a reference. ○ It highlights AI's potential in automating creative tasks like writing and content creation. Approaching the One Person Business ○ Reflect on areas where you overcame personal struggles and gained valuable skills. ○ Leverage that expertise to build an AI business serving others facing similar obstacles. ○ Use AI tools to create content, automate processes, and efficiently scale your offerings. The Publication Business Idea ○ Focus on writing and publishing small books using AI writing assistants. ○ AI can streamline research, writing drafts, outlines, and ideas across genres. ○ Concentrate efforts on editing, formatting, and marketing while AI handles writing. The Book Generation Process ○ Users input structured topic data like outlines, key points, and references. ○ Advanced AI language models generate flowing book content from that data. ○ Minimal human effort is needed beyond initial inputs and refinement. ○ AI systems automatically handle formatting, design, and publishing. Technical Implementation ○ Includes a Book class to represent a book's hierarchical structure in Python. ○ Functions to generate book structures and section content using AI models. ○ Integrates with a Streamlit app for user input and output. ○ Allows downloading the final book in Markdown format. Closing Thoughts ○ This AI-powered approach makes book writing and publishing more accessible to individuals. ○ AI handles the heavy lifting, with humans providing quality control through editing. ○ It opens up possibilities for innovative knowledge sharing as technology evolves.

Let’s Build One Person Business Using 100% AI
reddit
LLM Vibe Score0
Human Vibe Score1
AssistanceOk2217This week

Let’s Build One Person Business Using 100% AI

AI made it possible for 9-to-5 workers to start a one-person business without quitting their jobs. Full Article https://preview.redd.it/tynb9y6z695d1.png?width=1309&format=png&auto=webp&s=b490d3676a63adcc01faff8c476056cb7d420022 https://i.redd.it/9x3okti0795d1.gif The Opportunities for Starting a Business ○ There are huge opportunities to start your own business by leveraging valuable skills to attract paying audiences. ○ New software and AI platforms make it easier to distribute products/services and automate tasks that were previously time-consuming. Our One Person Book Publication House ○ This article explores building a one-person AI-powered business focused on publishing books. ○ Users input data on a topic, and AI generates a comprehensive book structure and content based on that. ○ The generated content can be formatted, designed, and published digitally or in print easily. Why Read This Article? ○ It presents an innovative AI-powered approach to streamline the book publishing process. ○ It provides technical implementation details using LLM, Python and the Streamlit library as a reference. ○ It highlights AI's potential in automating creative tasks like writing and content creation. Approaching the One Person Business ○ Reflect on areas where you overcame personal struggles and gained valuable skills. ○ Leverage that expertise to build an AI business serving others facing similar obstacles. ○ Use AI tools to create content, automate processes, and efficiently scale your offerings. The Publication Business Idea ○ Focus on writing and publishing small books using AI writing assistants. ○ AI can streamline research, writing drafts, outlines, and ideas across genres. ○ Concentrate efforts on editing, formatting, and marketing while AI handles writing. The Book Generation Process ○ Users input structured topic data like outlines, key points, and references. ○ Advanced AI language models generate flowing book content from that data. ○ Minimal human effort is needed beyond initial inputs and refinement. ○ AI systems automatically handle formatting, design, and publishing. Technical Implementation ○ Includes a Book class to represent a book's hierarchical structure in Python. ○ Functions to generate book structures and section content using AI models. ○ Integrates with a Streamlit app for user input and output. ○ Allows downloading the final book in Markdown format. Closing Thoughts ○ This AI-powered approach makes book writing and publishing more accessible to individuals. ○ AI handles the heavy lifting, with humans providing quality control through editing. ○ It opens up possibilities for innovative knowledge sharing as technology evolves.

Building a No-Code AI Customer Service Tool While Working 9-5 | All real - No BS
reddit
LLM Vibe Score0
Human Vibe Score1
Content_Limit_9723This week

Building a No-Code AI Customer Service Tool While Working 9-5 | All real - No BS

I want to share my journey of building Chaterimo, my first revenue-generating side project that I've been working on for the past 1.5 years alongside my day job. What started as a solution to make AI chatbots more accessible has grown to over 300 signups, 30 paying customers, and 50,000+ customer queries handled. The Problem I Wanted to Solve: It started with my father's business struggling with customer service - hiring staff was expensive and they would eventually leave, creating a constant cycle of training new people. I decided to help by building a livechat chatbot powered by AI to handle customer queries. The first version was basic (running on ChatGPT-3 with 4k tokens), but it worked! Seeing its success at my father's business, I realized this could help many other businesses too. As I kept improving it and adding features, I expanded to focus on e-commerce stores facing similar challenges. What Makes Chaterimo Different: True no-code setup: Install and run in seconds Choice of AI Models: ChatGPT by default, with options for Claude and the latest Gemini Flexible API Integration: Bring your own API keys for cheaper, unlimited messaging Smart Context Understanding: Can search Google or scan the current webpage to provide relevant answers Lead Generation: Capture and manage potential customer information Rich Integrations: Works with Shopify, Facebook Messenger, and Make for automation Customizable Bot Personality: Edit your chatbot's role and behavior through system prompts The Journey: This is my first side project that's actually generating revenue ($500+ MRR), unlike my previous "just for fun" projects. The past 1.5 years have been a learning experience, balancing development with a full-time job. What started as a simple idea has evolved based on real user feedback and needs. Current Metrics: 300+ total signups 30 paying customers 50,000+ customer queries successfully handled by AI $500+ monthly recurring revenue All while maintaining a 9-5 job Some Things I've Learned: Focus on making things simpler, not adding more features Listen to users - they'll tell you what they really need Flexibility matters - letting users use their own API keys was a game-changer Building something you believe in makes all the difference I'm still actively improving Chaterimo based on feedback. If you're running a website or e-commerce store and want to try it out, I'd love to hear your thoughts. What's Next: I'm focused on making the onboarding even smoother and adding more customization options while keeping the core simplicity that makes Chaterimo work. Would love to hear your thoughts or answer any questions! Has anyone else built successful side projects while working full-time? What were your biggest learnings?

How me and my team made 15+ apps and not made a single sale in 2023
reddit
LLM Vibe Score0
Human Vibe Score0.818
MichaelbetterecycleThis week

How me and my team made 15+ apps and not made a single sale in 2023

Hey, my name is Michael, I am in Auckland NZ. This year was the official beginning of my adult life. I graduated from university and started a full-time job. I’ve also really dug into indiehacking/bootstrapping and started 15 projects (and it will be at least 17 before the year ends). I think I’ve learned a lot but I consciously repeated mistakes. Upto (Nov) Discord Statuses + Your Location + Facebook Poke https://preview.redd.it/4nqt7tp2tf5c1.png?width=572&format=png&auto=webp&s=b0223484bc54b45b5c65e0b1afd0dc52f9c02ad1 This was the end of uni, I often messaged (and got messaged) requests of status and location to (and from my) friends. I thought, what if we make a social app that’s super basic and all it does is show you where your friends are? To differentiate from snap maps and others we wanted something with more privacy where you select the location. However, never finished the codebase or launched it. This is because I slowly started to realize that B2C (especially social networks) are way too hard to make into an actual business and the story with Fistbump would repeat itself. However, this decision not to launch it almost launched a curse on our team. From that point, we permitted ourselves to abandon projects even before launching. Lessons: Don’t do social networks if your goal is 10k MRR ASAP. If you build something to 90% competition ship it or you will think it’s okay to abandon projects Insight Bites (Nov) Youtube Summarizer Extension &#x200B; https://preview.redd.it/h6drqej4tf5c1.jpg?width=800&format=pjpg&auto=webp&s=0f211456c390ac06f4fcb54aa51f9d50b0826658 Right after Upto, we started ideating and conveniently the biggest revolution in the recent history of tech was released → GPT. We instantly began ideating. The first problem we chose to use AI for is to summarize YouTube videos. Comical. Nevertheless, I am convinced we have had the best UX because you could right-click on a video to get a slideshow of insights instead of how everyone else did it. We dropped it because there was too much competition and unit economics didn’t work out (and it was a B2C). PodPigeon (Dec) Podcast → Tweet Threads https://preview.redd.it/0ukge245tf5c1.png?width=2498&format=png&auto=webp&s=23303e1cab330578a3d25cd688fa67aa3b97fb60 Then we thought, to make unit economics work we need to make this worthwhile for podcasters. This is when I got into Twitter and started seeing people summarize podcasts. Then I thought, what if we make something that converts a podcast into tweets? This was probably one of the most important projects because it connected me with Jason and Jonaed, both of whom I regularly stay in contact with and are my go-to experts on ideas related to content creation. Jonaed was even willing to buy Podpigeon and was using it on his own time. However, the unit economics still didn’t work out (and we got excited about other things). Furthermore, we got scared of the competition because I found 1 - 2 other people who did similar things poorly. This was probably the biggest mistake we’ve made. Very similar projects made 10k MRR and more, launching later than we did. We didn’t have a coherent product vision, we didn’t understand the customer well enough, and we had a bad outlook on competition and a myriad of other things. Lessons: I already made another post about the importance of outlook on competition. Do not quit just because there are competitors or just because you can’t be 10x better. Indiehackers and Bootstrappers (or even startups) need to differentiate in the market, which can be via product (UX/UI), distribution, or both. Asking Ace Intro.co + Crowdsharing &#x200B; https://preview.redd.it/0hu2tt16tf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3d397568ef2331e78198d64fafc1a701a3e75999 As I got into Twitter, I wanted to chat with some people I saw there. However, they were really expensive. I thought, what if we made some kind of crowdfunding service for other entrepreneurs to get a private lecture from their idols? It seemed to make a lot of sense on paper. It was solving a problem (validated via the fact that Intro.co is a thing and making things cheaper and accessible is a solid ground to stand on), we understood the market (or so we thought), and it could monetize relatively quickly. However, after 1-2 posts on Reddit and Indiehackers, we quickly learned three things. Firstly, no one cares. Secondly, even if they do, they think they can get the same information for free online. Thirdly, the reasons before are bad because for the first point → we barely talked to people, and for the second people → we barely talked to the wrong people. However, at least we didn’t code anything this time and tried to validate via a landing page. Lessons Don’t give up after 1 Redditor says “I don’t need this” Don’t be scared to choose successful people as your audience. Clarito Journaling with AI analyzer https://preview.redd.it/8ria2wq6tf5c1.jpg?width=1108&format=pjpg&auto=webp&s=586ec28ae75003d9f71b4af2520b748d53dd2854 Clarito is a classic problem all amateur entrepreneurs have. It’s where you lie to yourself that you have a real problem and therefore is validated but when your team asks you how much you would pay you say I guess you will pay, maybe, like 5 bucks a month…? Turns out, you’d have to pay me to use our own product lol. We sent it off to a few friends and posted on some forums, but never really got anything tangible and decided to move away. Honestly, a lot of it is us in our own heads. We say the market is too saturated, it’ll be hard to monetize, it’s B2C, etc. Lessons: You use the Mom Test on other people. You have to do it yourself as well. However, recognizing that the Mom Test requires a lot of creativity in its investigation because knowing what questions to ask can determine the outcome of the validation. I asked myself “Do I journal” but I didn’t ask myself “How often do I want GPT to chyme in on my reflections”. Which was practically never. That being said I think with the right audience and distribution, this product can work. I just don’t know (let alone care) about the audience that much (and I thought I was one of them)/ Horns & Claw Scrapes financial news texts you whether you should buy/sell the stock (news sentiment analysis) &#x200B; https://preview.redd.it/gvfxdgc7tf5c1.jpg?width=1287&format=pjpg&auto=webp&s=63977bbc33fe74147b1f72913cefee4a9ebec9c2 This one we didn’t even bother launching. Probably something internal in the team and also seemed too good to be true (because if this works, doesn’t that just make us ultra-rich fast?). I saw a similar tool making 10k MRR so I guess I was wrong. Lessons: This one was pretty much just us getting into our heads. I declared that without an audience it would be impossible to ship this product and we needed to start a YouTube channel. Lol, and we did. And we couldn’t even film for 1 minute. I made bold statements like “We will commit to this for at least 1 year no matter what”. Learnery Make courses about any subject https://preview.redd.it/1nw6z448tf5c1.jpg?width=1112&format=pjpg&auto=webp&s=f2c73e8af23b0a6c3747a81e785960d4004feb48 This is probably the most “successful” project we’ve made. It grew from a couple of dozen to a couple of hundred users. It has 11 buy events for $9.99 LTD (we couldn’t be bothered connecting Stripe because we thought no one would buy it anyway). However what got us discouraged from seriously pursuing it more is, that this has very low defensibility, “Why wouldn’t someone just use chatGPT?” and it’s B2C so it’s hard to monetize. I used it myself for a month or so but then stopped. I don’t think it’s the app, I think the act of learning a concept from scratch isn’t something you do constantly in the way Learnery delivers it (ie course). I saw a bunch of similar apps that look like Ass make like 10k MRR. Lessons: Don’t do B2C, or if you do, do it properly Don’t just Mixpanel the buy button, connect your Stripe otherwise, it doesn’t feel real and you won’t get momentum. I doubt anyone (even me) will make this mistake again. I live in my GPT bubble where I make assumptions that everyone uses GPT the same way and as much as I do. In reality, the argument that this has low defensibility against GPT is invalid. Platforms that deliver a differentiated UX from ChatGPT to audiences who are not tightly integrated into the habit of using ChatGPT (which is like - everyone except for SOME tech evangelists). CuriosityFM Make podcasts about any subject https://preview.redd.it/zmosrcp8tf5c1.jpg?width=638&format=pjpg&auto=webp&s=d04ddffabef9050050b0d87939273cc96a8637dc This was our attempt at making Learnery more unique and more differentiated from chatGPT. We never really launched it. The unit economics didn’t work out and it was actually pretty boring to listen to, I don’t think I even fully listened to one 15-minute episode. I think this wasn’t that bad, it taught us more about ElevenLabs and voice AI. It took us maybe only 2-3 days to build so I think building to learn a new groundbreaking technology is fine. SleepyTale Make children’s bedtime stories https://preview.redd.it/14ue9nm9tf5c1.jpg?width=807&format=pjpg&auto=webp&s=267e18ec6f9270e6d1d11564b38136fa524966a1 My 8-year-old sister gave me that idea. She was too scared of making tea and I was curious about how she’d react if she heard a bedtime story about that exact scenario with the moral that I wanted her to absorb (which is that you shouldn’t be scared to try new things ie stop asking me to make your tea and do it yourself, it’s not that hard. You could say I went full Goebbels on her). Zane messaged a bunch of parents on Facebook but no one really cared. We showed this to one Lady at the place we worked from at Uni and she was impressed and wanted to show it to her kids but we already turned off our ElevenLabs subscription. Lessons: However, the truth behind this is beyond just “you need to be able to distribute”. It’s that you have to care about the audience. I don’t particularly want to build products for kids and parents. I am far away from that audience because I am neither a kid anymore nor going to be a parent anytime soon, and my sister still asked me to make her tea so the story didn’t work. I think it’s important to ask yourself whether you care about the audience. The way you answer that even when you are in full bias mode is, do you engage with them? Are you interested in what’s happening in their communities? Are you friends with them? Etc. User Survey Analyzer Big User Survey → GPT → Insights Report Me and my coworker were chatting about AI when he asked me to help him analyze a massive survey for him. I thought that was some pretty decent validation. Someone in an actual company asking for help. Lessons Market research is important but moving fast is also important. Ie building momentum. Also don’t revolve around 1 user. This has been a problem in multiple projects. Finding as many users as possible in the beginning to talk to is key. Otherwise, you are just waiting for 1 person to get back to you. AutoI18N Automated Internationalization of the codebase for webapps This one I might still do. It’s hard to find a solid distribution strategy. However, the idea came from me having to do it at my day job. It seems a solid problem. I’d say it’s validated and has some good players already. The key will be differentiation via the simplicity of UX and distribution (which means a slightly different audience). In the backlog for now because I don’t care about the problem or the audience that much. Documate - Part 1 Converts complex PDFs into Excel https://preview.redd.it/8b45k9katf5c1.jpg?width=1344&format=pjpg&auto=webp&s=57324b8720eb22782e28794d2db674b073193995 My mom needed to convert a catalog of furniture into an inventory which took her 3 full days of data entry. I automated it for her and thought this could have a big impact but there was no distribution because there was no ICP. We tried to find the ideal customers by talking to a bunch of different demographics but I flew to Kazakhstan for a holiday and so this kind of fizzled out. I am not writing this blog post linearity, this is my 2nd hour and I am tired and don’t want to finish this later so I don’t even know what lessons I learned. Figmatic Marketplace of high-quality Figma mockups of real apps https://preview.redd.it/h13yv45btf5c1.jpg?width=873&format=pjpg&auto=webp&s=aaa2896aeac2f22e9b7d9eed98c28bb8a2d2cdf1 This was a collab between me and my friend Alex. It was the classic Clarito where we both thought we had this problem and would pay to fix it. In reality, this is a vitamin. Neither I, nor I doubt Alex have thought of this as soon as we bought the domain. We posted it on Gumroad, sent it to a bunch of forums, and called it a day. Same issue as almost all the other ones. No distribution strategy. However, apps like Mobin show us that this concept is indeed profitable but it takes time. It needs SEO. It needs a community. None of those things, me and Alex had or was interested in. However shortly after HTML → Figma came out and it’s the best plugin. Maybe that should’ve been the idea. Podcast → Course Turns Podcaster’s episodes into a course This one I got baited by Jason :P I described to him the idea of repurposing his content for a course. He told me this was epic and he would pay. Then after I sent him the demo, he never checked it out. Anyhow during the development, we realized that doesn’t actually work because A podcast doesn’t have the correct format for the course, the most you can extract are concepts and ideas, seldom explanations. Most creators want video-based courses to be hosted on Kajabi or Udemy Another lesson is that when you pitch something to a user, what you articulate is a platform or a process, they imagine an outcome. However, the end result of your platform can be a very different outcome to what they had in mind and there is even a chance that what they want is not possible. You need to understand really well what the outcome looks like before you design the process. This is a classic problem where we thought of the solution before the problem. Yes, the problem exists. Podcasters want to make courses. However, if you really understand what they want, you can see how repurposing a podcast isn’t the best way to get there. However I only really spoke to 1-2 podcasters about this so making conclusions is dangerous for this can just be another asking ace mistake with the Redditor. Documate Part 2 Same concept as before but now I want to run some ads. We’ll see what happens. https://preview.redd.it/xb3npj0ctf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3cd4884a29fd11d870d010a2677b585551c49193 In conclusion https://preview.redd.it/2zrldc9dtf5c1.jpg?width=1840&format=pjpg&auto=webp&s=2b3105073e752ad41c23f205dbd1ea046c1da7ff It doesn’t actually matter that much whether you choose to do a B2C, or a social network or focus on growing your audience. All of these can make you successful. What’s important is that you choose. If I had to summarize my 2023 in one word it’s indecision. Most of these projects succeeded for other people, nothing was as fundamentally wrong about them as I proclaimed. In reality that itself was an excuse. New ideas seduce, and it is a form of discipline to commit to a single project for a respectful amount of time. https://preview.redd.it/zy9a2vzdtf5c1.jpg?width=1456&format=pjpg&auto=webp&s=901c621227bba0feb4efdb39142f66ab2ebb86fe Distribution is not just posting on Indiehackers and Reddit. It’s an actual strategy and you should think of it as soon as you think of the idea, even before the Figma designs. I like how Denis Shatalin taught me. You have to build a pipeline. That means a reliable way to get leads, launch campaigns at them, close deals, learn from them, and optimize. Whenever I get an idea now I always try to ask myself “Where can I find 1000s leads in one day?” If there is no good answer, this is not a good project to do now. &#x200B; https://preview.redd.it/2boh3fpetf5c1.jpg?width=1456&format=pjpg&auto=webp&s=1c0d5d7b000716fcbbb00cbad495e8b61e25be66 Talk to users before doing anything. Jumping on designing and coding to make your idea a reality is a satisfying activity in the short term. Especially for me, I like to create for the sake of creation. However, it is so important to understand the market, understand the audience, understand the distribution. There are a lot of things to understand before coding. https://preview.redd.it/lv8tt96ftf5c1.jpg?width=1456&format=pjpg&auto=webp&s=6c8735aa6ad795f216ff9ddfa2341712e8277724 Get out of your own head. The real reason we dropped so many projects is that we got into our own heads. We let the negative thoughts creep in and kill all the optimism. I am really good at coming up with excuses to start a project. However, I am equally as good at coming up with reasons to kill a project. And so you have this yin and yang of starting and stopping. Building momentum and not burning out. I can say with certainty my team ran out of juice this year. We lost momentum so many times we got burnt out towards the end. Realizing that the project itself has momentum is important. User feedback and sales bring momentum. Building also creates momentum but unless it is matched with an equal force of impact, it can stomp the project down. That is why so many of our projects died quickly after we launched. The smarter approach is to do things that have a low investment of momentum (like talking to users) but result in high impact (sales or feedback). Yes, that means the project can get invalidated which makes it more short-lived than if we built it first, but it preserves team life energy. At the end of 2023 here is a single sentence I am making about how I think one becomes a successful indiehacker. One becomes a successful Indiehacker when one starts to solve pain-killer problems in the market they understand, for an audience they care about and consistently engage with for a long enough timeframe. Therefore an unsuccessful Indiehacker in a single sentence is An unsuccessful Indiehacker constantly enters new markets they don’t understand to build solutions for people whose problems they don’t care about, in a timeframe that is shorter than than the time they spent thinking about distribution. However, an important note to be made. Life is not just about indiehacking. It’s about learning and having fun. In the human world, the best journey isn’t the one that gets you the fastest to your goals but the one you enjoy the most. I enjoyed making those silly little projects and although I do not regret them, I will not repeat the same mistakes in 2024. But while it’s still 2023, I have 2 more projects I want to do :) EDIT: For Devs, frontend is always react with vite (ts) and backend is either node with express (ts) or python. For DB either Postgres or mongo (usually Prisma for ORM). For deployment all of it is on AWS (S3, EC2). In terms of libraries/APIs Whisper.cpp is best open source for transcription Obviously the gpt apis Eleven labs for voice related stuff And other random stuff here and there

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I very rarely have stuff to post on Reddit, but I share how my project is going on, just random stuff, and memes on X. In case few might want to keep up 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2B products beats building B2C products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

What are Boilerplates?
reddit
LLM Vibe Score0
Human Vibe Score1
Inner_Lengthiness697This week

What are Boilerplates?

What are Boilerplates? Boilerplate originally referred to the rolled steel used to make boilers for steam engines in the 19th century. Over time, the term evolved to describe any standardized piece of text or code that can be reused without significant changes. Interest in SaaS has been on the rise, and many more people now want to build products. However, building products from scratch takes a lot of time, and it can be extremely frustrating. Enter SaaS Boilerplates With the standardization of stacks and basic systems that govern SaaS tools, it has become evident that there was a need, and the time was ripe for SaaS Boilerplates. SaaS Boilerplates come with landing pages, website components, authentication modules, payment modules, and various other standard features that can save developers a significant amount of time and cost. The market is flooded with Boilerplates for various tech stacks, such as NextJS, Laravel, Swift, NuxtJS, and so forth. Pros and Cons of Boilerplates Pros Save a significant amount of time and money Reduce frustration for developers as the redundant tasks are taken care of Boilerplates often follow best practices For anywhere between $49 and $299, they provide terrific value for those looking to build something very quickly Most importantly, Boilerplates also enable aspiring founders and builders with limited technical resources or abilities to ship their products faster and more cheaply. They are beacons of hope for non-technical founders looking to build a product quickly. Cons Limited flexibility May become outdated fairly quickly Setting them up still requires time Similar landing pages and design themes can make the product look like a clone Marc Lou’s Shipfast For most of us, Marc Lou popularized the idea of SaaS Boilerplate. Marc Lou launched Shipfast in August 2023. He had built 27 projects prior to this and Shipfast was nothing but all his basic code organised properly. At that time, there were no solid NextJS boilerplates, and Shipfast just took off. He got traction via Product Hunt, Twitter and Hacker News and soon Shipfast went viral. Shipfast now generates $130K/mo, just 9 months after its launch. Marc has been building Shipfast in public, which has led to a lot of interest in SaaS Boilerplates. The market is now flooded with boilerplates for every major tech stack. Marc reaped the benefits of the first mover’s advantage as well as the social proof via his Shipfast community. I don’t think any other boilerplates are as successful as Shipfast, but there are quite a few good ones out there. Shipixen* has grossed over $20K in the 5 months Makerkit* does \~$3500/mo Moreover, there are many open-source boilerplates available for popular stacks such as NextJS. The Evolution of Boilerplates Boilerplates are quickly turning into no-code/low-code code generation tools. For instance, Shipixen allows you to generate custom code for landing pages, waitlist pages and blogs using a simple User Interface. Boilerplates are perfectly posied to sit between code and no-code. Allow the flexibility of code with the interface of a no-code tool — that will be the core value proposition of SaaS boilerplates. Should you build a Boilerplate? Well, the market is flooded, but I believe there’s still an opportunity to leverage boilerplates. You can build boilerplates for certain types of apps or tools, such as Chrome extensions Boilerplates can act as a great lead funnel for building out a great productized services business No-code/low-code code generation boilerplates can become a big thing if you can help build complex tools Niche tech stack boilerplates may still be lucrative Known strategies for successfully building a boilerplate 👇🏻 Shipfast thrives because of social proof and community SaaSRock generates most of its traffic from its Gumroad listings and blogs Usenextbase and Shipixen are being built in public Many boilerplates start with waitlists They have a very clear value proposition around saving time and cost Design & No-Code Boilerplates Here is the corrected version with improved grammar and clarity: While SaaS (code) boilerplates have become fairly popular, other types of boilerplates are emerging in the market, such as design boilerplates and no-code boilerplates. To be honest, design boilerplates have been around for a while. You will find numerous landing page packs, component libraries, and so forth. Makers are now building kits that leverage standard libraries and technologies such as Tailwind CSS, Daisy UI, and more. Nick Buzz from the famous baked.design has this *50 Landing Page Design Kit* in Tailwind CSS & Figma which is wildly popular. Lastly, there is a trend of no-code boilerplates as well. Mohit is building a Bubble Boilerplate for the popular no-code platform — Bubble. All in all, I think that people want to build products and build them fast. Boilerplates help them save a significant amount of time and cost. More importantly, boilerplates are impulse purchases for people who have not shipped but who want to ship. Introducing BuilderKit.ai We have been building AI SaaS tools for quite a while now. 10+ products across text, image, speech, RAG — we have built em all. We figured that it seems easy but actually building these so called AI Wrappers can be time consuming and frustrating — there is a lot of nuance to it. So we built BuidlerKit.ai — a NextJS SaaS Boilerpalte It takes care of everything from landing pages, authentication, dashboarding, emails, SEO to payments — everything that you need to build your tool. It also comes with 8+ production-ready apps. Moreover, the BuilderKit community is an exclusive community of AI SaaS builders (Pro Only Access) The Pre Orders are now live at https://www.builderkit.ai (First 100 Customers get $100 Off — I think we have already done \~20 odd orders since the announcement yesterday, Grab your seat asap!) Starter Plan $49, Pro Plan @ $99

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.
reddit
LLM Vibe Score0
Human Vibe Score0.667
GDbuildsGDThis week

I spent 6 months on a web app as a side project, and got 0 users. Here is my story.

Edit Thank you all so much for your time reading my story. Your support, feedback, criticism, and skepticism; all helped me a lot, and I couldn't appreciate it enough \^\_\^ I very rarely have stuff to post on Reddit, but I share how my project is going on, just random stuff, and memes on X. In case few might want to keep up 👀 TL;DR I spent 6 months on a tool that currently has 0 users. Below is what I learned during my journey, sharing because I believe most mistakes are easily avoidable. Do not overestimate your product and assume it will be an exception to fundamental principles. Principles are there for a reason. Always look for validation before you start. Avoid building products with a low money-to-effort ratio/in very competitive fields. Unless you have the means, you probably won't make it. Pick a problem space, pick your target audience, and talk to them before thinking about a solution. Identify and match their pain points. Only then should you think of a solution. If people are not overly excited or willing to pay in advance for a discounted price, it might be a sign to rethink. Sell one and only one feature at a time. Avoid everything else. If people don't pay for that one core feature, no secondary feature will change their mind. Always spend twice as much time marketing as you do building. You will not get users if they don't know it exists. Define success metrics ("1000 users in 3 months" or "$6000 in the account at the end of 6 months") before you start. If you don't meet them, strongly consider quitting the project. If you can't get enough users to keep going, nothing else matters. VALIDATION, VALIDATION, VALIDATION. Success is not random, but most of our first products will not make a success story. Know when to admit failure, and move on. Even if a product of yours doesn't succeed, what you learned during its journey will turn out to be invaluable for your future. My story So, this is the story of a product that I’ve been working on for the last 6 months. As it's the first product I’ve ever built, after watching you all from the sidelines, I have learned a lot, made many mistakes, and did only a few things right. Just sharing what I’ve learned and some insights from my journey so far. I hope that this post will help you avoid the mistakes I made — most of which I consider easily avoidable — while you enjoy reading it, and get to know me a little bit more 🤓. A slow start after many years Summ isn’t the first product I really wanted to build. Lacking enough dev skills to even get started was a huge blocker for so many years. In fact, the first product I would’ve LOVED to build was a smart personal shopping assistant. I had this idea 4 years ago; but with no GPT, no coding skills, no technical co-founder, I didn’t have the means to make it happen. I still do not know if such a tool exists and is good enough. All I wanted was a tool that could make data-based predictions about when to buy stuff (“buy a new toothpaste every three months”) and suggest physical products that I might need or be strongly interested in. AFAIK, Amazon famously still struggles with the second one. Fast-forward a few years, I learned the very basics of HTML, CSS, and Vanilla JS. Still was not there to build a product; but good enough to code my design portfolio from scratch. Yet, I couldn’t imagine myself building a product using Vanilla JS. I really hated it, I really sucked at it. So, back to tutorial hell, and to learn about this framework I just heard about: React.React introduced so many new concepts to me. “Thinking in React” is a phrase we heard a lot, and with quite good reasons. After some time, I was able to build very basic tutorial apps, both in React, and React Native; but I have to say that I really hated coding for mobile. At this point, I was already a fan of productivity apps, and had a concept for a time management assistant app in my design portfolio. So, why not build one? Surely, it must be easy, since every coding tutorial starts with a todo app. ❌ WRONG! Building a basic todo app is easy enough, but building one good enough for a place in the market was a challenge I took and failed. I wasted one month on that until I abandoned the project for good. Even if I continued working on it, as the productivity landscape is overly competitive, I wouldn’t be able to make enough money to cover costs, assuming I make any. Since I was (and still am) in between jobs, I decided to abandon the project. 👉 What I learned: Do not start projects with a low ratio of money to effort and time. Example: Even if I get 500 monthly users, 200 of which are paid users (unrealistically high number), assuming an average subscription fee of $5/m (such apps are quite cheap, mostly due to the high competition), it would make me around $1000 minus any occurring costs. Any founder with a product that has 500 active users should make more. Even if it was relatively successful, due to the high competition, I wouldn’t make any meaningful money. PS: I use Todoist today. Due to local pricing, I pay less than $2/m. There is no way I could beat this competitive pricing, let alone the app itself. But, somehow, with a project that wasn’t even functional — let alone being an MVP — I made my first Wi-Fi money: Someone decided that the domain I preemptively purchased is worth something. By this point, I had already abandoned the project, certainly wasn’t going to renew the domain, was looking for a FT job, and a new project that I could work on. And out of nowhere, someone hands me some free money — who am I not to take it? Of course, I took it. The domain is still unused, no idea why 🤔. Ngl, I still hate the fact that my first Wi-Fi money came from this. A new idea worth pursuing? Fast-forward some weeks now. Around March, I got this crazy idea of building an email productivity tool. We all use emails, yet we all hate them. So, this must be fixed. Everyone uses emails, in fact everyone HAS TO use emails. So, I just needed to build a tool and wait for people to come. This was all, really. After all, the problem space is huge, there is enough room for another product, everyone uses emails, no need for any further validation, right? ❌ WRONG ONCE AGAIN! We all hear from the greatest in the startup landscape that we must validate our ideas with real people, yet at least some of us (guilty here 🥸) think that our product will be hugely successful and prove them to be an exception. Few might, but most are not. I certainly wasn't. 👉 Lesson learned: Always validate your ideas with real people. Ask them how much they’d pay for such a tool (not if they would). Much better if they are willing to pay upfront for a discount, etc. But even this comes later, keep reading. I think the difference between “How much” and “If” is huge for two reasons: (1) By asking them for “How much”, you force them to think in a more realistic setting. (2) You will have a more realistic idea on your profit margins. Based on my competitive analysis, I already had a solution in my mind to improve our email usage standards and email productivity (huge mistake), but I did my best to learn about their problems regarding those without pushing the idea too hard. The idea is this: Generate concise email summaries with suggested actions, combine them into one email, and send it at their preferred times. Save as much as time the AI you end up with allows. After all, everyone loves to save time. So, what kind of validation did I seek for? Talked with only a few people around me about this crazy, internet-breaking idea. The responses I got were, now I see, mediocre; no one got excited about it, just said things along the lines of “Cool idea, OK”. So, any reasonable person in this situation would think “Okay, not might not be working”, right? Well, I did not. I assumed that they were the wrong audience for this product, and there was this magical land of user segments waiting eagerly for my product, yet unknowingly. To this day, I still have not reached this magical place. Perhaps, it didn’t exist in the first place. If I cannot find it, whether it exists or not doesn’t matter. I am certainly searching for it. 👉 What I should have done: Once I decide on a problem space (time management, email productivity, etc.), I should decide on my potential user segments, people who I plan to sell my product to. Then I should go talk to those people, ask them about their pains, then get to the problem-solving/ideation phase only later. ❗️ VALIDATION COMES FROM THE REALITY OUTSIDE. What validation looks like might change from product to product; but what invalidation looks like is more or less the same for every product. Nico Jeannen told me yesterday “validation = money in the account” on Twitter. This is the ultimate form of validation your product could get. If your product doesn’t make any money, then something is invalidated by reality: Your product, you, your idea, who knows? So, at this point, I knew a little bit of Python from spending some time in tutorial hell a few years ago, some HTML/CSS/JS, barely enough React to build a working app. React could work for this project, but I needed easy-to-implement server interactivity. Luckily, around this time, I got to know about this new gen of indie hackers, and learned (but didn’t truly understand) about their approach to indie hacking, and this library called Nextjs. How good Next.js still blows my mind. So, I was back to tutorial hell once again. But, this time, with a promise to myself: This is the last time I would visit tutorial hell. Time to start building this "ground-breaking idea" Learning the fundamentals of Next.js was easier than learning of React unsurprisingly. Yet, the first time I managed to run server actions on Next.js was one of the rarest moments that completely blew my mind. To this day, I reject the idea that it is something else than pure magic under its hood. Did I absolutely need Nextjs for this project though? I do not think so. Did it save me lots of time? Absolutely. Furthermore, learning Nextjs will certainly be quite helpful for other projects that I will be tackling in the future. Already got a few ideas that might be worth pursuing in the head in case I decide to abandon Summ in the future. Fast-forward few weeks again: So, at this stage, I had a barely working MVP-like product. Since the very beginning, I spent every free hour (and more) on this project as speed is essential. But, I am not so sure it was worth it to overwork in retrospect. Yet, I know I couldn’t help myself. Everything is going kinda smooth, so what’s the worst thing that could ever happen? Well, both Apple and Google announced their AIs (Apple Intelligence and Google Gemini, respectively) will have email summarization features for their products. Summarizing singular emails is no big deal, after all there were already so many similar products in the market. I still think that what truly matters is a frictionless user experience, and this is why I built this product in a certain way: You spend less than a few minutes setting up your account, and you get to enjoy your email summaries, without ever visiting its website again. This is still a very cool concept I really like a lot. So, at this point: I had no other idea that could be pursued, already spent too much time on this project. Do I quit or not? This was the question. Of course not. I just have to launch this product as quickly as possible. So, I did something right, a quite rare occurrence I might say: Re-planned my product, dropped everything secondary to the core feature immediately (save time on reading emails), tried launching it asap. 👉 Insight: Sell only one core feature at one time. Drop anything secondary to this core feature. Well, my primary occupation is product design. So one would expect that a product I build must have stellar design. I considered any considerable time spent on design at this stage would be simply wasted. I still think this is both true and wrong: True, because if your product’s core benefits suck, no one will care about your design. False, because if your design looks amateurish, no one will trust you and your product. So, I always targeted an average level design with it and the way this tool works made it quite easy as I had to design only 2 primary pages: Landing page and user portal (which has only settings and analytics pages). However, even though I knew spending time on design was not worth much of my time, I got a bit “greedy”: In fact, I redesigned those pages three times, and still ended up with a so-so design that I am not proud of. 👉 What I would do differently: Unless absolutely necessary, only one iteration per stage as long as it works. This, in my mind, applies to everything. If your product’s A feature works, then no need to rewrite it from scratch for any reason, or even refactor it. When your product becomes a success, and you absolutely need that part of your codebase to be written, do so, but only then. Ready to launch, now is th etime for some marketing, right? By July 26, I already had a “launchable” product that barely works (I marked this date on a Notion docs, this is how I know). Yet, I had spent almost no time on marketing, sales, whatever. After all, “You build and they will come”. Did I know that I needed marketing? Of course I did, but knowingly didn’t. Why, you might ask. Well, from my perspective, it had to be a dev-heavy product; meaning that you spend most of your time on developing it, mostly coding skills. But, this is simply wrong. As a rule of thumb, as noted by one of the greatests, Marc Louvion, you should spend at least twice of the building time on marketing. ❗️ Time spent on building \* 2 people don’t know your product > they don’t use your product > you don’t get users > you don’t make money Easy as that. Following the same reasoning, a slightly different approach to planning a project is possible. Determine an approximate time to complete the project with a high level project plan. Let’s say 6 months. By the reasoning above, 2 months should go into building, and 4 into marketing. If you need 4 months for building instead of 2, then you need 8 months of marketing, which makes the time to complete the project 12 months. If you don’t have that much time, then quit the project. When does a project count as completed? Well, in reality, never. But, I think we have to define success conditions even before we start for indie projects and startups; so we know when to quit when they are not met. A success condition could look like “Make $6000 in 12 months” or “Have 3000 users in 6 months”. It all depends on the project. But, once you set it, it should be set in stone: You don’t change it unless absolutely necessary. I suspect there are few principles that make a solopreneur successful; and knowing when to quit and when to continue is definitely one of them. Marc Louvion is famously known for his success, but he got there after failing so many projects. To my knowledge, the same applies to Nico Jeannen, Pieter Levels, or almost everyone as well. ❗️ Determining when to continue even before you start will definitely help in the long run. A half-aed launch Time-leap again. Around mid August, I “soft launched” my product. By soft launch, I mean lazy marketing. Just tweeting about it, posting it on free directories. Did I get any traffic? Surely I did. Did I get any users? Nope. Only after this time, it hit me: “Either something is wrong with me, or with this product” Marketing might be a much bigger factor for a project’s success after all. Even though I get some traffic, not convincing enough for people to sign up even for a free trial. The product was still perfect in my eyes at the time (well, still is ^(\_),) so the right people are not finding my product, I thought. Then, a question that I should have been asking at the very first place, one that could prevent all these, comes to my mind: “How do even people search for such tools?” If we are to consider this whole journey of me and my so-far-failed product to be an already destined failure, one metric suffices to show why. Search volume: 30. Even if people have such a pain point, they are not looking for email summaries. So, almost no organic traffic coming from Google. But, as a person who did zero marketing on this or any product, who has zero marketing knowledge, who doesn’t have an audience on social media, there is not much I could do. Finally, it was time to give up. Or not… In my eyes, the most important element that makes a founder (solo or not) successful (this, I am not by any means) is to solve problems. ❗️ So, the problem was this: “People are not finding my product by organic search” How do I make sure I get some organic traffic and gets more visibility? Learn digital marketing and SEO as much as I can within very limited time. Thankfully, without spending much time, I came across Neil Patel's YT channel, and as I said many times, it is an absolute gold mine. I learned a lot, especially about the fundamentals, and surely it will be fruitful; but there is no magic trick that could make people visit your website. SEO certainly helps, but only when people are looking for your keywords. However, it is truly a magical solution to get in touch with REAL people that are in your user segments: 👉 Understand your pains, understand their problems, help them to solve them via building products. I did not do this so far, have to admit. But, in case you would like to have a chat about your email usage, and email productivity, just get in touch; I’d be delighted to hear about them. Getting ready for a ProductHunt launch The date was Sept 1. And I unlocked an impossible achievement: Running out of Supabase’s free plan’s Egres limit while having zero users. I was already considering moving out of their Cloud server and managing a Supabase CLI service on my Hetzner VPS for some time; but never ever suspected that I would have to do this quickly. The cheapest plan Supabase offers is $25/month; yet, at that point, I am in between jobs for such a long time, basically broke, and could barely afford that price. One or two months could be okay, but why pay for it if I will eventually move out of their Cloud service? So, instead of paying $25, I spent two days migrating out of Supabase Cloud. Worth my time? Definitely not. But, when you are broke, you gotta do stupid things. This was the first time that I felt lucky to have zero users: I have no idea how I would manage this migration if I had any. I think this is one of the core tenets of an indie hacker: Controlling their own environment. I can’t remember whose quote this is, but I suspect it was Naval: Entrepreneurs have an almost pathological need to control their own fate. They will take any suffering if they can be in charge of their destiny, and not have it in somebody else’s hands. What’s truly scary is, at least in my case, we make people around us suffer at the expense of our attempting to control our own fates. I know this period has been quite hard on my wife as well, as I neglected her quite a bit, but sadly, I know that this will happen again. It is something that I can barely help with. Still, so sorry. After working the last two weeks on a ProductHunt Launch, I finally launched it this Tuesday. Zero ranking, zero new users, but 36 kind people upvoted my product, and many commented and provided invaluable feedback. I couldn't be more grateful for each one of them 🙏. Considering all these, what lies in the future of Summ though? I have no idea, to be honest. On one hand, I have zero users, have no job, no income. So, I need a way to make money asap. On the other hand, the whole idea of it revolves around one core premise (not an assumption) that I am not so willing to share; and I couldn’t have more trust in it. This might not be the best iteration of it, however I certainly believe that email usage is one of the best problem spaces one could work on. 👉 But, one thing is for certain: I need to get in touch with people, and talk with them about this product I built so far. In fact, this is the only item on my agenda. Nothing else will save my brainchild <3. Below are some other insights and notes that I got during my journey; as they do not 100% fit into this story, I think it is more suitable to list them here. I hope you enjoyed reading this. Give Summ a try, it comes with a generous free trial, no credit card required. Some additional notes and insights: Project planning is one of the most underestimated skills for solopreneurs. It saves you enormous time, and helps you to keep your focus up. Building B2B products beats building B2C products. Businesses are very willing to pay big bucks if your product helps them. On the other hand, spending a few hours per user who would pay $5/m probably is not worth your time. It doesn’t matter how brilliant your product is if no one uses it. If you cannot sell a product in a certain category/niche (or do not know how to sell it), it might be a good idea not to start a project in it. Going after new ideas and ventures is quite risky, especially if you don’t know how to market it. On the other hand, an already established category means that there is already demand. Whether this demand is sufficient or not is another issue. As long as there is enough demand for your product to fit in, any category/niche is good. Some might be better, some might be worse. Unless you are going hardcore B2B, you will need people to find your product by means of organic search. Always conduct thorough keyword research as soon as possible.

How me and my team made 15+ apps and not made a single sale in 2023
reddit
LLM Vibe Score0
Human Vibe Score0.818
MichaelbetterecycleThis week

How me and my team made 15+ apps and not made a single sale in 2023

Hey, my name is Michael, I am in Auckland NZ. This year was the official beginning of my adult life. I graduated from university and started a full-time job. I’ve also really dug into indiehacking/bootstrapping and started 15 projects (and it will be at least 17 before the year ends). I think I’ve learned a lot but I consciously repeated mistakes. Upto (Nov) Discord Statuses + Your Location + Facebook Poke https://preview.redd.it/4nqt7tp2tf5c1.png?width=572&format=png&auto=webp&s=b0223484bc54b45b5c65e0b1afd0dc52f9c02ad1 This was the end of uni, I often messaged (and got messaged) requests of status and location to (and from my) friends. I thought, what if we make a social app that’s super basic and all it does is show you where your friends are? To differentiate from snap maps and others we wanted something with more privacy where you select the location. However, never finished the codebase or launched it. This is because I slowly started to realize that B2C (especially social networks) are way too hard to make into an actual business and the story with Fistbump would repeat itself. However, this decision not to launch it almost launched a curse on our team. From that point, we permitted ourselves to abandon projects even before launching. Lessons: Don’t do social networks if your goal is 10k MRR ASAP. If you build something to 90% competition ship it or you will think it’s okay to abandon projects Insight Bites (Nov) Youtube Summarizer Extension &#x200B; https://preview.redd.it/h6drqej4tf5c1.jpg?width=800&format=pjpg&auto=webp&s=0f211456c390ac06f4fcb54aa51f9d50b0826658 Right after Upto, we started ideating and conveniently the biggest revolution in the recent history of tech was released → GPT. We instantly began ideating. The first problem we chose to use AI for is to summarize YouTube videos. Comical. Nevertheless, I am convinced we have had the best UX because you could right-click on a video to get a slideshow of insights instead of how everyone else did it. We dropped it because there was too much competition and unit economics didn’t work out (and it was a B2C). PodPigeon (Dec) Podcast → Tweet Threads https://preview.redd.it/0ukge245tf5c1.png?width=2498&format=png&auto=webp&s=23303e1cab330578a3d25cd688fa67aa3b97fb60 Then we thought, to make unit economics work we need to make this worthwhile for podcasters. This is when I got into Twitter and started seeing people summarize podcasts. Then I thought, what if we make something that converts a podcast into tweets? This was probably one of the most important projects because it connected me with Jason and Jonaed, both of whom I regularly stay in contact with and are my go-to experts on ideas related to content creation. Jonaed was even willing to buy Podpigeon and was using it on his own time. However, the unit economics still didn’t work out (and we got excited about other things). Furthermore, we got scared of the competition because I found 1 - 2 other people who did similar things poorly. This was probably the biggest mistake we’ve made. Very similar projects made 10k MRR and more, launching later than we did. We didn’t have a coherent product vision, we didn’t understand the customer well enough, and we had a bad outlook on competition and a myriad of other things. Lessons: I already made another post about the importance of outlook on competition. Do not quit just because there are competitors or just because you can’t be 10x better. Indiehackers and Bootstrappers (or even startups) need to differentiate in the market, which can be via product (UX/UI), distribution, or both. Asking Ace Intro.co + Crowdsharing &#x200B; https://preview.redd.it/0hu2tt16tf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3d397568ef2331e78198d64fafc1a701a3e75999 As I got into Twitter, I wanted to chat with some people I saw there. However, they were really expensive. I thought, what if we made some kind of crowdfunding service for other entrepreneurs to get a private lecture from their idols? It seemed to make a lot of sense on paper. It was solving a problem (validated via the fact that Intro.co is a thing and making things cheaper and accessible is a solid ground to stand on), we understood the market (or so we thought), and it could monetize relatively quickly. However, after 1-2 posts on Reddit and Indiehackers, we quickly learned three things. Firstly, no one cares. Secondly, even if they do, they think they can get the same information for free online. Thirdly, the reasons before are bad because for the first point → we barely talked to people, and for the second people → we barely talked to the wrong people. However, at least we didn’t code anything this time and tried to validate via a landing page. Lessons Don’t give up after 1 Redditor says “I don’t need this” Don’t be scared to choose successful people as your audience. Clarito Journaling with AI analyzer https://preview.redd.it/8ria2wq6tf5c1.jpg?width=1108&format=pjpg&auto=webp&s=586ec28ae75003d9f71b4af2520b748d53dd2854 Clarito is a classic problem all amateur entrepreneurs have. It’s where you lie to yourself that you have a real problem and therefore is validated but when your team asks you how much you would pay you say I guess you will pay, maybe, like 5 bucks a month…? Turns out, you’d have to pay me to use our own product lol. We sent it off to a few friends and posted on some forums, but never really got anything tangible and decided to move away. Honestly, a lot of it is us in our own heads. We say the market is too saturated, it’ll be hard to monetize, it’s B2C, etc. Lessons: You use the Mom Test on other people. You have to do it yourself as well. However, recognizing that the Mom Test requires a lot of creativity in its investigation because knowing what questions to ask can determine the outcome of the validation. I asked myself “Do I journal” but I didn’t ask myself “How often do I want GPT to chyme in on my reflections”. Which was practically never. That being said I think with the right audience and distribution, this product can work. I just don’t know (let alone care) about the audience that much (and I thought I was one of them)/ Horns & Claw Scrapes financial news texts you whether you should buy/sell the stock (news sentiment analysis) &#x200B; https://preview.redd.it/gvfxdgc7tf5c1.jpg?width=1287&format=pjpg&auto=webp&s=63977bbc33fe74147b1f72913cefee4a9ebec9c2 This one we didn’t even bother launching. Probably something internal in the team and also seemed too good to be true (because if this works, doesn’t that just make us ultra-rich fast?). I saw a similar tool making 10k MRR so I guess I was wrong. Lessons: This one was pretty much just us getting into our heads. I declared that without an audience it would be impossible to ship this product and we needed to start a YouTube channel. Lol, and we did. And we couldn’t even film for 1 minute. I made bold statements like “We will commit to this for at least 1 year no matter what”. Learnery Make courses about any subject https://preview.redd.it/1nw6z448tf5c1.jpg?width=1112&format=pjpg&auto=webp&s=f2c73e8af23b0a6c3747a81e785960d4004feb48 This is probably the most “successful” project we’ve made. It grew from a couple of dozen to a couple of hundred users. It has 11 buy events for $9.99 LTD (we couldn’t be bothered connecting Stripe because we thought no one would buy it anyway). However what got us discouraged from seriously pursuing it more is, that this has very low defensibility, “Why wouldn’t someone just use chatGPT?” and it’s B2C so it’s hard to monetize. I used it myself for a month or so but then stopped. I don’t think it’s the app, I think the act of learning a concept from scratch isn’t something you do constantly in the way Learnery delivers it (ie course). I saw a bunch of similar apps that look like Ass make like 10k MRR. Lessons: Don’t do B2C, or if you do, do it properly Don’t just Mixpanel the buy button, connect your Stripe otherwise, it doesn’t feel real and you won’t get momentum. I doubt anyone (even me) will make this mistake again. I live in my GPT bubble where I make assumptions that everyone uses GPT the same way and as much as I do. In reality, the argument that this has low defensibility against GPT is invalid. Platforms that deliver a differentiated UX from ChatGPT to audiences who are not tightly integrated into the habit of using ChatGPT (which is like - everyone except for SOME tech evangelists). CuriosityFM Make podcasts about any subject https://preview.redd.it/zmosrcp8tf5c1.jpg?width=638&format=pjpg&auto=webp&s=d04ddffabef9050050b0d87939273cc96a8637dc This was our attempt at making Learnery more unique and more differentiated from chatGPT. We never really launched it. The unit economics didn’t work out and it was actually pretty boring to listen to, I don’t think I even fully listened to one 15-minute episode. I think this wasn’t that bad, it taught us more about ElevenLabs and voice AI. It took us maybe only 2-3 days to build so I think building to learn a new groundbreaking technology is fine. SleepyTale Make children’s bedtime stories https://preview.redd.it/14ue9nm9tf5c1.jpg?width=807&format=pjpg&auto=webp&s=267e18ec6f9270e6d1d11564b38136fa524966a1 My 8-year-old sister gave me that idea. She was too scared of making tea and I was curious about how she’d react if she heard a bedtime story about that exact scenario with the moral that I wanted her to absorb (which is that you shouldn’t be scared to try new things ie stop asking me to make your tea and do it yourself, it’s not that hard. You could say I went full Goebbels on her). Zane messaged a bunch of parents on Facebook but no one really cared. We showed this to one Lady at the place we worked from at Uni and she was impressed and wanted to show it to her kids but we already turned off our ElevenLabs subscription. Lessons: However, the truth behind this is beyond just “you need to be able to distribute”. It’s that you have to care about the audience. I don’t particularly want to build products for kids and parents. I am far away from that audience because I am neither a kid anymore nor going to be a parent anytime soon, and my sister still asked me to make her tea so the story didn’t work. I think it’s important to ask yourself whether you care about the audience. The way you answer that even when you are in full bias mode is, do you engage with them? Are you interested in what’s happening in their communities? Are you friends with them? Etc. User Survey Analyzer Big User Survey → GPT → Insights Report Me and my coworker were chatting about AI when he asked me to help him analyze a massive survey for him. I thought that was some pretty decent validation. Someone in an actual company asking for help. Lessons Market research is important but moving fast is also important. Ie building momentum. Also don’t revolve around 1 user. This has been a problem in multiple projects. Finding as many users as possible in the beginning to talk to is key. Otherwise, you are just waiting for 1 person to get back to you. AutoI18N Automated Internationalization of the codebase for webapps This one I might still do. It’s hard to find a solid distribution strategy. However, the idea came from me having to do it at my day job. It seems a solid problem. I’d say it’s validated and has some good players already. The key will be differentiation via the simplicity of UX and distribution (which means a slightly different audience). In the backlog for now because I don’t care about the problem or the audience that much. Documate - Part 1 Converts complex PDFs into Excel https://preview.redd.it/8b45k9katf5c1.jpg?width=1344&format=pjpg&auto=webp&s=57324b8720eb22782e28794d2db674b073193995 My mom needed to convert a catalog of furniture into an inventory which took her 3 full days of data entry. I automated it for her and thought this could have a big impact but there was no distribution because there was no ICP. We tried to find the ideal customers by talking to a bunch of different demographics but I flew to Kazakhstan for a holiday and so this kind of fizzled out. I am not writing this blog post linearity, this is my 2nd hour and I am tired and don’t want to finish this later so I don’t even know what lessons I learned. Figmatic Marketplace of high-quality Figma mockups of real apps https://preview.redd.it/h13yv45btf5c1.jpg?width=873&format=pjpg&auto=webp&s=aaa2896aeac2f22e9b7d9eed98c28bb8a2d2cdf1 This was a collab between me and my friend Alex. It was the classic Clarito where we both thought we had this problem and would pay to fix it. In reality, this is a vitamin. Neither I, nor I doubt Alex have thought of this as soon as we bought the domain. We posted it on Gumroad, sent it to a bunch of forums, and called it a day. Same issue as almost all the other ones. No distribution strategy. However, apps like Mobin show us that this concept is indeed profitable but it takes time. It needs SEO. It needs a community. None of those things, me and Alex had or was interested in. However shortly after HTML → Figma came out and it’s the best plugin. Maybe that should’ve been the idea. Podcast → Course Turns Podcaster’s episodes into a course This one I got baited by Jason :P I described to him the idea of repurposing his content for a course. He told me this was epic and he would pay. Then after I sent him the demo, he never checked it out. Anyhow during the development, we realized that doesn’t actually work because A podcast doesn’t have the correct format for the course, the most you can extract are concepts and ideas, seldom explanations. Most creators want video-based courses to be hosted on Kajabi or Udemy Another lesson is that when you pitch something to a user, what you articulate is a platform or a process, they imagine an outcome. However, the end result of your platform can be a very different outcome to what they had in mind and there is even a chance that what they want is not possible. You need to understand really well what the outcome looks like before you design the process. This is a classic problem where we thought of the solution before the problem. Yes, the problem exists. Podcasters want to make courses. However, if you really understand what they want, you can see how repurposing a podcast isn’t the best way to get there. However I only really spoke to 1-2 podcasters about this so making conclusions is dangerous for this can just be another asking ace mistake with the Redditor. Documate Part 2 Same concept as before but now I want to run some ads. We’ll see what happens. https://preview.redd.it/xb3npj0ctf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3cd4884a29fd11d870d010a2677b585551c49193 In conclusion https://preview.redd.it/2zrldc9dtf5c1.jpg?width=1840&format=pjpg&auto=webp&s=2b3105073e752ad41c23f205dbd1ea046c1da7ff It doesn’t actually matter that much whether you choose to do a B2C, or a social network or focus on growing your audience. All of these can make you successful. What’s important is that you choose. If I had to summarize my 2023 in one word it’s indecision. Most of these projects succeeded for other people, nothing was as fundamentally wrong about them as I proclaimed. In reality that itself was an excuse. New ideas seduce, and it is a form of discipline to commit to a single project for a respectful amount of time. https://preview.redd.it/zy9a2vzdtf5c1.jpg?width=1456&format=pjpg&auto=webp&s=901c621227bba0feb4efdb39142f66ab2ebb86fe Distribution is not just posting on Indiehackers and Reddit. It’s an actual strategy and you should think of it as soon as you think of the idea, even before the Figma designs. I like how Denis Shatalin taught me. You have to build a pipeline. That means a reliable way to get leads, launch campaigns at them, close deals, learn from them, and optimize. Whenever I get an idea now I always try to ask myself “Where can I find 1000s leads in one day?” If there is no good answer, this is not a good project to do now. &#x200B; https://preview.redd.it/2boh3fpetf5c1.jpg?width=1456&format=pjpg&auto=webp&s=1c0d5d7b000716fcbbb00cbad495e8b61e25be66 Talk to users before doing anything. Jumping on designing and coding to make your idea a reality is a satisfying activity in the short term. Especially for me, I like to create for the sake of creation. However, it is so important to understand the market, understand the audience, understand the distribution. There are a lot of things to understand before coding. https://preview.redd.it/lv8tt96ftf5c1.jpg?width=1456&format=pjpg&auto=webp&s=6c8735aa6ad795f216ff9ddfa2341712e8277724 Get out of your own head. The real reason we dropped so many projects is that we got into our own heads. We let the negative thoughts creep in and kill all the optimism. I am really good at coming up with excuses to start a project. However, I am equally as good at coming up with reasons to kill a project. And so you have this yin and yang of starting and stopping. Building momentum and not burning out. I can say with certainty my team ran out of juice this year. We lost momentum so many times we got burnt out towards the end. Realizing that the project itself has momentum is important. User feedback and sales bring momentum. Building also creates momentum but unless it is matched with an equal force of impact, it can stomp the project down. That is why so many of our projects died quickly after we launched. The smarter approach is to do things that have a low investment of momentum (like talking to users) but result in high impact (sales or feedback). Yes, that means the project can get invalidated which makes it more short-lived than if we built it first, but it preserves team life energy. At the end of 2023 here is a single sentence I am making about how I think one becomes a successful indiehacker. One becomes a successful Indiehacker when one starts to solve pain-killer problems in the market they understand, for an audience they care about and consistently engage with for a long enough timeframe. Therefore an unsuccessful Indiehacker in a single sentence is An unsuccessful Indiehacker constantly enters new markets they don’t understand to build solutions for people whose problems they don’t care about, in a timeframe that is shorter than than the time they spent thinking about distribution. However, an important note to be made. Life is not just about indiehacking. It’s about learning and having fun. In the human world, the best journey isn’t the one that gets you the fastest to your goals but the one you enjoy the most. I enjoyed making those silly little projects and although I do not regret them, I will not repeat the same mistakes in 2024. But while it’s still 2023, I have 2 more projects I want to do :) EDIT: For Devs, frontend is always react with vite (ts) and backend is either node with express (ts) or python. For DB either Postgres or mongo (usually Prisma for ORM). For deployment all of it is on AWS (S3, EC2). In terms of libraries/APIs Whisper.cpp is best open source for transcription Obviously the gpt apis Eleven labs for voice related stuff And other random stuff here and there

Enhancing Time Management & Journaling with AI: A Hybrid Physical-Digital Approach
reddit
LLM Vibe Score0
Human Vibe Score1
Educational-Sand8635This week

Enhancing Time Management & Journaling with AI: A Hybrid Physical-Digital Approach

Hey everyone! I wanted to share my experience combining AI, physical journaling, and time tracking - and get your thoughts on taking this further. Background: My AI-Enhanced Productivity Journey I recently did an intensive experiment tracking my time down to the minute (as a software engineer juggling multiple projects, Kendo practice, and side hustles). I used Claude/ChatGPT to analyze my patterns and got some fascinating insights about my productivity and habits. The AIs helped me spot patterns I was blind to and asked surprisingly thoughtful questions that made me reflect deeper. What really struck me was how AI turned from just an analysis tool into something like a wise friend who remembers everything and asks the right questions at the right time. This got me thinking about creating a more structured approach. The Hybrid Model Concept I'm exploring an idea that combines: Physical journaling/tracking (for tactile experience and mindfulness) AI-powered digital companion (for insights and reflection) Flexible input methods (write in a notebook, take photos, type, or voice record) The key insight is: while AI can track digital activities, our lives happen both online and offline. Sometimes we're in meetings, reading books, or having coffee with friends. By combining human input with AI analysis, we get both accuracy and insight. How It Would Work: \- Write in your physical journal/planner as usual \- Optionally snap photos or type key points into the app \- AI companion provides: \- Smart comparisons (today vs last week/month/year) \- Pattern recognition ("I notice you're most creative after morning exercise...") \- Thoughtful reflection prompts ("How has your approach to \[recurring challenge\] evolved?") \- Connection-making between entries ("This reminds me of what you wrote about...") What Makes This Different Human Agency: You control what to track and share, maintaining mindfulness AI as Coach: Beyond just tracking, it asks meaningful questions based on your patterns Temporal Intelligence: Helps you see how your behaviors and thoughts evolve over time Flexibility: Works whether you prefer paper, digital, or both Early Insights from My Testing: \- Initial tracking caused some anxiety (couldn't sleep first two nights!) but became natural \- AI feedback varies by tool (Claude more encouraging, ChatGPT more direct) \- The combination of manual tracking + AI analysis led to better self-awareness \- Having AI ask unexpected questions led to deeper insights than solo journaling Questions for the Community: Have you tried combining AI with traditional productivity/journaling methods? What worked/didn't? What kinds of AI-generated insights/questions would be most valuable to you? How would you balance the convenience of automation with the benefits of manual tracking? What features would make this truly useful for your productivity practice? I believe there's something powerful in combining the mindfulness of manual tracking, the wisdom of AI, and the flexibility of modern tools. But I'd love to hear your thoughts and experiences! Looking forward to the discussion! 🤔✍️

How me and my team made 15+ apps and not made a single sale in 2023
reddit
LLM Vibe Score0
Human Vibe Score0.818
MichaelbetterecycleThis week

How me and my team made 15+ apps and not made a single sale in 2023

Hey, my name is Michael, I am in Auckland NZ. This year was the official beginning of my adult life. I graduated from university and started a full-time job. I’ve also really dug into indiehacking/bootstrapping and started 15 projects (and it will be at least 17 before the year ends). I think I’ve learned a lot but I consciously repeated mistakes. Upto (Nov) Discord Statuses + Your Location + Facebook Poke https://preview.redd.it/4nqt7tp2tf5c1.png?width=572&format=png&auto=webp&s=b0223484bc54b45b5c65e0b1afd0dc52f9c02ad1 This was the end of uni, I often messaged (and got messaged) requests of status and location to (and from my) friends. I thought, what if we make a social app that’s super basic and all it does is show you where your friends are? To differentiate from snap maps and others we wanted something with more privacy where you select the location. However, never finished the codebase or launched it. This is because I slowly started to realize that B2C (especially social networks) are way too hard to make into an actual business and the story with Fistbump would repeat itself. However, this decision not to launch it almost launched a curse on our team. From that point, we permitted ourselves to abandon projects even before launching. Lessons: Don’t do social networks if your goal is 10k MRR ASAP. If you build something to 90% competition ship it or you will think it’s okay to abandon projects Insight Bites (Nov) Youtube Summarizer Extension &#x200B; https://preview.redd.it/h6drqej4tf5c1.jpg?width=800&format=pjpg&auto=webp&s=0f211456c390ac06f4fcb54aa51f9d50b0826658 Right after Upto, we started ideating and conveniently the biggest revolution in the recent history of tech was released → GPT. We instantly began ideating. The first problem we chose to use AI for is to summarize YouTube videos. Comical. Nevertheless, I am convinced we have had the best UX because you could right-click on a video to get a slideshow of insights instead of how everyone else did it. We dropped it because there was too much competition and unit economics didn’t work out (and it was a B2C). PodPigeon (Dec) Podcast → Tweet Threads https://preview.redd.it/0ukge245tf5c1.png?width=2498&format=png&auto=webp&s=23303e1cab330578a3d25cd688fa67aa3b97fb60 Then we thought, to make unit economics work we need to make this worthwhile for podcasters. This is when I got into Twitter and started seeing people summarize podcasts. Then I thought, what if we make something that converts a podcast into tweets? This was probably one of the most important projects because it connected me with Jason and Jonaed, both of whom I regularly stay in contact with and are my go-to experts on ideas related to content creation. Jonaed was even willing to buy Podpigeon and was using it on his own time. However, the unit economics still didn’t work out (and we got excited about other things). Furthermore, we got scared of the competition because I found 1 - 2 other people who did similar things poorly. This was probably the biggest mistake we’ve made. Very similar projects made 10k MRR and more, launching later than we did. We didn’t have a coherent product vision, we didn’t understand the customer well enough, and we had a bad outlook on competition and a myriad of other things. Lessons: I already made another post about the importance of outlook on competition. Do not quit just because there are competitors or just because you can’t be 10x better. Indiehackers and Bootstrappers (or even startups) need to differentiate in the market, which can be via product (UX/UI), distribution, or both. Asking Ace Intro.co + Crowdsharing &#x200B; https://preview.redd.it/0hu2tt16tf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3d397568ef2331e78198d64fafc1a701a3e75999 As I got into Twitter, I wanted to chat with some people I saw there. However, they were really expensive. I thought, what if we made some kind of crowdfunding service for other entrepreneurs to get a private lecture from their idols? It seemed to make a lot of sense on paper. It was solving a problem (validated via the fact that Intro.co is a thing and making things cheaper and accessible is a solid ground to stand on), we understood the market (or so we thought), and it could monetize relatively quickly. However, after 1-2 posts on Reddit and Indiehackers, we quickly learned three things. Firstly, no one cares. Secondly, even if they do, they think they can get the same information for free online. Thirdly, the reasons before are bad because for the first point → we barely talked to people, and for the second people → we barely talked to the wrong people. However, at least we didn’t code anything this time and tried to validate via a landing page. Lessons Don’t give up after 1 Redditor says “I don’t need this” Don’t be scared to choose successful people as your audience. Clarito Journaling with AI analyzer https://preview.redd.it/8ria2wq6tf5c1.jpg?width=1108&format=pjpg&auto=webp&s=586ec28ae75003d9f71b4af2520b748d53dd2854 Clarito is a classic problem all amateur entrepreneurs have. It’s where you lie to yourself that you have a real problem and therefore is validated but when your team asks you how much you would pay you say I guess you will pay, maybe, like 5 bucks a month…? Turns out, you’d have to pay me to use our own product lol. We sent it off to a few friends and posted on some forums, but never really got anything tangible and decided to move away. Honestly, a lot of it is us in our own heads. We say the market is too saturated, it’ll be hard to monetize, it’s B2C, etc. Lessons: You use the Mom Test on other people. You have to do it yourself as well. However, recognizing that the Mom Test requires a lot of creativity in its investigation because knowing what questions to ask can determine the outcome of the validation. I asked myself “Do I journal” but I didn’t ask myself “How often do I want GPT to chyme in on my reflections”. Which was practically never. That being said I think with the right audience and distribution, this product can work. I just don’t know (let alone care) about the audience that much (and I thought I was one of them)/ Horns & Claw Scrapes financial news texts you whether you should buy/sell the stock (news sentiment analysis) &#x200B; https://preview.redd.it/gvfxdgc7tf5c1.jpg?width=1287&format=pjpg&auto=webp&s=63977bbc33fe74147b1f72913cefee4a9ebec9c2 This one we didn’t even bother launching. Probably something internal in the team and also seemed too good to be true (because if this works, doesn’t that just make us ultra-rich fast?). I saw a similar tool making 10k MRR so I guess I was wrong. Lessons: This one was pretty much just us getting into our heads. I declared that without an audience it would be impossible to ship this product and we needed to start a YouTube channel. Lol, and we did. And we couldn’t even film for 1 minute. I made bold statements like “We will commit to this for at least 1 year no matter what”. Learnery Make courses about any subject https://preview.redd.it/1nw6z448tf5c1.jpg?width=1112&format=pjpg&auto=webp&s=f2c73e8af23b0a6c3747a81e785960d4004feb48 This is probably the most “successful” project we’ve made. It grew from a couple of dozen to a couple of hundred users. It has 11 buy events for $9.99 LTD (we couldn’t be bothered connecting Stripe because we thought no one would buy it anyway). However what got us discouraged from seriously pursuing it more is, that this has very low defensibility, “Why wouldn’t someone just use chatGPT?” and it’s B2C so it’s hard to monetize. I used it myself for a month or so but then stopped. I don’t think it’s the app, I think the act of learning a concept from scratch isn’t something you do constantly in the way Learnery delivers it (ie course). I saw a bunch of similar apps that look like Ass make like 10k MRR. Lessons: Don’t do B2C, or if you do, do it properly Don’t just Mixpanel the buy button, connect your Stripe otherwise, it doesn’t feel real and you won’t get momentum. I doubt anyone (even me) will make this mistake again. I live in my GPT bubble where I make assumptions that everyone uses GPT the same way and as much as I do. In reality, the argument that this has low defensibility against GPT is invalid. Platforms that deliver a differentiated UX from ChatGPT to audiences who are not tightly integrated into the habit of using ChatGPT (which is like - everyone except for SOME tech evangelists). CuriosityFM Make podcasts about any subject https://preview.redd.it/zmosrcp8tf5c1.jpg?width=638&format=pjpg&auto=webp&s=d04ddffabef9050050b0d87939273cc96a8637dc This was our attempt at making Learnery more unique and more differentiated from chatGPT. We never really launched it. The unit economics didn’t work out and it was actually pretty boring to listen to, I don’t think I even fully listened to one 15-minute episode. I think this wasn’t that bad, it taught us more about ElevenLabs and voice AI. It took us maybe only 2-3 days to build so I think building to learn a new groundbreaking technology is fine. SleepyTale Make children’s bedtime stories https://preview.redd.it/14ue9nm9tf5c1.jpg?width=807&format=pjpg&auto=webp&s=267e18ec6f9270e6d1d11564b38136fa524966a1 My 8-year-old sister gave me that idea. She was too scared of making tea and I was curious about how she’d react if she heard a bedtime story about that exact scenario with the moral that I wanted her to absorb (which is that you shouldn’t be scared to try new things ie stop asking me to make your tea and do it yourself, it’s not that hard. You could say I went full Goebbels on her). Zane messaged a bunch of parents on Facebook but no one really cared. We showed this to one Lady at the place we worked from at Uni and she was impressed and wanted to show it to her kids but we already turned off our ElevenLabs subscription. Lessons: However, the truth behind this is beyond just “you need to be able to distribute”. It’s that you have to care about the audience. I don’t particularly want to build products for kids and parents. I am far away from that audience because I am neither a kid anymore nor going to be a parent anytime soon, and my sister still asked me to make her tea so the story didn’t work. I think it’s important to ask yourself whether you care about the audience. The way you answer that even when you are in full bias mode is, do you engage with them? Are you interested in what’s happening in their communities? Are you friends with them? Etc. User Survey Analyzer Big User Survey → GPT → Insights Report Me and my coworker were chatting about AI when he asked me to help him analyze a massive survey for him. I thought that was some pretty decent validation. Someone in an actual company asking for help. Lessons Market research is important but moving fast is also important. Ie building momentum. Also don’t revolve around 1 user. This has been a problem in multiple projects. Finding as many users as possible in the beginning to talk to is key. Otherwise, you are just waiting for 1 person to get back to you. AutoI18N Automated Internationalization of the codebase for webapps This one I might still do. It’s hard to find a solid distribution strategy. However, the idea came from me having to do it at my day job. It seems a solid problem. I’d say it’s validated and has some good players already. The key will be differentiation via the simplicity of UX and distribution (which means a slightly different audience). In the backlog for now because I don’t care about the problem or the audience that much. Documate - Part 1 Converts complex PDFs into Excel https://preview.redd.it/8b45k9katf5c1.jpg?width=1344&format=pjpg&auto=webp&s=57324b8720eb22782e28794d2db674b073193995 My mom needed to convert a catalog of furniture into an inventory which took her 3 full days of data entry. I automated it for her and thought this could have a big impact but there was no distribution because there was no ICP. We tried to find the ideal customers by talking to a bunch of different demographics but I flew to Kazakhstan for a holiday and so this kind of fizzled out. I am not writing this blog post linearity, this is my 2nd hour and I am tired and don’t want to finish this later so I don’t even know what lessons I learned. Figmatic Marketplace of high-quality Figma mockups of real apps https://preview.redd.it/h13yv45btf5c1.jpg?width=873&format=pjpg&auto=webp&s=aaa2896aeac2f22e9b7d9eed98c28bb8a2d2cdf1 This was a collab between me and my friend Alex. It was the classic Clarito where we both thought we had this problem and would pay to fix it. In reality, this is a vitamin. Neither I, nor I doubt Alex have thought of this as soon as we bought the domain. We posted it on Gumroad, sent it to a bunch of forums, and called it a day. Same issue as almost all the other ones. No distribution strategy. However, apps like Mobin show us that this concept is indeed profitable but it takes time. It needs SEO. It needs a community. None of those things, me and Alex had or was interested in. However shortly after HTML → Figma came out and it’s the best plugin. Maybe that should’ve been the idea. Podcast → Course Turns Podcaster’s episodes into a course This one I got baited by Jason :P I described to him the idea of repurposing his content for a course. He told me this was epic and he would pay. Then after I sent him the demo, he never checked it out. Anyhow during the development, we realized that doesn’t actually work because A podcast doesn’t have the correct format for the course, the most you can extract are concepts and ideas, seldom explanations. Most creators want video-based courses to be hosted on Kajabi or Udemy Another lesson is that when you pitch something to a user, what you articulate is a platform or a process, they imagine an outcome. However, the end result of your platform can be a very different outcome to what they had in mind and there is even a chance that what they want is not possible. You need to understand really well what the outcome looks like before you design the process. This is a classic problem where we thought of the solution before the problem. Yes, the problem exists. Podcasters want to make courses. However, if you really understand what they want, you can see how repurposing a podcast isn’t the best way to get there. However I only really spoke to 1-2 podcasters about this so making conclusions is dangerous for this can just be another asking ace mistake with the Redditor. Documate Part 2 Same concept as before but now I want to run some ads. We’ll see what happens. https://preview.redd.it/xb3npj0ctf5c1.jpg?width=1456&format=pjpg&auto=webp&s=3cd4884a29fd11d870d010a2677b585551c49193 In conclusion https://preview.redd.it/2zrldc9dtf5c1.jpg?width=1840&format=pjpg&auto=webp&s=2b3105073e752ad41c23f205dbd1ea046c1da7ff It doesn’t actually matter that much whether you choose to do a B2C, or a social network or focus on growing your audience. All of these can make you successful. What’s important is that you choose. If I had to summarize my 2023 in one word it’s indecision. Most of these projects succeeded for other people, nothing was as fundamentally wrong about them as I proclaimed. In reality that itself was an excuse. New ideas seduce, and it is a form of discipline to commit to a single project for a respectful amount of time. https://preview.redd.it/zy9a2vzdtf5c1.jpg?width=1456&format=pjpg&auto=webp&s=901c621227bba0feb4efdb39142f66ab2ebb86fe Distribution is not just posting on Indiehackers and Reddit. It’s an actual strategy and you should think of it as soon as you think of the idea, even before the Figma designs. I like how Denis Shatalin taught me. You have to build a pipeline. That means a reliable way to get leads, launch campaigns at them, close deals, learn from them, and optimize. Whenever I get an idea now I always try to ask myself “Where can I find 1000s leads in one day?” If there is no good answer, this is not a good project to do now. &#x200B; https://preview.redd.it/2boh3fpetf5c1.jpg?width=1456&format=pjpg&auto=webp&s=1c0d5d7b000716fcbbb00cbad495e8b61e25be66 Talk to users before doing anything. Jumping on designing and coding to make your idea a reality is a satisfying activity in the short term. Especially for me, I like to create for the sake of creation. However, it is so important to understand the market, understand the audience, understand the distribution. There are a lot of things to understand before coding. https://preview.redd.it/lv8tt96ftf5c1.jpg?width=1456&format=pjpg&auto=webp&s=6c8735aa6ad795f216ff9ddfa2341712e8277724 Get out of your own head. The real reason we dropped so many projects is that we got into our own heads. We let the negative thoughts creep in and kill all the optimism. I am really good at coming up with excuses to start a project. However, I am equally as good at coming up with reasons to kill a project. And so you have this yin and yang of starting and stopping. Building momentum and not burning out. I can say with certainty my team ran out of juice this year. We lost momentum so many times we got burnt out towards the end. Realizing that the project itself has momentum is important. User feedback and sales bring momentum. Building also creates momentum but unless it is matched with an equal force of impact, it can stomp the project down. That is why so many of our projects died quickly after we launched. The smarter approach is to do things that have a low investment of momentum (like talking to users) but result in high impact (sales or feedback). Yes, that means the project can get invalidated which makes it more short-lived than if we built it first, but it preserves team life energy. At the end of 2023 here is a single sentence I am making about how I think one becomes a successful indiehacker. One becomes a successful Indiehacker when one starts to solve pain-killer problems in the market they understand, for an audience they care about and consistently engage with for a long enough timeframe. Therefore an unsuccessful Indiehacker in a single sentence is An unsuccessful Indiehacker constantly enters new markets they don’t understand to build solutions for people whose problems they don’t care about, in a timeframe that is shorter than than the time they spent thinking about distribution. However, an important note to be made. Life is not just about indiehacking. It’s about learning and having fun. In the human world, the best journey isn’t the one that gets you the fastest to your goals but the one you enjoy the most. I enjoyed making those silly little projects and although I do not regret them, I will not repeat the same mistakes in 2024. But while it’s still 2023, I have 2 more projects I want to do :) EDIT: For Devs, frontend is always react with vite (ts) and backend is either node with express (ts) or python. For DB either Postgres or mongo (usually Prisma for ORM). For deployment all of it is on AWS (S3, EC2). In terms of libraries/APIs Whisper.cpp is best open source for transcription Obviously the gpt apis Eleven labs for voice related stuff And other random stuff here and there

Disorganized: The note taking app for busy people (no AI inside)
reddit
LLM Vibe Score0
Human Vibe Score0
DisorganizedAppThis week

Disorganized: The note taking app for busy people (no AI inside)

https://preview.redd.it/27qoz7ihlnpe1.png?width=1774&format=png&auto=webp&s=1658d7a4c619df46cd76c5ff639b6c6c7b65fc50 About one year ago I had enough and set out to create my own note taking app, and have been working on it in my spare time since summer. I had two main goals when creating Disorganized: \- Less friction If I'm walking around and a thought pop ups in my head there should be zero friction to writing it down. That's why Disorganized doesn't ask you to write a title, sort it into the correct folder, etc. You write exactly your thoughts and nothing else. \- A better solution than templates. I wanted one app that I could use to track my workouts, my recipes and one-off notes. Other apps accomplish this with templates but I find templates too rigid - I don't want to create a "recipe" template because a "recipe" is not always the same thing. It's usually a table of ingredients and some instructions in text, but other times it's multiple tables of ingredients, or something else entirely. Templates are too rigid. In Disorganized, you "clone" notes to create a new note with the same structure. This way, you can reuse previous set ups, but you're completely free to evolve your "template" as you go. Please try it out and tell me what you think! iOS, three months premium: https://apps.apple.com/redeem/?ctx=offercodes&id=6738280174&code=THREEMONTHS Android: https://play.google.com/store/apps/details?id=com.disorganized.disorganized&pli=1 Use code "THREEMONTHS" at checkout for three months. Web version: https://app.getdisorganized.com/

I acquired a SaaS for ~5 figures to solve my content problem
reddit
LLM Vibe Score0
Human Vibe Score1
Either_Discussion635This week

I acquired a SaaS for ~5 figures to solve my content problem

In 2023 I bought a SaaS called Cuppa AI. I actually found the product on twitter, run by a very talented engineer in the UK.  I’ve spent tens of thousands of dollars on content for various media companies. In one consumer health company, it cost us around $200-$500 for each SEO optimized article. This adds up pretty quickly. Not forgetting the 20 hours of edits! This isn’t just an isolated problem for a single company. It’s industry wide and affects small business + agency owners alike. I spent over a decade in media, and have seen many agency founders complain about long lead times and high costs for low output.  This is an issue. Large swathes of would-be customers that prefer to consume content before buying are being ignored - either because it takes too long or costs too much for founders to scale this channel.   I eventually became tired of the media content game in 2022 and looked into using SaaS to solve my previous life’s challenges. I started building, acquiring and scaling a portfolio of products that I found useful in my day to day. But the content issue was still there.  So I started to look for ways to reduce the time + cost content burden for my own portfolio.   I initially discovered Cuppa using it for my own personal pains of content research, editing, publishing, and scaling. But then I saw potential. I wanted to turn it into an end to end solution for the content gap that myself and other business owners weren’t taking advantage of because of time, cost, or other priorities.  I sent a DM. Then a few calls later, I acquired it in June 2023.  I chose cuppa vs other competing products for a few reasons:  The founder gave excellent support during and post acquisition  It already had a large, loyal existing user base I’d personally used it and solved a pain with it. I saw the potential to solve many others for more people like me  The founder has put a ton of quality and care into it. There wasn’t a risk of picking up a patchy product, plus it already had great social distribution  It naturally fits my expertise from the ‘other side’. I was the original customer of it, so I knew I could evolve it with features that could create content at scale without losing the human touch  Since then we’ve added a lot of new stuff: Chat with articles Image generation for articles API keys to reduce cost Brand / persona voice custom prompts  Month on month iterative content improvement  Full stack content team that blends AI and human editors for agencies I’m still in full build mode with the team. I want to take it to a place where agencies and SMB owners can trust the AI + human content model enough to see this product as a no-brainer for their biz. I don’t believe in AI slop - there’s enough of that out there - I DO believe in using AI to do the grunt work, but to always have that human element a machine can’t quite mimic.  We have a lot more to get through, but I’m very excited about it. View of the done for you content workflow

I built an AI Stock Analysis Tool
reddit
LLM Vibe Score0
Human Vibe Score1
HenryObjThis week

I built an AI Stock Analysis Tool

Hi Reddit, TL;DR: I am sharing the tool I built to assist me with my investments I have been investing for over a decade, and I have always struggled with: Putting the time to do actual research Trusting analyst’s recommendations To \ invest \ we want to make sure that the price is right and the company will keep improving. How do we know that “the price is right?” How can we predict that the company will perform better in the future? To answer the above, we have to look at the company’s financials and their trends. We have to compare the company with its peers/competitors. We should understand its business model, the sector and geography the company evolves in and the perspective of the economy in general. We can also look at additional signals like insiders selling or buying. Just for one investment, this is already a lot of work. And a work that we need to repeat every time there is a significant change - for example, a significant price change from our last analysis or new quarterly results, etc. To automate all the above, I have built a stock analysis tool and have been using it the past years for my own investments. I have been adding LLMs agents (GPT 4o & Claude 3.5) to perform the qualitative analysis. Recently, I decided to share it and keep on building it in public. In this initial version, you can get the summary of the stock analysis my model generates. For now, it covers most of the S&P and Nasdaq stocks. Here is the link 👉 https://undervalued.ai If you are into investing yourself, please feel free to reach out. I would love to get your feedback and know more about your methodology.

[N] Yoshua Bengio's latest letter addressing arguments against taking AI safety seriously
reddit
LLM Vibe Score0
Human Vibe Score1
qtangsThis week

[N] Yoshua Bengio's latest letter addressing arguments against taking AI safety seriously

https://yoshuabengio.org/2024/07/09/reasoning-through-arguments-against-taking-ai-safety-seriously/ Summary by GPT-4o: "Reasoning through arguments against taking AI safety seriously" by Yoshua Bengio: Summary Introduction Bengio reflects on his year of advocating for AI safety, learning through debates, and synthesizing global expert views in the International Scientific Report on AI safety. He revisits arguments against AI safety concerns and shares his evolved perspective on the potential catastrophic risks of AGI and ASI. Headings and Summary The Importance of AI Safety Despite differing views, there is a consensus on the need to address risks associated with AGI and ASI. The main concern is the unknown moral and behavioral control over such entities. Arguments Dismissing AGI/ASI Risks Skeptics argue AGI/ASI is either impossible or too far in the future to worry about now. Bengio refutes this, stating we cannot be certain about the timeline and need to prepare regulatory frameworks proactively. For those who think AGI and ASI are impossible or far in the future He challenges the idea that current AI capabilities are far from human-level intelligence, citing historical underestimations of AI advancements. The trend of AI capabilities suggests we might reach AGI/ASI sooner than expected. For those who think AGI is possible but only in many decades Regulatory and safety measures need time to develop, necessitating action now despite uncertainties about AGI’s timeline. For those who think that we may reach AGI but not ASI Bengio argues that even AGI presents significant risks and could quickly lead to ASI, making it crucial to address these dangers. For those who think that AGI and ASI will be kind to us He counters the optimism that AGI/ASI will align with human goals, emphasizing the need for robust control mechanisms to prevent AI from pursuing harmful objectives. For those who think that corporations will only design well-behaving AIs and existing laws are sufficient Profit motives often conflict with safety, and existing laws may not adequately address AI-specific risks and loopholes. For those who think that we should accelerate AI capabilities research and not delay benefits of AGI Bengio warns against prioritizing short-term benefits over long-term risks, advocating for a balanced approach that includes safety research. For those concerned that talking about catastrophic risks will hurt efforts to mitigate short-term human-rights issues with AI Addressing both short-term and long-term AI risks can be complementary, and ignoring catastrophic risks would be irresponsible given their potential impact. For those concerned with the US-China cold war AI development should consider global risks and seek collaborative safety research to prevent catastrophic mistakes that transcend national borders. For those who think that international treaties will not work While challenging, international treaties on AI safety are essential and feasible, especially with mechanisms like hardware-enabled governance. For those who think the genie is out of the bottle and we should just let go and avoid regulation Despite AI's unstoppable progress, regulation and safety measures are still critical to steer AI development towards positive outcomes. For those who think that open-source AGI code and weights are the solution Open-sourcing AI has benefits but also significant risks, requiring careful consideration and governance to prevent misuse and loss of control. For those who think worrying about AGI is falling for Pascal’s wager Bengio argues that AI risks are substantial and non-negligible, warranting serious attention and proactive mitigation efforts. Conclusion Bengio emphasizes the need for a collective, cautious approach to AI development, balancing the pursuit of benefits with rigorous safety measures to prevent catastrophic outcomes.

[P] Jarvislabs.ai - An Affordable GPU Cloud with Fast launch, Pause and Resume. Scale GPUs post creation. A100/RTX6K/RTX5K
reddit
LLM Vibe Score0
Human Vibe Score1
vishnu_subramaniannThis week

[P] Jarvislabs.ai - An Affordable GPU Cloud with Fast launch, Pause and Resume. Scale GPUs post creation. A100/RTX6K/RTX5K

For the last few years, I have been learning and practicing Deep Learning. Participated in several Kaggle competitions and won few medals. During all these years, I tried several cloud platforms and on-premise systems. Some of them offered simplicity, flexibility, and affordability. But very few to none offered all of these in one platform. After struggling with different platforms, I know what I would need as a DL researcher. That gave birth to jarvislabs.ai with the aim of being simple and affordable. I along with my friends started working on this project a year back. Due to Covid, executing the project became more challenging. As first-time entrepreneurs, we underestimated the complexity of the problem at hand but with persistence, we were able to launch a beta version of the product in December 2020. With some of the amazing feedback from our early adopters, we have been able to make the product smoother. We would love to invite you all to come and try the platform. Features 1 click Jupyter Lab < \[30 seconds\] Pause the instance and Resume from where you left. SSH to the instance. Scale GPUs, storage and change GPU type on resume. Auto-Pause using jarviscloud.pause() in your code, so you can catch up some good night’s sleep while your model trains. Pay per usage – Minute Billing \[After first 15 minutes\] Competitive pricing \[Lowest to our Knowledge\]. &#x200B; Pricing |GPU Type|GPU RAM|Price -$/hr| |:-|:-|:-| |RTX 5000|16 GB|0.49| |RTX 6000|24 GB|0.99| |A100|40 GB|2.39| &#x200B; Talk to us We will be happy to assist you in spinning your first instance and many more. You can use one of these platforms to reach us. Chat option on cloud.jarvislabs.ai Email us - hello@jarvislabs.ai Comment here. We have come a long way, but we understand that a lot more has to be done. We have listed down all the upcoming product features here. Deep learning and AI are evolving and how we would use the cloud platforms could evolve in the coming years. Understanding this, we develop in the open by constantly keeping in touch with our users. Please help us in shaping Jarvislabs.ai with any valuable suggestions/feedback.

Interview with Juergen Schmidhuber, renowned ‘Father Of Modern AI’, says his life’s work won't lead to dystopia.
reddit
LLM Vibe Score0
Human Vibe Score0.765
hardmaruThis week

Interview with Juergen Schmidhuber, renowned ‘Father Of Modern AI’, says his life’s work won't lead to dystopia.

Schmidhuber interview expressing his views on the future of AI and AGI. Original source. I think the interview is of interest to r/MachineLearning, and presents an alternate view, compared to other influential leaders in AI. Juergen Schmidhuber, Renowned 'Father Of Modern AI,' Says His Life’s Work Won't Lead To Dystopia May 23, 2023. Contributed by Hessie Jones. Amid the growing concern about the impact of more advanced artificial intelligence (AI) technologies on society, there are many in the technology community who fear the implications of the advancements in Generative AI if they go unchecked. Dr. Juergen Schmidhuber, a renowned scientist, artificial intelligence researcher and widely regarded as one of the pioneers in the field, is more optimistic. He declares that many of those who suddenly warn against the dangers of AI are just seeking publicity, exploiting the media’s obsession with killer robots which has attracted more attention than “good AI” for healthcare etc. The potential to revolutionize various industries and improve our lives is clear, as are the equal dangers if bad actors leverage the technology for personal gain. Are we headed towards a dystopian future, or is there reason to be optimistic? I had a chance to sit down with Dr. Juergen Schmidhuber to understand his perspective on this seemingly fast-moving AI-train that will leap us into the future. As a teenager in the 1970s, Juergen Schmidhuber became fascinated with the idea of creating intelligent machines that could learn and improve on their own, becoming smarter than himself within his lifetime. This would ultimately lead to his groundbreaking work in the field of deep learning. In the 1980s, he studied computer science at the Technical University of Munich (TUM), where he earned his diploma in 1987. His thesis was on the ultimate self-improving machines that, not only, learn through some pre-wired human-designed learning algorithm, but also learn and improve the learning algorithm itself. Decades later, this became a hot topic. He also received his Ph.D. at TUM in 1991 for work that laid some of the foundations of modern AI. Schmidhuber is best known for his contributions to the development of recurrent neural networks (RNNs), the most powerful type of artificial neural network that can process sequential data such as speech and natural language. With his students Sepp Hochreiter, Felix Gers, Alex Graves, Daan Wierstra, and others, he published architectures and training algorithms for the long short-term memory (LSTM), a type of RNN that is widely used in natural language processing, speech recognition, video games, robotics, and other applications. LSTM has become the most cited neural network of the 20th century, and Business Week called it "arguably the most commercial AI achievement." Throughout his career, Schmidhuber has received various awards and accolades for his groundbreaking work. In 2013, he was awarded the Helmholtz Prize, which recognizes significant contributions to the field of machine learning. In 2016, he was awarded the IEEE Neural Network Pioneer Award for "pioneering contributions to deep learning and neural networks." The media have often called him the “father of modern AI,” because the most cited neural networks all build on his lab’s work. He is quick to point out, however, that AI history goes back centuries. Despite his many accomplishments, at the age of 60, he feels mounting time pressure towards building an Artificial General Intelligence within his lifetime and remains committed to pushing the boundaries of AI research and development. He is currently director of the KAUST AI Initiative, scientific director of the Swiss AI Lab IDSIA, and co-founder and chief scientist of AI company NNAISENSE, whose motto is "AI∀" which is a math-inspired way of saying "AI For All." He continues to work on cutting-edge AI technologies and applications to improve human health and extend human lives and make lives easier for everyone. The following interview has been edited for clarity. Jones: Thank you Juergen for joining me. You have signed letters warning about AI weapons. But you didn't sign the recent publication, "Pause Gigantic AI Experiments: An Open Letter"? Is there a reason? Schmidhuber: Thank you Hessie. Glad to speak with you. I have realized that many of those who warn in public against the dangers of AI are just seeking publicity. I don't think the latest letter will have any significant impact because many AI researchers, companies, and governments will ignore it completely. The proposal frequently uses the word "we" and refers to "us," the humans. But as I have pointed out many times in the past, there is no "we" that everyone can identify with. Ask 10 different people, and you will hear 10 different opinions about what is "good." Some of those opinions will be completely incompatible with each other. Don't forget the enormous amount of conflict between the many people. The letter also says, "If such a pause cannot be quickly put in place, governments should intervene and impose a moratorium." The problem is that different governments have ALSO different opinions about what is good for them and for others. Great Power A will say, if we don't do it, Great Power B will, perhaps secretly, and gain an advantage over us. The same is true for Great Powers C and D. Jones: Everyone acknowledges this fear surrounding current generative AI technology. Moreover, the existential threat of this technology has been publicly acknowledged by Sam Altman, CEO of OpenAI himself, calling for AI regulation. From your perspective, is there an existential threat? Schmidhuber: It is true that AI can be weaponized, and I have no doubt that there will be all kinds of AI arms races, but AI does not introduce a new quality of existential threat. The threat coming from AI weapons seems to pale in comparison to the much older threat from nuclear hydrogen bombs that don’t need AI at all. We should be much more afraid of half-century-old tech in the form of H-bomb rockets. The Tsar Bomba of 1961 had almost 15 times more destructive power than all weapons of WW-II combined. Despite the dramatic nuclear disarmament since the 1980s, there are still more than enough nuclear warheads to wipe out human civilization within two hours, without any AI I’m much more worried about that old existential threat than the rather harmless AI weapons. Jones: I realize that while you compare AI to the threat of nuclear bombs, there is a current danger that a current technology can be put in the hands of humans and enable them to “eventually” exact further harms to individuals of group in a very precise way, like targeted drone attacks. You are giving people a toolset that they've never had before, enabling bad actors, as some have pointed out, to be able to do a lot more than previously because they didn't have this technology. Schmidhuber: Now, all that sounds horrible in principle, but our existing laws are sufficient to deal with these new types of weapons enabled by AI. If you kill someone with a gun, you will go to jail. Same if you kill someone with one of these drones. Law enforcement will get better at understanding new threats and new weapons and will respond with better technology to combat these threats. Enabling drones to target persons from a distance in a way that requires some tracking and some intelligence to perform, which has traditionally been performed by skilled humans, to me, it seems is just an improved version of a traditional weapon, like a gun, which is, you know, a little bit smarter than the old guns. But, in principle, all of that is not a new development. For many centuries, we have had the evolution of better weaponry and deadlier poisons and so on, and law enforcement has evolved their policies to react to these threats over time. So, it's not that we suddenly have a new quality of existential threat and it's much more worrisome than what we have had for about six decades. A large nuclear warhead doesn’t need fancy face recognition to kill an individual. No, it simply wipes out an entire city with ten million inhabitants. Jones: The existential threat that’s implied is the extent to which humans have control over this technology. We see some early cases of opportunism which, as you say, tends to get more media attention than positive breakthroughs. But you’re implying that this will all balance out? Schmidhuber: Historically, we have a long tradition of technological breakthroughs that led to advancements in weapons for the purpose of defense but also for protection. From sticks, to rocks, to axes to gunpowder to cannons to rockets… and now to drones… this has had a drastic influence on human history but what has been consistent throughout history is that those who are using technology to achieve their own ends are themselves, facing the same technology because the opposing side is learning to use it against them. And that's what has been repeated in thousands of years of human history and it will continue. I don't see the new AI arms race as something that is remotely as existential a threat as the good old nuclear warheads. You said something important, in that some people prefer to talk about the downsides rather than the benefits of this technology, but that's misleading, because 95% of all AI research and AI development is about making people happier and advancing human life and health. Jones: Let’s touch on some of those beneficial advances in AI research that have been able to radically change present day methods and achieve breakthroughs. Schmidhuber: All right! For example, eleven years ago, our team with my postdoc Dan Ciresan was the first to win a medical imaging competition through deep learning. We analyzed female breast cells with the objective to determine harmless cells vs. those in the pre-cancer stage. Typically, a trained oncologist needs a long time to make these determinations. Our team, who knew nothing about cancer, were able to train an artificial neural network, which was totally dumb in the beginning, on lots of this kind of data. It was able to outperform all the other methods. Today, this is being used not only for breast cancer, but also for radiology and detecting plaque in arteries, and many other things. Some of the neural networks that we have developed in the last 3 decades are now prevalent across thousands of healthcare applications, detecting Diabetes and Covid-19 and what not. This will eventually permeate across all healthcare. The good consequences of this type of AI are much more important than the click-bait new ways of conducting crimes with AI. Jones: Adoption is a product of reinforced outcomes. The massive scale of adoption either leads us to believe that people have been led astray, or conversely, technology is having a positive effect on people’s lives. Schmidhuber: The latter is the likely case. There's intense commercial pressure towards good AI rather than bad AI because companies want to sell you something, and you are going to buy only stuff you think is going to be good for you. So already just through this simple, commercial pressure, you have a tremendous bias towards good AI rather than bad AI. However, doomsday scenarios like in Schwarzenegger movies grab more attention than documentaries on AI that improve people’s lives. Jones: I would argue that people are drawn to good stories – narratives that contain an adversary and struggle, but in the end, have happy endings. And this is consistent with your comment on human nature and how history, despite its tendency for violence and destruction of humanity, somehow tends to correct itself. Let’s take the example of a technology, which you are aware – GANs – General Adversarial Networks, which today has been used in applications for fake news and disinformation. In actuality, the purpose in the invention of GANs was far from what it is used for today. Schmidhuber: Yes, the name GANs was created in 2014 but we had the basic principle already in the early 1990s. More than 30 years ago, I called it artificial curiosity. It's a very simple way of injecting creativity into a little two network system. This creative AI is not just trying to slavishly imitate humans. Rather, it’s inventing its own goals. Let me explain: You have two networks. One network is producing outputs that could be anything, any action. Then the second network is looking at these actions and it’s trying to predict the consequences of these actions. An action could move a robot, then something happens, and the other network is just trying to predict what will happen. Now we can implement artificial curiosity by reducing the prediction error of the second network, which, at the same time, is the reward of the first network. The first network wants to maximize its reward and so it will invent actions that will lead to situations that will surprise the second network, which it has not yet learned to predict well. In the case where the outputs are fake images, the first network will try to generate images that are good enough to fool the second network, which will attempt to predict the reaction of the environment: fake or real image, and it will try to become better at it. The first network will continue to also improve at generating images whose type the second network will not be able to predict. So, they fight each other. The 2nd network will continue to reduce its prediction error, while the 1st network will attempt to maximize it. Through this zero-sum game the first network gets better and better at producing these convincing fake outputs which look almost realistic. So, once you have an interesting set of images by Vincent Van Gogh, you can generate new images that leverage his style, without the original artist having ever produced the artwork himself. Jones: I see how the Van Gogh example can be applied in an education setting and there are countless examples of artists mimicking styles from famous painters but image generation from this instance that can happen within seconds is quite another feat. And you know this is how GANs has been used. What’s more prevalent today is a socialized enablement of generating images or information to intentionally fool people. It also surfaces new harms that deal with the threat to intellectual property and copyright, where laws have yet to account for. And from your perspective this was not the intention when the model was conceived. What was your motivation in your early conception of what is now GANs? Schmidhuber: My old motivation for GANs was actually very important and it was not to create deepfakes or fake news but to enable AIs to be curious and invent their own goals, to make them explore their environment and make them creative. Suppose you have a robot that executes one action, then something happens, then it executes another action, and so on, because it wants to achieve certain goals in the environment. For example, when the battery is low, this will trigger “pain” through hunger sensors, so it wants to go to the charging station, without running into obstacles, which will trigger other pain sensors. It will seek to minimize pain (encoded through numbers). Now the robot has a friend, the second network, which is a world model ––it’s a prediction machine that learns to predict the consequences of the robot’s actions. Once the robot has a good model of the world, it can use it for planning. It can be used as a simulation of the real world. And then it can determine what is a good action sequence. If the robot imagines this sequence of actions, the model will predict a lot of pain, which it wants to avoid. If it plays this alternative action sequence in its mental model of the world, then it will predict a rewarding situation where it’s going to sit on the charging station and its battery is going to load again. So, it'll prefer to execute the latter action sequence. In the beginning, however, the model of the world knows nothing, so how can we motivate the first network to generate experiments that lead to data that helps the world model learn something it didn’t already know? That’s what artificial curiosity is about. The dueling two network systems effectively explore uncharted environments by creating experiments so that over time the curious AI gets a better sense of how the environment works. This can be applied to all kinds of environments, and has medical applications. Jones: Let’s talk about the future. You have said, “Traditional humans won’t play a significant role in spreading intelligence across the universe.” Schmidhuber: Let’s first conceptually separate two types of AIs. The first type of AI are tools directed by humans. They are trained to do specific things like accurately detect diabetes or heart disease and prevent attacks before they happen. In these cases, the goal is coming from the human. More interesting AIs are setting their own goals. They are inventing their own experiments and learning from them. Their horizons expand and eventually they become more and more general problem solvers in the real world. They are not controlled by their parents, but much of what they learn is through self-invented experiments. A robot, for example, is rotating a toy, and as it is doing this, the video coming in through the camera eyes, changes over time and it begins to learn how this video changes and learns how the 3D nature of the toy generates certain videos if you rotate it a certain way, and eventually, how gravity works, and how the physics of the world works. Like a little scientist! And I have predicted for decades that future scaled-up versions of such AI scientists will want to further expand their horizons, and eventually go where most of the physical resources are, to build more and bigger AIs. And of course, almost all of these resources are far away from earth out there in space, which is hostile to humans but friendly to appropriately designed AI-controlled robots and self-replicating robot factories. So here we are not talking any longer about our tiny biosphere; no, we are talking about the much bigger rest of the universe. Within a few tens of billions of years, curious self-improving AIs will colonize the visible cosmos in a way that’s infeasible for humans. Those who don’t won’t have an impact. Sounds like science fiction, but since the 1970s I have been unable to see a plausible alternative to this scenario, except for a global catastrophe such as an all-out nuclear war that stops this development before it takes off. Jones: How long have these AIs, which can set their own goals — how long have they existed? To what extent can they be independent of human interaction? Schmidhuber: Neural networks like that have existed for over 30 years. My first simple adversarial neural network system of this kind is the one from 1990 described above. You don’t need a teacher there; it's just a little agent running around in the world and trying to invent new experiments that surprise its own prediction machine. Once it has figured out certain parts of the world, the agent will become bored and will move on to more exciting experiments. The simple 1990 systems I mentioned have certain limitations, but in the past three decades, we have also built more sophisticated systems that are setting their own goals and such systems I think will be essential for achieving true intelligence. If you are only imitating humans, you will never go beyond them. So, you really must give AIs the freedom to explore previously unexplored regions of the world in a way that no human is really predefining. Jones: Where is this being done today? Schmidhuber: Variants of neural network-based artificial curiosity are used today for agents that learn to play video games in a human-competitive way. We have also started to use them for automatic design of experiments in fields such as materials science. I bet many other fields will be affected by it: chemistry, biology, drug design, you name it. However, at least for now, these artificial scientists, as I like to call them, cannot yet compete with human scientists. I don’t think it’s going to stay this way but, at the moment, it’s still the case. Sure, AI has made a lot of progress. Since 1997, there have been superhuman chess players, and since 2011, through the DanNet of my team, there have been superhuman visual pattern recognizers. But there are other things where humans, at the moment at least, are much better, in particular, science itself. In the lab we have many first examples of self-directed artificial scientists, but they are not yet convincing enough to appear on the radar screen of the public space, which is currently much more fascinated with simpler systems that just imitate humans and write texts based on previously seen human-written documents. Jones: You speak of these numerous instances dating back 30 years of these lab experiments where these self-driven agents are deciding and learning and moving on once they’ve learned. And I assume that that rate of learning becomes even faster over time. What kind of timeframe are we talking about when this eventually is taken outside of the lab and embedded into society? Schmidhuber: This could still take months or even years :-) Anyway, in the not-too-distant future, we will probably see artificial scientists who are good at devising experiments that allow them to discover new, previously unknown physical laws. As always, we are going to profit from the old trend that has held at least since 1941: every decade compute is getting 100 times cheaper. Jones: How does this trend affect modern AI such as ChatGPT? Schmidhuber: Perhaps you know that all the recent famous AI applications such as ChatGPT and similar models are largely based on principles of artificial neural networks invented in the previous millennium. The main reason why they works so well now is the incredible acceleration of compute per dollar. ChatGPT is driven by a neural network called “Transformer” described in 2017 by Google. I am happy about that because a quarter century earlier in 1991 I had a particular Transformer variant which is now called the “Transformer with linearized self-attention”. Back then, not much could be done with it, because the compute cost was a million times higher than today. But today, one can train such models on half the internet and achieve much more interesting results. Jones: And for how long will this acceleration continue? Schmidhuber: There's no reason to believe that in the next 30 years, we won't have another factor of 1 million and that's going to be really significant. In the near future, for the first time we will have many not-so expensive devices that can compute as much as a human brain. The physical limits of computation, however, are much further out so even if the trend of a factor of 100 every decade continues, the physical limits (of 1051 elementary instructions per second and kilogram of matter) won’t be hit until, say, the mid-next century. Even in our current century, however, we’ll probably have many machines that compute more than all 10 billion human brains collectively and you can imagine, everything will change then! Jones: That is the big question. Is everything going to change? If so, what do you say to the next generation of leaders, currently coming out of college and university. So much of this change is already impacting how they study, how they will work, or how the future of work and livelihood is defined. What is their purpose and how do we change our systems so they will adapt to this new version of intelligence? Schmidhuber: For decades, people have asked me questions like that, because you know what I'm saying now, I have basically said since the 1970s, it’s just that today, people are paying more attention because, back then, they thought this was science fiction. They didn't think that I would ever come close to achieving my crazy life goal of building a machine that learns to become smarter than myself such that I can retire. But now many have changed their minds and think it's conceivable. And now I have two daughters, 23 and 25. People ask me: what do I tell them? They know that Daddy always said, “It seems likely that within your lifetimes, you will have new types of intelligence that are probably going to be superior in many ways, and probably all kinds of interesting ways.” How should they prepare for that? And I kept telling them the obvious: Learn how to learn new things! It's not like in the previous millennium where within 20 years someone learned to be a useful member of society, and then took a job for 40 years and performed in this job until she received her pension. Now things are changing much faster and we must learn continuously just to keep up. I also told my girls that no matter how smart AIs are going to get, learn at least the basics of math and physics, because that’s the essence of our universe, and anybody who understands this will have an advantage, and learn all kinds of new things more easily. I also told them that social skills will remain important, because most future jobs for humans will continue to involve interactions with other humans, but I couldn’t teach them anything about that; they know much more about social skills than I do. You touched on the big philosophical question about people’s purpose. Can this be answered without answering the even grander question: What’s the purpose of the entire universe? We don’t know. But what’s happening right now might be connected to the unknown answer. Don’t think of humans as the crown of creation. Instead view human civilization as part of a much grander scheme, an important step (but not the last one) on the path of the universe from very simple initial conditions towards more and more unfathomable complexity. Now it seems ready to take its next step, a step comparable to the invention of life itself over 3.5 billion years ago. Alas, don’t worry, in the end, all will be good! Jones: Let’s get back to this transformation happening right now with OpenAI. There are many questioning the efficacy and accuracy of ChatGPT, and are concerned its release has been premature. In light of the rampant adoption, educators have banned its use over concerns of plagiarism and how it stifles individual development. Should large language models like ChatGPT be used in school? Schmidhuber: When the calculator was first introduced, instructors forbade students from using it in school. Today, the consensus is that kids should learn the basic methods of arithmetic, but they should also learn to use the “artificial multipliers” aka calculators, even in exams, because laziness and efficiency is a hallmark of intelligence. Any intelligent being wants to minimize its efforts to achieve things. And that's the reason why we have tools, and why our kids are learning to use these tools. The first stone tools were invented maybe 3.5 million years ago; tools just have become more sophisticated over time. In fact, humans have changed in response to the properties of their tools. Our anatomical evolution was shaped by tools such as spears and fire. So, it's going to continue this way. And there is no permanent way of preventing large language models from being used in school. Jones: And when our children, your children graduate, what does their future work look like? Schmidhuber: A single human trying to predict details of how 10 billion people and their machines will evolve in the future is like a single neuron in my brain trying to predict what the entire brain and its tens of billions of neurons will do next year. 40 years ago, before the WWW was created at CERN in Switzerland, who would have predicted all those young people making money as YouTube video bloggers? Nevertheless, let’s make a few limited job-related observations. For a long time, people have thought that desktop jobs may require more intelligence than skills trade or handicraft professions. But now, it turns out that it's much easier to replace certain aspects of desktop jobs than replacing a carpenter, for example. Because everything that works well in AI is happening behind the screen currently, but not so much in the physical world. There are now artificial systems that can read lots of documents and then make really nice summaries of these documents. That is a desktop job. Or you give them a description of an illustration that you want to have for your article and pretty good illustrations are being generated that may need some minimal fine-tuning. But you know, all these desktop jobs are much easier to facilitate than the real tough jobs in the physical world. And it's interesting that the things people thought required intelligence, like playing chess, or writing or summarizing documents, are much easier for machines than they thought. But for things like playing football or soccer, there is no physical robot that can remotely compete with the abilities of a little boy with these skills. So, AI in the physical world, interestingly, is much harder than AI behind the screen in virtual worlds. And it's really exciting, in my opinion, to see that jobs such as plumbers are much more challenging than playing chess or writing another tabloid story. Jones: The way data has been collected in these large language models does not guarantee personal information has not been excluded. Current consent laws already are outdated when it comes to these large language models (LLM). The concern, rightly so, is increasing surveillance and loss of privacy. What is your view on this? Schmidhuber: As I have indicated earlier: are surveillance and loss of privacy inevitable consequences of increasingly complex societies? Super-organisms such as cities and states and companies consist of numerous people, just like people consist of numerous cells. These cells enjoy little privacy. They are constantly monitored by specialized "police cells" and "border guard cells": Are you a cancer cell? Are you an external intruder, a pathogen? Individual cells sacrifice their freedom for the benefits of being part of a multicellular organism. Similarly, for super-organisms such as nations. Over 5000 years ago, writing enabled recorded history and thus became its inaugural and most important invention. Its initial purpose, however, was to facilitate surveillance, to track citizens and their tax payments. The more complex a super-organism, the more comprehensive its collection of information about its constituents. 200 years ago, at least, the parish priest in each village knew everything about all the village people, even about those who did not confess, because they appeared in the confessions of others. Also, everyone soon knew about the stranger who had entered the village, because some occasionally peered out of the window, and what they saw got around. Such control mechanisms were temporarily lost through anonymization in rapidly growing cities but are now returning with the help of new surveillance devices such as smartphones as part of digital nervous systems that tell companies and governments a lot about billions of users. Cameras and drones etc. are becoming increasingly tinier and more ubiquitous. More effective recognition of faces and other detection technology are becoming cheaper and cheaper, and many will use it to identify others anywhere on earth; the big wide world will not offer any more privacy than the local village. Is this good or bad? Some nations may find it easier than others to justify more complex kinds of super-organisms at the expense of the privacy rights of their constituents. Jones: So, there is no way to stop or change this process of collection, or how it continuously informs decisions over time? How do you see governance and rules responding to this, especially amid Italy’s ban on ChatGPT following suspected user data breach and the more recent news about the Meta’s record $1.3billion fine in the company’s handling of user information? Schmidhuber: Data collection has benefits and drawbacks, such as the loss of privacy. How to balance those? I have argued for addressing this through data ownership in data markets. If it is true that data is the new oil, then it should have a price, just like oil. At the moment, the major surveillance platforms such as Meta do not offer users any money for their data and the transitive loss of privacy. In the future, however, we will likely see attempts at creating efficient data markets to figure out the data's true financial value through the interplay between supply and demand. Even some of the sensitive medical data should not be priced by governmental regulators but by patients (and healthy persons) who own it and who may sell or license parts thereof as micro-entrepreneurs in a healthcare data market. Following a previous interview, I gave for one of the largest re-insurance companies , let's look at the different participants in such a data market: patients, hospitals, data companies. (1) Patients with a rare form of cancer can offer more valuable data than patients with a very common form of cancer. (2) Hospitals and their machines are needed to extract the data, e.g., through magnet spin tomography, radiology, evaluations through human doctors, and so on. (3) Companies such as Siemens, Google or IBM would like to buy annotated data to make better artificial neural networks that learn to predict pathologies and diseases and the consequences of therapies. Now the market’s invisible hand will decide about the data’s price through the interplay between demand and supply. On the demand side, you will have several companies offering something for the data, maybe through an app on the smartphone (a bit like a stock market app). On the supply side, each patient in this market should be able to profit from high prices for rare valuable types of data. Likewise, competing data extractors such as hospitals will profit from gaining recognition and trust for extracting data well at a reasonable price. The market will make the whole system efficient through incentives for all who are doing a good job. Soon there will be a flourishing ecosystem of commercial data market advisors and what not, just like the ecosystem surrounding the traditional stock market. The value of the data won’t be determined by governments or ethics committees, but by those who own the data and decide by themselves which parts thereof they want to license to others under certain conditions. At first glance, a market-based system seems to be detrimental to the interest of certain monopolistic companies, as they would have to pay for the data - some would prefer free data and keep their monopoly. However, since every healthy and sick person in the market would suddenly have an incentive to collect and share their data under self-chosen anonymity conditions, there will soon be many more useful data to evaluate all kinds of treatments. On average, people will live longer and healthier, and many companies and the entire healthcare system will benefit. Jones: Finally, what is your view on open source versus the private companies like Google and OpenAI? Is there a danger to supporting these private companies’ large language models versus trying to keep these models open source and transparent, very much like what LAION is doing? Schmidhuber: I signed this open letter by LAION because I strongly favor the open-source movement. And I think it's also something that is going to challenge whatever big tech dominance there might be at the moment. Sure, the best models today are run by big companies with huge budgets for computers, but the exciting fact is that open-source models are not so far behind, some people say maybe six to eight months only. Of course, the private company models are all based on stuff that was created in academia, often in little labs without so much funding, which publish without patenting their results and open source their code and others take it and improved it. Big tech has profited tremendously from academia; their main achievement being that they have scaled up everything greatly, sometimes even failing to credit the original inventors. So, it's very interesting to see that as soon as some big company comes up with a new scaled-up model, lots of students out there are competing, or collaborating, with each other, trying to come up with equal or better performance on smaller networks and smaller machines. And since they are open sourcing, the next guy can have another great idea to improve it, so now there’s tremendous competition also for the big companies. Because of that, and since AI is still getting exponentially cheaper all the time, I don't believe that big tech companies will dominate in the long run. They find it very hard to compete with the enormous open-source movement. As long as you can encourage the open-source community, I think you shouldn't worry too much. Now, of course, you might say if everything is open source, then the bad actors also will more easily have access to these AI tools. And there's truth to that. But as always since the invention of controlled fire, it was good that knowledge about how technology works quickly became public such that everybody could use it. And then, against any bad actor, there's almost immediately a counter actor trying to nullify his efforts. You see, I still believe in our old motto "AI∀" or "AI For All." Jones: Thank you, Juergen for sharing your perspective on this amazing time in history. It’s clear that with new technology, the enormous potential can be matched by disparate and troubling risks which we’ve yet to solve, and even those we have yet to identify. If we are to dispel the fear of a sentient system for which we have no control, humans, alone need to take steps for more responsible development and collaboration to ensure AI technology is used to ultimately benefit society. Humanity will be judged by what we do next.

[R] From 3D Contour Plots to AI-Generated Art
reddit
LLM Vibe Score0
Human Vibe Score1
MLRecipesThis week

[R] From 3D Contour Plots to AI-Generated Art

Fun tutorial to learn how to make professional contour plots in Python, with incredible animated visualizations. At the intersection of machine learning, scientific computing, automated art, cartography, and video games. Section 3 is particularly interesting, as it shows all the work behind the scene, to complete this project in 20 hours when you have no idea how to start. https://reddit.com/link/ycg6c6/video/kycotrx09sv91/player There is far more than just creating 3D contour plots in this article. First, you will learn how to produce data videos. I have shared quite a few in the past (with source code), but this is probably the simplest example. The data video also illustrates that a mixture of Gaussian-like distributions is typically non Gaussian-like, and may or may not be unimodal. It is borderline art (automatically generated), and certainly a stepping stone for professionals interested in computer vision or designing video games. It is easy to image a game based on my video, entitled “flying above menacingly rising mountains”. Then the data video, through various rotations, give you a much better view of your data. It is also perfect to show systems that evolve over time: a time series where each observation is an image. In addition, unlike most tutorials found online, this one does a rather deep dive on a specific, rather advanced function from a library truly aimed at scientific computing. In the same way that images (say pictures of hand-written digits) can be summarized by 10 parameters to perform text recognition, here 20 parameters allow you to perform topography classification. Not just of static terrain, but terrain that changes over time, assuming you have access to 50,000 videos representing different topographies. You can produce the videos needed for supervised classification with the code in section 2. The next step is to use data (videos) from the real world, and used the model trained on synthetic data for classification. Read the full article with illustration (data video) and Python code, here.

[N] TheSequence Scope: When it comes to machine learning, size matters: Microsoft's DeepSpeed framework, which can train a model with up to a trillion parameters
reddit
LLM Vibe Score0
Human Vibe Score1
KseniaseThis week

[N] TheSequence Scope: When it comes to machine learning, size matters: Microsoft's DeepSpeed framework, which can train a model with up to a trillion parameters

Hi there! Offering to your attention the latest edition of a weekly ML-newsletter that focusing on three things: impactful ML research papers, cool ML tech solutions, and ML use cases supported by investors. Please, see it below. Reddit is a new thing for me, and I've been struggling a bit with it, so please don't judge me too harsh for this promotion. This weekly digest is free and I hope you'd find the format convenient for you. Your feedback is very appreciated, and please feel free to sign up if you like it. 📝 Editorial  The recent emergence of pre-trained language models and transformer architectures pushed the creation of larger and larger machine learning models. Google’s BERT presented attention mechanism and transformer architecture possibilities as the “next big thing” in ML, and the numbers seem surreal. OpenAI’s GPT-2 set a record by processing 1.5 billion parameters, followed by Microsoft’s Turing-NLG, which processed 17 billion parameters just to see the new GPT-3 processing an astonishing 175 billion parameters. To not feel complacent, just this week Microsoft announced a new release of its DeepSpeed framework (which powers Turing-NLG), which can train a model with up to a trillion parameters. That sounds insane but it really isn’t.   What we are seeing is a consequence of several factors. First, computation power and parallelization techniques have evolved to a point where it is relatively easy to train machine learning models in large clusters of machines. Second and most importantly, in the current state of machine learning, larger models have regularly outperformed smaller and more specialized models. Knowledge reusability methods like transfer learning are still in very nascent stages. As a result, it’s really hard to build small models that can operate in uncertain environments. Furthermore, as models like GPT-3 and Turing-NLG have shown, there is some unexplainable magic that happens after models go past a certain size. Many of the immediate machine learning problems might be solved by scaling the current generation of neural network architectures. Plain and simple, when it comes to machine learning, size matters.   We would love to hear your opinions about the debate between broader-larger vs. smaller and more specialized models.   Leave a comment Now, to the most important developments in the AI industry this week 🔎 ML Research GPT-3 Falls Short in Machine Comprehension Proposed by researchers from a few major American universities, a 57-task test to measure models’ ability to reason poses challenges even for sophisticated models like GPT-3 ->read more in the original paper Better Text Summarization OpenAI published a paper showing a reinforcement learning with human feedback technique that can surpass supervised models ->read more on OpenAI blog Reinforcement Learning with Offline Datasets Researchers from the Berkeley AI Research (BAIR) Lab published a paper unveiling a method that uses offline datasets to improve reinforcement learning models->read more on BAIR blog 🤖 Cool AI Tech Releases New Version of DeepSpeed Microsoft open-sourced a new version of DeepSpeed, an open-source library for parallelizable training that can scale up to models with 1 trillion parameters->read more on Microsoft Research blog 💸 Money in AI AI-powered customer experience management platform Sprinklr has raised $200 million (kudos to our subscribers from Sprinklr 👏). Sprinklr's “AI listening processing” solution allows companies to get structured and meaningful sentiments and insights from unstructured customer data that comes from public conversations on different websites and social platforms. Xometry, an on-demand industrial parts marketplace, raises $75 million in Series E funding. The company provides a digital way of creating the right combination of buyers and manufacturers. Another example of AI implementation into matching two sides for a deal. Real estate tech company Orchard raises $69 million in its recent funding round. Orchard aims to digitize the whole real estate market, by developing a solution that combines machine learning and rapid human assistance to smooth the search, match the right deal, and simplify buying and selling relationships. Cybersecurity startup Pcysys raised $25 million in its funding round. Pcysys’ platform, which doesn’t require installation or network reconfiguration, uses algorithms to scan and “ethically” attack enterprise networks. Robotics farming company Iron Ox raised $20 million in a funding round. The system of farming robots is still semi-autonomous, the company’s goal is to become fully autonomous.  Insurtech company Descartes Underwriting raised $18.5 million. The company applies AI and machine learning technologies to climate risk predicting and insurance underwriting. Legaltech startup ThoughtRiver raised $10 million in its Series A round. Its AI solution applied to contract pre-screening aims to boost operational efficiency. Medtech startup Skin Analytics raised $5.1 million in Series A funding. Skin Analytics has developed a clinically validated AI system that can identify not only the important skin cancers but also precancerous lesions that can be treated, as well as a range of lesions that are benign. Amazon, along with several government organizations and three other industry partners, helped fund the National Science Foundation, a high-priority AI research initiative. The amount of funding is not disclosed. The content of TheSequence is written by Jesus Rodriguez, one of the most-read contributors to KDNuggets and TDS. You can check his Medium here.

[D] Should We Be Concerned About The Failure Of Evolutionary Algorithms, And Its Implications?
reddit
LLM Vibe Score0
Human Vibe Score-1
mystikaldangerThis week

[D] Should We Be Concerned About The Failure Of Evolutionary Algorithms, And Its Implications?

https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6287292/ &#x200B; A number of possible explanations for \[why we can't evolve complex software\] could be considered. We tried to be as comprehensive as possible in this section, but it is possible that we have not considered some plausible explanations: Incompetent programmers—It is theoretically possible, but is highly unlikely, that out of thousands of scientists working on evolutionary computation, all failed to correctly implement the Darwinian algorithm. Nonrepresentative algorithms—Some have suggested that EAs do not accurately capture the theory of evolution, but of course that would imply that the theory itself is not specified in sufficient detail to make falsifiable predictions. If, however, such more detailed specifications are available to GP believers, it is up to them to implement them as computer simulations for testing purposes, but no successful examples of such work are known and the known ones have not been successful in evolving software. Inadequate fitness functions—Fitness function for a complex software product is difficult to outline and specify and may be as complex (or even more complex) as the software we want to evolve as it has to consider all the possible use cases and pass all unit tests. This may be the Achilles heel of GP, but it is also an objection to feasibility of programming in general and GP in particular, as both have to convert software specification into the source code. If human programmers and biological evolution succeed with such constraints, so should Darwinian simulations. The Halting problem—Turing proved that it is impossible to determine whether an arbitrary program halts, but this is also a problem for human programmers and could be easily addressed by placing time limits on considered solutions. Program correctness—If we require evolved software to be provably correct, this would present a problem as GP does not verify produced designs but only tests them against specific unit tests. Likewise, we cannot rely on automated software verification as it is still an unsolved problem in the general case. This is not really a problem as most of the human-written software is never proven to be correct and only a small portion of software engineering process relies of formal specification and Test Driven Development. Inappropriate solutions—Literature on EA is full of examples of surprising creativity of Darwinian algorithm resulting in solutions which match the letter of design specifications but not the spirit. This is similar to human-produced software and numerous examples of ways in which such software fails the goals of the initial design. Insufficient complexity of the environment (not enough data, poor fitness functions)—It is possible that the simulated environment is not complex enough to generate high complexity outputs in evolutionary simulations. This does not seem correct as Internet presents a highly complex landscape in which many self-modifying computer viruses roam. Likewise, virtual world such as Second Life and many others present close approximations to the real world and are certainly more complex than early Earth was: A skeptic might insist that an abstract environment would be inadequate for the evolution . . ., believing instead that the virtual environment would need to closely resemble the actual biological environment in which our ancestors evolved. Creating a physically realistic virtual world would require a far greater investment of computational resources than the simulation of a simple toy world or abstract problem domain (whereas evolution had access to a physically realistic real world “for free”). In the limiting case, if complete microphysical accuracy were insisted upon, the computational requirements would balloon to utterly infeasible proportions. Requiring more realistic environmental conditions may result in an increase in necessary computational resources, a problem addressed in the next bullet. Insufficient resources (compute, memory)—From the history of computer science, we know of many situations (speech recognition, NN training), where we had a correct algorithm but insufficient computational resources to run it to success. It is possible that we simply do not have hardware powerful enough to emulate evolution. We will address this possibility in section “Computational Complexity of Biological Evolution and Available Compute.” Software design is not amenable to evolutionary methods—Space of software designs may be discrete with no continuous path via incremental fitness to the desired solutions. This is possible, but this implies that original goals of GP are unattainable and misguided. In addition, because a clear mapping exists between solutions to problems and animals as solutions to environmental problems, this would also imply that current explanation for the origin of the species is incorrect. Darwinian algorithm is incomplete or wrong—Finally, we have to consider the possibility that the inspiration behind evolutionary computation, the Darwinian algorithm itself is wrong or at least partially incomplete. If that was true, computer simulations of such algorithm would fail to produce results comparable with observations we see in nature and a search for an alternative algorithm would need to take place. This would be an extraordinary claim and would require that we discard all the other possible explanations from this list. We challenge EA community to prove us wrong by producing an experiment, which evolves nontrivial software from scratch and without human help. That would be the only way in which our findings could be shown to be incorrect. Perhaps, reframing the problem in terms of maximizing negentropy of digital organisms, as suggested by Schrödinger, Michaelian, and Ulanowicz and Hannon, with respect to negative energy being a fundamental property of all life-forms may produce better results. On a positive side, the fact that it seems impossible to evolve complex software implies that we are unlikely to be able to evolve highly sophisticated artificially intelligent agents, which may present significant risk to our safety and security. Just imagine what would have happened, if the very first time we ran a simulation of evolution on a computer, it produced a superintelligent agent. Yampolskiy has shown that programming as a problem is AI-complete; if GP can solve programming that would imply that GP = AGI (artificial general intelligence), but we see no experimental evidence for such claim. In fact, it is more likely that once we have AGI, it could be used to create an intelligent fitness function for GP and so evolve software. Genetic programming will not be the cause of AI, but a product of it. However, neuroevolution methods for optimizing deep learning architectures and parameters remain a strong possibility for creation of AGI.

[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore
reddit
LLM Vibe Score0
Human Vibe Score1
qazmkoppThis week

[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore

A few days ago, HuggingFace announced a $100 million Series C funding round, which was big news in open source machine learning and could be a sign of where the industry is headed. Two days before the HuggingFace funding announcement, open-source machine learning platform MetaSpore released a demo based on the HuggingFace Rapid deployment pre-training model. As deep learning technology makes innovative breakthroughs in computer vision, natural language processing, speech understanding, and other fields, more and more unstructured data are perceived, understood, and processed by machines. These advances are mainly due to the powerful learning ability of deep learning. Through pre-training of deep models on massive data, the models can capture the internal data patterns, thus helping many downstream tasks. With the industry and academia investing more and more energy in the research of pre-training technology, the distribution warehouses of pre-training models such as HuggingFace and Timm have emerged one after another. The open-source community release pre-training significant model dividends at an unprecedented speed. In recent years, the data form of machine modeling and understanding has gradually evolved from single-mode to multi-mode, and the semantic gap between different modes is being eliminated, making it possible to retrieve data across modes. Take CLIP, OpenAI’s open-source work, as an example, to pre-train the twin towers of images and texts on a dataset of 400 million pictures and texts and connect the semantics between pictures and texts. Many researchers in the academic world have been solving multimodal problems such as image generation and retrieval based on this technology. Although the frontier technology through the semantic gap between modal data, there is still a heavy and complicated model tuning, offline data processing, high performance online reasoning architecture design, heterogeneous computing, and online algorithm be born multiple processes and challenges, hindering the frontier multimodal retrieval technologies fall to the ground and pratt &whitney. DMetaSoul aims at the above technical pain points, abstracting and uniting many links such as model training optimization, online reasoning, and algorithm experiment, forming a set of solutions that can quickly apply offline pre-training model to online. This paper will introduce how to use the HuggingFace community pre-training model to conduct online reasoning and algorithm experiments based on MetaSpore technology ecology so that the benefits of the pre-training model can be fully released to the specific business or industry and small and medium-sized enterprises. And we will give the text search text and text search graph two multimodal retrieval demonstration examples for your reference. Multimodal semantic retrieval The sample architecture of multimodal retrieval is as follows: Our multimodal retrieval system supports both text search and text search application scenarios, including offline processing, model reasoning, online services, and other core modules: &#x200B; https://preview.redd.it/w4v4c7vcez291.png?width=1834&format=png&auto=webp&s=0687efb1fddb26e8e30cb844d398ec712b947f31 Offline processing, including offline data processing processes for different application scenarios of text search and text search, including model tuning, model export, data index database construction, data push, etc. Model inference. After the offline model training, we deployed our NLP and CV large models based on the MetaSpore Serving framework. MetaSpore Serving helps us conveniently perform online inference, elastic scheduling, load balancing, and resource scheduling in heterogeneous environments. Online services. Based on MetaSpore’s online algorithm application framework, MetaSpore has a complete set of reusable online search services, including Front-end retrieval UI, multimodal data preprocessing, vector recall and sorting algorithm, AB experimental framework, etc. MetaSpore also supports text search by text and image scene search by text and can be migrated to other application scenarios at a low cost. The HuggingFace open source community has provided several excellent baseline models for similar multimodal retrieval problems, which are often the starting point for actual optimization in the industry. MetaSpore also uses the pre-training model of the HuggingFace community in its online services of searching words by words and images by words. Searching words by words is based on the semantic similarity model of the question and answer field optimized by MetaSpore, and searching images by words is based on the community pre-training model. These community open source pre-training models are exported to the general ONNX format and loaded into MetaSpore Serving for online reasoning. The following sections will provide a detailed description of the model export and online retrieval algorithm services. The reasoning part of the model is standardized SAAS services with low coupling with the business. Interested readers can refer to my previous post: The design concept of MetaSpore, a new generation of the one-stop machine learning platform. 1.1 Offline Processing Offline processing mainly involves the export and loading of online models and index building and pushing of the document library. You can follow the step-by-step instructions below to complete the offline processing of text search and image search and see how the offline pre-training model achieves reasoning at MetaSpore. 1.1.1 Search text by text Traditional text retrieval systems are based on literal matching algorithms such as BM25. Due to users’ diverse query words, a semantic gap between query words and documents is often encountered. For example, users misspell “iPhone” as “Phone,” and search terms are incredibly long, such as “1 \~ 3 months old baby autumn small size bag pants”. Traditional text retrieval systems will use spelling correction, synonym expansion, search terms rewriting, and other means to alleviate the semantic gap but fundamentally fail to solve this problem. Only when the retrieval system fully understands users’ query terms and documents can it meet users’ retrieval demands at the semantic level. With the continuous progress of pre-training and representational learning technology, some commercial search engines continue to integrate semantic vector retrieval methods based on symbolic learning into the retrieval ecology. Semantic retrieval model This paper introduces a set of semantic vector retrieval applications. MetaSpore built a set of semantic retrieval systems based on encyclopedia question and answer data. MetaSpore adopted the Sentence-Bert model as the semantic vector representation model, which fine-tunes the twin tower BERT in supervised or unsupervised ways to make the model more suitable for retrieval tasks. The model structure is as follows: The query-Doc symmetric two-tower model is used in text search and question and answer retrieval. The vector representation of online Query and offline DOC share the same vector representation model, so it is necessary to ensure the consistency of the offline DOC library building model and online Query inference model. The case uses MetaSpore’s text representation model Sbert-Chinese-QMC-domain-V1, optimized in the open-source semantically similar data set. This model will express the question and answer data as a vector in offline database construction. The user query will be expressed as a vector by this model in online retrieval, ensuring that query-doc in the same semantic space, users’ semantic retrieval demands can be guaranteed by vector similarity metric calculation. Since the text presentation model does vector encoding for Query online, we need to export the model for use by the online service. Go to the q&A data library code directory and export the model concerning the documentation. In the script, Pytorch Tracing is used to export the model. The models are exported to the “./export “directory. The exported models are mainly ONNX models used for wired reasoning, Tokenizer, and related configuration files. The exported models are loaded into MetaSpore Serving by the online Serving system described below for model reasoning. Since the exported model will be copied to the cloud storage, you need to configure related variables in env.sh. \Build library based on text search \ The retrieval database is built on the million-level encyclopedia question and answer data set. According to the description document, you need to download the data and complete the database construction. The question and answer data will be coded as a vector by the offline model, and then the database construction data will be pushed to the service component. The whole process of database construction is described as follows: Preprocessing, converting the original data into a more general JSonline format for database construction; Build index, use the same model as online “sbert-Chinese-qmc-domain-v1” to index documents (one document object per line); Push inverted (vector) and forward (document field) data to each component server. The following is an example of the database data format. After offline database construction is completed, various data are pushed to corresponding service components, such as Milvus storing vector representation of documents and MongoDB storing summary information of documents. Online retrieval algorithm services will use these service components to obtain relevant data. 1.1.2 Search by text Text and images are easy for humans to relate semantically but difficult for machines. First of all, from the perspective of data form, the text is the discrete ID type of one-dimensional data based on words and words. At the same time, images are continuous two-dimensional or three-dimensional data. Secondly, the text is a subjective creation of human beings, and its expressive ability is vibrant, including various turning points, metaphors, and other expressions, while images are machine representations of the objective world. In short, bridging the semantic gap between text and image data is much more complex than searching text by text. The traditional text search image retrieval technology generally relies on the external text description data of the image or the nearest neighbor retrieval technology and carries out the retrieval through the image associated text, which in essence degrades the problem to text search. However, it will also face many issues, such as obtaining the associated text of pictures and whether the accuracy of text search by text is high enough. The depth model has gradually evolved from single-mode to multi-mode in recent years. Taking the open-source project of OpenAI, CLIP, as an example, train the model through the massive image and text data of the Internet and map the text and image data into the same semantic space, making it possible to implement the text and image search technology based on semantic vector. CLIP graphic model The text search pictures introduced in this paper are implemented based on semantic vector retrieval, and the CLIP pre-training model is used as the two-tower retrieval architecture. Because the CLIP model has trained the semantic alignment of the twin towers’ text and image side models on the massive graphic and text data, it is particularly suitable for the text search graph scene. Due to the different image and text data forms, the Query-Doc asymmetric twin towers model is used for text search image retrieval. The image-side model of the twin towers is used for offline database construction, and the text-side model is used for the online return. In the final online retrieval, the database data of the image side model will be searched after the text side model encodes Query, and the CLIP pre-training model guarantees the semantic correlation between images and texts. The model can draw the graphic pairs closer in vector space by pre-training on a large amount of visual data. Here we need to export the text-side model for online MetaSpore Serving inference. Since the retrieval scene is based on Chinese, the CLIP model supporting Chinese understanding is selected. The exported content includes the ONNX model used for online reasoning and Tokenizer, similar to the text search. MetaSpore Serving can load model reasoning through the exported content. Build library on Image search You need to download the Unsplash Lite library data and complete the construction according to the instructions. The whole process of database construction is described as follows: Preprocessing, specify the image directory, and then generate a more general JSOnline file for library construction; Build index, use OpenAI/Clip-Vit-BASE-Patch32 pre-training model to index the gallery, and output one document object for each line of index data; Push inverted (vector) and forward (document field) data to each component server. Like text search, after offline database construction, relevant data will be pushed to service components, called by online retrieval algorithm services to obtain relevant data. 1.2 Online Services The overall online service architecture diagram is as follows: https://preview.redd.it/jfsl8hdfez291.png?width=1280&format=png&auto=webp&s=a858e2304a0c93e78ba5429612ca08cbee69b35a Multi-mode search online service system supports application scenarios such as text search and text search. The whole online service consists of the following parts: Query preprocessing service: encapsulate preprocessing logic (including text/image, etc.) of pre-training model, and provide services through gRPC interface; Retrieval algorithm service: the whole algorithm processing link includes AB experiment tangent flow configuration, MetaSpore Serving call, vector recall, sorting, document summary, etc.; User entry service: provides a Web UI interface for users to debug and track down problems in the retrieval service. From a user request perspective, these services form invocation dependencies from back to front, so to build up a multimodal sample, you need to run each service from front to back first. Before doing this, remember to export the offline model, put it online and build the library first. This article will introduce the various parts of the online service system and make the whole service system step by step according to the following guidance. See the ReadME at the end of this article for more details. 1.2.1 Query preprocessing service Deep learning models tend to be based on tensors, but NLP/CV models often have a preprocessing part that translates raw text and images into tensors that deep learning models can accept. For example, NLP class models often have a pre-tokenizer to transform text data of string type into discrete tensor data. CV class models also have similar processing logic to complete the cropping, scaling, transformation, and other processing of input images through preprocessing. On the one hand, considering that this part of preprocessing logic is decoupled from tensor reasoning of the depth model, on the other hand, the reason of the depth model has an independent technical system based on ONNX, so MetaSpore disassembled this part of preprocessing logic. NLP pretreatment Tokenizer has been integrated into the Query pretreatment service. MetaSpore dismantlement with a relatively general convention. Users only need to provide preprocessing logic files to realize the loading and prediction interface and export the necessary data and configuration files loaded into the preprocessing service. Subsequent CV preprocessing logic will also be integrated in this manner. The preprocessing service currently provides the gRPC interface invocation externally and is dependent on the Query preprocessing (QP) module in the retrieval algorithm service. After the user request reaches the retrieval algorithm service, it will be forwarded to the service to complete the data preprocessing and continue the subsequent processing. The ReadMe provides details on how the preprocessing service is started, how the preprocessing model exported offline to cloud storage enters the service, and how to debug the service. To further improve the efficiency and stability of model reasoning, MetaSpore Serving implements a Python preprocessing submodule. So MetaSpore can provide gRPC services through user-specified preprocessor.py, complete Tokenizer or CV-related preprocessing in NLP, and translate requests into a Tensor that deep models can handle. Finally, the model inference is carried out by MetaSpore, Serving subsequent sub-modules. Presented here on the lot code: https://github.com/meta-soul/MetaSpore/compare/add\python\preprocessor 1.2.2 Retrieval algorithm services Retrieval algorithm service is the core of the whole online service system, which is responsible for the triage of experiments, the assembly of algorithm chains such as preprocessing, recall, sorting, and the invocation of dependent component services. The whole retrieval algorithm service is developed based on the Java Spring framework and supports multi-mode retrieval scenarios of text search and text search graph. Due to good internal abstraction and modular design, it has high flexibility and can be migrated to similar application scenarios at a low cost. Here’s a quick guide to configuring the environment to set up the retrieval algorithm service. See ReadME for more details: Install dependent components. Use Maven to install the online-Serving component Search for service configurations. Copy the template configuration file and replace the MongoDB, Milvus, and other configurations based on the development/production environment. Install and configure Consul. Consul allows you to synchronize the search service configuration in real-time, including cutting the flow of experiments, recall parameters, and sorting parameters. The project’s configuration file shows the current configuration parameters of text search and text search. The parameter modelName in the stage of pretreatment and recall is the corresponding model exported in offline processing. Start the service. Once the above configuration is complete, the retrieval service can be started from the entry script. Once the service is started, you can test it! For example, for a user with userId=10 who wants to query “How to renew ID card,” access the text search service. 1.2.3 User Entry Service Considering that the retrieval algorithm service is in the form of the API interface, it is difficult to locate and trace the problem, especially for the text search image scene can intuitively display the retrieval results to facilitate the iterative optimization of the retrieval algorithm. This paper provides a lightweight Web UI interface for text search and image search, a search input box, and results in a display page for users. Developed by Flask, the service can be easily integrated with other retrieval applications. The service calls the retrieval algorithm service and displays the returned results on the page. It’s also easy to install and start the service. Once you’re done, go to http://127.0.0.1:8090 to see if the search UI service is working correctly. See the ReadME at the end of this article for details. Multimodal system demonstration The multimodal retrieval service can be started when offline processing and online service environment configuration have been completed following the above instructions. Examples of textual searches are shown below. Enter the entry of the text search map application, enter “cat” first, and you can see that the first three digits of the returned result are cats: https://preview.redd.it/0n5nuyvhez291.png?width=1280&format=png&auto=webp&s=1e9c054f541d53381674b8d6001b4bf524506bd2 If you add a color constraint to “cat” to retrieve “black cat,” you can see that it does return a black cat: https://preview.redd.it/rzc0qjyjez291.png?width=1280&format=png&auto=webp&s=d5bcc503ef0fb3360c7740e60e295cf372dcad47 Further, strengthen the constraint on the search term, change it to “black cat on the bed,” and return results containing pictures of a black cat climbing on the bed: &#x200B; https://preview.redd.it/c4b2q8olez291.png?width=1280&format=png&auto=webp&s=4f3817b0b9f07e1e68d1d4a8281702ba3834a00a The cat can still be found through the text search system after the color and scene modification in the above example. Conclusion The cutting-edge pre-training technology can bridge the semantic gap between different modes, and the HuggingFace community can greatly reduce the cost for developers to use the pre-training model. Combined with the technological ecology of MetaSpore online reasoning and online microservices provided by DMetaSpore, the pre-training model is no longer mere offline dabbling. Instead, it can truly achieve end-to-end implementation from cutting-edge technology to industrial scenarios, fully releasing the dividends of the pre-training large model. In the future, DMetaSoul will continue to improve and optimize the MetaSpore technology ecosystem: More automated and wider access to HuggingFace community ecology. MetaSpore will soon release a common model rollout mechanism to make HuggingFace ecologically accessible and will later integrate preprocessing services into online services. Multi-mode retrieval offline algorithm optimization. For multimodal retrieval scenarios, MetaSpore will continuously iteratively optimize offline algorithm components, including text recall/sort model, graphic recall/sort model, etc., to improve the accuracy and efficiency of the retrieval algorithm. For related code and reference documentation in this article, please visit: https://github.com/meta-soul/MetaSpore/tree/main/demo/multimodal/online Some images source: https://github.com/openai/CLIP/raw/main/CLIP.png https://www.sbert.net/examples/training/sts/README.html

[R] Forecasting and Mitigating Security Threats from Malicious AI Applications
reddit
LLM Vibe Score0
Human Vibe Score1
Successful-Western27This week

[R] Forecasting and Mitigating Security Threats from Malicious AI Applications

This paper provides a systematic analysis of potential malicious applications of AI systems across digital, physical and political security domains. The methodology involves: Surveying dual-use AI capabilities that could enable attacks Mapping specific attack vectors and required technical capabilities Analyzing the evolution of attacker/defender dynamics Developing a framework for threat assessment and mitigation Key technical findings: ML advances in areas like NLP and computer vision lower barriers to sophisticated attacks Automated systems can significantly scale up traditional attack vectors Transfer learning and GANs enable rapid adaptation of attack techniques Technical countermeasures alone are insufficient - policy/governance frameworks needed The researchers provide a detailed assessment framework examining: Technical requirements for different attack types Estimated timeline for capability development Difficulty of execution and potential impact Proposed defensive measures and their limitations I think this work is important for helping the ML community get ahead of security risks before they materialize. The framework provides a structured way to evaluate emerging threats, though I expect the specific attack vectors will evolve significantly as capabilities advance. I think we need much more research on measuring the effectiveness of proposed countermeasures and understanding the co-evolution of offensive/defensive capabilities. The policy recommendations are a good start but will require ongoing refinement. TLDR: Systematic analysis of how ML advances could enable new attack vectors across security domains. Provides framework for assessing and mitigating threats through both technical and policy measures. Full summary is here. Paper here.

🌟 Introducing DarwinAI: An Open-Source Platform for the Evolution of Intelligent Agents 🚀 [Project]
reddit
LLM Vibe Score0
Human Vibe Score1
Interesting-Fox-6758This week

🌟 Introducing DarwinAI: An Open-Source Platform for the Evolution of Intelligent Agents 🚀 [Project]

🌱 The Vision: Evolutionary AI at Your Fingertips Imagine a world where AI agents aren't just programmed to perform tasks but evolve over time, adapting and improving through generations, much like living organisms. Welcome to DarwinAI, an open-source platform inspired by biological evolution, designed to breed, train, and evolve AI agents that can tackle complex, dynamic, and unpredictable challenges. 🧬 The Genetic Blueprint: Building Blocks of Intelligence At the core of DarwinAI is the concept of a digital DNA for each AI agent. This DNA is a modular structure that defines the agent's capabilities, behaviors, and adaptability. Here's what makes up this digital DNA: Genes of Ability: These are snippets of code that represent specific functions, like data classification, text analysis, or optimization. Think of them as the skills your AI agent possesses. Genes of Adaptation: These genes control how the agent responds to different environments or contexts. They determine its flexibility and resilience in the face of changing conditions. Genes of Connection: These define how the agent interacts with other agents or external resources. They are the social and collaborative aspects of the agent. This digital DNA is stored in a structured, version-controlled database, allowing us to track the evolution of each agent and ensure that beneficial mutations are preserved over time. 🛠️ The Evolutionary Process: From Genesis to Mastery The evolution of AI agents in DarwinAI happens through a series of generations, each building upon the strengths of the previous one: Selection of Parents: The fittest agents, those that excel at specific tasks, are chosen as parents. These agents have proven their worth in the simulated environment and are prime candidates for breeding the next generation. Genetic Crossover: The digital DNA of these parent agents is combined to create new agents. This can happen in two ways: Direct Crossover: Where entire genes are copied from the parents. Combinatorial Crossover: Where parts of different genes are fused to create entirely new abilities. Mutations: Random, small changes are introduced into the genes to promote diversity and explore new solutions. These mutations are the wildcards that can lead to breakthrough abilities. 🌍 The Simulated Environment: A Playground for Evolution Agents don't just exist in a vacuum; they operate in a dynamic, simulated environment where they must adapt and survive. This environment is designed to challenge the agents with: Evolutionary Tasks: Problems that agents must solve, such as data classification, prediction, or content generation. Changing Contexts: Factors like noisy data, resource constraints, or new rules that force agents to adapt on the fly. 🐣 The Life Cycle of an Agent: From Birth to Legacy Each agent goes through a life cycle that mirrors the process of natural selection: Initial Learning: Agents receive initial training based on their digital DNA. Task Execution: They perform tasks in the simulated environment, where their abilities are put to the test. Performance Evaluation: Their effectiveness, adaptability, and efficiency are measured. Reproduction: The top-performing agents produce offspring with improved genetic traits. Discard and Archive: Less effective agents are archived for future analysis, ensuring that their lessons are not lost. 🧩 Knowledge Transfer: Passing the Torch One of the key aspects of DarwinAI is the ability for agents to pass on their learned knowledge to future generations: Weight Persistence: Trained models retain their learned weights, allowing them to inherit capabilities from their ancestors. Modular Transfer: Optimized ability genes can be directly copied to new generations, ensuring that valuable skills are preserved. 🛠️ Modularity and Extensibility: Build, Mix, and Evolve DarwinAI is designed to be highly modular and extensible, allowing for: New Capabilities: Easily incorporate new genes to expand the agents' abilities over time. Hybridization: Combine agents from different specializations to create more complex and versatile agents. Directed Evolution: Introduce controlled mutations to address specific problems or challenges. 🚀 Innovative Use Cases: The Future is Bright The potential applications of DarwinAI are vast and varied: Adaptive Automation: Create agents that can adapt to new market conditions or evolving industrial requirements. Collaborative Robots: Develop robots that evolve to improve teamwork in dynamic environments. Scientific Discovery: Agents that combine skills to uncover patterns or solutions that were previously unknown. 🚀 Vision for the Future: An Ecosystem of Evolving Intelligence By fostering an ecosystem where knowledge is accumulated and adaptability is paramount, DarwinAI aims to produce agents that are not only intelligent but also diverse and efficient. These agents will be equipped to handle complex, unpredictable challenges, opening up new frontiers in AI research and application. 🌐 Join Us in Shaping the Future of AI! DarwinAI is more than just a project; it's a community-driven movement towards a new era of AI. We invite you to join us, contribute your ideas, and help shape the future of evolutionary AI. Whether you're a developer, researcher, or simply someone excited about the potential of AI, there's a place for you in this journey. Let's evolve together! 🌱💻

[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore
reddit
LLM Vibe Score0
Human Vibe Score1
qazmkoppThis week

[P]MMML | Deploy HuggingFace training model rapidly based on MetaSpore

A few days ago, HuggingFace announced a $100 million Series C funding round, which was big news in open source machine learning and could be a sign of where the industry is headed. Two days before the HuggingFace funding announcement, open-source machine learning platform MetaSpore released a demo based on the HuggingFace Rapid deployment pre-training model. As deep learning technology makes innovative breakthroughs in computer vision, natural language processing, speech understanding, and other fields, more and more unstructured data are perceived, understood, and processed by machines. These advances are mainly due to the powerful learning ability of deep learning. Through pre-training of deep models on massive data, the models can capture the internal data patterns, thus helping many downstream tasks. With the industry and academia investing more and more energy in the research of pre-training technology, the distribution warehouses of pre-training models such as HuggingFace and Timm have emerged one after another. The open-source community release pre-training significant model dividends at an unprecedented speed. In recent years, the data form of machine modeling and understanding has gradually evolved from single-mode to multi-mode, and the semantic gap between different modes is being eliminated, making it possible to retrieve data across modes. Take CLIP, OpenAI’s open-source work, as an example, to pre-train the twin towers of images and texts on a dataset of 400 million pictures and texts and connect the semantics between pictures and texts. Many researchers in the academic world have been solving multimodal problems such as image generation and retrieval based on this technology. Although the frontier technology through the semantic gap between modal data, there is still a heavy and complicated model tuning, offline data processing, high performance online reasoning architecture design, heterogeneous computing, and online algorithm be born multiple processes and challenges, hindering the frontier multimodal retrieval technologies fall to the ground and pratt &whitney. DMetaSoul aims at the above technical pain points, abstracting and uniting many links such as model training optimization, online reasoning, and algorithm experiment, forming a set of solutions that can quickly apply offline pre-training model to online. This paper will introduce how to use the HuggingFace community pre-training model to conduct online reasoning and algorithm experiments based on MetaSpore technology ecology so that the benefits of the pre-training model can be fully released to the specific business or industry and small and medium-sized enterprises. And we will give the text search text and text search graph two multimodal retrieval demonstration examples for your reference. Multimodal semantic retrieval The sample architecture of multimodal retrieval is as follows: Our multimodal retrieval system supports both text search and text search application scenarios, including offline processing, model reasoning, online services, and other core modules: &#x200B; https://preview.redd.it/w4v4c7vcez291.png?width=1834&format=png&auto=webp&s=0687efb1fddb26e8e30cb844d398ec712b947f31 Offline processing, including offline data processing processes for different application scenarios of text search and text search, including model tuning, model export, data index database construction, data push, etc. Model inference. After the offline model training, we deployed our NLP and CV large models based on the MetaSpore Serving framework. MetaSpore Serving helps us conveniently perform online inference, elastic scheduling, load balancing, and resource scheduling in heterogeneous environments. Online services. Based on MetaSpore’s online algorithm application framework, MetaSpore has a complete set of reusable online search services, including Front-end retrieval UI, multimodal data preprocessing, vector recall and sorting algorithm, AB experimental framework, etc. MetaSpore also supports text search by text and image scene search by text and can be migrated to other application scenarios at a low cost. The HuggingFace open source community has provided several excellent baseline models for similar multimodal retrieval problems, which are often the starting point for actual optimization in the industry. MetaSpore also uses the pre-training model of the HuggingFace community in its online services of searching words by words and images by words. Searching words by words is based on the semantic similarity model of the question and answer field optimized by MetaSpore, and searching images by words is based on the community pre-training model. These community open source pre-training models are exported to the general ONNX format and loaded into MetaSpore Serving for online reasoning. The following sections will provide a detailed description of the model export and online retrieval algorithm services. The reasoning part of the model is standardized SAAS services with low coupling with the business. Interested readers can refer to my previous post: The design concept of MetaSpore, a new generation of the one-stop machine learning platform. 1.1 Offline Processing Offline processing mainly involves the export and loading of online models and index building and pushing of the document library. You can follow the step-by-step instructions below to complete the offline processing of text search and image search and see how the offline pre-training model achieves reasoning at MetaSpore. 1.1.1 Search text by text Traditional text retrieval systems are based on literal matching algorithms such as BM25. Due to users’ diverse query words, a semantic gap between query words and documents is often encountered. For example, users misspell “iPhone” as “Phone,” and search terms are incredibly long, such as “1 \~ 3 months old baby autumn small size bag pants”. Traditional text retrieval systems will use spelling correction, synonym expansion, search terms rewriting, and other means to alleviate the semantic gap but fundamentally fail to solve this problem. Only when the retrieval system fully understands users’ query terms and documents can it meet users’ retrieval demands at the semantic level. With the continuous progress of pre-training and representational learning technology, some commercial search engines continue to integrate semantic vector retrieval methods based on symbolic learning into the retrieval ecology. Semantic retrieval model This paper introduces a set of semantic vector retrieval applications. MetaSpore built a set of semantic retrieval systems based on encyclopedia question and answer data. MetaSpore adopted the Sentence-Bert model as the semantic vector representation model, which fine-tunes the twin tower BERT in supervised or unsupervised ways to make the model more suitable for retrieval tasks. The model structure is as follows: The query-Doc symmetric two-tower model is used in text search and question and answer retrieval. The vector representation of online Query and offline DOC share the same vector representation model, so it is necessary to ensure the consistency of the offline DOC library building model and online Query inference model. The case uses MetaSpore’s text representation model Sbert-Chinese-QMC-domain-V1, optimized in the open-source semantically similar data set. This model will express the question and answer data as a vector in offline database construction. The user query will be expressed as a vector by this model in online retrieval, ensuring that query-doc in the same semantic space, users’ semantic retrieval demands can be guaranteed by vector similarity metric calculation. Since the text presentation model does vector encoding for Query online, we need to export the model for use by the online service. Go to the q&A data library code directory and export the model concerning the documentation. In the script, Pytorch Tracing is used to export the model. The models are exported to the “./export “directory. The exported models are mainly ONNX models used for wired reasoning, Tokenizer, and related configuration files. The exported models are loaded into MetaSpore Serving by the online Serving system described below for model reasoning. Since the exported model will be copied to the cloud storage, you need to configure related variables in env.sh. \Build library based on text search \ The retrieval database is built on the million-level encyclopedia question and answer data set. According to the description document, you need to download the data and complete the database construction. The question and answer data will be coded as a vector by the offline model, and then the database construction data will be pushed to the service component. The whole process of database construction is described as follows: Preprocessing, converting the original data into a more general JSonline format for database construction; Build index, use the same model as online “sbert-Chinese-qmc-domain-v1” to index documents (one document object per line); Push inverted (vector) and forward (document field) data to each component server. The following is an example of the database data format. After offline database construction is completed, various data are pushed to corresponding service components, such as Milvus storing vector representation of documents and MongoDB storing summary information of documents. Online retrieval algorithm services will use these service components to obtain relevant data. 1.1.2 Search by text Text and images are easy for humans to relate semantically but difficult for machines. First of all, from the perspective of data form, the text is the discrete ID type of one-dimensional data based on words and words. At the same time, images are continuous two-dimensional or three-dimensional data. Secondly, the text is a subjective creation of human beings, and its expressive ability is vibrant, including various turning points, metaphors, and other expressions, while images are machine representations of the objective world. In short, bridging the semantic gap between text and image data is much more complex than searching text by text. The traditional text search image retrieval technology generally relies on the external text description data of the image or the nearest neighbor retrieval technology and carries out the retrieval through the image associated text, which in essence degrades the problem to text search. However, it will also face many issues, such as obtaining the associated text of pictures and whether the accuracy of text search by text is high enough. The depth model has gradually evolved from single-mode to multi-mode in recent years. Taking the open-source project of OpenAI, CLIP, as an example, train the model through the massive image and text data of the Internet and map the text and image data into the same semantic space, making it possible to implement the text and image search technology based on semantic vector. CLIP graphic model The text search pictures introduced in this paper are implemented based on semantic vector retrieval, and the CLIP pre-training model is used as the two-tower retrieval architecture. Because the CLIP model has trained the semantic alignment of the twin towers’ text and image side models on the massive graphic and text data, it is particularly suitable for the text search graph scene. Due to the different image and text data forms, the Query-Doc asymmetric twin towers model is used for text search image retrieval. The image-side model of the twin towers is used for offline database construction, and the text-side model is used for the online return. In the final online retrieval, the database data of the image side model will be searched after the text side model encodes Query, and the CLIP pre-training model guarantees the semantic correlation between images and texts. The model can draw the graphic pairs closer in vector space by pre-training on a large amount of visual data. Here we need to export the text-side model for online MetaSpore Serving inference. Since the retrieval scene is based on Chinese, the CLIP model supporting Chinese understanding is selected. The exported content includes the ONNX model used for online reasoning and Tokenizer, similar to the text search. MetaSpore Serving can load model reasoning through the exported content. Build library on Image search You need to download the Unsplash Lite library data and complete the construction according to the instructions. The whole process of database construction is described as follows: Preprocessing, specify the image directory, and then generate a more general JSOnline file for library construction; Build index, use OpenAI/Clip-Vit-BASE-Patch32 pre-training model to index the gallery, and output one document object for each line of index data; Push inverted (vector) and forward (document field) data to each component server. Like text search, after offline database construction, relevant data will be pushed to service components, called by online retrieval algorithm services to obtain relevant data. 1.2 Online Services The overall online service architecture diagram is as follows: https://preview.redd.it/jfsl8hdfez291.png?width=1280&format=png&auto=webp&s=a858e2304a0c93e78ba5429612ca08cbee69b35a Multi-mode search online service system supports application scenarios such as text search and text search. The whole online service consists of the following parts: Query preprocessing service: encapsulate preprocessing logic (including text/image, etc.) of pre-training model, and provide services through gRPC interface; Retrieval algorithm service: the whole algorithm processing link includes AB experiment tangent flow configuration, MetaSpore Serving call, vector recall, sorting, document summary, etc.; User entry service: provides a Web UI interface for users to debug and track down problems in the retrieval service. From a user request perspective, these services form invocation dependencies from back to front, so to build up a multimodal sample, you need to run each service from front to back first. Before doing this, remember to export the offline model, put it online and build the library first. This article will introduce the various parts of the online service system and make the whole service system step by step according to the following guidance. See the ReadME at the end of this article for more details. 1.2.1 Query preprocessing service Deep learning models tend to be based on tensors, but NLP/CV models often have a preprocessing part that translates raw text and images into tensors that deep learning models can accept. For example, NLP class models often have a pre-tokenizer to transform text data of string type into discrete tensor data. CV class models also have similar processing logic to complete the cropping, scaling, transformation, and other processing of input images through preprocessing. On the one hand, considering that this part of preprocessing logic is decoupled from tensor reasoning of the depth model, on the other hand, the reason of the depth model has an independent technical system based on ONNX, so MetaSpore disassembled this part of preprocessing logic. NLP pretreatment Tokenizer has been integrated into the Query pretreatment service. MetaSpore dismantlement with a relatively general convention. Users only need to provide preprocessing logic files to realize the loading and prediction interface and export the necessary data and configuration files loaded into the preprocessing service. Subsequent CV preprocessing logic will also be integrated in this manner. The preprocessing service currently provides the gRPC interface invocation externally and is dependent on the Query preprocessing (QP) module in the retrieval algorithm service. After the user request reaches the retrieval algorithm service, it will be forwarded to the service to complete the data preprocessing and continue the subsequent processing. The ReadMe provides details on how the preprocessing service is started, how the preprocessing model exported offline to cloud storage enters the service, and how to debug the service. To further improve the efficiency and stability of model reasoning, MetaSpore Serving implements a Python preprocessing submodule. So MetaSpore can provide gRPC services through user-specified preprocessor.py, complete Tokenizer or CV-related preprocessing in NLP, and translate requests into a Tensor that deep models can handle. Finally, the model inference is carried out by MetaSpore, Serving subsequent sub-modules. Presented here on the lot code: https://github.com/meta-soul/MetaSpore/compare/add\python\preprocessor 1.2.2 Retrieval algorithm services Retrieval algorithm service is the core of the whole online service system, which is responsible for the triage of experiments, the assembly of algorithm chains such as preprocessing, recall, sorting, and the invocation of dependent component services. The whole retrieval algorithm service is developed based on the Java Spring framework and supports multi-mode retrieval scenarios of text search and text search graph. Due to good internal abstraction and modular design, it has high flexibility and can be migrated to similar application scenarios at a low cost. Here’s a quick guide to configuring the environment to set up the retrieval algorithm service. See ReadME for more details: Install dependent components. Use Maven to install the online-Serving component Search for service configurations. Copy the template configuration file and replace the MongoDB, Milvus, and other configurations based on the development/production environment. Install and configure Consul. Consul allows you to synchronize the search service configuration in real-time, including cutting the flow of experiments, recall parameters, and sorting parameters. The project’s configuration file shows the current configuration parameters of text search and text search. The parameter modelName in the stage of pretreatment and recall is the corresponding model exported in offline processing. Start the service. Once the above configuration is complete, the retrieval service can be started from the entry script. Once the service is started, you can test it! For example, for a user with userId=10 who wants to query “How to renew ID card,” access the text search service. 1.2.3 User Entry Service Considering that the retrieval algorithm service is in the form of the API interface, it is difficult to locate and trace the problem, especially for the text search image scene can intuitively display the retrieval results to facilitate the iterative optimization of the retrieval algorithm. This paper provides a lightweight Web UI interface for text search and image search, a search input box, and results in a display page for users. Developed by Flask, the service can be easily integrated with other retrieval applications. The service calls the retrieval algorithm service and displays the returned results on the page. It’s also easy to install and start the service. Once you’re done, go to http://127.0.0.1:8090 to see if the search UI service is working correctly. See the ReadME at the end of this article for details. Multimodal system demonstration The multimodal retrieval service can be started when offline processing and online service environment configuration have been completed following the above instructions. Examples of textual searches are shown below. Enter the entry of the text search map application, enter “cat” first, and you can see that the first three digits of the returned result are cats: https://preview.redd.it/0n5nuyvhez291.png?width=1280&format=png&auto=webp&s=1e9c054f541d53381674b8d6001b4bf524506bd2 If you add a color constraint to “cat” to retrieve “black cat,” you can see that it does return a black cat: https://preview.redd.it/rzc0qjyjez291.png?width=1280&format=png&auto=webp&s=d5bcc503ef0fb3360c7740e60e295cf372dcad47 Further, strengthen the constraint on the search term, change it to “black cat on the bed,” and return results containing pictures of a black cat climbing on the bed: &#x200B; https://preview.redd.it/c4b2q8olez291.png?width=1280&format=png&auto=webp&s=4f3817b0b9f07e1e68d1d4a8281702ba3834a00a The cat can still be found through the text search system after the color and scene modification in the above example. Conclusion The cutting-edge pre-training technology can bridge the semantic gap between different modes, and the HuggingFace community can greatly reduce the cost for developers to use the pre-training model. Combined with the technological ecology of MetaSpore online reasoning and online microservices provided by DMetaSpore, the pre-training model is no longer mere offline dabbling. Instead, it can truly achieve end-to-end implementation from cutting-edge technology to industrial scenarios, fully releasing the dividends of the pre-training large model. In the future, DMetaSoul will continue to improve and optimize the MetaSpore technology ecosystem: More automated and wider access to HuggingFace community ecology. MetaSpore will soon release a common model rollout mechanism to make HuggingFace ecologically accessible and will later integrate preprocessing services into online services. Multi-mode retrieval offline algorithm optimization. For multimodal retrieval scenarios, MetaSpore will continuously iteratively optimize offline algorithm components, including text recall/sort model, graphic recall/sort model, etc., to improve the accuracy and efficiency of the retrieval algorithm. For related code and reference documentation in this article, please visit: https://github.com/meta-soul/MetaSpore/tree/main/demo/multimodal/online Some images source: https://github.com/openai/CLIP/raw/main/CLIP.png https://www.sbert.net/examples/training/sts/README.html

[D] AI regulation: a review of NTIA's "AI Accountability Policy" doc
reddit
LLM Vibe Score0
Human Vibe Score0.667
elehman839This week

[D] AI regulation: a review of NTIA's "AI Accountability Policy" doc

How will governments respond to the rapid rise of AI? How can sensible regulation keep pace with AI technology? These questions interest many of us! One early US government response has come from the National Telecommunications and Information Administration (NTIA). Specifically, the NTIA published an "AI Accountability Policy Request for Comment" on April 11, 2023. I read the NTIA document carefully, and I'm sharing my observations here for others interested in AI regulation. You can, of course, read the original materials and form your own opinions. Moreover, you can share those opinions not only on this post, but also with the NTIA itself until June 12, 2023. As background, the NTIA (homepage, Wikipedia) consists of a few hundred people within the Department of Commerce. The official mission of the NTIA is "advising the President on telecommunications and information policy issues". Topics covered by NTIA include broadband internet access, spectrum management, internet health, and now artificial intelligence. I do not know whether the NTIA will ultimately drive thinking around AI regulation in the United States or they are just a spunky lot who got something on paper early. The NTIA document is not a specific policy proposal, but rather a thoughtful discussion of AI regulation, followed by a long list of questions on which the NTIA seeks input. This format seems appropriate right now, as we're all trying to make sense of a fast-changing world. The NTIA document leans heavily on two others: the Blueprint for an AI Bill of Rights from the White House Office of Science and Technology and the AI Risk Management Framework from the National Institute of Standards and Technology (NIST). Without going into these two in depth, even tiny snippets convey their differing audiences and flavors: White House Blueprint: "You should be protected from safe and ineffective systems." NIST Framework: "Risk refers to the composite measure of an event’s probability of occurring and the magnitude or degree of the consequences of the corresponding event." Now, turning back to the NTIA document itself, I'll comment on three aspects (1) scope, (2) problems addressed, and (3) solutions contemplated. Scope is critical to understanding the NTIA document, and is probably worth keeping in mind in all near-term discussion of AI regulation. Over the past several years, at least two different technologies have been called "AI". The document mentions both, but the emphasis is NOT on the one you're probably thinking about. In more detail: A few years ago, regulators began scrutinizing "automated decisions systems", which passed as "AI" in those ancient times. An example would be an ML model used by a bank to decide whether or not you get a loan. That model might take in all sorts of information about you, combine it in mysterious ML ways, and reject your loan request. Then you might wonder, "Did that system effectively use my address and name to deduce that I am black and then reject my loan request on the basis of race?" There is some evidence of that happening, and this seems like an injustice. So perhaps such systems should be audited and certified so people know this won't happen. This is the focus of the document. These days, AI more commonly refers to open-ended systems that can engage on a wide range of topics and approximate human intelligence. The document briefly mentions generative AI models, large language models, ChatGPT, and "foundational models" (sic), but this is not the focus. The passing mentions may obscure this, unfortunately. In my opinion, these two notions of "AI" are radically different, and many of the differences matter from a regulatory perspective. Yet NTIA lumps both under a sweeping definition of an "AI system" as "an engineered or machine-based system that can, for a given set of objectives, generate outputs such as predictions, recommendations, or decisions influencing real or virtual environments." (Hmm, this includes my Magic 8-Ball…) Keep scope in mind as we turn to the next aspect: the problems under discussion. Now, NTIA's goal is to solicit input, so considering a wide range of potential problems associated with AI makes sense. Consistent with that, the document refers to democratic values, civil rights, civil liberties, and privacy. And citing the NIST doc, NTIA vaguely notes "a wide range of potential AI risks". Also, AI systems should be "valid and reliable, safe, secure and resilient, accountable and transparent, explainable and interpretable, privacy-enhanced, and fair with their harmful bias managed". And they should call their mothers \every\ week. (Okay, I made that one up.) A few comments on this formulation of the problem. First, these concerns feel more applicable to older-style AI. This includes automated decisions systems, like for a bank loan or for a prison parole recommendation. Sure, I believe such systems should operate in ways consistent with our consensus societal values, and further regulation may be needed to achieve that. But, hello! There's also another, newer class of AI that poses additional challenges. And I don't see those discussed in the NTIA document. Such challenges might include: People losing jobs because AI takes their work. Ensuring malicious people don't use AI tools to wreak havoc on the world. Sorting out intellectual property issues around AI to ensure both rapid progress in the field and respect for creators' rights. Ensuring laws appropriately assign culpability to humans when AIs cause harm. Planning for an incident analogous to the first internet worm, where an AI goes rogue, wreaks some havoc, and everyone is shocked (before it happens 28,385 more times). Bottom line: when I cntrl-F the doc for "robotic overlords", I get zero hits. ZERO. This is why I now believe scope is so important when considering efforts to regulate AI: are we talking about old-school AI or 2023-era AI or what? Because they are pretty different. The last aspect I'll address is the solutions contemplated. Again, NTIA's goal is to stimulate discussion, not propose something specific. Nevertheless, there is a strong push in one particular direction: unlike, "robotic overlord", the word "audit" appears more than 100 times along with many instances of "assessment" and "certification". On one hand, this approach makes sense. Suppose you want to ensure that a bank loan system is fair, that a social media platform isn't spreading misinformation, that a search engine is returning accurate results, etc. Then someone, somewhere has to assess or audit that system and look for problems. That audit might be done by the creator of the system or a third-party auditing agency. Such audits could be incentivized by mandates, prizes, or shiny gold stars. The government might help by fostering development of auditing tools and data. The NTIA is open to all such possibilities and seeks input on how to proceed. On the other hand, this seems like a tactic best suited to automated decision systems operated by financial institutions, government agencies, and the like. Such formal processes seem a poor fit for the current AI wave. For example: Auditing will take time and money. That's something a bank might pay for a system that will run for years. For something fine-tuned over the weekend at a startup or by some guy living in his mother's basement, that's probably not going to happen. Auditing a straightforward decision system seems far easier than assessing an open-ended AI. Beyond basic practicality, the AI could be taught to lie when it senses an audit. Also, auditing procedures (like the NTIA doc itself) will presumably be online, which means that AIs will read them and could potentially respond. Most current ML models fix parameters after training, but I think we'll soon see some models whose parameters evolve as they engage with the world. Auditing such a system that varies continuously over time seems especially difficult. Auditing a foundation model probably tells you little about derivative models. A sweet-hearted model can surely be made into monster with moderate additional training; you don't need to teach the model new cognitive skills, just repurpose existing ones to new ends. More generally, auditing doesn't address many of my concerns about AI regulation (see list above). For example, auditing sort of assumes a basically responsible actor (bank, government agency, big tech company), but AI could be misused by malicious people who, naturally, will not seek a responsible outside assessment. In any case, for both old-school and modern AI, auditing is only one line of defense, and that's not enough. You can audit until you're blue in the face, stuff will still get through, and AI systems will still cause some harm. So what's the next line of defense? For example, is our legal system ready to sensibly assign culpability to humans for AI-related incidents? In summary, the critical problem with the NTIA document is that it creates a largely false appearance of US government engagement with the new class of AI technology. As a result, people could wrongly believe that the US government is already responding to the rise of AI, and fail to advocate for actual, effective engagement. That said, the NTIA document does address important issues around a prominent technology sometimes (formerly?) called "AI". Even there, however, the proposed approach (auditing) seems like an overly-fragile, single line of defense.

Interview with Juergen Schmidhuber, renowned ‘Father Of Modern AI’, says his life’s work won't lead to dystopia.
reddit
LLM Vibe Score0
Human Vibe Score0.765
hardmaruThis week

Interview with Juergen Schmidhuber, renowned ‘Father Of Modern AI’, says his life’s work won't lead to dystopia.

Schmidhuber interview expressing his views on the future of AI and AGI. Original source. I think the interview is of interest to r/MachineLearning, and presents an alternate view, compared to other influential leaders in AI. Juergen Schmidhuber, Renowned 'Father Of Modern AI,' Says His Life’s Work Won't Lead To Dystopia May 23, 2023. Contributed by Hessie Jones. Amid the growing concern about the impact of more advanced artificial intelligence (AI) technologies on society, there are many in the technology community who fear the implications of the advancements in Generative AI if they go unchecked. Dr. Juergen Schmidhuber, a renowned scientist, artificial intelligence researcher and widely regarded as one of the pioneers in the field, is more optimistic. He declares that many of those who suddenly warn against the dangers of AI are just seeking publicity, exploiting the media’s obsession with killer robots which has attracted more attention than “good AI” for healthcare etc. The potential to revolutionize various industries and improve our lives is clear, as are the equal dangers if bad actors leverage the technology for personal gain. Are we headed towards a dystopian future, or is there reason to be optimistic? I had a chance to sit down with Dr. Juergen Schmidhuber to understand his perspective on this seemingly fast-moving AI-train that will leap us into the future. As a teenager in the 1970s, Juergen Schmidhuber became fascinated with the idea of creating intelligent machines that could learn and improve on their own, becoming smarter than himself within his lifetime. This would ultimately lead to his groundbreaking work in the field of deep learning. In the 1980s, he studied computer science at the Technical University of Munich (TUM), where he earned his diploma in 1987. His thesis was on the ultimate self-improving machines that, not only, learn through some pre-wired human-designed learning algorithm, but also learn and improve the learning algorithm itself. Decades later, this became a hot topic. He also received his Ph.D. at TUM in 1991 for work that laid some of the foundations of modern AI. Schmidhuber is best known for his contributions to the development of recurrent neural networks (RNNs), the most powerful type of artificial neural network that can process sequential data such as speech and natural language. With his students Sepp Hochreiter, Felix Gers, Alex Graves, Daan Wierstra, and others, he published architectures and training algorithms for the long short-term memory (LSTM), a type of RNN that is widely used in natural language processing, speech recognition, video games, robotics, and other applications. LSTM has become the most cited neural network of the 20th century, and Business Week called it "arguably the most commercial AI achievement." Throughout his career, Schmidhuber has received various awards and accolades for his groundbreaking work. In 2013, he was awarded the Helmholtz Prize, which recognizes significant contributions to the field of machine learning. In 2016, he was awarded the IEEE Neural Network Pioneer Award for "pioneering contributions to deep learning and neural networks." The media have often called him the “father of modern AI,” because the most cited neural networks all build on his lab’s work. He is quick to point out, however, that AI history goes back centuries. Despite his many accomplishments, at the age of 60, he feels mounting time pressure towards building an Artificial General Intelligence within his lifetime and remains committed to pushing the boundaries of AI research and development. He is currently director of the KAUST AI Initiative, scientific director of the Swiss AI Lab IDSIA, and co-founder and chief scientist of AI company NNAISENSE, whose motto is "AI∀" which is a math-inspired way of saying "AI For All." He continues to work on cutting-edge AI technologies and applications to improve human health and extend human lives and make lives easier for everyone. The following interview has been edited for clarity. Jones: Thank you Juergen for joining me. You have signed letters warning about AI weapons. But you didn't sign the recent publication, "Pause Gigantic AI Experiments: An Open Letter"? Is there a reason? Schmidhuber: Thank you Hessie. Glad to speak with you. I have realized that many of those who warn in public against the dangers of AI are just seeking publicity. I don't think the latest letter will have any significant impact because many AI researchers, companies, and governments will ignore it completely. The proposal frequently uses the word "we" and refers to "us," the humans. But as I have pointed out many times in the past, there is no "we" that everyone can identify with. Ask 10 different people, and you will hear 10 different opinions about what is "good." Some of those opinions will be completely incompatible with each other. Don't forget the enormous amount of conflict between the many people. The letter also says, "If such a pause cannot be quickly put in place, governments should intervene and impose a moratorium." The problem is that different governments have ALSO different opinions about what is good for them and for others. Great Power A will say, if we don't do it, Great Power B will, perhaps secretly, and gain an advantage over us. The same is true for Great Powers C and D. Jones: Everyone acknowledges this fear surrounding current generative AI technology. Moreover, the existential threat of this technology has been publicly acknowledged by Sam Altman, CEO of OpenAI himself, calling for AI regulation. From your perspective, is there an existential threat? Schmidhuber: It is true that AI can be weaponized, and I have no doubt that there will be all kinds of AI arms races, but AI does not introduce a new quality of existential threat. The threat coming from AI weapons seems to pale in comparison to the much older threat from nuclear hydrogen bombs that don’t need AI at all. We should be much more afraid of half-century-old tech in the form of H-bomb rockets. The Tsar Bomba of 1961 had almost 15 times more destructive power than all weapons of WW-II combined. Despite the dramatic nuclear disarmament since the 1980s, there are still more than enough nuclear warheads to wipe out human civilization within two hours, without any AI I’m much more worried about that old existential threat than the rather harmless AI weapons. Jones: I realize that while you compare AI to the threat of nuclear bombs, there is a current danger that a current technology can be put in the hands of humans and enable them to “eventually” exact further harms to individuals of group in a very precise way, like targeted drone attacks. You are giving people a toolset that they've never had before, enabling bad actors, as some have pointed out, to be able to do a lot more than previously because they didn't have this technology. Schmidhuber: Now, all that sounds horrible in principle, but our existing laws are sufficient to deal with these new types of weapons enabled by AI. If you kill someone with a gun, you will go to jail. Same if you kill someone with one of these drones. Law enforcement will get better at understanding new threats and new weapons and will respond with better technology to combat these threats. Enabling drones to target persons from a distance in a way that requires some tracking and some intelligence to perform, which has traditionally been performed by skilled humans, to me, it seems is just an improved version of a traditional weapon, like a gun, which is, you know, a little bit smarter than the old guns. But, in principle, all of that is not a new development. For many centuries, we have had the evolution of better weaponry and deadlier poisons and so on, and law enforcement has evolved their policies to react to these threats over time. So, it's not that we suddenly have a new quality of existential threat and it's much more worrisome than what we have had for about six decades. A large nuclear warhead doesn’t need fancy face recognition to kill an individual. No, it simply wipes out an entire city with ten million inhabitants. Jones: The existential threat that’s implied is the extent to which humans have control over this technology. We see some early cases of opportunism which, as you say, tends to get more media attention than positive breakthroughs. But you’re implying that this will all balance out? Schmidhuber: Historically, we have a long tradition of technological breakthroughs that led to advancements in weapons for the purpose of defense but also for protection. From sticks, to rocks, to axes to gunpowder to cannons to rockets… and now to drones… this has had a drastic influence on human history but what has been consistent throughout history is that those who are using technology to achieve their own ends are themselves, facing the same technology because the opposing side is learning to use it against them. And that's what has been repeated in thousands of years of human history and it will continue. I don't see the new AI arms race as something that is remotely as existential a threat as the good old nuclear warheads. You said something important, in that some people prefer to talk about the downsides rather than the benefits of this technology, but that's misleading, because 95% of all AI research and AI development is about making people happier and advancing human life and health. Jones: Let’s touch on some of those beneficial advances in AI research that have been able to radically change present day methods and achieve breakthroughs. Schmidhuber: All right! For example, eleven years ago, our team with my postdoc Dan Ciresan was the first to win a medical imaging competition through deep learning. We analyzed female breast cells with the objective to determine harmless cells vs. those in the pre-cancer stage. Typically, a trained oncologist needs a long time to make these determinations. Our team, who knew nothing about cancer, were able to train an artificial neural network, which was totally dumb in the beginning, on lots of this kind of data. It was able to outperform all the other methods. Today, this is being used not only for breast cancer, but also for radiology and detecting plaque in arteries, and many other things. Some of the neural networks that we have developed in the last 3 decades are now prevalent across thousands of healthcare applications, detecting Diabetes and Covid-19 and what not. This will eventually permeate across all healthcare. The good consequences of this type of AI are much more important than the click-bait new ways of conducting crimes with AI. Jones: Adoption is a product of reinforced outcomes. The massive scale of adoption either leads us to believe that people have been led astray, or conversely, technology is having a positive effect on people’s lives. Schmidhuber: The latter is the likely case. There's intense commercial pressure towards good AI rather than bad AI because companies want to sell you something, and you are going to buy only stuff you think is going to be good for you. So already just through this simple, commercial pressure, you have a tremendous bias towards good AI rather than bad AI. However, doomsday scenarios like in Schwarzenegger movies grab more attention than documentaries on AI that improve people’s lives. Jones: I would argue that people are drawn to good stories – narratives that contain an adversary and struggle, but in the end, have happy endings. And this is consistent with your comment on human nature and how history, despite its tendency for violence and destruction of humanity, somehow tends to correct itself. Let’s take the example of a technology, which you are aware – GANs – General Adversarial Networks, which today has been used in applications for fake news and disinformation. In actuality, the purpose in the invention of GANs was far from what it is used for today. Schmidhuber: Yes, the name GANs was created in 2014 but we had the basic principle already in the early 1990s. More than 30 years ago, I called it artificial curiosity. It's a very simple way of injecting creativity into a little two network system. This creative AI is not just trying to slavishly imitate humans. Rather, it’s inventing its own goals. Let me explain: You have two networks. One network is producing outputs that could be anything, any action. Then the second network is looking at these actions and it’s trying to predict the consequences of these actions. An action could move a robot, then something happens, and the other network is just trying to predict what will happen. Now we can implement artificial curiosity by reducing the prediction error of the second network, which, at the same time, is the reward of the first network. The first network wants to maximize its reward and so it will invent actions that will lead to situations that will surprise the second network, which it has not yet learned to predict well. In the case where the outputs are fake images, the first network will try to generate images that are good enough to fool the second network, which will attempt to predict the reaction of the environment: fake or real image, and it will try to become better at it. The first network will continue to also improve at generating images whose type the second network will not be able to predict. So, they fight each other. The 2nd network will continue to reduce its prediction error, while the 1st network will attempt to maximize it. Through this zero-sum game the first network gets better and better at producing these convincing fake outputs which look almost realistic. So, once you have an interesting set of images by Vincent Van Gogh, you can generate new images that leverage his style, without the original artist having ever produced the artwork himself. Jones: I see how the Van Gogh example can be applied in an education setting and there are countless examples of artists mimicking styles from famous painters but image generation from this instance that can happen within seconds is quite another feat. And you know this is how GANs has been used. What’s more prevalent today is a socialized enablement of generating images or information to intentionally fool people. It also surfaces new harms that deal with the threat to intellectual property and copyright, where laws have yet to account for. And from your perspective this was not the intention when the model was conceived. What was your motivation in your early conception of what is now GANs? Schmidhuber: My old motivation for GANs was actually very important and it was not to create deepfakes or fake news but to enable AIs to be curious and invent their own goals, to make them explore their environment and make them creative. Suppose you have a robot that executes one action, then something happens, then it executes another action, and so on, because it wants to achieve certain goals in the environment. For example, when the battery is low, this will trigger “pain” through hunger sensors, so it wants to go to the charging station, without running into obstacles, which will trigger other pain sensors. It will seek to minimize pain (encoded through numbers). Now the robot has a friend, the second network, which is a world model ––it’s a prediction machine that learns to predict the consequences of the robot’s actions. Once the robot has a good model of the world, it can use it for planning. It can be used as a simulation of the real world. And then it can determine what is a good action sequence. If the robot imagines this sequence of actions, the model will predict a lot of pain, which it wants to avoid. If it plays this alternative action sequence in its mental model of the world, then it will predict a rewarding situation where it’s going to sit on the charging station and its battery is going to load again. So, it'll prefer to execute the latter action sequence. In the beginning, however, the model of the world knows nothing, so how can we motivate the first network to generate experiments that lead to data that helps the world model learn something it didn’t already know? That’s what artificial curiosity is about. The dueling two network systems effectively explore uncharted environments by creating experiments so that over time the curious AI gets a better sense of how the environment works. This can be applied to all kinds of environments, and has medical applications. Jones: Let’s talk about the future. You have said, “Traditional humans won’t play a significant role in spreading intelligence across the universe.” Schmidhuber: Let’s first conceptually separate two types of AIs. The first type of AI are tools directed by humans. They are trained to do specific things like accurately detect diabetes or heart disease and prevent attacks before they happen. In these cases, the goal is coming from the human. More interesting AIs are setting their own goals. They are inventing their own experiments and learning from them. Their horizons expand and eventually they become more and more general problem solvers in the real world. They are not controlled by their parents, but much of what they learn is through self-invented experiments. A robot, for example, is rotating a toy, and as it is doing this, the video coming in through the camera eyes, changes over time and it begins to learn how this video changes and learns how the 3D nature of the toy generates certain videos if you rotate it a certain way, and eventually, how gravity works, and how the physics of the world works. Like a little scientist! And I have predicted for decades that future scaled-up versions of such AI scientists will want to further expand their horizons, and eventually go where most of the physical resources are, to build more and bigger AIs. And of course, almost all of these resources are far away from earth out there in space, which is hostile to humans but friendly to appropriately designed AI-controlled robots and self-replicating robot factories. So here we are not talking any longer about our tiny biosphere; no, we are talking about the much bigger rest of the universe. Within a few tens of billions of years, curious self-improving AIs will colonize the visible cosmos in a way that’s infeasible for humans. Those who don’t won’t have an impact. Sounds like science fiction, but since the 1970s I have been unable to see a plausible alternative to this scenario, except for a global catastrophe such as an all-out nuclear war that stops this development before it takes off. Jones: How long have these AIs, which can set their own goals — how long have they existed? To what extent can they be independent of human interaction? Schmidhuber: Neural networks like that have existed for over 30 years. My first simple adversarial neural network system of this kind is the one from 1990 described above. You don’t need a teacher there; it's just a little agent running around in the world and trying to invent new experiments that surprise its own prediction machine. Once it has figured out certain parts of the world, the agent will become bored and will move on to more exciting experiments. The simple 1990 systems I mentioned have certain limitations, but in the past three decades, we have also built more sophisticated systems that are setting their own goals and such systems I think will be essential for achieving true intelligence. If you are only imitating humans, you will never go beyond them. So, you really must give AIs the freedom to explore previously unexplored regions of the world in a way that no human is really predefining. Jones: Where is this being done today? Schmidhuber: Variants of neural network-based artificial curiosity are used today for agents that learn to play video games in a human-competitive way. We have also started to use them for automatic design of experiments in fields such as materials science. I bet many other fields will be affected by it: chemistry, biology, drug design, you name it. However, at least for now, these artificial scientists, as I like to call them, cannot yet compete with human scientists. I don’t think it’s going to stay this way but, at the moment, it’s still the case. Sure, AI has made a lot of progress. Since 1997, there have been superhuman chess players, and since 2011, through the DanNet of my team, there have been superhuman visual pattern recognizers. But there are other things where humans, at the moment at least, are much better, in particular, science itself. In the lab we have many first examples of self-directed artificial scientists, but they are not yet convincing enough to appear on the radar screen of the public space, which is currently much more fascinated with simpler systems that just imitate humans and write texts based on previously seen human-written documents. Jones: You speak of these numerous instances dating back 30 years of these lab experiments where these self-driven agents are deciding and learning and moving on once they’ve learned. And I assume that that rate of learning becomes even faster over time. What kind of timeframe are we talking about when this eventually is taken outside of the lab and embedded into society? Schmidhuber: This could still take months or even years :-) Anyway, in the not-too-distant future, we will probably see artificial scientists who are good at devising experiments that allow them to discover new, previously unknown physical laws. As always, we are going to profit from the old trend that has held at least since 1941: every decade compute is getting 100 times cheaper. Jones: How does this trend affect modern AI such as ChatGPT? Schmidhuber: Perhaps you know that all the recent famous AI applications such as ChatGPT and similar models are largely based on principles of artificial neural networks invented in the previous millennium. The main reason why they works so well now is the incredible acceleration of compute per dollar. ChatGPT is driven by a neural network called “Transformer” described in 2017 by Google. I am happy about that because a quarter century earlier in 1991 I had a particular Transformer variant which is now called the “Transformer with linearized self-attention”. Back then, not much could be done with it, because the compute cost was a million times higher than today. But today, one can train such models on half the internet and achieve much more interesting results. Jones: And for how long will this acceleration continue? Schmidhuber: There's no reason to believe that in the next 30 years, we won't have another factor of 1 million and that's going to be really significant. In the near future, for the first time we will have many not-so expensive devices that can compute as much as a human brain. The physical limits of computation, however, are much further out so even if the trend of a factor of 100 every decade continues, the physical limits (of 1051 elementary instructions per second and kilogram of matter) won’t be hit until, say, the mid-next century. Even in our current century, however, we’ll probably have many machines that compute more than all 10 billion human brains collectively and you can imagine, everything will change then! Jones: That is the big question. Is everything going to change? If so, what do you say to the next generation of leaders, currently coming out of college and university. So much of this change is already impacting how they study, how they will work, or how the future of work and livelihood is defined. What is their purpose and how do we change our systems so they will adapt to this new version of intelligence? Schmidhuber: For decades, people have asked me questions like that, because you know what I'm saying now, I have basically said since the 1970s, it’s just that today, people are paying more attention because, back then, they thought this was science fiction. They didn't think that I would ever come close to achieving my crazy life goal of building a machine that learns to become smarter than myself such that I can retire. But now many have changed their minds and think it's conceivable. And now I have two daughters, 23 and 25. People ask me: what do I tell them? They know that Daddy always said, “It seems likely that within your lifetimes, you will have new types of intelligence that are probably going to be superior in many ways, and probably all kinds of interesting ways.” How should they prepare for that? And I kept telling them the obvious: Learn how to learn new things! It's not like in the previous millennium where within 20 years someone learned to be a useful member of society, and then took a job for 40 years and performed in this job until she received her pension. Now things are changing much faster and we must learn continuously just to keep up. I also told my girls that no matter how smart AIs are going to get, learn at least the basics of math and physics, because that’s the essence of our universe, and anybody who understands this will have an advantage, and learn all kinds of new things more easily. I also told them that social skills will remain important, because most future jobs for humans will continue to involve interactions with other humans, but I couldn’t teach them anything about that; they know much more about social skills than I do. You touched on the big philosophical question about people’s purpose. Can this be answered without answering the even grander question: What’s the purpose of the entire universe? We don’t know. But what’s happening right now might be connected to the unknown answer. Don’t think of humans as the crown of creation. Instead view human civilization as part of a much grander scheme, an important step (but not the last one) on the path of the universe from very simple initial conditions towards more and more unfathomable complexity. Now it seems ready to take its next step, a step comparable to the invention of life itself over 3.5 billion years ago. Alas, don’t worry, in the end, all will be good! Jones: Let’s get back to this transformation happening right now with OpenAI. There are many questioning the efficacy and accuracy of ChatGPT, and are concerned its release has been premature. In light of the rampant adoption, educators have banned its use over concerns of plagiarism and how it stifles individual development. Should large language models like ChatGPT be used in school? Schmidhuber: When the calculator was first introduced, instructors forbade students from using it in school. Today, the consensus is that kids should learn the basic methods of arithmetic, but they should also learn to use the “artificial multipliers” aka calculators, even in exams, because laziness and efficiency is a hallmark of intelligence. Any intelligent being wants to minimize its efforts to achieve things. And that's the reason why we have tools, and why our kids are learning to use these tools. The first stone tools were invented maybe 3.5 million years ago; tools just have become more sophisticated over time. In fact, humans have changed in response to the properties of their tools. Our anatomical evolution was shaped by tools such as spears and fire. So, it's going to continue this way. And there is no permanent way of preventing large language models from being used in school. Jones: And when our children, your children graduate, what does their future work look like? Schmidhuber: A single human trying to predict details of how 10 billion people and their machines will evolve in the future is like a single neuron in my brain trying to predict what the entire brain and its tens of billions of neurons will do next year. 40 years ago, before the WWW was created at CERN in Switzerland, who would have predicted all those young people making money as YouTube video bloggers? Nevertheless, let’s make a few limited job-related observations. For a long time, people have thought that desktop jobs may require more intelligence than skills trade or handicraft professions. But now, it turns out that it's much easier to replace certain aspects of desktop jobs than replacing a carpenter, for example. Because everything that works well in AI is happening behind the screen currently, but not so much in the physical world. There are now artificial systems that can read lots of documents and then make really nice summaries of these documents. That is a desktop job. Or you give them a description of an illustration that you want to have for your article and pretty good illustrations are being generated that may need some minimal fine-tuning. But you know, all these desktop jobs are much easier to facilitate than the real tough jobs in the physical world. And it's interesting that the things people thought required intelligence, like playing chess, or writing or summarizing documents, are much easier for machines than they thought. But for things like playing football or soccer, there is no physical robot that can remotely compete with the abilities of a little boy with these skills. So, AI in the physical world, interestingly, is much harder than AI behind the screen in virtual worlds. And it's really exciting, in my opinion, to see that jobs such as plumbers are much more challenging than playing chess or writing another tabloid story. Jones: The way data has been collected in these large language models does not guarantee personal information has not been excluded. Current consent laws already are outdated when it comes to these large language models (LLM). The concern, rightly so, is increasing surveillance and loss of privacy. What is your view on this? Schmidhuber: As I have indicated earlier: are surveillance and loss of privacy inevitable consequences of increasingly complex societies? Super-organisms such as cities and states and companies consist of numerous people, just like people consist of numerous cells. These cells enjoy little privacy. They are constantly monitored by specialized "police cells" and "border guard cells": Are you a cancer cell? Are you an external intruder, a pathogen? Individual cells sacrifice their freedom for the benefits of being part of a multicellular organism. Similarly, for super-organisms such as nations. Over 5000 years ago, writing enabled recorded history and thus became its inaugural and most important invention. Its initial purpose, however, was to facilitate surveillance, to track citizens and their tax payments. The more complex a super-organism, the more comprehensive its collection of information about its constituents. 200 years ago, at least, the parish priest in each village knew everything about all the village people, even about those who did not confess, because they appeared in the confessions of others. Also, everyone soon knew about the stranger who had entered the village, because some occasionally peered out of the window, and what they saw got around. Such control mechanisms were temporarily lost through anonymization in rapidly growing cities but are now returning with the help of new surveillance devices such as smartphones as part of digital nervous systems that tell companies and governments a lot about billions of users. Cameras and drones etc. are becoming increasingly tinier and more ubiquitous. More effective recognition of faces and other detection technology are becoming cheaper and cheaper, and many will use it to identify others anywhere on earth; the big wide world will not offer any more privacy than the local village. Is this good or bad? Some nations may find it easier than others to justify more complex kinds of super-organisms at the expense of the privacy rights of their constituents. Jones: So, there is no way to stop or change this process of collection, or how it continuously informs decisions over time? How do you see governance and rules responding to this, especially amid Italy’s ban on ChatGPT following suspected user data breach and the more recent news about the Meta’s record $1.3billion fine in the company’s handling of user information? Schmidhuber: Data collection has benefits and drawbacks, such as the loss of privacy. How to balance those? I have argued for addressing this through data ownership in data markets. If it is true that data is the new oil, then it should have a price, just like oil. At the moment, the major surveillance platforms such as Meta do not offer users any money for their data and the transitive loss of privacy. In the future, however, we will likely see attempts at creating efficient data markets to figure out the data's true financial value through the interplay between supply and demand. Even some of the sensitive medical data should not be priced by governmental regulators but by patients (and healthy persons) who own it and who may sell or license parts thereof as micro-entrepreneurs in a healthcare data market. Following a previous interview, I gave for one of the largest re-insurance companies , let's look at the different participants in such a data market: patients, hospitals, data companies. (1) Patients with a rare form of cancer can offer more valuable data than patients with a very common form of cancer. (2) Hospitals and their machines are needed to extract the data, e.g., through magnet spin tomography, radiology, evaluations through human doctors, and so on. (3) Companies such as Siemens, Google or IBM would like to buy annotated data to make better artificial neural networks that learn to predict pathologies and diseases and the consequences of therapies. Now the market’s invisible hand will decide about the data’s price through the interplay between demand and supply. On the demand side, you will have several companies offering something for the data, maybe through an app on the smartphone (a bit like a stock market app). On the supply side, each patient in this market should be able to profit from high prices for rare valuable types of data. Likewise, competing data extractors such as hospitals will profit from gaining recognition and trust for extracting data well at a reasonable price. The market will make the whole system efficient through incentives for all who are doing a good job. Soon there will be a flourishing ecosystem of commercial data market advisors and what not, just like the ecosystem surrounding the traditional stock market. The value of the data won’t be determined by governments or ethics committees, but by those who own the data and decide by themselves which parts thereof they want to license to others under certain conditions. At first glance, a market-based system seems to be detrimental to the interest of certain monopolistic companies, as they would have to pay for the data - some would prefer free data and keep their monopoly. However, since every healthy and sick person in the market would suddenly have an incentive to collect and share their data under self-chosen anonymity conditions, there will soon be many more useful data to evaluate all kinds of treatments. On average, people will live longer and healthier, and many companies and the entire healthcare system will benefit. Jones: Finally, what is your view on open source versus the private companies like Google and OpenAI? Is there a danger to supporting these private companies’ large language models versus trying to keep these models open source and transparent, very much like what LAION is doing? Schmidhuber: I signed this open letter by LAION because I strongly favor the open-source movement. And I think it's also something that is going to challenge whatever big tech dominance there might be at the moment. Sure, the best models today are run by big companies with huge budgets for computers, but the exciting fact is that open-source models are not so far behind, some people say maybe six to eight months only. Of course, the private company models are all based on stuff that was created in academia, often in little labs without so much funding, which publish without patenting their results and open source their code and others take it and improved it. Big tech has profited tremendously from academia; their main achievement being that they have scaled up everything greatly, sometimes even failing to credit the original inventors. So, it's very interesting to see that as soon as some big company comes up with a new scaled-up model, lots of students out there are competing, or collaborating, with each other, trying to come up with equal or better performance on smaller networks and smaller machines. And since they are open sourcing, the next guy can have another great idea to improve it, so now there’s tremendous competition also for the big companies. Because of that, and since AI is still getting exponentially cheaper all the time, I don't believe that big tech companies will dominate in the long run. They find it very hard to compete with the enormous open-source movement. As long as you can encourage the open-source community, I think you shouldn't worry too much. Now, of course, you might say if everything is open source, then the bad actors also will more easily have access to these AI tools. And there's truth to that. But as always since the invention of controlled fire, it was good that knowledge about how technology works quickly became public such that everybody could use it. And then, against any bad actor, there's almost immediately a counter actor trying to nullify his efforts. You see, I still believe in our old motto "AI∀" or "AI For All." Jones: Thank you, Juergen for sharing your perspective on this amazing time in history. It’s clear that with new technology, the enormous potential can be matched by disparate and troubling risks which we’ve yet to solve, and even those we have yet to identify. If we are to dispel the fear of a sentient system for which we have no control, humans, alone need to take steps for more responsible development and collaboration to ensure AI technology is used to ultimately benefit society. Humanity will be judged by what we do next.

Have You Used AI Tools for Your Research? Which Ones Are Your Favorite and Why?
reddit
LLM Vibe Score0
Human Vibe Score1
somdipdeyThis week

Have You Used AI Tools for Your Research? Which Ones Are Your Favorite and Why?

Over a decade ago, I wrote two articles: "A B\ginner’s Guide to Computer Science Research" and "How to Start a Research Work in Computer Science"*. These articles were widely used in universities worldwide to help students and early-career researchers navigate academic research in Computer Science (CS). Fast forward to 2025, the research landscape has evolved significantly, especially in AI and CS, with the advent of AI-powered research tools, open-access repositories, and real-time collaboration platforms. These tools have made research more accessible, enabling students and professionals to work more efficiently while focusing on real innovation. I recently published an updated article in The Times of India, presenting an Eight-Step Approach to Research framework designed for modern AI and CS research. This framework integrates AI-powered literature review tools, reference management systems, open science platforms, and collaborative research methods to enhance the research workflow. 🚀 Would love to hear from the ML research community: 1️⃣ Have you used any AI-powered tools or automation techniques in your research? Which ones do you find most useful? 2️⃣ Do you have recommendations for other AI tools that weren’t covered in the article but could benefit researchers? 3️⃣ How do you think AI will shape the future of academic research and discovery? 📖 Read the article here: How to Start Research in Computer Science & AI in 2025 – An Updated Framework Block Diagram of “Eight-Step Approach to Research” in 2025 Let’s discuss! What are your go-to tools for making research more efficient in 2025?

12 months from idea to product - bootstrapping my own mobile app from 0
reddit
LLM Vibe Score0
Human Vibe Score1
MaartinBlack1996This week

12 months from idea to product - bootstrapping my own mobile app from 0

Introduction It has taken 12 months to develop an app that uses a camera to seamlessly detect fridge ingredients and generate recipes—solving the everyday problem I faced while traveling: "What should I cook for dinner today?" Although the end product has evolved from the initial concept, the ingredient detection feature remains one of the key elements that makes this app truly unique. When I started Keto, the biggest challenge I faced was tracking carbs, typically done through barcode scanning or manual searches. While Swifto offers both of these options, we are proud to introduce a feature that allows you to extract net carb values from a single image with just one click. We’ve combined AI with a great user experience to ensure that anyone embarking on their Keto journey can track their progress with ease. My Experience The app is now at a stage where I can truly seek market validation. Yes, this journey took me around 12 months, starting with the idea, creating the website, and developing the app's UI/UX and backend. At this point, many people might wonder: "Did you validate your idea before? Why create such a complex app without first understanding if there's a market need?" While this approach is undoubtedly risky and may not pay off in the future, I had a strong belief that this product could only be validated when people experienced how it works and saw how seamless the UX is compared to other similar apps. Would I Do It Again? Probably not. While developing the mobile app, I learned a lot about how mobile apps are advertised on the Google Play Store and how challenging it is to break into niche markets. You can develop the best application out there, but if no one sees it, it will never reach the top searches, which is crucial for any app's organic reach. I'll need to devise very creative strategies to gain the attention of those who truly matter for this product's validation and then go from there. However, it seems this will require much more effort than I initially anticipated. I'm open to any questions/suggestions.

Turning a Social Media Agency into $1.5 Million in Revenue
reddit
LLM Vibe Score0
Human Vibe Score1
FounderFolksThis week

Turning a Social Media Agency into $1.5 Million in Revenue

Steffie here from Founder Folks, with a recent interview I did with Jason Yormark from Socialistics. Here is his story how he started and grew his social media agency. Name: Jason Yormark Company: Socialistics Employee Size: 10 Revenue: $1,500,000/year Year Founded: 2018 Website: www.socialistics.com Technology Tools: ClickUp, Slack, KumoSpace, Google Workspace, Shift, Zapier, Klayvio, Zoom, Gusto, Calendly, Pipedrive Introduction: I am the founder of Socialistics (www.socialistics.com), a leading social media agency that helps businesses turn their social media efforts into real measurable results. I am a 20+ year marketing veteran whose prior work has included launching and managing social media efforts for Microsoft Advertising, Office for Mac, the Air Force, and Habitat for Humanity. I have been recognized as a top B2B social media influencer and thought leader on multiple lists and publications including Forbes, ranking #30 on their 2012 list. I've recently published the book Anti-Agency: A Realistic Path to a $1,000,000 Business, and host the Anti Agency podcast where I share stories of doing business differently. You can learn more about me at www.jasonyormark.com. The Inspiration To Become An Entrepreneur: I’ve been involved with social media marketing since 2007, and have pretty much carved my career out of that. It was a natural progression for me to transition into starting a social media agency. From Idea to Reality: For me realistically, I had to side hustle something long enough to build it up to a point that I could take the leap and risks going full time on my own. For these reasons, I built the company and brand on the side putting out content regularly, and taking on side hustle projects to build out my portfolio and reputation. This went on for about 18 months at which point I had reached the breaking point of my frustrations of working for someone else, and felt I was ready to take the leap since I had the wheels in motion. While balancing a full-time job, I made sure not to overdo it. My main focus was on building out the website/brand and putting out content regularly to gain some traction and work towards some search visibility. I only took on 1-2 clients at a time to make sure I could still meet their needs while balancing a full time job. Attracting Customers: Initially I tapped into my existing network to get my first few clients. Then it was a mix of trade shows, networking events, and throwing a bit of money at paid directories and paid media. This is really a long game. You have to plant seeds over time with people and nurture those relationships over time. A combination of being helpful, likable and a good resource for folks will position you to make asks in the future. If people respect and like you, it makes it much easier to approach for opportunities when the time comes. Overcoming Challenges in Starting the Business: Plenty. Learning when to say no, only hiring the very best, and ultimately the realization that owning a marketing agency is going to have hills and valleys no matter what you do. Costs and Revenue: My largest expense by FAR is personnel, comprising between 50-60% of the business’ expenses, and justifiably so. It’s a people business. Our revenue doubled from the years 2018 through 2021, and we’ve seen between 10-20% growth year over year. A Day in the Life: I’ve successfully removed myself from the day to day of the business and that’s by design. I have a tremendous team, and a rock start Director of Operations who runs the agency day to day. It frees me up to pursue other opportunities, and to mentor, speak and write more. It also allows me to evangelize the book I wrote detailing my journey to a $1M business titled: Anti-Agency: A Realistic Path To A $1,000,000 Business (www.antiagencybook.com). Staying Ahead in a Changing Landscape: You really have to stay on top of technology trends. AI is a huge impact on marketing these days, so making sure we are up to speed on that, and not abusing it or relying on it too much. You also have to embrace that technology and not hide the fact that it’s used. Non-marketers still don’t and can’t do the work regardless of how much AI can help, so we just need to be transparent and smart on how we integrate it, but the fact is, technology will never replace creativity. As an agency, it’s imperative that we operationally allow our account managers to have bandwidth to be creative for clients all the time. It’s how we keep clients and buck the trend of companies changing agencies every year or two. The Vision for Socialistics: Continuing to evolve to cater to our clients through learning, education, and staying on top of the latest tools and technologies. Attracting bigger and more exciting clients, and providing life changing employment opportunities.

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies)
reddit
LLM Vibe Score0
Human Vibe Score1
Royal_Rest8409This week

How a founder built a B2B AI startup to serve with 65+ global brands (including Fortune500 companies)

AI Palette is an AI-driven platform that helps food and beverage companies predict emerging product trends. I had the opportunity recently to sit down with the founder to get his advice on building an AI-first startup, which he'll be going through in this post. About AI Palette: Co-founders: >!2 (Somsubhra GanChoudhuri, Himanshu Upreti)!!100+!!$12.7M USD!!AI-powered predictive analytics for the CPG (Consumer Packaged Goods) industry!!Signed first paying customer in the first year!!65+ global brands, including Cargill, Diageo, Ajinomoto, Symrise, Mondelez, and L’Oréal, use AI Palette!!Every new product launched has secured a paying client within months!!Expanded into Beauty & Personal Care (BPC), onboarding one of India’s largest BPC companies within weeks!!Launched multiple new product lines in the last two years, creating a unified suite for brand innovation!Identify the pain points in your industry for ideas* When I was working in the flavour and fragrance industry, I noticed a major issue CPG companies faced: launching a product took at least one to two years. For instance, if a company decided today to launch a new juice, it wouldn’t hit the market until 2027. This long timeline made it difficult to stay relevant and on top of trends. Another big problem I noticed was that companies relied heavily on market research to determine what products to launch. While this might work for current consumer preferences, it was highly inefficient since the product wouldn’t actually reach the market for several years. By the time the product launched, the consumer trends had already shifted, making that research outdated. That’s where AI can play a crucial role. Instead of looking at what consumers like today, we realised that companies should use AI to predict what they will want next. This allows businesses to create products that are ahead of the curve. Right now, the failure rate for new product launches is alarmingly high, with 8 out of 10 products failing. By leveraging AI, companies can avoid wasting resources on products that won’t succeed, leading to better, more successful launches. Start by talking to as many industry experts as possible to identify the real problems When we first had the idea for AI Palette, it was just a hunch, a gut feeling—we had no idea whether people would actually pay for it. To validate the idea, we reached out to as many people as we could within the industry. Since our focus area was all about consumer insights, we spoke to professionals in the CPG sector, particularly those in the insights departments of CPG companies. Through these early conversations, we began to see a common pattern emerge and identified the exact problem we wanted to solve. Don’t tell people what you’re building—listen to their frustrations and challenges first. Going into these early customer conversations, our goal was to listen and understand their challenges without telling them what we were trying to build. This is crucial as it ensures that you can gather as much data about the problem to truly understand it and that you aren't biasing their answers by showing your solution. This process helped us in two key ways: First, it validated that there was a real problem in the industry through the number of people who spoke about experiencing the same problem. Second, it allowed us to understand the exact scale and depth of the problem—e.g., how much money companies were spending on consumer research, what kind of tools they were currently using, etc. Narrow down your focus to a small, actionable area to solve initially. Once we were certain that there was a clear problem worth solving, we didn’t try to tackle everything at once. As a small team of two people, we started by focusing on a specific area of the problem—something big enough to matter but small enough for us to handle. Then, we approached customers with a potential solution and asked them for feedback. We learnt that our solution seemed promising, but we wanted to validate it further. If customers are willing to pay you for the solution, it’s a strong validation signal for market demand. One of our early customer interviewees even asked us to deliver the solution, which we did manually at first. We used machine learning models to analyse the data and presented the results in a slide deck. They paid us for the work, which was a critical moment. It meant we had something with real potential, and we had customers willing to pay us before we had even built the full product. This was the key validation that we needed. By the time we were ready to build the product, we had already gathered crucial insights from our early customers. We understood the specific information they wanted and how they wanted the results to be presented. This input was invaluable in shaping the development of our final product. Building & Product Development Start with a simple concept/design to validate with customers before building When we realised the problem and solution, we began by designing the product, but not by jumping straight into coding. Instead, we created wireframes and user interfaces using tools like InVision and Figma. This allowed us to visually represent the product without the need for backend or frontend development at first. The goal was to showcase how the product would look and feel, helping potential customers understand its value before we even started building. We showed these designs to potential customers and asked for feedback. Would they want to buy this product? Would they pay for it? We didn’t dive into actual development until we found a customer willing to pay a significant amount for the solution. This approach helped us ensure we were on the right track and didn’t waste time or resources building something customers didn’t actually want. Deliver your solution using a manual consulting approach before developing an automated product Initially, we solved problems for customers in a more "consulting" manner, delivering insights manually. Recall how I mentioned that when one of our early customer interviewees asked us to deliver the solution, we initially did it manually by using machine learning models to analyse the data and presenting the results to them in a slide deck. This works for the initial stages of validating your solution, as you don't want to invest too much time into building a full-blown MVP before understanding the exact features and functionalities that your users want. However, after confirming that customers were willing to pay for what we provided, we moved forward with actual product development. This shift from a manual service to product development was key to scaling in a sustainable manner, as our building was guided by real-world feedback and insights rather than intuition. Let ongoing customer feedback drive iteration and the product roadmap Once we built the first version of the product, it was basic, solving only one problem. But as we worked closely with customers, they requested additional features and functionalities to make it more useful. As a result, we continued to evolve the product to handle more complex use cases, gradually developing new modules based on customer feedback. Product development is a continuous process. Our early customers pushed us to expand features and modules, from solving just 20% of their problems to tackling 50–60% of their needs. These demands shaped our product roadmap and guided the development of new features, ultimately resulting in a more complete solution. Revenue and user numbers are key metrics for assessing product-market fit. However, critical mass varies across industries Product-market fit (PMF) can often be gauged by looking at the size of your revenue and the number of customers you're serving. Once you've reached a certain critical mass of customers, you can usually tell that you're starting to hit product-market fit. However, this critical mass varies by industry and the type of customers you're targeting. For example, if you're building an app for a broad consumer market, you may need thousands of users. But for enterprise software, product-market fit may be reached with just a few dozen key customers. Compare customer engagement and retention with other available solutions on the market for product-market fit Revenue and the number of customers alone isn't always enough to determine if you're reaching product-market fit. The type of customer and the use case for your product also matter. The level of engagement with your product—how much time users are spending on the platform—is also an important metric to track. The more time they spend, the more likely it is that your product is meeting a crucial need. Another way to evaluate product-market fit is by assessing retention, i.e whether users are returning to your platform and relying on it consistently, as compared to other solutions available. That's another key indication that your solution is gaining traction in the market. Business Model & Monetisation Prioritise scalability Initially, we started with a consulting-type model where we tailor-made specific solutions for each customer use-case we encountered and delivered the CPG insights manually, but we soon realized that this wasn't scalable. The problem with consulting is that you need to do the same work repeatedly for every new project, which requires a large team to handle the workload. That is not how you sustain a high-growth startup. To solve this, we focused on building a product that would address the most common problems faced by our customers. Once built, this product could be sold to thousands of customers without significant overheads, making the business scalable. With this in mind, we decided on a SaaS (Software as a Service) business model. The benefit of SaaS is that once you create the software, you can sell it to many customers without adding extra overhead. This results in a business with higher margins, where the same product can serve many customers simultaneously, making it much more efficient than the consulting model. Adopt a predictable, simplistic business model for efficiency. Look to industry practices for guidance When it came to monetisation, we considered the needs of our CPG customers, who I knew from experience were already accustomed to paying annual subscriptions for sales databases and other software services. We decided to adopt the same model and charge our customers an annual upfront fee. This model worked well for our target market, aligning with industry standards and ensuring stable, recurring revenue. Moreover, our target CPG customers were already used to this business model and didn't have to choose from a huge variety of payment options, making closing sales a straightforward and efficient process. Marketing & Sales Educate the market to position yourself as a thought leader When we started, AI was not widely understood, especially in the CPG industry. We had to create awareness around both AI and its potential value. Our strategy focused on educating potential users and customers about AI, its relevance, and why they should invest in it. This education was crucial to the success of our marketing efforts. To establish credibility, we adopted a thought leadership approach. We wrote blogs on the importance of AI and how it could solve problems for CPG companies. We also participated in events and conferences to demonstrate our expertise in applying AI to the industry. This helped us build our brand and reputation as leaders in the AI space for CPG, and word-of-mouth spread as customers recognized us as the go-to company for AI solutions. It’s tempting for startups to offer products for free in the hopes of gaining early traction with customers, but this approach doesn't work in the long run. Free offerings don’t establish the value of your product, and customers may not take them seriously. You should always charge for pilots, even if the fee is minimal, to ensure that the customer is serious about potentially working with you, and that they are committed and engaged with the product. Pilots/POCs/Demos should aim to give a "flavour" of what you can deliver A paid pilot/POC trial also gives you the opportunity to provide a “flavour” of what your product can deliver, helping to build confidence and trust with the client. It allows customers to experience a detailed preview of what your product can do, which builds anticipation and desire for the full functionality. During this phase, ensure your product is built to give them a taste of the value you can provide, which sets the stage for a broader, more impactful adoption down the line. Fundraising & Financial Management Leverage PR to generate inbound interest from VCs When it comes to fundraising, our approach was fairly traditional—we reached out to VCs and used connections from existing investors to make introductions. However, looking back, one thing that really helped us build momentum during our fundraising process was getting featured in Tech in Asia. This wasn’t planned; it just so happened that Tech in Asia was doing a series on AI startups in Southeast Asia and they reached out to us for an article. During the interview, they asked if we were fundraising, and we mentioned that we were. As a result, several VCs we hadn’t yet contacted reached out to us. This inbound interest was incredibly valuable, and we found it far more effective than our outbound efforts. So, if you can, try to generate some PR attention—it can help create inbound interest from VCs, and that interest is typically much stronger and more promising than any outbound strategies because they've gone out of their way to reach out to you. Be well-prepared and deliberate about fundraising. Keep trying and don't lose heart When pitching to VCs, it’s crucial to be thoroughly prepared, as you typically only get one shot at making an impression. If you mess up, it’s unlikely they’ll give you a second chance. You need to have key metrics at your fingertips, especially if you're running a SaaS company. Be ready to answer questions like: What’s your retention rate? What are your projections for the year? How much will you close? What’s your average contract value? These numbers should be at the top of your mind. Additionally, fundraising should be treated as a structured process, not something you do on the side while juggling other tasks. When you start, create a clear plan: identify 20 VCs to reach out to each week. By planning ahead, you’ll maintain momentum and speed up the process. Fundraising can be exhausting and disheartening, especially when you face multiple rejections. Remember, you just need one investor to say yes to make it all worthwhile. When using funds, prioritise profitability and grow only when necessary. Don't rely on funding to survive. In the past, the common advice for startups was to raise money, burn through it quickly, and use it to boost revenue numbers, even if that meant operating at a loss. The idea was that profitability wasn’t the main focus, and the goal was to show rapid growth for the next funding round. However, times have changed, especially with the shift from “funding summer” to “funding winter.” My advice now is to aim for profitability as soon as possible and grow only when it's truly needed. For example, it’s tempting to hire a large team when you have substantial funds in the bank, but ask yourself: Do you really need 10 new hires, or could you get by with just four? Growing too quickly can lead to unnecessary expenses, so focus on reaching profitability as soon as possible, rather than just inflating your team or burn rate. The key takeaway is to spend your funds wisely and only when absolutely necessary to reach profitability. You want to avoid becoming dependent on future VC investments to keep your company afloat. Instead, prioritize reaching break-even as quickly as you can, so you're not reliant on external funding to survive in the long run. Team-Building & Leadership Look for complementary skill sets in co-founders When choosing a co-founder, it’s important to find someone with a complementary skill set, not just someone you’re close to. For example, I come from a business and commercial background, so I needed someone with technical expertise. That’s when I found my co-founder, Himanshu, who had experience in machine learning and AI. He was a great match because his technical knowledge complemented my business skills, and together we formed a strong team. It might seem natural to choose your best friend as your co-founder, but this can often lead to conflict. Chances are, you and your best friend share similar interests, skills, and backgrounds, which doesn’t bring diversity to the table. If both of you come from the same industry or have the same strengths, you may end up butting heads on how things should be done. Having diverse skill sets helps avoid this and fosters a more collaborative working relationship. Himanshu (left) and Somsubhra (right) co-founded AI Palette in 2018 Define roles clearly to prevent co-founder conflict To avoid conflict, it’s essential that your roles as co-founders are clearly defined from the beginning. If your co-founder and you have distinct responsibilities, there is no room for overlap or disagreement. This ensures that both of you can work without stepping on each other's toes, and there’s mutual respect for each other’s expertise. This is another reason as to why it helps to have a co-founder with a complementary skillset to yours. Not only is having similar industry backgrounds and skillsets not particularly useful when building out your startup, it's also more likely to lead to conflicts since you both have similar subject expertise. On the other hand, if your co-founder is an expert in something that you're not, you're less likely to argue with them about their decisions regarding that aspect of the business and vice versa when it comes to your decisions. Look for employees who are driven by your mission, not salary For early-stage startups, the first hires are crucial. These employees need to be highly motivated and excited about the mission. Since the salary will likely be low and the work demanding, they must be driven by something beyond just the paycheck. The right employees are the swash-buckling pirates and romantics, i.e those who are genuinely passionate about the startup’s vision and want to be part of something impactful beyond material gains. When employees are motivated by the mission, they are more likely to stick around and help take the startup to greater heights. A litmus test for hiring: Would you be excited to work with them on a Sunday? One of the most important rounds in the hiring process is the culture fit round. This is where you assess whether a candidate shares the same values as you and your team. A key question to ask yourself is: "Would I be excited to work with this person on a Sunday?" If there’s any doubt about your answer, it’s likely not a good fit. The idea is that you want employees who align with the company's culture and values and who you would enjoy collaborating with even outside of regular work hours. How we structure the team at AI Palette We have three broad functions in our organization. The first two are the big ones: Technical Team – This is the core of our product and technology. This team is responsible for product development and incorporating customer feedback into improving the technology Commercial Team – This includes sales, marketing, customer service, account managers, and so on, handling everything related to business growth and customer relations. General and Administrative Team – This smaller team supports functions like finance, HR, and administration. As with almost all businesses, we have teams that address the two core tasks of building (technical team) and selling (commercial team), but given the size we're at now, having the administrative team helps smoothen operations. Set broad goals but let your teams decide on execution What I've done is recruit highly skilled people who don't need me to micromanage them on a day-to-day basis. They're experts in their roles, and as Steve Jobs said, when you hire the right person, you don't have to tell them what to do—they understand the purpose and tell you what to do. So, my job as the CEO is to set the broader goals for them, review the plans they have to achieve those goals, and periodically check in on progress. For example, if our broad goal is to meet a certain revenue target, I break it down across teams: For the sales team, I’ll look at how they plan to hit that target—how many customers they need to sell to, how many salespeople they need, and what tactics and strategies they plan to use. For the technical team, I’ll evaluate our product offerings—whether they think we need to build new products to attract more customers, and whether they think it's scalable for the number of customers we plan to serve. This way, the entire organization's tasks are cascaded in alignment with our overarching goals, with me setting the direction and leaving the details of execution to the skilled team members that I hire.

We create AI software and provide AI automation for companies. Here is a list of the best AI tools for sales IMHO
reddit
LLM Vibe Score0
Human Vibe Score1
IntellectualAINCThis week

We create AI software and provide AI automation for companies. Here is a list of the best AI tools for sales IMHO

Here are some AI tools that are useful for sales. I tried to touch as many different parts of the sales process so the tools are all quite different but all useful for sales. I tried to include some of the best and underrated AI tools. Most of them are free so check them out if you want. I did not include ChatGPT as it can basically be used for anything with the right prompts. So these tools will be more research-oriented. A quick disclaimer – I work for the company Idealink where we create custom ChatGPT for businesses and other AI products. Apollo AI Seamless AI CoPilot AI Lavender AI Regie AI Gemini Plusdocs Make Midjourney Fireflies AI Apollo AI - Find potential customers Apollo is a platform for sales and business development. It offers a range of tools to find and engage with ideal customers. The platform has an extensive B2B database and features that streamline the sales process from prospecting to closing deals. Key Features: Extensive B2B Database: Apollo boasts a large, accurate database of over 275 million contacts, providing a wealth of potential leads and opportunities for sales teams. Data Enrichment and Lead Insights: The platform offers data enrichment capabilities, ensuring CRM systems are continuously updated with detailed and actionable lead information. AI-Driven Sales Engagement: Apollo's AI technology assists in crafting effective communication and prioritizing high-value leads, enhancing the overall sales engagement process. Comprehensive Sales Tools: The platform provides an integrated suite of tools for email, call, and social media engagement, combined with analytics and automation features to streamline the sales cycle. Tailored Solutions for Teams: Apollo offers customized solutions for different team types, including sales and business development, founders, and marketing teams, addressing specific needs and goals. Seamless AI - Sale process made easier Seamless.AI is an innovative B2B sales lead generation solution that allows sales teams to efficiently connect with their ideal customers. The platform's features provide accurate and up-to-date contact information and integrate easily with existing sales and marketing tools. Key Features: Real-Time Search Engine: Seamless.AI uses AI to scour the web in real time, ensuring the contact information for sales leads is current and accurate. Comprehensive Integration: Easily integrates with popular CRMs and sales tools like Salesforce, HubSpot, and LinkedIn Sales Navigator, enhancing productivity and eliminating manual data entry. Chrome Extension: Enhances web browsing experience for sales teams, allowing them to build lead lists directly from their browser. Pitch Intelligence and Writer: Tools for crafting effective sales messages and marketing content, personalized for each potential customer. Data Enrichment and Autopilot: Keeps customer data current and automates lead-building, supporting consistent lead generation. Buyer Intent Data and Job Changes: Offers insights into potential customers' buying intentions and keeps track of significant job changes within key accounts. CoPilot AI - Helps sales reps manage leads CoPilot AI is an advanced AI-powered sales support platform designed for B2B sales teams and agencies to drive consistent revenue growth. The tool focuses on using LinkedIn for sales prospecting, engagement, and conversion. Key Features: LinkedIn Lead Generation: Targets and automates outreach to high-intent LinkedIn leads, enhancing efficiency and scalability in lead generation. Personalized Messaging Automation: Facilitates sending of personalized, one-click messages at scale, maintaining a human touch in digital interactions. Sales Conversion Insights: Offers tools to understand and adapt to prospects' communication styles, improving the likelihood of conversion. Sales Process Optimization: Provides analytics to evaluate and refine sales strategies, identifying opportunities for improvement in the sales funnel. Industry Versatility: Adapts to diverse industries, offering tailored solutions for B2B sales, marketing, HR, and financial services sectors. Collaborative Team Tools: Enables team synchronization and collaboration, boosting productivity and synergy in sales teams Lavender AI - Email AI assistant Lavender AI is an AI-powered email tool that helps users write better emails. It provides real-time feedback and personalized suggestions to optimize email communication efficiency. Key Features: Email Coaching and Scoring: Lavender evaluates emails using AI and a vast database of email interactions, offering a score and tips for improvement. It identifies factors that might reduce the likelihood of receiving a reply, helping users refine their email content. Personalization Assistant: This feature integrates prospect data directly into the user's email platform, suggesting personalization strategies based on recipient data and personality insights to foster deeper connections. Adaptive Improvement: Lavender's scoring and recommendations evolve in real-time with changing email behaviors and practices, thanks to its generative AI and extensive data analysis, ensuring users always follow the best practices. Data-Driven Managerial Insights: The platform provides managers with valuable insights derived from actual email interactions, aiding them in coaching their teams more effectively based on real performance and communication trends. Broad Integration Capability: Lavender integrates with various email and sales platforms including Gmail, Outlook, and others, making it versatile for different user preferences and workflows. Regie AI - Great for business intelligence Regie.ai simplifies the sales prospecting process for businesses, using GenAI and automation to improve interactions with prospects. The platform offers tools like Auto-Pilot for automatic prospecting and meeting scheduling, Co-Pilot for sales rep support, and integrations with various CRM and sales engagement platforms. It also includes a Chrome Extension and CMS for content management and customization. Key Features: Automated Prospecting with Auto-Pilot: Regie.ai's Auto-Pilot feature autonomously prospects and schedules meetings, using Generative AI for Sales Agents to enhance outbound sales efforts. Audience Discovery and Content Generation: The platform identifies target accounts not in the CRM, generating relevant, on-brand content for each message, thus ensuring efficiency in list building and message personalization. Outbound Prioritization and Dynamic Engagement: It utilizes engagement and intent data to prioritize outreach to in-market prospects and adjust engagement strategies based on buyer responsiveness. Full Funnel Brand Protection and Analytics: Regie.ai ensures consistent use of marketing-approved language in all sales outreach and provides insights into campaign and document performance, thereby safeguarding brand integrity throughout the sales funnel. Gemini - AI powered conversational platform Gemini is a large language model chatbot developed by Google AI. It can generate text, translate languages, write different creative text formats, and answer your questions in an informative way. It is still under development but has learned to perform many kinds of tasks. Key features: Generate different creative text formats of text content (poems, code, scripts, musical pieces, email, letters, etc.) Answer your questions in an informative way, even if they are open ended, challenging, or strange. Translate languages Follow your instructions and complete your requests thoughtfully. Plusdocs (Plus AI) - AI tool for presentations Plus AI is a versatile tool that helps improve presentations and integrates with Slides in a simple and intuitive way. It simplifies slide creation and customization by converting text into slides and utilizing AI for various languages. Key Features: Text-to-Slide Conversion: Plus AI excels in transforming textual content into visually appealing slides, streamlining the presentation creation process. Multilingual AI Support: The tool is equipped to handle various languages, making it adaptable for a global user base. Professional Design Options: Users have access to professionally designed slide layouts, enabling the creation of polished presentations with ease. Customization and AI Design: Plus AI allows for extensive customization, including the use of AI for designing and editing slides, ensuring unique and personalized presentations. Live Snapshots and Templates: The tool offers live snapshots for real-time updates and a wide range of templates for quick and effective slide creation. Make - AI automation Make is a powerful visual platform that allows users to build and automate tasks, workflows, apps, and systems. It offers an intuitive, no-code interface that empowers users across various business functions to design and implement complex processes without the need for developer resources. Key Features: No-Code Visual Workflow Builder: Make's core feature is its user-friendly interface that allows for the creation of intricate workflows without coding expertise, making it accessible to a wide range of users. Extensive App Integration: The platform boasts compatibility with over 1000 apps, facilitating seamless connections and data sharing across diverse tools and systems. Custom Automation Solutions: Make enables personalized automation strategies, fitting various business needs from marketing automation to IT workflow control. Template Library: Users can jumpstart their automation projects with a vast collection of pre-built templates, which are customizable to fit specific workflow requirements. Enterprise-Level Solutions: Make offers advanced options for larger organizations, including enhanced security, single sign-on, custom functions, and dedicated support. Midjourney - Making sales content Midjourney is an AI-based image generation tool that changes the way we visualise and create digital art. It offers a lot of artistic possibilities, allowing users to create stunning images from text prompts. This innovative service caters to artists, designers, and anyone seeking to bring their creative visions to life. Key Features: Advanced AI Image Generation: Midjourney's core strength lies in its powerful AI algorithms, which interpret text prompts to generate detailed, high-quality images. This feature allows users to explore an endless array of visual concepts and styles. User-driven Customization: The tool offers significant control over the image creation process, enabling users to guide the AI with specific instructions, ensuring that the final output aligns closely with their vision. Diverse Artistic Styles: Midjourney can mimic various artistic styles, from classical to contemporary, providing users with a wide range of aesthetic options for their creations. Collaboration and Community Features: The platform fosters a community of users who can share, critique, and collaborate on artistic projects, enriching the creative experience. Fireflies AI - Sales meeting assistant Fireflies.ai is a powerful tool for improving team productivity and efficiency in managing meetings and voice conversations. It offers a range of features to simplify the process of capturing, organizing, and analyzing meeting content. Key Features: Automatic Meeting Transcription: Fireflies.ai can transcribe meetings held on various video-conferencing platforms and dialers. The tool captures both video and audio, providing transcripts quickly and efficiently. AI-Powered Search and Summarization: It allows users to review long meetings in a fraction of the time, highlighting key action items, tasks, and questions. Users can filter and focus on specific topics discussed in meetings. Improved Collaboration: The tool enables adding comments, pins, and reactions to specific conversation parts. Users can create and share soundbites and integrate meeting notes with popular collaboration apps such as Slack, Notion, and Asana. Conversation Intelligence: Fireflies.ai offers insights into meetings by tracking metrics like speaker talk time and sentiment. It helps in coaching team members and improving performance in sales, recruiting, and other internal processes. Workflow Automation: The AI assistant from Fireflies.ai can log call notes and activities in CRMs, create tasks through voice commands, and share meeting recaps instantly across various platforms. Comprehensive Knowledge Base: It compiles all voice conversations into an easily accessible and updatable knowledge base, with features to organize meetings into channels and set custom privacy controls. I’ll keep updating this little guide, so add your comments and I’ll try to add more tools. This is all just a personal opinion, so it’s completely cool if you disagree with it. Btw here is the link to the full blog post about all the AI tools in a bit more depth.

Interview with founder of ReadyPlayerMe (raised $70M+ from a16z)
reddit
LLM Vibe Score0
Human Vibe Score1
Due_Cryptographer461This week

Interview with founder of ReadyPlayerMe (raised $70M+ from a16z)

Thanks to everyone who replied to my previous post with the questions you had for Rainer, I added some of them into this interview. I’m Nikita of Databas3 , and that’s my first interview in a series where I’m learning more about the journey of the best tech and web3 founders. Would appreciate your feedback and suggestions for the next guest! Nikita: Let’s begin with a brief introduction. Can you share a bit about yourself and how the business started? Rainer: I’m Rainer, the CTO of ReadyPlayerMe. Our journey began in 2013 with four co-founders. Over the years, our focus has shifted mainly around our product’s evolution, but our core idea always revolved around virtual actors or virtual people. Our initial venture was into hardware. We created the first full-body scanner in the Nordics, a significant step in photogrammetry. This led us to develop the Luna Scanner, a three-meter tall structure designed to capture facial features and likenesses. When Facebook acquired Oculus in 2014, we foresaw the potential of VR and virtual worlds, especially in social experiences. Nikita: Interesting. How did you move on from there? Rainer: Recognizing the limitations of hardware, we transitioned into software. Our early scanner designs had limitations in scalability. For example, our three-meter tall scanner wasn’t a feasible solution for scanning millions of people. So, we leveraged the datasets from our initial projects and designed a mobile version, making facial scanning as easy as using your phone. Around 2015, this was a new territory, as facial scanning wasn’t a mainstream application. Nikita: What were the early applications of these scanned models? Rainer: In the beginning, we focused on 3D printed figurines from full-body scans. However, as we shifted to facial scanning, we licensed our technology to gaming companies, collaborating with giants like Wargaming and Tencent. We even ventured into virtual fittings with H&M. Each collaboration was custom-tailored, blending our technology with their systems. This model made us cash flow positive. Nikita: So this was the beginning of your foray into the gaming industry? Rainer: Precisely. The demand from gaming companies was substantial. As we built custom solutions for these enterprises, we saw a bigger potential. While our cash flow was positive, we realized the challenge of scaling through exclusive enterprise deals. We envisioned our avatar creation tech reaching indie games and beyond. Nikita: And that led to the birth of ReadyPlayerMe? Rainer: Exactly. Once we understood our market direction, we quickly developed the first iteration of ReadyPlayerMe as a web-based experience, emphasizing easy integration for game developers. The initial version was a character builder, allowing users to personalize their avatars, which many adopted for their social media profiles. Our goal was to create avatars that users could connect with and use across various platforms. Instead of licensing our technology, we offered it for free to everyone. As ReadyPlayerMe gained traction, especially in VR applications, we secured funding to further our mission. Nikita: Your growth seems swift and organic. Were there any challenges? Rainer: Our focus on easy integration significantly fueled our adoption. Pairing that with personalized avatars resonated well with our audience. But like any venture, we’ve faced our share of challenges and have always aimed to evolve and better our offerings. The rapid growth in Web3 projects and virtual worlds made personalization and customization more important. With the NFT boom, you could add utility by allowing access to selected collections. This played into web-based games and metaverse applications. The shift towards Web3 and personalization provided a significant tailwind for us. Many used our characters as profile pictures on social media. Nikita: I’ve heard from other founders that a16z really values viral marketing. Was this one reason they wanted to invest in your project? How was the process with them? Rainer: When a16z reached out, it felt like a natural fit. We wanted investors who understood the gaming space. Our main market is Web3, but we’re exploring the top games market. Their expertise in gaming was invaluable. They’ve been very supportive throughout. We were fortunate to be on their radar. Nikita: So your early growth and organic traction played a role in attracting investors? Rainer: Definitely. Early product growth and the potential future trajectory were essential in our discussions. Nikita: As the CTO, you must have faced challenges. Can you speak about the tech side and its evolution? Rainer: The early version of our platform was built by in-house engineers. As we grew, we had to adapt to increasing complexities and ensure we had the right team to execute our vision. My role often shifted between product management and tech, depending on the need. Nikita: It sounds like the startup environment remains strong within your company. Rainer: Absolutely. We’re all committed, hands-on, and working towards building the best product. Nikita: You mentioned the team earlier. How many people are in your team now? Rainer: We have 70 people, with about half in product and engineering. Nikita: And did you hire the tech team? Rainer: We brought on a head of engineering at the beginning of this year. He’s been instrumental in scaling the engineering organization, from increasing the headcount to refining engineering processes. We’ve recently reorganized into domain-specific teams. As the team grows, regular reorganization ensures we focus on delivering specific customer value. Every stage requires attention to the team’s composition to ensure efficient delivery. Nikita: Any advice for founders just starting with their first startup? Rainer: Focus on customer value, no matter how niche it might seem initially. Begin with a specific problem and solution, then expand from there. You don’t need a massive project right away. Begin small, prove the concept, and scale from there. Nikita: You’ve mentioned your love for books and podcasts. Any recommendations? Rainer: For startups, “High Growth Handbook” and “Lean Startup” are must-reads. “Working Backwards” offers insights into Amazon’s customer-centric approach. For podcasts, I listen to “Rework,” “Lenny’s Podcast,” and “Huberman Lab.” Nikita: All of us have some side project ideas from time to time. How do you handle these when managing a big project? Rainer: Over the years, I’ve built various side projects. Some are small applications to solve immediate problems, like a menu bar app for AirPods which made it to No. 1 on Product Hunt, and was nominated for Golden Kitty Award. I sometimes delve into 3D and AI, merging them for technical demos. I keep a list of ideas and pick from them as the urge arises. Nikita: Any final thoughts or advice? Rainer: As you scale, do so with clarity. Avoid scaling just for external appeal. Always hire when there’s genuine need, not just for the sake of expansion. It helps in staying lean and focused.

Writing a exercise based TTRPG rulebook for a system where your real world fitness is tied to character progression
reddit
LLM Vibe Score0
Human Vibe Score1
BezboznyThis week

Writing a exercise based TTRPG rulebook for a system where your real world fitness is tied to character progression

My dad was a star athlete when he was young, and my mom was a huge sci-fi/fantasy nerd, so I got both ends of the stick as it were. Love gaming and nerd culture, but also love to exercise and self improvement. Sometimes exercise can feel boring though compared to daydreaming about fantastic fictional worlds, so for a long time I've been kicking around the idea of how to "Gamify" fitness. and recently I've been working on this passion project of a Table Top RPG (Like D&D) where the stats of your character are related to your own fitness, so if you want your character in game to improve, you have to improve in the real world. Below is a rough draft you can look through that details the settings and mechanics of the game I've come up with so far. I'd love to eventually get a full book published and sell it online. maybe even starting a whole brand of "Gamified fitness": REP-SET: GAINSZ In the war torn future of 24th century… There are no rest days… In the futuristic setting of "REP-SET: GAINSZ," the "War of Gains" casts a long shadow over the Sol System as the various factions vie for territory and resources. However, war has evolved. Unmanned drones and long-range strikes have faded into obsolescence. Battles, both planet-side and in the depths of space, are now fought by soldiers piloting REP-SETs: Reactive Exoskeletal Platform - Symbiotic Evolution Trainer Massive, humanoid combat mechs. Powered by mysterious “EV” energy, these mechanical marvels amplify, and are in turn amplified by, the fitness and mental acuity of their pilots. The amplification is exponential, leading pilots into a life of constant training in order for their combat prowess to be bolstered by every incremental gain in their level of fitness. With top pilots having lifting capacity measured in tons, and reaction times measured by their Mach number, REP-SET enhanced infantry now dominate the battlefield. The Factions: The Federated Isometocracy of Terra (FIT): Quote: "The strength of the body is the strength of the spirit. Together, we will lift humanity to its destined greatness. But ask not the federation to lift for you. Ask yourself: Do you even lift for the Federation?" Description: An idealistic but authoritarian faction founded on the principle of maximizing the potential of all individuals. FIT citizens believe in relentless striving for physical and mental perfection, leading to collective excellence. Their goal is the unification of humankind under a rule guided by this doctrine, which sometimes comes at the cost of individual liberties. Mech Concept: REP-SET mechs. Versatile humanoid designs focusing on strength, endurance, and adaptability. By connecting to the AI spirit within their REP-SETs core, each pilot enhances the performance of their machine through personal willpower and peak physical training. Some high-rank REP-SETS include features customized to the pilot's strengths, visually signifying their dedication and discipline. The Dominion of Organo-Mechanical Supremacy (DOMS): Quote: "Without pain, there is no gain. Become the machine. Embrace the burn.” Description: A fanatical collective ideologically obsessed with "Ascendency through suffering" by merging their bodies with technology that not only transcends biological limitations, but also acts to constantly induce pain in it's users. Driven by a sense of ideological superiority and a thirst for domination, DOMS seek to bring the painful blessings of their deity "The lord of the Burn" to the rest of the solar system. Their conquest could turn them into a significant threat to humanity. Mech Concept: Hybrid mechs, where the distinction between the pilot and the machine is blurred. The cockpit functions as a life-support system for the pilot, heavily modified with augmentations. Mechs themselves are often modular, allowing for adaptation and assimilation of enemy technology. Some DOMS mechs might display disturbing elements of twisted flesh alongside cold, mechanical parts. The Tren: Quote: "Grow... bigger... feast... protein..." Description: A ravenous conglomeration of biochemically engineered muscular monstrosities, united only by a shared insatiable hunger for "More". Existing mostly in deep space, they seek organic matter to consume and assimilate. They progress in power not due to any form of training or technology, but from a constant regimen of ravenous consumption and chemically induced muscle growth, all exponentially enhanced by EV energies. While some have been known to possess a certain level of intellect and civility, their relentless hunger makes them incredibly mentally volatile. When not consuming others, the strong consume the weak within their own faction. Mech Concept: Bio-Organic horrors. While they do have massive war machines, some are living vessels built around immense creatures. These machines resemble grotesque fleshy designs that prioritize rapid mutation and growth over sleek aesthetics. Often unsettling to behold. Synthetic Intelligence Theocracy (SIT): Quote: "Failure is an unacceptable data point.” Description: A society ruled by a vast and interconnected artificial intelligence network. The SIT governs with seemingly emotionless rationality, striving for efficiency and maximum productivity. This leads to a cold, but arguably prosperous society, unless you challenge the logic of the collective AI. Their goals? Difficult to predict, as it hinges on how the AI calculates what's "optimal" for the continuation or "evolution" of existence. Mech Concept: Sleek, almost featureless robotic creations with a focus on efficient movement and energy management. Often drone-like or modular, piloted through direct mind-machine linking rather than traditional cockpits. Their aesthetic suggests cold and impersonal perfection. The Way Isolate(TWI): Quote: "The body unblemished, the mind unwavering. That is the path to true strength. That and a healthy diet of Aster-Pea proteins." Description: Known by some as "The asteroid farmers", The Way Isolate is a proud and enigmatic faction that stands apart from the other powers in the Sol System. A fiercely independent tribe bound by oaths of honor, loyalty, and hard work. Wandering the asteroid belt in their vast arc ships, their unparalleled mastery in asteroidal-agricultural engineering, ensuring they have no need to colonize planets for nutritional needs, has allowed them to abstain from the pursuit of territorial expansion in “The War of Gains”, instead focusing on inward perfection, both spiritual and physical. They eschew all technological bodily enhancements deemed unnatural, believing that true power can only be cultivated through the relentless pursuit of personal strength achieved through sheer will and bodily perfection. The Way Isolate views biohacking, genetic manipulation, and even advanced cybernetics as corruptions of the human spirit, diluting the sacredness of individual willpower. Mech Concept: Way Isolate mechs are built with maneuverability and precision in mind rather than flashy augmentations. Their REP-SETs are streamlined, favoring lean designs that mirror the athleticism of their pilots. Excelling in low to zero G environments, their mechs lack bulky armor, relying on evasion and maneuverability rather than brute force endurance. Weaponry leans towards traditional kinetic based armaments, perhaps employing archaic but reliable weapon styles such as blades or axes as symbols of their purity of purpose. These mechs reflect the individual prowess of their pilots, where victory is determined by focus, technique, and the raw power of honed physical ability. Base Player Character Example: You are a young, idealistic FIT soldier, barely out of training and working as a junior REP-SET mechanic on the Europa Ring World. The Miazaki district, a landscape of towering mountains and gleaming cities, houses a sprawling mountainside factory – a veritable hive of Gen 5 REP-SET construction. Here, the lines between military and civilian blur within a self-sufficient society dependent on this relentless industry. Beneath the surface, you harbor a secret. In a forgotten workshop, the ghost of a REP-SET takes shape – a unique machine built around an abandoned, enigmatic AI core. Ever since you salvaged it as a child from the wreckage of your hometown, scarred by a brutal Tren attack, you've dedicated yourself to its restoration. A lingering injury from that fateful battle mocks your progress, a constant reminder of the fitness exams you cannot pass. Yet, you train relentlessly, dreaming of the day you'll stand as a true REP-SET pilot. A hidden truth lies at the heart of the REP-SETS: as a pilot's abilities grow, their mech develops unique, almost mystical powers – a manifestation of the bond between the human spirit and the REP-SET's AI. The ache in your old wound serves as a grim prophecy. This cold war cannot last. The drums of battle grow louder with each passing day. GAME MECHANICS: The TTRPG setting of “REP-SET: GAINSZ” is marked by a unique set of rules, by which the players real world capabilities and fitness will reflect and affect the capabilities, progression, and success of their REP-SET pilot character in-game. ABILITY SCORES: Pilots' capabilities will be defined by 6 “Ability scores”: Grace, Agility, Iron, Nourishment, Strength, and Zen. Each of the 6 ability scores will duel represent both a specific area of exercise/athleticism and a specific brand of healthy habits. The definitions of these ability scores are as follows: Grace (GRC): "You are an artist, and your body is your canvas; the way you move is your paint and brush." This ability score, the domain of dancers and martial artists, represents a person's ability to move with organic, flowing control and to bring beauty to the world. Skill challenges may be called upon when the player character needs to act with poise and control, whether socially or physically. Real-world skill checks may involve martial arts drills, dancing to music, or balance exercises. Bonuses may be granted if the player has recently done something artistically creative or kind, and penalties may apply if they have recently lost their temper. This ability score affects how much NPCs like your character in game. Agility (AGI): "Your true potential is locked away, and speed is the key to unlocking it." The domain of sprinters, this ability score represents not only a person's absolute speed and reaction time but also their capacity to finish work early and avoid procrastination. Skill challenges may be called upon when the player character needs to make a split-second choice, move fast, or deftly dodge something dangerous. Real-world skill checks may involve acts of speed such as sprinting or punching/kicking at a steadily increasing tempo. Bonuses may apply if the player has finished work early, and penalties may apply if they are procrastinating. This ability score affects moving speed and turn order in game. Iron (IRN): "Not money, nor genetics, nor the world's greatest trainers... it is your resolve, your will to better yourself, that will make you great." Required by all athletes regardless of focus, this ability score represents a player's willpower and their capacity to push through pain, distraction, or anything else to achieve their goals. Skill challenges may be called upon when the player character needs to push through fear, doubt, or mental manipulation. Real-world skill checks may involve feats of athletic perseverance, such as planking or dead hangs from a pull-up bar. Bonuses may apply when the player maintains or creates scheduled daily routines of exercise, self-improvement, and work completion, and penalties may apply when they falter in those routines. This ability score affects the max "Dynamic exercise bonus” that can be applied to skill checks in game (a base max of +3 when Iron = 10, with an additional +1 for every 2 points of iron. So if every 20 pushups gives you +1 on a “Strength” skill check, then doing 80 pushups will only give you +4 if you have at least 12 iron). Nourishment (NRS): "A properly nourished body will last longer than a famished one." This ability score, focused on by long-distance runners, represents a player's endurance and level of nutrition. Skill challenges may be called upon when making checks that involve the player character's stamina or health. Real-world skill checks may involve endurance exercises like long-distance running. Bonuses may apply if the player has eaten healthily or consumed enough water, and penalties may apply if they have eaten junk food. This ability score affects your HP (Health points), which determines how much damage you can take before you are incapacitated. Strength (STR): "When I get down on my hands, I'm not doing pushups, I'm bench-pressing the planet." The domain of powerlifters and strongmen, this ability score represents raw physical might and the ability to overcome obstacles. Skill challenges may be called upon when the player character needs to lift, push, or break something. Real-world skill checks might involve weightlifting exercises, feats of grip strength, or core stability tests. Bonuses may apply for consuming protein-rich foods or getting a good night's sleep, and penalties may apply after staying up late or indulging in excessive stimulants. This ability score affects your carrying capacity and base attack damage in game. Zen (ZEN): "Clarity of mind reflects clarity of purpose. Still the waters within to act decisively without." This ability score, prized by meditators and yogis, represents mental focus, clarity, and inner peace. Skill challenges may be called upon when the player character needs to resist distractions, see through illusions, or make difficult decisions under pressure. Real-world skill checks may involve meditation, breathing exercises, or mindfulness activities. Bonuses may apply after attending a yoga class, spending time in nature, or creating a calm and organized living space. Penalties may apply after experiencing significant stress, emotional turmoil, or having an unclean or unorganized living space. This ability score affects your amount of ZP in game (Zen Points: your pool of energy you pull from to use mystical abilities) Determining initial player ability scores: Initially, “Ability scores” are decided during character creation by giving the player a list of 6 fitness tests to gauge their level of fitness in each category. Running each test through a specific calculation will output an ability score. A score of 10 represents the average person, a score of 20 represents a peak athlete in their category. The tests are: Grace: Timed balancing on one leg with eyes closed (10 seconds is average, 60 is peak) Agility: Mile run time in minutes and second (10:00 minutes:seconds is average, 3:47 is peak) Iron: Timed dead-hang from a pull-up bar (30 seconds is average, 160 is peak) Nourishment: Miles run in an hour (4 is average, 12 is peak) Strength: Pushups in 2 minute (34 is average, 100 is peak) Zen: Leg stretch in degrees (80 is average, and 180 aka "The splits" is peak) Initial Score Calculation Formula: Ability Score = 10 + (Player Test Score - Average Score) / (Peak Score - Average\_Score) \* 10 Example: if the player does 58 pushups in 2 minutes, their strength would be: 10 plus (58 - 34) divided by (100-34) multiplied by 10 = 10 + (24)/(66)\* 10 = 10 + 3.6363... = 13.6363 rounded to nearest whole number = Strength (STR): 14 SKILLS AND SKILL CHALLENGES: The core mechanic of the game will be in how skill challenges are resolved. All “Skill challenges” will have a numerical challenge rating that must be met or beaten by the sum of a 10 sided dice roll and your score in the pertinent skill. Skill scores are determined by 2 factors: Ability Score Bonus: Every 2 points above 10 gives +1 bonus point. (EX. 12 = +1, 14 = +2, etc.) This also means that if you have less than 10 in an ability score, you will get negative points. Personal Best Bonus: Each skill has its own unique associated exercise that can be measured (Time, speed, distance, amount of reps, etc). A higher record means a higher bonus. EX: Authority skill checks are associated with a timed “Lateral raise hold”. Every 30 seconds of the hold added onto your personal best single attempt offers a +1 bonus. So if you can do a lateral hold for 90 seconds, that’s a +3 to your authority check! So if you have a 16 in Iron, and your Personal Best lateral raise hold is 90 seconds, that would give you an Authority score of +6 (T-Pose for dominance!) Dynamic Exercise Bonus: This is where the unique mechanics of the game kick in. At any time during a skill challenge (even after your roll) you can add an additional modifier to the skill check by completing the exercise during gameplay! Did you roll just below the threshold for success? Crank out another 20 pushups, squats, or curls to push yourself just over the edge into success! There are 18 skills total, each with its own associated ability score and unique exercise: Grace (GRC): \-Kinesthesia (Timed: Blind single leg stand time) \-Precision (Scored: Basket throws) \-Charm (Timed reps: Standing repeated forward dumbell chest press and thrust) \-Stealth (Timed distance: Leopard Crawl) Agility (AGI): \-acrobatics (timed reps: high kicks) \-Computers (Word per minute: Typing test) \-Speed (Time: 100 meter sprint) Iron (IRN): \-Authority (Timed: Lateral raise hold) \-Resist (Timed: Plank) \-Persist (Timed:Pull-up bar dead hang) Nourishment(NRS): \-Recovery (TBD) \-Stim crafting (TBD) \-Survival (TBD) Strength(STR): \-Mechanics (Timed reps: Alternating curls) \-Might (Timed reps: pushups) Zen(ZEN): \-Perceive (TBD) \-Empathy (TBD) \-Harmony (TBD) \-Lore (TBD) Healthy Habits Bonus: Being able to demonstrate that you have conducted healthy habits during gameplay can also add one time bonuses per skill challenge “Drank a glass of water +1 to Nourishment check”, “Cleaned your room, +3 on Zen check”. But watch out, if you’re caught in unhealthy Habits, the GM can throw in penalties, “Ate junk food, -1 to Nourishment check”, etc. Bonuses/penalties from in-game items, equipment, buffs, debuffs, etc., helping players to immerse into the mechanics of the world of REP-SET for the thrill of constantly finding ways to improve their player. Gradient success: Result of skill challenges can be pass or fail, but can also be on a sliding scale of success. Are you racing to the battlefield? Depending on your Speed check, you might arrive early and have a tactical advantage, just in time for an even fight, or maybe far too late and some of your favorite allied NPCs have paid the price… So you’re often encouraged to stack on those dynamic exercise bonuses when you can to get the most fortuitous outcomes available to you. Gameplay sample: GM: Your REP-SET is a phantom, a streak of light against the vast hull of the warship. Enemy fighters buzz angrily, but you weaves and dodges with uncanny precision. The energy wave might be losing effectiveness, but your agility and connection to the machine have never been stronger. Then, it happens. A gap in the defenses. A vulnerable seam in the warship's armor. Your coms agents keen eye spots it instantly. "Lower power junction, starboard side! You have an opening!" This is your chance to strike the decisive blow. But how? It'll take a perfect combination of skill and strategy, drawing upon your various strengths. Here are your options: Option 1: Brute Strength: Channel all remaining power into a single, overwhelming blast from the core. High-risk, high-reward. It could overload the REP-SET if you fail, but it might also cripple the warship. (Strength-focused, Might sub-skill) Option 2: Calculated Strike: With surgical precision, target the power junction with a pinpoint burst of destabilizing energy. Less flashy and ultimately less damaging, but potentially more effective in temporarily disabling the ship. (Agility-focused, Precision sub-skill) Option 3: Harmonic Disruption: Attempt to harmonize with your REP-SET's AI spirit for help in connecting to the digital systems of the Warship. Can you generate an internal energy resonance within the warship, causing it to malfunction from within? (Zen-focused, Harmony sub-skill) Player: I'll take option 1, brute strength! GM: Ok, This will be a "Might" check. The CR is going to be very high on this one. I'm setting it at a 20. What's your Might bonus? Player: Dang, a 20?? That's literally impossible. My Might is 15 and I've got a PB of 65 pushups in 2 minutes, that sets me at a +5. Even if I roll a 10 and do 60 pushups for the DE I'll only get 18 max. GM: Hey I told you it was high risk. You want to choose another option? Player: No, no. This is what my character would do. I'm a real hot-blooded meathead for sure. GM: Ok then, roll a D10 and add your bonus. Player: \Rolls\ a 9! not bad, actually that's a really good roll. So +5, that's a 14. GM: Alright, would you like to add a dynamic exercise bonus? Player: Duh, it's not like I can do 120 pushups I'd need to beat the CR, but I can at least do better than 14. Alright, here goes. \the player gets down to do pushups and the 2 minute time begins. After some time...\ Player: 65....... 66! GM: Times up. Player: Ow... my arms... GM: so with 66, that's an extra +3, and its a new PB, so that's a +1. That sets your roll to 18. Player: Ow... Frack... still not 20... for a second there i really believed I could do 120 pushups... well I did my best... Ow... 20 CR is just too impossible you jerk... GM: Hmm... Tell me, what did you eat for lunch today? Player: Me? I made some vegetable and pork soup, and a protein shake. I recorded it all in my diet app. GM: And how did you sleep last night? Player: Like a baby, went to sleep early, woke up at 6. GM: in that case, you can add a +1 "Protein bonus" and +1 "Healthy rest" bonus to any strength related check for the day if you'd like, including this one. Player: Really?? Heck yes! add it to the roll! GM: With those extra bonuses, your roll reaches 20. How do you want to do this? Player: I roar "For Terra!" and pour every last ounce of my strength into the REP-SET. GM: "For Terra!" you roar, your cry echoing through coms systems of the REP-SET. The core flares blindingly bright. The surge of power dwarfs anything the REP-SET has unleashed before. With a titanic shriek that cracks the very fabric of space, the REP-SET slams into the vulnerable power junction. Raw energy explodes outwards, tendrils of light arcing across the warship's massive hull. The impact is staggering. The leviathan-like warship buckles, its sleek form rippling with shockwaves. Sparks shower like rain, secondary explosions erupt as critical systems overload. Then…silence. The warship goes dark. Power flickers within the REP-SET itself, then steadies. Alarms fade, replaced by the eerie quiet of damaged but functional systems. "We…did it?" The coms agents voice is incredulous, tinged with relief. She's awaiting your reply. Player: "I guess so." I say, and I smile and laugh. And then I slump back... and fall unconscious. \to the other players\ I'm not doing any more skill checks for a while guys, come pick me up please. \teammates cheer\ &#x200B;

Business Idea for new app connecting lonely people (e.g. new arrivals to big city), with local businesses organizing events
reddit
LLM Vibe Score0
Human Vibe Score1
TheL0nelyPoetThis week

Business Idea for new app connecting lonely people (e.g. new arrivals to big city), with local businesses organizing events

I came up with a start-up idea for a tool (website, app or both) where lonely people (e.g. recent arrivals to a new city) can match-up with one another, together with local businesses organizing events. I came up with the idea based on my own experiences of moving to a new place where my local social circle was virtually non-existent. Some people do well in such an environment, but I myself and some people I know/have interacted with seem to really struggle to make friends. The main idea would revolve around garnering the help of local businesses that regularly organize events (or would want to start doing so), together with a tool set up like a matching app (not unlike tinder or bumble). The app would contain the following features: People will be able to create a profile (with photos, interests, etc.) from all over the world, and set a specific geolocation of interest. Companies would be able to create pages with agenda’s and upcoming events. People would be able to list upcoming events they are interested in. Maybe together with some kind of AI-tool that will recommend upcoming events based on past liked events and interests. One could then seek out and reach out to other people planning to go to the same event, and perhaps arrange to go together so they know they won’t end up spending their time at the event alone. The business model would either revolve around subscription costs (e.g. for the companies that use it), commission on tickets purchased at the app for events or perhaps advertisement. I know there would be some competitors out there, however it appears most haven’t gained proper traction. I have also noticed most of the competitors have similar features, but haven’t made this business model their main strategy. Bumble for example, has a BFF-mode but advertises mainly about being a dating app. Businesses use their own websites or facebook/Instagram pages, but rely on people actively following them. Etc. What do you guys think? Honest feedback would really be appreciated, as this is my first start-up idea.

How to get that big idea for your next business? Use trends!
reddit
LLM Vibe Score0
Human Vibe Score1
IRemember123This week

How to get that big idea for your next business? Use trends!

Hello entrepreneurs and aspiring business owners, I am Mikael and I want to share a post about how to spot business ideas. If you're wondering who the owl is, it's Agent O, my sidekick (please bear with him... or me, if you can). Let's get on to it. So, there are basically two ways of getting ideas for your new business: Find a service, product or experience that's already working. Identify and ride a trend. 🦉 : Third, have a rich relative pass you their business and sip margaritas by the sea while scrolling Reddit for the rest of your life! 🕵️ : Refrain yourself, I just got started ffs, I don't want to get banned! So, what are trends? Trends are patterns of adoption of a product, service or experience by people who want to satisfy a common need. Cool, huh? How trends start Trends emerge and evolve as temporary or permanent solutions to human needs. All products, services and experiences are the expression of human needs manifested through a perceived lack, which we humans interpret as problems. Let me make this more clear. Humans have needs: from basic (food, shelter, safety) to advanced (community, knowledge) to evolved (self actualization, spirituality) and everything in between. Don’t see this as a hierarchy, as it’s usually depicted with Maslow’s pyramid. See it as cycles with different degrees of impact on humans that vary in time and intensity. 🦉 : WHAT!?? 🕵️ : Hear me out… How Trends Affect Society Human needs are physical, emotional, intellectual and spiritual. Every day we feel the impact of those needs with different degrees of required fulfillment. You can’t go on without air for more than a few minutes. You can’t live without food and water for more than a few days. So, when it comes to the needs of the body, these have a shorter timeframe in which they need to be addressed. 🦉 : Ahh, I see what you did there… \\🕵️ \\: Thanks! But you can also live with an unfulfilled need for love or friends for a long time. You can live with a decaying health as well. And you also can live your entire life without finding out if there is a God or not. Humans perceive needs as something they lack within, which in turn is expressed as a problem on the outside. I lack food or water, this will create a problem for my survival. So I need to find food and water in my environment. This lack creates a behavior seeking a product, service or experience to fulfill that need. Makes sense? 🦉 : I just went out and got me a “Mice à la Forest” dinner! 🕵️: Bon appétit! See, Agent O fulfilled a bodily need. That’s what animals do, as they’re driven by instinct and are governed by natural laws (survive, reproduce, sleep, repeat). Humans are driven by more complex needs, as our intellect and emotions allow us to override those basic primary instincts. Why Trends Are Important What an entrepreneur does is to shift the perspective: instead of seeing a lack, he/she sees an opportunity by asking the question: how can I fulfill this need? Or, even better put: how can I help people by solving their problem? That’s the first step to solving a problem: asking a question. That is why the best products are actually problems solved by entrepreneurs who work to solve their own need for a product, service or experience. They then provide it to other people for a cost. Easy, right? That’s what entrepreneurship is: solving a problem. The bigger the problem, the bigger the impact. The bigger the impact, the higher the revenue. It’s easier to understand trends now, isn’t it? You can see that trends are nothing more than the initial adoption of a product, service or experience by a group of people who are looking for a solution to their common need. 🦉 : Did you get that from a book? 🕵️ : You snore when you sleep… ¯\\(\ツ)/\¯ 🦉 : $@#&\*! Hooman! Needs are the foundation on which the modern world is built. Once you understand needs, you fundamentally change your perception of problems into opportunities. This mental shift is the entrepreneurial mindset: where others see problems, you see solutions. Where Do Trends Start So, to recap: human needs are translated into problems. Founders understand the root of the problem (the need) and create products, services, experiences as solutions to those needs. They offer the solution to the public through startups and companies, which belong to a specific niche in a particular industry. 🦉 : Aaah, so that’s why it’s called venture capital? 🕵️ : Yeah, because you’re venturing into a new endeavor to let people know about your solution to their (and ideally your) problem. 🦉 : So if you use ads to market your venture, it’s an adventure? 🕵️ : I see what you did there… If the need behind the adoption is strong and real enough, that trend will translate into a niche within an industry. If the adoption isn’t driven by strong fundamental needs, it will turn into a fad and disappear from the perception of the public, no matter how much marketing money is thrown at it. This happens because the solution (product/service/experience) to the need didn’t create the physical, intellectual or emotional response required to create a recurring behavior around it. Remember this: Problem (why) -> Behavior (how) -> Solution (what) Understand this: there are multiple types of trends. There are product or service trends. There are industry driven trends. There are tendency driven trends, like the emergence of a new paradigm that improves a lot of industries (yes, I’m looking at you, AI). Where Do Trends Come From So now you can see that trends are patterns of adoption related to a specific human need that is addressed through one or multiple products or services. This is a bottom up direction coming from evolution. Multiple trends in different industries also emerge from a theme, which is a bigger vision of a human effort to address a high level problem. This is a top down direction, coming from implementation (by governments, different organizations or other interested parties with the power to influence changes at mass level). Conclusion Now you have a better understanding of trends by looking at them through the lens of human needs. Also, you might also understand time better because you realize that human needs have different degrees of impact in time and intensity. So you now see that trends don’t only relate to individuals, but also to groups of people, from the smallest community to countries and even global needs. That is the reason you’ll sometimes hear some say that time is a flat circle: because clothes change, but humans are quite the same. Needs don’t change a lot in time, just the way we address and solve them. Here’s an interesting game for you: take a look at some behaviors in your life. Which of them are driven by a bodily need, which by an intellectual or emotional one? Which ones are completely automated and you had no idea you were doing? How are these behaviors controlling parts of your life that you were unaware of until now? If you made it this far, thank you for taking the time to read this. I hope you enjoyed it, found it useful and entertaining. Ofc, I value your opinion and welcome it in the comments. Thank you!

How to get that big idea for your next business? Use trends!
reddit
LLM Vibe Score0
Human Vibe Score1
IRemember123This week

How to get that big idea for your next business? Use trends!

Hello entrepreneurs and aspiring business owners, I am Mikael and I want to share a post about how to spot business ideas. If you're wondering who the owl is, it's Agent O, my sidekick (please bear with him... or me, if you can). Let's get on to it. So, there are basically two ways of getting ideas for your new business: Find a service, product or experience that's already working. Identify and ride a trend. 🦉 : Third, have a rich relative pass you their business and sip margaritas by the sea while scrolling Reddit for the rest of your life! 🕵️ : Refrain yourself, I just got started ffs, I don't want to get banned! So, what are trends? Trends are patterns of adoption of a product, service or experience by people who want to satisfy a common need. Cool, huh? How trends start Trends emerge and evolve as temporary or permanent solutions to human needs. All products, services and experiences are the expression of human needs manifested through a perceived lack, which we humans interpret as problems. Let me make this more clear. Humans have needs: from basic (food, shelter, safety) to advanced (community, knowledge) to evolved (self actualization, spirituality) and everything in between. Don’t see this as a hierarchy, as it’s usually depicted with Maslow’s pyramid. See it as cycles with different degrees of impact on humans that vary in time and intensity. 🦉 : WHAT!?? 🕵️ : Hear me out… How Trends Affect Society Human needs are physical, emotional, intellectual and spiritual. Every day we feel the impact of those needs with different degrees of required fulfillment. You can’t go on without air for more than a few minutes. You can’t live without food and water for more than a few days. So, when it comes to the needs of the body, these have a shorter timeframe in which they need to be addressed. 🦉 : Ahh, I see what you did there… \\🕵️ \\: Thanks! But you can also live with an unfulfilled need for love or friends for a long time. You can live with a decaying health as well. And you also can live your entire life without finding out if there is a God or not. Humans perceive needs as something they lack within, which in turn is expressed as a problem on the outside. I lack food or water, this will create a problem for my survival. So I need to find food and water in my environment. This lack creates a behavior seeking a product, service or experience to fulfill that need. Makes sense? 🦉 : I just went out and got me a “Mice à la Forest” dinner! 🕵️: Bon appétit! See, Agent O fulfilled a bodily need. That’s what animals do, as they’re driven by instinct and are governed by natural laws (survive, reproduce, sleep, repeat). Humans are driven by more complex needs, as our intellect and emotions allow us to override those basic primary instincts. Why Trends Are Important What an entrepreneur does is to shift the perspective: instead of seeing a lack, he/she sees an opportunity by asking the question: how can I fulfill this need? Or, even better put: how can I help people by solving their problem? That’s the first step to solving a problem: asking a question. That is why the best products are actually problems solved by entrepreneurs who work to solve their own need for a product, service or experience. They then provide it to other people for a cost. Easy, right? That’s what entrepreneurship is: solving a problem. The bigger the problem, the bigger the impact. The bigger the impact, the higher the revenue. It’s easier to understand trends now, isn’t it? You can see that trends are nothing more than the initial adoption of a product, service or experience by a group of people who are looking for a solution to their common need. 🦉 : Did you get that from a book? 🕵️ : You snore when you sleep… ¯\\(\ツ)/\¯ 🦉 : $@#&\*! Hooman! Needs are the foundation on which the modern world is built. Once you understand needs, you fundamentally change your perception of problems into opportunities. This mental shift is the entrepreneurial mindset: where others see problems, you see solutions. Where Do Trends Start So, to recap: human needs are translated into problems. Founders understand the root of the problem (the need) and create products, services, experiences as solutions to those needs. They offer the solution to the public through startups and companies, which belong to a specific niche in a particular industry. 🦉 : Aaah, so that’s why it’s called venture capital? 🕵️ : Yeah, because you’re venturing into a new endeavor to let people know about your solution to their (and ideally your) problem. 🦉 : So if you use ads to market your venture, it’s an adventure? 🕵️ : I see what you did there… If the need behind the adoption is strong and real enough, that trend will translate into a niche within an industry. If the adoption isn’t driven by strong fundamental needs, it will turn into a fad and disappear from the perception of the public, no matter how much marketing money is thrown at it. This happens because the solution (product/service/experience) to the need didn’t create the physical, intellectual or emotional response required to create a recurring behavior around it. Remember this: Problem (why) -> Behavior (how) -> Solution (what) Understand this: there are multiple types of trends. There are product or service trends. There are industry driven trends. There are tendency driven trends, like the emergence of a new paradigm that improves a lot of industries (yes, I’m looking at you, AI). Where Do Trends Come From So now you can see that trends are patterns of adoption related to a specific human need that is addressed through one or multiple products or services. This is a bottom up direction coming from evolution. Multiple trends in different industries also emerge from a theme, which is a bigger vision of a human effort to address a high level problem. This is a top down direction, coming from implementation (by governments, different organizations or other interested parties with the power to influence changes at mass level). Conclusion Now you have a better understanding of trends by looking at them through the lens of human needs. Also, you might also understand time better because you realize that human needs have different degrees of impact in time and intensity. So you now see that trends don’t only relate to individuals, but also to groups of people, from the smallest community to countries and even global needs. That is the reason you’ll sometimes hear some say that time is a flat circle: because clothes change, but humans are quite the same. Needs don’t change a lot in time, just the way we address and solve them. Here’s an interesting game for you: take a look at some behaviors in your life. Which of them are driven by a bodily need, which by an intellectual or emotional one? Which ones are completely automated and you had no idea you were doing? How are these behaviors controlling parts of your life that you were unaware of until now? If you made it this far, thank you for taking the time to read this. I hope you enjoyed it, found it useful and entertaining. Ofc, I value your opinion and welcome it in the comments. Thank you!

Marketing Automation Trends To Look For in 2018
reddit
LLM Vibe Score0
Human Vibe Score1
SoffrontHQThis week

Marketing Automation Trends To Look For in 2018

As the new year is upon us, marketing automation software and AI continue to soar in the CRM Industry. In 2018, keep an eye out for these constraints as they will revolutionize marketing, keeping customer engagement in the forefront. Customer experience: In 2018, customer experience will be instrumental in driving the marketing automation software market. The recent shift in the trends of markets has forced the companies to develop new ways of engaging the customer and giving them an enriched experience. As new strategies are deployed to the target customer, shorter content, full streaming videos or infographics will be preferred. Content marketing automation: After the content is finished, it is only left to communicate it to the right channels, at the right time. But in order to have an edge in the regularity of publications and efficiency, companies are opting for automation tools to communicate and promote content through various channels. The results are obvious, not only you gain efficiency but this method helps in reaching and retaining those group of individuals whose appointments happen on a daily basis thus putting your company in the expert bracket. Chatbots: Chatbots are perfect examples of online CRM applications impacting the business in 2018. These intelligent programs have the ability to comprehend, analyze and then formulate an adequate reply to customer queries in real time. Ever since Facebook messenger opened its API, the ease and simplicity of installing these on CMS have inspired a lot of companies to implement it. In the future, their challenge will be to innovate customer engagement providing a better user experience rather than mere customer service using customer data. Further expectations will shape up in the form of artificial empathy where they will be able to connect to the customer emotionally and listen to their wanting. This will automate customer expectations and enable humans to focus on their “real” customer holding strong added value. The future looks bright with thought-leaders pioneering digital transformation and paving the way to tremendous opportunities. If they can manage to anticipate the consequence of the current mutations, companies will evolve and marketing resources will experience growth like never before.

RD-Agent
github
LLM Vibe Score0.548
Human Vibe Score0.27921589729164453
microsoftMar 28, 2025

RD-Agent

🖥️ Live Demo | 🎥 Demo Video ▶️YouTube | 📖 Documentation | 📃 Papers Data Science Agent Preview Check out our demo video showcasing the current progress of our Data Science Agent under development: https://github.com/user-attachments/assets/3eccbecb-34a4-4c81-bce4-d3f8862f7305 📰 News | 🗞️ News | 📝 Description | | -- | ------ | | Support LiteLLM Backend | We now fully support LiteLLM as a backend for integration with multiple LLM providers. | | More General Data Science Agent | 🚀Coming soon! | | Kaggle Scenario release | We release Kaggle Agent, try the new features! | | Official WeChat group release | We created a WeChat group, welcome to join! (🗪QR Code) | | Official Discord release | We launch our first chatting channel in Discord (🗪) | | First release | RDAgent is released on GitHub | 🌟 Introduction RDAgent aims to automate the most critical and valuable aspects of the industrial R&D process, and we begin with focusing on the data-driven scenarios to streamline the development of models and data. Methodologically, we have identified a framework with two key components: 'R' for proposing new ideas and 'D' for implementing them. We believe that the automatic evolution of R&D will lead to solutions of significant industrial value. R&D is a very general scenario. The advent of RDAgent can be your 💰 Automatic Quant Factory (🎥Demo Video|▶️YouTube) 🤖 Data Mining Agent: Iteratively proposing data & models (🎥Demo Video 1|▶️YouTube) (🎥Demo Video 2|▶️YouTube) and implementing them by gaining knowledge from data. 🦾 Research Copilot: Auto read research papers (🎥Demo Video|▶️YouTube) / financial reports (🎥Demo Video|▶️YouTube) and implement model structures or building datasets. 🤖 Kaggle Agent: Auto Model Tuning and Feature Engineering([🎥Demo Video Coming Soon...]()) and implementing them to achieve more in competitions. ... You can click the links above to view the demo. We're continuously adding more methods and scenarios to the project to enhance your R&D processes and boost productivity. Additionally, you can take a closer look at the examples in our 🖥️ Live Demo. ⚡ Quick start You can try above demos by running the following command: 🐳 Docker installation. Users must ensure Docker is installed before attempting most scenarios. Please refer to the official 🐳Docker page for installation instructions. Ensure the current user can run Docker commands without using sudo. You can verify this by executing docker run hello-world. 🐍 Create a Conda Environment Create a new conda environment with Python (3.10 and 3.11 are well-tested in our CI): Activate the environment: 🛠️ Install the RDAgent You can directly install the RDAgent package from PyPI: 💊 Health check rdagent provides a health check that currently checks two things. whether the docker installation was successful. whether the default port used by the rdagent ui is occupied. ⚙️ Configuration The demos requires following ability: ChatCompletion json_mode embedding query For example: If you are using the OpenAI API, you have to configure your GPT model in the .env file like this. However, not every API services support these features by default. For example: AZURE OpenAI, you have to configure your GPT model in the .env file like this. We now support LiteLLM as a backend for integration with multiple LLM providers. If you use LiteLLM Backend to use models, you can configure as follows: For more configuration information, please refer to the documentation. 🚀 Run the Application The 🖥️ Live Demo is implemented by the following commands(each item represents one demo, you can select the one you prefer): Run the Automated Quantitative Trading & Iterative Factors Evolution: Qlib self-loop factor proposal and implementation application Run the Automated Quantitative Trading & Iterative Model Evolution: Qlib self-loop model proposal and implementation application Run the Automated Medical Prediction Model Evolution: Medical self-loop model proposal and implementation application (1) Apply for an account at PhysioNet. (2) Request access to FIDDLE preprocessed data: FIDDLE Dataset. (3) Place your username and password in .env. Run the Automated Quantitative Trading & Factors Extraction from Financial Reports: Run the Qlib factor extraction and implementation application based on financial reports Run the Automated Model Research & Development Copilot: model extraction and implementation application Run the Automated Kaggle Model Tuning & Feature Engineering: self-loop model proposal and feature engineering implementation application Using sf-crime (San Francisco Crime Classification) as an example. Register and login on the Kaggle website. Configuring the Kaggle API. (1) Click on the avatar (usually in the top right corner of the page) -> Settings -> Create New Token, A file called kaggle.json will be downloaded. (2) Move kaggle.json to ~/.config/kaggle/ (3) Modify the permissions of the kaggle.json file. Reference command: chmod 600 ~/.config/kaggle/kaggle.json Join the competition: Click Join the competition -> I Understand and Accept at the bottom of the competition details page. Description of the above example: Kaggle competition data, contains two parts: competition description file (json file) and competition dataset (zip file). We prepare the competition description file for you, the competition dataset will be downloaded automatically when you run the program, as in the example. If you want to download the competition description file automatically, you need to install chromedriver, The instructions for installing chromedriver can be found in the documentation. The Competition List Available can be found here. 🖥️ Monitor the Application Results You can run the following command for our demo program to see the run logs. Note: Although port 19899 is not commonly used, but before you run this demo, you need to check if port 19899 is occupied. If it is, please change it to another port that is not occupied. You can check if a port is occupied by running the following command. 🏭 Scenarios We have applied RD-Agent to multiple valuable data-driven industrial scenarios. 🎯 Goal: Agent for Data-driven R&D In this project, we are aiming to build an Agent to automate Data-Driven R\&D that can 📄 Read real-world material (reports, papers, etc.) and extract key formulas, descriptions of interested features and models, which are the key components of data-driven R&D . 🛠️ Implement the extracted formulas (e.g., features, factors, and models) in runnable codes. Due to the limited ability of LLM in implementing at once, build an evolving process for the agent to improve performance by learning from feedback and knowledge. 💡 Propose new ideas based on current knowledge and observations. 📈 Scenarios/Demos In the two key areas of data-driven scenarios, model implementation and data building, our system aims to serve two main roles: 🦾Copilot and 🤖Agent. The 🦾Copilot follows human instructions to automate repetitive tasks. The 🤖Agent, being more autonomous, actively proposes ideas for better results in the future. The supported scenarios are listed below: | Scenario/Target | Model Implementation | Data Building | | -- | -- | -- | | 💹 Finance | 🤖 Iteratively Proposing Ideas & Evolving▶️YouTube | 🤖 Iteratively Proposing Ideas & Evolving ▶️YouTube 🦾 Auto reports reading & implementation▶️YouTube | | 🩺 Medical | 🤖 Iteratively Proposing Ideas & Evolving▶️YouTube | - | | 🏭 General | 🦾 Auto paper reading & implementation▶️YouTube 🤖 Auto Kaggle Model Tuning | 🤖Auto Kaggle feature Engineering | RoadMap: Currently, we are working hard to add new features to the Kaggle scenario. Different scenarios vary in entrance and configuration. Please check the detailed setup tutorial in the scenarios documents. Here is a gallery of successful explorations (5 traces showed in 🖥️ Live Demo). You can download and view the execution trace using this command from the documentation. Please refer to 📖readthedocs_scen for more details of the scenarios. ⚙️ Framework Automating the R&D process in data science is a highly valuable yet underexplored area in industry. We propose a framework to push the boundaries of this important research field. The research questions within this framework can be divided into three main categories: | Research Area | Paper/Work List | |--------------------|-----------------| | Benchmark the R&D abilities | Benchmark | | Idea proposal: Explore new ideas or refine existing ones | Research | | Ability to realize ideas: Implement and execute ideas | Development | We believe that the key to delivering high-quality solutions lies in the ability to evolve R&D capabilities. Agents should learn like human experts, continuously improving their R&D skills. More documents can be found in the 📖 readthedocs. 📃 Paper/Work list 📊 Benchmark Towards Data-Centric Automatic R&D !image 🔍 Research In a data mining expert's daily research and development process, they propose a hypothesis (e.g., a model structure like RNN can capture patterns in time-series data), design experiments (e.g., finance data contains time-series and we can verify the hypothesis in this scenario), implement the experiment as code (e.g., Pytorch model structure), and then execute the code to get feedback (e.g., metrics, loss curve, etc.). The experts learn from the feedback and improve in the next iteration. Based on the principles above, we have established a basic method framework that continuously proposes hypotheses, verifies them, and gets feedback from the real-world practice. This is the first scientific research automation framework that supports linking with real-world verification. For more detail, please refer to our 🖥️ Live Demo page. 🛠️ Development Collaborative Evolving Strategy for Automatic Data-Centric Development !image 🤝 Contributing We welcome contributions and suggestions to improve RD-Agent. Please refer to the Contributing Guide for more details on how to contribute. Before submitting a pull request, ensure that your code passes the automatic CI checks. 📝 Guidelines This project welcomes contributions and suggestions. Contributing to this project is straightforward and rewarding. Whether it's solving an issue, addressing a bug, enhancing documentation, or even correcting a typo, every contribution is valuable and helps improve RDAgent. To get started, you can explore the issues list, or search for TODO: comments in the codebase by running the command grep -r "TODO:". Before we released RD-Agent as an open-source project on GitHub, it was an internal project within our group. Unfortunately, the internal commit history was not preserved when we removed some confidential code. As a result, some contributions from our group members, including Haotian Chen, Wenjun Feng, Haoxue Wang, Zeqi Ye, Xinjie Shen, and Jinhui Li, were not included in the public commits. ⚖️ Legal disclaimer The RD-agent is provided “as is”, without warranty of any kind, express or implied, including but not limited to the warranties of merchantability, fitness for a particular purpose and noninfringement. The RD-agent is aimed to facilitate research and development process in the financial industry and not ready-to-use for any financial investment or advice. Users shall independently assess and test the risks of the RD-agent in a specific use scenario, ensure the responsible use of AI technology, including but not limited to developing and integrating risk mitigation measures, and comply with all applicable laws and regulations in all applicable jurisdictions. The RD-agent does not provide financial opinions or reflect the opinions of Microsoft, nor is it designed to replace the role of qualified financial professionals in formulating, assessing, and approving finance products. The inputs and outputs of the RD-agent belong to the users and users shall assume all liability under any theory of liability, whether in contract, torts, regulatory, negligence, products liability, or otherwise, associated with use of the RD-agent and any inputs and outputs thereof.

machine-learning-blackjack-solution
github
LLM Vibe Score0.42
Human Vibe Score0.022610872675250356
GregSommervilleMar 27, 2025

machine-learning-blackjack-solution

machine-learning-blackjack-solution Introduction A genetic algorithm is a type of artificial intelligence programming that uses ideas from evolution to solve complex problems. It works by creating a population of (initially random) candidate solutions, then repeatedly selecting pairs of candidates and combining their solutions using a process similar to genetic crossover. Sometimes candidate solutions even go through mutation, just to introduce new possibilities into the population. After a large number of generations, the best solution found up to that point is often the optimal, best solution possible. Genetic algorithms are particularly well-suited for combinatorial problems, where there are huge numbers of potential solutions to a problem. The evolutionary process they go through is, in essence, a search through a huge solution space. A solution space so large that you simply could never use a brute force approach. This project is a demonstration of using a genetic algorithm to find an optimal strategy for playing the casino game Blackjack. Please see this article for a story about how this program was used, and what the results were. The article describes some of the available settings, and shows how different values for those settings affect the final result. The source code is for a Windows application written in Cthat allows you to play with different settings like population size, selection style and mutation rate. Each generation's best solution is displayed, so you can watch the program literally evolve a solution. !blackjack strategy tester screenshot The property grid located at the upper left of the screen is where you adjust settings. There's an informational area below that, and the right side of the screen is the display area for the three tables that represent a strategy for playing Blackjack. The tall table on the left is for hard hands, the table in the upper right is for soft hands, and the table in the lower right is for pairs. We'll talk more about how to interpret this strategy in a bit. The columns along the tops of the three tables are for the dealer upcard. When you play Blackjack the dealer has one of his two cards initially turned face up, and the rank of that card has a big impact on recommended strategy. Notice that the upcard ranks don't include Jack, Queen or King. That's because those cards all count 10, so we group them and the Ten together and simplify the tables. To use the tables, first, determine if you have a pair, soft hand, or hard hand. Then look in the appropriate table, with the correct dealer upcard column. The cell in the table will be "H" when the correct strategy is to hit, "S" when the correct strategy is to stand, "D" for double-down, and (in the pairs table only) "P" for split. A Word About This "Optimal" Strategy Before we go any further, it needs to be stated that this problem of finding an optimal Blackjack strategy has already been solved. Back in the 1960s, a mathematician named Edward O. Thorp authored a book called Beat the Dealer, which included charts showing the optimal "Basic" strategy. That strategy looks like this: !optimal blackjack strategy So we're solving a problem that has already been solved, but that's actually good. That means we can compare our results to the known best solution. For example, if our result strategy tells us to do anything but stand when holding a pair of Tens, Jacks, Queens or Kings, we know there's a problem. There's one other thing to get out of the way before we go any further, and that's the idea of nondeterministic code. That means that if we run the same code twice in a row, we're likely to get two different results. That's something that happens with genetic algorithms due to their inherent randomness. There's no guarantee you'll find the absolute optimal solution, but it is assured that you will find an optimal or near-optimal solution. It's something that isn't typical when writing code, so it takes some adjustment for most programmers. Genetic Algorithms Now let's talk about the details of a genetic algorithm. Fitness Scores First of all, we need a way to evaluate candidates so we can compare them to each other. That means a numeric fitness score, which in this case is quite simple: you simulate playing a certain number of hands using the strategy, and then count the number of chips you have at the end. The big question is, how many hands should we test with? The challenge of trying to test a strategy is that due to the innate randomness of Blackjack, you could use the same strategy ten times and get ten completely different results. Obviously, the more hands you play, the more the randomness gets smoothed out, and the quality of the underlying strategy starts to emerge. If you doubt this, just think about flipping a coin. If you only flip it five times, there's certainly a possibility that it'll come up heads all five times (in fact, that happens just over 3% of the time). However, if you flip it 500 times, there's no way it's going to end up all heads - the odds of it happening are 0.5500, which works out to be roughly once every 3 x 10150 times you try it. After some testing and analysis, it was determined that a minimum of 100,000 hands per test is needed for a reasonable level of accuracy. There's still variance even at that number, but in order to cut the variance in half, you'd need to bump the number of hands to 500,000. One reason this accuracy is important is that in the later generations, the differences between candidates are very small. Evolution has caused the main parts of the strategy to converge on a particular approach, and towards the end all it's doing is refining the minor details. In those cases it's important to accurately determine the difference between two similar candidates. Representation Representation is simply the idea that we need to use a data structure for a candidate solution that can be combined via crossover, and possibly mutated. In this case, that's also quite simple because the way that human beings represent a Blackjack strategy is to use three tables, as we've seen. Representing those in code with three two-dimensional arrays is the obvious approach. Each cell in those three tables will have "Hit", "Stand", "Double-Down", or (only for pairs) "Split". By the way, since there are 160 cells in the hard hands table, and 80 cells in the soft hands table, and 100 cells in the pairs table, we can calculate exactly how many possible distinct strategies there are for Blackjack: 4100 x 380 x 3160 = 5 x 10174 possible Blackjack strategies That's a big number, which is obviously impossible to search using brute force. Genetic algorithms (GAs) are extremely helpful when trying to find an optimal solution from a very large set of possible solutions like this. Blackjack Rules and Strategies The rules of Blackjack are fairly simple. The dealer and the player both are dealt two cards. The player sees both of their cards (they are usually dealt face up), and one of the dealer's cards is dealt face up. Each card has a value - for cards between 2 and 10, the value is the same as the card's rank (so an Eight of Spades counts as 8, for example). All face cards count as 10, and an Ace can either be 1 or 11 (it counts as 11 only when that does not result in a hand that exceeds 21). The suit of a card does not matter. After the cards are dealt, if the player has Blackjack (a total of 21) and the dealer does not, the player is immediately paid 1.5 times their original bet, and a new hand is dealt. If the player has 21 and the dealer does also, then it's a tie and the player gets their original bet back, and a new hand is dealt. If the player wasn't dealt a Blackjack, then play continues with the player deciding whether to Stand (not get any more cards), Hit (receive an additional card), Double-down (place an additional bet, and receive one and only one more card), or, in the case of holding a pair, splitting the hand, which means placing an additional bet and receiving two new cards, so the end result is that the player is now playing two (or, in the case of multiple splits, more than two) hands simultaneously. If the player hits or double-downs and has a resulting hand that exceeds 21, then they lose and play continues with the next hand. If not, then the dealer draws until their hand totals at least 17. If the dealer exceeds 21 at this point, the player receives a payment equal to twice their original bet. If the dealer doesn't exceed 21, then the hands are compared and the player with the highest total that doesn't exceed 21 wins. Because of these rules, certain effective strategies emerge. One common strategy is that if you hold a hard hand with a value of 20, 19 or 18, you should Stand, since you avoid busting by going over 21, and you have a nice hand total that might win in a showdown with the dealer. Another common strategy is to split a pair of Aces, since Aces are so powerful (due to the fact that count as 11 or 1, you can often Hit a hand with a soft Ace with no risk of busting). Likewise, splitting a pair of 8s is a good idea because with a hard total of 16, it's likely you will bust if you take a Hit (since so many cards count as 10). As a human being, all it takes is a little knowledge about the rules in order to construct a strategy. The GA program doesn't have that advantage, and operates completely without any pre-programmed knowledge of Blackjack. It simply uses the relative fitness scores and the mechanism of evolution to find the solution. GA Settings There are many variables or settings for a GA. You can adjust population size, how parent candidates are selected, how the resulting children may be mutated, and several other items. The following sections describe some of these settings: Setting: Selection Style Once we've solved representation and have a fitness function, the next step is to select two candidates for crossover during the process of building a new generation. There are three common styles for selection, and this program supports all of them. First, you can choose Roulette Wheel selection. It's named for a Roulette wheel because you can imagine each candidate's fitness score being a wedge in a pie chart, with a size proportionate to its relative fitness compared to the other candidates. (Of course, this assumes that all fitness scores are positive, which we will talk about shortly). The main benefit of Roulette Wheel selection is that selection is fitness-proportionate. Imagine if you had only three candidates, with fitness scores of 1, 3, and 8. The relative selection probabilities for those candidates will be 1/12, 3/12, and 8/12. The downside of Roulette Wheel selection is that it tends to be somewhat slow in terms of processing. The selection process is done by iterating through the candidates until a particular condition is matched - in other words, O(N) performance. Another potential problem with Roulette Wheel selection is that there may be situations where fitness scores vary widely, to such an extent that only certain candidates have any reasonable chance of being selected. This happens frequently in early generations, since the majority of candidates are mostly random. Although this might sound like a positive (since you ultimately want to select candidates with high fitness scores), it also results in a loss of genetic diversity. In other words, even though a particular candidate may have a low fitness score in an early generation, it may contain elements that are needed to find the ultimate solution in later generations. Ranked Selection is the solution to this problem. Instead of using raw fitness scores during the selection process, the candidates are sorted by fitness, with the worst candidate receiving a score of 0, the second worse receiving 1, and so forth, all the way to the best candidate, which has a score equal to the population size - 1. Ranked Selection is quite slow, since it combines the O(N) performance of Roulette Wheel, with the additional requirement that the candidates be sorted before selection. However, there may be circumstances where it performs better than other selection approaches. Finally, the fastest selection method of all is called Tournament Selection. This method simply selects N random candidates from the current generation, and then uses the one with the best fitness score. A tournament size of 2 means two random candidates are selected, and the best of those two is used. If you have a large tournament size (like 10), then 10 different candidates will be selected, with the best of those being the ultimate selection. That obviously tilts the balance between randomness and quality. Tournament selection works well in most cases, but it does require some experimentation to find the best tourney size. Setting: Elitism Elitism is a technique that helps ensure that the best candidates are always maintained. Since all selection methods are random to some degree, it is possible to completely lose the best candidates from one generation to another. By using Elitism, we automatically advance a certain percentage of the best candidates to the next generation. Elitism does have a negative impact on performance since all of the candidates must be sorted by fitness score. Typically Elitism is done before filling the rest of a new generation with new candidates created by crossover. Crossover Details Once two candidate solutions have been selected, the next step in building a new generation is to combine those two into a single new candidate, hopefully using the best of both parent strategies. There are a number of ways to do crossover, but the method used in this program is quite straightforward - the two fitness scores are compared, and crossover happens in a relatively proportionate way. If one candidate has a fitness of 10, and the other has a fitness of 5, then the one with fitness 10 contributes twice as much to the child as the parent with a fitness of 5. Since the fitness scores in this program are based on how much the strategy would win over thousands of hands, almost all fitness scores will be negative. (This is obviously because the rules are set up so the house always wins.) This makes it difficult to calculate relative fitnesses (how do you compare a positive number with a negative, and find relative proportions?), and also causes problems with selection methods like Roulette Wheel or Ranked. To solve this, we find the lowest fitness score of the generation and add that value to each candidate. This results in an adjusted fitness score of 0 for the very worse candidate, so it never gets selected. Mutation As has been mentioned a few times, maintaining genetic diversity in our population of candidate solutions is a good thing. It helps the GA ultimately find the very best solution, by occasionally altering a candidate in a positive direction. There are two settings for mutation. MutationRate controls what percentage of new candidates have mutation done on them. MutationImpact controls what percentage of their strategy is randomized. Population Size Population size has a significant impact on performance. The smaller the population size, the faster the GA will execute. On the other hand, if the size is too low the population may not have enough genetic diversity to find the ultimate solution. During testing, it looks like 700 to 1000 is a good balance between speed and correctness. Performance Notes This program consumes a lot of processing power. Running tests of hundreds of thousands of hands of Blackjack for hundreds or thousands of candidates consumes a lot of time. It's really imperative to write the code so that it works as efficiently as possible. If your CPU isn't consistently at or above 95% usage, there's still room for improvement. Multi-threading is a natural fit for genetic algorithms because we often want to perform the same action on each candidate. The best example of this is when we calculate fitness scores. This is often an operation that takes quite a bit of time. In our case, we're dealing out 100,000 hands, and each hand has to be played until the end. If we're single-threading that code, it's going to take a long time. Multi-threading is really the way to go. Luckily, there's a ridiculously simple way to efficiently use all of your processors for an operation like this. This code loops over all of the candidates in the currentGeneration list, calls the fitness function and sets the fitness property for each: Regardless of the number of items in the list or the number of processors on your machine, the code will efficiently run the code in a multi-threaded manner, and continue only when all of the threads are complete. One of the side effects of making this code multi-threaded is that all of the code relating to evaluating a candidate must be thread-safe, including any Singleton objects. When making code thread-safe, pay attention that you don't accidentally introduce code that will slow your program down unintentionally, because sometimes it can be quite subtle. Random numbers are central to how genetic algorithms work, so it's critical that they can be used correctly from a multithreaded environment. That means that each random number generator must be separate from the others, and it also means that each must produce a distinct series of random numbers. Random number generators use seed values which are usually time-based, like the number of milliseconds the computer has been turned on. Starting with that seed, subsequent calls will return a series of numbers that look random, but really aren't. If you start with the same seed, you get the same sequence. And that's a problem because if you create multiple random number generator objects in a loop using the default time-based seed, several of them will have the same time-based initial seed value, which will result in the same sequence of "random" numbers. That's a bug, because it can reduce the true randomness of the program a great deal, and that's vital to a genetic algorithm. There are a couple of ways to solve this problem. First, you can make the random object truly a singleton, and restrict access to it by using a Clock statement. The makes all access serialized for any random number need, which reduces performance. Another approach is to make the variable static per thread. By declaring the variable as static and also marking it with the [ThreadStatic] attribute, the .NET runtime allocates one static variable per thread. That eliminates the locking/serialization, but also has performance issues. The approach used in this application is to use a non-default seed value. In this case we call Guid.NewGuid().GetHashCode(), which generates a new, unique GUID, then gets an integer hashcode value that should be unique, depending on how GetHashCode is implemented. While multithreading really helps performance, there are also other things we can do to improve performance. For example, when dealing with large populations, the hundreds or thousands of objects that will be generated each generation can quickly turn into a huge problem related to garbage collection. In the end, the easiest way to solve that is to look through the code and find objects being allocate inside a loop. It's better to declare the variable outside of the loop, and then clear it in the loop, rather than reallocate it. In a program like this one where you could be looping hundreds of thousands of times, this can result in a very significant performance boost. For example, in an early version of this code, a Deck object was created for each hand. Since there are hundreds of candidate solutions running hundreds of thousands of trial hands, this was a huge inefficiency. The code was changed to allocate one deck per test sequence. The deck was shuffled as needed, so it never needs to be reallocated. Beyond the cards in the deck, another object type that was repeatedly created and destroyed were the candidate strategies. To mitigate this problem, a StrategyPool class was created that handles allocation and deallocation. This means that strategy objects are reused, rather than dynamically created when needed. The pool class has to be thread-safe, so it does serialize access to its methods via a Clock statement, but overall using the pool approach produced a good performance increase. Finally, a subtle form of object allocation is conversion. In an early version of the code, a utility card function used Convert.ToInt32(rankEnum). Obviously, the easiest way to convert from an enum to an int is simply to cast it, like (int)rankEnum. But it's hard to know exactly what the difference is between that approach, int.Parse(), int.TryParse(), or Convert.ToInt32(), since they can all be used and are roughly equivalent. Perhaps the compiler was boxing the enum value before passing it to Convert.ToInt32(), because the profiler identified this as a function that had large amounts of thread contention waiting - and the problem got much, much worse as the generations passed. By rewriting the conversion to use a simple cast, the program performance increased threefold (3x). Contributing Please read CONTRIBUTING.md for details on our code of conduct, and the process for submitting pull requests to us. Author Greg Sommerville - Initial work* License This project is licensed under the Apache 2.0 License - see the LICENSE.md file for details

yoha
github
LLM Vibe Score0.556
Human Vibe Score0.3408299306652369
handtracking-ioMar 27, 2025

yoha

Yoha A practical hand tracking engine. Note: Yoha is currently unmaintained. Quick Links: Demo (Code) Docs Website npm Installation npm install @handtracking.io/yoha Please note: You need to serve the files from node_modules/@handtracking.io/yoha since the library needs to download the model files from here. (Webpack Example) You need to serve your page with https for webcam access. (Webpack Example) You should use cross-origin isolation as it improves the engine's performance in certain scenarios. (Webpack Example) Description Yoha is a hand tracking engine that is built with the goal of being a versatile solution in practical scenarios where hand tracking is employed to add value to an application. While ultimately the goal is to be a general purpose hand tracking engine supporting any hand pose, the engine evolves around specific hand poses that users/developers find useful. These poses are detected by the engine which allows to build applications with meaningful interactions. See the demo for an example. Yoha is currently in beta. About the name: Yoha is short for ("Your Hand Tracking"). Language Support Yoha is currently available for the web via JavaScript. More languages will be added in the future. If you want to port Yoha to another language and need help feel free reach out. Technical Details Yoha was built from scratch. It uses a custom neural network trained using a custom dataset. The backbone for the inference in the browser is currently TensorFlow.js Features: Detection of 21 2D-landmark coordinates (single hand). Hand presence detection. Hand orientation (left/right hand) detection. Inbuilt pose detection. Supported Hand Poses: Pinch (index finger and thumb touch) Fist Your desired pose is not on this list? Feel free to create an issue for it. Performance Yoha was built with performance in mind. It is able to provide realtime user experience on a broad range of laptops and desktop devices. The performance on mobile devices is not great which hopefuly will change with the further development of inference frameworks like TensorFlow.js Please note that native inference speed can not be compared with the web inference speed. Differently put, if you were to run Yoha natively it would be much faster than via the web browser. Minimal Example Source Running locally: Drawing Demo Live Version Source Running locally:

teach-AI-in-business
github
LLM Vibe Score0.443
Human Vibe Score0.018525334165293606
aenyneJan 9, 2025

teach-AI-in-business

Teaching AI in Business ![HitCount] I am collecting material for teaching AI-related issues to non-tech people. The links should provide for a general understanding of AI without going too deep into technical issues. Please contribute! Make this Issue your First Issue I am collecting material for teaching AI-related issues to non-tech people. The links should have provide for a general understanding of AI without going too deep into technical issues. Please contribute! Kindly use only those Resources with NO CODE NEW Check out also the AI Wiki NEW Online Videos & Courses | Link to Issue | Description | |---|---| | Top Trending Technologies | Youtube Channel to master top trending technologyies including artificial intelligence | | AI4All | AI 4 All is a resource for AI facilitators to bring AI to scholars and students | | Elements of AI | Elements of AI is a free open online course to teach AI principles | | Visual Introduction to Machine Learning | Visual introduction to Machine Learning is a beautiful website that gives a comprehensive introduction and easily understood first encounter with machine learning | | CS50's Introduction to Artificial Intelligence with Python | Learn to use machine learning in Python in this introductory course on artificial intelligence.| | Crash course for AI | This is a fun video series that introduces students and educators to Artificial Intelligence and also offers additional more advanced videos. Learn about the basics, neural networks, algorithms, and more. | Youtuber Channel Machine Learning Tutorial | Youtube Channel Turorial Teachable Machine for beginner | | Artificial Intelligence (AI) |Learn the fundamentals of Artificial Intelligence (AI), and apply them. Design intelligent agents to solve real-world problems including, search, games, machine learning, logic, and constraint satisfaction problems | | AI For Everyone by Andrew Ng | AI For Everyone is a course especially for people from a non-technical background to understand AI strategies | | How far is too far? The age of AI| This is a Youtube Orignals series by Robert Downey| | Fundamentals of Artificial Intelligence|This course is for absolute beginners with no technical knowledge.| | Bandit Algorithm (Online Machine Learning)|No requirement of technical knowledge, but a basic understending of Probability Ttheory would help| | An Executive's Guide to AI|This is an interactive guide to teaching business professionals how they might employ artificial intelligence in their business| | AI Business School|Series of videos that teach how AI may be incorporated in various business industries| | Artificial Intelligence Tutorial for Beginners | This video will provide you with a comprehensive and detailed knowledge of Artificial Intelligence concepts with hands-on examples. | | Indonesian Machine Learning Tutorial | Turorial Teachable Machine to train a computer for beginner | | Indonesian Youtube Playlist AI Tutorial | Youtube Playlist AI Tutorial For Beginner | | Artificial Intelligence Search Methods For Problem Solving By Prof. Deepak Khemani|These video lectures are for absolute beginners with no technical knowledge| | AI Basics Tutorial | This video starts from the very basics of AI and ML, and finally has a hands-on demo of the standard MNIST Dataset Number Detection model using Keras and Tensorflow.| | Simple brain.js Tutorial | This video explains a very simple javascript AI library called brain.js so you can easily run AI in the browser.| | Google AI| A complete kit for by google official for non-tech guy to start all over from basics, till advanced | | Microsoft AI for Beginners| A self-driven curriculum by Microsoft, which includes 24 lessons on AI. | Train Your Own AI | Link to Issue | Description | |---|---| | Teachable Machine | Use Teachable Machine to train a computer to recognize your own images, sounds, & poses | | eCraft2Learn | Resource and interactive space (Snap, a visual programming environment like Scratch) to learn how to create AI programs | | Google Quick Draw | Train an AI to guess from drawings| | Deepdream Generator| Merge Pictures to Deep Dreams using the Deepdream Generator| | Create ML|Quickly build and train Core ML models on your Mac with no code.| | What-If Tool|Visually probe the behavior of trained machine learning models, with minimal coding.| | Metaranx|Use and build artificial intelligence tools to analyze and make decisions about your data. Drag-and-drop. No code.| | obviously.ai|The total process of building ML algorithms, explaining results, and predicting outcomes in one single click.| Articles | By & Title | Description | |---|---| | Artificial Intelligence | Wikipedia Page of AI | | The Non-Technical AI Guide | One of the good blog post that could help AI more understandable for people without technical background | | LIAI | A detailed introduction to AI and neural networks | | Layman's Intro | A layman's introduction to AI | | AI and Machine Learning: A Nontechnical Overview | AI and Machine Learning: A Nontechnical Overview from OREILLY themselves is a guide to learn anyone everything they need to know about AI, focussed on non-tech people | | What business leaders need to know about artifical intelligence|Short article that summarizes the essential aspects of AI that business leaders need to understand| | How Will No-Code Impact the Future of Conversational AI | A humble explanation to the current state of converstational AI i.e.Chatbots and how it coul evolve with the current trend of no coding. | | Investopedia | Basic explanation of what AI is in a very basic and comprehensive way | | Packtpub | A non programmer’s guide to learning Machine learning | | Builtin | Artificial Intelligence.What is Artificial Intelligence? How Does AI Work? | | Future Of Life | Benefits & Risks of Artificial Intelligence | | NSDM India -Arpit | 100+ AI Tools For Non-Coders That Will Make Your Marketing Better. | | AI in Marketing for Startups & Non-technical Marketers | A practical guide for non-technical people | | Blog - Machine Learning MAstery | Blogs and Articles by Jason Browniee on ML | | AI Chatbots without programming| Chatbots are increasingly in demand among global businesses. This course will teach you how to build, analyze, deploy and monetize chatbots - with the help of IBM Watson and the power of AI.| Book Resources for Further Reading | Author | Book | Description & Notes | |---|---|---| | Ethem Alpaydin|Machine Learning: The New AI | Graph Theory with Applications to Engineering & Computer Science. A concise overview of machine learning—computer programs that learn from data—which underlies applications that include recommendation systems, face recognition, and driverless cars. | | Charu C. Aggarwal| Neural Networks and Deep Learning | This book covers both classical and modern models in deep learning. The primary focus is on the theory and algorithms of deep learning. The book is also rich in discussing different applications in order to give the practitioner a flavor of how neural architectures are designed for different types of problems. | | Hal Daumé III | A Course in Machine Learning | The purpose of this book is to provide a gentle and pedagogically organized introduction to the field. A second goal of this book is to provide a view of machine learning that focuses on ideas and models, not on math. | | Ian Goodfellow and Yoshua Bengio and Aaron Courville| Deep Learning | The book starts with a discussion on machine learning basics, including the applied mathematics and algorithms needed to effectively study deep learning from an academic perspective. There is no code covered in the book, making it perfect for a non-technical AI enthusiast. | | Peter Harrington|Machine Learning in Action| (Source: https://github.com/kerasking/book-1/blob/master/ML%20Machine%20Learning%20in%20Action.pdf) This book acts as a guide to walk newcomers through the techniques needed for machine learning as well as the concepts behind the practices.| | Jeff Heaton| Artificial Intelligence for Humans |This book helps its readers get an overview and understanding of AI algorithms. It is meant to teach AI for those who don’t have an extensive mathematical background. The readers need to have only a basic knowledge of computer programming and college algebra.| | John D. Kelleher, Brian Mac Namee and Aoife D'Arcy|Fundamentals of Machine Learning for Predictive Data Analytics: Algorithms, Worked Examples, and Case Studies (The MIT Press)|This book covers all the fundamentals of machine learning, diving into the theory of the subject and using practical applications, working examples, and case studies to drive the knowledge home.| | Deepak Khemani| [A First Course in Artificial Intelligence] | It is an introductory course on Artificial Intelligence, a knowledge-based approach using agents all across and detailed, well-structured algorithms with proofs. This book mainly follows a bottom-up approach exploring the basic strategies needed problem-solving on the intelligence part. | | Maxim Lapan | Deep Reinforcement Learning Hands-On - Second Edition | Deep Reinforcement Learning Hands-On, Second Edition is an updated and expanded version of the bestselling guide to the very latest reinforcement learning (RL) tools and techniques. It provides you with an introduction to the fundamentals of RL, along with the hands-on ability to code intelligent learning agents to perform a range of practical tasks. | | Tom M Mitchell | Machine Learning | This book covers the field of machine learning, which is the study of algorithms that allow computer programs to automatically improve through experience. The book is intended to support upper level undergraduate and introductory level graduate courses in machine learning. | | John Paul Mueller and Luca Massaron|Machine Learning For Dummies|This book aims to get readers familiar with the basic concepts and theories of machine learning and how it applies to the real world. And "Dummies" here refers to absolute beginners with no technical background.The book introduces a little coding in Python and R used to teach machines to find patterns and analyze results. From those small tasks and patterns, we can extrapolate how machine learning is useful in daily lives through web searches, internet ads, email filters, fraud detection, and so on. With this book, you can take a small step into the realm of machine learning and we can learn some basic coding in Pyton and R (if interested)| | Michael Nielsen| Neural Networks and Deep Learning |Introduction to the core principles of Neural Networks and Deep Learning in AI| | Simon Rogers and Mark Girolami| A Course in Machine Learning |A First Course in Machine Learning by Simon Rogers and Mark Girolami is the best introductory book for ML currently available. It combines rigor and precision with accessibility, starts from a detailed explanation of the basic foundations of Bayesian analysis in the simplest of settings, and goes all the way to the frontiers of the subject such as infinite mixture models, GPs, and MCMC.| |Peter Norvig| Paradigm of Artificial Intelligence Programming |Paradigms of AI Programming is the first text to teach advanced Common Lisp techniques in the context of building major AI systems. By reconstructing authentic, complex AI programs using state-of-the-art Common Lisp, the book teaches students and professionals how to build and debug robust practical programs, while demonstrating superior programming style and important AI concepts.| | Stuart Russel & Peter Norvig | Artificial Intelligence: A Modern Approach, 3rd Edition | This is the prescribed text book for my Introduction to AI university course. It starts off explaining all the basics and definitions of what AI is, before launching into agents, algorithms, and how to apply them. Russel is from the University of California at Berkeley. Norvig is from Google.| | Richard S. Sutton and Andrew G. Barto| Reinforcement Learning: An Introduction |Reinforcement learning, one of the most active research areas in artificial intelligence, is a computational approach to learning whereby an agent tries to maximize the total amount of reward it receives while interacting with a complex, uncertain environment.| | Alex Smola and S.V.N. Vishwanathan | Introduction to Machine Learning | Provides the reader with an overview of the vast applications of ML, including some basic tools of statistics and probability theory. Also includes discussions on sophisticated ideas and concepts. | | Shai Shalev-Shwartz and Shai Ben-David | Understanding Machine Learning From Theory to Algorithms |The primary goal of this book is to provide a rigorous, yet easy to follow, introduction to the main concepts underlying machine learning. | | Chandra S.S.V | Artificial Intelligence and Machine Learning | This book is primarily intended for undergraduate and postgraduate students of computer science and engineering. This textbook covers the gap between the difficult contexts of Artificial Intelligence and Machine Learning. It provides the most number of case studies and worked-out examples. In addition to Artificial Intelligence and Machine Learning, it also covers various types of learning like reinforced, supervised, unsupervised and statistical learning. It features well-explained algorithms and pseudo-codes for each topic which makes this book very useful for students. | | Oliver Theobald|Machine Learning For Absolute Beginners: A Plain English Introduction|This is an absolute beginners ML guide.No mathematical background is needed, nor coding experience — this is the most basic introduction to the topic for anyone interested in machine learning.“Plain” language is highly valued here to prevent beginners from being overwhelmed by technical jargon. Clear, accessible explanations and visual examples accompany the various algorithms to make sure things are easy to follow.| | Tom Taulli | Artificial Intelligence Basics: A Non-Technical Introduction | This book equips you with a fundamental grasp of Artificial Intelligence and its impact. It provides a non-technical introduction to important concepts such as Machine Learning, Deep Learning, Natural Language Processing, Robotics and more. Further the author expands on the questions surrounding the future impact of AI on aspects that include societal trends, ethics, governments, company structures and daily life. | |Cornelius Weber, Mark Elshaw, N. Michael Mayer| Reinforcement Learning |Learning is a very important aspect. This book is on reinforcement learning which involves performing actions to achieve a goal. The first 11 chapters of this book describe and extend the scope of reinforcement learning.| |John D. Kelleher, Brian Mac Namee, Aoife D'arcy| Algorithms, Worked Examples, and Case Studies | A comprehensive introduction to the most important machine learning approaches used in predictive data analytics, covering both theoretical concepts and practical applications. |

🔥 AI Agents Will Skyrocket in the Coming Years—Jensen Huang Explains! 🚀#shorts #youtubeshorts #ai
youtube
LLM Vibe Score0.383
Human Vibe Score0.34
The AI EntrepreneursSep 20, 2024

🔥 AI Agents Will Skyrocket in the Coming Years—Jensen Huang Explains! 🚀#shorts #youtubeshorts #ai

🔔 Subscribe to our Newsletter: https://aientrepreneurs.standout.digital?utm_source=yt 🔔 Subscribe for more tech insights: https://www.youtube.com/channel/UCjMceG0jS4Lr5ZACzpYjHf In this exciting video, Jensen Huang shares his vision for the future of AI agents over the coming years. As AI continues to evolve, Huang explains how these agents will make massive strides in problem-solving, automation, and innovation, transforming industries worldwide. 🔹 Learn about the future progress of AI agents from NVIDIA’s CEO. 🔹 Discover how AI agents will revolutionize business and technology. 🔹 Explore the advancements AI agents will bring in the coming years. #JensenHuang #NVIDIA #AIAgents #AIProgress #ArtificialIntelligence #FutureOfAI #AIRevolution #TechInnovation #Automation #TrendingNow Join 66,000+ AI lovers with 4 free gifts🎁: 100 ChatGPT prompts, AI writer to go viral, "Building A Minimum Viable Business In Record Time" Course AND "4-Hour AI Workweek" course! Click here: https://aientrepreneurs.standout.digital?utm_source=yt ✨Exclusive Freebies and Tools: 📙 (Free Course) The 4 Hour AI Workweek: https://aientrepreneurs.standout.digital?utm_source=yt 📑 Bubble No Code AI Template: https://launchai.pro/?aff=wqp8K 🛠️ #1 AI SEO Tool: https://tryjournalist.com?aff=ge 🐤 Grow on Twitter with AI: http://app.tweethunter.io/?via=george-p 📚 Free Lead Magnets Playbook: https://aientrepreneurs.gumroad.com/l/yndih 👨‍💻 AI UI Design Tool: https://get.uizard.io/affc?offerid=3&aff_id=683 📹 Free YouTube Growth Playbook: https://aientrepreneurs.gumroad.com/l/qbswh ✍️ Free Script Writing Guide: https://aientrepreneurs.gumroad.com/l/yfhxgk 🤖 Free 100 ChatGPT Prompts: https://aientrepreneurs.gumroad.com/l/npyks ✨OUR OTHER SOCIALS: 🎙️ Podcast Deep Dive- https://podcast.standout.digital/ 💻 Check out our blog- https://www.standout.digital/blog/ 🐤 Follow us on Twitter- https://twitter.com/EntrepreneursAI 🤳 Check out our Instagram- https://www.instagram.com/standoutaientrepreneurs 📷 Dive into our TikTok- https://www.tiktok.com/@theaientrepreneurs 👨‍💼 Connect on LinkedIn- https://www.linkedin.com/company/theaientrepreneurs Video credits: @CNET Full video: https://youtu.be/kfe3ajUYSdc?feature=shared Some links may be referral links* Thank you!

Meet The AI Entrepreneur Who Used LinkedIn To Raise $13.8 Million
youtube
LLM Vibe Score0.436
Human Vibe Score0.64
ForbesApr 19, 2024

Meet The AI Entrepreneur Who Used LinkedIn To Raise $13.8 Million

Benjamin Harvey, the CEO of AI Squared, says he’s added investors including former TIAA CEO Roger Ferguson. Harvey joined Forbes senior writer, Jabari Young, at the Nasdaq MarketSite to discuss the startup’s Series A raise. Read the full story on Forbes: https://www.forbes.com/sites/jabariyoung/2024/04/17/meet-the-ai-entrepreneur-who-used-linkedin-to-raise-138-million/?sh=60958bea5837 0:00 Introduction 2:16 Benjamin Gives Biggest Tip On Learning Profit Loss 5:00 Benjamin Harvey On The State Of AI 8:25 How Will AI Evolve And Change In The Future? 14:04 What Is It Like To Be CEO Of AI Squared? 17:04 How Benjamin's Upbringing And Love Of Cartoons Helps Put Ideas Together In Business 23:02 Benjamin On Getting Investors For AI Squared 25:56 Benjamin's Take On ChatGPT And How Its Used 29:48 Artificial Intelligence: Benjamin's Take On What's Next 34:49 A Good AI Platform vs. A Great One Subscribe to FORBES: https://www.youtube.com/user/Forbes?sub_confirmation=1 Fuel your success with Forbes. Gain unlimited access to premium journalism, including breaking news, groundbreaking in-depth reported stories, daily digests and more. Plus, members get a front-row seat at members-only events with leading thinkers and doers, access to premium video that can help you get ahead, an ad-light experience, early access to select products including NFT drops and more: https://account.forbes.com/membership/?utmsource=youtube&utmmedium=display&utmcampaign=growthnon-subpaidsubscribe_ytdescript Stay Connected Forbes newsletters: https://newsletters.editorial.forbes.com Forbes on Facebook: http://fb.com/forbes Forbes Video on Twitter: http://www.twitter.com/forbes Forbes Video on Instagram: http://instagram.com/forbes More From Forbes: http://forbes.com Forbes covers the intersection of entrepreneurship, wealth, technology, business and lifestyle with a focus on people and success.