Best Way to Learn About AI | VibeBuilders.ai Resource Directory

Team Polk’s Bryan Pellegrino Talks About His AI Research And How It Helped Formulate Strategies To Win $1.2 Million [P]

LateProduce•This week

I'm technical looking for non-technical co-founder with a good idea and good background.

Hi all! So things have fell through with my co-founder and I have decided to start looking for new opportunities. I'm a senior software engineer looking to work with someone who already has an idea. I've primarily worked on fintech during my career. I've build payment systems, fraud prevention mechanisms, and arrear collections infrastructure. The products I've had a key role in developing have helped UK governments and banks save millions of pounds. I've built beautiful front end systems (web, android, and IOS) that are being used by thousands of people and have developed back end infrastructure that is currently servicing millions of requests per day. I'm open to working in most domains if the idea and the founder behind are great. I'm looking for a co-founder who is ideally an expert in there space and has a good idea. I'll try to get back to everyone who pings me. All the best!

#reddit #technical #looking

Accepted To Y Combinator - I will not promote

0

AI-Data-Expert•This week

Accepted To Y Combinator - I will not promote

UPDATE: Thanks to everyone for giving clear and honest advice. It really helped me to make my decisions and know what I should focus on first. This community is awesome! I'm trying to get accepted to Y Combinator and realistically assessing my profile. I'm a non-technical, solo founder, in my early 40s, and balancing startup ambitions with family responsibilities (two kids). I understand the traditional YC profile often skews younger and technical, and solo non-technical founders might face an uphill climb. I'm specifically interested in hearing from anyone in r/startups who can identify with this background and applied (or was accepted) to YC. Were you accepted to YC despite being a non-technical, solo founder, and/or over 40 with family commitments? If you applied and were not accepted, do you feel these factors played a role, and what was your experience? Any advice for someone in my situation to strengthen my application and approach? Does anyone have recommendations for me as a non-technical founder to effectively attract and onboard a technical co-founder in the AI domain? Thank you for sharing your expertise and experiences.

#reddit #accepted #combinator

0

0.667

GDbuildsGD•This 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.

#reddit #spent #months

0

found_it_online_01•This week

Selling equity - what’s next?

Hey all, Seeking some guidance / advice as I plan my exit from a marketing agency I helped grow to $5M Long story short, I was hired part time to build their digital marketing department that sat at around 40k annual agency revenue. Since then I’ve become a minority equity partner, and at one point the agency was above $5M in gross agency revenue. The digital department that I run had up to 13 FTE employees at one point And digital revenue accounted for 60% of all agency revenue for the last 3-4 years. So, why am I leaving? Things are groovy, right? Well, we have dropped from $5M to now $3M this year and we’ll be lucky to hit that. As a minority equity party it’s been hard to watch leadership continue to disregard our agency as a digital agency. They don’t want to niche down, and they don’t want to identify as a digital agency, but instead by a full service “strategic agency”. Clients have felt our lack of expertise and direction, so they leave for someone who is an expert in xyz platform or industry. I no longer see their vision, and so I’m planning a sale of my equity and looking for new venture opportunities. While I am perfectly capable of running Google ads and Facebook ads campaigns, and as an accomplished SEO I know how to rank sites, and still find it fun. But I’m not interested in the labor arbitrage model of agency work anymore. I’d rather build a portfolio of in-house properties or digital assets where I have more control. Lately my obsession has been using AI and zapier to automate business processes, documentation, project management etc. Agency life has also exposed me to a lot of industries and business models, which I am always fascinated by. Eventually I will launch my own business, but I’m supporting my partner while they finish school. So I’m a single income household.. Therefore a W2 would be ideal but I’m open to contract work. So my question is- what positions or roles would I fill? I’ve done my share of research but this community has always given me new things to consider. Any feedback or questions are welcomed.

#reddit #selling #equity

0

1

ayezee33•This week

Am I on the right track?

This might be a little long for the average reader. But i'll do my best to format it so it's skimmable. Context I left my SaaS company 2 months ago. I was employee number 4 and helped them grow to 8 figures. I had a seat at the executive table and equity in the business. Burnt out and wanted to start my own thing. I forgot how hard it is to go from 0 👉 1 📚 Two schools of thought Build a product that solves your pain point and find others with that pain point Perform customer discovery calls until you get signal and start building + follow up with them 🥇 First approach For the last 45 days I built the product I wished I had when leading a 10 person marketing/sales team for the SaaS I was previously at. It checked all the boxes, pulled data, automated specific steps, showed the conversion tracking, data, etc. I launched it as a beta to my close network and the crowd went MILD. 😒 After some follow up - I realized I built something that already kind of exists and it's hard to convince others (even those who personally know me) that it's different or better. Undiscouraged, I am going to go back to the drawing board and try approach #2 above and schedule some customer discovery calls. 🥈 Second approach After trying and failing to turn the marketing numbers around at my last role I am convicted of 4 brutal truths about digital marketing today Truth #1 – AI-generated content is flooding the internet and ANYONE can and will be creating content with AI. Truth #2 – Ranking for high-volume keywords is harder than ever and probably not worth it anymore. Truth #3 – AI-driven efficiency is non-negotiable. If you haven’t installed AI in your business - you are WAY behind. Truth #4 – Most businesses are thinking about AI completely wrong. Easy button vs quality stair step. I have some early thoughts on how I would like to solve this (backed by data and some user stories). But my main question and the entire point of this post is.... ⁉️ Questions Before I schedule these product discovery calls should I make it clear where I am convicted and find those who want to talk (agree or disagree) with the above. Or just keep that out of the mix and ask them my product discovery questions regardless? I am probably overthinking it - but I just hit up my personal network with a beta launch, feels silly to go back with product discovery questions for them. Is there a good place (besides reddit) to pay people for product discovery calls? A quick Google Search and it's unclear to me.

#reddit #right #track?

0

1

Royal_Rest8409•This 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.

#reddit #founder #built

After building an AI Co-founder to solve my startup struggles, I realized we might be onto something bigger. What problems would you want YOUR AI Co-founder to solve?

0

Consistent_Yak6765•This week

After building an AI Co-founder to solve my startup struggles, I realized we might be onto something bigger. What problems would you want YOUR AI Co-founder to solve?

A few days ago, I shared my entrepreneurial journey and the endless loop of startup struggles I was facing. The response from the community was overwhelming, and it validated something I had stumbled upon while trying to solve my own problems. In just a matter of days, we've built out the core modules I initially used for myself, deep market research capabilities, automated outreach systems, and competitor analysis. It's surreal to see something born out of personal frustration turning into a tool that others might actually find valuable. But here's where it gets interesting (and where I need your help). While we're actively onboarding users for our alpha test, I can't shake the feeling that we're just scratching the surface. We've built what helped me, but what would help YOU? When you're lying awake at 3 AM, stressed about your startup, what tasks do you wish you could delegate to an AI co-founder who actually understands context and can take meaningful action? Of course, it's not a replacement for an actual AI cofounder, but using our prior entrepreneurial experience and conversations with other folks, we understand that OUTREACH and SALES might actually be a big problem statement we can go deeper on as it naturally helps with the following: Idea Validation - Testing your assumptions with real customers before building Pricing strategy - Understanding what the market is willing to pay Product strategy - Getting feedback on features and roadmap Actually revenue - Converting conversations into real paying customers I'm not asking you to imagine some sci-fi scenario, we've already built modules that can: Generate comprehensive 20+ page market analysis reports with actionable insights Handle customer outreach Monitor competitors and target accounts, tracking changes in their strategy Take supervised actions based on the insights gathered (Manual effort is required currently) But what else should it do? What would make you trust an AI co-founder with parts of your business? Or do you think this whole concept is fundamentally flawed? I'm committed to building this the right way, not just another AI tool or an LLM Wrapper, but an agentic system that can understand your unique challenges and work towards overcoming them. Whether you think this is revolutionary or ridiculous, I want to hear your honest thoughts. But more importantly, I want to hear your unfiltered feedback in the comments. What would make this truly valuable for YOU? Edit 1: The AI cofounder will take no equity in your startup.

#reddit #after #building

What I Learned from a Failed Startup: Seeking Advice on Engineering, Co-Founder Agreements & Execution (i will not promote)

0

1

GummyBear8659•This week

What I Learned from a Failed Startup: Seeking Advice on Engineering, Co-Founder Agreements & Execution (i will not promote)

Hey everyone! Long-time lurker, first-time founder here. I’m reaching out to get feedback on a recent startup experience—what went wrong, what I could have done better, and how I should approach future opportunities. The Background There were three founders in this venture: • Founder A (CEO, 50%) – The product/growth guy who identified the problem space. • Founder B (Me, CTO, 37.5%) – A software engineer with a software dev shop and multiple clients. I wanted to diversify into building my own products but am not inherently a “product person.” • Founder C (COO, 12.5%) – Brought into the mix by Founder A, with the goal of leveraging his network for traction once the product was built. The idea was to create Product X, a solution targeting the SMB space while competitors were moving upmarket. It wasn’t revolutionary—more of a strategic market play. The Initial Plan & My Role • Founder A would define and prioritize product specs, guiding what needed to be built. • I (Founder B) didn’t have time to code myself, so I allocated engineers from my dev shop (which I personally paid for). My stake was adjusted from 32.5% to 37.5% to reflect this contribution. • Founder C was more of an observer early on, planning to help with traction once we had a product ready. We agreed on a 1-year cliff and a 4-year vesting schedule for equity. Where Things Started to Go Wrong • Lack of a Clear Product Roadmap – Founder A was very focused on getting something built fast, but we never signed off on a structured roadmap or milestones. I underestimated the complexity of what was actually needed for customer conversations. • Engineering Expectations vs. Reality – The team (one part-time lead + two full-time juniors from my dev shop) faced early feedback that development was too slow. In response, I ramped up the lead to full-time and added a part-time PM. But Founder A continued pushing for speed, despite real hurdles (OAuth integrations, etc.). • Shifting MVP Goalposts – Midway, Founder A concluded that an MVP wouldn’t cut it—we needed a more complete product to be competitive. This meant more engineering, more delays, and more of my own money spent on development. The Breaking Point Near the 1-year vesting mark, we had an opportunity: a paying client willing to fund an app. I didn’t have devs on the bench, so I asked Founder A to hold off our project briefly while I hired more engineers to avoid stalling either effort. This was the final straw. Founder A (with Founder C somewhat aligned) decided the arrangement wasn’t working—citing past disagreements and the “slowness” issue. The decision was made to end the partnership. Now, Founder A, as majority holder, is requesting a full handover of the code, Founder C is indifferent, and all engineering costs I covered are essentially lost. Key Takeaways (So Far) Crystal-Clear Agreements Upfront – A formalized product roadmap and timeline should’ve been locked in from day one. Business Needs > Engineering Standards – I wanted to build something solid and scalable, but in an early-stage startup, speed to market is king. This was before AI tools became mainstream, so our approach wasn’t as optimized. Don’t Overextend Without Protection – I personally financed all engineering, but without clear safeguards, that investment became a sunk cost. Expenses Must Be Distributed – I was solely covering engineering salaries, which created an imbalance in financial risk. Future partnerships should ensure costs are shared proportionally, rather than one person shouldering the burden. Where I Need Advice Looking back, I want to improve as an engineer, CEO, and co-founder. • What should I have done differently in structuring this partnership? • How do you balance engineering quality with the startup need for speed? • As a dev shop owner, how can I better navigate equity deals where I’m also bringing in engineering resources? I really appreciate everyone who went through this long post and provide any insights from founders, engineers, or anyone who has been in a similar situation. Thanks for reading! ===================================================================== For readers who might be thinking what set this type of expectation? Because I had a dev shop and I thought my co-founders will be understanding of my business circumstance and I was a bit trigger to build a product with a C-exec team, I gave the impression of "unlimited" engineering which I later realized down the line that it was not feasible for me. Something I learned that I have to be more careful with and set expectations accordingly from the very beginning. And from the feedback of the commenters here, I am much more aware what I should offer and how to set expectations, esp. in the early stages of execution. So thank you all! 🙏🏾 EDIT: I would like to thank everyone who contributed to this thread. You not only helped me but future founders who are considering to get into the startup scene!

#reddit #learned #failed

0

0.667

GDbuildsGD•This 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.

#reddit #spent #months

0

1

GummyBear8659•This week

What I Learned from a Failed Startup: Seeking Advice on Engineering, Co-Founder Agreements & Execution (i will not promote)

Hey everyone! Long-time lurker, first-time founder here. I’m reaching out to get feedback on a recent startup experience—what went wrong, what I could have done better, and how I should approach future opportunities. The Background There were three founders in this venture: • Founder A (CEO, 50%) – The product/growth guy who identified the problem space. • Founder B (Me, CTO, 37.5%) – A software engineer with a software dev shop and multiple clients. I wanted to diversify into building my own products but am not inherently a “product person.” • Founder C (COO, 12.5%) – Brought into the mix by Founder A, with the goal of leveraging his network for traction once the product was built. The idea was to create Product X, a solution targeting the SMB space while competitors were moving upmarket. It wasn’t revolutionary—more of a strategic market play. The Initial Plan & My Role • Founder A would define and prioritize product specs, guiding what needed to be built. • I (Founder B) didn’t have time to code myself, so I allocated engineers from my dev shop (which I personally paid for). My stake was adjusted from 32.5% to 37.5% to reflect this contribution. • Founder C was more of an observer early on, planning to help with traction once we had a product ready. We agreed on a 1-year cliff and a 4-year vesting schedule for equity. Where Things Started to Go Wrong • Lack of a Clear Product Roadmap – Founder A was very focused on getting something built fast, but we never signed off on a structured roadmap or milestones. I underestimated the complexity of what was actually needed for customer conversations. • Engineering Expectations vs. Reality – The team (one part-time lead + two full-time juniors from my dev shop) faced early feedback that development was too slow. In response, I ramped up the lead to full-time and added a part-time PM. But Founder A continued pushing for speed, despite real hurdles (OAuth integrations, etc.). • Shifting MVP Goalposts – Midway, Founder A concluded that an MVP wouldn’t cut it—we needed a more complete product to be competitive. This meant more engineering, more delays, and more of my own money spent on development. The Breaking Point Near the 1-year vesting mark, we had an opportunity: a paying client willing to fund an app. I didn’t have devs on the bench, so I asked Founder A to hold off our project briefly while I hired more engineers to avoid stalling either effort. This was the final straw. Founder A (with Founder C somewhat aligned) decided the arrangement wasn’t working—citing past disagreements and the “slowness” issue. The decision was made to end the partnership. Now, Founder A, as majority holder, is requesting a full handover of the code, Founder C is indifferent, and all engineering costs I covered are essentially lost. Key Takeaways (So Far) Crystal-Clear Agreements Upfront – A formalized product roadmap and timeline should’ve been locked in from day one. Business Needs > Engineering Standards – I wanted to build something solid and scalable, but in an early-stage startup, speed to market is king. This was before AI tools became mainstream, so our approach wasn’t as optimized. Don’t Overextend Without Protection – I personally financed all engineering, but without clear safeguards, that investment became a sunk cost. Expenses Must Be Distributed – I was solely covering engineering salaries, which created an imbalance in financial risk. Future partnerships should ensure costs are shared proportionally, rather than one person shouldering the burden. Where I Need Advice Looking back, I want to improve as an engineer, CEO, and co-founder. • What should I have done differently in structuring this partnership? • How do you balance engineering quality with the startup need for speed? • As a dev shop owner, how can I better navigate equity deals where I’m also bringing in engineering resources? I really appreciate everyone who went through this long post and provide any insights from founders, engineers, or anyone who has been in a similar situation. Thanks for reading! ===================================================================== For readers who might be thinking what set this type of expectation? Because I had a dev shop and I thought my co-founders will be understanding of my business circumstance and I was a bit trigger to build a product with a C-exec team, I gave the impression of "unlimited" engineering which I later realized down the line that it was not feasible for me. Something I learned that I have to be more careful with and set expectations accordingly from the very beginning. And from the feedback of the commenters here, I am much more aware what I should offer and how to set expectations, esp. in the early stages of execution. So thank you all! 🙏🏾 EDIT: I would like to thank everyone who contributed to this thread. You not only helped me but future founders who are considering to get into the startup scene!

#reddit #learned #failed

0

Consistent_Yak6765•This week

After building an AI Co-founder to solve my startup struggles, I realized we might be onto something bigger. What problems would you want YOUR AI Co-founder to solve?

A few days ago, I shared my entrepreneurial journey and the endless loop of startup struggles I was facing. The response from the community was overwhelming, and it validated something I had stumbled upon while trying to solve my own problems. In just a matter of days, we've built out the core modules I initially used for myself, deep market research capabilities, automated outreach systems, and competitor analysis. It's surreal to see something born out of personal frustration turning into a tool that others might actually find valuable. But here's where it gets interesting (and where I need your help). While we're actively onboarding users for our alpha test, I can't shake the feeling that we're just scratching the surface. We've built what helped me, but what would help YOU? When you're lying awake at 3 AM, stressed about your startup, what tasks do you wish you could delegate to an AI co-founder who actually understands context and can take meaningful action? Of course, it's not a replacement for an actual AI cofounder, but using our prior entrepreneurial experience and conversations with other folks, we understand that OUTREACH and SALES might actually be a big problem statement we can go deeper on as it naturally helps with the following: Idea Validation - Testing your assumptions with real customers before building Pricing strategy - Understanding what the market is willing to pay Product strategy - Getting feedback on features and roadmap Actually revenue - Converting conversations into real paying customers I'm not asking you to imagine some sci-fi scenario, we've already built modules that can: Generate comprehensive 20+ page market analysis reports with actionable insights Handle customer outreach Monitor competitors and target accounts, tracking changes in their strategy Take supervised actions based on the insights gathered (Manual effort is required currently) But what else should it do? What would make you trust an AI co-founder with parts of your business? Or do you think this whole concept is fundamentally flawed? I'm committed to building this the right way, not just another AI tool or an LLM Wrapper, but an agentic system that can understand your unique challenges and work towards overcoming them. Whether you think this is revolutionary or ridiculous, I want to hear your honest thoughts. But more importantly, I want to hear your unfiltered feedback in the comments. What would make this truly valuable for YOU? Edit 1: The AI cofounder will take no equity in your startup.

#reddit #after #building

I will not promote. I am looking for a collaborator to develop an AI agent.

0

Chemes96•This week

I will not promote. I am looking for a collaborator to develop an AI agent.

Hi, I got an Idea and I am looking for someone to collaborate to develop an MVP. I am from Algeria (North Africa), I recently graduated from a university abroad. During my years of study a lot of people (mainly from non-western countries) reached out to me for helping them gather information about enrolling to universities. I helped a lot of the students, and a lot of them were available to pay me for it. There is a huge market for people from non-western countries wanting to study in western countries, and people in my country are available to pay 500 dollars for just getting the chance to get an admission and a visa to study aborad. We are talking generally about sons of rich dads who are lazy or lack information to do the procedure. The procedure to get enrolled is pretty repetitive, meaning that it can be replicated, and generally the universities ask for the same documents, with slightly different requirements. Based on this, I was thinking: Why not automating this? I already have a network of people that can test whatever this AI agent will look like. Now I am in a state in which I need a tech person (I am a techie too) to collaborate. I am serious, and I have personal savings that can be used for tech tools and frameworks to develop an MVP.

#reddit #will #promote.

0

1

adriannelestrange•This week

I studied how 7 Founders found their first 100 customers for their businesses. Summarizing it here!

I am learning marketing, and so I combed through the internet to find specific advice that helped founders reach 100 users and not random Google answers. Here’s what I found: Llama Life by Marie Marie founder of Llama Life, a productivity app ($51.4K+ revenue) got her first 100 users using Snowballing effect. She shared great advice that I want to add here verbatim, “Need to think about what you have that you can leverage based on your current situation. eg..When you have no customers, think about where you can post to get the 1st customer eg Product Hunt. If you do well on PH, say you get #3 product of the day, then you post somewhere else saying ‘I got #3 product of the day’.. to get your next few customers. Maybe that post is on reddit with some learnings that you found. If the reddit post does well, then you might post it on Twitter, saying reddit did well and what learnings you got from that etc. or even if it doesn’t do well you can still post about it.” Another tip she shared is to build related products that get more viral than the product itself. These are small stand-alone sites that would appeal to the same target audience, but by nature, are more shareable. On these sites, you can mention your startup like: ‘brought to you by Llama Life’ and then provide a link to the main website if someone is interested. If one of those gets viral or ranks on Google, you’ll have a passive traffic source. Scraping bee by Pierre Pierre, founder of Scraping Bee, a web scraping tool has now reached $1.5M ARR. Pierre and his cofounder Kevin started with 10 Free Beta Users in 2019, and after 6 months asked them to take a paid subscription if they wanted to continue using the product. That’s how they got their first user within 50 minutes of that email. Then they listed it on dozens of startup directories but their core strategy was writing the best possible content for their target audience — Developers. 3 very successful pieces of content that worked were : A small tutorial on how to scrape single-page application An extensive general guide about web scraping without getting blocked A complete introduction to web scraping with Python They didn’t do content marketing for the sake of content marketing but deep-dived into the value they were providing their customer. One of these got 70K visits, and all this together got them to over 100 users. WePay by Bill Clerico Bill Clerico left his cushy corporate job to build WePay which was then acquired for $400M got his first users by using his app. He got his first users by using his app! The app was for group payments. So he hosted a Poker tournament at his house and collected payments only with his app. Then they hosted a barbecue for fraternity treasurers at San Jose State & helped them do their annual dues collection. Good old word-of-mouth marketing, that however, started with an event where they used what they made! RealWorld by Genevieve Genevieve — Founder and CEO of Realworld stands by the old-school advice of value giving. RealWorld is an app that helps GenZ navigate adulthood. So, before launching their direct-to-consumer platform, they had an educational course that they sold to college career centers and students. They already had a pipeline of adults who turned to Realworld for their adulting challenges. From there, she gained her first 100 followers. Saner dot ai by Austin Austin got 100 users from Reddit for his startup Saner.ai. Reddit hates advertising, and so his tips to market your startup on Reddit is to Write value-driven posts on your niche. Instead of writing posts, find posts where people are looking for solutions DM people facing problems that your SaaS solves. But instead of selling, ask about their problem to see if your product is a good fit Heartfelt posts about why you built it, aren’t gonna cut it To find posts and people, search Reddit with relevant keywords and join all the subreddits A Stock Portfolio Newsletter A financial investor got his first 100 paid newsletter subscribers for his stock portfolio newsletter. His tips : Don’t reinvent the wheel. Work what’s already working. He saw a company making $500M+ from stock picking newsletter, so decided to try that. Find the gaps in “already working” and leverage them. That newsletter did not have portfolios of advisors writing them. That was his USP. He added his own portfolio to his newsletter. Now to 100 users, he partnered with a guy running an investing website and getting good traffic. That guy got a cut of his revenue, in exchange. That one simple step got him to 100 users. Hypefury by Yannick and Samy Yannick and Samy from Hypefury, Twitter and Social Media Automation tool got their first beta testers and users from a paid community. They launched Hypefury there and asked if someone wanted to try it. A couple of people tried it and gave feedback. Samy conducted user interviews and product demos for them, And shared the reviews on Twitter. That alone, along with word-of-mouth marketing on Twitter got them their first 100 users. To conclude: Don’t reinvent the wheel, try what’s working. Find the gaps in what’s working, and leverage that. Instead of thinking about millions of customers, think about the first 10. Then first 100. Leverage what you have. Get the first 10 customers, then talk about this to get the next 100. Use your app. Find ways, events, and opportunities to use your app in front of people. And get them to use it. Write content not only for SEO but also to help people. It won’t work tomorrow, but it will work for years after it picks up. Leverage other sources of traffic by partnering up! Do things that don’t scale. I’m also doing SaaS marketing deep dives over 30 pieces of content. I'm posting here for the first time, so I'm not sure if it will stay or not, sorry if it doesn't. I've helped a SaaS grow from $19K to $100K MRR as a marketer in last 2 years, and now I wanna dive deep. Cheers! (1/30)

#reddit #studied #founders

Seeking advice from every type of business owner - if you have a moment & an opinion please chime in.

0

1

Organic_Crab7397•This week

Seeking advice from every type of business owner - if you have a moment & an opinion please chime in.

Hello everyone. I haven't started selling yet and wanted to get some insight from the community I'm trying to serve (that makes the most sense to me). So over the past couple months I've gotten into AI & Automation. I got a HighLevel account and went to town learning new things. I learned how to make automations and workflows that make running a business easier (my dad has been letting me use his concrete business as a guinea pig). I also learned how to build and train AI Chat Assistants. I want to start a service based business that uses AI & workflows to automate some of the customer service tasks & lead generation for business. What I'm seeking advice about are as follows: NICHE SELECTION: Part of me thinks I shouldn't niche down in the beginning and just take whoever comes and niche down once I find an industry I'm comfortable with. Another side thinks I should choose one. What is your opinion on niche selection in the beginning? PRICING: I know that pricing largely depends on the value I bring to the client, but I've seen people doing the same or similar things as I want to do and charging vastly different prices. From $300- $2,000. While I think these solutions could absolutely help companies get and retain new business and reduce some of the workload of their staff -- I'm not comfortable charging a high price until I've got enough experience and data to justify that.  THESE ARE THE SERVICES I'M THINKING OF OFFERING: Customer Service Chat Assistant. This will be on the website as a "Live Chat". It also connects to Facebook Messenger & Google Business Chat. I'd train the chat assistant on everything related to the company; pertinent info (NAP, company mission, industry background), contact info, services / products / pricing, FAQs, current specials &/or discount codes (this can be changed monthly), how to handle upset clients, etc. It can also connect to a calendar like Google or Calendly so customers can make an appointment or schedule a call directly from the conversation. Missed Call Follow Up. If you're familiar with the platform HighLevel it's commonly called "Missed Call Text Back". The idea is that when a call is missed a text message is automatically fired to the prospect's phone saying something along the lines of "Hey this is \\\\\\ from \\\\\\\_. How can I help you?" and the business owner is alerted to the missed call via text notification. People have said they see a lot of success for their clients with this alone due to the instant follow up. I see a lot of people charging $300 /m. for this. My issues with this are: 1). The text fires automatically when the call is missed, but if the business owner isn't available to actually follow up and keep texting after the customer texts back, they will look inconsistent and bothersome. 2). Without context a prospect may wonder why you didn't answer when they called, but texted them instead. So my answer to these problems are #3. SMS Answering Service. It is essentially taking 2 + 1 and combining them. The missed call text goes out to the prospect, but with context on why they're being texted (because no one is available to take the call at the moment) and IF the prospect responds, a Customer Service Chat Assistant will take over the conversation with the goal of answering their questions and either getting them on the phone with the company via a call back OR helping them schedule an appointment. This offers a more consistent solution than just a text to the business owner / team & the prospect is contacted and helped (hopefully) before they have a chance to start calling a competitor. Lead Nurture / Lead Qualifying Sales Funnel. This one is more than just AI & automation. It's a full funnel. It can be for either Facebook or Google. The process is AD -> Landing Page -> AI Text Message Convo -> Booking/Schedule Call/ Appointment. Typically the ad will offer a lead magnet which they will claim on the LP by giving their information. After the form is submitted, they get a text message and begin a conversation with the AI. It can be trained to just walk them through a booking process, nurture a sale by answering questions and handling objections or to qualify leads. Lead qualification via text works well if you want to weed out who is serious versus who is curious. To be clear; I'd be making the ad, landing page & training the AI -- all parts of the funnel. For whichever service a few things are universal: \- All conversations; no matter what platform they're had on, all go to one inbox which is pretty helpful to see them all in one place. \- When scheduling / booking these can also collect payment. \- Tags can be added to keep track of how they came into the business and where they are in a sales pipeline. There are a lot of fun things I can do with these automations and I'm excited about learning more everyday. I'd really like to know what you think these services could be worth to a business. If you do reply please tell me what type of business you're in so I have an idea of what industries I should be looking towards. Thank you for any response I get as I know this was a long read! SN: I currently do digital marketing & web design as a freelancer.

#reddit #seeking #advice

Month 2 of building my startup after being laid off - $200 in revenue and 4 (actual) paying customers

0

1

WhosAfraidOf_138•This week

Month 2 of building my startup after being laid off - $200 in revenue and 4 (actual) paying customers

In September 2024, I got laid off from my Silicon Valley job. It fucking sucked. I took a day to be sad, then got to work - I'm not one to wallow, I prefer action. Updated my resume, hit up my network, started interviewing. During this time, I had a realization - I'm tired of depending on a single income stream. I needed to diversify. Then it hit me: I literally work with RAG (retrieval augmented generation) in AI. Why not use this knowledge to help small businesses reduce their customer service load and boost sales? One month later, Answer HQ 0.5 (the MVP) was in the hands of our first users (shoutout to these alpha testers - their feedback shaped everything). By month 2, Answer HQ 1.0 launched with four paying customers, and growing. You're probably thinking - great, another chatbot. Yes, Answer HQ is a chatbot at its core. But here's the difference: it actually works. Our paying customers are seeing real results in reducing support load, plus it has something unique - it actively drives sales by turning customer questions into conversions. How? The AI doesn't just answer questions, it naturally recommends relevant products and content (blogs, social media, etc). Since I'm targeting small business owners (who usually aren't tech wizards) and early startups, Answer HQ had to be dead simple to set up. Here's my onboarding process - just 4 steps. I've checked out competitors like Intercom and Crisp, and I can say this: if my non-tech fiancée can set up an assistant on her blog in minutes, anyone can. Key learnings so far: Building in public is powerful. I shared my journey on Threads and X, and the support for a solo founder has been amazing. AI dev tools (Cursor, Claude Sonnet 3.5) have made MVP development incredibly accessible. You can get a working prototype frontend ready in days. I don't see how traditional no-code tools can survive in this age. But.. for a production-ready product? You still need dev skills and background. Example: I use Redis for super-fast loading of configs and themes. An AI won't suggest this optimization unless you know to ask for it. Another example: Cursor + Sonnet 3.5 struggles with code bases with many files and dependencies. It will change things you don't want it to change. Unless you can read code + understand it + know what needs to be changed and not changed, you'll easily run into upper limits of what prompting alone can do. I never mention "artificial intelligence" "AI" "machine learning" or any of these buzzwords once in my copy in my landing page, docs, product, etc. There is no point. Your customers do not care that something has AI in it. AI is not the product. Solving their pain points and problems is the product. AI is simply a tool of many tools like databases, APIs, caching, system design, etc. Early on, I personally onboarded every user through video calls. Time-consuming? Yes. But it helped me deeply understand their pain points and needs. I wasn't selling tech - I was showing them solutions to their problems. Tech stack: NextJS/React/Tailwind/shadcn frontend, Python FastAPI backend. Using Supabase Postgres, Upstash Redis, and Pinecone for different data needs. Hosted on Vercel and Render.com. Customer growth: Started with one alpha tester who saw such great results (especially in driving e-commerce sales) that he insisted on paying for a full year to keep me motivated. This led to two monthly customers, then a fourth annual customer after I raised prices. My advisor actually pushed me to raise prices again, saying I was undercharging for the value provided. I have settled on my final pricing now. I am learning so much. Traditionally, I have a software development and product management background. I am weak in sales and marketing. Building that app, designing the architecture, talking to customers, etc, these are all my strong suits. I enjoy doing it too. But now I need to improve on my ability to market the startup and really start learning things like SEO, content marketing, cold outreach, etc. I enjoying learning new skills. Happy to answer any questions about the journey so far!

#reddit #month #building

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

0

0.667

GDbuildsGD•This 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.

#reddit #spent #months

Share Your Expertise: AI, Automation, and Efficient Organizational Tools, Strategies and Routines!

0

ferreiracarcara•This week

Share Your Expertise: AI, Automation, and Efficient Organizational Tools, Strategies and Routines!

Hello everyone, As we navigate through the advancements in AI and automation, it's clear that these technologies are reshaping the way we approach work and business management. To stay ahead, sharing our collective knowledge on these subjects is crucial. I'm inviting this community to share insights and experiences with AI tools, automation strategies, and especially, innovative organizational approaches you've found effective. From automating mundane tasks to optimizing digital marketing strategies, every piece of wisdom is valuable. Here’s what we’re specifically interested in: Automated Workflows: What are your strategies for creating automated workflows that enhance productivity and efficiency? Visual Organization: How do you utilize mind maps and other visual tools to organize thoughts and projects efficiently? Canvas Maps: Have you implemented CANVAS Maps in customer interaction, ideation, strategy development, or action planning? How has it improved your processes? AI in Marketing: How has AI helped you optimize your digital marketing strategies and data analysis? What tools or methodologies have you found most effective? This thread aims to be a resource for all of us to learn from each other's successes and innovations. Whether it’s a simple tip or a comprehensive strategy, your input can significantly impact someone’s approach to challenges. What groundbreaking AI solutions, automation hacks, or organizational methods have you discovered that made a noticeable difference in your work or business? Share your stories and let’s empower each other to achieve greater efficiency and success. Thank you for contributing to our shared journey toward innovation and improvement!

#reddit #share #your

Struggling with Emotions Automating Jobs

0

1

PossibleMess4577•This week

AI for small business

Hello fellow small business owners, I'm curious to learn how you are incorporating artificial intelligence (AI) into your business to improve efficiency and productivity. With the rapid advancements in AI technology, I believe there are numerous opportunities for small businesses to leverage these tools to streamline operations and gain a competitive edge. I would love to hear your experiences and insights on the following: What specific AI tools or platforms are you currently using in your business? How have these AI solutions helped you streamline your workflows, reduce costs, or improve customer experience? Are there any particular areas of your business where you have found AI to be especially beneficial (e.g., marketing, customer service, inventory management)? Did you face any challenges or obstacles when implementing AI in your business, and how did you overcome them? Based on your experience, what advice would you give to other small business owners who are considering integrating AI into their operations? Thank you in advance for sharing your valuable insights. I believe this discussion will be beneficial for all small business owners looking to harness the power of AI to grow and succeed in today's competitive landscape.

#reddit #small #business

0

ferreiracarcara•This week

Share Your Expertise: AI, Automation, and Efficient Organizational Tools, Strategies and Routines!

Hello everyone, As we navigate through the advancements in AI and automation, it's clear that these technologies are reshaping the way we approach work and business management. To stay ahead, sharing our collective knowledge on these subjects is crucial. I'm inviting this community to share insights and experiences with AI tools, automation strategies, and especially, innovative organizational approaches you've found effective. From automating mundane tasks to optimizing digital marketing strategies, every piece of wisdom is valuable. Here’s what we’re specifically interested in: Automated Workflows: What are your strategies for creating automated workflows that enhance productivity and efficiency? Visual Organization: How do you utilize mind maps and other visual tools to organize thoughts and projects efficiently? Canvas Maps: Have you implemented CANVAS Maps in customer interaction, ideation, strategy development, or action planning? How has it improved your processes? AI in Marketing: How has AI helped you optimize your digital marketing strategies and data analysis? What tools or methodologies have you found most effective? This thread aims to be a resource for all of us to learn from each other's successes and innovations. Whether it’s a simple tip or a comprehensive strategy, your input can significantly impact someone’s approach to challenges. What groundbreaking AI solutions, automation hacks, or organizational methods have you discovered that made a noticeable difference in your work or business? Share your stories and let’s empower each other to achieve greater efficiency and success. Thank you for contributing to our shared journey toward innovation and improvement!

#reddit #share #your

Finally launching my side project: a tool to automate your tasks with AI

0

MannheimMan•This week

Finally launching my side project: a tool to automate your tasks with AI

Hey community 👋 I've been working on this side gig for a while now and finally launching it! Would appreciate if many of you that helped me throughout this would check it out and upvote at: https://www.producthunt.com/posts/coflow 🙏

#reddit #finally #launching

Heeelp - How are you using AI and automations to actually benefit you?

0

1

Round_Savings_6662•This week

Heeelp - How are you using AI and automations to actually benefit you?

Hey fellow small business owners! 👋 I have been trying to use Ai and automations to streamline my every day business tasks, but sometimes it feels like setting things up is more complicated and time consuming than the actual benefit. So here is my question - what AI tools and automations are really working for your small businesses. What tools do you swear by?How have they helped you save time or money?

#reddit #heeelp #automations

0

1

TechPrimo•This week

How I Started Learning Machine Learning

Hello, everyone. As promised, I'll write a longer post about how I entered the world of ML, hoping it will help someone shape their path. I'll include links to all the useful materials I used alongside the story, which you can use for learning. I like to call myself an AI Research Scientist who enjoys exploring new AI trends, delving deeper into understanding their background, and applying them to real products. This way, I try to connect science and entrepreneurship because I believe everything that starts as scientific research ends up "on the shelves" as a product that solves a specific user problem. I began my journey in ML in 2016 when it wasn't such a popular field. Everyone had heard of it, but few were applying it. I have several years of development experience and want to try my hand at ML. The first problem I encountered was where to start - whether to learn mathematics, statistics, or something else. That's when I came across a name and a course that completely changed my career. Let's start You guessed it. It was Professor Andrew Ng and his globally popular Machine Learning course available on Coursera (I still have the certificate, hehe). This was also my first official online course ever. Since that course no longer exists as it's been replaced by a new one, I recommend you check out: Machine Learning (Stanford CS229) Machine Learning Specialization These two courses start from the basics of ML and all the necessary calculus you need to know. Many always ask questions like whether to learn linear algebra, statistics, or probability, but you don't need to know everything in depth. This knowledge helps if you're a scientist developing a new architecture, but as an engineer, not really. You need to know some basics to understand, such as how the backpropagation algorithm works. I know that Machine Learning (Stanford CS229) is a very long and arduous course, but it's the right start if you want to be really good at ML. In my time, I filled two thick notebooks by hand while taking the course mentioned above. TensorFlow and Keras After the course, I didn't know how to apply my knowledge because I hadn't learned specifically how to code things. Then, I was looking for ways to learn how to code it. That's when I came across a popular framework called Keras, now part of TensorFlow. I started with a new course and acquiring practical knowledge: Deep Learning Specialization Deep Learning by Ian Goodfellow Machine Learning Yearning by Andrew Ng These resources above were my next step. I must admit that I learned the most from that course and from the book Deep Learning by Ian Goodfellow because I like reading books (although this one is quite difficult to read). Learn by coding To avoid just learning, I went through various GitHub repositories that I manually retyped and learned that way. It may be an old-fashioned technique, but it helped me a lot. Now, most of those repositories don't exist, so I'll share some that I found to be good: Really good Jupyter notebooks that can teach you the basics of TensorFlow Another good repo for learning TF and Keras Master the challenge After mastering the basics in terms of programming in TF/Keras, I wanted to try solving some real problems. There's no better place for that challenge than Kaggle and the popular Titanic dataset. Here, you can really find a bunch of materials and simple examples of ML applications. Here are some of my favorites: Titanic - Machine Learning from Disaster Home Credit Default Risk House Prices - Advanced Regression Techniques Two Sigma: Using News to Predict Stock Movements I then decided to further develop my career in the direction of applying ML to the stock market, first using predictions on time series and then using natural language processing. I've remained in this field until today and will defend my doctoral dissertation soon. How to deploy models To continue, before I move on to the topic of specialization, we need to address the topic of deployment. Now that we've learned how to make some basic models in Keras and how to use them, there are many ways and services, but I'll only mention what I use today. For all my ML models, whether simple regression models or complex GPT models, I use FastAPI. It's a straightforward framework, and you can quickly create API endpoints. I'll share a few older and useful tutorials for beginners: AI as an API tutorial series A step-by-step guide Productizing an ML Model with FastAPI and Cloud Run Personally, I've deployed on various cloud providers, of which I would highlight GCP and AWS because they have everything needed for model deployment, and if you know how to use them, they can be quite cheap. Chose your specialization The next step in developing my career, besides choosing finance as the primary area, was my specialization in the field of NLP. This happened in early 2020 when I started working with models based on the Transformer architecture. The first model I worked with was BERT, and the first tasks were related to classifications. My recommendations are to master the Transformer architecture well because 99% of today's LLM models are based on it. Here are some resources: The legendary paper "Attention Is All You Need" Hugging Face Course on Transformers Illustrated Guide to Transformers - Step by Step Explanation Good repository How large language models work, a visual intro to transformers After spending years using encoder-based Transformer models, I started learning GPT models. Good open-source models like Llama 2 then appear. Then, I started fine-tuning these models using the excellent Unsloth library: How to Finetune Llama-3 and Export to Ollama Fine-tune Llama 3.1 Ultra-Efficiently with Unsloth After that, I focused on studying various RAG techniques and developing Agent AI systems. This is now called AI engineering, and, as far as I can see, it has become quite popular. So I'll write more about that in another post, but here I'll leave what I consider to be the three most famous representatives, i.e., their tutorials: LangChain tutorial LangGraph tutorial CrewAI examples Here I am today Thanks to the knowledge I've generated over all these years in the field of ML, I've developed and worked on numerous projects. The most significant publicly available project is developing an agent AI system for well-being support, which I turned into a mobile application. Also, my entire doctoral dissertation is related to applying ML to the stock market in combination with the development of GPT models and reinforcement learning (more on that in a separate post). After long 6 years, I've completed my dissertation, and now I'm just waiting for its defense. I'll share everything I'm working on for the dissertation publicly on the project, and in tutorials I'm preparing to write. If you're interested in these topics, I announce that I'll soon start with activities of publishing content on Medium and a blog, but I'll share all of that here on Reddit as well. Now that I've gathered years of experience and knowledge in this field, I'd like to share it with others and help as much as possible. If you have any questions, feel free to ask them, and I'll try to answer all of them. Thank you for reading.

#reddit #started #learning

0

1

TechPrimo•This week

How I Started Learning Machine Learning

Hello, everyone. As promised, I'll write a longer post about how I entered the world of ML, hoping it will help someone shape their path. I'll include links to all the useful materials I used alongside the story, which you can use for learning. I like to call myself an AI Research Scientist who enjoys exploring new AI trends, delving deeper into understanding their background, and applying them to real products. This way, I try to connect science and entrepreneurship because I believe everything that starts as scientific research ends up "on the shelves" as a product that solves a specific user problem. I began my journey in ML in 2016 when it wasn't such a popular field. Everyone had heard of it, but few were applying it. I have several years of development experience and want to try my hand at ML. The first problem I encountered was where to start - whether to learn mathematics, statistics, or something else. That's when I came across a name and a course that completely changed my career. Let's start You guessed it. It was Professor Andrew Ng and his globally popular Machine Learning course available on Coursera (I still have the certificate, hehe). This was also my first official online course ever. Since that course no longer exists as it's been replaced by a new one, I recommend you check out: Machine Learning (Stanford CS229) Machine Learning Specialization These two courses start from the basics of ML and all the necessary calculus you need to know. Many always ask questions like whether to learn linear algebra, statistics, or probability, but you don't need to know everything in depth. This knowledge helps if you're a scientist developing a new architecture, but as an engineer, not really. You need to know some basics to understand, such as how the backpropagation algorithm works. I know that Machine Learning (Stanford CS229) is a very long and arduous course, but it's the right start if you want to be really good at ML. In my time, I filled two thick notebooks by hand while taking the course mentioned above. TensorFlow and Keras After the course, I didn't know how to apply my knowledge because I hadn't learned specifically how to code things. Then, I was looking for ways to learn how to code it. That's when I came across a popular framework called Keras, now part of TensorFlow. I started with a new course and acquiring practical knowledge: Deep Learning Specialization Deep Learning by Ian Goodfellow Machine Learning Yearning by Andrew Ng These resources above were my next step. I must admit that I learned the most from that course and from the book Deep Learning by Ian Goodfellow because I like reading books (although this one is quite difficult to read). Learn by coding To avoid just learning, I went through various GitHub repositories that I manually retyped and learned that way. It may be an old-fashioned technique, but it helped me a lot. Now, most of those repositories don't exist, so I'll share some that I found to be good: Really good Jupyter notebooks that can teach you the basics of TensorFlow Another good repo for learning TF and Keras Master the challenge After mastering the basics in terms of programming in TF/Keras, I wanted to try solving some real problems. There's no better place for that challenge than Kaggle and the popular Titanic dataset. Here, you can really find a bunch of materials and simple examples of ML applications. Here are some of my favorites: Titanic - Machine Learning from Disaster Home Credit Default Risk House Prices - Advanced Regression Techniques Two Sigma: Using News to Predict Stock Movements I then decided to further develop my career in the direction of applying ML to the stock market, first using predictions on time series and then using natural language processing. I've remained in this field until today and will defend my doctoral dissertation soon. How to deploy models To continue, before I move on to the topic of specialization, we need to address the topic of deployment. Now that we've learned how to make some basic models in Keras and how to use them, there are many ways and services, but I'll only mention what I use today. For all my ML models, whether simple regression models or complex GPT models, I use FastAPI. It's a straightforward framework, and you can quickly create API endpoints. I'll share a few older and useful tutorials for beginners: AI as an API tutorial series A step-by-step guide Productizing an ML Model with FastAPI and Cloud Run Personally, I've deployed on various cloud providers, of which I would highlight GCP and AWS because they have everything needed for model deployment, and if you know how to use them, they can be quite cheap. Chose your specialization The next step in developing my career, besides choosing finance as the primary area, was my specialization in the field of NLP. This happened in early 2020 when I started working with models based on the Transformer architecture. The first model I worked with was BERT, and the first tasks were related to classifications. My recommendations are to master the Transformer architecture well because 99% of today's LLM models are based on it. Here are some resources: The legendary paper "Attention Is All You Need" Hugging Face Course on Transformers Illustrated Guide to Transformers - Step by Step Explanation Good repository How large language models work, a visual intro to transformers After spending years using encoder-based Transformer models, I started learning GPT models. Good open-source models like Llama 2 then appear. Then, I started fine-tuning these models using the excellent Unsloth library: How to Finetune Llama-3 and Export to Ollama Fine-tune Llama 3.1 Ultra-Efficiently with Unsloth After that, I focused on studying various RAG techniques and developing Agent AI systems. This is now called AI engineering, and, as far as I can see, it has become quite popular. So I'll write more about that in another post, but here I'll leave what I consider to be the three most famous representatives, i.e., their tutorials: LangChain tutorial LangGraph tutorial CrewAI examples Here I am today Thanks to the knowledge I've generated over all these years in the field of ML, I've developed and worked on numerous projects. The most significant publicly available project is developing an agent AI system for well-being support, which I turned into a mobile application. Also, my entire doctoral dissertation is related to applying ML to the stock market in combination with the development of GPT models and reinforcement learning (more on that in a separate post). After long 6 years, I've completed my dissertation, and now I'm just waiting for its defense. I'll share everything I'm working on for the dissertation publicly on the project, and in tutorials I'm preparing to write. If you're interested in these topics, I announce that I'll soon start with activities of publishing content on Medium and a blog, but I'll share all of that here on Reddit as well. Now that I've gathered years of experience and knowledge in this field, I'd like to share it with others and help as much as possible. If you have any questions, feel free to ask them, and I'll try to answer all of them. Thank you for reading.

#reddit #started #learning

How to Effectively Read Research Papers Like RCNN, Fast RCNN, etc.?

0

1

Intrepid-Purpose2151•This week

How to Effectively Read Research Papers Like RCNN, Fast RCNN, etc.?

Hey everyone, I'm starting to read research papers on object detection, beginning with RCNN, Fast RCNN, and others. Since these papers are packed with technical details, I want to make sure I'm reading them the right way and extracting the most useful insights. For those experienced in reading ML/AI research papers, what’s the best approach? Specifically: What key things should I focus on while reading these papers!? Any strategies to understand the important contributions of a paper? I’d appreciate any tips or resources that helped you when you started! Thanks in advance.

#reddit #effectively #read

0

1

Will_fever•This week

I recreated an AI phone calling agent that increased booked calls by 30% for a plumbing business in 30 days

AI has always intrigued me, especially when it comes to automating repetitive tasks and streamlining business operations. Recently, I found a compelling case study about a voice agent that significantly enhanced customer service and lead capture for a plumbing company. Motivated by the potential of this technology, I decided to build a similar system to see how it could be adapted for other industries. I’ve added the case study below along with a number to the demo voice agent I created to see if this is something people would really be interested in. AI technology is advancing rapidly, and I’m excited to dive deeper into this space. Case Study A family-owned plumbing business was facing challenges managing a high volume of customer calls. They were missing potential leads, particularly during after-hours and weekends, which meant lost revenue opportunities. Hiring a dedicated call support team was considered but deemed too expensive and hard to scale. Solution To solve these issues, the company deployed an AI-powered voice agent capable of handling calls autonomously. The system collected essential customer information, identified service needs, and sent real-time alerts to service technicians via SMS. It also had the ability to transfer calls to human agents if necessary, ensuring a seamless experience for customers. Impact The AI voice agent quickly proved its worth by streamlining call management and improving response times. With the AI handling routine inquiries and initial call filtering, the plumbing business saw a noticeable improvement in how quickly they could respond to customer needs. Details The AI-powered voice agent included several advanced features designed to optimize customer service: Answer Calls Anytime: Ensured every call received a friendly and professional response, regardless of the time of day. Spot Emergencies Fast: Quickly identified high-priority issues that required urgent attention. Collect Important Info: Accurately recorded critical customer details to facilitate seamless follow-ups and service scheduling. Send Alerts Right Away: Immediately notified service technicians about emergencies, enabling faster response times. Live Transfers: Live call transfer options when human assistance was needed. Results The AI-powered voice agent delivered measurable improvements across key performance metrics: 100% Call Answer Rate: No missed calls ensured that every customer inquiry was addressed promptly. 5-minute Emergency Response Time: The average response time for urgent calls was reduced significantly. 30% Increase in Lead Capture: The business saw more qualified leads, improving their chances of conversion. 25% Improvement in Resource Efficiency: Better allocation of resources allowed the team to focus on high-priority tasks. By implementing the AI-powered voice agent, the plumbing business enhanced its ability to capture more leads and provide better service to its customers. The improved call handling efficiency helped reduce missed opportunities and boosted overall customer satisfaction. Here’s the number to the demo agent I created: +1 (210) 405-0982 I’d love to hear some honest thoughts on it and which industries you think could benefit the most from this technology.

#reddit #recreated #phone

0

1

AlexSnakeKing•This week

[D] Is the Covid-19 crisis the rock on which the ML hype wave finally crashes?

People have been predicting the end of the ML Hype for a while, but it didn't seem to go away. Andrew Ng's "A.I. is the new electricity" statement looked like it was true, and the number of ML related stuff on resumes, job descriptions and software requirements, not to mention startups, seemed to keep increasing and increasing, and increasing.... Then came a virus, with a billion years of optimization and search efficiency baked into its RNA. Some considerations: Despite all the hype, production grade ML was still a challenge for most companies outside of the big tech shops and some talented startups. With the Covid-19 induced economic meltdown, most companies don't have the money or the resources to fund the projects required to take ML from PoC/Jupyter Notebook status to value generating production applications. Most of the startups that are building ML productionizing tools and platforms will run out of funds, clients, or both. Moreover, the current economic meltdown makes most historical data on business KPIs, Customer behavior, time series forecasting, etc...is no longer useful as training data. The only data sets that are still useful are those for "hard-core" ML problems like computer vision and NLP, for which completely automated APIs have been already developed and Auto-ML works pretty well, so no real ML talent is needed in deploying them. All of this tells me that Q2 2020 will mark the end of the ML and Deep Learning hype, and besides a likely multi-year economic depression in the U.S., we are also headed into another AI winter. I'm not happy about the ML hype dying, it has helped me a lot in my career, and I really really love Deep Learning from a purely conceptual point of view. But one needs to be realistic in such a job market, should we all start reframing our skill sets and our resumes? I'm kind of hoping somebody will prove my above reasoning wrong.

#reddit #covid-19 #crisis

DownEdit

DownEdit is a fast and powerful program for downloading and editing videos from top platforms like TikTok, Douyin, and Kuaishou. Effortlessly grab videos from user profiles, make bulk edits, throughout the entire directory with just one click. Plus, our advanced Chat & AI features let you download, edit, and generate videos, images, and sounds in bulk. Exciting new features are coming soon—stay tuned! ✨ Preview 🔥 Current Features Edit Video: Enhance videos with various functions designed to streamline editing tasks across entire directories. Edit Photo: Quickly enhance images in bulk with various functions, including AI-powered functions, Edit Sound: Improve audio in bulk using powerful functions, including cutting-edge AI-powered tools. Download all videos: Retrieve videos from users (TikTok, Kuaishou, Douyin, etc.) without watermarks. Bulk AI Generator: Generate images and videos in bulk using powerful generative AI. AI Editor: Enhance your content effortlessly with using AI editor designed for images, sounds and videos. 🌐 Service | Website| Provider| Single Video | User's Videos | Stream | Access | Status | | --- | --- | --- | --- | --- | --- | --- | | tiktok.com | None | ✔️ | ✔️ | ❌ | API (Cookie) | !Inactive | | douyin.com | None | ✔️ | ✔️ | ❌ | API (Cookie) | !Inactive | | kuaishou.com | None | ✔️ | ✔️ | ❌ | Login Required (Cookie) | !Active | | youtube.com | None | ✔️ | ✔️ | ❌ | (Public/Private) | !Active | 🤖 AI Cloud | Type | Model | Provider| Minimal | Bulk | Access | Status | | --- | --- | --- | --- | --- | --- | --- | | Image Generation | None | | None | ✔️ | API (Public) | !Active | | Video Generation | None | | None | ✔️ | | !Inactive | | Sound Generation | None | | None | ✔️ | | !Inactive | Local | Type | Model | Provider| Minimal | Bulk | Access | Status | | --- | --- | --- | --- | --- | --- | --- | | Image Generation | None | | None | ✔️ | | !Inactive | | Video Generation | None | | None | ✔️ | | !Inactive | | Sound Generation | None | | None | ✔️ | | !Inactive | 🚀 Usage Edit Video - Simply copy and paste (right click) whatever directory location you would like to process. Tutorial !EditVideoAdobeExpress Change it according to your desired video speed. Input your music file location Download douyin videos - Download all video from user by input user link. Tutorial Download tiktok videos - Download all video from user by input username with @. Tutorial Download kuaishou videos - Remember to input your own Cookie. Otherwise it won't work. Tutorial Step 1. Right click and select on Inspect element. Step 2. Copy your Cookie browser. Step 3. Copy user ID you want to download. Tips: If you still getting error, try changing your Browser, use Incognito/Private mode and reset your Internet/IP. Edit Photo - Simply copy and paste (right click) whatever directory location you would like to process. Tutorial Remove Background AI 🔎 Requirements Python [!NOTE] Version must be between 3.8 and 3.12. ⚙ Installation Step 1. Download and install python on your pc. Step 2. libraries installation You have three options to install the required libraries: Option 1: Manual Installation Option 2: Automatic installation & virtual environments Option 3: Terminal & virtual environments Step 3. Run the script For Regular Use: You can also download the application and use it on your PC without installing python. Windows: Download macOS: None [!TIP] Fix Terminal Font Issues Install the Microsoft Cascadia font on your computer if your terminal does not support the font, which is resulting in program error. 🔨 Module The following dependencies are required for the project: List Pystyle Requests Inquirer Colorama Moviepy Rich Playwright Rembg WMI Psutil Httpx Aiofiles Author 👤 Sokun Heng Github: @SokunHeng Show your support Please ⭐️ this repository if this project helped you! 📚 Reference Documentation 📝 License Copyright © 2022 SokunHeng.

Liam Evans•Jun 23, 2023

Sign Your First AI Agency Client With This ChatBot Strategy

✅ Automate your business's sales and marketing in 30 days with our AI Growth System (+ Access our resources and guides): https://www.unorthodox.digital/start If you're new here, my name is Liam, and for the past 8 years, I've been building businesses online. For the past 3 years, we've helped 100's of our clients do the same with www.unorthodox.digital where we build them complete sales and marketing systems powered by AI and automation, giving them back their time whilst helping them grow their businesses fast. We use GHL the run our business and recommend you do the same: https://www.gohighlevel.com/?fp_ref=unorthodox46