Alone

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

youtube

0.351

0.5

Cosmic Hippo•Mar 17, 2025

Alone at the Office - Coding Music for Maximum Productivity

The office is quiet, the world outside fades away, and it's just you, your screen, and the flow of deep work. This chillstep mix is designed to help you lock in and maximize productivity, blending atmospheric synths, smooth basslines, and steady rhythms to keep distractions at bay. Whether you're coding, studying, designing, or working late into the night, this soundtrack creates the perfect focus-driven environment. Let the music guide your concentration and fuel your creativity. If you enjoy this mix, subscribe for more deep-focus playlists. Disclaimer: This music has been created with the help of AI tools. Tracklist 0:00 Silent Workspace 3:13 Midnight Overtime 6:12 Dim Lights 8:54 Late Night Grind 11:50 Deadline Mode 14:57 Office Echoes 16:53 After-Work Silence 19:09 Corporate Ghost Town 20:56 Cubicle Zen 24:47 Final Stretch 28:50 Lights On, World Off 32:20 One More Line of Code 35:59 Overtime Flow 39:47 Quiet Hustle 43:49 The Empty Office 45:45 Glass Towers 48:38 Night Shift 50:44 Productivity After Dark 53:00 Silent Hours 56:16 Work Late, Dream Big #focusmusic #deepwork #codingbeats #chillstep #productivitymusic #loficoding #studybeats #workmusic #synthwave #concentrationmusic #alone #creativeflow #deepfocus

#focusmusic#deepwork#codingbeats

coursera

0.501

0.257

IBM•This week

Building AI Powered Chatbots Without Programming

Chatbots can save businesses up to 30% on customer support costs alone (Shopify), and AI developers with strong chatbot skills are in high demand! This Building AI Powered Chatbots Without Programming course gives aspiring AI application developers and engineers the skills businesses need to build chatbots in just 6 weeks. No programming experience required!

#coursera#building#powered

reddit

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

reddit

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

reddit

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

reddit

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

reddit

0

1

colbyn-wadman•This week

Content aggregation that acts as a middleman for content discovery via third-party marketplace & revenue sharing (i will not promote but I'm looking for fellow researchers)

High level I’m considering a content aggregation business model, but one that acts as an open marketplace where third party devs and where world class data scientists compete to build the best recommenders for different use cases. (E.g. the incentives can be ad revenue sharing or subscription based for niche professional markets.) The idea is to facilitate more bottom up innovation from third party data scientists. The platform itself just acts as the middleman. (Also something that strips out original ads and makes it easy to skip paid sponsorship sections would be great.)  I’ve seen startups building web crawlers and content aggregation systems for other AI startups. My proposal is better in the sense that third party devs are instead responsible for implementing whatever questionable hacks are necessarily to scrape platforms that don’t necessarily want to be scraped.  Personally, I’m more concerned about getting the right information than ever before, to this end I can’t rely on platform specific recommenders. The solution is more bottom up innovation in content promotion. More generally, if you’re also concerned about consuming game changing information that’s too easily missed: we need a platform that incentivizes bottom up innovation of content promotion. What we need is a platform that functions like a marketplace where third party devs and where world class data scientists compete to build the best recommenders for different use cases. Here’s some elevator pitches I’m considering:  Did you know that the magic behind YouTube is its recommendation engine? Now, imagine an open platform where independent engines compete to deliver the most personalized content feed—from news to local events—directly to you. Interested in rethinking how we find content? “In today’s fragmented digital landscape, a single platform no longer holds sway over content discovery. The Network Effect is dead: audiences are more mobile than ever; and big tech killed it. In such a fragmented landscape we’re building a bottom-up, decentralized marketplace for recommendation engines—a solution that taps into diverse revenue streams through subscriptions, ad revenue, and affiliate partnerships. Invest in the future of personalized content aggregation.” “Are you a developer passionate about algorithms and content discovery? Our open marketplace lets you build and monetize your own recommendation engine, competing to deliver the most engaging, personalized feeds. Join a revolution where your innovation can directly shape how the world finds content.” “Are you tired of being told what to watch or read by one mysterious algorithm? Imagine taking control—choosing from a marketplace of smart recommendation engines that curate content just for you. It’s a revolution in content discovery where you hold the power.” (As a Utahn this one is interesting because even mormons are talking about the dangers of “doom scrolling” though it’s seldom discussed in society at large.) As far as simple hooks I’m considering:  One platform to rule them all and in the darkness bind them.  Choose how you discover—content recommenders that work for you.  The area where recommender engines battle to win your feed. Request I would love to start prototyping this idea and see what else I can uncover from such preliminary research. But I want to get a couple other likeminded individuals onboard.  I'm the best when it comes to iOS/macOS development, but there's tons of backend work that needs to be done which I wouldn’t have the time for if i'm focused on the native clients. Who am I 'ideally' looking for?  I’ve heard of weird stats to the effect that if you scale up a population to billions of people, the number of life overlaps starts skyrocketing. Not just physical lookalikes, but people with eerily similar life paths, personalities, habits, and even thoughts — without ever knowing each other. Where are my clones? Such is whom I’m looking for in an ideal world.  Take a hunch  People nowadays have no concept of going out on a limb, taking a ‘hunch’, and backing their instincts. Everything has to be calculated, proven, and guaranteed before they make a move. In contrast consider the success of the Chinese DeepSeek project: According to Asianometry’s YouTube video on DeepSeek, their “memory-saving multi-head latent architecture” (whatever that means, just quoting the name) came about from a researchers ‘hunch’, which the company bet big on and the result was drastically improved performance on low end hardware…  Here in the west the idea of betting on a hunch is inconceivable. We have no balls to chase long term insights. My own instincts when it comes to software is such because I’ve wasted too much of my life on small scale projects. All I’m trying to do is attempt a more scaled up experiment based on some hunches with me and a few other likeminded individuals.  Just as the early oil prospectors didn’t have precise maps—just intuition and test drills. They had to drill, analyze the pressure, and adjust. The best oil fields weren’t found by foresight alone, but by adaptive exploration. The startup space itself is liken to the first prospectors who got the gold nuggets lying in the riverbed. In such an environment moving first has its advantages but nowadays I wish I could have all those shitty ‘engineers’ sent to their maker.  Today the reality is such that you’ve got to dig deep—where vast stores of wealth can be found—or go home, and those who dig into the depths cannot use mere forethought, for what lies beneath cannot be seen by the mind’s eye.  I will not promote but I'm looking for fellow research oriented minds.

#reddit#content#aggregation

reddit

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

reddit

0

1

Few_Incident4781•This week

AI will obsolete most young vertical SAAS startups, I will not promote

This is an unpopular opinion, but living in New York City and working with a ton of vertical SaaS startups, meaning basically database wrapper startups that engineer workflows for specific industries and specific users, what they built was at one point in time kind of innovative, or their edge was the fact that they built these like very specific workflows. And so a lot of venture capital and seed funding has gone into these types of startups. But with AI, those database wrapper startups are basically obsolete. I personally feel like all of these companies are going to have to shift like quickly to AI or watch all of their edge and what value they bring to the table absolutely evaporate. It's something that I feel like it's not currently being priced in and no one really knows how to price, but it's going to be really interesting to watch as more software becomes generated and workflows get generated. I’m not saying these companies are worth nothing, but their products need to be completely redone EDIT: for people not understanding: The UX is completely different from traditional vertical saas. Also in real world scenarios, AI does not call the same APIs as the front end. The data handling and validation is different. It’s 50% rebuild. Then add in the technical debt, the fact that they might need a different tech stack to build agents correctly, different experience in their engineers. the power struggles that occur inside companies that need a huge change like this could tank the whole thing alone. It can be done, but these companies are vulnerable. The edge they have is working with existing customers to get it right. But they basically blew millions on a tech implementation that’s not as relevant going forwards. Investors maybe better served putting money into a fresh cap table

#reddit#will#obsolete

reddit

0

1

Cliznitch•This week

We're building a tool to help you find grants. Would you use it?

Hi there! In Europe alone, we spend almost € 400 billion annually on subsidies to support businesses. We estimate there are around 18,000 different grants available to entrepreneurs. Via the EU of course, but also via cities, national governments and literally countless public bodies all offering different kinds of support. I've been working for the government for about 10 years now, and I've noticed how difficult it can be for smaller companies to identify the right subsidy opportunities. Because they don't know they exist (and thus don't know where to find them), or because the eligibility criteria are just overwhelming, for example. Together with my co-founder we're building a tool to make it easier to find the grants that best align with your goals (fingers crossed!). Basically we scan all subsidies in Europe, use AI to analyze the goals and criteria and match companies with those subsidies that work best for them. So my question for you guys: do you look for subsidies or grants at all? And would such a tool be helpful for you? And if so, what kind of features would be most helpful for you? Really appreciate any thoughts from your side! Also if you think the idea is just rubbish :) Jesse

#reddit#we're#building

reddit

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

reddit

0

1

Altruistic-Flan-8222•This week

Looking for a Marketing Partner for an Innovative AI Mobile App [i will not promote]

Hello everyone! I'm a software engineer and AI developer working on something great in the mobile AI space. If you have been following the trends on TikTok and similar platforms, you have probably noticed the explosion of AI apps (like Rizz AI and similar) that follow the simple "scan → solve" concept. These apps have been massively successful because they solve specific problems with minimal user friction. Here's what makes my project different: I have identified an unique market where there is currently zero competition for this app idea that I'm creating and the potential user base is massive - we are talking about 200M+ potential users in the US alone (60% of the US population could use this app). Even capturing just 0.05% of this market could generate significant revenue, considering similar apps typically charge $4-6 per user. What I'm looking for: A marketing partner (preferably US-based or someone familiar with the US market/audience) who can help grow this app. Initially, it requires about 30–60 minutes per day for content creation and posting. No experience is required. If you don't have marketing experience, don't worry. In today's marketing, passion is often more important than skills (and a bit of luck, haha). What I'm offering: For now, it's a revenue share partnership. I have invested my savings into the development of the app and the necessary equipment and I'm offering a revenue share until we generate enough profit for paid positions. Once we gain traction, the goal is to transition this into a part-time or full-time role. If you have zero creativity skills, I can provide you with my automated content generation tool to assist with marketing. It is basically a script that generates the type of content that gets the most views on other AI apps promoted on social media platforms. This is also a long-term partnership, if we achieve some results but not good enough with one app, we can try a new niche or just continue on this one. About the project: The app is almost complete and will likely launch in mid-February. It is a self-funded venture, meaning all profits will be reinvested into growth, including ads, revenue sharing and potentially useful tools to improve marketing. Also, the app is unique, I made a deep research and there is no similar app in this niche and it is very easy to promote. Overall, it follows a simple and effective business model with a clear monetization strategy. If you're interested in being part of something with genuine growth potential and want to learn more, DM me. We can discuss details on Reddit, Discord, LinkedIn, anything you like. The app launches in mid-February so I'm looking to bring someone on board soon to help out. Note: I will share specific details about the niche and app functionality in private messages to protect the idea before launch.

#reddit#looking#marketing

reddit

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

reddit

0

1

consultali•This week

Serious B2B businesses will not try to create a solution using AI - This is why. [i will not promote]

After architecting and developing multiple B2B SaaS platforms and resolving countless challenges, here's why I don't think a proper B2B solution can be developed using AI. You must have senior tech-folks in your teams - even if you choose to leverage AI for expediting some code generation. This isn't theory - this is battle-tested reality. You can use this as a template if you're building one. Core Considerations: Multi-Tenancy Foundation (B2B) Proper tenant isolation at every layer (data, compute, networking) Flexible deployment models (pooled vs. silo) based on customer tier Tenant-aware everything (logging, metrics, tracing) Identity & Security (B2B/Standalone) Enterprise-grade authentication, often with SSO support Role-based access control (RBAC) at tenant level (may need dynamic policy generation for resource access) Audit trails for all system actions (specially if you're in a regulated domain) Client/Tenant Management (B2B) Self-service onboarding with admin approval workflows Automated tenant provisioning/deprovisioning Tenant-specific configurations and customizations Cross-tenant analytics and administration Operational Excellence (B2B/Standalone) Zero-downtime deployments (helps with canary releases) Tenant-isolated debugging capabilities Resource quotas and throttling by tenant tier Automated backup and disaster recovery per tenant Scalability Architecture (B2B) Independent scaling of tenant workloads Resource isolation for "noisy neighbor" prevention Tier-based performance guarantees (SLAs) Dynamic resource allocation Each of these topics can be as complicated as you can think of - depends on the solution you're building. I have seen many seasoned architects and developers struggle also because of their "single-tenant" mindset. Here are some common pitfalls to avoid (B2B/Standalone): Standalone - mindset in database design Hard-coded configurations Lack of context in logging/monitoring Insufficient tenant isolation in shared services (B2B) Missing tenant-aware cost allocation (B2B) You need people great with infrastructure as well. They need to consider: Tenant-aware routing (API Gateway or whatever you're using) Code with isolation when/if required Data storage with proper partitioning Shared services vs. dedicated services strategy There are a number of common problems I have seen people often make. Often it's because of a pressure from high above. But every architectural decision must considered in terms of the solution you're building. In many cases, security cannot be bolted on later, observability must be tenant-aware from day one, operations must scale. This is just the foundation. Your actual business logic sits ON TOP of all this. Now, would you think these can be done by AI? I'll be waiting for that day. :-)

#reddit#serious#businesses

reddit

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

reddit

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

reddit

0

1

mind4wave•This week

Should we give up?

I'm currently very demotivated because we're working on our SaaS startup since 1,5 years and we still haven't found active users, let alone a customer. We're building an AI-first tool that automates user research analysis. We've released two MVPs so far and are planning to build a third. People respond well to outreach (5-7% book a demo from those who received a first message) but then they fail to use it. We are talking with users a lot so we are aware of the problems, and we might be able to solve them if we continue building and testing. I find it hard though to solve these problems efficiently, because there are no similar established AI-first products on the market and it feels like we have to create a new UX standard. Some problems might be very hard to be solved, e.g. there are high cost of switching products for many of our potential users. Also, my time is limited, as I recently (5 months ago) became a mother. I can only work 30 hours per week. It's a competitive area we're in and our competitors have gradually developed into the same direction and it's getting harder to position ourselves. Also, GPTs might soon be able to do what we're doing - for free. I feel like AI tools are generally expected by many to be free. The price we're expecting to be able to bill is getting lower and lower and our finance plan is already looking tight. However, there are adjacent audiences which we could target as well, but none of us knows them. Is it normal as a founder to struggle so much at the beginning? I've read that it took established SaaS 2,5 years on average from founding to first revenue. We haven't founded so far so you could say we're not behind \sarcasm\ Shall we keep pushing? My tech co-founder is optimistic and thinks this is where the wheat is separated from the chaff. We're currently supported financially by a government fund so we haven't spent much private money. However, I feel like my career outlook gets worse with each day that I unsuccessfully try to raise this startup.

#reddit#should#give

reddit

0

0.4

Official-DATS•This week

Good at coding, bad at marketing. Summary

Hello. I posted a question on what to do if you are good at coding but bad at marketing four days ago, and I received so many responses and tips. The original post is here. I was really glad and excited to read comments. To return the favor to the community and add some more value, I’ve summarized all the comments I got on the original post. Here are they, with my personal comments on some of the advice I got. You’ll never believe it, but the most common advice was to learn. Really, the first and only thing you should start with if you’re bad at marketing is learning. Yet learning could be different. I highlighted 5 main areas. Educate yourself on general questions. Learn more about some basics. For example, start by finding out what the 4P’s of marketing are, and afterward, you’ll inevitably run into YouTube videos, seminars, Udemy courses, or any other resource that resonates with you on some ideas/avenues you could pursue. Read books and watch videos. There are tons of books on marketing and sales. People shared in the comments books by Dan Kennedy and “Cashvertising”, written by Drew Eric Whitman. (I’ve never heard of them, but already ordered on Amazon). For sales, the most common idea was to start with YouTube videos. For example, Alex Hormozi videos and Startup school delivered by Ycombinator videos. Check out Indie Hackers and scrutinize it for a piece of good advice from developers in the same situation. Also, there was advice to follow up and read some guy on Twitter. (Don't want to get unfairly banned from here, so won't post it) Educate yourself and hire a professional or find a co-founder to help you: Hire a seasoned marketer in this field to help you out. He will help you achieve cost-efficient scales. But it could be a real problem to find the right person. Marketing agencies are expensive. Try to look on LinkedIn or among your acquaintances. Look for professionals with credentials or extensive experience. Seek marketing referrals from startups of a similar size/industry. If you don't have those, try to bring a trusted/experienced marketer friend into the intro meetings to help assess whether the service provider knows what they are doing. Talented freelancers can often get the job done for less than hiring an entire agency. Look for a co-founder who is savvy in marketing, passionate, and ready to work hard towards mutual success. Educate and DIY Being the face of your business is way better than having faceless communication. The startup checklist is made based on the comments is next: At least have your product defined. Define your target audience. Set up the goals you want to achieve. Make domain expertise and understand the market and the direction of its development. The next stage is answering tricky questions: Have you created a business model? How do you plan to compete? What’s your unique selling point? How much do you plan to budget for marketing? Are you planning to work alone, or will you need other devs? Then you start thinking about clients… You need the exposure to truly understand the customer's pain points and build a product that they love. You need to think about how your clients would think, and you should tailor each step you take for them. Get feedback from your early users if you already have a product. Interview your potential customers to learn how they buy. This will help you narrow your choice of marketing channels. Get your product or service used by several startups and help them achieve their goals. Endorsements are very valuable marketing assets. You need a landing to validate your value proposition and start sending traffic, or you can run meta instant form campaigns... It would depend on the category of your startup. You need a benchmark of the competition's ads both in Meta and Google, blog posts, domain authority, their landing page, and average search volumes. Do affiliate marketing for your product since it's an effective strategy. Educate and use AI tools for dealing with marketing. Build an LLM-based product to automate marketing. (Sounds like an idea for a startup, right?) Learn following ChatGPT advice. In 1–3 months, you will be another updated person. Look at marketowl, an AI marketing department for startups and microbusinesses that have no budget or time to do marketing. It will automate the basic tasks your business needs, but it doesn't require your marketing expertise. Check out AI tools that are delivering very good marketing content (gocharlie, jasper, copyai). Educate yourself and run socials Start a blog or YouTube channel where you can share your expertise in coding or anything else you are good at and how your product simplifies life. Engage with your audience on social media platforms like Instagram and LinkedIn, where you can showcase your industry knowledge. Start a page on Twitter and an account on Reddit. Follow and read subreddits and pages where your potential customers are. Learn the pain from the inside. Do not simply promote, people will lose interest immediately. Start by taking focused time to create informational content, so people will eventually be naturally intrigued by what you do and want to support you when they start to “know” you. Educate your potential users about the value of your product. Create content based on what ideal customers are asking at the various stages of marketing. e.g., if they are at the beginning of the process, they may use basic language; if they are further down the process, maybe they’ll be specific. Try to get on podcasts and build as many social links as you can. In other words, don’t live in a shell! Post regularly, and eventually you’ll find sites or people that are willing to promote for you. I omitted here all personal help offers and newsletters, however you could find them in the original post. Hope that will be helpful!

#reddit#good#coding,

reddit

0

1

What_The_Hex•This week

I am considering starting a SaaS business that automates the creation of long-form SEO-optimized blog posts. Is this something you would find useful, as a business owner?

Trying to gauge the general interest level, from other entrepreneurs/business owners. The idea is, a tool that automates the process of creating long-form SEO optimized blog posts to promote your business -- perhaps creating entire batches of such posts, all from just one button click. Like if you could just describe your business, click a button, and BAM, it just outputs like an entire month's worth of absolutely fire SEO-optimized long-form blog posts? That would be super fucking convenient. Yes you can use ChatGPT for this, but the character limits make it so it can only output very short posts. Otherwise it requires first asking for an outline, then getting the different sections piecemeal and pasting it all together yourself. Still super time-consuming to do it that way. A GPT-based solution could probably automate the process I've hit upon in my own SEO blog-posting workflow -- where I output not just finished long-form blog posts, but also convert them into SEO-optimized HTML code so you can just paste it into your blog post website and have all the header tags etc set up for optimal SEO/keyword ranking purposes. Biggest counter-argument I make against this is, there are undoubtedly lots of companies already offering this. Doesn't mean I can't make money doing it. I just don't like entering super crowded marketplaces. Other main argument I have is, if I used my OpenAI account for this, there's the risk of some malicious/idiot user firing prompts that violate the OpenAI ToS and get me banned. I COULD have them input their own OpenAI API tokens, but that just adds adoption/usage barriers that would make it way harder to market/acquire initial customers. I guess I could sanitize the user inputs as a pre-processing step to block any obscene prompts or anything like that, but still, it's a risk. Let me know your thoughts on this idea. ASSUMING it worked effectively -- and made it very easy for you to just describe your business offerings / value propositions / target market(s), then get genuinely useful long-form SEO-optimized blog posts, is this something you'd be willing to pay for? If so, what dollar amount, to you, would seem reasonable? It would probably just be hosted on a website. Then you'd just copy the outputted final result for use as needed on your website. That would be the simplest way to do it. Technically it could function as like, a plugin for specific websites that maybe auto-posts them for you too -- it would be simpler, on my end, to start out doing this on a standalone website. (Might also make it easier to allow users to try it out, on first visit.) One last point -- MAYBE it would have an optional intermediate step, where it would first output the planned outline for the blog post, allowing you to pop in, quickly modify that, add your own thoughts / valuable ideas (to help make the blog post more unique, truly useful for readers, more your own) -- THEN you could finalize it and hit submit. Again, that's the workflow I've hit upon in my own semi-automated blog-posting workflow, and it's led to some pretty useful long-form content that isn't just, boring garbage, but contains lots of genuinely useful ideas that I would include in my own uniquely-created blog posts on the subject. But instead of me taking the time to write it, I just kinda toss in a few quickly typed out ideas to expand upon, and ChatGPT does the rest. Imagine that kind of optional / customizable workflow, but the rest of it is fully automated. OR you could just get the fully automated blog posts with no revisions on your part. Thanks!

#reddit#considering#starting

reddit

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. &#x200B; 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

reddit

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

reddit

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

reddit

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

reddit

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

reddit

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. &#x200B; 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

reddit

0

0.5

LeadgeniusAI•This week

The Rise of AI: Will It Signal the Demise of LinkedIn Automation as We Know It?

Have you ever received a spammy LinkedIn automation sequence that left a bad taste in your mouth? You're not alone. But what if LinkedIn automation could be used in a way that was actually useful and effective? As a busy small business owner, you don't have time to spend hours on LinkedIn every day, so automation can be a lifesaver. After trying out many LinkedIn automation tools, I realized that the biggest gap in the market was in the area of ultra-personalization. Most tools only offer basic personalization like name, job title, and location tags, but that's not enough to get the attention of busy prospects. That's where AI comes in. Imagine being able to scrape publicly available information like someone's bio, work experience, headline, education, and more, and then use AI to create an ultra-personalized outreach for each individual. This would be a game-changer for LinkedIn marketers. That's why I have built an online tool that does just that. With this tool, you'll be able to create highly personalized outreach messages that are customized for each person you're targeting. And, of course, it will be automated to save you time and effort. So what do you think? Would you be interested in using a tool like this to market your offer on LinkedIn? Let me know in the comments!

#reddit#rise#will

reddit

0

0.333

Otherwise_Soil39•This week

How do you explain, to a non-programmer why it's hard to replace programmers with AI?

to me it seems that AI is best at creative writing and absolutely dogshit at programming, it can't even get complex enough SQL no matter how much you try to correct it and feed it output. Let alone production code.. And since it's all just probability this isn't something that I see fixed in the near future. So from my perspective the last job that will be replaced is programming. But for some reason popular media has convinced everyone that programming is a dead profession that is currently being given away to robots. The best example I could come up with was saying: "It doesn't matter whether the AI says 'very tired' or 'exhausted' but in programming the equivalent would lead to either immediate issues or hidden issues in the future" other then that I made some bad attempts at explaining the scale, dependencies, legacy, and in-house services of large projects. But that did not win me the argument, because they saw a TikTok where the AI created a whole website! (generated boilerplate html) or heard that hundreds of thousands of programers are being laid off because "their 6 figure jobs are better done by AI already".

#reddit#explain,#non-programmer

reddit

0

1

SaraSavvy24•This week

My Manager Thinks ML Projects Takes 5 Minutes 🤦‍♀️

Hey, everyone! I’ve got to vent a bit because work has been something else lately. I’m a BI analyst at a bank, and I’m pretty much the only one dealing with machine learning and AI stuff. The rest of my team handles SQL and reporting—no Python, no R, no ML knowledge AT ALL. You could say I’m the only one handling data science stuff So, after I did a Python project for retail, my boss suddenly decided I’m the go-to for all things ML. Since then, I’ve been getting all the ML projects dumped on me (yay?), but here’s the kicker: my manager, who knows nothing about ML, acts like he’s some kind of expert. He keeps making suggestions that make zero sense and setting unrealistic deadlines. I swear, it’s like he read one article and thinks he’s cracked the code. And the best part? Whenever I finish a project, he’s all “we completed this” and “we came up with these insights.” Ummm, excuse me? We? I must’ve missed all those late-night coding sessions you didn’t show up for. The higher-ups know it’s my work and give me credit, but my manager just can’t help himself. Last week, he set a ridiculous deadline of 10 days for a super complex ML project. TEN DAYS! Like, does he even know that data preprocessing alone can take weeks? I’m talking about cleaning up messy datasets, handling missing values, feature engineering, and then model tuning. And that’s before even thinking about building the model! The actual model development is like the tip of the iceberg. But I just nodded and smiled because I was too exhausted to argue. 🤷‍♀️ And then, this one time, they didn’t even invite me to a meeting where they were presenting my work! The assistant manager came to me last minute, like, “Hey, can you explain these evaluation metrics to me so I can present them to the heads?” I was like, excuse me, what? Why not just invite me to the meeting to present my own work? But nooo, they wanted to play charades on me So, I gave the most complicated explanation ever, threw in all the jargon just to mess with him. He came back 10 minutes later, all flustered, and was like, “Yeah, you should probably do the presentation.” I just smiled and said, “I know… data science isn’t for everyone.” Anyway, they called me in at the last minute, and of course, I nailed it because I know my stuff. But seriously, the nerve of not including me in the first place and expecting me to swoop in like some kind of superhero. I mean, at least give me a cape if I’m going to keep saving the day! 🤦‍♀️ Honestly, I don’t know how much longer I can keep this up. I love the work, but dealing with someone who thinks they’re an ML guru when they can barely spell Python is just draining. I have built like some sort of defense mechanism to hit them with all the jargon and watch their eyes glaze over How do you deal with a manager who takes credit for your work and sets impossible deadlines? Should I keep pushing back or just let it go and keep my head down? Any advice! TL;DR: My manager thinks ML projects are plug-and-play, takes credit for my work, and expects me to clean and process data, build models, and deliver results in 10 days. How do I deal with this without snapping? #WorkDrama

#reddit#manager#thinks

reddit

0

1

Primary_Cheesecake63•This week

[Help Needed] Developing an AI to Play Mini Metro – Struggling with Data Extraction & Strategy method

Hello everyone ! First of all, please excuse my English if i do mistakes, as it is not my native language and I am not necessarily comfortable with it :) Regarding this project, I will explain my initial intention. I know very little about coding, but I enjoy it and have had some Python lessons, along with a few small personal projects for fun, mostly using YouTube tutorials. Nothing too advanced... However, now I want to take it to the next level. Since I have some familiarity with coding, I’ve wanted to work on artificial intelligence for a while. I have never coded AI myself, but I enjoy downloading existing projects (for chess, checkers, cat-and-mouse games, etc.), testing their limits, and understanding how they work. One of my favorite strategy game genres is management games, especially Mini Metro. Given its relatively simple mechanics, I assumed there would already be AI projects for it. But to my surprise, I could only find mods that add maps ! I admit that I am neither the best nor the most patient researcher, so I haven’t spent hours searching, but the apparent lack of projects for this game struck me. Maybe the community is just small ? I haven't looked deeply into it. So, I got it into my head to create my own AI. After all, everything is on the internet, and perseverance is key ! However, perseverance alone is not enough when you are not particularly experienced, so I am turning to the community to find knowledgeable people who can help me. The First Obstacle: Getting Game Data I quickly realized that the biggest challenge is that Mini Metro does not have an accessible API (at least, not one I could find). This means I cannot easily extract game data. My initial idea was to have an AI analyze the game, think about the best move, and then write out the actions to be performed, instead of coding a bot that directly manipulates the game. But first, I needed a way to retrieve and store game data. Attempt #1: Image Recognition (Failed) Since there was no API, I tried using image recognition to gather game data. Unfortunately, it was a disaster. I used mss for screenshots ,Tesseract for OCR, andNumPy to manipulate images in the HSV color space but it produced unreliable results : It detected many false positives (labeling empty spaces as stations) It failed to consistently detect numbers (scores or resources like trains and lines) Dotted bridge indicators over rivers were misinterpreted as stations While I could detect stations, lines, and moving trains, the data was chaotic and unreliable Attempt #2: Manual Data Entry (Partially Successful but Impractical) Since image recognition was unreliable, I decided to manually update the game data in real-time. I created a script that : Displays an overlay when I press Shift+R. Allows me to manually input stations, lines, and other game elements. Saves the current state when I press Shift+R again, so I can resume playing. Implements a simple resource management system (trains, lines, etc.). This works better than image recognition because I control the input, but I’m running into serious limitations : Some game mechanics are hard to implement manually (adding a station in the middle of a line, extending the correct line when two lines overlap at a station) Keeping track of station demands (the shapes passengers want to travel to) becomes overwhelming as the game progresses Updating the score in real-time is practically impossible manually, and the score is essential for training an AI (for my reward systems) My Dilemma At this point, I am unsure of how to proceed. My questions for the community : Am I going in the right direction? Should I continue improving my manual tracking system or is it a dead end? Should I have persevered with image recognition instead? Is there a better way to extract game data that I haven’t thought of? I would appreciate any guidance or ideas. Thanks in advance ! if you need more info, i have posted my codes here : https://github.com/Dmsday/mini\metro\data\analyzer (for the image detection version I'm not sure that it's the latest version aka the most "functional" version that I could do because I think I deleted it out of boredom...)

#reddit#[help#needed]

reddit

0

0.818

Michaelbetterecycle•This week

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

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

#reddit#team#made

reddit

0

1

tilopedia•This week

My Side Projects: From CEO to 4th Developer (Thanks, AI 🤖)

Hey Reddit 👋, I wanted to share a bit about some side projects I’ve been working on lately. Quick background for context: I’m the CEO of a mid-to-large-scale eCommerce company pulling in €10M+ annually in net turnover. We even built our own internal tracking software that’s now a SaaS (in early review stages on Shopify), competing with platforms like Lifetimely and TrueROAS. But! That’s not really the point of this post — there’s another journey I’ve been on that I’m super excited to share (and maybe get your feedback on!). AI Transformed My Role (and My Ideas List) I’m not a developer by trade — never properly learned how to code, and to be honest, I don’t intend to. But, I’ve always been the kind of guy who jots down ideas in a notes app and dreams about execution. My dev team calls me their “4th developer” (they’re a team of three) because I have solid theoretical knowledge and can kinda read code. And then AI happened. 🛠️ It basically turned my random ideas app into an MVP generation machine. I thought it’d be fun to share one of the apps I’m especially proud of. I am also planning to build this in public and therefore I am planning to post my progress on X and every project will have /stats page where live stats of the app will be available. Tackling My Task Management Problem 🚀 I’ve sucked at task management for YEARS, I still do! I’ve tried literally everything — Sheets, Todoist, Asana, ClickUp, Notion — you name it. I’d start… and then quit after a few weeks - always. What I struggle with the most is delegating tasks. As a CEO, I delegate a ton, and it’s super hard to track everything I’ve handed off to the team. Take this example: A few days ago, I emailed an employee about checking potential collaboration opportunities with a courier company. Just one of 10s of tasks like this I delegate daily. Suddenly, I thought: “Wouldn’t it be AMAZING if just typing out this email automatically created a task for me to track?” 💡 So… I jumped in. With the power of AI and a few intense days of work, I built a task manager that does just that. But of course, I couldn’t stop there. Research & Leveling It Up 📈 I looked at similar tools like TickTick and Todoist, scraped their G2 reviews (totally legally, promise! 😅), and ran them through AI for a deep SWOT analysis. I wanted to understand what their users liked/didn’t like and what gaps my app could fill. Some of the features people said they were missing didn’t align with the vision for my app (keeping it simple and personal), but I found some gold nuggets: Integration with calendars (Google) Reminders Customizable UX (themes) So, I started implementing what made sense and am keeping others on the roadmap for the future. And I’ve even built for that to, it still doesn’t have a name, however the point is you select on how many reviews of a specific app you want to make a SWOT analysis on and it will do it for you. Example for Todoist in comments. But more on that, some other time, maybe other post ... Key Features So Far: Here’s what’s live right now: ✅ Email to Task: Add an email as to, cc, or bcc — and it automatically creates a task with context, due dates, labels, etc. ✅ WhatsApp Reminders: Get nudged to handle your tasks via WhatsApp. ✅ WhatsApp to Task: Send a message like /task buy groceries — bam, it’s added with full context etc.. ✅ Chrome Extension (work-in-progress): Highlight text on any page, right-click, and send it straight to your task list. Next Steps: Build WITH the Community 👥 Right now, the app is 100% free while still in the early stages. But hey, API calls and server costs aren’t cheap, so pricing is something I’ll figure out with you as we grow. For now, my goal is to hit 100 users and iterate from there. My first pricing idea is, without monthly subscription, I don’t want to charge someone for something he didn’t use. So I am planning on charging "per task", what do you think? Here’s what I have planned: 📍 End of Year Goal: 100 users (starting from… 1 🥲). 💸 Revenue Roadmap: When we establish pricing, we’ll talk about that. 🛠️ Milestones: Post on Product Hunt when we hit 100 users. Clean up my self-written spaghetti code (hire a pro dev for review 🙃). Hire a part-time dev once we hit MRR that can cover its costs. You can check how are we doing on thisisatask.me/stats Other Side Projects I’m Working On: Because… what’s life without taking on too much, right? 😂 Full list of things I’m building: Internal HRM: Not public, tried and tested in-house. Android TV App: Syncs with HRM to post announcements to office TVs (streamlined and simple). Stats Tracker App: Connects to our internal software and gives me real-time company insights. Review Analyzer: Scrapes SaaS reviews (e.g., G2) and runs deep analysis via AI. This was originally for my Shopify SaaS but is quickly turning into something standalone. Coming soon! Mobile app game: secret for now. Let’s Build This Together! Would love it if you guys checked out https://thisisatask.me and gave it a spin! Still super early, super raw, but I’m pumped to hear your thoughts. Also, what’s a must-have task manager feature for you? Anything that frustrates you with current tools? I want to keep evolving this in public, so your feedback is gold. 🌟 Let me know, Reddit! Are you with me? 🙌

#reddit#side#projects:

reddit

0

0.667

GDbuildsGD•This week

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

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

#reddit#spent#months

reddit

0

1

jottrled•This week

How I went from $27 to $3K as a solopreneur still in a 9-5

My journey started back in November 2023. I was scrolling through Twitter and YouTube and saw a word that I had never come across before. Solopreneur. The word caught my eye. Mainly because I was pretty sure I knew what it meant even though it's not a word you'll find in the dictionary. I liked what it was describing. A solo entrepreneur. A one man business. It completely resonated with me. As a software engineer by trade I'm used to working alone, especially since the pandemic hit and we were forced to work remotely. See, I always wanted to ditch the 9-5 thing but thought that was too big and too scary for a single person to do. Surely you would need a lot of money to get started, right? Surely you would need investors? The whole concept seemed impossible to me. That was until I found all the success stories. I became obsessed with the concept of solopreneurship. As I went further down the rabbit hole I found people like Justin Welsh, Kieran Drew and Marc Louvion to name a few. All of whom have one person businesses making huge money every year. So I thought, if they can do it, why can't I? People like this have cleared the pathway for those looking to escape the 9-5 grind. I decided 2024 would be the year I try this out. My main goal for the year? Build a one man business, earn my first $ online and learn a sh\*t ton along the way. My main goal in general? Build my business to $100K per year, quit my 9-5 and live with freedom. From December 2023 to February 2024 I began brainstorming ideas. I was like a lost puppy looking for his ball. How on earth did people find good ideas? I began writing everything and anything that came to mind down in my notes app on my phone. By February I would have approximately 70 ideas. Each as weird and whacky as the other. I was skeptical though. If I went through all the trouble of building a product for one of these ideas how would I know if anyone would even be interested in using it? I got scared and took a break for a week. All these ideas seemed too big and the chance that they would take off into the atmosphere was slim (in my mind anyways). I was learning more and more about solopreneurship as the weeks went on so I decided to build a product centered around everything I was learning about. The idea was simple. Enter a business idea and use AI to give the user details about how to market it, who their target customers were, what to write on their landing page, etc. All for a measly $27 per use. I quickly built it and launched on March 3rd 2024. I posted about it on Indie Hackers, Reddit and Hacker News. I was so excited about the prospect of earning my first internet $! Surely everyone wanted to use my product! Nope...all I got was crickets. I was quickly brought back down to earth. That was until 5 days later. I looked at my phone and had a new Stripe notification! Cha-ching! My first internet $. What a feeling! That was goal number 1 complete. It would be another 6 days before I would get my second sale...and then another 15 days to get my third. It was an emotional rollercoaster. I went from feeling like quitting the 9-5 was actually possible to thinking that maybe the ups and downs aren't worth it. On one hand I had made my first internet dollar so I should my ecstatic, and don't get me wrong, I was but I wanted more. More validation that I could do this long term. By May I was starting to give up on the product. I had learned so much in the past few months about marketing, SEO, building an audience, etc. and I wanted to build something that I thought could have more success so I focused on one critical thing that I had learned about. What was it? Building a product that had SEO potential. A product that I knew hundreds of people were looking for. See this was my thinking - If I could find a keyword that people were searching for on Google hundreds/thousands of times every month and it was easy to rank high on search engines then I would go all in (in SEO land this equates to a Keyword that has a Keyword Difficulty of = 500). I began researching and found that the keyword "micro saas ideas" was being searched for around 600 times each month. Micro Saas was something that really interested me. It was perfect for solopreneurs. Small software products that 1 person could build. What's not to like if you're in the game of software and solopreneurship? Researching keywords like this became like a game for me. I was hooked. I was doing it every day, finding gems that were being searched for hundreds and thousands of times every month that still had potential. That's when I came up with my next product idea. I decided to create a database of Micro Saas Ideas all with this sort of SEO potential. See if you can build a product that you know people are looking for then that's all the validation you need. So I put this theory to the test. I created a database of Micro Saas Ideas with SEO Potential and launched it in June 2024. This time it was different. I made $700 in the first week of launching. A large contrast to my previous failed attempt at becoming the worlds greatest solopreneur. Since launch I have grown the product to $3K and I couldn't be happier. I know what you're saying, $3K isn't a lot. But it's validation. It's validation that I can earn $ online. Validation that I can grow a business and it gives me hope that one day I'll be able to quit that 9-5 grind. My plan is to keep growing the business. I expect there to be a few challenges up ahead but I'll tackle them as I go and learn from the failures and successes. I have a newsletter where I share Micro Saas Ideas with SEO potential every week which I'll leave below in the first comment. Feel free to come along for the ride. If not I hope this post brings you some value If you're thinking about starting as a solopreneur, stop thinking and start doing, you won't regret it.

#reddit#went#solopreneur

reddit

0

0.667

GDbuildsGD•This week

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

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

#reddit#spent#months

reddit

0

0.818

Michaelbetterecycle•This week

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

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

#reddit#team#made

reddit

0

1

thewolfofslovenia•This week

0-20+ faceless AI automated YouTube channels in 1 year - my process and tools

First of all before diving deep into this process (scroll a bit below) I have to say something that everyone keeps asking me, is it profitable? Yes. It's by far my most profitable venture outside of my regular 9-5... But it took a lot of work, delegation and building processes to get here. So the one thing I would love to get out of this post - if you have any insights, feedback or tools I might be missing out post them below and let's help each other out. Now, how you can get started with (AI) YouTube automation: Pick a topic that is BOTH: a) in demand b) interesting to you & you have knowledge about Do everything yourself at first - delegate later No one cares about the videos as much as you do, so make sure to nail the ideation, scripts, editing, format and packaging yourself first. Now that we got that out of the way: Use this workflow: VidIQ - outliers sections is pure gold, I use it all the time to find trending video packaging, topics, etc. ChatGPT or Claude - high level video ideas at scale and your assistant (I use projects inside ChatGPT and its really good at managing and prioritizing). If you are using it for scripts please for the love of god, make final edits yourself by hand. Add character, personal insights, ideas, etc. Katalist AI - all in one video generator tool I use to quickly go from video idea to script, storyboard, AI voiceover and then final visuals. It's surprisingly good and to make a decent video it only takes about 1-2 hours in TOTAL. Once you understand how it works and have a process, delegate to tech savvy VAs / content creators for $5-$15/hour and you have final, good quality videos for less than $30. Pikzels / Krea AI - your AI thumbnail generator, I dont remember the last time we used Photoshop outside of quick text or image edits. Its basically AI image manipulation at scale and it costs 10-30x less than a human thumbnail designer and the thumbnails are really good. VidIQ+TubeBuddy - titles & optimization, but you have to know that most of the views come usually from recommended, so dont over obsess and add 392x keywords in your title and description. Its all about the packaging. Now whats left is track performance & iterate - it's practically impossible to nail it the first few times, but each video you make look at the data (not just in YT studio) and UNDERSTAND why it did not perform as well as you thought it would. Regarding monetization, adsense sucks - sell digital products. If I was relying on adsense alone I would never ever be profitable, but selling mini digital products and mentioning CTAs in the actual video not just in the description makes this super profitable and scaleable, especially since video production is so cheap. Final thoughts: (AI) YouTube automation absolutely works, but it’s not an overnight success or a total hands-off cashcow machine. It’s a real business and you need systems, consistent effort, iteration, failing and learning along the way. If you’ve got any tips, hidden gems or tools I might be missing, drop them below & let’s help each other out.

#reddit#0-20+#faceless

reddit

0

0.818

Michaelbetterecycle•This week

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

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

#reddit#team#made

reddit

0

1

thewolfofslovenia•This week

0-20+ faceless AI automated YouTube channels in 1 year - my process and tools

First of all before diving deep into this process (scroll a bit below) I have to say something that everyone keeps asking me, is it profitable? Yes. It's by far my most profitable venture outside of my regular 9-5... But it took a lot of work, delegation and building processes to get here. So the one thing I would love to get out of this post - if you have any insights, feedback or tools I might be missing out post them below and let's help each other out. Now, how you can get started with (AI) YouTube automation: Pick a topic that is BOTH: a) in demand b) interesting to you & you have knowledge about Do everything yourself at first - delegate later No one cares about the videos as much as you do, so make sure to nail the ideation, scripts, editing, format and packaging yourself first. Now that we got that out of the way: Use this workflow: VidIQ - outliers sections is pure gold, I use it all the time to find trending video packaging, topics, etc. ChatGPT or Claude - high level video ideas at scale and your assistant (I use projects inside ChatGPT and its really good at managing and prioritizing). If you are using it for scripts please for the love of god, make final edits yourself by hand. Add character, personal insights, ideas, etc. Katalist AI - all in one video generator tool I use to quickly go from video idea to script, storyboard, AI voiceover and then final visuals. It's surprisingly good and to make a decent video it only takes about 1-2 hours in TOTAL. Once you understand how it works and have a process, delegate to tech savvy VAs / content creators for $5-$15/hour and you have final, good quality videos for less than $30. Pikzels / Krea AI - your AI thumbnail generator, I dont remember the last time we used Photoshop outside of quick text or image edits. Its basically AI image manipulation at scale and it costs 10-30x less than a human thumbnail designer and the thumbnails are really good. VidIQ+TubeBuddy - titles & optimization, but you have to know that most of the views come usually from recommended, so dont over obsess and add 392x keywords in your title and description. Its all about the packaging. Now whats left is track performance & iterate - it's practically impossible to nail it the first few times, but each video you make look at the data (not just in YT studio) and UNDERSTAND why it did not perform as well as you thought it would. Regarding monetization, adsense sucks - sell digital products. If I was relying on adsense alone I would never ever be profitable, but selling mini digital products and mentioning CTAs in the actual video not just in the description makes this super profitable and scaleable, especially since video production is so cheap. Final thoughts: (AI) YouTube automation absolutely works, but it’s not an overnight success or a total hands-off cashcow machine. It’s a real business and you need systems, consistent effort, iteration, failing and learning along the way. If you’ve got any tips, hidden gems or tools I might be missing, drop them below & let’s help each other out.

#reddit#0-20+#faceless

reddit

0

1

JackRipperVA•This week

[P] [R] sANNd: A New Neural Network Framework Using Trainable Iterators

sANNd sANNd is a lightweight, modular neural network library designed as a sandbox for experimenting with new ideas in artificial intelligence. The Mould Class: A Pythonic Building Block The Mould class is a core component of sANNd. It provides a Pythonic way to apply functions to data that’s bundled inside objects: Encapsulated Variables: Each Mould object holds a set of variables (for example, weights or parameters) inside it. This means related data is kept together in one place (the object), making the code organized and intuitive. Static Functions: A Mould class defines its operation as a static method – essentially a function that isn’t tied to a specific instance. This static function takes in inputs (and possibly other Mould objects’ variables) and produces an output. In simple terms, the Mould’s static method describes how to transform input data using the Mould’s internal variables. Pythonic Usage: Using static methods in this way is a clean, Pythonic design. You call the Mould’s function through the class, but it applies to the data in the object. This approach lets you clearly separate what the operation is (the logic in the static function) from which data it uses (the variables inside the Mould instance). Example: Imagine a Mould class called LinearMould that has a static function to compute a linear transformation (like y = W*x + b). An instance of LinearMould would hold specific W and b values, and you’d use the static method to apply that linear formula to an input. This gives you the convenience of object-oriented design (encapsulating W and b) with the clarity of a standalone function defining the math. Chaining Moulds for Complex Computations Moulds become even more powerful when you chain them together. You can connect multiple Moulds so that the output of one becomes the input of the next: Sequential Operations: Just like stacking layers in a neural network, you can place Moulds in sequence. For example, you might take the output from LinearMouldA and feed it into LinearMouldB. In code, this might look as simple as using the output of one call as the argument to the next. The design of sANNd makes this straightforward – the static function of each Mould knows how to handle the data coming in. Building Pipelines: By chaining Moulds, you create a pipeline of transformations. Each Mould handles one step of computation, and together they produce a final result. This could represent a multi-layer neural network, a data processing pipeline, or any custom sequence of operations you need. There’s no strict limit to how you can chain them; you have the freedom to combine Moulds in any order that makes sense for your experiment. Clarity and Modularity: Because each Mould is a self-contained piece (with its variables and function), chaining them doesn’t turn your code into a black box. You can inspect or modify any part of the chain easily. This modular design means you can insert, remove, or replace Moulds to see how it affects the overall computation, which is great for experimentation. Implicit Backward Path (Automatic Backpropagation) One major benefit of using chained Moulds is that they implicitly define the backward path for training with gradient descent (backpropagation): Automatic Gradient Flow: When you connect Moulds in a sequence for a forward pass (input → Mould A → Mould B → output), you’ve essentially defined a computation graph. sANNd uses this graph to handle the reverse computation automatically. In other words, if you calculate an error or loss based on the final output, sANNd can propagate that error backwards through each Mould in the chain. No Manual Backprop: You do not need to manually code how gradients flow through each Mould. The way you set up the Moulds’ static functions already determines how outputs depend on inputs and internal variables. sANNd leverages that to perform backpropagation. This is similar in spirit to how libraries like PyTorch/TF do “autograd,” but here it’s a natural result of the Mould chain architecture. Gradient Descent Ready: Because the backward path is established by the forward connections, you can apply gradient descent optimizations out of the box. For instance, you can adjust the weights inside each Mould based on the computed gradients to minimize your loss. The design ensures that each Mould’s contribution to the final error is tracked, so all parts of your model learn appropriately during training. In short, defining your model with Moulds means you get training capability for free. You focus on describing the forward computations, and sANNd handles the math behind learning from errors. Comparing sANNd to Traditional Frameworks sANNd’s approach is quite different from traditional Python-based neural network frameworks. Here’s how it stacks up against frameworks like TensorFlow, PyTorch, or Keras in terms of approach, flexibility, and intended use: Design Approach: Traditional frameworks use predefined layer classes and often build a computation graph behind the scenes. For example, Keras might have a Dense layer class, and TensorFlow might construct a static graph (in TF1) or use eager execution (in TF2). sANNd takes a simpler approach – it uses plain Python classes and static functions (Moulds) to define computations. There’s no need to learn a new graph syntax or decorators; if you know Python functions and classes, you can read and write sANNd models. This makes the internal workings more transparent and easier to follow. Flexibility: While frameworks like PyTorch and TensorFlow are very powerful, they can introduce a lot of boilerplate and assume you’re building typical architectures. sANNd is extremely modular and flexible. You aren’t limited to the layers someone else defined – you can create any operation you want as a Mould. Want to experiment with a novel activation function or a custom recurrent connection? Just define it in a Mould. There’s less magic and abstraction obscuring your code, so unconventional model structures are easier to implement. (Of course, major frameworks can also be extended, but sANNd makes this feel more natural by staying within standard Python paradigms.) Intended Use: sANNd is intended for experimentation and research. It’s like a toolkit for tinkering. You get fine-grained control over every part of the network, which is ideal for trying out bold new ideas that don’t fit the mold of common deep learning models. In contrast, TensorFlow/PyTorch shine in production environments and large-scale training – they are optimized (GPU support, highly efficient tensor operations) and come with many utilities for things like data loading, distributed training, etc. sANNd doesn’t aim to replace them for those heavy-lifting tasks. Instead, it’s meant for when you need a lighter, more interpretable setup to prototype concepts. You might use sANNd to prove out a concept or test a hypothesis in AI research, and later switch to a bigger framework if you need to scale it up. Simplicity vs. Complexity: By design, sANNd keeps things simple. The trade-off is that it might not have the raw performance optimizations of the large frameworks. However, this simplicity is a feature – it means the code is easier to understand and modify. For many research scenarios, being able to quickly tweak an idea is more important than squeezing out maximum speed. Traditional frameworks, with their complexity, can sometimes be harder to adapt for radically different ideas (you might find yourself fighting the framework). With sANNd, the framework gets out of your way as much as possible. Modular and Experimental by Nature One of the driving philosophies of sANNd is to be modular and experimental, to further ML research: Modularity: sANNd is built from small, composable pieces. The Mould class is one such piece, and you can imagine building additional components in a similar spirit. This modular design means you can re-use components, mix and match them, or replace one implementation with another without affecting the rest of your system. It’s like having a box of building blocks for neural networks – you can assemble them in standard ways or in completely novel configurations. Experimentation Friendly: Because it avoids heavy abstraction, sANNd lets you directly see and control what’s happening at each step. This is great for research, where you might need to observe intermediate results, inject custom behavior, or adjust the learning process on the fly. sANNd’s straightforward structure (Python objects and functions) makes such interventions possible. You’re not constrained to a fixed training loop or forced to use certain layer types. True Intelligence Research: Achieving “True Intelligence” (often related to artificial general intelligence or other forms of broader AI) may require going beyond the usual neural network designs. sANNd aims to be a playground for these ideas. Its flexibility allows researchers to integrate unconventional elements — be it new memory structures, dynamic connection patterns, or hybrid models that combine symbolic and neural approaches. You can use sANNd to prototype these offbeat ideas quickly. In essence, it’s easier to test “what if we try this?” scenarios with sANNd than with more rigid frameworks. In summary, sANNd’s unique Mould class and design philosophy offer a fresh take on building neural networks. It emphasizes clarity, composability, and flexibility, allowing you to focus on creativity and understanding. Whether you’re stacking simple Moulds into a deep model, or inventing a completely new form of network, sANNd provides a friendly foundation. It’s not here to dethrone TensorFlow or PyTorch in industry applications – instead, it’s here to give researchers and enthusiasts a more malleable tool for exploring the frontiers of AI. Enjoy using sANNd as your neural network sandbox, and happy experimenting!

#reddit#sannd:#neural

reddit

0

0.6

AlexSnakeKing•This week

[Discussion] When ML and Data Science are the death of a good company: A cautionary tale.

TD;LR: At Company A, Team X does advanced analytics using on-prem ERP tools and older programming languages. Their tools work very well and are designed based on very deep business and domain expertise. Team Y is a new and ambitious Data Science team that thinks they can replace Team X's tools with a bunch of R scripts and a custom built ML platform. Their models are simplistic, but more "fashionable" compared to the econometric models used by Team X, and team Y benefits from the ML/DS moniker so leadership is allowing Team Y to start a large scale overhaul of the analytics platform in question. Team Y doesn't have the experience for such a larger scale transformation, and is refusing to collaborate with team X. This project is very likely going to fail, and cause serious harm to the company as a whole financially and from a people perspective. I argue that this is not just because of bad leadership, but also because of various trends and mindsets in the DS community at large. Update (Jump to below the line for the original story): Several people in the comments are pointing out that this just a management failure, not something due to ML/DS, and that you can replace DS with any buzz tech and the story will still be relevant. My response: Of course, any failure at an organization level is ultimately a management failure one way or the other. Moreover, it is also the case that ML/DS when done correctly, will always improve a company's bottom line. There is no scenario where the proper ML solution, delivered at a reasonable cost and in a timely fashion, will somehow hurt the company's bottom line. My point is that in this case management is failing because of certain trends and practices that are specific to the ML/DS community, namely: The idea that DS teams should operate independently of tech and business orgs -- too much autonomy for DS teams The disregard for domain knowledge that seems prevalent nowadays thanks to the ML hype, that DS can be generalists and someone with good enough ML chops can solve any business problem. That wasn't the case when I first left academia for the industry in 2009 (back then nobody would even bother with a phone screen if you didn't have the right domain knowledge). Over reliance on resources who check all the ML hype related boxes (knows Python, R, Tensorflow, Shiny, etc..., has the right Coursera certifications, has blogged on the topic, etc...), but are lacking in depth of experience. DS interviews nowadays all seem to be: Can you tell me what a p-value is? What is elastic net regression? Show me how to fit a model in sklearn? How do you impute NAs in an R dataframe? Any smart person can look those up on Stackoverflow or Cross-Validated,.....Instead teams should be asking stuff like: why does portfolio optimization use QP not LP? How does a forecast influence a customer service level? When should a recommendation engine be content based and when should it use collaborative filtering? etc... (This is a true story, happening to the company I currently work for. Names, domains, algorithms, and roles have been shuffled around to protect my anonymity)  Company A has been around for several decades. It is not the biggest name in its domain, but it is a well respected one. Risk analysis and portfolio optimization have been a core of Company A's business since the 90s. They have a large team of 30 or so analysts who perform those tasks on a daily basis. These analysts use ERP solutions implemented for them by one the big ERP companies (SAP, Teradata, Oracle, JD Edwards,...) or one of the major tech consulting companies (Deloitte, Accenture, PWC, Capgemini, etc...) in collaboration with their own in house engineering team. The tools used are embarrassingly old school: Classic RDBMS running on on-prem servers or maybe even on mainframes, code written in COBOL, Fortran, weird proprietary stuff like ABAP or SPSS.....you get the picture. But the models and analytic functions were pretty sophisticated, and surprisingly cutting edge compared to the published academic literature. Most of all, they fit well with the company's enterprise ecosystem, and were honed based on years of deep domain knowledge.  They have a tech team of several engineers (poached from the aforementioned software and consulting companies) and product managers (who came from the experienced pools of analysts and managers who use the software, or poached from business rivals) maintaining and running this software. Their technology might be old school, but collectively, they know the domain and the company's overall architecture very, very well. They've guided the company through several large scale upgrades and migrations and they have a track record of delivering on time, without too much overhead. The few times they've stumbled, they knew how to pick themselves up very quickly. In fact within their industry niche, they have a reputation for their expertise, and have very good relations with the various vendors they've had to deal with. They were the launching pad of several successful ERP consulting careers.  Interestingly, despite dealing on a daily basis with statistical modeling and optimization algorithms, none of the analysts, engineers, or product managers involved describe themselves as data scientists or machine learning experts. It is mostly a cultural thing: Their expertise predates the Data Science/ML hype that started circa 2010, and they got most of their chops using proprietary enterprise tools instead of the open source tools popular nowadays. A few of them have formal statistical training, but most of them came from engineering or domain backgrounds and learned stats on the fly while doing their job. Call this team "Team X".  Sometime around the mid 2010s, Company A started having some serious anxiety issues: Although still doing very well for a company its size, overall economic and demographic trends were shrinking its customer base, and a couple of so called disruptors came up with a new app and business model that started seriously eating into their revenue. A suitable reaction to appease shareholders and Wall Street was necessary. The company already had a decent website and a pretty snazzy app, what more could be done? Leadership decided that it was high time that AI and ML become a core part of the company's business. An ambitious Manager, with no science or engineering background, but who had very briefly toyed with a recommender system a couple of years back, was chosen to build a data science team, call it team "Y" (he had a bachelor's in history from the local state college and worked for several years in the company's marketing org). Team "Y" consists mostly of internal hires who decided they wanted to be data scientists and completed a Coursera certification or a Galvanize boot camp, before being brought on to the team, along with a few of fresh Ph.D or M.Sc holders who didn't like academia and wanted to try their hand at an industry role. All of them were very bright people, they could write great Medium blog posts and give inspiring TED talks, but collectively they had very little real world industry experience. As is the fashion nowadays, this group was made part of a data science org that reported directly to the CEO and Board, bypassing the CIO and any tech or business VPs, since Company A wanted to claim the monikers "data driven" and "AI powered" in their upcoming shareholder meetings. In 3 or 4 years of existence, team Y produced a few Python and R scripts. Their architectural experience  consisted almost entirely in connecting Flask to S3 buckets or Redshift tables, with a couple of the more resourceful ones learning how to plug their models into Tableau or how to spin up a Kuberneties pod.  But they needn't worry: The aforementioned manager, who was now a director (and was also doing an online Masters to make up for his qualifications gap and bolster his chances of becoming VP soon - at least he now understands what L1 regularization is), was a master at playing corporate politics and self-promotion. No matter how few actionable insights team Y produced or how little code they deployed to production, he always had their back and made sure they had ample funding. In fact he now had grandiose plans for setting up an all-purpose machine learning platform that can be used to solve all of the company's data problems.  A couple of sharp minded members of team Y, upon googling their industry name along with the word "data science", realized that risk analysis was a prime candidate for being solved with Bayesian models, and there was already a nifty R package for doing just that, whose tutorial they went through on R-Bloggers.com. One of them had even submitted a Bayesian classifier Kernel for a competition on Kaggle (he was 203rd on the leaderboard), and was eager to put his new-found expertise to use on a real world problem. They pitched the idea to their director, who saw a perfect use case for his upcoming ML platform. They started work on it immediately, without bothering to check whether anybody at Company A was already doing risk analysis. Since their org was independent, they didn't really need to check with anybody else before they got funding for their initiative. Although it was basically a Naive Bayes classifier, the term ML was added to the project tile, to impress the board.  As they progressed with their work however, tensions started to build. They had asked the data warehousing and CA analytics teams to build pipelines for them, and word eventually got out to team X about their project. Team X was initially thrilled: They offered to collaborate whole heartedly, and would have loved to add an ML based feather to their already impressive cap. The product owners and analysts were totally onboard as well: They saw a chance to get in on the whole Data Science hype that they kept hearing about. But through some weird mix of arrogance and insecurity, team Y refused to collaborate with them or share any of their long term goals with them, even as they went to other parts of the company giving brown bag presentations and tutorials on the new model they created.  Team X got resentful: from what they saw of team Y's model, their approach was hopelessly naive and had little chances of scaling or being sustainable in production, and they knew exactly how to help with that. Deploying the model to production would have taken them a few days, given how comfortable they were with DevOps and continuous delivery (team Y had taken several months to figure out how to deploy a simple R script to production). And despite how old school their own tech was, team X were crafty enough to be able to plug it in to their existing architecture. Moreover, the output of the model was such that it didn't take into account how the business will consume it or how it was going to be fed to downstream systems, and the product owners could have gone a long way in making the model more amenable to adoption by the business stakeholders. But team Y wouldn't listen, and their leads brushed off any attempts at communication, let alone collaboration. The vibe that team Y was giving off was "We are the cutting edge ML team, you guys are the legacy server grunts. We don't need your opinion.", and they seemed to have a complete disregard for domain knowledge, or worse, they thought that all that domain knowledge consisted of was being able to grasp the definitions of a few business metrics.  Team X got frustrated and tried to express their concerns to leadership. But despite owning a vital link in Company A's business process, they were only \~50 people in a large 1000 strong technology and operations org, and they were several layers removed from the C-suite, so it was impossible for them to get their voices heard.  Meanwhile, the unstoppable director was doing what he did best: Playing corporate politics. Despite how little his team had actually delivered, he had convinced the board that all analysis and optimization tasks should now be migrated to his yet to be delivered ML platform. Since most leaders now knew that there was overlap between team Y and team X's objectives, his pitch was no longer that team Y was going to create a new insight, but that they were going to replace (or modernize) the legacy statistics based on-prem tools with more accurate cloud based ML tools. Never mind that there was no support in the academic literature for the idea that Naive Bayes works better than the Econometric approaches used by team X, let alone the additional wacky idea that Bayesian Optimization would definitely outperform the QP solvers that were running in production.  Unbeknownst to team X, the original Bayesian risk analysis project has now grown into a multimillion dollar major overhaul initiative, which included the eventual replacement of all of the tools and functions supported by team X along with the necessary migration to the cloud. The CIO and a couple of business VPs are on now board, and tech leadership is treating it as a done deal. An outside vendor, a startup who nobody had heard of, was contracted to help build the platform, since team Y has no engineering skills. The choice was deliberate, as calling on any of the established consulting or software companies would have eventually led leadership to the conclusion that team X was better suited for a transformation on this scale than team Y.  Team Y has no experience with any major ERP deployments, and no domain knowledge, yet they are being tasked with fundamentally changing the business process that is at the core of Company A's business. Their models actually perform worse than those deployed by team X, and their architecture is hopelessly simplistic, compared to what is necessary for running such a solution in production.  Ironically, using Bayesian thinking and based on all the evidence, the likelihood that team Y succeeds is close to 0%. At best, the project is going to end up being a write off of 50 million dollars or more. Once the !@#$!@hits the fan, a couple of executive heads are going to role, and dozens of people will get laid off. At worst, given how vital risk analysis and portfolio optimization is to Company A's revenue stream, the failure will eventually sink the whole company. It probably won't go bankrupt, but it will lose a significant portion of its business and work force. Failed ERP implementations can and do sink large companies: Just see what happened to National Grid US, SuperValu or Target Canada.  One might argue that this is more about corporate disfunction and bad leadership than about data science and AI. But I disagree. I think the core driver of this debacle is indeed the blind faith in Data Scientists, ML models and the promise of AI, and the overall culture of hype and self promotion that is very common among the ML crowd.  We haven't seen the end of this story: I sincerely hope that this ends well for the sake of my colleagues and all involved. Company A is a good company, and both its customers and its employees deserver better. But the chances of that happening are negligible given all the information available, and this failure will hit my company hard.

#reddit#[discussion]#data

reddit

0

0

darkItachi94•This week

[P] My experiments with Knowledge Distillation

Hi r/MachineLearning community! I conducted several experiments on Knowledge Distillation and wanted to share my findings. Here is a snippet of the results comparing performance of teacher, student, fine tuned and distilled models: |Dataset|Qwen2 Model Family|MMLU (Reasoning)|GSM8k (Math)|WikiSQL (Coding)| |:-|:-|:-|:-|:-| |||||| |1|Pretrained - 7B|0.598|0.724|0.536| |2|Pretrained - 1.5B|0.486|0.431|0.518| |3|Finetuned - 1.5B|0.494|0.441|0.849| |4|Distilled - 1.5B, Logits Distillation|0.531|0.489|0.862| |5|Distilled - 1.5B, Layers Distillation|0.527|0.481|0.841| For a detailed analysis, you can read this report. I also created an open source library to facilitate its adoption. You can try it here. My conclusion: Prefer distillation over fine-tuning when there is a substantial gap between the larger and smaller model on the target dataset. In such cases, distillation can effectively transfer knowledge, leading to significantly better performance than standard fine-tuning alone. P.S. This blog post gives a high level introduction to Distillation. Let me know what you think!

#reddit#experiments#knowledge

reddit

0

0

zimonitrome•This week

[D] Should the praise of "Data-centric" AI be taken with a grain of salt?

I hear co-workers, professors, entrepreneurs talk about just how important it is to switch from model-centric AI to a data-centric approach. Personally I don't see a problem focusing on attaining better data but I have been seeing this simplification that AI performance = model + data which seems massively misleading. A better generalization would be AI performance = model data or even AI performance = model log(len(data)). Looking at the rapidly changing problem of image synthesis, it is clear that data alone could not produce the same results seen even two years ago. On the other hand, it can seem unproductive for the field as a whole to try to create another classification model that achieves a .02% increased performance on ImageNet... again and again... And this is maybe why we hear more talk in industry about focusing on the data instead of models: Industry generally faces simpler tasks with negligible improvement as of recently (regression, classification). Therefore it's more easy and valuable to increase and improve the training data. And yes, most machine learning models NEED a large training set to approximate a complex distribution. We have already known this since forever. I think the term has just recently become a pet peeve for me as a novel "catch all" solution to any problem. What are your opinions on the matter?

#reddit#should#praise

reddit

0

0.765

hardmaru•This week

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

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

#reddit#interview#juergen

reddit

0

1

Successful-Western27•This week

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

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

#reddit#forecasting#mitigating

reddit

0

1

EsotericaCapital•This week

[N] New Trends to Power Faster Artificial Intelligence and Machine Learning Adoption?

In 2012, Google X lab created a neural network that can identify cats. Since then, technology companies have been increasingly adopting AI/ML on a large scale to build better applications and services for consumers (ToC). On the other hand, AI/ML's adoption on the enterprises' side (ToB) has yet to see the same growth trajectory due to the costs and complexities in both hardware and software. However, Since 2020, we started noticing three emerging tech trends that can help accelerate enterprises' adoption of AI/ML. Breakthrough in semiconductors: In 2020, Nvidia debut the concept of "Data Processing Unit," a new class of programmable processors that combine high-performance CPU with SmartNiC (network interface controller). Data centers can deploy DPUs to optimize computing offload and frees up CPUs to focus on intended tasks, such as machine learning. DPUs help resolve a significant bottleneck for ML training, where models, sometimes with billions of parameters, are way too big for traditional CPUs and GPUs to handle. Other leading semiconductor players, such as Marvell and Xilinx, follow suit with their in-house or partner-designed DPUs. Industry analysts have forecasted that the market size for DPUs in data centers alone could reach $50 billion by 2025. &#x200B; https://preview.redd.it/l436muluhnn61.png?width=1430&format=png&auto=webp&s=ba8d1298056ea31bddd25f1596ff64b7e107580a Breakthrough in software: we also saw significant progress of "Conversational AI," a new form of AI that can understand and speak languages with human-like accuracy, in 2020. Conversational AI allows two-way interactions and provides a much better user experience than traditional AI-powered Chatbot, mostly a one-way response system. The secret of conversational AI is its ability to handle lots of human conversation variance. Developers have designed innovative algorithms such as "Switch transformers" and "Sparse training" to enable models to handle vast amounts of data. The size of conversational AI training models is enormous and keeps expanding. For example, in February 2021, Google Brain announced a model with 1.6 trillion parameters, nine times the size of the famous Open AI GPT-3 (175 billion parameters) unveiled in July 2020. GPT-3 is 100+ times bigger than GPT-2 introduced in 2019. &#x200B; https://preview.redd.it/oajpi2yvhnn61.png?width=1430&format=png&auto=webp&s=1482913a98e17ddc1d62cc79864598d4012ad6f7 Cloud giants are expanding machine-learning platforms for developers. Andy Jassy famously said that "AI is shifting from a niche experiment inside technical departments to becoming more mainstream in business processes." in the 2020 AWS reInvent. During the conference, AWS rolled out many AI products across the technology stack, including AI chips (AWS Trainium), database (Aurora Machine Learning), and vertical solutions (Amazon Healthlake), etc. However, the most significant development is the drastic expansion of "Amazon SageMaker," one of the largest cloud machine-learning platforms. SageMaker has been offering new features to make it easier for developers to automate machine learning workflow. Microsoft Azure and Google Cloud are also growing their ML developer platforms. &#x200B; https://preview.redd.it/z9wf2o8xhnn61.png?width=1430&format=png&auto=webp&s=9f607acfe8f0dbf36fb9b472f3cb40b80f13879e Witnessing these breakthroughs in semiconductor and software, coupled with cloud giants' effort to democratize AI, we see a coming inflection point of accelerated AI adoption in both ToC and ToB markets. So how do we benefit from this megatrend? In semiconductors, we like companies with DPUs exposure. In AI development and processing, we favor multi-cloud AI platforms such as Databricks. In enterprise software, we believe there will be a strong wave of new AI-based enterprise applications that can be creative and efficient in solving real-world problems.

#reddit#trends#power

reddit

0

0.765

hardmaru•This week

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

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

#reddit#interview#juergen

reddit

0

0.6

AlexSnakeKing•This week

[Discussion] When ML and Data Science are the death of a good company: A cautionary tale.

TD;LR: At Company A, Team X does advanced analytics using on-prem ERP tools and older programming languages. Their tools work very well and are designed based on very deep business and domain expertise. Team Y is a new and ambitious Data Science team that thinks they can replace Team X's tools with a bunch of R scripts and a custom built ML platform. Their models are simplistic, but more "fashionable" compared to the econometric models used by Team X, and team Y benefits from the ML/DS moniker so leadership is allowing Team Y to start a large scale overhaul of the analytics platform in question. Team Y doesn't have the experience for such a larger scale transformation, and is refusing to collaborate with team X. This project is very likely going to fail, and cause serious harm to the company as a whole financially and from a people perspective. I argue that this is not just because of bad leadership, but also because of various trends and mindsets in the DS community at large. Update (Jump to below the line for the original story): Several people in the comments are pointing out that this just a management failure, not something due to ML/DS, and that you can replace DS with any buzz tech and the story will still be relevant. My response: Of course, any failure at an organization level is ultimately a management failure one way or the other. Moreover, it is also the case that ML/DS when done correctly, will always improve a company's bottom line. There is no scenario where the proper ML solution, delivered at a reasonable cost and in a timely fashion, will somehow hurt the company's bottom line. My point is that in this case management is failing because of certain trends and practices that are specific to the ML/DS community, namely: The idea that DS teams should operate independently of tech and business orgs -- too much autonomy for DS teams The disregard for domain knowledge that seems prevalent nowadays thanks to the ML hype, that DS can be generalists and someone with good enough ML chops can solve any business problem. That wasn't the case when I first left academia for the industry in 2009 (back then nobody would even bother with a phone screen if you didn't have the right domain knowledge). Over reliance on resources who check all the ML hype related boxes (knows Python, R, Tensorflow, Shiny, etc..., has the right Coursera certifications, has blogged on the topic, etc...), but are lacking in depth of experience. DS interviews nowadays all seem to be: Can you tell me what a p-value is? What is elastic net regression? Show me how to fit a model in sklearn? How do you impute NAs in an R dataframe? Any smart person can look those up on Stackoverflow or Cross-Validated,.....Instead teams should be asking stuff like: why does portfolio optimization use QP not LP? How does a forecast influence a customer service level? When should a recommendation engine be content based and when should it use collaborative filtering? etc... (This is a true story, happening to the company I currently work for. Names, domains, algorithms, and roles have been shuffled around to protect my anonymity)  Company A has been around for several decades. It is not the biggest name in its domain, but it is a well respected one. Risk analysis and portfolio optimization have been a core of Company A's business since the 90s. They have a large team of 30 or so analysts who perform those tasks on a daily basis. These analysts use ERP solutions implemented for them by one the big ERP companies (SAP, Teradata, Oracle, JD Edwards,...) or one of the major tech consulting companies (Deloitte, Accenture, PWC, Capgemini, etc...) in collaboration with their own in house engineering team. The tools used are embarrassingly old school: Classic RDBMS running on on-prem servers or maybe even on mainframes, code written in COBOL, Fortran, weird proprietary stuff like ABAP or SPSS.....you get the picture. But the models and analytic functions were pretty sophisticated, and surprisingly cutting edge compared to the published academic literature. Most of all, they fit well with the company's enterprise ecosystem, and were honed based on years of deep domain knowledge.  They have a tech team of several engineers (poached from the aforementioned software and consulting companies) and product managers (who came from the experienced pools of analysts and managers who use the software, or poached from business rivals) maintaining and running this software. Their technology might be old school, but collectively, they know the domain and the company's overall architecture very, very well. They've guided the company through several large scale upgrades and migrations and they have a track record of delivering on time, without too much overhead. The few times they've stumbled, they knew how to pick themselves up very quickly. In fact within their industry niche, they have a reputation for their expertise, and have very good relations with the various vendors they've had to deal with. They were the launching pad of several successful ERP consulting careers.  Interestingly, despite dealing on a daily basis with statistical modeling and optimization algorithms, none of the analysts, engineers, or product managers involved describe themselves as data scientists or machine learning experts. It is mostly a cultural thing: Their expertise predates the Data Science/ML hype that started circa 2010, and they got most of their chops using proprietary enterprise tools instead of the open source tools popular nowadays. A few of them have formal statistical training, but most of them came from engineering or domain backgrounds and learned stats on the fly while doing their job. Call this team "Team X".  Sometime around the mid 2010s, Company A started having some serious anxiety issues: Although still doing very well for a company its size, overall economic and demographic trends were shrinking its customer base, and a couple of so called disruptors came up with a new app and business model that started seriously eating into their revenue. A suitable reaction to appease shareholders and Wall Street was necessary. The company already had a decent website and a pretty snazzy app, what more could be done? Leadership decided that it was high time that AI and ML become a core part of the company's business. An ambitious Manager, with no science or engineering background, but who had very briefly toyed with a recommender system a couple of years back, was chosen to build a data science team, call it team "Y" (he had a bachelor's in history from the local state college and worked for several years in the company's marketing org). Team "Y" consists mostly of internal hires who decided they wanted to be data scientists and completed a Coursera certification or a Galvanize boot camp, before being brought on to the team, along with a few of fresh Ph.D or M.Sc holders who didn't like academia and wanted to try their hand at an industry role. All of them were very bright people, they could write great Medium blog posts and give inspiring TED talks, but collectively they had very little real world industry experience. As is the fashion nowadays, this group was made part of a data science org that reported directly to the CEO and Board, bypassing the CIO and any tech or business VPs, since Company A wanted to claim the monikers "data driven" and "AI powered" in their upcoming shareholder meetings. In 3 or 4 years of existence, team Y produced a few Python and R scripts. Their architectural experience  consisted almost entirely in connecting Flask to S3 buckets or Redshift tables, with a couple of the more resourceful ones learning how to plug their models into Tableau or how to spin up a Kuberneties pod.  But they needn't worry: The aforementioned manager, who was now a director (and was also doing an online Masters to make up for his qualifications gap and bolster his chances of becoming VP soon - at least he now understands what L1 regularization is), was a master at playing corporate politics and self-promotion. No matter how few actionable insights team Y produced or how little code they deployed to production, he always had their back and made sure they had ample funding. In fact he now had grandiose plans for setting up an all-purpose machine learning platform that can be used to solve all of the company's data problems.  A couple of sharp minded members of team Y, upon googling their industry name along with the word "data science", realized that risk analysis was a prime candidate for being solved with Bayesian models, and there was already a nifty R package for doing just that, whose tutorial they went through on R-Bloggers.com. One of them had even submitted a Bayesian classifier Kernel for a competition on Kaggle (he was 203rd on the leaderboard), and was eager to put his new-found expertise to use on a real world problem. They pitched the idea to their director, who saw a perfect use case for his upcoming ML platform. They started work on it immediately, without bothering to check whether anybody at Company A was already doing risk analysis. Since their org was independent, they didn't really need to check with anybody else before they got funding for their initiative. Although it was basically a Naive Bayes classifier, the term ML was added to the project tile, to impress the board.  As they progressed with their work however, tensions started to build. They had asked the data warehousing and CA analytics teams to build pipelines for them, and word eventually got out to team X about their project. Team X was initially thrilled: They offered to collaborate whole heartedly, and would have loved to add an ML based feather to their already impressive cap. The product owners and analysts were totally onboard as well: They saw a chance to get in on the whole Data Science hype that they kept hearing about. But through some weird mix of arrogance and insecurity, team Y refused to collaborate with them or share any of their long term goals with them, even as they went to other parts of the company giving brown bag presentations and tutorials on the new model they created.  Team X got resentful: from what they saw of team Y's model, their approach was hopelessly naive and had little chances of scaling or being sustainable in production, and they knew exactly how to help with that. Deploying the model to production would have taken them a few days, given how comfortable they were with DevOps and continuous delivery (team Y had taken several months to figure out how to deploy a simple R script to production). And despite how old school their own tech was, team X were crafty enough to be able to plug it in to their existing architecture. Moreover, the output of the model was such that it didn't take into account how the business will consume it or how it was going to be fed to downstream systems, and the product owners could have gone a long way in making the model more amenable to adoption by the business stakeholders. But team Y wouldn't listen, and their leads brushed off any attempts at communication, let alone collaboration. The vibe that team Y was giving off was "We are the cutting edge ML team, you guys are the legacy server grunts. We don't need your opinion.", and they seemed to have a complete disregard for domain knowledge, or worse, they thought that all that domain knowledge consisted of was being able to grasp the definitions of a few business metrics.  Team X got frustrated and tried to express their concerns to leadership. But despite owning a vital link in Company A's business process, they were only \~50 people in a large 1000 strong technology and operations org, and they were several layers removed from the C-suite, so it was impossible for them to get their voices heard.  Meanwhile, the unstoppable director was doing what he did best: Playing corporate politics. Despite how little his team had actually delivered, he had convinced the board that all analysis and optimization tasks should now be migrated to his yet to be delivered ML platform. Since most leaders now knew that there was overlap between team Y and team X's objectives, his pitch was no longer that team Y was going to create a new insight, but that they were going to replace (or modernize) the legacy statistics based on-prem tools with more accurate cloud based ML tools. Never mind that there was no support in the academic literature for the idea that Naive Bayes works better than the Econometric approaches used by team X, let alone the additional wacky idea that Bayesian Optimization would definitely outperform the QP solvers that were running in production.  Unbeknownst to team X, the original Bayesian risk analysis project has now grown into a multimillion dollar major overhaul initiative, which included the eventual replacement of all of the tools and functions supported by team X along with the necessary migration to the cloud. The CIO and a couple of business VPs are on now board, and tech leadership is treating it as a done deal. An outside vendor, a startup who nobody had heard of, was contracted to help build the platform, since team Y has no engineering skills. The choice was deliberate, as calling on any of the established consulting or software companies would have eventually led leadership to the conclusion that team X was better suited for a transformation on this scale than team Y.  Team Y has no experience with any major ERP deployments, and no domain knowledge, yet they are being tasked with fundamentally changing the business process that is at the core of Company A's business. Their models actually perform worse than those deployed by team X, and their architecture is hopelessly simplistic, compared to what is necessary for running such a solution in production.  Ironically, using Bayesian thinking and based on all the evidence, the likelihood that team Y succeeds is close to 0%. At best, the project is going to end up being a write off of 50 million dollars or more. Once the !@#$!@hits the fan, a couple of executive heads are going to role, and dozens of people will get laid off. At worst, given how vital risk analysis and portfolio optimization is to Company A's revenue stream, the failure will eventually sink the whole company. It probably won't go bankrupt, but it will lose a significant portion of its business and work force. Failed ERP implementations can and do sink large companies: Just see what happened to National Grid US, SuperValu or Target Canada.  One might argue that this is more about corporate disfunction and bad leadership than about data science and AI. But I disagree. I think the core driver of this debacle is indeed the blind faith in Data Scientists, ML models and the promise of AI, and the overall culture of hype and self promotion that is very common among the ML crowd.  We haven't seen the end of this story: I sincerely hope that this ends well for the sake of my colleagues and all involved. Company A is a good company, and both its customers and its employees deserver better. But the chances of that happening are negligible given all the information available, and this failure will hit my company hard.

#reddit#[discussion]#data

reddit

0

1

Royal_Rest8409•This week

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

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

#reddit#founder#built

reddit

0

1

jamesackerman1234•This week

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]

Hello Everyone (VERY LONG CASE STUDY AHEAD) - 355% return in 9 months Note: I own a 7-figures USD valued portfolio of 41+ content sites that generates 5-6 figures USD a month in passive income. This is my first time posting in this sub and my goal is to NOT share generic advice but precise numbers, data and highly refined processes so you can also get started with this business yourself or if you already have an existing business, drive huge traffic to it and scale it substantially (get more customers). I will use a case study to explain the whole process. As most of us are entrepreneurs here, explaining an actual project would be more meaningful. In this case study I used AI assisted content to grow an existing site from $217/m to $2,836/m in 9 months (NO BACKLINKS) and sold it for $59,000. ROI of 3 months: 355% Previous case studies (before I give an overview of the model) Amazon Affiliate Content Site: $371/m to $19,263/m in 14 MONTHS - $900K CASE STUDY \[AMA\] Affiliate Website from $267/m to $21,853/m in 19 months (CASE STUDY - Amazon?) \[AMA\] Amazon Affiliate Website from $0 to $7,786/month in 11 months Amazon Affiliate Site from $118/m to $3,103/m in 8 MONTHS (SOLD it for $62,000+) Note: You can check pinned posts on my profile. Do go through the comments as well as a lot of questions are answered in those. However, if you still have any questions, feel free to reach out. This is an \[AMA\]. Quick Overview of the Model Approach: High traffic, niche specific, informative content websites that monetise its traffic through highly automated methods like display ads and affiliate. The same model can be applied to existing businesses to drive traffic and get customers. Main idea: Make passive income in a highly automated way Easy to understand analogy You have real estate (here you have digital asset like a website) You get rental income (here you get ads and affiliate income with no physical hassle, in case you have a business like service, product etc. then you can get customers for that too but if not, it's alright) Real estate has value (this digital asset also has value that can be appreciated with less effort) Real estate can be sold (this can be sold too but faster) IMPORTANT NOTE: Search traffic is the BEST way to reach HUGE target audience and it's important when it comes to scaling. This essentially means that you can either monetise that via affiliate, display etc. or if you have a business then you can reach a bigger audience to scale. Overview of this website's valuation (then and now: Oct. 2022 and June 2023) Oct 2022: $217/m Valuation: $5,750.5 (26.5x) - set it the same as the multiple it was sold for June 2023: $2,836/m Traffic and revenue trend: growing fast Last 3 months avg: $2,223 Valuation now: $59,000 (26.5x) Description: The domain was registered in 2016, it grew and then the project was left unattended. I decided to grow it again using properly planned AI assisted content. Backlink profile: 500+ Referring domains (Ahrefs). Backlinks mean the sites linking back to you. This is important when it comes to ranking. Summary of Results of This Website - Before and After Note: If the terms seem technical, do not worry. I will explain them in detail later. Still if you have any questions. Feel free to comment or reach out. |Metric|Oct 2022|June 2023|Difference|Comments| |:-|:-|:-|:-|:-| |Articles|314|804|\+490|AI Assisted content published in 3 months| |Traffic|9,394|31,972|\+22,578|Organic| |Revenue|$217|$2,836|\+$2,619|Multiple sources| |RPM (revenue/1000 web traffic)|23.09|$88.7|\+$65.61|Result of Conversion rate optimisation (CRO). You make changes to the site for better conversions| |EEAT (expertise, experience, authority and trust of website)|2 main authors|8 authors|6|Tables, video ads and 11 other fixations| |CRO|Nothing|Tables, video ads |Tables, video ads and 11 other fixations || &#x200B; Month by Month Growth |Month|Revenue|Steps| |:-|:-|:-| |Sept 2022|NA|Content Plan| |Oct 2022|$217|Content Production| |Nov 2022|$243|Content production + EEAT authors| |Dec 2022|$320|Content production + EEAT authors| |Jan 2023|$400|Monitoring| |Feb 2023|$223|Content production + EEAT authors| |Mar 2023|$2,128|CRO & Fixations| |April 2023|$1,609|CRO & Fixations| |May 2023|$2,223|Content production + EEAT authors| |June 2023|$2,836|CRO and Fixations| |Total|$10,199|| &#x200B; What will I share Content plan and Website structure Content Writing Content Uploading, formatting and onsite SEO Faster indexing Conversion rate optimisation Guest Posting EEAT (Experience, Expertise, Authority, Trust) Costing ROI The plans moving forward with these sites &#x200B; Website Structure and Content Plan This is probably the most important important part of the whole process. The team spends around a month just to get this right. It's like defining the direction of the project. Description: Complete blueprint of the site's structure in terms of organisation of categories, subcategories and sorting of articles in each one of them. It also includes the essential pages. The sorted articles target main keyword, relevant entities and similar keywords. This has to be highly data driven and we look at over 100 variables just to get it right. It's like beating Google's algorithm to ensure you have a blueprint for a site that will rank. It needs to be done right. If there is a mistake, then even if you do everything right - it's not going to work out and after 8-16 months you will realise that everything went to waste. Process For this project, we had a niche selected already so we didn't need to do a lot of research pertaining to that. We also knew the topic since the website was already getting good traffic on that. We just validated from Ahrefs, SEMRUSH and manual analysis if it would be worth it to move forward with that topic. &#x200B; Find entities related to the topic: We used Ahrefs and InLinks to get an idea about the related entities (topics) to create a proper topical relevance. In order to be certain and have a better idea, we used ChatGPT to find relevant entities as well \> Ahrefs (tool): Enter main keyword in keywords explorer. Check the left pain for popular topics \> Inlinks (tool): Enter the main keyword, check the entity maps \> ChatGPT (tool): Ask it to list down the most important and relevant entities in order of their priority Based on this info, you can map out the most relevant topics that are semantically associated to your main topic Sorting the entities in topics (categories) and subtopics (subcategories): Based on the information above, cluster them properly. The most relevant ones must be grouped together. Each group must be sorted into its relevant category. \> Example: Site about cycling. \> Categories/entities: bicycles, gear and equipment, techniques, safety, routes etc. \> The subcategories/subentities for let's say "techniques" would be: Bike handling, pedaling, drafting etc. Extract keywords for each subcategory/subentity: You can do this using Ahrefs or Semrush. Each keyword would be an article. Ensure that you target the similar keywords in one article. For example: how to ride a bicycle and how can I ride a bicycle will be targeted by one article. Make the more important keyword in terms of volume and difficulty as the main keyword and the other one(s) as secondary Define main focus vs secondary focus: Out of all these categories/entities - there will be one that you would want to dominate in every way. So, focus on just that in the start. This will be your main focus. Try to answer ALL the questions pertaining to that. You can extract the questions using Ahrefs. \> Ahrefs > keywords explorer \> enter keyword \> Questions \> Download the list and cluster the similar ones. This will populate your main focus category/entity and will drive most of the traffic. Now, you need to write in other categories/subentities as well. This is not just important, but crucial to complete the topical map loop. In simple words, if you do this Google sees you as a comprehensive source on the topic - otherwise, it ignores you and you don't get ranked Define the URLs End result: List of all the entities and sub-entities about the main site topic in the form of categories and subcategories respectively. A complete list of ALL the questions about the main focus and at around 10 questions for each one of the subcategories/subentities that are the secondary focus Content Writing So, now that there's a plan. Content needs to be produced. Pick out a keyword (which is going to be a question) and... Answer the question Write about 5 relevant entities Answer 10 relevant questions Write a conclusion Keep the format the same for all the articles. Content Uploading, formatting and onsite SEO Ensure the following is taken care of: H1 Permalink H2s H3s Lists Tables Meta description Socials description Featured image 2 images in text \\Schema Relevant YouTube video (if there is) Note: There are other pointers link internal linking in a semantically relevant way but this should be good to start with. Faster Indexing Indexing means Google has read your page. Ranking only after this step has been done. Otherwise, you can't rank if Google hasn't read the page. Naturally, this is a slow process. But, we expedite it in multiple ways. You can use RankMath to quickly index the content. Since, there are a lot of bulk pages you need a reliable method. Now, this method isn't perfect. But, it's better than most. Use Google Indexing API and developers tools to get indexed. Rank Math plugin is used. I don't want to bore you and write the process here. But, a simple Google search can help you set everything up. Additionally, whenever you post something - there will be an option to INDEX NOW. Just press that and it would be indexed quite fast. Conversion rate optimisation Once you get traffic, try adding tables right after the introduction of an article. These tables would feature a relevant product on Amazon. This step alone increased our earnings significantly. Even though the content is informational and NOT review. This still worked like a charm. Try checking out the top pages every single day in Google analytics and add the table to each one of them. Moreover, we used EZOIC video ads as well. That increased the RPM significantly as well. Both of these steps are highly recommended. Overall, we implemented over 11 fixations but these two contribute the most towards increasing the RPM so I would suggest you stick to these two in the start. Guest Posting We made additional income by selling links on the site as well. However, we were VERY careful about who we offered a backlink to. We didn't entertain any objectionable links. Moreover, we didn't actively reach out to anyone. We had a professional email clearly stated on the website and a particularly designated page for "editorial guidelines" A lot of people reached out to us because of that. As a matter of fact, the guy who bought the website is in the link selling business and plans to use the site primarily for selling links. According to him, he can easily make $4000+ from that alone. Just by replying to the prospects who reached out to us. We didn't allow a lot of people to be published on the site due to strict quality control. However, the new owner is willing to be lenient and cash it out. EEAT (Experience, Expertise, Authority, Trust) This is an important ranking factor. You need to prove on the site that your site has authors that are experienced, have expertise, authority and trust. A lot of people were reaching out to publish on our site and among them were a few established authors as well. We let them publish on our site for free, added them on our official team, connected their socials and shared them on all our socials. In return, we wanted them to write 3 articles each for us and share everything on all the social profiles. You can refer to the tables I shared above to check out the months it was implemented. We added a total of 6 writers (credible authors). Their articles were featured on the homepage and so were their profiles. Costing Well, we already had the site and the backlinks on it. Referring domains (backlinks) were already 500+. We just needed to focus on smart content and content. Here is the summary of the costs involved. Articles: 490 Avg word count per article: 1500 Total words: 735,000 (approximately) Cost per word: 2 cents (includes research, entities, production, quality assurance, uploading, formatting, adding images, featured image, alt texts, onsite SEO, publishing/scheduling etc.) Total: $14,700 ROI (Return on investment) Earning: Oct 22 - June 23 Earnings: $10,199 Sold for: $59,000 Total: $69,199 Expenses: Content: $14,700 Misc (hosting and others): $500 Total: $15,200 ROI over a 9 months period: 355.25% The plans moving forward This website was a part of a research and development experiment we did. With AI, we wanted to test new waters and transition more towards automation. Ideally, we want to use ChatGPT or some other API to produce these articles and bulk publish on the site. The costs with this approach are going to be much lower and the ROI is much more impressive. It's not the the 7-figures projects I created earlier (as you may have checked the older case studies on my profile), but it's highly scalable. We plan to refine this model even further, test more and automate everything completely to bring down our costs significantly. Once we have a model, we are going to scale it to 100s of sites. The process of my existing 7-figures websites portfolio was quite similar. I tested out a few sites, refined the model and scaled it to over 41 sites. Now, the fundamentals are the same however, we are using AI in a smarter way to do the same but at a lower cost, with a smaller team and much better returns. The best thing in my opinion is to run numerous experiments now. Our experimentation was slowed down a lot in the past since we couldn't write using AI but now it's much faster. The costs are 3-6 times lower so when it used to take $50-100k to start, grow and sell a site. Now you can pump 3-6 more sites for the same budget. This is a good news for existing business owners as well who want to grow their brand. Anyway, I am excited to see the results of more sites. In the meantime, if you have any questions - feel free to let me know. Best of luck for everything. Feel free to ask questions. I'd be happy to help. This is an AMA.

#reddit#[case#study]

reddit

0

1

mr_t_forhire•This week

Started a content marketing agency 6 years ago - $0 to $5,974,324 (2023 update)

Hey friends, My name is Tyler and for the past 6 years, I’ve been documenting my experience building a content marketing agency called Optimist. Year 1 - 0 to $500k ARR Year 2 - $500k to $1MM ARR Year 3 - $1MM ARR to $1.5MM(ish) ARR Year 4 - $3,333,686 Revenue Year 5 - $4,539,659 Revenue How Optimist Works First, an overview/recap of the Optimist business model: We operate as a “collective” of full time/professional freelancers Everyone aside from me is a contractor Entirely remote/distributed team Each freelancer earns $65-85/hour Clients pay us a flat monthly fee for full-service content marketing (research, strategy, writing, editing, design/photography, reporting and analytics, targeted linkbuilding, and more) We recently introduced hourly engagements for clients who fit our model but have some existing in-house support Packages range in price from $10-20k/mo We offer profit share to everyone on our core team as a way to give everyone ownership in the company In 2022, we posted $1,434,665 in revenue. It was our highest revenue year to date and brings our lifetime total to $5,974,324. Here’s our monthly revenue from January 2017 to December of 2022. But, like every year, it was a mix of ups and downs. Here’s my dispatch for 2023. — Running a business is like spilling a drink. It starts as a small and simple thing. But, if you don’t clean it up, the spill will spread and grow — taking up more space, seeping into every crack. There’s always something you could be doing. Marketing you could be working on. Pitches you could be making. Networking you could be doing. Client work you could help with. It can be all-consuming. And it will be — if you don’t clean up the spill. I realized this year that I had no containment for the spill that I created. Running an agency was spilling over into nearly every moment of my life. When I wasn’t working, I was thinking about work. When I wasn’t thinking about work, I was dreaming about it. Over the years, I’ve shared about a lot of my personal feelings and experience as an entrepreneur. And I also discussed my reckoning with the limitations of running the business we’ve built. My acceptance that it was an airplane but not a rocket. And my plan to try to compartmentalize the agency to make room in my life for other things — new business ideas, new revenue streams, and maybe some non-income-producing activity. 🤷 What I found in 2022 was that the business wasn’t quite ready for me to make that move. It was still sucking up too much of my time and attention. There were still too many gaps to fill and I was the one who was often filling them. So what do you do? Ultimately you have two choices on the table anytime you run a business and it’s not going the way you want it: Walk away Turn the ship — slowly For a huge number of reasons (personal, professional, financial, etc), walking away from Optimist was not really even an option or the right move for me. But it did feel like things needed to change. I needed to keep turning the ship to get it to the place where it fit into my life — instead of my life fitting around the business. This means 2022 was a year of transition for the agency. (Again?) Refocusing on Profit Some money is better than no money. Right? Oddly, this was one of the questions I found myself asking in 2022. Over the years, we’ve been fortunate to have many clients who have stuck with us a long time. In some cases, we’ve had clients work with us for 2, 3, or even 4 years. (That’s over half of our existence!) But, things have gotten more expensive — we’ve all felt it. We’ve had to increase pay to remain competitive for top talent. Software costs have gone up. It’s eaten into our margin. Because of our increasing costs and evolving scope, many of our best, most loyal clients were our least profitable. In fact, many were barely profitable — if at all. We’ve tried to combat that by increasing rates on new, incoming clients to reflect our new costs and try to make up for shrinking margin on long-term clients. But we didn’t have a good strategy in place for updating pricing for current clients. And it bit us in the ass. Subsidizing lower-profit, long-term clients with new, higher-margin clients ultimately didn’t work out. Our margins continued to dwindle and some months we were barely breaking even while posting six-figures of monthly revenue. 2022 was our highest revenue year but one of our least profitable. It only left one option. We had to raise rates on some of our long-term clients. But, of course, raising rates on a great, long-term client can be delicate. You’ve built a relationship with these people over the years and you’re setting yourself up for an ultimatum — are you more valuable to the client or is the client more valuable to you? Who will blink first? We offered all of these clients the opportunity to move to updated pricing. Unfortunately, some of them weren’t on board. Again, we had 2 options: Keep them at a low/no profit rate Let them churn It seems intuitive that having a low-profit client is better than having no client. But we’ve learned an important lesson many times over the years. Our business doesn’t scale infinitely and we can only handle so many clients at a time. That means that low-profit clients are actually costing us money in some cases. Say our average client generates $2,500 per month in profit — $30,000 per year. If one of our clients is only generating $500/mo in profit, working with them means missing out on bringing on a more profitable client (assuming our team is currently at capacity). Instead of $30,000/year, we’re only making $6,000. Keeping that client costs us $24,000. That’s called opportunity cost. So it’s clear: We had to let these clients churn. We decided to churn about 25% of our existing clients. On paper, the math made sense. And we had a pretty consistent flow of new opportunities coming our way. At the time, it felt like a no-brainer decision. And I felt confident that we could quickly replace these low-profit clients with higher-margin ones. I was wrong. Eating Shit Right after we initiated proactively churning some of our clients, other clients — ones we planned to keep — gave us notice that they were planning to end the engagement. Ouch. Fuck. We went from a 25% planned drop in revenue to a nearly 40% cliff staring us right in the face. Then things got even worse. Around Q3 of this year, talk of recession and layoffs really started to intensify. We work primarily with tech companies and startups. And these were the areas most heavily impacted by the economic news. Venture funding was drying up. Our leads started to slow down. This put us in a tough position. Looking back now, I think it’s clear that I made the wrong decision. We went about this process in the wrong way. The reality sinks in when you consider the imbalance between losing a client and gaining a client. It takes 30 days for someone to fire us. It’s a light switch. But it could take 1-3 months to qualify, close, and onboard a new client. We have lots of upfront work, research, and planning that goes into the process. We have to learn a new brand voice, tone, and style. It’s a marathon. So, for every client we “trade”, there’s a lapse in revenue and work. This means that, in retrospect, I would probably have made this transition using some kind of staggered schedule rather than a cut-and-dry approach. We could have gradually off-boarded clients when we had more definitive work to replace them. I was too confident. But that’s a lesson I had to learn the hard way. Rebuilding & Resetting Most of the voluntary and involuntary churn happened toward the end of 2022. So we’re still dealing with the fall out. Right now, it feels like a period of rebuilding. We didn’t quite lose 50% of our revenue, but we definitely saw a big hit heading into 2023. To be transparent: It sucks. It feels like a gigantic mistake that I made which set us back significantly from our previous high point. I acted rashly and it cost us a lot of money — at least on the surface. But I remind myself of the situation we were in previously. Nearly twice the revenue but struggling to maintain profitability. Would it have been better to try to slowly fix that situation and battle through months of loss or barely-break-even profits? Or was ripping off the bandaid the right move after all? I’m an optimist. (Heh, heh) Plus, I know that spiraling over past decisions won’t change them or help me move forward. So I’m choosing to look at this as an opportunity — to rebuild, reset, and refocus the company. I get to take all of the tough lessons I’ve learned over the last 6 years and apply them to build the company in a way that better aligns with our new and current goals. It’s not quite a fresh, clean start, but by parting ways with some of our oldest clients, we’ve eliminated some of the “debt” that’s accumulated over the years. We get a chance to fully realize the new positioning that we rolled out last year. Many of those long-term clients who churned had a scope of work or engagement structure that didn’t fit with our new positioning and focus. So, by losing them, we’re able to completely close up shop on the SOWs that no longer align with the future version of Optimist. Our smaller roster of clients is a better fit for that future. My job is to protect that positioning by ensuring that while we’re rebuilding our new roster of clients we don’t get desperate. We maintain the qualifications we set out for future clients and only take on work that fits. How’s that for seeing the upside? Some other upside from the situation is that we got an opportunity to ask for candid feedback from clients who were leaving. We asked for insight about their decision, what factors they considered, how they perceived us, and the value of our work. Some of the reasons clients left were obvious and possibly unavoidable. Things like budget cuts, insourcing, and uncertainty about the economy all played at least some part of these decisions. But, reading between the lines, where was one key insight that really struck me. It’s one of those, “oh, yeah — duh — I already knew that,” things that can be difficult to learn and easy to forget…. We’re in the Relationship Business (Plan Accordingly) For all of our focus on things like rankings, keywords, content, conversions, and a buffet of relevant metrics, it can be easy to lose the forest for the trees. Yes, the work itself matters. Yes, the outcomes — the metrics — matter. But sometimes the relationship matters more. When you’re running an agency, you can live or die by someone just liking you. Admittedly, this feels totally unfair. It opens up all kinds of dilemmas, frustration, opportunity for bias and prejudice, and other general messiness. But it’s the real world. If a client doesn’t enjoy working with us — even if for purely personal reasons — they could easily have the power to end of engagement, regardless of how well we did our actual job. We found some evidence of this in the offboarding conversations we had with clients. In some cases, we had clients who we had driven triple- and quadruple-digital growth. Our work was clearly moving the needle and generating positive ROI and we had the data to prove it. But they decided to “take things in another direction” regardless. And when we asked about why they made the decision, it was clear that it was more about the working relationship than anything we could have improved about the service itself. The inverse is also often true. Our best clients have lasting relationships with our team. The work is important — and they want results. But even if things aren’t quite going according to plan, they’re patient and quick to forgive. Those relationships feel solid — unshakeable. Many of these folks move onto new roles or new companies and quickly look for an opportunity to work with us again. On both sides, relationships are often more important than the work itself. We’ve already established that we’re not building a business that will scale in a massive way. Optimist will always be a small, boutique service firm. We don’t need 100 new leads per month We need a small, steady roster of clients who are a great fit for the work we do and the value we create. We want them to stick around. We want to be their long-term partner. I’m not built for churn-and-burn agency life. And neither is the business. When I look at things through this lens, I realize how much I can cut from our overall business strategy. We don’t need an ultra-sophisticated, multi-channel marketing strategy. We just need strong relationships — enough of them to make our business work. There are a few key things we can take away from this as a matter of business strategy: Put most of our effort into building and strengthening relationships with our existing clients Be intentional about establishing a strong relationship with new clients as part of onboarding Focus on relationships as the main driver of future business development Embracing Reality: Theory vs Practice Okay, so with the big learnings out the way, I want to pivot into another key lesson from 2022. It’s the importance of understanding theory vs practice — specifically when it comes to thinking about time, work, and life. It all started when I was considering how to best structure my days and weeks around running Optimist, my other ventures, and my life goals outside of work. Over the years, I’ve dabbled in many different ways to block time and find focus — to compartmentalize all of the things that are spinning and need my attention. As I mapped this out, I realized that I often tried to spread myself too thin throughout the week. Not just that I was trying to do too much but that I was spreading that work into too many small chunks rather than carving out time for focus. In theory, 5 hours is 5 hours. If you have 5 hours of work to get done, you just fit into your schedule whenever you have an open time slot. In reality, a single 5-hour block of work is 10x more productive and satisfying than 10, 30-minute blocks of work spread out across the week. In part, this is because of context switching. Turning your focus from one thing to another thing takes time. Achieving flow and focus takes time. And the more you jump from one project to another, the more time you “lose” to switching. This is insightful for me both in the context of work and planning my day, but also thinking about my life outside of Optimist. One of my personal goals is to put a finite limit on my work time and give myself more freedom. I can structure that in many different ways. Is it better to work 5 days a week but log off 1 hour early each day? Or should I try to fit more hours into each workday so I can take a full day off? Of course, it’s the latter. Both because of the cost of context switching and spreading work into more, smaller chunks — but also because of the remainder that I end up with when I’m done working. A single extra hour in my day probably means nothing. Maybe I can binge-watch one more episode of a new show or do a few extra chores around the house. But it doesn’t significantly improve my life or help me find greater balance. Most things I want to do outside of work can’t fit into a single extra hour. A full day off from work unlocks many more options. I can take the day to go hiking or biking. I can spend the day with my wife, planning or playing a game. Or I can push it up against the weekend and take a 3-day trip. It gives me more of the freedom and balance that I ultimately want. So this has become a guiding principle for how I structure my schedule. I want to: Minimize context switching Maximize focused time for work and for non-work The idea of embracing reality also bleeds into some of the shifts in business strategy that I mentioned above. In theory, any time spent on marketing will have a positive impact on the company. In reality, focusing more on relationships than blasting tweets into the ether is much more likely to drive the kind of growth and stability that we’re seeking. As I think about 2023, I think this is a recurring theme. It manifests in many ways. Companies are making budget cuts and tough decisions about focus and strategy. Most of us are looking for ways to rein in the excess and have greater impact with a bit less time and money. We can’t do everything. We can’t even do most things. So our #1 priority should be to understand the reality of our time and our effort to make the most of every moment (in both work and leisure). That means thinking deeply about our strengths and our limitations. Being practical, even if it feels like sacrifice. Update on Other Businesses Finally, I want to close up by sharing a bit about my ventures outside of Optimist. I shared last year how I planned to shift some of my (finite) time and attention to new ventures and opportunities. And, while I didn’t get to devote as much as I hoped to these new pursuits, they weren’t totally in vain. I made progress across the board on all of the items I laid out in my post. Here’s what happened: Juice: The first Optimist spin-out agency At the end of 2021, we launched our first new service business based on demand from Optimist clients. Focused entirely on building links for SEO, we called the agency Juice. Overall, we made strong progress toward turning this into a legitimate standalone business in 2022. Relying mostly on existing Optimist clients and a few word-of-mouth opportunities (no other marketing), we built a team and set up a decent workflow and operations. There’s still many kinks and challenges that we’re working through on this front. All told, Juice posted almost $100,000 in revenue in our first full year. Monetizing the community I started 2022 with a focus on figuring out how to monetize our free community, Top of the Funnel. Originally, my plan was to sell sponsorships as the main revenue driver. And that option is still on the table. But, this year, I pivoted to selling paid content and subscriptions. We launched a paid tier for content and SEO entrepreneurs where I share more of my lessons, workflows, and ideas for building and running a freelance or agency business. It’s gained some initial traction — we reached \~$1,000 MRR from paid subscriptions. In total, our community revenue for 2022 was about $2,500. In 2023, I’m hoping to turn this into a $30,000 - $50,000 revenue opportunity. Right now, we’re on track for \~$15,000. Agency partnerships and referrals In 2022, we also got more serious about referring leads to other agencies. Any opportunity that was not a fit for Optimist or we didn’t have capacity to take on, we’d try to connect with another partner. Transparently, we struggled to operationalize this as effectively as I would have liked. In part, this was driven by my lack of focus here. With the other challenges throughout the year, I wasn’t able to dedicate as much time as I’d like to setting goals and putting workflows into place. But it wasn’t a total bust. We referred out several dozen potential clients to partner agencies. Of those, a handful ended up converting into sales — and referral commission. In total, we generated about $10,000 in revenue from referrals. I still see this as a huge opportunity for us to unlock in 2023. Affiliate websites Lastly, I mentioned spending some time on my new and existing affiliate sites as another big business opportunity in 2022. This ultimately fell to the bottom of my list and didn’t get nearly the attention I wanted. But I did get a chance to spend a few weeks throughout the year building this income stream. For 2022, I generated just under $2,000 in revenue from affiliate content. My wife has graciously agreed to dedicate some of her time and talent to these projects. So, for 2023, I think this will become a bit of a family venture. I’m hoping to build a solid and consistent workflow, expand the team, and develop a more solid business strategy. Postscript — AI, SEO, OMG As I’m writing this, much of my world is in upheaval. If you’re not in this space (and/or have possibly been living under a rock), the release of ChatGPT in late 2022 has sparked an arms race between Google, Bing, OpenAI, and many other players. The short overview: AI is likely to fundamentally change the way internet search works. This has huge impact on almost all of the work that I do and the businesses that I run. Much of our focus is on SEO and understanding the current Google algorithm, how to generate traffic for clients, and how to drive traffic to our sites and projects. That may all change — very rapidly. This means we’re standing at a very interesting point in time. On the one hand, it’s scary as hell. There’s a non-zero chance that this will fundamentally shift — possibly upturn — our core business model at Optimist. It could dramatically change how we work and/or reduce demand for our core services. No bueno. But it’s also an opportunity (there’s the optimist in me, again). I certainly see a world where we can become leaders in this new frontier. We can pivot, adjust, and capitalize on a now-unknown version of SEO that’s focused on understanding and optimizing for AI-as-search. With that, we may also be able to help others — say, those in our community? — also navigate this tumultuous time. See? It’s an opportunity. I wish I had the answers right now. But, it’s still a time of uncertainty. I just know that there’s a lot of change happening and I want to be in front of it rather than trying to play catch up. Wish me luck. — Alright friends — that's my update for 2023! I’ve always appreciated sharing these updates with the Reddit community, getting feedback, being asked tough questions, and even battling it out with some of my haters (hey!! 👋) As usual, I’m going to pop in throughout the next few days to respond to comments or answer questions. Feel free to share thoughts, ideas, and brutal takedowns in the comments. If you're interested in following the Optimist journey and the other projects I'm working on in 2023, you can follow me on Twitter. Cheers, Tyler P.S. - If you're running or launching a freelance or agency business and looking for help figuring it out, please DM me. Our subscription community, Middle of the Funnel, was created to provide feedback, lessons, and resources for other entrepreneurs in this space.

#reddit#started#content

reddit

0

1

AntsyNursery58•This week

AI Will Make You Extremely Rich or Kill Your Business in 2024

Preface: I'm a solo-founder in the AI space and previously worked as an ML scientist; the new advancements in AI that I'm seeing are going to impact everyone here. It doesn't matter if you're just starting out, or a bootstrapped brick and mortar founder, or even a VC backed hard tech founder. Last year was when the seeds were laid, and this is the year we'll see them bloom. There will be an onslaught of advancements that take place that are borderline inconceivable due to the nature of exponential progress. This will change every single vertical. I'm making this post because I think AI execution strategy will make or break businesses. Dramatically. Over $50B was put into AI startups in 2023 alone. This figure excludes the hundreds of billions poured into AI from enterprises. So, let's follow the money: &#x200B; 1) AI enterprise software. There's a lot to unpack here and this is what I’m currently working on. AI enterprise software will encompass everything from hyper personalized email outbound to AI cold calls to AI that A/B tests ads on synthetic data to vertical specific software. The impact of the former is relatively self explanatory, so I'll focus on the latter. To illustrate vertical specific AI software, I'll use a simple example in the legal space. Lawyers typically have to comb through thousands of pages of documents. Now, using an LLM + a VDB, an AI can instantly answer all of those questions while surfacing the source and highlighting the specific answer in the contract/document. There are dozens of AI startups for this use case alone. This saves lawyers an immense amount of time and allows them to move faster. Firms that adopt this have a fundamental advantage over law firms that don't adopt this. This was 2023 technology. I'm seeing vertical AI software getting built by my friends in areas from construction, to real estate, to even niche areas like chimney manufacturing. This will exist everywhere. Now, this can be extrapolated much further to be applicable to systems that can do reports and even browse the Internet. This brings me to my next point. &#x200B; 2) AI information aggregation and spread. My gut tells me that this will have a crescendo moment in the future with hardware advancements (Rabbit, Tab, etc.). You won't have to google things because it will be surfaced to you. It's predictive in nature. The people who can get information the fastest will grow their business the fastest. This part is semi-speculative, but due to the nature of LLMs being so expensive to train, I have a strong feeling that large institutions will have access to the \fastest\ and \best\ models that can do this quicker than you and I can. This is why it's important to stay on top. &#x200B; 3) AI content generation This is relevant to running advertisements and any digital marketing aspect of your business. If you can rapidly make content faster than your competitors to put in social media, you will outpace your competitors rapidly. I think most folks are familiar with MidJourney, Stable diffusion, etc. but don't know how to use it. You can generate consistent models for a clothing brand or generate images of a product that you would normally need to hire a professional photographer to take. There's also elevenlabs which is relatively easy to use and can be used to make an MP3 clip as a narration for an ad; this is something I've already done. I'm also still shocked by how many people are unfamiliar with tools like Pika which can do video generation. You could imagine companies having fleets of digital influencers that they control or conjuring up the perfect ad for a specific demographic using a combination of all of the aforementioned tools. &#x200B; In summary, if you feel like I'm being hyperbolic or propagating science fiction fantasies, you're likely already behind. I truly recommend that everyone stays up to date on these advancements as much as possible. If your competitor comes across an AI tool that can increase their ROAS by 5x they can crush you. If your competitor uses a tool that increases the rate at which they receive and aggregate information by 200% (modest estimate) they will crush you. If your competitors have a tool that can reduce their employee size, then they will use it. They'll fire their employees to cut costs and reinvest the money back into their business. It will compound to the point where you're outpaced, and this isn't a level of innovation we've seen since the birth of the industrial revolution. Your customers can get stolen overnight, or you can steal your competition’s customers overnight. TL;DR: This is an opportunity for entrepreneurs to scale faster than they could have possibly imagined, but this also comes with the potential for your company to be obliterated. We've never seen advancements that can have this drastic of an impact this quickly. Adoption will happen fast, and first movers will have a disproportionate and compounding advantage. Watch guides, meet with startups, follow the news, and get rich.

#reddit#will#make

reddit

0

1

Current-Payment-5403•This week

Beginner to the 1st sale: my journey building an AI for social media marketers

Hey everyone! Here’s my journey building an AI for social media marketers all the way up until my first pre-launch sale, hope that could help some of you: My background: studied maths at uni before dropping out to have some startup experiences. Always been drawn to building new things so I reckoned I would have some proper SaaS experiences and see how VC-funded startups are doing it before launching my own.  I’ve always leaned towards taking more risks in my life so leaving my FT job to launch my company wasn’t a big deal for me (+ I’m 22 so still have time to fail over and over). When I left my job, I started reading a lot about UI/UX, no-code tools, marketing, sales and every tool a worthwhile entrepreneur needs to learn about. Given the complexity of the project I set out to achieve, I asked a more technical friend to join as a cofounder and that's when AirMedia was born. We now use bubble for landing page as I had to learn it and custom-code stack for our platform.  Here's our goal: streamlining social media marketing using AI. I see this technology has only being at the premises of what it will be able to achieve in the near-future. We want to make the experience dynamic i.e. all happens from a discussion and you see the posts being analysed from there as well as the creation process - all from within the chat. Fast forward a few weeks ago, we finished developing the first version of our tool that early users describe as a "neat piece of tech" - just this comment alone can keep me going for months :) Being bootstrapped until now, I decided to sell lifetime deals for the users in the waitlist that want to get the tool in priority as well as secure their spot for life. We've had the first sale the first day we made that public ! Now what you all are looking for: How ?  Here was my process starting to market the platform: I need a high-converting landing page so I reckoned which companies out there have the most data and knows what convert and what doesn’t: Unbounce. Took their landing page and adapted it to my value proposition and my ICP.  The ICP has been defined from day 1 and although I’m no one to provide any advice, I strongly believe the ICP has to be defined from day 1 (even before deciding the name of the company). It helps a lot when the customer is you and you’ve had this work experience that helps you identify the problems your users encounter. Started activating the network, posting on Instagram and LinkedIn about what we've built (I've worked in many SaaS start-ups in the past so I have to admit that's a bit of a cheat code). Cold outreach from Sales NAV to our ICP, been growing the waitlist in parallel of building the tool for months now so email marketings with drip sequences and sharing dev updates to build the trust along the way (after all we're making that tool for our users - they should be the first aware about what we're building). I also came across some Whatsapp groups with an awesome community that welcomed our platform with excitement.) The landing page funnel is the following: Landing page -> register waitlist -> upsell page -> confirmation. I've made several landing pages e.g. for marketing agencies, for real estate agents, for marketing director in several different industries. The goal now is just testing out the profiles and who does it resonate the most with. Another growth hack that got us 40+ people on the waitlist: I identified some Instagram posts from competitors where their CTA was "comment AI" and I'll send you our tool and they got over 2k people commenting. Needless to say, I messaged every single user to check out our tool and see if it could help them. (Now that i think about it, the 2% conversion rate there is not great - especially considering the manual labour and the time put behind it). We’ve now got over 400 people on the waitlist so I guess we’re doing something right but we’ll keep pushing as the goal is to sell these lifetime deals to have a strong community to get started. (Also prevents us from going to VCs and I can keep my time focussing exclusively on our users - I’m not into boardroom politics, just wanna build something useful for marketers). Now I’m still in the process of testing out different marketing strategies while developing and refining our platform to make it next level on launch day. Amongst those:  LinkedIn Sales Nav outreach (first sale came from there) Product Hunt Highly personalised cold emails (there I’m thinking of doing 20 emails a day with a personalised landing page to each of those highly relevant marketers). Never seen that and I think this could impress prospects but not sure it’s worth it time / conversion wise. Make content to could go viral (at least 75 videos) that I’m posting throughout several social media accounts such as airmedia\\, airmedia\reels, airmedia\ai (you get the hack) always redirecting to the main page both in the profile description and tagging the main account. I have no idea how this will work so will certainly update some of you that would like to know the results. Will do the same across Facebook, TikTok, Youtube Shorts etc… I’m just looking for a high potential of virality there. This strategy is mainly used to grow personal brands but never seen it applied to companies. Good old cold calling Reddit (wanna keep it transparent ;) ) I’m alone to execute all these strategies + working in parallel to refine the product upon user’s feedback I’m not sure I can do more than that for now. Let me know if you have any feedback/ideas/ tasks I could implement.  I could also make another post about the proper product building process as this post was about the marketing. No I certainly haven’t accomplished anything that puts me in a position to provide advices but I reckon I’m on my way to learn more and more. Would be glad if this post could help some of you.  And of course as one of these marketing channels is Reddit I’ll post the link below for the entrepreneurs that want to streamline their social media or support us. Hope I was able to provide enough value in this post for you to consider :) https://airmedia.uk/

#reddit#beginner#sale:

reddit

0

1

tilopedia•This week

My Side Projects: From CEO to 4th Developer (Thanks, AI 🤖)

Hey Reddit 👋, I wanted to share a bit about some side projects I’ve been working on lately. Quick background for context: I’m the CEO of a mid-to-large-scale eCommerce company pulling in €10M+ annually in net turnover. We even built our own internal tracking software that’s now a SaaS (in early review stages on Shopify), competing with platforms like Lifetimely and TrueROAS. But! That’s not really the point of this post — there’s another journey I’ve been on that I’m super excited to share (and maybe get your feedback on!). AI Transformed My Role (and My Ideas List) I’m not a developer by trade — never properly learned how to code, and to be honest, I don’t intend to. But, I’ve always been the kind of guy who jots down ideas in a notes app and dreams about execution. My dev team calls me their “4th developer” (they’re a team of three) because I have solid theoretical knowledge and can kinda read code. And then AI happened. 🛠️ It basically turned my random ideas app into an MVP generation machine. I thought it’d be fun to share one of the apps I’m especially proud of. I am also planning to build this in public and therefore I am planning to post my progress on X and every project will have /stats page where live stats of the app will be available. Tackling My Task Management Problem 🚀 I’ve sucked at task management for YEARS, I still do! I’ve tried literally everything — Sheets, Todoist, Asana, ClickUp, Notion — you name it. I’d start… and then quit after a few weeks - always. What I struggle with the most is delegating tasks. As a CEO, I delegate a ton, and it’s super hard to track everything I’ve handed off to the team. Take this example: A few days ago, I emailed an employee about checking potential collaboration opportunities with a courier company. Just one of 10s of tasks like this I delegate daily. Suddenly, I thought: “Wouldn’t it be AMAZING if just typing out this email automatically created a task for me to track?” 💡 So… I jumped in. With the power of AI and a few intense days of work, I built a task manager that does just that. But of course, I couldn’t stop there. Research & Leveling It Up 📈 I looked at similar tools like TickTick and Todoist, scraped their G2 reviews (totally legally, promise! 😅), and ran them through AI for a deep SWOT analysis. I wanted to understand what their users liked/didn’t like and what gaps my app could fill. Some of the features people said they were missing didn’t align with the vision for my app (keeping it simple and personal), but I found some gold nuggets: Integration with calendars (Google) Reminders Customizable UX (themes) So, I started implementing what made sense and am keeping others on the roadmap for the future. And I’ve even built for that to, it still doesn’t have a name, however the point is you select on how many reviews of a specific app you want to make a SWOT analysis on and it will do it for you. Example for Todoist in comments. But more on that, some other time, maybe other post ... Key Features So Far: Here’s what’s live right now: ✅ Email to Task: Add an email as to, cc, or bcc — and it automatically creates a task with context, due dates, labels, etc. ✅ WhatsApp Reminders: Get nudged to handle your tasks via WhatsApp. ✅ WhatsApp to Task: Send a message like /task buy groceries — bam, it’s added with full context etc.. ✅ Chrome Extension (work-in-progress): Highlight text on any page, right-click, and send it straight to your task list. Next Steps: Build WITH the Community 👥 Right now, the app is 100% free while still in the early stages. But hey, API calls and server costs aren’t cheap, so pricing is something I’ll figure out with you as we grow. For now, my goal is to hit 100 users and iterate from there. My first pricing idea is, without monthly subscription, I don’t want to charge someone for something he didn’t use. So I am planning on charging "per task", what do you think? Here’s what I have planned: 📍 End of Year Goal: 100 users (starting from… 1 🥲). 💸 Revenue Roadmap: When we establish pricing, we’ll talk about that. 🛠️ Milestones: Post on Product Hunt when we hit 100 users. Clean up my self-written spaghetti code (hire a pro dev for review 🙃). Hire a part-time dev once we hit MRR that can cover its costs. You can check how are we doing on thisisatask.me/stats Other Side Projects I’m Working On: Because… what’s life without taking on too much, right? 😂 Full list of things I’m building: Internal HRM: Not public, tried and tested in-house. Android TV App: Syncs with HRM to post announcements to office TVs (streamlined and simple). Stats Tracker App: Connects to our internal software and gives me real-time company insights. Review Analyzer: Scrapes SaaS reviews (e.g., G2) and runs deep analysis via AI. This was originally for my Shopify SaaS but is quickly turning into something standalone. Coming soon! Mobile app game: secret for now. Let’s Build This Together! Would love it if you guys checked out thisisatask.me and gave it a spin! Still super early, super raw, but I’m pumped to hear your thoughts. Also, what’s a must-have task manager feature for you? Anything that frustrates you with current tools? I want to keep evolving this in public, so your feedback is gold. 🌟 Let me know, Reddit! Are you with me? 🙌

#reddit#side#projects:

reddit

0

0.882

mr_t_forhire•This week

Started a content marketing agency 8 years ago - $0 to $7,863,052 (2025 update)

Hey friends, My name is Tyler and for the past 8 years, I’ve been documenting my experience building a content marketing agency called Optimist. Year 1 — 0 to $500k ARR Year 2 — $500k to $1MM ARR Year 3 — $1MM ARR to $1.5MM(ish) ARR Year 4 — $3,333,686 Revenue Year 5 — $4,539,659 Revenue Year 6 — $5,974,324 Revenue Year 7 - $6,815,503 Revenue (Edit: Seems like links are banned now. You can check my post history for all of my previous updates with lessons and learnings.) How Optimist Works First, an overview/recap of the Optimist business model: We operate as a “collective” of full time/professional freelancers Everyone aside from me is a contractor Entirely remote/distributed team We pay freelancers a flat fee for most work, working out to roughly $65-100/hour. Clients pay us a flat monthly fee for full-service content marketing (research, strategy, writing, editing, design/photography, reporting and analytics, targeted linkbuilding, and more)\ Packages range in price from \~$10-20k/mo \This is something we are revisiting now* The Financials In 2024, we posted $1,032,035.34 in revenue. This brings our lifetime revenue to $7,863,052. Here’s our monthly revenue from January 2017 to December of 2024. (Edit: Seems like I'm not allowed to link to the chart.) The good news: Revenue is up 23% YoY. EBITDA in Q4 trending up 1-2 points. We hosted our first retreat in 4 years, going to Ireland with about half the team. The bad news: Our revenue is still historically low. At $1MM for the year, we’re down about 33% from our previous years over $1.5MM. Revenue has been rocky. It doesn’t feel like we’ve really “recovered” from the bumps last year. The trend doesn’t really look great. Even though, anecdotally, it feels like we are moving in a good direction. EBITDA is still hovering at around 7%. Would love to get that closer to 20%. (For those who may ask: I’m calculating EBITDA after paying taxes and W2 portion of my income.) — Almost every year, my update starts the same way: This has been a year of growth and change. Both for my business—and me personally. 2024 was no different. I guess that tells you something about entrepreneurship. It’s a lot more like sailing a ship than driving a car. You’re constantly adapting, tides are shifting, and any blip of calm is usually just a moment before the next storm. As with past years, there’s a lot to unpack from the last 12 months. Here we go again. Everything is Burning In the last 2 years, everything has turned upside down in the world of content and SEO. Back in 2020, we made a big decision to re-position the agency. (See post history) We decided to narrow our focus to our most successful, profitable, and consistent segment of clients and re-work our entire operation to focus on serving them. We defined our ICP as: \~Series A ($10mm+ funding) with 6-12 months runway to scale organic as a channel Product-led company with “simple” sales cycle involving fewer stakeholders Demonstrable opportunity to use SEO to drive business growth Our services: Content focused on growing organic search (SEO) Full-service engagements that included research, planning, writing, design, reporting And our engagement structure: Engaged directly with an executive; ownership over strategy and day-to-day execution 1-2 points of contact or stakeholders Strategic partner that drives business growth (not a service vendor who makes content) Most importantly, we decided that we were no longer going to offer a broader range of content that we used to sell. That included everything from thought leadership content to case studies and ebooks. We doubled-down on “SEO content” for product-led SaaS companies. And this worked phenomenally for us. We started bringing on more clients than ever. We developed a lot of internal system and processes that helped us scale and take on more work than we’ve ever had and drive great outcomes for our ideal clients. But in 2023 and 2024, things started going awry. One big change, of course, was the rise of AI. Many companies and executives (and writers) feel that AI can write content just as well as an agency like ours. That made it a lot harder to sell a $10,000 per month engagement when they feel like the bulk of the work could be “done for free.” (Lots of thoughts on this if you want my opinions.) But it wasn’t just that. Google also started tinkering with their algorithm, introducing new features like AI Overviews, and generally changing the rules of the game. This created 3 big shifts in our world: The perceived value of content (especially “SEO content”) dropped dramatically in many people’s minds because of AI’s writing capabilities SEO became less predictable as a source of traffic and revenue It’s harder than ever for startups and smaller companies to rank for valuable keywords (let alone generate any meaningful traffic or revenue from them) The effect? The middle of the content market has hollowed out. People—like us—providing good, human-crafted content aimed on driving SEO growth saw a dramatic decline in demand. We felt it all year. Fewer and fewer leads. The leads we did see usually scoffed at our prices. They were indexing us against the cost of content mills and mass-produced AI articles. It was a time of soul-searching and looking for a way forward. I spent the first half of the year convinced that the only way to survive was to run toward the fire. We have to build our own AI workflows. We have to cut our rates internally. We have to get faster and cheaper to stay competitive with the agencies offering the same number of deliverables for a fraction of our rates. It’s the only way forward. But then I asked myself a question… Is this the game I actually want to play? As an entrepreneur, do I want to run a business where I’m competing mostly on price and efficiency rather than quality and value? Do I want to hop into a race toward cheaper and cheaper content? Do I want to help people chase a dwindling amount of organic traffic that’s shrinking in value? No. That’s not the game I want to play. That’s not a business I want to run. I don’t want to be in the content mill business. So I decided to turn the wheel—again. Repositioning Part II: Electric Boogaloo What do you do when the whole world shifts around you and the things that used to work aren’t working anymore? You pivot. You re-position the business and move in another direction. So that’s what we decided to do. Again. There was only one problem: I honestly wasn’t sure what opportunities existed in the content marketing industry outside of what we were already doing. We lived in a little echo chamber of startups and SEO. It felt like the whole market was on fire and I had fight through the smoke to find an escape hatch. So I started making calls. Good ol’ fashioned market research. I reached out to a few dozen marketing and content leaders at a bunch of different companies. I got on the phone and just asked lots of questions about their content programs, their goals, and their pain points. I wanted to understand what was happening in the market and how we could be valuable. And, luckily, this process really paid off. I learned a lot about the fragmentation happening across content and how views were shifting. I noticed key trends and how our old target market really wasn’t buying what we were selling. Startups and small companies are no longer willing to invest in an agency like ours. If they were doing content and SEO at all, they were focused entirely on using AI to scale output and minimize costs. VC money is still scarce and venture-backed companies are more focused on profitability than pure growth and raising another round. Larger companies (\~500+ employees) are doing more content than ever and drowning in content production. They want to focus on strategy but can barely tread water keeping up with content requests from sales, demand gen, the CEO, and everyone else. Many of the companies still investing in content are looking at channels and formats outside of SEO. Things like thought leadership, data reports, interview-driven content, and more. They see it as a way to stand out from the crowd of “bland SEO content.” Content needs are constantly in flux. They range from data reports and blog posts to product one-pagers. The idea of a fixed-scope retainer is a total mismatch for the needs of most companies. All of this led to the logical conclusion: We were talking to the wrong people about the wrong things\.\ Many companies came to one of two logical conclusions: SEO is a risky bet, so it’s gotta be a moonshot—super-low cost with a possibility for a big upside (i.e., use AI to crank out lots of content. If it works, great. If it doesn’t, then at least we aren’t out much money.) SEO is a risky bet, so we should diversify into other strategies and channels to drive growth (i.e., shift our budget from SEO and keyword-focused content to video, podcasts, thought leadership, social, etc) Unless we were going to lean into AI and dramatically cut our costs and rates, our old buyers weren’t interested. And the segment of the market that needs our help most are looking primarily for production support across a big range of content types. They’re not looking for a team to run a full-blown program focused entirely on SEO. So we had to go back to the drawing board. I’ve written before about our basic approach to repositioning the business. But, ultimately it comes down to identifying our unique strengths as a team and then connecting them to needs in the market. After reviewing the insights from my discussions and taking another hard look at our business and our strengths, I decided on a new direction: Move upmarket: Serve mid-size to enterprise businesses with \~500-5,000 employees instead of startups Focus on content that supports a broader range of business goals instead of solely on SEO and organic growth (e.g., sales, demand gen, brand, etc) Shift back to our broader playbook of content deliverables, including thought leadership, data studies, and more Focus on content execution and production to support an internally-directed content strategy across multiple functions In a way, it’s sort of a reverse-niche move. Rather than zooming in specifically on driving organic growth for startups, we want to be more of an end-to-end content production partner that solves issues of execution and operations for all kinds of content teams. It’s early days, but the response here has been promising. We’ve seen an uptick in leads through Q4. And more companies in our pipeline fit the new ICP. They’re bigger, often have more budget. (But they move more slowly). We should know by the end of the quarter if this maneuver is truly paying off. Hopefully, this will work out. Hopefully our research and strategy are right and we’ll find a soft landing serving a different type of client. If it doesn’t? Then it will be time to make some harder decisions. As I already mentioned, I’m not interested in the race to the bottom of AI content. And if that’s the only game left in town, then it might be time to think hard about a much bigger change. — To be done: Build new content playbooks for expanded deliverables Build new showcase page for expanded deliverables Retooling the Operation It’s easy to say we’re doing something new. It’s a lot harder to actually do it—and do it well. Beyond just changing our positioning, we have to do open-heart surgery on the entire content operation behind the scenes. We need to create new systems that work for a broader range of content types, formats, and goals. Here’s the first rub: All of our workflows are tooled specifically for SEO-focused content. Every template, worksheet, and process that we’ve built and scaled in the last 5 years assumes that the primary goal of every piece of content is SEO. Even something as simple as requiring a target keyword is a blocker in a world where we’re not entirely focused on SEO. This is relatively easy to fix, but it requires several key changes: Update content calendars to make keywords optional Update workflows to determine whether we need an optimization report for each deliverable Next, we need to break down the deliverables into parts rather than a single line item. In our old system, we would plan content as a single row in a Content Calendar spreadsheet. It was a really wide sheet with lots of fields where we’d define the dimensions of each individual article. This was very efficient and simple to follow. But every article had the same overall scope when it came to the workflow. In Asana (our project management tool), all of the steps in the creation were strung together in a single task. We would create a few basic templates for each client, and then each piece would flow through the same steps: Briefing Writing Editing Design etc. If we had anything that didn’t fit into the “standard” workflow, we’d just tag it in the calendar with an unofficial notation \[USING BRACKETS\]. It worked. But it wasn’t ideal. Now we need the steps to be more modular. Imagine, for example, a client asks us to create a mix of deliverables: 1 article with writing + design 1 content brief 1 long-form ebook with an interview + writing + design Each of these would require its own steps and its own workflow. We need to break down the work to accommodate for a wider variety of workflows and variables. This means we need to update the fields and structure of our calendar to accommodate for the new dimensions—while also keeping the planning process simple and manageable. This leads to the next challenge: The number of “products” that we’re offering could be almost infinite. Just looking at the example scope above, you can mix and match all of these different building blocks to create a huge variety of different types of work, each requiring its own workflow. This is part of the reason we pivoted away from this model to focus on a productized, SEO-focused content service back in 2020. Take something as simple as a case study. On the surface, it seems like one deliverable that can be easily scoped and priced, right? Well, unpack what goes into a case study: Is there already source material from the customer or do we need to conduct an interview? How long is it? Is it a short overview case study or a long-form narrative? Does it need images and graphics? How many? Each of these variables opens up 2-3 possibilities. And when you combine them, we end up with something like 10 possible permutations for this single type of deliverable. It gets a bit messy. But not only do we have to figure out how to scope and price all for all of these variables, we also have to figure out how to account for these variables in the execution. We have to specify—for every deliverable—what type it is, how long, which steps are involved and not involved, the timeline for delivery, and all of the other factors. We’re approaching infinite complexity, here. We have to figure out a system that allows for a high level of flexibility to serve the diverse needs of our clients but is also productized enough that we can build workflows, process, and templates to deliver the work. I’ve spent the last few months designing that system. Failed Attempt #1: Ultra-Productization In my first pass, I tried to make it as straight forward as possible. Just sit down, make a list of all of the possible deliverables we could provide and then assign them specific scopes and services. Want a case study? Okay that’ll include an interview, up to 2,000 words of content, and 5 custom graphics. It costs $X. But this solution quickly fell apart when we started testing it against real-world scenarios. What if the client provided the brief instead of us creating one? What if they didn’t want graphics? What if this particular case study really needs to be 3,000 words but all of the others should be 2,000? In order for this system to work, we’d need to individual scope and price all of these permutations of each productized service. Then we’d need to somehow keep track of all of these and make sure that we accurately scope, price, and deliver them across dozens of clients. It’s sort of like a restaurant handling food allergies by creating separate versions of every single dish to account for every individual type of allergy. Most restaurants have figured out that it makes way more sense to have a “standard” and an “allergy-free” version. Then you only need 2 options to cover 100% of the cases. Onto the next option. Failed Attempt #2: Deliverable-Agnostic Services Next, I sat down with my head of Ops, Katy, to try to map it out. We took a big step back and said: Why does the deliverable itself even matter? At the end of the day, what we’re selling is just a few types of work (research, writing, editing, design, etc) that can be packaged up in an infinite number of ways. Rather than try to define deliverables, shouldn’t we leave it open ended for maximum flexibility? From there, we decided to break down everything into ultra-modular building blocks. We started working on this super complex system of modular deliverables where we would have services like writing, design, editing, etc—plus a sliding scale for different scopes like the length of writing or the number of images. In theory, it would allow us to mix and match any combination of services to create custom deliverables for the client. In fact, we wanted the work to be deliverable-agnostic. That way we could mold it to fit any client’s needs and deliver any type of content, regardless of the format or goal. Want a 5,000-word case study with 15 custom graphics? That’ll be $X. Want a 2,000-word blog post with an interview and no visuals? $Y. Just want us to create 10 briefs, you handle the writing, and we do design? It’s $Z. Again, this feels like a reasonable solution. But it quickly spiraled out of amuck. (That’s an Office reference.) For this to work, we need to have incredibly precise scoping process for every single deliverable. Before we can begin work (or even quote a price), we need to know pretty much the exact word count of the final article, for example. In the real world? This almost never happens. The content is as long as the content needs to be. Clients rarely know if the blog post should be 2,000 words or 3,000 words. They just want good content. We have a general ballpark, but we can rarely dial it in within just 1,000 words until we’ve done enough research to create the brief. Plus, from a packaging and pricing perspective, it introduces all kind of weird scenarios where clients will owe exactly $10,321 for this ultra-specific combination of services. We were building an open system that could accommodate any and all types of potential deliverables. On the face that seems great because it makes us incredibly flexible. In reality, the ambiguity actually works against us. It makes it harder for us to communicate to clients clearly about what they’ll get, how much it will cost, and how long it will take. That, of course, also means that it hurts our client relationships. (This actually kind of goes back to my personal learnings, which I’ll mention in a bit. I tend to be a “let’s leave things vague so we don’t have to limit our options” kind of person. But I’m working on fixing this to be more precise, specific, and clear in everything that we do.) Dialing It In: Building a Closed System We were trying to build an open system. We need to build a closed system. We need to force clarity and get specific about what we do, what we don’t do, and how much it all costs. Then we need a system to expand on that closed system—add new types of deliverables, new content playbooks, and new workflows if and when the need arises. With that in mind, we can start by mapping out the key dimensions of any type of deliverable that we would ever want to deliver. These are the universal dimensions that determine the scope, workflow, and price of any deliverable—regardless of the specific type output. Dimensions are: Brief scope Writing + editing scope Design scope Interview scope Revision (rounds) Scope, essentially, just tells us how many words, graphics, interviews, etc are required for the content we’re creating. In our first crack at the system, we got super granular with these scopes. But to help force a more manageable system, we realized that we didn’t need tiny increments for most of this work. Instead, we just need boundaries—you pay $X for up to Y words. We still need some variability around the scope of these articles. Obviously, most clients won’t be willing to pay the same price for a 1,000-word article as a 10,000-word article. But we can be smarter about the realistic break points. We boiled it down to the most common ranges: (Up to) 250 words 1,000 words 3,000 words 6,000 words 10,000 words This gives us a much more manageable number of variables. But we still haven’t exactly closed the system. We need one final dimension: Deliverable type. This tells us what we’re actually building with these building blocks. This is how we’ll put a cap on the potentially infinite number of combinations we could offer. The deliverable type will define what the final product should look like (e.g., blog post, case study, ebook, etc). And it will also give us a way to put standards and expectations around different types of deliverables that we want to offer. Then we can expand on this list of deliverables to offer new services. In the mean time, only the deliverables that we have already defined are, “on the menu,” so to speak. If a client comes to us and asks for something like a podcast summary article (which we don’t currently offer), we’ll have to either say we can’t provide that work or create a new deliverable type and define the dimensions of that specific piece. But here’s the kicker: No matter the deliverable type, it has to still fit within the scopes we’ve already defined. And the pricing will be the same. This means that if you’re looking for our team to write up to 1,000 words of content, it costs the same amount—whether it’s a blog post, an ebook, a LinkedIn post, or anything else. Rather than trying to retool our entire system to offer this new podcast summary article deliverable, we’ll just create the new deliverable type, add it to the list of options, and it’s ready to sell with the pre-defined dimensions we’ve already identified. To do: Update onboarding workflow Update contracts and scope documents Dial in new briefing process Know Thyself For the last year, I’ve been going through personal therapy. (Huge shout out to my wife, Laura, for her support and encouragement throughout the process.) It’s taught me a lot about myself and my tendencies. It’s helped me find some of my weaknesses and think about how I can improve as a person, as a partner, and as an entrepreneur. And it’s forced me to face a lot of hard truths. For example, consider some of the critical decisions I’ve made for my business: Unconventional freelance “collective” model No formal management structure Open-ended retainers with near-infinite flexibility General contracts without defined scope “Take it or leave it” approach to sales and marketing Over the years, I’ve talked about almost everything on this list as a huge advantage. I saw these things as a reflection of how I wanted to do things differently and better than other companies. But now, I see them more as a reflection of my fears and insecurities. Why did I design my business like this? Why do I want so much “flexibility” and why do I want things left open-ended rather than clearly defined? One reason that could clearly explain it: I’m avoidant. If you’re not steeped in the world of therapy, this basically means that my fight or flight response gets turned all the way to “flight.” If I’m unhappy or uncomfortable, my gut reaction is usually to withdraw from the situation. I see commitment and specificity as a prelude to future conflict. And I avoid conflict whenever possible. So I built my business to minimize it. If I don’t have a specific schedule of work that I’m accountable for delivering, then we can fudge the numbers a bit and hope they even out in the end. If I don’t set a specific standard for the length of an article, then I don’t have to let the client know when their request exceeds that limit. Conflict….avoided? Now, that’s not to say that everything I’ve built was wrong or bad. There is a lot of value in having flexibility in your business. For example, I would say that our flexible retainers are, overall, an advantage. Clients have changing needs. Having flexibility to quickly adapt to those needs can be a huge value add. And not everything can be clearly defined upfront (at least not without a massive amount of time and work just to decide how long to write an article). Overly-rigid structures and processes can be just as problematic as loosey-goosey ones. But, on the whole, I realized that my avoidant tendencies and laissez faire approach to management have left a vacuum in many areas. The places where I avoided specificity were often the places where there was the most confusion, uncertainty, and frustration from the team and from clients. People simply didn’t know what to expect or what was expected of them. Ironically, this often creates the conflict I’m trying to avoid. For example, if I don’t give feedback to people on my team, then they feel uneasy about their work. Or they make assumptions about expectations that don’t match what I’m actually expecting. Then the client might get upset, I might get upset, and our team members may be upset. Conflict definitely not avoided. This happens on the client side, too. If we don’t define a specific timeline when something will be delivered, the client might expect it sooner than we can deliver—creating frustration when we don’t meet their expectation. This conflict actually would have been avoided if we set clearer expectations upfront. But we didn’t do that. I didn’t do that. So it’s time to step up and close the gaps. Stepping Up and Closing the Gaps If I’m going to address these gaps and create more clarity and stability, I have to step up. Both personally and professionally. I have to actually face the fear and uncertainty that drives me to be avoidant. And then apply that to my business in meaningful ways that aren’t cop-out ways of kinda-sorta providing structure without really doing it. I’ve gotta be all in. This means: Fill the gaps where I rely on other people to do things that aren’t really their job but I haven’t put someone in place to do it Set and maintain expectations about our internal work processes, policies, and standards Define clear boundaries on things like roles, timelines, budgets, and scopes Now, this isn’t going to happen overnight. And just because I say that I need to step up to close these gaps doesn’t mean that I need to be the one who’s responsible for them (at least not forever). It just means that, as the business leader, I need to make sure the gaps get filled—by me or by someone else who has been specifically charged with owning that part of the operation. So, this is probably my #1 focus over the coming quarter. And it starts by identifying the gaps that exist. Then, step into those gaps myself, pay someone else to fill that role, or figure out how to eliminate the gap another way. This means going all the way back to the most basic decisions in our business. One of the foundational things about Optimist is being a “different kind” of agency. I always wanted to build something that solved for the bureaucracy, hierarchy, and siloed structure of agencies. If a client has feedback, they should be able to talk directly to the person doing the work rather than going through 3 layers of account management and creative directors. So I tried to be clever. I tried to design all kinds of systems and processes that eliminated these middle rungs. (In retrospect, what I was actually doing was designing a system that played into my avoidant tendencies and made it easy to abdicate responsibility for lots of things.) Since we didn’t want to create hierarchy, we never implemented things like Junior and Senior roles. We never hired someone to manage or direct the individual creatives. We didn’t have Directors or VPs. (Hell, we barely had a project manager for the first several years of existence.) This aversion to hierarchy aligned with our values around elevating ownership and collective contribution. I still believe in the value a flat structure. But a flat structure doesn’t eliminate the complexity of a growing business. No one to review writers and give them 1:1 feedback? I guess I’ll just have to do that….when I have some spare time. No Content Director? Okay, well someone needs to manage our content playbooks and roll out new ones. Just add it to my task list. Our flat structure didn’t eliminate the need for these roles. It just eliminated the people to do them. All of those unfilled roles ultimately fell back on me or our ops person, Katy. Of course, this isn’t the first time we’ve recognized this. We’ve known there were growing holes in our business as it’s gotten bigger and more complex. Over the years, we’ve experimented with different ways to solve for it. The Old Solution: Distributed Ops One system we designed was a “distributed ops” framework. Basically, we had one person who was the head of ops (at the time, we considered anything that was non-client-facing to be “ops”). They’d plan and organize all of the various things that needed to happen around Optimist. Then they’d assign out the work to whoever was able to help. We had a whole system for tying this into the our profit share and even gave people “Partner” status based on their contributions to ops. It worked—kinda. One big downfall is that all of the tasks and projects were ad hoc. People would pick up jobs, but they didn’t have much context or expertise to apply. So the output often varied. Since we were trying to maintain a flat structure, there was minimal oversight or management of the work. In other words, we didn’t always get the best results. But, more importantly, we still didn’t close all of the gaps entirely. Because everything was an ad-hoc list of tasks and projects, we never really had the “big picture” view of everything that needed to be done across the business. This also meant we rarely had clarity on what was important, what was trivial, and what was critical. We need a better system. Stop Reinventing the Wheel (And Create a Damn Org Chart) It’s time to get serious about filling the gaps in our business. It can’t be a half-fix or an ad hoc set of projects and tasks. We need clarity on the roles that need to be filled and then fill them. The first step here is to create an org chart. A real one. Map out all of the jobs that need to be done for Optimist to be successful besides just writers and designers. Roles like: Content director Design director SEO manager Reporting Finance Account management Business development Sales Marketing Project management It feels a bit laughable listing all of these roles. Because most are either empty or have my name attached to them. And that’s the problem. I can’t do everything. And all of the empty roles are gaps in our structure—places where people aren’t getting the direction, feedback, or guidance they need to do their best work. Or where things just aren’t being done consistently. Content director, for example, should be responsible for steering the output of our content strategists, writers, and editors. They’re not micromanaging every deliverable. But they give feedback, set overall policy, and help our team identify opportunities to get better. Right now we don’t have anyone in that role. Which means it’s my job—when I have time. Looking at the org chart (a real org chart that I actually built to help with this), it’s plain as day how many roles look like this. Even if we aren’t going to implement a traditional agency structure and a strict hierarchy, we still need to address these gaps. And the only way for that to happen is face the reality and then create a plan to close the gaps. Now that we have a list of theoretical roles, we need to clearly define the responsibilities and boundaries of those roles to make sure they cover everything that actually needs to happen. Then we can begin the process of delegating, assigning, hiring, and otherwise addressing each one. So that’s what I need to do. To be done: Create job descriptions for all of the roles we need to fill Hire Biz Dev role Hire Account Lead role(s) Hire Head of Content Playing Offense As we move into Q1 of 2025 and I reflect on the tumultuous few years we’ve had, one thought keeps running through my head. We need to play offense. Most of the last 1-2 years was reacting to changes that were happening around us. Trying to make sense and chart a new path forward. Reeling. But what I really want—as a person and as an entrepreneur—is to be proactive. I want to think and plan ahead. Figure out where we want to go before we’re forced to change course by something that’s out of our control. So my overarching focus for Q1 is playing offense. Thinking longer term. Getting ahead of the daily deluge and creating space to be more proactive, innovative, and forward thinking. To do: Pilot new content formats Audit and update our own content strategy Improve feedback workflows Build out long-term roadmap for 1-2 years for Optimist Final Note on Follow-Through and Cadence In my reflection this year, one of the things I’ve realized is how helpful these posts are for me. I process by writing. So I actually end up making a lot of decisions and seeing things more clearly each time I sit down to reflect and write my yearly recap. It also gives me a space to hold myself accountable for the things I said I would do. So, I’m doing two things a bit differently from here on out. First: I’m identifying clear action items that I’m holding myself accountable for getting done in the next 3 months (listed in the above sections). In each future update, I’ll do an accounting of what I got done and what wasn’t finished (and why). Second: I’m going to start writing shorter quarterly updates. This will gives me more chances each year to reflect, process, and make decisions. Plus it gives me a shorter feedback loop for the action items that I identified above. (See—playing offense.) — Okay friends, enemies, and frenemies. This is my first update for 2025. Glad to share with y’all. And thanks to everyone who’s read, commented, reached out, and shared their own experiences over the years. We are all the accumulation of our connections and our experiences. As always, I will pop in to respond to comments and answer questions. Feel free to share your thoughts, questions, and general disdain down below. Cheers, Tyler

#reddit#started#content

reddit

0

0.333

Alarming_Management3•This week

Switching Gears: Implementing AI for My Agency’s Marketing After a Decade

Hi there, I’ve been running a software development and design agency for the last 10 years, mainly focusing on building custom solutions for businesses and SaaS. For the last 2 years, I’ve consistently recommended that clients use AI technologies, especially for social media and content creation to generate traffic. Funny enough, I wasn’t practicing what I preached. Most of my client projects came from platforms like Upwork and word-of-mouth referrals from clients or people from networking events. Background I started my journey in 2014, switching from an employee to a freelancer. Within the first 10 months, my initial projects grew beyond what I could handle alone, prompting me to hire additional developers. This shift turned my role from a full-stack developer to a team lead and developer. Over the years, my focus has been a blend of tech and product. About five years ago, I realized the importance of design, leading me to adding designers to the agency to provide full-cycle service development—from product ideation and design to development, testing, launch, and support. I still continue to set up dedicated teams for some clients, maintaining a strong technical role as a tech lead, solution architect, and head product designer. To enhance my skills, I even completed UI/UX design courses to offer better product solutions. Despite these changes, building products has always been the easy part. The challenge was ensuring these client products didn’t end up in the graveyard due to poor product-market fit, often caused by inadequate marketing and sales strategies but more often just absence of them. (we are talking about startup and first time founders here 🙂 ) My Journey and Observations Advising Clients: I often found myself advising clients on increasing traffic for their SaaS products and crafting strategic marketing plans. Learning: I’ve gained most of my knowledge from consuming internet materials, courses, and blog posts and learning from successful client project launches. Realization: Despite giving this advice, I wasn’t applying these strategies to my own business, leading to low visits to my agency’s website. Initial Solution: Hiring a Marketer Hiring: I brought in a marketer with a solid background in content creating and interview video editing from an educational organization. Goal: The aim was to increase website visits through a comprehensive marketing strategy. Outcome: Although the content produced was high-quality and useful for pitching services, it didn’t lead to significant traffic increases. Issue: The marketer focused more on content creation rather than distribution channels, which limited effectiveness. Shift to AI-Driven Strategy Experiment: I decided to try using AI for content creation and distribution, which aligns with my agency’s specialization in design-driven development and AI integrations. Implementation plan: I will be generating all content with minimal edits using AI and implementing a strategic backlinking approach. Backlinking Strategy Initial Plan: I initially thought of hiring a specialist for backlinks. Realization: The costs and profiles of freelancers didn’t seem promising. Solution: I found AI-driven services for backlinks, which seem more efficient and cost-effective. Plan: My plan is to use these tools for programmatic SEO-driven AI-generated articles and third-party backlinking services over the next two to three months. Current Approach Management: This approach can be managed and executed by 1 person and monitored weekly, reducing human error and optimizing efficiency. I will start it myself and then replace myself with an editor with managing skills. Reflection: It’s a bit ironic and funny that it took me 10 years to start implementing these strategies in my own agency business, but I now feel more confident with AI and automation in place. Why Increase Website Visitors? You might ask, why do I want to increase the number of visitors to the site, and how can I ensure these visitors will be qualified? Hands-On Experience: To gain hands-on experience and perform this exercise effectively. Introduce Packaged Services: I want to introduce a set of low-cost packaged services tailored for non-technical people who want to build things for themselves - the DIY kits for non-technical folks. These services will provide a foundational template for them to build upon on top of existing established solutions such as Wix, Square Why am I Posting and Sharing Here? You might also wonder, why am I posting it here and sharing this? Well, I'm doing this more for myself. Most of my career, the things I’ve done have been behind the curtains. With this small project, I want to make it public to see the reaction of the community. Perhaps there will be good and smart suggestions offered, and maybe some insights or highlights of tools I wasn’t aware of or didn’t consider. I’ll keep sharing updates on this journey of website promotion, marketing, and SEO. My current goal is to reach 2,000 visits per month, which is a modest start. Looking forward to any thoughts or advice from this community! Disclaimer: This content was not generated by AI, but it was edited by it 😛

#reddit#switching#gears:

reddit

0

0.333

Alarming_Management3•This week

Switching Gears: Implementing AI for My Agency’s Marketing After a Decade

Hi there, I’ve been running a software development and design agency for the last 10 years, mainly focusing on building custom solutions for businesses and SaaS. For the last 2 years, I’ve consistently recommended that clients use AI technologies, especially for social media and content creation to generate traffic. Funny enough, I wasn’t practicing what I preached. Most of my client projects came from platforms like Upwork and word-of-mouth referrals from clients or people from networking events. Background I started my journey in 2014, switching from an employee to a freelancer. Within the first 10 months, my initial projects grew beyond what I could handle alone, prompting me to hire additional developers. This shift turned my role from a full-stack developer to a team lead and developer. Over the years, my focus has been a blend of tech and product. About five years ago, I realized the importance of design, leading me to adding designers to the agency to provide full-cycle service development—from product ideation and design to development, testing, launch, and support. I still continue to set up dedicated teams for some clients, maintaining a strong technical role as a tech lead, solution architect, and head product designer. To enhance my skills, I even completed UI/UX design courses to offer better product solutions. Despite these changes, building products has always been the easy part. The challenge was ensuring these client products didn’t end up in the graveyard due to poor product-market fit, often caused by inadequate marketing and sales strategies but more often just absence of them. (we are talking about startup and first time founders here 🙂 ) My Journey and Observations Advising Clients: I often found myself advising clients on increasing traffic for their SaaS products and crafting strategic marketing plans. Learning: I’ve gained most of my knowledge from consuming internet materials, courses, and blog posts and learning from successful client project launches. Realization: Despite giving this advice, I wasn’t applying these strategies to my own business, leading to low visits to my agency’s website. Initial Solution: Hiring a Marketer Hiring: I brought in a marketer with a solid background in content creating and interview video editing from an educational organization. Goal: The aim was to increase website visits through a comprehensive marketing strategy. Outcome: Although the content produced was high-quality and useful for pitching services, it didn’t lead to significant traffic increases. Issue: The marketer focused more on content creation rather than distribution channels, which limited effectiveness. Shift to AI-Driven Strategy Experiment: I decided to try using AI for content creation and distribution, which aligns with my agency’s specialization in design-driven development and AI integrations. Implementation plan: I will be generating all content with minimal edits using AI and implementing a strategic backlinking approach. Backlinking Strategy Initial Plan: I initially thought of hiring a specialist for backlinks. Realization: The costs and profiles of freelancers didn’t seem promising. Solution: I found AI-driven services for backlinks, which seem more efficient and cost-effective. Plan: My plan is to use these tools for programmatic SEO-driven AI-generated articles and third-party backlinking services over the next two to three months. Current Approach Management: This approach can be managed and executed by 1 person and monitored weekly, reducing human error and optimizing efficiency. I will start it myself and then replace myself with an editor with managing skills. Reflection: It’s a bit ironic and funny that it took me 10 years to start implementing these strategies in my own agency business, but I now feel more confident with AI and automation in place. Why Increase Website Visitors? You might ask, why do I want to increase the number of visitors to the site, and how can I ensure these visitors will be qualified? Hands-On Experience: To gain hands-on experience and perform this exercise effectively. Introduce Packaged Services: I want to introduce a set of low-cost packaged services tailored for non-technical people who want to build things for themselves - the DIY kits for non-technical folks. These services will provide a foundational template for them to build upon on top of existing established solutions such as Wix, Square Why am I Posting and Sharing Here? You might also wonder, why am I posting it here and sharing this? Well, I'm doing this more for myself. Most of my career, the things I’ve done have been behind the curtains. With this small project, I want to make it public to see the reaction of the community. Perhaps there will be good and smart suggestions offered, and maybe some insights or highlights of tools I wasn’t aware of or didn’t consider. I’ll keep sharing updates on this journey of website promotion, marketing, and SEO. My current goal is to reach 2,000 visits per month, which is a modest start. Looking forward to any thoughts or advice from this community! Disclaimer: This content was not generated by AI, but it was edited by it 😛

#reddit#switching#gears:

reddit

0

1

TheValueProvider•This week

10 Side Projects in 10 Years: Lessons from Failures and a $700 Exit

Hey folks, I'm sharing my journey so far in case it can help others. Entrepreneurship can sometimes be demotivating. In my case, I've always been involved in side projects and what I've realized is that every time you crash a project, the next one makes it a bit further. So this is a long-term game and consistency ends up paying off The $1 Android Game (2015, age 18) What Happened: 500 downloads, 1€ in ad revenue Ugly UI, performance issues Key Lessons: Don’t be afraid of launching. Delaying for “perfection” is often a sign that you fear being ignored. I was trying to perfect every aspect of the game. In reality, I was delaying the launch because I feared no one would download the app. Commit to the project or kill it. At some point, this project was no longer fun (it was just about fixing device responsiveness). Most importantly, I wasn't learning anything new so I moved to smth else. The Forex Bot Regret (2016, age 19) What Happened: Lost months identifying inexistent chart patterns Created a Trading bot that was never profitable Key Lessons: Day trading’s real winners are usually brokers. There are plenty of guys selling a bot or systems that are not making money trading, why would they sell a “money-printing machine” otherwise... Develop an unfair advantage. With these projects, I developed a strong coding foundation that gave me an edge when dealing with non-technical business people. Invest countless hours to create a skills gap between you and others, one that becomes increasingly difficult for them to close (coding, public speaking, networking, etc.) The $700 Instagram Exit (2018, age 21) What Happened: Grew a motivational account to 60k followers Sold it for $700 90% of followers were in low-income countries (hard to monetize) Key Lessons: Follower quality > quantity. I focused on growth and ended up with an audience I couldn’t truly define. If brands don’t see value, you won’t generate revenue. Also, if you do not know who you are creating content for, you'll end up demotivated and stop posting. Great 3rd party product + domain authority = Affiliate marketing works. In this case, I could easily promote an IG growing service because my 50k+ followers conveyed trust. Most importantly, the service I was promoting worked amazingly. The Illegal Amazon Review Marketplace (2020, age 23) What Happened: Sellers were reimbursing buyers for positive reviews Built a WordPress marketplace to facilitate “free products for reviews” Realized it violated Amazon’s terms Key Lessons: Check for “red flags” when doing idea assessment. There will always be red and orange flags. It’s about learning to differentiate between them (e.g. illegality, 100% dependence on a platform, etc.) If there’s competition, it’s good, if they are making money it’s even better. I was thrilled when I saw no competition for my “unique idea”. Later, I discovered the obvious reason. Copying a “Proven” Business Model (2020, age 23) What Happened: Tried recreating an Instagram “comment for comment” growth tool Instagram changed the algorithm and killed the growth strategy that the product used. Key Lessons: Do not build a business that depends 100% on another business, it is too risky. Mr. Musk can increase Twitter on API pricing to $42,000 monthly without notice and Tik Tok can be banned in the US. Due to the IG algorithm change, we had built a product that was not useful, and worse, now we had no idea how to grow an IG account. Consider future project synergies before selling. I regret having sold the 60k follower IG account since it could have saved me a lot of time when convincing users to try the service. NFT Marathon Medals (2021, age 24) What Happened: Created NFT race medals Sold 20 for 5€ each, but spent 95% of meetings explaining “what is an NFT?” Key Lessons: Market timing is crucial. As with every new technology, it is only useful as long as society is ready to adopt it. No matter how promising the tech is in the eyes of SV, society will end up dictating its success (blockchain, AI, etc). In this case, the runner community was not ready to adopt blockchain (it is not even prepared today). Race organizers did not know what they were selling, and runners did not know what they were buying. The 30-day rule in Fanatical Prospecting. Do not stop prospecting. I did prospecting and closed deals 3 months after the outbound efforts. Then I was busy executing the projects and had no clients once the projects were finished. AI Portal & Co-Founder Misalignment (2023, age 26) What Happened: Built a portal for SMEs to find AI use cases Co-founders disagreed on vision and execution Platform still gets \~1 new user/day Key Lessons: Define roles and equity clearly. Our biggest strength ended up killing us. Both founders had strong strategic skills and we were constantly arguing about decisions. NextJS + Vercel + Supabase: Great stack to create a SaaS MVP. (but do not use AI with frameworks unless you know how they work conceptually) SEO is king. One of our users creates a use case on “Changing Song Lyrics with AI.” Not being our target use case, it brings 90% of our traffic. Building an AI Tool & Getting Ghosted (2024, age 27) What Happened: SEO agency wanted to automate rewriting product descriptions Built it in 3 weeks, but the client vanished Key Lessons: Validate manually first. Don’t code a full-blown solution for a problem you haven’t tested in real-world workflows. I kept rewriting code only to throw it away. Jumping straight into building a solution ended up costing more time than it saved. Use templates, no-code, and open-source for prototyping. In my case, using a Next.js template saved me about four weeks of development only to hit the same dead end, but much faster. Fall in love with your ICP or walk away. I realized I didn’t enjoy working with SEO agencies. Looking back, I should have been honest with myself and admitted that I wasn’t motivated enough by this type of customer. Ignoring Code Perfection Doubled Traffic (2025, age 28) What Happened: Partnered with an ex-colleague to build an AI agents directory Focused on content & marketing, not endless bug fixes Traffic soared organically Key Lessons: Measure the impact of your actions and double down on what works. We set up an analytics system with PostHog and found wild imbalances (e.g. 1 post about frameworks outperformed 20 promotional posts). You have to start somewhere. For us, the AI agents directory is much more than just a standalone site, it's a strategic project that will allow us to discover new products, gain domain authority, and boost other projects. It builds the path for bigger opportunities. Less coding, more traction. Every day I have to fight against myself not to code “indispensable features”. Surprisingly, the directory keeps gaining consistent traffic despite being far from perfect Quitting My Job & Looking Ahead (2025, age 28) What Happened: Left full-time work to go all-in Plan to build vertical AI agents that handle entire business workflows (support, marketing, sales) Key Lessons: Bet on yourself. The opportunity cost of staying in my full-time job outweighed the benefits. It might be your case too I hope this post helps anyone struggling with their project and inspires those considering quitting their full-time job to take the leap with confidence.

#reddit#side#projects

reddit

0

1

BalloonWheelie•This week

Why the value of writing code and other digital services is going to zero

I must preface this with a trigger warning because I make some statements in this post that might be upsetting to some. This post discusses my experience building in the new era of entrepreneurship, which is one where the founder is the center of the universe, and the consultants, overpriced SaaS, and corporate swamp creatures are replaced by single-user custom software, bots, and self-hosted automations. If you work in the legacy economy, I really don't intend to stress you out or say things you are doing are quickly becoming irrelevant, but I must share the reality of how I am operating, because I would like to hear from others who are doing the same, or desire to do the same. I am currently operating with the belief that AI-powered tools are going to make 1-person million dollar businesses much more common. Building anything digital is becoming extremely easy, cheap, and quick to implement. The value of code and digital tools is approaching zero, or at most 5% of what it currently is. Right now, the most powerful AI tools are aimed at developers, so folks who have some technical and business ability basically have nothing holding them back aside from the speed of their brain right now. I happen to be a part of the cohort, and am building like there is no tomorrow, but I don't believe this cohort is actually all that big. The next hurdle to unlock the new era of entrepreneurship is empowering every entrepreneur to build at the same pace that is currently locked behind having technical ability. This cohort is huge (millions, if the number of people in this sub is any indication). This post is aimed at them (you?). If you are part of this cohort, what is holding you back from launching a new product for near-zero cost? What is too complicated, too expensive, too unknown for you to be able to build your new/current business at maximum speed? I look forward to seeing the replies, I hope some insights shared can help the community, and be a catalyst for more tools to enable non-technical founders to launch. I will now share some of how I am testing, launching, and selling as a one-man-show. This will be a little bit technical, but if the output of any layer of my stack is something you want, please comment because maybe someone will build a cheap way of accessing it without needing to manage the code yourself. \#1 BOTS I cannot overstate how much leverage bots have created for me. I run all of my bots locally and interface with with via Telegram. Bots do things like: \- watch social media pages, forums, subreddits, etc related to my customers and notify me of what is going on, and suggest SEO blog posts that could be published to capture traffic related to the topic. with a single message, my bot will generate a blog post, send it to me for review, apply edits i suggest, and then publish it live, all from within telegram \- pay attention to all my key metrics/analytics, and attempt to find insights/corrolations (ex. there is a lot of traffic on this page, blog post, video, etc. here's why, and how we can take advantage of it to drive business goals) \- repurposing content. i have dozens of social media profiles that are 100% run by bots, they are all related to my customer niches and will do things like post news, snippets from my blogs, interact with human creators in the niche, etc. this builds my audience automatically which I can then advertise to/try to convert into paying customers, since they are interested in the things my bot is posting and become followers, it's like automated qualified lead gen 24/7 across every social platform and every niche I care about. you may be thinking by now that this post is made by a bot, but you will have to trust me that this is 100% hand-written by my sleep-deprived brain. let's continue: \#2 replacing every SaaS with a shitty version of it designed for what i need out of it it's absurd that we pay ten's of dollars per seat per month for basic digital functions like chat (slack), CRM (active camppaign, sales force, hubspot, etc), email stuff (mailchip, etc), link sharing (linktree, etc), website builders (wix, squarespace, etc), etc. all of these SaaS tools are overpriced and overbuilt. I believe many of them are going to be caught in the innovators dilemma and will go to 0. I don't use any of these anymore, I build and self-host my own shitty version of each of them that does only what i need out of the tool. for example, my CRM doesn't have a fancy drag and drop email builder and 10000 3rd party plugins, because i dont need any of that shit I just need to segment and communicate with my customers. if i need more features, i can generate them on the fly. \#3 working alone I have worked with cofounders in the past, raised money from investors, hired consultants, burned money and time, suffered sleepless nights from stress caused by other people not delivering, trying to convince others they are wrong, or they are pushing the company off a cliff, waste waste waste. no more of that. In the new age of entrepreneurship, the BUILDER (you and I) are the ones creating the value, and AI empowers us to do it alone. this might seem daunting, but there is no business problem that can't be solved with a detailed discussion sesh with chatgpt, no facts that can't be found with perplexity, and no task that can't be automated with claude. there is no need for anymore swamp creatures. you are the start and the end point, you don't need to rely on anyone else for anything. this may sound ignorant, but this is the conclusion I have come to believe, and it continues to be proven every day my businesses progress with me being the only human involved. This is getting quite long so I'll cut it here. I look forward to hearing about how you are operating in this new era and hopefully getting inspired/learning some new ideas to add to my current stack.

#reddit#value#writing

reddit

0

0.543

DrJigsaw•This week

101 best SEO tips to help you drive traffic in 2k21

Hey guys! I don't have to tell you how SEO can be good for your business - you can drive leads to your SaaS on autopilot, drive traffic to your store/gym/bar/whatever, etc. The thing with SEO, though, is that most SEO tips on the internet are just not that good. Most of the said tips: Are way too simple & basic (“add meta descriptions to your images”*) Are not impactful. Sure, adding that meta tag to an image is important, but that’s not what’s going to drive traffic to your website Don’t talk much about SEO strategy (which is ultimately the most important thing for SEO). Sure, on-page SEO is great, but you sure as hell won't drive much traffic if you can't hire the right writers to scale your content. And to drive serious SEO traffic, you'll need a LOT more than that. Over the past few years, my and my co-founder have helped grow websites to over 200k+ monthly traffic (check out our older Reddit post if you want to learn more about us, our process, and what we do), and we compiled all our most important SEO tips and tricks, as well as case studies, research, and experiments from the web, into this article. Hope you like it ;) If you think we missed something super important, let us know and we'll add it to the list. And btw, we also published this article on our own blog with images, smart filters, and all that good stuff. If you want to check it out, click here. That said, grab some coffee (or beer) & let's dive in - this is going to be a long one. SEO Strategy Tips Tip #1. A Lot of SEO Tips On The Internet Are NOT Necessarily Factual A lot of the SEO content you’ll read on the internet will be based on personal experiences and hearsay. Unfortunately, Google is a bit vague about SEO advice, so you have to rely more on experiments conducted by SEO pros in the community. So, sometimes, a lot of this information is questionable, wrong, or simply based on inaccurate data.  What we’re getting at here is, whenever you hear some new SEO advice, take it with a grain of salt. Google it to double-check other sources, and really understand what this SEO advice is based on (instead of just taking it at face value). Tip #2. SEO Takes Time - Get Used to It Any way you spin it, SEO takes time.  It can take around 6 months to 2 years (depending on the competition in your niche) before you start seeing some serious results.  So, don’t get disappointed if you don’t see any results within 3 months of publishing content. Tip #3. SEO Isn’t The Best Channel for Everyone That said, if you need results for your business tomorrow, you might want to reconsider SEO altogether.  If you just started your business, for example, and are trying to get to break-even ASAP, SEO is a bad idea - you’ll quit before you even start seeing any results.  If that’s the case, focus on other marketing channels that can have faster results like content marketing, PPC, outreach, etc. Tip #4. Use PPC to Validate Keywords Not sure if SEO is right for your business? Do this: set up Google Search ads for the most high-intent keywords in your niche. See how well the traffic converts and then decide if it’s worthwhile to focus on SEO (and rank on these keywords organically). Tip #5. Use GSC to See If SEO Is Working While it takes a while to see SEO results, it IS possible to see if you’re going in the right direction. On a monthly basis, you can use Search Console to check if your articles are indexed by Google and if their average position is improving over time. Tip #6. Publish a TON of Content The more content you publish on your blog, the better. We recommend a minimum of 10,000 words per month and optimally 20,000 - 30,000 (especially if your website is fresh). If an agency offers you the typical “4 500-word articles per month” deal, stay away. No one’s ever gotten results in SEO with short, once-per-week articles. Tip #7. Upgrade Your Writers Got a writer that’s performing well? Hire them as an editor and get them to oversee content operations / edit other writers’ content. Then, upgrade your best editor to Head of Content and get them to manage the entire editor / writer ops. Tip #8. Use Backlink Data to Prioritize Content When doing keyword research, gather the backlink data of the top 3 ranking articles and add it to your sheet. Then, use this data to help you prioritize which keywords to focus on first. We usually prioritize keywords that have lower competition, high traffic, and a medium to high buyer intent. Tip #9. Conduct In-Depth Keyword Research Make your initial keyword research as comprehensive as possible. This will give you a much more realistic view of your niche and allow you to prioritize content the right way. We usually aim for 100 to 300 keywords (depending on the niche) for the initial keyword research when we start working with a client. Tip #10. Start With Competitive Analysis Start every keyword research with competitive analysis. Extract the keywords your top 3 competitors are ranking on.  Then, use them as inspiration and build upon it. Use tools like UberSuggest to help generate new keyword ideas. Tip #11. Get SEMrush of Ahrefs You NEED SEMrush or Ahrefs, there’s no doubt about it. While they might seem expensive at a glance (99 USD per month billed annually), they’re going to save you a lot of manpower doing menial SEO tasks. Tip #12. Don’t Overdo It With SEO Tools Don’t overdo it with SEO tools. There are hundreds of those out there, and if you’re the type that’s into SaaS, you might be tempted to play around with dozens at a time. And yes, to be fair, most of these tools ARE helpful one way or another. To effectively do organic SEO, though, you don’t really need that many tools. In most cases, you just need the following: SEMrush/Ahrefs Screaming Frog RankMath/Yoast SEO Whichever outreach tool you prefer (our favorite is snov.io). Tip #13. Try Some of the Optional Tools In addition to the tools we mentioned before, you can also try the following 2 which are pretty useful & popular in the SEO community: Surfer SEO - helps with on-page SEO and creating content briefs for writers. ClusterAI - tool that helps simplify keyword research & save time. Tip #14. Constantly Source Writers Want to take your content production to the next level? You’ll need to hire more writers.  There is, however, one thing that makes this really, really difficult: 95 - 99% of writers applying for your gigs won’t be relevant. Up to 80% will be awful at writing, and the remainder just won’t be relevant for your niche. So, in order to scale your writing team, we recommend sourcing constantly, and not just once every few months. Tip #15. Create a Process for Writer Filtering As we just mentioned, when sourcing writers, you’ll be getting a ton of applicants, but most won’t be qualified. Fun fact \- every single time we post a job ad on ProBlogger, we get around 300 - 500 applications (most of which are totally not relevant). Trust us, you don’t want to spend your time going through such a huge list and checking out the writer samples. So, instead, we recommend you do this: Hire a virtual assistant to own the process of evaluating and short-listing writers. Create a process for evaluating writers. We recommend evaluating writers by: Level of English. If their samples aren’t fluent, they’re not relevant. Quality of Samples. Are the samples engaging / long-form content, or are they boring 500-word copy-pastes? Technical Knowledge. Has the writer written about a hard-to-explain topic before? Anyone can write about simple topics like traveling - you want to look for someone who knows how to research a new topic and explain it in a simple and easy to read way. If someone’s written about how to create a perfect cover letter, they can probably write about traveling, but the opposite isn’t true. The VA constantly evaluates new applicants and forwards the relevant ones to the editor. The editor goes through the short-listed writers and gives them trial tasks and hires the ones that perform well. Tip #16. Use The Right Websites to Source Writers “Is UpWork any good?” This question pops up on social media time and time again. If you ask us, no, UpWork is not good at all. Of course, there are qualified writers there (just like anywhere else), but from our experience, those writers are few and far in-between. Instead, here are some of our favorite ways to source writers: Cult of Copy Job Board ProBlogger Headhunting on LinkedIn If you really want to use UpWork, use it for headhunting (instead of posting a job ad) Tip #17. Hire Writers the Right Way If you want to seriously scale your content production, hire your writers full-time. This (especially) makes sense if you’re a content marketing agency that creates a TON of content for clients all the time. If you’re doing SEO just for your own blog, though, it usually makes more sense to use freelancers. Tip #18. Topic Authority Matters Google keeps your website's authoritativeness in mind. Meaning, if you have 100 articles on digital marketing, you’re probably more of an authority on the topic than someone that has just 10. Hence, Google is a lot more likely to reward you with better rankings. This is also partially why content volume really matters: the more frequently you publish content, the sooner Google will view you as an authority. Tip #19. Focus on One Niche at a Time Let’s say your blog covers the following topics: sales, accounting, and business management.  You’re more likely to rank if you have 30 articles on a single topic (e.g. accounting) than if you have 10 articles on each. So, we recommend you double-down on one niche instead of spreading your content team thin with different topics. Tip #20. Don’t Fret on the Details While technical SEO is important, you shouldn’t get too hung up on it.  Sure, there are thousands of technical tips you can find on the internet, and most of them DO matter. The truth, though, is that Google won’t punish you just because your website doesn’t load in 3 milliseconds or there’s a meta description missing on a single page. Especially if you have SEO fundamentals done right: Get your website to run as fast as possible. Create a ton of good SEO content. Get backlinks for your website on a regular basis. You’ll still rank, even if your website isn’t 100% optimized. Tip #21. Do Yourself a Favor and Hire a VA There are a TON of boring SEO tasks that your team should really not be wasting time with. So, hire a full-time VA to help with all that. Some tasks you want to outsource include gathering contacts to reach out to for link-building, uploading articles on WordPress, etc. Tip #22. Google Isn’t Everything While Google IS the dominant search engine in most parts of the world, there ARE countries with other popular search engines.  If you want to improve your SEO in China, for example, you should be more concerned with ranking on Baidu. Targeting Russia? Focus on Yandex. Tip #23. No, Voice Search is Still Not Relevant Voice search is not and will not be relevant (no matter what sensationalist articles might say). It’s just too impractical for most search queries to use voice (as opposed to traditional search). Tip #24. SEO Is Not Dead SEO is not dead and will still be relevant decades down the line. Every year, there’s a sensationalist article talking about this.  Ignore those. Tip #25. Doing Local SEO? Focus on Service Pages If you’re doing local SEO, focus on creating service-based landing pages instead of content.  E.g. if you’re an accounting firm based in Boston, you can make a landing page about /accounting-firm-boston/, /tax-accounting-boston/, /cpa-boston/, and so on. Thing is, you don’t really need to rank on global search terms - you just won’t get leads from there. Even if you ranked on the term “financial accounting,” it wouldn’t really matter for your bottom line that much. Tip #26. Learn More on Local SEO Speaking of local SEO, we definitely don’t do the topic justice in this guide. There’s a lot more you need to know to do local SEO effectively and some of it goes against the general SEO advice we talk about in this article (e.g. you don't necessarily need blog content for local SEO). We're going to publish an article on that soon enough, so if you want to check it out, DM me and I'll hit you up when it's up. Tip #27. Avoid Vanity Metrics Don’t get side-tracked by vanity metrics.  At the end of the day, you should care about how your traffic impacts your bottom line. Fat graphs and lots of traffic are nice and all, but none of it matters if the traffic doesn’t have the right search intent to convert to your product/service. Tip #28. Struggling With SEO? Hire an Expert Failing to make SEO work for your business? When in doubt, hire an organic SEO consultant or an SEO agency.  The #1 benefit of hiring an SEO agency or consultant is that they’ve been there and done that - more than once. They might be able to catch issues an inexperienced SEO can’t. Tip #29. Engage With the Community Need a couple of SEO questions answered?  SEO pros are super helpful & easy to reach! Join these Facebook groups and ask your question - you’ll get about a dozen helpful answers! SEO Signals Lab SEO & Content Marketing The Proper SEO Group. Tip #30. Stay Up to Date With SEO Trends SEO is always changing - Google is constantly pumping out new updates that have a significant impact on how the game is played.  Make sure to stay up to date with the latest SEO trends and Google updates by following the Google Search Central blog. Tip #31. Increase Organic CTR With PPC Want to get the most out of your rankings? Run PPC ads for your best keywords. Googlers who first see your ad are more likely to click your organic listing. Content & On-Page SEO Tips Tip #32. Create 50% Longer Content On average, we recommend you create an article that’s around 50% longer than the best article ranking on the keyword.  One small exception, though, is if you’re in a super competitive niche and all top-ranking articles are already as comprehensive as they can be. For example, in the VPN niche, all articles ranking for the keyword “best VPN” are around 10,000 - 11,000 words long. And that’s the optimal word count - even if you go beyond, you won’t be able to deliver that much value for the reader to make it worth the effort of creating the content. Tip #33. Longer Is Not Always Better Sometimes, a short-form article can get the job done much better.  For example, let’s say you’re targeting the keyword “how to tie a tie.”  The reader expects a short and simple guide, something under 500 words, and not “The Ultimate Guide to Tie Tying for 2021 \[11 Best Tips and Tricks\]” Tip #34. SEO is Not Just About Written Content Written content is not always best. Sometimes, videos can perform significantly better. E.g. If the Googler is looking to learn how to get a deadlift form right, they’re most likely going to be looking for a video. Tip #35. Don’t Forget to Follow Basic Optimization Tips For all your web pages (articles included), follow basic SEO optimization tips. E.g. include the keyword in the URL, use the right headings etc.  Just use RankMath or YoastSEO for this and you’re in the clear! Tip #36. Hire Specialized Writers When hiring content writers, try to look for ones that specialize in creating SEO content.  There are a LOT of writers on the internet, plenty of which are really good.  However, if they haven’t written SEO content before, chances are, they won’t do that good of a job. Tip #37. Use Content Outlines Speaking of writers - when working with writers, create a content outline that summarizes what the article should be about and what kind of topics it needs to cover instead of giving them a keyword and asking them to “knock themselves out.”   This makes it a lot more likely for the writer to create something that ranks. When creating content outlines, we recommend you include the following information: Target keyword Related keywords that should be mentioned in the article Article structure - which headings should the writer use? In what order? Article title Tip #38. Find Writers With Niche Knowledge Try to find a SEO content writer with some experience or past knowledge about your niche. Otherwise, they’re going to take around a month or two to become an expert. Alternatively, if you’re having difficulty finding a writer with niche knowledge, try to find someone with experience in technical or hard to explain topics. Writers who’ve written about cybersecurity in the past, for example, are a lot more likely to successfully cover other complicated topics (as opposed to, for example, a food or travel blogger). Tip #39. Keep Your Audience’s Knowledge in Mind When creating SEO content, always keep your audience’s knowledge in mind. If you’re writing about advanced finance, for example, you don’t need to teach your reader what an income statement is. If you’re writing about income statements, on the other hand, you’d want to start from the very barebone basics. Tip #40. Write for Your Audience If your readers are suit-and-tie lawyers, they’re going to expect professionally written content. 20-something hipsters? You can get away with throwing a Rick and Morty reference here and there. Tip #41. Use Grammarly Trust us, it’ll seriously make your life easier! Keep in mind, though, that the app is not a replacement for a professional editor. Tip #42. Use Hemingway Online content should be very easy to read & follow for everyone, whether they’re a senior profession with a Ph.D. or a college kid looking to learn a new topic. As such, your content should be written in a simple manner - and that’s where Hemingway comes in. It helps you keep your blog content simple. Tip #43. Create Compelling Headlines Want to drive clicks to your articles? You’ll need compelling headlines. Compare the two headlines below; which one would you click? 101 Productivity Tips \[To Get Things Done in 2021\] VS Productivity Tips Guide Exactly! To create clickable headlines, we recommend you include the following elements: Keyword Numbers Results Year (If Relevant) Tip #44. Nail Your Blog Content Formatting Format your blog posts well and avoid overly long walls of text. There’s a reason Backlinko content is so popular - it’s extremely easy to read and follow. Tip #45. Use Relevant Images In Your SEO Content Key here - relevant. Don’t just spray random stock photos of “office people smiling” around your posts; no one likes those.  Instead, add graphs, charts, screenshots, quote blocks, CSS boxes, and other engaging elements. Tip #46. Implement the Skyscraper Technique (The Right Way) Want to implement Backlinko’s skyscraper technique?  Keep this in mind before you do: not all content is meant to be promoted.  Pick a topic that fits the following criteria if you want the internet to care: It’s on an important topic. “Mega-Guide to SaaS Marketing” is good, “top 5 benefits of SaaS marketing” is not. You’re creating something significantly better than the original material. The internet is filled with mediocre content - strive to do better. Tip #47. Get The URL Slug Right for Seasonal Content If you want to rank on a seasonal keyword with one piece of content (e.g. you want to rank on “saas trends 2020, 2021, etc.”), don’t mention the year in the URL slug - keep it /saas-trends/ and just change the headline every year instead.  If you want to rank with separate articles, on the other hand (e.g. you publish a new trends report every year), include the year in the URL. Tip #48. Avoid content cannibalization.  Meaning, don’t write 2+ articles on one topic. This will confuse Google on which article it should rank. Tip #49. Don’t Overdo Outbound Links Don’t include too many outbound links in your content. Yes, including sources is good, but there is such a thing as overdoing it.  If your 1,000 word article has 20 outbound links, Google might consider it as spam (even if all those links are relevant). Tip #50. Consider “People Also Ask” To get the most out of SERP, you want to grab as many spots on the search result as possible, and this includes “people also ask (PAA):” Make a list of the topic’s PAA questions and ensure that your article answers them.  If you can’t fit the questions & answers within the article, though, you can also add an FAQ section at the end where you directly pose these questions and provide the answers. Tip #51. Optimize For Google Snippet Optimize your content for the Google Snippet. Check what’s currently ranking as the snippet. Then, try to do something similar (or even better) in terms of content and formatting. Tip #52. Get Inspired by Viral Content Want to create content that gets insane shares & links?  Reverse-engineer what has worked in the past. Look up content in your niche that went viral on Reddit, Hacker News, Facebook groups, Buzzsumo, etc. and create something similar, but significantly better. Tip #53. Avoid AI Content Tools No, robots can’t write SEO content.  If you’ve seen any of those “AI generated content tools,” you should know to stay away. The only thing those tools are (currently) good for is creating news content. Tip #54. Avoid Bad Content You will never, ever, ever rank with one 500-word article per week.  There are some SEO agencies (even the more reputable ones) that offer this as part of their service. Trust us, this is a waste of time. Tip #55. Update Your Content Regularly Check your top-performing articles annually and see if there’s anything you can do to improve them.  When most companies finally get the #1 ranking for a keyword, they leave the article alone and never touch it again… ...Until they get outranked, of course, by someone who one-upped their original article. Want to prevent this from happening? Analyze your top-performing content once a year and improve it when possible. Tip #56. Experiment With CTR Do your articles have low CTR? Experiment with different headlines and see if you can improve it.  Keep in mind, though, that what a “good CTR” is really depends on the keyword.  In some cases, the first ranking will drive 50% of the traffic. In others, it’s going to be less than 15%. Link-Building Tips Tip #57. Yes, Links Matter. Here’s What You Need to Know “Do I need backlinks to rank?” is probably one of the most common SEO questions.  The answer to the question (alongside all other SEO-related questions) is that it depends on the niche.  If your competitors don’t have a lot of backlinks, chances are, you can rank solely by creating superior content. If you’re in an extremely competitive niche (e.g. VPN, insurance, etc.), though, everyone has amazing, quality content - that’s just the baseline.  What sets top-ranking content apart from the rest is backlinks. Tip #58. Sometimes, You’ll Have to Pay For Links Unfortunately, in some niches, paying for links is unavoidable - e.g. gambling, CBD, and others. In such cases, you either need a hefty link-building budget, or a very creative link-building campaign (create a viral infographic, news-worthy story based on interesting data, etc.). Tip #59. Build Relationships, Not Links The very best link-building is actually relationship building.  Make a list of websites in your niche and build a relationship with them - don’t just spam them with the standard “hey, I have this amazing article, can you link to it?”.  If you spam, you risk ruining your reputation (and this is going to make further outreach much harder). Tip #60. Stick With The Classics At the end of the day, the most effective link-building tactics are the most straightforward ones:  Direct Outreach Broken Link-Building Guest Posting Skyscraper Technique Creating Viral Content Guestposting With Infographics Tip #61. Give, Don’t Just Take! If you’re doing link-building outreach, don’t just ask for links - give something in return.  This will significantly improve the reply rate from your outreach email. If you own a SaaS tool, for example, you can offer the bloggers you’re reaching out to free access to your software. Or, alternatively, if you’re doing a lot of guest posting, you can offer the website owner a link from the guest post in exchange for the link to your website. Tip #62. Avoid Link Resellers That guy DMing you on LinkedIn, trying to sell you links from a Google Sheet?  Don’t fall for it - most of those links are PBNs and are likely to backfire on you. Tip #63. Avoid Fiverr Like The Plague Speaking of spammy links, don’t touch anything that’s sold on Fiverr - pretty much all of the links there are useless. Tip #64. Focus on Quality Links Not all links are created equal. A link is of higher quality if it’s linked from a page that: Is NOT a PBN. Doesn’t have a lot of outbound links. If the page links to 20 other websites, each of them gets less link juice. Has a lot of (quality) backlinks. Is part of a website with a high domain authority. Is about a topic relevant to the page it’s linking to. If your article about pets has a link from an accounting blog, Google will consider it a bit suspicious. Tip #65. Data-Backed Content Just Works Data-backed content can get insane results for link-building.  For example, OKCupid used to publish interesting data & research based on how people interacted with their platform and it never failed to go viral. Each of their reports ended up being covered by dozens of news media (which got them a ton of easy links). Tip #66. Be Creative - SEO Is Marketing, After All Be novel & creative with your link-building initiatives.  Here’s the thing: the very best link-builders are not going to write about the tactics they’re using.  If they did, you’d see half the internet using the exact same tactic as them in less than a week! Which, as you can guess, would make the tactic cliche and significantly less effective. In order to get superior results with your link-building, you’ll need to be creative - think about how you can make your outreach different from what everyone does. Experiment it, measure it, and improve it till it works! Tip #67. Try HARO HARO, or Help a Reporter Out, is a platform that matches journalists with sources. You get an email every day with journalists looking for experts in specific niches, and if you pitch them right, they might feature you in their article or link to your website. Tip #68. No-Follow Links Aren’t That Bad Contrary to what you might’ve heard, no-follow links are not useless. Google uses no-follow as more of a suggestion than anything else.  There have been case studies that prove Google can disregard the no-follow tag and still reward you with increased rankings. Tip #69. Start Fresh With an Expired Domain Starting a new website? It might make sense to buy an expired one with existing backlinks (that’s in a similar niche as yours). The right domain can give you a serious boost to how fast you can rank. Tip #70. Don’t Overspend on Useless Links “Rel=sponsored” links don’t pass pagerank and hence, won’t help increase your website rankings.  So, avoid buying links from media websites like Forbes, Entrepreneur, etc. Tip #71. Promote Your Content Other than link-building, focus on organic content promotion. For example, you can repost your content on Facebook groups, LinkedIn, Reddit, etc. and focus on driving traffic.  This will actually lead to you getting links, too. We got around 95 backlinks to our SEO case study article just because of our successful content promotion. Tons of people saw the article on the net, liked it, and linked to it from their website. Tip #72. Do Expert Roundups Want to build relationships with influencers in your niche, but don’t know where to start?  Create an expert roundup article. If you’re in the sales niche, for example, you can write about Top 21 Sales Influencers in 2021 and reach out to the said influencers letting them know that they got featured. Trust us, they’ll love you for this! Tip #73. .Edu Links are Overhyped .edu links are overrated. According to John Mueller, .edu domains tend to have a ton of outbound links, and as such, Google ignores a big chunk of them. Tip #74. Build Relationships With Your Customers Little-known link-building hack: if you’re a SaaS company doing SEO, you can build relationships with your customers (the ones that are in the same topical niche as you are) and help each other build links! Tip #75. Reciprocal Links Aren’t That Bad Reciprocal links are not nearly as bad as Google makes them out to be. Sure, they can be bad at scale (if trading links is all you’re doing). Exchanging a link or two with another website / blog, though, is completely harmless in 99% of cases. Tip #76. Don’t Overspam Don’t do outreach for every single post you publish - just the big ones.  Most people already don’t care about your outreach email. Chances are, they’re going to care even less if you’re asking them to link to this new amazing article you wrote (which is about the top 5 benefits of adopting a puppy). Technical SEO Tips Tip #77. Use PageSpeed Insights If your website is extremely slow, it’s definitely going to impact your rankings. Use PageSpeed Insights to see how your website is currently performing. Tip #78. Load Speed Matters While load speed doesn’t impact rankings directly, it DOES impact your user experience. Chances are, if your page takes 5 seconds to load, but your competition’s loads instantly, the average Googler will drop off and pick them over you. Tip #79. Stick to a Low Crawl Depth Crawl depth of any page on your website should be lower than 4 (meaning, any given page should be possible to reach in no more than 3 clicks from the homepage).  Tip #80. Use Next-Gen Image Formats Next-gen image formats such as JPEG 2000, JPEG XR, and WebP can be compressed a lot better than PNG or JPG. So, when possible, use next-get formats for images on your website. Tip #81. De-Index Irrelevant Pages Hide the pages you don’t want Google to index (e.g: non-public, or unimportant pages) via your Robots.txt. If you’re a SaaS, for example, this would include most of your in-app pages or your internal knowledge base pages. Tip #82. Make Your Website Mobile-Friendly Make sure that your website is mobile-friendly. Google uses “mobile-first indexing.” Meaning, unless you have a working mobile version of your website, your rankings will seriously suffer. Tip #83. Lazy-Load Images Lazy-load your images. If your pages contain a lot of images, you MUST activate lazy-loading. This allows images that are below the screen, to be loaded only once the visitor scrolls down enough to see the image. Tip #84. Enable Gzip Compression Enable Gzip compression to allow your HTML, CSS and JS files to load faster. Tip #85. Clean Up Your Code If your website loads slowly because you have 100+ external javascript files and stylesheets being requested from the server, you can try minifying, aggregating, and inlining some of those files. Tip 86. Use Rel-Canonical Have duplicate content on your website? Use rel-canonical to show Google which version is the original (and should be prioritized for search results). Tip #87. Install an SSL Certificate Not only does an SSL certificate help keep your website safe, but it’s also a direct ranking factor. Google prioritizes websites that have SSL certificates over the ones that don’t. Tip #88. Use Correct Anchor Texts for Internal Links When linking to an internal page, mention the keyword you’re trying to rank for on that page in the anchor text. This helps Google understand that the page is, indeed, about the keyword you’re associating it with. Tip #89. Use GSC to Make Sure Your Content is Interlinked Internal links can have a serious impact on your rankings. So, make sure that all your blog posts (especially the new ones) are properly linked to/from your past content.  You can check how many links any given page has via Google Search Console. Tip #90. Bounce rate is NOT a Google ranking factor. Meaning, you can still rank high-up even with a high bounce rate. Tip #91. Don’t Fret About a High Bounce Rate Speaking of the bounce rate, you’ll see that some of your web pages have a higher-than-average bounce rate (70%+).  While this can sometimes be a cause for alarm, it’s not necessarily so. Sometimes, the search intent behind a given keyword means that you WILL have a high bounce rate even if your article is the most amazing thing ever.  E.g. if it’s a recipe page, the reader gets the recipe and bounces off (since they don’t need anything else). Tip #92. Google Will Ignore Your Meta Description More often than not, Google won’t use the meta description you provide - that’s normal. It will, instead, automatically pick a part of the text that it thinks is most relevant and use it as a meta description. Despite this, you should always add a meta description to all pages. Tip #93. Disavow Spammy & PBN Links Keep track of your backlinks and disavow anything that’s obviously spammy or PBNy. In most cases, Google will ignore these links anyway. However, you never know when a competitor is deliberately targeting you with too many spammy or PBN links (which might put you at risk for being penalized). Tip #94. Use The Correct Redirect  When permanently migrating your pages, use 301 redirect to pass on the link juice from the old page to the new one. If the redirect is temporary, use a 302 redirect instead. Tip #95. When A/B Testing, Do This A/B testing two pages? Use rel-canonical to show Google which page is the original. Tip #96. Avoid Amp DON’T use Amp.  Unless you’re a media company, Amp will negatively impact your website. Tip #97. Get Your URL Slugs Right Keep your blog URLs short and to-the-point. Good Example: apollodigital.io/blog/seo-case-study Bad Example: apollodigital.io/blog/seo-case-study-2021-0-to-200,000/ Tip #98. Avoid Dates in URLs An outdated date in your URL can hurt your CTR. Readers are more likely to click / read articles published recently than the ones written years back. Tip #99. Social Signals Matter Social signals impact your Google rankings, just not in the way you think. No, your number of shares and likes does NOT impact your ranking at all.  However, if your article goes viral and people use Google to find your article, click it, and read it, then yes, it will impact your rankings.  E.g. you read our SaaS marketing guide on Facebook, then look up “SaaS marketing” on Google, click it, and read it from there. Tip #100. Audit Your Website Frequently Every other month, crawl your website with ScreamingFrog and see if you have any broken links, 404s, etc. Tip #101. Use WordPress Not sure which CMS platform to use?  99% of the time, you’re better off with WordPress.  It has a TON of plugins that will make your life easier.  Want a drag & drop builder? Use Elementor. Wix, SiteGround and similar drag & drops are bad for SEO. Tip #102. Check Rankings the Right Way When checking on how well a post is ranking on Google Search Console, make sure to check Page AND Query to get the accurate number.  If you check just the page, it’s going to give you the average ranking on all keywords the page is ranking for (which is almost always going to be useless data). Conclusion Aaand that's about it - thanks for the read! Now, let's circle back to Tip #1 for a sec. Remember when we said a big chunk of what you read on SEO is based on personal experiences, experiments, and the like? Well, the tips we've mentioned are part of OUR experience. Chances are, you've done something that might be different (or completely goes against) our advice in this article. If that's the case, we'd love it if you let us know down in the comments. If you mention something extra-spicy, we'll even include it in this article.

#reddit#best#tips

reddit

0

1

AntsyNursery58•This week

AI Will Make You Extremely Rich or Kill Your Business in 2024

Preface: I'm a solo-founder in the AI space and previously worked as an ML scientist; the new advancements in AI that I'm seeing are going to impact everyone here. It doesn't matter if you're just starting out, or a bootstrapped brick and mortar founder, or even a VC backed hard tech founder. Last year was when the seeds were laid, and this is the year we'll see them bloom. There will be an onslaught of advancements that take place that are borderline inconceivable due to the nature of exponential progress. This will change every single vertical. I'm making this post because I think AI execution strategy will make or break businesses. Dramatically. Over $50B was put into AI startups in 2023 alone. This figure excludes the hundreds of billions poured into AI from enterprises. So, let's follow the money: &#x200B; 1) AI enterprise software. There's a lot to unpack here and this is what I’m currently working on. AI enterprise software will encompass everything from hyper personalized email outbound to AI cold calls to AI that A/B tests ads on synthetic data to vertical specific software. The impact of the former is relatively self explanatory, so I'll focus on the latter. To illustrate vertical specific AI software, I'll use a simple example in the legal space. Lawyers typically have to comb through thousands of pages of documents. Now, using an LLM + a VDB, an AI can instantly answer all of those questions while surfacing the source and highlighting the specific answer in the contract/document. There are dozens of AI startups for this use case alone. This saves lawyers an immense amount of time and allows them to move faster. Firms that adopt this have a fundamental advantage over law firms that don't adopt this. This was 2023 technology. I'm seeing vertical AI software getting built by my friends in areas from construction, to real estate, to even niche areas like chimney manufacturing. This will exist everywhere. Now, this can be extrapolated much further to be applicable to systems that can do reports and even browse the Internet. This brings me to my next point. &#x200B; 2) AI information aggregation and spread. My gut tells me that this will have a crescendo moment in the future with hardware advancements (Rabbit, Tab, etc.). You won't have to google things because it will be surfaced to you. It's predictive in nature. The people who can get information the fastest will grow their business the fastest. This part is semi-speculative, but due to the nature of LLMs being so expensive to train, I have a strong feeling that large institutions will have access to the \fastest\ and \best\ models that can do this quicker than you and I can. This is why it's important to stay on top. &#x200B; 3) AI content generation This is relevant to running advertisements and any digital marketing aspect of your business. If you can rapidly make content faster than your competitors to put in social media, you will outpace your competitors rapidly. I think most folks are familiar with MidJourney, Stable diffusion, etc. but don't know how to use it. You can generate consistent models for a clothing brand or generate images of a product that you would normally need to hire a professional photographer to take. There's also elevenlabs which is relatively easy to use and can be used to make an MP3 clip as a narration for an ad; this is something I've already done. I'm also still shocked by how many people are unfamiliar with tools like Pika which can do video generation. You could imagine companies having fleets of digital influencers that they control or conjuring up the perfect ad for a specific demographic using a combination of all of the aforementioned tools. &#x200B; In summary, if you feel like I'm being hyperbolic or propagating science fiction fantasies, you're likely already behind. I truly recommend that everyone stays up to date on these advancements as much as possible. If your competitor comes across an AI tool that can increase their ROAS by 5x they can crush you. If your competitor uses a tool that increases the rate at which they receive and aggregate information by 200% (modest estimate) they will crush you. If your competitors have a tool that can reduce their employee size, then they will use it. They'll fire their employees to cut costs and reinvest the money back into their business. It will compound to the point where you're outpaced, and this isn't a level of innovation we've seen since the birth of the industrial revolution. Your customers can get stolen overnight, or you can steal your competition’s customers overnight. TL;DR: This is an opportunity for entrepreneurs to scale faster than they could have possibly imagined, but this also comes with the potential for your company to be obliterated. We've never seen advancements that can have this drastic of an impact this quickly. Adoption will happen fast, and first movers will have a disproportionate and compounding advantage. Watch guides, meet with startups, follow the news, and get rich.

#reddit#will#make

reddit

0

1

jottrled•This week

How I went from $27 to $3K as a solopreneur still in a 9-5

My journey started back in November 2023. I was scrolling through Twitter and YouTube and saw a word that I had never come across before. Solopreneur. The word caught my eye. Mainly because I was pretty sure I knew what it meant even though it's not a word you'll find in the dictionary. I liked what it was describing. A solo entrepreneur. A one man business. It completely resonated with me. As a software engineer by trade I'm used to working alone, especially since the pandemic hit and we were forced to work remotely. See, I always wanted to ditch the 9-5 thing but thought that was too big and too scary for a single person to do. Surely you would need a lot of money to get started, right? Surely you would need investors? The whole concept seemed impossible to me. That was until I found all the success stories. I became obsessed with the concept of solopreneurship. As I went further down the rabbit hole I found people like Justin Welsh, Kieran Drew and Marc Louvion to name a few. All of whom have one person businesses making huge money every year. So I thought, if they can do it, why can't I? People like this have cleared the pathway for those looking to escape the 9-5 grind. I decided 2024 would be the year I try this out. My main goal for the year? Build a one man business, earn my first $ online and learn a sh\*t ton along the way. My main goal in general? Build my business to $100K per year, quit my 9-5 and live with freedom. From December 2023 to February 2024 I began brainstorming ideas. I was like a lost puppy looking for his ball. How on earth did people find good ideas? I began writing everything and anything that came to mind down in my notes app on my phone. By February I would have approximately 70 ideas. Each as weird and whacky as the other. I was skeptical though. If I went through all the trouble of building a product for one of these ideas how would I know if anyone would even be interested in using it? I got scared and took a break for a week. All these ideas seemed too big and the chance that they would take off into the atmosphere was slim (in my mind anyways). I was learning more and more about solopreneurship as the weeks went on so I decided to build a product centered around everything I was learning about. The idea was simple. Enter a business idea and use AI to give the user details about how to market it, who their target customers were, what to write on their landing page, etc. All for a measly $27 per use. I quickly built it and launched on March 3rd 2024. I posted about it on Indie Hackers, Reddit and Hacker News. I was so excited about the prospect of earning my first internet $! Surely everyone wanted to use my product! Nope...all I got was crickets. I was quickly brought back down to earth. That was until 5 days later. I looked at my phone and had a new Stripe notification! Cha-ching! My first internet $. What a feeling! That was goal number 1 complete. It would be another 6 days before I would get my second sale...and then another 15 days to get my third. It was an emotional rollercoaster. I went from feeling like quitting the 9-5 was actually possible to thinking that maybe the ups and downs aren't worth it. On one hand I had made my first internet dollar so I should my ecstatic, and don't get me wrong, I was but I wanted more. More validation that I could do this long term. By May I was starting to give up on the product. I had learned so much in the past few months about marketing, SEO, building an audience, etc. and I wanted to build something that I thought could have more success so I focused on one critical thing that I had learned about. What was it? Building a product that had SEO potential. A product that I knew hundreds of people were looking for. See this was my thinking - If I could find a keyword that people were searching for on Google hundreds/thousands of times every month and it was easy to rank high on search engines then I would go all in (in SEO land this equates to a Keyword that has a Keyword Difficulty of = 500). I began researching and found that the keyword "micro saas ideas" was being searched for around 600 times each month. Micro Saas was something that really interested me. It was perfect for solopreneurs. Small software products that 1 person could build. What's not to like if you're in the game of software and solopreneurship? Researching keywords like this became like a game for me. I was hooked. I was doing it every day, finding gems that were being searched for hundreds and thousands of times every month that still had potential. That's when I came up with my next product idea. I decided to create a database of Micro Saas Ideas all with this sort of SEO potential. See if you can build a product that you know people are looking for then that's all the validation you need. So I put this theory to the test. I created a database of Micro Saas Ideas with SEO Potential and launched it in June 2024. This time it was different. I made $700 in the first week of launching. A large contrast to my previous failed attempt at becoming the worlds greatest solopreneur. Since launch I have grown the product to $3K and I couldn't be happier. I know what you're saying, $3K isn't a lot. But it's validation. It's validation that I can earn $ online. Validation that I can grow a business and it gives me hope that one day I'll be able to quit that 9-5 grind. My plan is to keep growing the business. I expect there to be a few challenges up ahead but I'll tackle them as I go and learn from the failures and successes. I have a newsletter where I share Micro Saas Ideas with SEO potential every week which I'll leave below in the first comment. Feel free to come along for the ride. If not I hope this post brings you some value If you're thinking about starting as a solopreneur, stop thinking and start doing, you won't regret it.

#reddit#went#solopreneur

reddit

0

1

jamesackerman1234•This week

[CASE STUDY] From 217/m to $2,836/m in 9 months - Sold for $59,000; I grow and monetise web traffic of 5, 6, 7 figures USD valued passive income content sites [AMA]

Hello Everyone (VERY LONG CASE STUDY AHEAD) - 355% return in 9 months Note: I own a 7-figures USD valued portfolio of 41+ content sites that generates 5-6 figures USD a month in passive income. This is my first time posting in this sub and my goal is to NOT share generic advice but precise numbers, data and highly refined processes so you can also get started with this business yourself or if you already have an existing business, drive huge traffic to it and scale it substantially (get more customers). I will use a case study to explain the whole process. As most of us are entrepreneurs here, explaining an actual project would be more meaningful. In this case study I used AI assisted content to grow an existing site from $217/m to $2,836/m in 9 months (NO BACKLINKS) and sold it for $59,000. ROI of 3 months: 355% Previous case studies (before I give an overview of the model) Amazon Affiliate Content Site: $371/m to $19,263/m in 14 MONTHS - $900K CASE STUDY \[AMA\] Affiliate Website from $267/m to $21,853/m in 19 months (CASE STUDY - Amazon?) \[AMA\] Amazon Affiliate Website from $0 to $7,786/month in 11 months Amazon Affiliate Site from $118/m to $3,103/m in 8 MONTHS (SOLD it for $62,000+) Note: You can check pinned posts on my profile. Do go through the comments as well as a lot of questions are answered in those. However, if you still have any questions, feel free to reach out. This is an \[AMA\]. Quick Overview of the Model Approach: High traffic, niche specific, informative content websites that monetise its traffic through highly automated methods like display ads and affiliate. The same model can be applied to existing businesses to drive traffic and get customers. Main idea: Make passive income in a highly automated way Easy to understand analogy You have real estate (here you have digital asset like a website) You get rental income (here you get ads and affiliate income with no physical hassle, in case you have a business like service, product etc. then you can get customers for that too but if not, it's alright) Real estate has value (this digital asset also has value that can be appreciated with less effort) Real estate can be sold (this can be sold too but faster) IMPORTANT NOTE: Search traffic is the BEST way to reach HUGE target audience and it's important when it comes to scaling. This essentially means that you can either monetise that via affiliate, display etc. or if you have a business then you can reach a bigger audience to scale. Overview of this website's valuation (then and now: Oct. 2022 and June 2023) Oct 2022: $217/m Valuation: $5,750.5 (26.5x) - set it the same as the multiple it was sold for June 2023: $2,836/m Traffic and revenue trend: growing fast Last 3 months avg: $2,223 Valuation now: $59,000 (26.5x) Description: The domain was registered in 2016, it grew and then the project was left unattended. I decided to grow it again using properly planned AI assisted content. Backlink profile: 500+ Referring domains (Ahrefs). Backlinks mean the sites linking back to you. This is important when it comes to ranking. Summary of Results of This Website - Before and After Note: If the terms seem technical, do not worry. I will explain them in detail later. Still if you have any questions. Feel free to comment or reach out. |Metric|Oct 2022|June 2023|Difference|Comments| |:-|:-|:-|:-|:-| |Articles|314|804|\+490|AI Assisted content published in 3 months| |Traffic|9,394|31,972|\+22,578|Organic| |Revenue|$217|$2,836|\+$2,619|Multiple sources| |RPM (revenue/1000 web traffic)|23.09|$88.7|\+$65.61|Result of Conversion rate optimisation (CRO). You make changes to the site for better conversions| |EEAT (expertise, experience, authority and trust of website)|2 main authors|8 authors|6|Tables, video ads and 11 other fixations| |CRO|Nothing|Tables, video ads |Tables, video ads and 11 other fixations || &#x200B; Month by Month Growth |Month|Revenue|Steps| |:-|:-|:-| |Sept 2022|NA|Content Plan| |Oct 2022|$217|Content Production| |Nov 2022|$243|Content production + EEAT authors| |Dec 2022|$320|Content production + EEAT authors| |Jan 2023|$400|Monitoring| |Feb 2023|$223|Content production + EEAT authors| |Mar 2023|$2,128|CRO & Fixations| |April 2023|$1,609|CRO & Fixations| |May 2023|$2,223|Content production + EEAT authors| |June 2023|$2,836|CRO and Fixations| |Total|$10,199|| &#x200B; What will I share Content plan and Website structure Content Writing Content Uploading, formatting and onsite SEO Faster indexing Conversion rate optimisation Guest Posting EEAT (Experience, Expertise, Authority, Trust) Costing ROI The plans moving forward with these sites &#x200B; Website Structure and Content Plan This is probably the most important important part of the whole process. The team spends around a month just to get this right. It's like defining the direction of the project. Description: Complete blueprint of the site's structure in terms of organisation of categories, subcategories and sorting of articles in each one of them. It also includes the essential pages. The sorted articles target main keyword, relevant entities and similar keywords. This has to be highly data driven and we look at over 100 variables just to get it right. It's like beating Google's algorithm to ensure you have a blueprint for a site that will rank. It needs to be done right. If there is a mistake, then even if you do everything right - it's not going to work out and after 8-16 months you will realise that everything went to waste. Process For this project, we had a niche selected already so we didn't need to do a lot of research pertaining to that. We also knew the topic since the website was already getting good traffic on that. We just validated from Ahrefs, SEMRUSH and manual analysis if it would be worth it to move forward with that topic. &#x200B; Find entities related to the topic: We used Ahrefs and InLinks to get an idea about the related entities (topics) to create a proper topical relevance. In order to be certain and have a better idea, we used ChatGPT to find relevant entities as well \> Ahrefs (tool): Enter main keyword in keywords explorer. Check the left pain for popular topics \> Inlinks (tool): Enter the main keyword, check the entity maps \> ChatGPT (tool): Ask it to list down the most important and relevant entities in order of their priority Based on this info, you can map out the most relevant topics that are semantically associated to your main topic Sorting the entities in topics (categories) and subtopics (subcategories): Based on the information above, cluster them properly. The most relevant ones must be grouped together. Each group must be sorted into its relevant category. \> Example: Site about cycling. \> Categories/entities: bicycles, gear and equipment, techniques, safety, routes etc. \> The subcategories/subentities for let's say "techniques" would be: Bike handling, pedaling, drafting etc. Extract keywords for each subcategory/subentity: You can do this using Ahrefs or Semrush. Each keyword would be an article. Ensure that you target the similar keywords in one article. For example: how to ride a bicycle and how can I ride a bicycle will be targeted by one article. Make the more important keyword in terms of volume and difficulty as the main keyword and the other one(s) as secondary Define main focus vs secondary focus: Out of all these categories/entities - there will be one that you would want to dominate in every way. So, focus on just that in the start. This will be your main focus. Try to answer ALL the questions pertaining to that. You can extract the questions using Ahrefs. \> Ahrefs > keywords explorer \> enter keyword \> Questions \> Download the list and cluster the similar ones. This will populate your main focus category/entity and will drive most of the traffic. Now, you need to write in other categories/subentities as well. This is not just important, but crucial to complete the topical map loop. In simple words, if you do this Google sees you as a comprehensive source on the topic - otherwise, it ignores you and you don't get ranked Define the URLs End result: List of all the entities and sub-entities about the main site topic in the form of categories and subcategories respectively. A complete list of ALL the questions about the main focus and at around 10 questions for each one of the subcategories/subentities that are the secondary focus Content Writing So, now that there's a plan. Content needs to be produced. Pick out a keyword (which is going to be a question) and... Answer the question Write about 5 relevant entities Answer 10 relevant questions Write a conclusion Keep the format the same for all the articles. Content Uploading, formatting and onsite SEO Ensure the following is taken care of: H1 Permalink H2s H3s Lists Tables Meta description Socials description Featured image 2 images in text \\Schema Relevant YouTube video (if there is) Note: There are other pointers link internal linking in a semantically relevant way but this should be good to start with. Faster Indexing Indexing means Google has read your page. Ranking only after this step has been done. Otherwise, you can't rank if Google hasn't read the page. Naturally, this is a slow process. But, we expedite it in multiple ways. You can use RankMath to quickly index the content. Since, there are a lot of bulk pages you need a reliable method. Now, this method isn't perfect. But, it's better than most. Use Google Indexing API and developers tools to get indexed. Rank Math plugin is used. I don't want to bore you and write the process here. But, a simple Google search can help you set everything up. Additionally, whenever you post something - there will be an option to INDEX NOW. Just press that and it would be indexed quite fast. Conversion rate optimisation Once you get traffic, try adding tables right after the introduction of an article. These tables would feature a relevant product on Amazon. This step alone increased our earnings significantly. Even though the content is informational and NOT review. This still worked like a charm. Try checking out the top pages every single day in Google analytics and add the table to each one of them. Moreover, we used EZOIC video ads as well. That increased the RPM significantly as well. Both of these steps are highly recommended. Overall, we implemented over 11 fixations but these two contribute the most towards increasing the RPM so I would suggest you stick to these two in the start. Guest Posting We made additional income by selling links on the site as well. However, we were VERY careful about who we offered a backlink to. We didn't entertain any objectionable links. Moreover, we didn't actively reach out to anyone. We had a professional email clearly stated on the website and a particularly designated page for "editorial guidelines" A lot of people reached out to us because of that. As a matter of fact, the guy who bought the website is in the link selling business and plans to use the site primarily for selling links. According to him, he can easily make $4000+ from that alone. Just by replying to the prospects who reached out to us. We didn't allow a lot of people to be published on the site due to strict quality control. However, the new owner is willing to be lenient and cash it out. EEAT (Experience, Expertise, Authority, Trust) This is an important ranking factor. You need to prove on the site that your site has authors that are experienced, have expertise, authority and trust. A lot of people were reaching out to publish on our site and among them were a few established authors as well. We let them publish on our site for free, added them on our official team, connected their socials and shared them on all our socials. In return, we wanted them to write 3 articles each for us and share everything on all the social profiles. You can refer to the tables I shared above to check out the months it was implemented. We added a total of 6 writers (credible authors). Their articles were featured on the homepage and so were their profiles. Costing Well, we already had the site and the backlinks on it. Referring domains (backlinks) were already 500+. We just needed to focus on smart content and content. Here is the summary of the costs involved. Articles: 490 Avg word count per article: 1500 Total words: 735,000 (approximately) Cost per word: 2 cents (includes research, entities, production, quality assurance, uploading, formatting, adding images, featured image, alt texts, onsite SEO, publishing/scheduling etc.) Total: $14,700 ROI (Return on investment) Earning: Oct 22 - June 23 Earnings: $10,199 Sold for: $59,000 Total: $69,199 Expenses: Content: $14,700 Misc (hosting and others): $500 Total: $15,200 ROI over a 9 months period: 355.25% The plans moving forward This website was a part of a research and development experiment we did. With AI, we wanted to test new waters and transition more towards automation. Ideally, we want to use ChatGPT or some other API to produce these articles and bulk publish on the site. The costs with this approach are going to be much lower and the ROI is much more impressive. It's not the the 7-figures projects I created earlier (as you may have checked the older case studies on my profile), but it's highly scalable. We plan to refine this model even further, test more and automate everything completely to bring down our costs significantly. Once we have a model, we are going to scale it to 100s of sites. The process of my existing 7-figures websites portfolio was quite similar. I tested out a few sites, refined the model and scaled it to over 41 sites. Now, the fundamentals are the same however, we are using AI in a smarter way to do the same but at a lower cost, with a smaller team and much better returns. The best thing in my opinion is to run numerous experiments now. Our experimentation was slowed down a lot in the past since we couldn't write using AI but now it's much faster. The costs are 3-6 times lower so when it used to take $50-100k to start, grow and sell a site. Now you can pump 3-6 more sites for the same budget. This is a good news for existing business owners as well who want to grow their brand. Anyway, I am excited to see the results of more sites. In the meantime, if you have any questions - feel free to let me know. Best of luck for everything. Feel free to ask questions. I'd be happy to help. This is an AMA.

#reddit#[case#study]

reddit

0

0.857

adamkstinson•This week

AI Content Campaign Got 4M impressions, Thousands of Website Views, Hundreds of Customers for About $100 — This is the future of marketing

Alright. So, a few months ago I tested a marketing strategy for a client that I’ve sense dedicated my life to developing on. The Idea was to take the clients Pillar content (their YouTube videos) and use AI to rewrite the content for all the viable earned media channels (mainly Reddit). The campaign itself was moderately successful. To be specific, after one month it became their 2nd cheapest customer acquisition cost (behind their organic YouTube content). But there is a lot to be done to improve the concept. I will say, having been in growth marketing for a decade, I felt like I had hit something big with the concept. I’m going to detail how I built that AI system, and what worked well and what didn’t here. Hopefully you guys will let me know what you think and whether or not there is something here to keep working on. DEFINING THE GOAL Like any good startup, their marketing budget was minimal. They wanted to see results, fast and cheap. Usually, marketers like me hate to be in this situation because getting results usually either takes time or it takes money. But you can get results fast and cheap if you focus on an earned media strategy - basically getting featured in other people’s publication. The thing is these strategies are pretty hard to scale or grow over time. That was a problem for future me though. I looked through their analytics and saw they were getting referral traffic from Reddit - it was their 5th or 6th largest source of traffic - and they weren’t doing any marketing on the platform. It was all digital word of mouth there. It kind of clicked for me there, that Reddit might be the place to start laying the ground work. So with these considerations in mind the goal became pretty clear: Create content for relevant niche communities on Reddit with the intent of essentially increasing brand awareness. Use an AI system to repurpose their YouTube videos to keep the cost of producing unique content for each subreddit really low. THE HIGH-LEVEL STRATEGY I knew that there are huge amounts of potential customers on Reddit (About 12M people in all the relevant communities combined) AND that most marketers have a really tough time with the platform. I also knew that any earned media strategy, Reddit or not, means Click Through Rates on our content would be extremely low. A lot of people see this as a Reddit specific problem because you can’t self-promote on the platform, but really you have to keep self-promotion to a minimum with any and all earned media. This basically meant we had to get a lot of impressions to make up for it. The thing about Reddit is if your post absolutely crushes it, it can get millions of views. But crushing it is very specific to what the expectations are of that particular subreddit. So we needed to make content that was specifically written for that Subreddit. With that I was able to essentially design how this campaign would work: We would put together a list of channels (specifically subreddits to start) that we wanted to create content for. For each channel, we would write a content guideline that details out how to write great content for this subreddit. These assets would be stored in an AirTable base, along with the transcripts of the YouTube videos that were the base of our content. We would write and optimize different AI Prompts that generated different kinds of posts (discussion starters about a stock, 4-5 paragraph stock analysis, Stock update and what it means, etc…) We would build an automation that took the YouTube transcripts, ran each prompt on it, and then edited each result to match the channel writing guidelines. And then we would find a very contextual way to leave a breadcrumb back to the client. Always as part of the story of the content. At least, this is how I originally thought things would go. CHOOSING THE RIGHT SUBREDDITS Picking the right communities was vital. Here’s the basic rubric we used to pick and prioritize them: • Relevance: We needed communities interested in stock analysis, personal finance, or investing. • Subreddit Size vs. Engagement: Large subreddits offer more potential impressions but can be less focused. Smaller subreddits often have higher engagement rates. • Content Feasibility: We had to ensure we could consistently create high-value posts for each chosen subreddit. We started with about 40 possibilities, then narrowed it down to four or five that consistently delivered upvotes and user signups. CREATING CHANNEL-SPECIFIC GUIDES By the end, creating channel specific writing guidelines looked like a genius decision. Here’s how we approached it and used AI to get it done quickly: Grabbed Top Posts: We filtered the subreddit’s top posts (change filter to “Top” and then “All Time”) of all time to see the kinds of content that performed best Compiled The Relevant Posts: We took the most relevant posts to what we were trying to do and put them all on one document (basically created one document per subreddit that just had the top 10 posts in that subreddit). Had AI Create Writing Guideline Based On Posts: For each channel, we fed the document with the 10 posts with the instructions “Create a writing guideline for this subreddit based on these high performing posts. I had to do some editing on each guideline but this worked pretty well and saved a lot of time. Each subreddit got a custom guideline, and we put these inside the “Channels” table of the AirTable base we were developing with these assets. BUILDING THE AI PROMPTS THAT GENERATED CONTENT Alright this is probably the most important section so I’ll be detailed. Essentially, we took all the assets we developed up until this point, and used them to create unique posts for each channel. This mean each AI prompt was about 2,000 words of context and produced about a 500-word draft. There was a table in our AirTable where we stored the prompts, as I alluded to earlier. And these were basically the instructions for each prompt. More specifically, they detailed out our expectations for the post. In other words, there were different kinds of posts that performed well on each channel. For example, you can write a post that’s a list of resources (5 tools we used to…), or a how to guide (How we built…), etc.. Those weren’t the specific ones we used, but just wanted to really explain what I meant there. That actual automation that generated the content worked as follows: New source content (YouTube video transcript) was added to the Source Content table. This triggered the Automation. The automation grabbed all the prompts in the prompt table. For each prompt in the prompt table, we sent a prompt to OpenAI (gpt-4o) that contained first the prompt and also the source content. Then, for each channel that content prompt could be used on, we sent another prompt to OpenAI that revised the result of the first prompt based on the specific channel guidelines. The output of that prompt was added to the Content table in AirTable. To be clear, our AirTable had 4 tables: Content Channels Prompts Source Content The Source Content, Prompts, and Channel Guidelines were all used in the prompt that generated content. And the output was put in the Content table. Each time the automation ran, the Source Content was turned into about 20 unique posts, each one a specific post type generated for a specific channel. In other words, we were create a ton of content. EDITING & REFINING CONTENT The AI drafts were never perfect. Getting them Reddit-ready took editing and revising The main things I had to go in and edit for were: • Tone Adjustments: We removed excessively cliche language. The AI would say silly things like “Hello fellow redditors!” which sound stupid. • Fact-Checking: Financial data can be tricky. We discovered AI often confused figures, so we fact check all stock related metrics. Probably something like 30-40% error rate here. Because the draft generation was automated, that made the editing and getting publish ready the human bottleneck. In other words, after creating the system I spent basically all my time reviewing the content. There were small things I could do to make this more efficient, but not too much. The bigger the model we used, the less editing the content needed. THE “BREADCRUMB” PROMOTION STRATEGY No where in my prompt to the AI did I mention that we were doing any marketing. I just wanted the AI to focus on creating content that would do well on the channel. So in the editing process I had to find a way to promote the client. I called it a breadcrumb strategy once and that stuck. Basically, the idea was to never overtly promote anything. Instead find a way to leave a breadcrumb that leads back to the client, and let the really interested people follow the trail. Note: this is supposed to be how we do all content marketing. Some examples of how we did this were: Shared Visuals with a Subtle Watermark: Because our client’s product offered stock data, we’d often include a chart or graph showing a company’s financial metric with the client’s branding in the corner. Added Supporting Data from Client’s Website: If we mentioned something like a company’s cash flow statement, we could link to that company’s cash flow statement on the client’s website. It worked only because there was a lot of data on the client’s website that wasn’t gated. These tactics were really specific to the client. Which is should be. For other companies I would rethink what tactics I use here. THE RESULTS I’m pretty happy with the results • Impressions: – Early on posts averaged \~30,000 apiece, but after about a month of optimization, we hit \~70,000 impressions average. Over about two months, we reached 4 million total impressions. • Signups: – In their signups process there was one of those “Where did you find us?” questions and the amount of people who put Reddit jumped into the few hundred a month. Precise tracking of this is impossible. • Cost Efficiency (This is based on what I charged, and not the actual cost of running the campaign which is about $100/mo): – CPM (cost per thousand impressions) was about $0.08, which is far better than most paid channels. – Cost per free user: \~$8-10. After about a 10% conversion rate to a paid plan, our cost per paying user was $80–$100—well below the client’s previous $300–$400. HIGHLIGHTS: WHAT WORKED Subreddit-Specific Content: – Tailoring each post’s format and length to the audience norms boosted engagement. Worked out really well. 1 post got over 1M views alone. We regularly had posts that had hundreds of thousands. Breadcrumbs: – We never had anyone call us out for promoting. And really we weren’t. Our first priority was writing content that would crush on that subreddit. Using the Founder’s Existing Material: – The YouTube transcripts grounded the AI’s content in content we already made. This was really why we were able to produce so much content. CHALLENGES: WHAT DIDN’T WORK AI is still off: – Maybe it’s expecting too much, but still I wish the AI had done a better job. I editing a lot of content. Human oversight was critical. Scheduling all the content was a pain: – Recently I automated this pretty well. But at first I was scheduling everything manually and scheduling a hundred or so posts was a hassle. Getting Data and Analytics: – Not only did we have not very good traffic data, but the data from reddit had to be collected manually. Will probably automate this in the future. COST & TIME INVESTMENT Setup: The setup originally took me a couple weeks. I’ve since figured out how to do much faster (about 1 week). AirTable Setup here was easy and the tools costs $24/mo so not bad. ChatGPT costs were pretty cheap. Less than $75 per month. I’ve sense switched to using o1 which is much more expensive but saves me a lot of editing time Human Editing: Because this is the human part of the process and everything else was automated it mean by default all my time was spent editing content. Still this was a lot better than creating content from scratch probably by a factor of 5 or 10. The main expense was paying an editor (or using your own time) to refine posts. Worth it? Yes even with the editing time I was able to generate way more content that I would have otherwise. LESSONS & ACTIONABLE TAKEAWAYS Reddit as a Growth Channel: – If you genuinely respect each subreddit’s culture, you can achieve massive reach on a tight budget. AI + Human Collaboration: – AI excels at first drafts, but human expertise is non-negotiable for polishing and ensuring factual integrity. Soft Promotion Wins: – The “breadcrumb” approach paid off. It might feel like too light a touch, but is crucial for Reddit communities. Create once, repurpose as many times as possible: – If you have blog posts, videos, podcasts, or transcripts, feed them into AI to keep your message accurate and brand-consistent. CONCLUSION & NEXT STEPS If you try a similar approach: • Begin with smaller tests in a few niches to learn what resonates. • Create a clear “channel guide” for each community. • Carefully fact-check AI-generated posts. • Keep brand mentions low-key until you’ve established credibility.

#reddit#content#campaign

reddit

0

1

BalloonWheelie•This week

Why the value of writing code and other digital services is going to zero

I must preface this with a trigger warning because I make some statements in this post that might be upsetting to some. This post discusses my experience building in the new era of entrepreneurship, which is one where the founder is the center of the universe, and the consultants, overpriced SaaS, and corporate swamp creatures are replaced by single-user custom software, bots, and self-hosted automations. If you work in the legacy economy, I really don't intend to stress you out or say things you are doing are quickly becoming irrelevant, but I must share the reality of how I am operating, because I would like to hear from others who are doing the same, or desire to do the same. I am currently operating with the belief that AI-powered tools are going to make 1-person million dollar businesses much more common. Building anything digital is becoming extremely easy, cheap, and quick to implement. The value of code and digital tools is approaching zero, or at most 5% of what it currently is. Right now, the most powerful AI tools are aimed at developers, so folks who have some technical and business ability basically have nothing holding them back aside from the speed of their brain right now. I happen to be a part of the cohort, and am building like there is no tomorrow, but I don't believe this cohort is actually all that big. The next hurdle to unlock the new era of entrepreneurship is empowering every entrepreneur to build at the same pace that is currently locked behind having technical ability. This cohort is huge (millions, if the number of people in this sub is any indication). This post is aimed at them (you?). If you are part of this cohort, what is holding you back from launching a new product for near-zero cost? What is too complicated, too expensive, too unknown for you to be able to build your new/current business at maximum speed? I look forward to seeing the replies, I hope some insights shared can help the community, and be a catalyst for more tools to enable non-technical founders to launch. I will now share some of how I am testing, launching, and selling as a one-man-show. This will be a little bit technical, but if the output of any layer of my stack is something you want, please comment because maybe someone will build a cheap way of accessing it without needing to manage the code yourself. \#1 BOTS I cannot overstate how much leverage bots have created for me. I run all of my bots locally and interface with with via Telegram. Bots do things like: \- watch social media pages, forums, subreddits, etc related to my customers and notify me of what is going on, and suggest SEO blog posts that could be published to capture traffic related to the topic. with a single message, my bot will generate a blog post, send it to me for review, apply edits i suggest, and then publish it live, all from within telegram \- pay attention to all my key metrics/analytics, and attempt to find insights/corrolations (ex. there is a lot of traffic on this page, blog post, video, etc. here's why, and how we can take advantage of it to drive business goals) \- repurposing content. i have dozens of social media profiles that are 100% run by bots, they are all related to my customer niches and will do things like post news, snippets from my blogs, interact with human creators in the niche, etc. this builds my audience automatically which I can then advertise to/try to convert into paying customers, since they are interested in the things my bot is posting and become followers, it's like automated qualified lead gen 24/7 across every social platform and every niche I care about. you may be thinking by now that this post is made by a bot, but you will have to trust me that this is 100% hand-written by my sleep-deprived brain. let's continue: \#2 replacing every SaaS with a shitty version of it designed for what i need out of it it's absurd that we pay ten's of dollars per seat per month for basic digital functions like chat (slack), CRM (active camppaign, sales force, hubspot, etc), email stuff (mailchip, etc), link sharing (linktree, etc), website builders (wix, squarespace, etc), etc. all of these SaaS tools are overpriced and overbuilt. I believe many of them are going to be caught in the innovators dilemma and will go to 0. I don't use any of these anymore, I build and self-host my own shitty version of each of them that does only what i need out of the tool. for example, my CRM doesn't have a fancy drag and drop email builder and 10000 3rd party plugins, because i dont need any of that shit I just need to segment and communicate with my customers. if i need more features, i can generate them on the fly. \#3 working alone I have worked with cofounders in the past, raised money from investors, hired consultants, burned money and time, suffered sleepless nights from stress caused by other people not delivering, trying to convince others they are wrong, or they are pushing the company off a cliff, waste waste waste. no more of that. In the new age of entrepreneurship, the BUILDER (you and I) are the ones creating the value, and AI empowers us to do it alone. this might seem daunting, but there is no business problem that can't be solved with a detailed discussion sesh with chatgpt, no facts that can't be found with perplexity, and no task that can't be automated with claude. there is no need for anymore swamp creatures. you are the start and the end point, you don't need to rely on anyone else for anything. this may sound ignorant, but this is the conclusion I have come to believe, and it continues to be proven every day my businesses progress with me being the only human involved. This is getting quite long so I'll cut it here. I look forward to hearing about how you are operating in this new era and hopefully getting inspired/learning some new ideas to add to my current stack.

#reddit#value#writing

reddit

0

0.5

ImpossibleBell4759•This week

ChatGPT, Claude.ai and Perplexity for my Youtube Business

I use ChatGPT, Claude. ai and Perplexity for my Youtube Software Review Businesses. I run OVER 20 Youtube Faceless Software Review channels, and those AI tools basically help me with ideas, titles and descriptions. I like how simple is it to use those AI tools and crank out ideas, titles and descriptions in less than 20 minutes. ChatGPT, Claude. ai and Perplexity save me so much time. Managing all those Youtube channels is an all day event. I also save time by not editing and not scripting my videos. I do software reviews and I crank out 3 videos per hour. I can use software to automate some of the videos, but they don't get the same effect, so I do every video with original content. I'm thinking about using Elevenlabs. com so I can have access to hundreds of voices that I can use for my videos. I like their "Speech to Speech" technology. The only problem with Elevenlabs is that I have to do some editing to make it work... and I hate editing. I rather just record my video and upload it to Youtube. I might have to skip on Elevenlabs and the editing, because I need to crank out at least 20 videos per day. It seems like a lot but I focus on 12 hours a day and 3 videos per hour. 12 hours times 3 videos= 36 videos per day. But I only need 20 videos in the 12 hours, so I know I can meet my quota for the day. I'm looking at 20 videos per day times roughly 30 days is 600 videos per month. My goal is to finish the year with at least $100,000 in "CASH" after taxes, paying rent, buying food and having all my bills paid. So, I need to make $273.97 per day times 365 days= $100,000. The most I've made was off 1 video with only 600 views and I made over $3,300. I wasn't even monetized by Youtube. I made all that money from software commissions alone. I don't care about being monetized by Youtube what so ever. With Youtube monetized payouts you need millions of views to make money, with software commissions ranging from 20%- 40% I don't need Youtube revenue. I've broken my Youtube business plan down into bite sized pieces so that I know I can achieve my Goals. CHEERS!

#reddit#chatgpt,#claude.ai

reddit

0

0.5

ImpossibleBell4759•This week

ChatGPT, Claude.ai and Perplexity for my Youtube Business

I use ChatGPT, Claude. ai and Perplexity for my Youtube Software Review Businesses. I run OVER 20 Youtube Faceless Software Review channels, and those AI tools basically help me with ideas, titles and descriptions. I like how simple is it to use those AI tools and crank out ideas, titles and descriptions in less than 20 minutes. ChatGPT, Claude. ai and Perplexity save me so much time. Managing all those Youtube channels is an all day event. I also save time by not editing and not scripting my videos. I do software reviews and I crank out 3 videos per hour. I can use software to automate some of the videos, but they don't get the same effect, so I do every video with original content. I'm thinking about using Elevenlabs. com so I can have access to hundreds of voices that I can use for my videos. I like their "Speech to Speech" technology. The only problem with Elevenlabs is that I have to do some editing to make it work... and I hate editing. I rather just record my video and upload it to Youtube. I might have to skip on Elevenlabs and the editing, because I need to crank out at least 20 videos per day. It seems like a lot but I focus on 12 hours a day and 3 videos per hour. 12 hours times 3 videos= 36 videos per day. But I only need 20 videos in the 12 hours, so I know I can meet my quota for the day. I'm looking at 20 videos per day times roughly 30 days is 600 videos per month. My goal is to finish the year with at least $100,000 in "CASH" after taxes, paying rent, buying food and having all my bills paid. So, I need to make $273.97 per day times 365 days= $100,000. The most I've made was off 1 video with only 600 views and I made over $3,300. I wasn't even monetized by Youtube. I made all that money from software commissions alone. I don't care about being monetized by Youtube what so ever. With Youtube monetized payouts you need millions of views to make money, with software commissions ranging from 20%- 40% I don't need Youtube revenue. I've broken my Youtube business plan down into bite sized pieces so that I know I can achieve my Goals. CHEERS!

#reddit#chatgpt,#claude.ai

reddit

0

1

jottrled•This week

How I went from $27 to $3K as a solopreneur still in a 9-5

My journey started back in November 2023. I was scrolling through Twitter and YouTube and saw a word that I had never come across before. Solopreneur. The word caught my eye. Mainly because I was pretty sure I knew what it meant even though it's not a word you'll find in the dictionary. I liked what it was describing. A solo entrepreneur. A one man business. It completely resonated with me. As a software engineer by trade I'm used to working alone, especially since the pandemic hit and we were forced to work remotely. See, I always wanted to ditch the 9-5 thing but thought that was too big and too scary for a single person to do. Surely you would need a lot of money to get started, right? Surely you would need investors? The whole concept seemed impossible to me. That was until I found all the success stories. I became obsessed with the concept of solopreneurship. As I went further down the rabbit hole I found people like Justin Welsh, Kieran Drew and Marc Louvion to name a few. All of whom have one person businesses making huge money every year. So I thought, if they can do it, why can't I? People like this have cleared the pathway for those looking to escape the 9-5 grind. I decided 2024 would be the year I try this out. My main goal for the year? Build a one man business, earn my first $ online and learn a sh\*t ton along the way. My main goal in general? Build my business to $100K per year, quit my 9-5 and live with freedom. From December 2023 to February 2024 I began brainstorming ideas. I was like a lost puppy looking for his ball. How on earth did people find good ideas? I began writing everything and anything that came to mind down in my notes app on my phone. By February I would have approximately 70 ideas. Each as weird and whacky as the other. I was skeptical though. If I went through all the trouble of building a product for one of these ideas how would I know if anyone would even be interested in using it? I got scared and took a break for a week. All these ideas seemed too big and the chance that they would take off into the atmosphere was slim (in my mind anyways). I was learning more and more about solopreneurship as the weeks went on so I decided to build a product centered around everything I was learning about. The idea was simple. Enter a business idea and use AI to give the user details about how to market it, who their target customers were, what to write on their landing page, etc. All for a measly $27 per use. I quickly built it and launched on March 3rd 2024. I posted about it on Indie Hackers, Reddit and Hacker News. I was so excited about the prospect of earning my first internet $! Surely everyone wanted to use my product! Nope...all I got was crickets. I was quickly brought back down to earth. That was until 5 days later. I looked at my phone and had a new Stripe notification! Cha-ching! My first internet $. What a feeling! That was goal number 1 complete. It would be another 6 days before I would get my second sale...and then another 15 days to get my third. It was an emotional rollercoaster. I went from feeling like quitting the 9-5 was actually possible to thinking that maybe the ups and downs aren't worth it. On one hand I had made my first internet dollar so I should my ecstatic, and don't get me wrong, I was but I wanted more. More validation that I could do this long term. By May I was starting to give up on the product. I had learned so much in the past few months about marketing, SEO, building an audience, etc. and I wanted to build something that I thought could have more success so I focused on one critical thing that I had learned about. What was it? Building a product that had SEO potential. A product that I knew hundreds of people were looking for. See this was my thinking - If I could find a keyword that people were searching for on Google hundreds/thousands of times every month and it was easy to rank high on search engines then I would go all in (in SEO land this equates to a Keyword that has a Keyword Difficulty of = 500). I began researching and found that the keyword "micro saas ideas" was being searched for around 600 times each month. Micro Saas was something that really interested me. It was perfect for solopreneurs. Small software products that 1 person could build. What's not to like if you're in the game of software and solopreneurship? Researching keywords like this became like a game for me. I was hooked. I was doing it every day, finding gems that were being searched for hundreds and thousands of times every month that still had potential. That's when I came up with my next product idea. I decided to create a database of Micro Saas Ideas all with this sort of SEO potential. See if you can build a product that you know people are looking for then that's all the validation you need. So I put this theory to the test. I created a database of Micro Saas Ideas with SEO Potential and launched it in June 2024. This time it was different. I made $700 in the first week of launching. A large contrast to my previous failed attempt at becoming the worlds greatest solopreneur. Since launch I have grown the product to $3K and I couldn't be happier. I know what you're saying, $3K isn't a lot. But it's validation. It's validation that I can earn $ online. Validation that I can grow a business and it gives me hope that one day I'll be able to quit that 9-5 grind. My plan is to keep growing the business. I expect there to be a few challenges up ahead but I'll tackle them as I go and learn from the failures and successes. I have a newsletter where I share Micro Saas Ideas with SEO potential every week which I'll leave below in the first comment. Feel free to come along for the ride. If not I hope this post brings you some value If you're thinking about starting as a solopreneur, stop thinking and start doing, you won't regret it.

#reddit#went#solopreneur

reddit

0

0.846

Gluteous_Maximus•This week

I’m building a “DesignPickle” for all things Funnels. Would love your feedback...

Hey Entrepreneurs, Early next year I’m rolling out a productized service business along the lines of Design Pickle, but instead of design assets, we create on-demand marketing assets: Things like landing pages, lead magnets, email campaigns, etc. This is NOT an agency with client engagements, etc.  It is an on-demand, menu-item style fulfillment platform where we do a few predefined things really, really well, and as much as possible try to reduce the complexity (and required customer inputs) so that creating your next killer Funnel is as easy as ordering dinner on Skip the Dishes. Below I’ve laid out our current thinking (we’re still distilling this into a deck), just so you have the full context.  And at the end, I pose 5 feedback questions. So if this “deck” seems interesting to you, then I’d love to get your feedback at the end 🙂 Thanks! And here goes... \--- The current elevator pitch:  We will research your business, your market and your competitors to develop a killer Lead Magnet, Landing Page, Ad Creatives and a 30-Day Email Drip campaign designed to turn your traffic into a rabid, lifelong buyer tribe (that you can email for years... like having your own, on-demand cash printer).  The overall thesis:  While AI is getting continually better at creating things like one-off graphics, article content, and so on - we do not think it can deeply understand market psychology, what keeps your customers up at night, or the underlying emotions that drive purchase decisions at the individual level, for your specific offer(s). Moreover, it’s also this psychological aspect of marketing where most businesses simply do not have the talent, resources or frankly the experience to create high-performing funnels themselves, regardless of how much "automation" they might have at their fingertips. And that’s because this is where you need to know who your customer really is, and what they’re actually buying (hint: not your features). Few marketers focus on these fundamentals, let alone understand the selling process. This is also why tools like ClickFunnels, HighLevel, LeadPages, etc. while very helpful, can only help with the logistics of selling. It’s still on each business to figure out how to actually tell their story, capture demand, and sell effectively. This is why a productized service that nails market research, competitor analysis & world-class copywriting that can actually turn cold traffic into lifelong customers is going to be a no-brainer for a business that’s currently struggling to actually get a steady flow of online sales. This is not something we see AI replacing effectively, any time soon. Current gaps & unknowns:  At a top level, I’m not overly worried about validation or viability; there are several existing competitors, and obviously the automation platforms have substantial customer bases (ClickFunnels etc). There will be a certain cohort that will want experts to do the actual thinking for them, storytelling, etc. Even if it’s a relatively small cohort, given the CLTV of a service like this, it still makes for a decent sized business. But where I’m less confident is in who our ideal customer actually is... Yes, basically every direct-response internet business needs an effective funnel that can sell. Whether you’re an Enterprise SaaS platform or a solopreneur launching your first $39 ebook, you will benefit from a killer funnel. As a “DesignPickle” type service though, here’s the challenges I see with each core customer category... B2B SaaS: While sales decisions are still emotional, it’s more about account-based considerations; people usually aren’t spending their own money, so it’s more about not looking stupid vs. gaining some benefit. Harder to systemize. Very high stakes. Consumer / SMB SaaS: While I think in general these are ideal customers, there will be resistance to leaning in hard on personality (and personal brand); founders usually want to sell at some point, so if they become the face of the platform, then boosting performance with a high-personality funnel might ironically make it a harder business to sell. SaaS founders are also generally very technical and stereotypically avoid marketing like the plague. Ecommerce: Most DTC brands think of funnels as an extension of their FB ad campaigns; few see their customers as a long-term audience that can become a significant asset. However, certain lifestyle / luxury brands might differ. Online Courses / Coaches: Of all the customer profiles, this group probably has the most appreciation for the effectiveness of marketing psychology, copywriting, etc. and would get the value prop quickly. The problem is that most won’t have the budget or traction to outsource asset creation. This is the “poorest” segment of the market. Service Businesses: Agencies, consultancies, and so on would greatly benefit from having a strong personal brand + storytelling premise (funnel). However, they’re also the worst offenders when it comes to never practicing what they preach / do for others. Client work soaks up all their resources. Local & Brick/Mortar: Generally speaking most local businesses are going to have smaller audiences (email lists under 2K subs), where funnel ops might have limited value long-term due to a lack of scale. And for larger B&M brands with franchises across various locations, you get into stakeholder friction; messaging usually gets watered down to basic corporate-speak as a result. Now, to be clear, I still see a ton of opportunity in each of those main customer categories as well, but I like to be clear-eyed about the overall resistance each niche will have - mainly because this helps to refine messaging to an ideal customer profile within them. In this case though, so far, nothing’s really jumping out at me as a clear “winner” at a category level. So far, what I’m thinking is our ICP might be situational / conditional. For example: A business has a funnel / is invested in the process, but it’s not working yet A business sees their competitor killing it with a funnel, and they’re ultra motivated to do it even better A business has one funnel that’s working awesome, and everything else they try sucks (so they can’t scale / expand) Etc. Basically, our most ideal customer might be ANY type of business who gets it, who’s tried to do this themselves, and now needs the pros to come in and fix things. \--- This is where your feedback would be incredibly valuable... First, if you’ve made it all the way down to this point - thanks for enduring my rambling mess above! But I did think the context might be helpful. Based on our overall biz plan & go-to-market considerations discussed above, if you run a business (or work with one) that might benefit from something like this, I’d love to ask a few questions... What is the nature of your business? (What do you sell)? What do you find hardest about selling to your online audience? Have you built a funnel in the past / are you running one currently? If not, what’s stopping you from building a high-performing funnel? If you had a “magic marketing lamp” where a genie could create ONE amazing marketing asset for you (eg. a killer landing page, video ad, launch strategy, etc), but you could only use it ONCE, what would you have the genie do for you? Please reply below as a comment, or DM me if you’d prefer to keep answers anonymous.  Thanks so much And again, apologies for the novel... Cheers

#reddit#building#“designpickle”

reddit

0

1

AI_Scout_Official•This week

As a soloproneur, here is how I'm scaling with AI and GPT-based tools

Being a solopreneur has its fair share of challenges. Currently I've got businesses in ecommerce, agency work, and affiliate marketing, and one undeniable truth remains: to truly scale by yourself, you need more than just sheer will. That's where I feel technology, especially AI, steps in. As such, I wanted some AI tools that have genuinely made a difference in my own work as a solo business operator. No fluff, just tried-and-true tools and platforms that have worked for me. The ability for me to scale alone with AI tools that take advantage of GPT in one way, or another has been significant and really changed my game over the past year. They bring in an element of adaptability and intelligence and work right alongside “traditional automation”. Whether you're new to this or looking to optimize your current setup, I hope this post helps. FYI I used multiple prompts with GPT-4 to draft this using my personal notes. Plus AI (add-on for google slides/docs) I handle a lot of sales calls and demos for my AI automation agency. As I’m providing a custom service rather than a product, every client has different pain points and as such I need to make a new slide deck each time. And making slides used to be a huge PITA and pretty much the bane of my existence until slide deck generators using GPT came out. My favorite so far has been PlusAI, which works as a plugin for Google Slides. You pretty much give it a rough idea, or some key points and it creates some slides right within Google Slides. For me, I’ve been pasting the website copy or any information on my client, then telling PlusAI the service I want to propose. After the slides are made, you have a lot of leeway to edit the slides again with AI, compared to other slide generators out there. With 'Remix', I can switch up layouts if something feels off, and 'Rewrite' is there to gently nudge the AI in a different direction if I ever need it to. It's definitely given me a bit of breathing space in a schedule that often feels suffocating. echo.win (web-based app) As a solopreneur, I'm constantly juggling roles. Managing incoming calls can be particularly challenging. Echo.win, a modern call management platform, has become a game-changer for my business. It's like having a 24/7 personal assistant. Its advanced AI understands and responds to queries in a remarkably human way, freeing up my time. A standout feature is the Scenario Builder, allowing me to create personalized conversation flows. Live transcripts and in-depth analytics help me make data-driven decisions. The platform is scalable, handling multiple simultaneous calls and improving customer satisfaction. Automatic contact updates ensure I never miss an important call. Echo.win's pricing is reasonable, offering a personalized business number, AI agents, unlimited scenarios, live transcripts, and 100 answered call minutes per month. Extra minutes are available at a nominal cost. Echo.win has revolutionized my call management. It's a comprehensive, no-code platform that ensures my customers are always heard and never missed MindStudio by YouAi (web app/GUI) I work with numerous clients in my AI agency, and a recurring task is creating chatbots and demo apps tailored to their specific needs and connected to their knowledge base/data sources. Typically, I would make production builds from scratch with libraries such as LangChain/LlamaIndex, however it’s quite cumbersome to do this for free demos. As each client has unique requirements, it means I'm often creating something from scratch. For this, I’ve been using MindStudio (by YouAi) to quickly come up with the first iteration of my app. It supports multiple AI models (GPT, Claude, Llama), let’s you upload custom data sources via multiple formats (PDF, CSV, Excel, TXT, Docx, and HTML), allows for custom flows and rules, and lets you to quickly publish your apps. If you are in their developer program, YouAi has built-in payment infrastructure to charge your users for using your app. Unlike many of the other AI builders I’ve tried, MindStudio basically lets me dictate every step of the AI interaction at a high level, while at the same time simplifying the behind-the-scenes work. Just like how you'd sketch an outline or jot down main points, you start with a scaffold or decide to "remix" an existing AI, and it will open up the IDE. I often find myself importing client data or specific project details, and then laying out the kind of app or chatbot I'm looking to prototype. And once you've got your prototype you can customize the app as much as you want. LLamaIndex (Python framework) As mentioned before, in my AI agency, I frequently create chatbots and apps for clients, tailored to their specific needs and connected to their data sources. LlamaIndex, a data framework for LLM applications, has been a game-changer in this process. It allows me to ingest, structure, and access private or domain-specific data. The major difference over LangChain is I feel like LlamaIndex does high level abstraction much better.. Where LangChain unnecessarily abstracts the simplest logic, LlamaIndex actually has clear benefits when it comes to integrating your data with LLMs- it comes with data connectors that ingest data from various sources and formats, data indexes that structure data for easy consumption by LLMs, and engines that provide natural language access to data. It also includes data agents, LLM-powered knowledge workers augmented by tools, and application integrations that tie LlamaIndex back into the rest of the ecosystem. LlamaIndex is user-friendly, allowing beginners to use it with just five lines of code, while advanced users can customize and extend any module to fit their needs. To be completely honest, to me it’s more than a tool- at its heart it’s a framework that ensures seamless integration of LLMs with data sources while allowing for complete flexibility compared to no-code tools. GoCharlie (web app) GoCharlie, the first AI Agent product for content creation, has been a game-changer for my business. Powered by a proprietary LLM called Charlie, it's capable of handling multi-input/multi-output tasks. GoCharlie's capabilities are vast, including content repurposing, image generation in 4K and 8K for various aspect ratios, SEO-optimized blog creation, fact-checking, web research, and stock photo and GIF pull-ins. It also offers audio transcriptions for uploaded audio/video files and YouTube URLs, web scraping capabilities, and translation. One standout feature is its multiple input capability, where I can attach a file (like a brand brief from a client) and instruct it to create a social media campaign using brand guidelines. It considers the file, prompt, and website, and produces multiple outputs for each channel, each of which can be edited separately. Its multi-output feature allows me to write a prompt and receive a response, which can then be edited further using AI. Overall, very satisfied with GoCharlie and in my opinion it really presents itself as an effective alternative to GPT based tools. ProfilePro (chrome extension) As someone overseeing multiple Google Business Profiles (GBPs) for my various businesses, I’ve been using ProfilePro by Merchynt. This tool stood out with its ability to auto-generate SEO-optimized content like review responses and business updates based on minimal business input. It works as a Chrome extension, and offers suggestions for responses automatically on your GBP, with multiple options for the tone it will write in. As a plus, it can generate AI images for Google posts, and offer suggestions for services and service/product descriptions. While it streamlines many GBP tasks, it still allows room for personal adjustments and refinements, offering a balance between automation and individual touch. And if you are like me and don't have dedicated SEO experience, it can handle ongoing optimization tasks to help boost visibility and drive more customers to profiles through Google Maps and Search

#reddit#soloproneur,#here

reddit

0

1

TheL0nelyPoet•This week

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

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

#reddit#business#idea

reddit

0

1

Alarmed-Argument-605•This week

Made 60k mrr for a business by just lead nurturing. Need suggestions and validation.

Apart from the story I need a suggestion and validation here. It's a bit long, skip to tl;dr if you couldn't handle length. A few days ago, I saw a person on Reddit sharing his struggles that, Even after generating a lot of leads from ads of Meta and Google (even with lowest cpc cpa cpl), he was not able to convert them into sales. Out of curiosity I dm'ed him with all fancy services that I offer and expressed that as a agency I would work with him for monthly recurring fee. He suggested for one time consulting fee, I agreed. It was literally a eye opener for me. This guy is in coaching business offering courses for people. His niche was too vague. Courses were on mindset coaching, confidence and public speaking coaching, right attitude coaching, manifestation coaching and all crap shits related to this. At first I thought he was not getting sales because who will pay for all this craps. I openly discussed with him that he has to change what he offers because, if I saw this ad I wouldn't buy this for sure. He then showed me how much money people offering similar service are making . I was literally taken back. He was part of a influencer group (the main guy who encourages these guys to start coaching business, looks like some mlm shit) where people post their succes stories. Literally lot of guys were making above 150k and 200k per month. Even with very basic landing page and average offer They are still winning. Here's where it gets interesting. I tried to clone everything that the top people in this industry are doing in marketing from end to end.( like the same landing page, bonus offers around 50k, exclusive community, free 1 on 1 calls for twice a month).Nothing worked for a month and later surprisingly even the sales started dropping a bit more. I got really confused here. So to do a discovery I went and purchased the competitor course and Man I was literally taken back. Like he has automated everything from end to end. You click the ad, see vsl, you have to fill a form and join a free Skool community where he gives away free stuffs and post success stories of people who took the course. Now every part of this journey you will get a follow up mail and follow up sms. Like after filling the form. after that now if you join and don't purchase the course you will be pampered with email and sms filled with success stories. For sure anybody will be tempted to buy the course. Here is the key take away. He was able to make more sales because he was very successful in nurturing the leads with follow ups after follow ups. Even after you purchased his course he is making passive income from 1 on calls and bonus live webinars. So follow ups will be for 1 on 1 calls and webinars after the course is over. Core point is our guy even after spending 2 to 3k per month on ads was not able to bring huge sales like competitors because he failed the nuture them. Even after making the same offers and the same patterns of marketing as competitors, the sales declined because people thought this is some spam that everyone is doing because the template of the ads was very professional and similar. suprising one is people fall for basic templates thinking it's a underrated one. so what we did here is we integrated a few softwares into one and set up all same webinars, automated email and sms follow ups, ad managers for stats, launched him a free LMS platform where without any additional fees so he can uploaded unlimited courses, skool like community and add product's like Shopify ( he was selling few merchandise with his brand name on) where he can add unlimited products with connection to all payment gateway, integrated with crm with unlimited contacts, workflow and lead nurturing with calender syncing for 1 on 1 calls. But these are a bit old school, what we did was even better. integrated a conversational ai with all of his sales platforms and gave a nocode automation builder with ai for the workflow. we also set him up with a ai voice agent that's automatically calls and markets for his course and also replies for queries when called. we also set up him a dedicated afflitate manager portal with automated commissions. Though he didn't cross 100k Mark, He did a great number after this. He was struggling with 6k sales, now he has reached somewhere mid of 45k to 50k mrr. Max he hit was 61.8k. I see this a big difference.So one small thing, nurturing the lead can bring you immense sales. To set up all of this it costs around 1.2k monthly for me with all the bills. ( I know there are few free for Individual user platforms out there, but It gets very costly when you switch to their premium plans. with heavy volumes you would require more than premium they offer.) I offered him like 3k per month to work as a agency for him who takes care of all these stuffs. He declined and offered for one time set up fee stating that he will pay 1.2k directly. The one time fee was also a bit low, though I agreed since this was a learning for me. what happened next after that is, he referred me to a few other people in the same niche. But the problem is they are not interested in spending 1 to 2 k in bills for software. They requested that if, will I be able to provide the saas alone for less than 500 dollars with one time set up fee. I haven't responded yet since I have to take an enterprise plan for all the software used and pay full advance price for billings. Then to break even that I have to make minimum 50 or odd users for that. let's grantly say 100 users with all other future costs. So here's what I'm planning to do. I'm planning to offer this as saas for let's say 239 dollars per month. with may or may not one time set up fee. ( I checked the entire internet, there is no single person offering at this price point for unlimited. Also one can easily start their marketing agency with this.) The suggestion and validation that I need here is 1.are you going through the same struggles or faced these struggles? would you be interested to buy at 239 dollars per month? let's say you're from a different niche, Did the features I told were okay for you or you need something specific for your industry that you will be interested in buying? please answer in comments and if you will purchase for this price let me know in comments/dms. I will take that into account and if the response rate is above 100 queries, then will integrate this and sell for that price. (ps: If you see this post on similar subs, please bear cause I'm trying to get suggestions from different POV) tl;dr - lead nurturing can massively boost sales *I made a software integration for a client for a 1.2k per month billing and here I want to know if more than 100 people are interested so that I will make this into my own saas and sell it for like a cheap price of 239 dollars per month TIA.

#reddit#made#business

reddit

0

1

No-Definition-2886•This week

I single-handedly built the world’s best AI investing platform. Here’s NexusTrade’s 2024 year in review

I copy-pasted the content of this article to save you a click! I’ve been developing an AI investing platform for 4 years, and I’m blown away by all of the new features I’ve gotten done! Here’s my project’s 2024 year in review —- When someone asks me what is the best way to learn how to trade and invest, I have an unbiased answer – NexusTrade.io. I started NexusTrade to empower everybody, including beginners and non-technical investors, to learn how to make smarter investing decisions. NexusTrade is the best way for a new investor to learn algorithmic trading and financial research, and I’m not the only person to think so. Just this year alone, user growth has skyrocketed from 1,703 users to 14,319 users. This is driven by new features, better research tools, and the launch of algorithmic trading. Here’s NexusTrade’s 2024 year in review, a semi-complete list of the features I’ve launched. Summarizing this year in review TL;DR: I implemented a variety of new features to enhance NexusTrade’s algorithmic trading and financial research capabilities. This includes: Cryptocurrency support Enhanced financial research, like the AI-Powered Stock Screener Unique watchlists and daily market summaries Live-trading with Alpaca. Next year, I plan to implement features to make NexusTrade more tailored for each user’s experience, and launch several unique features including copy trading and fully automated algorithmic trading. Feature-by-feature: What have I done so far in 2024? Algorithmic Cryptocurrency Trading Picture: Algorithmic Cryptocurrency Trading I kicked off the year by adding cryptocurrency support to NexusTrade. Users can now research, design, and implement automated strategies for popular cryptocurrencies, such as Bitcoin, Dogecoin, and Ethereum. AI-Powered Stock Screener and research capabilities Picture: AI-Powered Stock Screener In tandem with cryptocurrency support, I made a huge update to Aurora, the AI Assistant in NexusTrade, by implementing a natural language stock screener. This screener makes it easy to find fundamentally strong stocks. Throughout the year, I’ve made several enhancements to it. Over time, I’ve made the screener faster, more accurate, and expanded its capabilities. Using fundamental indicators within trading strategies Picture: Using fundamental indicators Doing financial research for companies isn’t enough; we also need a way to integrate this type of research into trading strategies. Thus, I’ve expanded the NexusTrade indicators, and made it possible to create strategies using metrics like revenue, net income, free cash flow, and P/E ratio. Stock watchlists with tailored, automated daily emails Picture: Stock watchlists In addition, I didn’t want the research you may have done for a stock (or list of stocks) to be forgotten. Thus, I created the most useful watchlist page of any investing platform. This watchlist makes it easy to keep track of your favorite stocks, track them over time, and even receive curated, daily emails about them. Enhanced user profile page, Google sign-ins, and two-factor authentication Picture: Enhanced user profile Keeping in theme with adding new pages to NexusTrade, many pages, such as the profile page, got a huge revamp. The new profile page is cleaner, easier to use, and allows you to secure your account more effectively, for example, by using two-factor authentication. GPT-Reports: an AI-generated analysis of every stock in the market Picture: GPT-Reports I created GPT-Stock Reports, an AI-Generated analysis of every stock in the market. This report was generated by taking each company’s earnings data and asking GPT to analyze the stock and give it a rating. Manual and semi-automated algorithmic trading with Alpaca Picture: Manual and semi-automated trading Finally, I’ve fully launched the Alpaca integration, and enabled users to execute real trades directly in the NexusTrade app! This integration has transformed NexusTrade from a financial research app into a real, algorithmic trading platform for retail investors. Concluding Thoughts When I say that NexusTrade is the best platform for traders and investors to make more money in the stock market, you may naively think that I’m biased. I created the app, and the rose-tinted glasses is bound to make every red flag look like a regular flag, right? Wrong. NexusTrade is objectively a completely new way for investors to approach financial markets. The fact that the app is so expansive is nothing short of miraculous.

#reddit#single-handedly#built

github

0.62

1

rasbt•Mar 28, 2025

LLMs-from-scratch

Build a Large Language Model (From Scratch) This repository contains the code for developing, pretraining, and finetuning a GPT-like LLM and is the official code repository for the book Build a Large Language Model (From Scratch). In Build a Large Language Model (From Scratch), you'll learn and understand how large language models (LLMs) work from the inside out by coding them from the ground up, step by step. In this book, I'll guide you through creating your own LLM, explaining each stage with clear text, diagrams, and examples. The method described in this book for training and developing your own small-but-functional model for educational purposes mirrors the approach used in creating large-scale foundational models such as those behind ChatGPT. In addition, this book includes code for loading the weights of larger pretrained models for finetuning. Link to the official source code repository Link to the book at Manning (the publisher's website) Link to the book page on Amazon.com ISBN 9781633437166 To download a copy of this repository, click on the Download ZIP button or execute the following command in your terminal: (If you downloaded the code bundle from the Manning website, please consider visiting the official code repository on GitHub at https://github.com/rasbt/LLMs-from-scratch for the latest updates.) Table of Contents Please note that this README.md file is a Markdown (.md) file. If you have downloaded this code bundle from the Manning website and are viewing it on your local computer, I recommend using a Markdown editor or previewer for proper viewing. If you haven't installed a Markdown editor yet, MarkText is a good free option. You can alternatively view this and other files on GitHub at https://github.com/rasbt/LLMs-from-scratch in your browser, which renders Markdown automatically. Tip: If you're seeking guidance on installing Python and Python packages and setting up your code environment, I suggest reading the README.md file located in the setup directory. | Chapter Title | Main Code (for Quick Access) | All Code + Supplementary | |------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------|-------------------------------| | Setup recommendations | - | - | | Ch 1: Understanding Large Language Models | No code | - | | Ch 2: Working with Text Data | - ch02.ipynb- dataloader.ipynb (summary)- exercise-solutions.ipynb | ./ch02 | | Ch 3: Coding Attention Mechanisms | - ch03.ipynb- multihead-attention.ipynb (summary) - exercise-solutions.ipynb| ./ch03 | | Ch 4: Implementing a GPT Model from Scratch | - ch04.ipynb- gpt.py (summary)- exercise-solutions.ipynb | ./ch04 | | Ch 5: Pretraining on Unlabeled Data | - ch05.ipynb- gpttrain.py (summary) - gptgenerate.py (summary) - exercise-solutions.ipynb | ./ch05 | | Ch 6: Finetuning for Text Classification | - ch06.ipynb - gptclassfinetune.py - exercise-solutions.ipynb | ./ch06 | | Ch 7: Finetuning to Follow Instructions | - ch07.ipynb- gptinstructionfinetuning.py (summary)- ollamaevaluate.py (summary)- exercise-solutions.ipynb | ./ch07 | | Appendix A: Introduction to PyTorch | - code-part1.ipynb- code-part2.ipynb- DDP-script.py- exercise-solutions.ipynb | ./appendix-A | | Appendix B: References and Further Reading | No code | - | | Appendix C: Exercise Solutions | No code | - | | Appendix D: Adding Bells and Whistles to the Training Loop | - appendix-D.ipynb | ./appendix-D | | Appendix E: Parameter-efficient Finetuning with LoRA | - appendix-E.ipynb | ./appendix-E | The mental model below summarizes the contents covered in this book. Hardware Requirements The code in the main chapters of this book is designed to run on conventional laptops within a reasonable timeframe and does not require specialized hardware. This approach ensures that a wide audience can engage with the material. Additionally, the code automatically utilizes GPUs if they are available. (Please see the setup doc for additional recommendations.) Bonus Material Several folders contain optional materials as a bonus for interested readers: Setup Python Setup Tips Installing Python Packages and Libraries Used In This Book Docker Environment Setup Guide Chapter 2: Working with text data Byte Pair Encoding (BPE) Tokenizer From Scratch Comparing Various Byte Pair Encoding (BPE) Implementations Understanding the Difference Between Embedding Layers and Linear Layers Dataloader Intuition with Simple Numbers Chapter 3: Coding attention mechanisms Comparing Efficient Multi-Head Attention Implementations Understanding PyTorch Buffers Chapter 4: Implementing a GPT model from scratch FLOPS Analysis Chapter 5: Pretraining on unlabeled data: Alternative Weight Loading Methods Pretraining GPT on the Project Gutenberg Dataset Adding Bells and Whistles to the Training Loop Optimizing Hyperparameters for Pretraining Building a User Interface to Interact With the Pretrained LLM Converting GPT to Llama Llama 3.2 From Scratch Memory-efficient Model Weight Loading Extending the Tiktoken BPE Tokenizer with New Tokens PyTorch Performance Tips for Faster LLM Training Chapter 6: Finetuning for classification Additional experiments finetuning different layers and using larger models Finetuning different models on 50k IMDB movie review dataset Building a User Interface to Interact With the GPT-based Spam Classifier Chapter 7: Finetuning to follow instructions Dataset Utilities for Finding Near Duplicates and Creating Passive Voice Entries Evaluating Instruction Responses Using the OpenAI API and Ollama Generating a Dataset for Instruction Finetuning Improving a Dataset for Instruction Finetuning Generating a Preference Dataset with Llama 3.1 70B and Ollama Direct Preference Optimization (DPO) for LLM Alignment Building a User Interface to Interact With the Instruction Finetuned GPT Model Questions, Feedback, and Contributing to This Repository I welcome all sorts of feedback, best shared via the Manning Forum or GitHub Discussions. Likewise, if you have any questions or just want to bounce ideas off others, please don't hesitate to post these in the forum as well. Please note that since this repository contains the code corresponding to a print book, I currently cannot accept contributions that would extend the contents of the main chapter code, as it would introduce deviations from the physical book. Keeping it consistent helps ensure a smooth experience for everyone. Citation If you find this book or code useful for your research, please consider citing it. Chicago-style citation: Raschka, Sebastian. Build A Large Language Model (From Scratch). Manning, 2024. ISBN: 978-1633437166. BibTeX entry:

#github#llms-from-scratch

github

0.447

0.1014145151561518

superiorlu•Mar 28, 2025

AITreasureBox

AI TreasureBox English | 中文 Collect practical AI repos, tools, websites, papers and tutorials on AI. Translated from ChatGPT, picture from Midjourney. Catalog Repos Tools Websites Report&Paper Tutorials Repos updated repos and stars every 2 hours and re-ranking automatically. | No. | Repos | Description | | ----:|:-----------------------------------------|:------------------------------------------------------------------------------------------------------| | 1|🔥codecrafters-io/build-your-own-x !2025-03-28364681428|Master programming by recreating your favorite technologies from scratch.| | 2|sindresorhus/awesome !2025-03-28353614145|😎 Awesome lists about all kinds of interesting topics| | 3|public-apis/public-apis !2025-03-28334299125|A collective list of free APIs| | 4|kamranahmedse/developer-roadmap !2025-03-2831269540|Interactive roadmaps, guides and other educational content to help developers grow in their careers.| | 5|vinta/awesome-python !2025-03-28238581114|A curated list of awesome Python frameworks, libraries, software and resources| | 6|practical-tutorials/project-based-learning !2025-03-28222661124|Curated list of project-based tutorials| | 7|tensorflow/tensorflow !2025-03-281888714|An Open Source Machine Learning Framework for Everyone| | 8|Significant-Gravitas/AutoGPT !2025-03-2817391338|An experimental open-source attempt to make GPT-4 fully autonomous.| | 9|jackfrued/Python-100-Days !2025-03-2816305141|Python - 100天从新手到大师| | 10|AUTOMATIC1111/stable-diffusion-webui !2025-03-2815011553|Stable Diffusion web UI| | 11|huggingface/transformers !2025-03-2814207850|🤗 Transformers: State-of-the-art Machine Learning for Pytorch, TensorFlow, and JAX.| | 12|ollama/ollama !2025-03-28135166151|Get up and running with Llama 2, Mistral, Gemma, and other large language models.| | 13|f/awesome-chatgpt-prompts !2025-03-2812212738 |This repo includes ChatGPT prompt curation to use ChatGPT better.| | 14|justjavac/free-programming-books-zhCN !2025-03-2811316119|📚 免费的计算机编程类中文书籍，欢迎投稿| | 15|krahets/hello-algo !2025-03-2811107930|《Hello 算法》：动画图解、一键运行的数据结构与算法教程。支持 Python, Java, C++, C, C#, JS, Go, Swift, Rust, Ruby, Kotlin, TS, Dart 代码。简体版和繁体版同步更新，English version ongoing| | 16|yt-dlp/yt-dlp !2025-03-28105801114|A feature-rich command-line audio/video downloader| | 17|langchain-ai/langchain !2025-03-2810449479|⚡ Building applications with LLMs through composability ⚡| | 18|goldbergyoni/nodebestpractices !2025-03-281021629|✅ The Node.js best practices list (July 2024)| | 19|puppeteer/puppeteer !2025-03-289018212|JavaScript API for Chrome and Firefox| | 20|pytorch/pytorch !2025-03-288833938|Tensors and Dynamic neural networks in Python with strong GPU acceleration| | 21|neovim/neovim !2025-03-288781482|Vim-fork focused on extensibility and usability| | 22|🔥🔥langgenius/dify !2025-03-2887342639 |One API for plugins and datasets, one interface for prompt engineering and visual operation, all for creating powerful AI applications.| | 23|mtdvio/every-programmer-should-know !2025-03-28867069|A collection of (mostly) technical things every software developer should know about| | 24|open-webui/open-webui !2025-03-2886025159|User-friendly WebUI for LLMs (Formerly Ollama WebUI)| | 25|ChatGPTNextWeb/NextChat !2025-03-288231521|✨ Light and Fast AI Assistant. Support: Web | | 26|supabase/supabase !2025-03-287990956|The open source Firebase alternative.| | 27|openai/whisper !2025-03-287905542|Robust Speech Recognition via Large-Scale Weak Supervision| | 28|home-assistant/core !2025-03-287773219|🏡 Open source home automation that puts local control and privacy first.| | 29|tensorflow/models !2025-03-28774694|Models and examples built with TensorFlow| | 30| ggerganov/llama.cpp !2025-03-287731836 | Port of Facebook's LLaMA model in C/C++ | | 31|3b1b/manim !2025-03-287641918|Animation engine for explanatory math videos| | 32|microsoft/generative-ai-for-beginners !2025-03-287623860|12 Lessons, Get Started Building with Generative AI 🔗 https://microsoft.github.io/generative-ai-for-beginners/| | 33|nomic-ai/gpt4all !2025-03-28729285 |gpt4all: an ecosystem of open-source chatbots trained on a massive collection of clean assistant data including code, stories and dialogue| | 34|comfyanonymous/ComfyUI !2025-03-2872635111|The most powerful and modular diffusion model GUI, api and backend with a graph/nodes interface.| | 35|bregman-arie/devops-exercises !2025-03-2872225209|Linux, Jenkins, AWS, SRE, Prometheus, Docker, Python, Ansible, Git, Kubernetes, Terraform, OpenStack, SQL, NoSQL, Azure, GCP, DNS, Elastic, Network, Virtualization. DevOps Interview Questions| | 36|elastic/elasticsearch !2025-03-28721419|Free and Open, Distributed, RESTful Search Engine| | 37|🔥n8n-io/n8n !2025-03-2872093495|Free and source-available fair-code licensed workflow automation tool. Easily automate tasks across different services.| | 38|fighting41love/funNLP !2025-03-287200422|The Most Powerful NLP-Weapon Arsenal| | 39|hoppscotch/hoppscotch !2025-03-287060134|Open source API development ecosystem - https://hoppscotch.io (open-source alternative to Postman, Insomnia)| | 40|abi/screenshot-to-code !2025-03-286932817|Drop in a screenshot and convert it to clean HTML/Tailwind/JS code| | 41|binary-husky/gptacademic !2025-03-28680374|Academic Optimization of GPT| | 42|d2l-ai/d2l-zh !2025-03-286774142|Targeting Chinese readers, functional and open for discussion. The Chinese and English versions are used for teaching in over 400 universities across more than 60 countries| | 43|josephmisiti/awesome-machine-learning !2025-03-286739215|A curated list of awesome Machine Learning frameworks, libraries and software.| | 44|grafana/grafana !2025-03-286725414|The open and composable observability and data visualization platform. Visualize metrics, logs, and traces from multiple sources like Prometheus, Loki, Elasticsearch, InfluxDB, Postgres and many more.| | 45|python/cpython !2025-03-286602218|The Python programming language| | 46|apache/superset !2025-03-286519020|Apache Superset is a Data Visualization and Data Exploration Platform| | 47|xtekky/gpt4free !2025-03-28639391 |decentralizing the Ai Industry, free gpt-4/3.5 scripts through several reverse engineered API's ( poe.com, phind.com, chat.openai.com etc...)| | 48|sherlock-project/sherlock !2025-03-286332536|Hunt down social media accounts by username across social networks| | 49|twitter/the-algorithm !2025-03-28630586 |Source code for Twitter's Recommendation Algorithm| | 50|keras-team/keras !2025-03-28627835|Deep Learning for humans| | 51|openai/openai-cookbook !2025-03-28625136 |Examples and guides for using the OpenAI API| | 52|immich-app/immich !2025-03-286238670|High performance self-hosted photo and video management solution.| | 53|AppFlowy-IO/AppFlowy !2025-03-286173528|Bring projects, wikis, and teams together with AI. AppFlowy is an AI collaborative workspace where you achieve more without losing control of your data. The best open source alternative to Notion.| | 54|scikit-learn/scikit-learn !2025-03-286158212|scikit-learn: machine learning in Python| | 55|binhnguyennus/awesome-scalability !2025-03-286117021|The Patterns of Scalable, Reliable, and Performant Large-Scale Systems| | 56|labmlai/annotateddeeplearningpaperimplementations !2025-03-285951726|🧑‍🏫 59 Implementations/tutorials of deep learning papers with side-by-side notes 📝; including transformers (original, xl, switch, feedback, vit, ...), optimizers (adam, adabelief, ...), gans(cyclegan, stylegan2, ...), 🎮 reinforcement learning (ppo, dqn), capsnet, distillation, ... 🧠| | 57|OpenInterpreter/open-interpreter !2025-03-285894710|A natural language interface for computers| | 58|lobehub/lobe-chat !2025-03-285832054|🤖 Lobe Chat - an open-source, extensible (Function Calling), high-performance chatbot framework. It supports one-click free deployment of your private ChatGPT/LLM web application.| | 59|meta-llama/llama !2025-03-28579536|Inference code for Llama models| | 60|nuxt/nuxt !2025-03-28566437|The Intuitive Vue Framework.| | 61|imartinez/privateGPT !2025-03-28555192|Interact with your documents using the power of GPT, 100% privately, no data leaks| | 62|Stirling-Tools/Stirling-PDF !2025-03-285500846|#1 Locally hosted web application that allows you to perform various operations on PDF files| | 63|PlexPt/awesome-chatgpt-prompts-zh !2025-03-285459720|ChatGPT Chinese Training Guide. Guidelines for various scenarios. Learn how to make it listen to you| | 64|dair-ai/Prompt-Engineering-Guide !2025-03-285451025 |🐙 Guides, papers, lecture, notebooks and resources for prompt engineering| | 65|ageitgey/facerecognition !2025-03-28544382|The world's simplest facial recognition api for Python and the command line| | 66|CorentinJ/Real-Time-Voice-Cloning !2025-03-285384814|Clone a voice in 5 seconds to generate arbitrary speech in real-time| | 67|geekan/MetaGPT !2025-03-285375376|The Multi-Agent Meta Programming Framework: Given one line Requirement, return PRD, Design, Tasks, Repo | | 68|gpt-engineer-org/gpt-engineer !2025-03-285367419|Specify what you want it to build, the AI asks for clarification, and then builds it.| | 69|lencx/ChatGPT !2025-03-2853653-3|🔮 ChatGPT Desktop Application (Mac, Windows and Linux)| | 70|deepfakes/faceswap !2025-03-28535672|Deepfakes Software For All| | 71|langflow-ai/langflow !2025-03-285319584|Langflow is a low-code app builder for RAG and multi-agent AI applications. It’s Python-based and agnostic to any model, API, or database.| | 72|commaai/openpilot !2025-03-28529759|openpilot is an operating system for robotics. Currently, it upgrades the driver assistance system on 275+ supported cars.| | 73|clash-verge-rev/clash-verge-rev !2025-03-2852848124|Continuation of Clash Verge - A Clash Meta GUI based on Tauri (Windows, MacOS, Linux)| | 74|All-Hands-AI/OpenHands !2025-03-285150675|🙌 OpenHands: Code Less, Make More| | 75|xai-org/grok-1 !2025-03-28502504|Grok open release| | 76|meilisearch/meilisearch !2025-03-284999122|A lightning-fast search API that fits effortlessly into your apps, websites, and workflow| | 77|🔥browser-use/browser-use !2025-03-2849910294|Make websites accessible for AI agents| | 78|jgthms/bulma !2025-03-28496783|Modern CSS framework based on Flexbox| | 79|facebookresearch/segment-anything !2025-03-284947116|The repository provides code for running inference with the SegmentAnything Model (SAM), links for downloading the trained model checkpoints, and example notebooks that show how to use the model.| |!green-up-arrow.svg 80|hacksider/Deep-Live-Cam !2025-03-2848612146|real time face swap and one-click video deepfake with only a single image (uncensored)| |!red-down-arrow 81|mlabonne/llm-course !2025-03-284860934|Course with a roadmap and notebooks to get into Large Language Models (LLMs).| | 82|PaddlePaddle/PaddleOCR !2025-03-284785530|Awesome multilingual OCR toolkits based on PaddlePaddle (practical ultra lightweight OCR system, support 80+ languages recognition, provide data annotation and synthesis tools, support training and deployment among server, mobile, embedded and IoT devices)| | 83|alist-org/alist !2025-03-284732618|🗂️A file list/WebDAV program that supports multiple storages, powered by Gin and Solidjs. / 一个支持多存储的文件列表/WebDAV程序，使用 Gin 和 Solidjs。| | 84|infiniflow/ragflow !2025-03-2847027129|RAGFlow is an open-source RAG (Retrieval-Augmented Generation) engine based on deep document understanding.| | 85|Avik-Jain/100-Days-Of-ML-Code !2025-03-284679312|100 Days of ML Coding| | 86|v2ray/v2ray-core !2025-03-28458706|A platform for building proxies to bypass network restrictions.| | 87|hiyouga/LLaMA-Factory !2025-03-284555881|Easy-to-use LLM fine-tuning framework (LLaMA, BLOOM, Mistral, Baichuan, Qwen, ChatGLM)| | 88|Asabeneh/30-Days-Of-Python !2025-03-284544930|30 days of Python programming challenge is a step-by-step guide to learn the Python programming language in 30 days. This challenge may take more than100 days, follow your own pace. These videos may help too: https://www.youtube.com/channel/UC7PNRuno1rzYPb1xLa4yktw| | 89|type-challenges/type-challenges !2025-03-284488511|Collection of TypeScript type challenges with online judge| | 90|lllyasviel/Fooocus !2025-03-284402716|Focus on prompting and generating| | 91|RVC-Boss/GPT-SoVITS !2025-03-284327738|1 min voice data can also be used to train a good TTS model! (few shot voice cloning)| | 92|rasbt/LLMs-from-scratch !2025-03-284320667|Implementing a ChatGPT-like LLM from scratch, step by step| | 93|oobabooga/text-generation-webui !2025-03-284302012 |A gradio web UI for running Large Language Models like LLaMA, llama.cpp, GPT-J, OPT, and GALACTICA.| | 94|vllm-project/vllm !2025-03-2842982102|A high-throughput and memory-efficient inference and serving engine for LLMs| | 95|dani-garcia/vaultwarden !2025-03-284297121|Unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs| | 96|microsoft/autogen !2025-03-284233049|Enable Next-Gen Large Language Model Applications. Join our Discord: https://discord.gg/pAbnFJrkgZ| | 97|jeecgboot/JeecgBoot !2025-03-284205920|🔥「企业级低代码平台」前后端分离架构SpringBoot 2.x/3.x，SpringCloud，Ant Design&Vue3，Mybatis，Shiro，JWT。强大的代码生成器让前后端代码一键生成，无需写任何代码! 引领新的开发模式OnlineCoding->代码生成->手工MERGE，帮助Java项目解决70%重复工作，让开发更关注业务，既能快速提高效率，帮助公司节省成本，同时又不失灵活性。| | 98|Mintplex-Labs/anything-llm !2025-03-284186955|A full-stack application that turns any documents into an intelligent chatbot with a sleek UI and easier way to manage your workspaces.| | 99|THUDM/ChatGLM-6B !2025-03-28410192 |ChatGLM-6B: An Open Bilingual Dialogue Language Model| | 100|hpcaitech/ColossalAI !2025-03-28406902|Making large AI models cheaper, faster and more accessible| | 101|Stability-AI/stablediffusion !2025-03-28406337|High-Resolution Image Synthesis with Latent Diffusion Models| | 102|mingrammer/diagrams !2025-03-28405063|🎨 Diagram as Code for prototyping cloud system architectures| | 103|Kong/kong !2025-03-28404616|🦍 The Cloud-Native API Gateway and AI Gateway.| | 104|getsentry/sentry !2025-03-284040913|Developer-first error tracking and performance monitoring| | 105| karpathy/nanoGPT !2025-03-284034613 |The simplest, fastest repository for training/finetuning medium-sized GPTs| | 106|fastlane/fastlane !2025-03-2840014-1|🚀 The easiest way to automate building and releasing your iOS and Android apps| | 107|psf/black !2025-03-28399765|The uncompromising Python code formatter| | 108|OpenBB-finance/OpenBBTerminal !2025-03-283972074 |Investment Research for Everyone, Anywhere.| | 109|2dust/v2rayNG !2025-03-283943415|A V2Ray client for Android, support Xray core and v2fly core| | 110|apache/airflow !2025-03-283937314|Apache Airflow - A platform to programmatically author, schedule, and monitor workflows| | 111|KRTirtho/spotube !2025-03-283902746|🎧 Open source Spotify client that doesn't require Premium nor uses Electron! Available for both desktop & mobile!| | 112|coqui-ai/TTS !2025-03-283889719 |🐸💬 - a deep learning toolkit for Text-to-Speech, battle-tested in research and production| | 113|ggerganov/whisper.cpp !2025-03-283882116|Port of OpenAI's Whisper model in C/C++| | 114|ultralytics/ultralytics !2025-03-283866951|NEW - YOLOv8 🚀 in PyTorch > ONNX > OpenVINO > CoreML > TFLite| | 115|typst/typst !2025-03-283863914|A new markup-based typesetting system that is powerful and easy to learn.| | 116|streamlit/streamlit !2025-03-283845828|Streamlit — A faster way to build and share data apps.| | 117|LC044/WeChatMsg !2025-03-283836931|提取微信聊天记录，将其导出成HTML、Word、Excel文档永久保存，对聊天记录进行分析生成年度聊天报告，用聊天数据训练专属于个人的AI聊天助手| | 118|lm-sys/FastChat !2025-03-283822112 |An open platform for training, serving, and evaluating large languages. Release repo for Vicuna and FastChat-T5.| | 119|NaiboWang/EasySpider !2025-03-283819013|A visual no-code/code-free web crawler/spider易采集：一个可视化浏览器自动化测试/数据采集/爬虫软件，可以无代码图形化的设计和执行爬虫任务。别名：ServiceWrapper面向Web应用的智能化服务封装系统。| | 120|microsoft/DeepSpeed !2025-03-283765816 |A deep learning optimization library that makes distributed training and inference easy, efficient, and effective| | 121|QuivrHQ/quivr !2025-03-28376067|Your GenAI Second Brain 🧠 A personal productivity assistant (RAG) ⚡️🤖 Chat with your docs (PDF, CSV, ...) & apps using Langchain, GPT 3.5 / 4 turbo, Private, Anthropic, VertexAI, Ollama, LLMs, that you can share with users ! Local & Private alternative to OpenAI GPTs & ChatGPT powered by retrieval-augmented generation.| | 122|freqtrade/freqtrade !2025-03-283757817 |Free, open source crypto trading bot| | 123|suno-ai/bark !2025-03-28373178 |🔊 Text-Prompted Generative Audio Model| | 124|🔥cline/cline !2025-03-2837307282|Autonomous coding agent right in your IDE, capable of creating/editing files, executing commands, and more with your permission every step of the way.| | 125|LAION-AI/Open-Assistant !2025-03-28372712 |OpenAssistant is a chat-based assistant that understands tasks, can interact with third-party systems, and retrieve information dynamically to do so.| | 126|penpot/penpot !2025-03-283716217|Penpot: The open-source design tool for design and code collaboration| | 127|gradio-app/gradio !2025-03-283713320|Build and share delightful machine learning apps, all in Python. 🌟 Star to support our work!| | 128|FlowiseAI/Flowise !2025-03-283667135 |Drag & drop UI to build your customized LLM flow using LangchainJS| | 129|SimplifyJobs/Summer2025-Internships !2025-03-28366506|Collection of Summer 2025 tech internships!| | 130|TencentARC/GFPGAN !2025-03-28365027 |GFPGAN aims at developing Practical Algorithms for Real-world Face Restoration.| | 131|ray-project/ray !2025-03-283626819|Ray is a unified framework for scaling AI and Python applications. Ray consists of a core distributed runtime and a toolkit of libraries (Ray AIR) for accelerating ML workloads.| | 132|babysor/MockingBird !2025-03-28360498|🚀AI拟声: 5秒内克隆您的声音并生成任意语音内容 Clone a voice in 5 seconds to generate arbitrary speech in real-time| | 133|unslothai/unsloth !2025-03-283603691|5X faster 50% less memory LLM finetuning| | 134|zhayujie/chatgpt-on-wechat !2025-03-283600124 |Wechat robot based on ChatGPT, which uses OpenAI api and itchat library| | 135|upscayl/upscayl !2025-03-283599824|🆙 Upscayl - Free and Open Source AI Image Upscaler for Linux, MacOS and Windows built with Linux-First philosophy.| | 136|freeCodeCamp/devdocs !2025-03-28359738|API Documentation Browser| | 137|XingangPan/DragGAN !2025-03-28359043 |Code for DragGAN (SIGGRAPH 2023)| | 138|2noise/ChatTTS !2025-03-283543922|ChatTTS is a generative speech model for daily dialogue.| | 139|google-research/google-research !2025-03-28352207 |Google Research| | 140|karanpratapsingh/system-design !2025-03-28351003|Learn how to design systems at scale and prepare for system design interviews| | 141|lapce/lapce !2025-03-28350855|Lightning-fast and Powerful Code Editor written in Rust| | 142| microsoft/TaskMatrix !2025-03-2834500-3 | Talking, Drawing and Editing with Visual Foundation Models| | 143|chatchat-space/Langchain-Chatchat !2025-03-283442020|Langchain-Chatchat (formerly langchain-ChatGLM), local knowledge based LLM (like ChatGLM) QA app with langchain| | 144|unclecode/crawl4ai !2025-03-283434163|🔥🕷️ Crawl4AI: Open-source LLM Friendly Web Crawler & Scrapper| | 145|Bin-Huang/chatbox !2025-03-283374733 |A desktop app for GPT-4 / GPT-3.5 (OpenAI API) that supports Windows, Mac & Linux| | 146|milvus-io/milvus !2025-03-283366525 |A cloud-native vector database, storage for next generation AI applications| | 147|mendableai/firecrawl !2025-03-2833297128|🔥 Turn entire websites into LLM-ready markdown| | 148|pola-rs/polars !2025-03-283269320|Fast multi-threaded, hybrid-out-of-core query engine focussing on DataFrame front-ends| | 149|Pythagora-io/gpt-pilot !2025-03-28325321|PoC for a scalable dev tool that writes entire apps from scratch while the developer oversees the implementation| | 150|hashicorp/vault !2025-03-28320797|A tool for secrets management, encryption as a service, and privileged access management| | 151|shardeum/shardeum !2025-03-28319580|Shardeum is an EVM based autoscaling blockchain| | 152|Chanzhaoyu/chatgpt-web !2025-03-28319242 |A demonstration website built with Express and Vue3 called ChatGPT| | 153|lllyasviel/ControlNet !2025-03-283186413 |Let us control diffusion models!| | 154|google/jax !2025-03-28317727|Composable transformations of Python+NumPy programs: differentiate, vectorize, JIT to GPU/TPU, and more| | 155|facebookresearch/detectron2 !2025-03-28315987|Detectron2 is a platform for object detection, segmentation and other visual recognition tasks.| | 156|myshell-ai/OpenVoice !2025-03-28315233|Instant voice cloning by MyShell| | 157|TheAlgorithms/C-Plus-Plus !2025-03-283151411|Collection of various algorithms in mathematics, machine learning, computer science and physics implemented in C++ for educational purposes.| | 158|hiroi-sora/Umi-OCR !2025-03-283138129|OCR图片转文字识别软件，完全离线。截屏/批量导入图片，支持多国语言、合并段落、竖排文字。可排除水印区域，提取干净的文本。基于 PaddleOCR 。| | 159|mudler/LocalAI !2025-03-283127815|🤖 The free, Open Source OpenAI alternative. Self-hosted, community-driven and local-first. Drop-in replacement for OpenAI running on consumer-grade hardware. No GPU required. Runs gguf, transformers, diffusers and many more models architectures. It allows to generate Text, Audio, Video, Images. Also with voice cloning capabilities.| | 160|facebookresearch/fairseq !2025-03-28312124 |Facebook AI Research Sequence-to-Sequence Toolkit written in Python.| | 161|alibaba/nacos !2025-03-28310559|an easy-to-use dynamic service discovery, configuration and service management platform for building cloud native applications.| | 162|yunjey/pytorch-tutorial !2025-03-28310326|PyTorch Tutorial for Deep Learning Researchers| | 163|v2fly/v2ray-core !2025-03-28307448|A platform for building proxies to bypass network restrictions.| | 164|mckaywrigley/chatbot-ui !2025-03-283067714|The open-source AI chat interface for everyone.| | 165|TabbyML/tabby !2025-03-28305949 |Self-hosted AI coding assistant| | 166|deepseek-ai/awesome-deepseek-integration !2025-03-283053193|| | 167|danielmiessler/fabric !2025-03-283028914|fabric is an open-source framework for augmenting humans using AI.| | 168|xinntao/Real-ESRGAN !2025-03-283026623 |Real-ESRGAN aims at developing Practical Algorithms for General Image/Video Restoration.| | 169|paul-gauthier/aider !2025-03-283014642|aider is GPT powered coding in your terminal| | 170|tatsu-lab/stanfordalpaca !2025-03-28299022 |Code and documentation to train Stanford's Alpaca models, and generate the data.| | 171|DataTalksClub/data-engineering-zoomcamp !2025-03-282971817|Free Data Engineering course!| | 172|HeyPuter/puter !2025-03-282967014|🌐 The Internet OS! Free, Open-Source, and Self-Hostable.| | 173|mli/paper-reading !2025-03-282962314|Classic Deep Learning and In-Depth Reading of New Papers Paragraph by Paragraph| | 174|linexjlin/GPTs !2025-03-28295568|leaked prompts of GPTs| | 175|s0md3v/roop !2025-03-28295286 |one-click deepfake (face swap)| | 176|JushBJJ/Mr.-Ranedeer-AI-Tutor !2025-03-2829465-1 |A GPT-4 AI Tutor Prompt for customizable personalized learning experiences.| | 177|opendatalab/MinerU !2025-03-282927074|A one-stop, open-source, high-quality data extraction tool, supports PDF/webpage/e-book extraction.一站式开源高质量数据提取工具，支持PDF/网页/多格式电子书提取。| | 178|mouredev/Hello-Python !2025-03-282920720|Curso para aprender el lenguaje de programación Python desde cero y para principiantes. 75 clases, 37 horas en vídeo, código, proyectos y grupo de chat. Fundamentos, frontend, backend, testing, IA...| | 179|Lightning-AI/pytorch-lightning !2025-03-28292039|Pretrain, finetune and deploy AI models on multiple GPUs, TPUs with zero code changes.| | 180|crewAIInc/crewAI !2025-03-282919344|Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.| | 181|facebook/folly !2025-03-282916612|An open-source C++ library developed and used at Facebook.| | 182|google-ai-edge/mediapipe !2025-03-28291519|Cross-platform, customizable ML solutions for live and streaming media.| | 183| getcursor/cursor !2025-03-282892025 | An editor made for programming with AI| | 184|chatanywhere/GPTAPIfree !2025-03-282856424|Free ChatGPT API Key, Free ChatGPT API, supports GPT-4 API (free), ChatGPT offers a free domestic forwarding API that allows direct connections without the need for a proxy. It can be used in conjunction with software/plugins like ChatBox, significantly reducing interface usage costs. Enjoy unlimited and unrestricted chatting within China| | 185|meta-llama/llama3 !2025-03-28285552|The official Meta Llama 3 GitHub site| | 186|tinygrad/tinygrad !2025-03-282845811|You like pytorch? You like micrograd? You love tinygrad! ❤️| | 187|google-research/tuningplaybook !2025-03-282841514|A playbook for systematically maximizing the performance of deep learning models.| | 188|huggingface/diffusers !2025-03-282830222|🤗 Diffusers: State-of-the-art diffusion models for image and audio generation in PyTorch and FLAX.| | 189|tokio-rs/tokio !2025-03-28282408|A runtime for writing reliable asynchronous applications with Rust. Provides I/O, networking, scheduling, timers, ...| | 190|RVC-Project/Retrieval-based-Voice-Conversion-WebUI !2025-03-282823817|Voice data !2025-03-282822612|Jan is an open source alternative to ChatGPT that runs 100% offline on your computer| | 192|openai/CLIP !2025-03-282814720|CLIP (Contrastive Language-Image Pretraining), Predict the most relevant text snippet given an image| | 193|🔥khoj-ai/khoj !2025-03-2828112313|Your AI second brain. A copilot to get answers to your questions, whether they be from your own notes or from the internet. Use powerful, online (e.g gpt4) or private, local (e.g mistral) LLMs. Self-host locally or use our web app. Access from Obsidian, Emacs, Desktop app, Web or Whatsapp.| | 194| acheong08/ChatGPT !2025-03-2828054-2 | Reverse engineered ChatGPT API | | 195|iperov/DeepFaceLive !2025-03-28279345 |Real-time face swap for PC streaming or video calls| | 196|eugeneyan/applied-ml !2025-03-28278471|📚 Papers & tech blogs by companies sharing their work on data science & machine learning in production.| | 197|XTLS/Xray-core !2025-03-282778213|Xray, Penetrates Everything. Also the best v2ray-core, with XTLS support. Fully compatible configuration.| | 198|feder-cr/JobsApplierAIAgent !2025-03-282776410|AutoJobsApplierAI_Agent aims to easy job hunt process by automating the job application process. Utilizing artificial intelligence, it enables users to apply for multiple jobs in an automated and personalized way.| | 199|mindsdb/mindsdb !2025-03-282750631|The platform for customizing AI from enterprise data| | 200|DataExpert-io/data-engineer-handbook !2025-03-282721611|This is a repo with links to everything you'd ever want to learn about data engineering| | 201|exo-explore/exo !2025-03-282721633|Run your own AI cluster at home with everyday devices 📱💻 🖥️⌚| | 202|taichi-dev/taichi !2025-03-2826926-1|Productive, portable, and performant GPU programming in Python.| | 203|mem0ai/mem0 !2025-03-282689134|The memory layer for Personalized AI| | 204|svc-develop-team/so-vits-svc !2025-03-28268096 |SoftVC VITS Singing Voice Conversion| | 205|OpenBMB/ChatDev !2025-03-28265624|Create Customized Software using Natural Language Idea (through Multi-Agent Collaboration)| | 206|roboflow/supervision !2025-03-282632010|We write your reusable computer vision tools. 💜| | 207|drawdb-io/drawdb !2025-03-282626913|Free, simple, and intuitive online database design tool and SQL generator.| | 208|karpathy/llm.c !2025-03-28261633|LLM training in simple, raw C/CUDA| | 209|airbnb/lottie-ios !2025-03-28261431|An iOS library to natively render After Effects vector animations| | 210|openai/openai-python !2025-03-282607713|The OpenAI Python library provides convenient access to the OpenAI API from applications written in the Python language.| | 211|academic/awesome-datascience !2025-03-28259876|📝 An awesome Data Science repository to learn and apply for real world problems.| | 212|harry0703/MoneyPrinterTurbo !2025-03-282576618|Generate short videos with one click using a large model| | 213|gabime/spdlog !2025-03-282571511|Fast C++ logging library.| | 214|ocrmypdf/OCRmyPDF !2025-03-2825674217|OCRmyPDF adds an OCR text layer to scanned PDF files, allowing them to be searched| | 215|Vision-CAIR/MiniGPT-4 !2025-03-28256170 |Enhancing Vision-language Understanding with Advanced Large Language Models| | 216|Stability-AI/generative-models !2025-03-28255936|Generative Models by Stability AI| | 217|DS4SD/docling !2025-03-282555662|Get your docs ready for gen AI| | 218|PostHog/posthog !2025-03-282533227|🦔 PostHog provides open-source product analytics, session recording, feature flagging and A/B testing that you can self-host.| | 219|nrwl/nx !2025-03-282509612|Smart Monorepos · Fast CI| | 220|continuedev/continue !2025-03-282500737|⏩ the open-source copilot chat for software development—bring the power of ChatGPT to VS Code| | 221|opentofu/opentofu !2025-03-28247968|OpenTofu lets you declaratively manage your cloud infrastructure.| | 222|invoke-ai/InvokeAI !2025-03-28247293|InvokeAI is a leading creative engine for Stable Diffusion models, empowering professionals, artists, and enthusiasts to generate and create visual media using the latest AI-driven technologies. The solution offers an industry leading WebUI, supports terminal use through a CLI, and serves as the foundation for multiple commercial products.| | 223|deepinsight/insightface !2025-03-282471615 |State-of-the-art 2D and 3D Face Analysis Project| | 224|apache/flink !2025-03-28246865|Apache Flink| | 225|ComposioHQ/composio !2025-03-28246436|Composio equips agents with well-crafted tools empowering them to tackle complex tasks| | 226|Genesis-Embodied-AI/Genesis !2025-03-282458314|A generative world for general-purpose robotics & embodied AI learning.| | 227|stretchr/testify !2025-03-28243184|A toolkit with common assertions and mocks that plays nicely with the standard library| | 228| yetone/openai-translator !2025-03-28242921 | Browser extension and cross-platform desktop application for translation based on ChatGPT API | | 229|frappe/erpnext !2025-03-282425211|Free and Open Source Enterprise Resource Planning (ERP)| | 230|songquanpeng/one-api !2025-03-282410034|OpenAI 接口管理 & 分发系统，支持 Azure、Anthropic Claude、Google PaLM 2 & Gemini、智谱 ChatGLM、百度文心一言、讯飞星火认知、阿里通义千问、360 智脑以及腾讯混元，可用于二次分发管理 key，仅单可执行文件，已打包好 Docker 镜像，一键部署，开箱即用. OpenAI key management & redistribution system, using a single API for all LLMs, and features an English UI.| | 231| microsoft/JARVIS !2025-03-28240604 | a system to connect LLMs with ML community | | 232|google/flatbuffers !2025-03-28239965|FlatBuffers: Memory Efficient Serialization Library| | 233|microsoft/graphrag !2025-03-282398928|A modular graph-based Retrieval-Augmented Generation (RAG) system| | 234|rancher/rancher !2025-03-28239675|Complete container management platform| | 235|bazelbuild/bazel !2025-03-282384618|a fast, scalable, multi-language and extensible build system| | 236|modularml/mojo !2025-03-28238236 |The Mojo Programming Language| | 237|danny-avila/LibreChat !2025-03-282378753|Enhanced ChatGPT Clone: Features OpenAI, GPT-4 Vision, Bing, Anthropic, OpenRouter, Google Gemini, AI model switching, message search, langchain, DALL-E-3, ChatGPT Plugins, OpenAI Functions, Secure Multi-User System, Presets, completely open-source for self-hosting. More features in development| |!green-up-arrow.svg 238|🔥🔥🔥Shubhamsaboo/awesome-llm-apps !2025-03-28237391211|Collection of awesome LLM apps with RAG using OpenAI, Anthropic, Gemini and opensource models.| |!red-down-arrow 239|microsoft/semantic-kernel !2025-03-282373611|Integrate cutting-edge LLM technology quickly and easily into your apps| |!red-down-arrow 240|TheAlgorithms/Rust !2025-03-28236995|All Algorithms implemented in Rust| | 241|stanford-oval/storm !2025-03-28236326|An LLM-powered knowledge curation system that researches a topic and generates a full-length report with citations.| | 242|openai/gpt-2 !2025-03-28232483|Code for the paper "Language Models are Unsupervised Multitask Learners"| | 243|labring/FastGPT !2025-03-282319445|A platform that uses the OpenAI API to quickly build an AI knowledge base, supporting many-to-many relationships.| | 244|pathwaycom/llm-app !2025-03-2822928-10|Ready-to-run cloud templates for RAG, AI pipelines, and enterprise search with live data. 🐳Docker-friendly.⚡Always in sync with Sharepoint, Google Drive, S3, Kafka, PostgreSQL, real-time data APIs, and more.| | 245|warpdotdev/Warp !2025-03-282286825|Warp is a modern, Rust-based terminal with AI built in so you and your team can build great software, faster.| | 246|🔥agno-agi/agno !2025-03-2822833298|Agno is a lightweight library for building Multimodal Agents. It exposes LLMs as a unified API and gives them superpowers like memory, knowledge, tools and reasoning.| | 247|qdrant/qdrant !2025-03-282275214 |Qdrant - Vector Database for the next generation of AI applications. Also available in the cloud https://cloud.qdrant.io/| | 248|ashishpatel26/500-AI-Machine-learning-Deep-learning-Computer-vision-NLP-Projects-with-code !2025-03-282271815|500 AI Machine learning Deep learning Computer vision NLP Projects with code| | 249|stanfordnlp/dspy !2025-03-282268321|Stanford DSPy: The framework for programming—not prompting—foundation models| | 250|PaddlePaddle/Paddle !2025-03-28226246|PArallel Distributed Deep LEarning: Machine Learning Framework from Industrial Practice （『飞桨』核心框架，深度学习&机器学习高性能单机、分布式训练和跨平台部署）| | 251|zulip/zulip !2025-03-28225464|Zulip server and web application. Open-source team chat that helps teams stay productive and focused.| | 252|Hannibal046/Awesome-LLM !2025-03-282240721|Awesome-LLM: a curated list of Large Language Model| | 253|facefusion/facefusion !2025-03-282218812|Next generation face swapper and enhancer| | 254|Mozilla-Ocho/llamafile !2025-03-28220624|Distribute and run LLMs with a single file.| | 255|yuliskov/SmartTube !2025-03-282201614|SmartTube - an advanced player for set-top boxes and tvs running Android OS| | 256|haotian-liu/LLaVA !2025-03-282201316 |Large Language-and-Vision Assistant built towards multimodal GPT-4 level capabilities.| | 257|ashishps1/awesome-system-design-resources !2025-03-282189367|This repository contains System Design resources which are useful while preparing for interviews and learning Distributed Systems| | 258|Cinnamon/kotaemon !2025-03-28218248|An open-source RAG-based tool for chatting with your documents.| | 259|CodePhiliaX/Chat2DB !2025-03-282179757|🔥🔥🔥AI-driven database tool and SQL client, The hottest GUI client, supporting MySQL, Oracle, PostgreSQL, DB2, SQL Server, DB2, SQLite, H2, ClickHouse, and more.| | 260|blakeblackshear/frigate !2025-03-282177113|NVR with realtime local object detection for IP cameras| | 261|facebookresearch/audiocraft !2025-03-28217111|Audiocraft is a library for audio processing and generation with deep learning. It features the state-of-the-art EnCodec audio compressor / tokenizer, along with MusicGen, a simple and controllable music generation LM with textual and melodic conditioning.| | 262|karpathy/minGPT !2025-03-28216567|A minimal PyTorch re-implementation of the OpenAI GPT (Generative Pretrained Transformer) training| | 263|grpc/grpc-go !2025-03-282159510|The Go language implementation of gRPC. HTTP/2 based RPC| | 264|HumanSignal/label-studio !2025-03-282137618|Label Studio is a multi-type data labeling and annotation tool with standardized output format| | 265|yoheinakajima/babyagi !2025-03-28212764 |uses OpenAI and Pinecone APIs to create, prioritize, and execute tasks, This is a pared-down version of the original Task-Driven Autonomous Agent| | 266|deepseek-ai/DeepSeek-Coder !2025-03-282118210|DeepSeek Coder: Let the Code Write Itself| | 267|BuilderIO/gpt-crawler !2025-03-282118010|Crawl a site to generate knowledge files to create your own custom GPT from a URL| | 268| openai/chatgpt-retrieval-plugin !2025-03-2821152-1 | Plugins are chat extensions designed specifically for language models like ChatGPT, enabling them to access up-to-date information, run computations, or interact with third-party services in response to a user's request.| | 269|microsoft/OmniParser !2025-03-282113123|A simple screen parsing tool towards pure vision based GUI agent| | 270|black-forest-labs/flux !2025-03-282107219|Official inference repo for FLUX.1 models| | 271|ItzCrazyKns/Perplexica !2025-03-282099154|Perplexica is an AI-powered search engine. It is an Open source alternative to Perplexity AI| | 272|microsoft/unilm !2025-03-28209876|Large-scale Self-supervised Pre-training Across Tasks, Languages, and Modalities| | 273|Sanster/lama-cleaner !2025-03-282077614|Image inpainting tool powered by SOTA AI Model. Remove any unwanted object, defect, people from your pictures or erase and replace(powered by stable diffusion) any thing on your pictures.| | 274|assafelovic/gpt-researcher !2025-03-282057222|GPT based autonomous agent that does online comprehensive research on any given topic| | 275|PromtEngineer/localGPT !2025-03-28204230 |Chat with your documents on your local device using GPT models. No data leaves your device and 100% private.| | 276|elastic/kibana !2025-03-28203482|Your window into the Elastic Stack| | 277|fishaudio/fish-speech !2025-03-282033222|Brand new TTS solution| | 278|mlc-ai/mlc-llm !2025-03-282028110 |Enable everyone to develop, optimize and deploy AI models natively on everyone's devices.| | 279|deepset-ai/haystack !2025-03-282005320|🔍 Haystack is an open source NLP framework to interact with your data using Transformer models and LLMs (GPT-4, ChatGPT and alike). Haystack offers production-ready tools to quickly build complex question answering, semantic search, text generation applications, and more.| | 280|tree-sitter/tree-sitter !2025-03-28200487|An incremental parsing system for programming tools| | 281|Anjok07/ultimatevocalremovergui !2025-03-281999811|GUI for a Vocal Remover that uses Deep Neural Networks.| | 282|guidance-ai/guidance !2025-03-28199622|A guidance language for controlling large language models.| | 283|ml-explore/mlx !2025-03-28199619|MLX: An array framework for Apple silicon| | 284|mlflow/mlflow !2025-03-281995314|Open source platform for the machine learning lifecycle| | 285|ml-tooling/best-of-ml-python !2025-03-28198631|🏆 A ranked list of awesome machine learning Python libraries. Updated weekly.| | 286|BerriAI/litellm !2025-03-281981862|Call all LLM APIs using the OpenAI format. Use Bedrock, Azure, OpenAI, Cohere, Anthropic, Ollama, Sagemaker, HuggingFace, Replicate (100+ LLMs)| | 287|LazyVim/LazyVim !2025-03-281981320|Neovim config for the lazy| | 288|wez/wezterm !2025-03-281976018|A GPU-accelerated cross-platform terminal emulator and multiplexer written by @wez and implemented in Rust| | 289|valkey-io/valkey !2025-03-281970416|A flexible distributed key-value datastore that supports both caching and beyond caching workloads.| | 290|LiLittleCat/awesome-free-chatgpt !2025-03-28196185|🆓免费的 ChatGPT 镜像网站列表，持续更新。List of free ChatGPT mirror sites, continuously updated.| | 291|Byaidu/PDFMathTranslate !2025-03-281947645|PDF scientific paper translation with preserved formats - 基于 AI 完整保留排版的 PDF 文档全文双语翻译，支持 Google/DeepL/Ollama/OpenAI 等服务，提供 CLI/GUI/Docker| | 292|openai/swarm !2025-03-281947111|Educational framework exploring ergonomic, lightweight multi-agent orchestration. Managed by OpenAI Solution team.| | 293|HqWu-HITCS/Awesome-Chinese-LLM !2025-03-281921423|Organizing smaller, cost-effective, privately deployable open-source Chinese language models, including related datasets and tutorials| | 294|stitionai/devika !2025-03-28190903|Devika is an Agentic AI Software Engineer that can understand high-level human instructions, break them down into steps, research relevant information, and write code to achieve the given objective. Devika aims to be a competitive open-source alternative to Devin by Cognition AI.| | 295|OpenBMB/MiniCPM-o !2025-03-28190887|MiniCPM-o 2.6: A GPT-4o Level MLLM for Vision, Speech and Multimodal Live Streaming on Your Phone| | 296|samber/lo !2025-03-281904815|💥 A Lodash-style Go library based on Go 1.18+ Generics (map, filter, contains, find...)| | 297|chroma-core/chroma !2025-03-281895221 |the AI-native open-source embedding database| | 298|DarkFlippers/unleashed-firmware !2025-03-28189278|Flipper Zero Unleashed Firmware| | 299|brave/brave-browser !2025-03-281892710|Brave browser for Android, iOS, Linux, macOS, Windows.| | 300| tloen/alpaca-lora !2025-03-28188641 | Instruct-tune LLaMA on consumer hardware| | 301|VinciGit00/Scrapegraph-ai !2025-03-281884618|Python scraper based on AI| | 302|gitroomhq/postiz-app !2025-03-281879110|📨 Schedule social posts, measure them, exchange with other members and get a lot of help from AI 🚀| | 303|PrefectHQ/prefect !2025-03-281878715|Prefect is a workflow orchestration tool empowering developers to build, observe, and react to data pipelines| | 304|ymcui/Chinese-LLaMA-Alpaca !2025-03-28187723 |Chinese LLaMA & Alpaca LLMs| | 305|kenjihiranabe/The-Art-of-Linear-Algebra !2025-03-28187335|Graphic notes on Gilbert Strang's "Linear Algebra for Everyone"| | 306|joonspk-research/generativeagents !2025-03-28187288|Generative Agents: Interactive Simulacra of Human Behavior| | 307|renovatebot/renovate !2025-03-28186820|Universal dependency update tool that fits into your workflows.| | 308|gventuri/pandas-ai !2025-03-28186109 |Pandas AI is a Python library that integrates generative artificial intelligence capabilities into Pandas, making dataframes conversational| | 309|thingsboard/thingsboard !2025-03-28185184|Open-source IoT Platform - Device management, data collection, processing and visualization.| | 310|ente-io/ente !2025-03-28184722|Fully open source, End to End Encrypted alternative to Google Photos and Apple Photos| | 311|serengil/deepface !2025-03-281840113|A Lightweight Face Recognition and Facial Attribute Analysis (Age, Gender, Emotion and Race) Library for Python| | 312|Raphire/Win11Debloat !2025-03-281840132|A simple, easy to use PowerShell script to remove pre-installed apps from windows, disable telemetry, remove Bing from windows search as well as perform various other changes to declutter and improve your windows experience. This script works for both windows 10 and windows 11.| | 313|Avaiga/taipy !2025-03-28179235|Turns Data and AI algorithms into production-ready web applications in no time.| | 314|microsoft/qlib !2025-03-281784231|Qlib is an AI-oriented quantitative investment platform that aims to realize the potential, empower research, and create value using AI technologies in quantitative investment, from exploring ideas to implementing productions. Qlib supports diverse machine learning modeling paradigms. including supervised learning, market dynamics modeling, and RL.| | 315|CopilotKit/CopilotKit !2025-03-281778571|Build in-app AI chatbots 🤖, and AI-powered Textareas ✨, into react web apps.| | 316|QwenLM/Qwen-7B !2025-03-281766017|The official repo of Qwen-7B (通义千问-7B) chat & pretrained large language model proposed by Alibaba Cloud.| | 317|w-okada/voice-changer !2025-03-28176078 |リアルタイムボイスチェンジャー Realtime Voice Changer| | 318|rlabbe/Kalman-and-Bayesian-Filters-in-Python !2025-03-281756011|Kalman Filter book using Jupyter Notebook. Focuses on building intuition and experience, not formal proofs. Includes Kalman filters,extended Kalman filters, unscented Kalman filters, particle filters, and more. All exercises include solutions.| | 319|Mikubill/sd-webui-controlnet !2025-03-28174794 |WebUI extension for ControlNet| | 320|jingyaogong/minimind !2025-03-2817380116|「大模型」3小时完全从0训练26M的小参数GPT，个人显卡即可推理训练！| | 321|apify/crawlee !2025-03-28172696|Crawlee—A web scraping and browser automation library for Node.js to build reliable crawlers. In JavaScript and TypeScript. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with Puppeteer, Playwright, Cheerio, JSDOM, and raw HTTP. Both headful and headless mode. With proxy rotation.| | 322|apple/ml-stable-diffusion !2025-03-28172395|Stable Diffusion with Core ML on Apple Silicon| | 323| transitive-bullshit/chatgpt-api !2025-03-28172095 | Node.js client for the official ChatGPT API. | | 324|teableio/teable !2025-03-281719222|✨ The Next Gen Airtable Alternative: No-Code Postgres| | 325| xx025/carrot !2025-03-28170900 | Free ChatGPT Site List | | 326|microsoft/LightGBM !2025-03-28170723|A fast, distributed, high-performance gradient boosting (GBT, GBDT, GBRT, GBM or MART) framework based on decision tree algorithms, used for ranking, classification and many other machine learning tasks.| | 327|VikParuchuri/surya !2025-03-28169827|Accurate line-level text detection and recognition (OCR) in any language| | 328|deepseek-ai/Janus !2025-03-281692825|Janus-Series: Unified Multimodal Understanding and Generation Models| | 329|ardalis/CleanArchitecture !2025-03-28168823|Clean Architecture Solution Template: A starting point for Clean Architecture with ASP.NET Core| | 330|neondatabase/neon !2025-03-28166466|Neon: Serverless Postgres. We separated storage and compute to offer autoscaling, code-like database branching, and scale to zero.| | 331|kestra-io/kestra !2025-03-281661313|⚡ Workflow Automation Platform. Orchestrate & Schedule code in any language, run anywhere, 500+ plugins. Alternative to Zapier, Rundeck, Camunda, Airflow...| | 332|Dao-AILab/flash-attention !2025-03-281659720|Fast and memory-efficient exact attention| | 333|RPCS3/rpcs3 !2025-03-281655712|PS3 emulator/debugger| | 334|meta-llama/llama-recipes !2025-03-28165486|Scripts for fine-tuning Llama2 with composable FSDP & PEFT methods to cover single/multi-node GPUs. Supports default & custom datasets for applications such as summarization & question answering. Supporting a number of candid inference solutions such as HF TGI, VLLM for local or cloud deployment.Demo apps to showcase Llama2 for WhatsApp & Messenger| | 335|emilwallner/Screenshot-to-code !2025-03-28165180|A neural network that transforms a design mock-up into a static website.| | 336|datawhalechina/llm-cookbook !2025-03-281650922|面向开发者的 LLM 入门教程，吴恩达大模型系列课程中文版| | 337|e2b-dev/awesome-ai-agents !2025-03-281643923|A list of AI autonomous agents| | 338|QwenLM/Qwen2.5 !2025-03-281641114|Qwen2.5 is the large language model series developed by Qwen team, Alibaba Cloud.| | 339|dair-ai/ML-YouTube-Courses !2025-03-28164114|📺 Discover the latest machine learning / AI courses on YouTube.| | 340|pybind/pybind11 !2025-03-28163620|Seamless operability between C++11 and Python| | 341|graphdeco-inria/gaussian-splatting !2025-03-281627116|Original reference implementation of "3D Gaussian Splatting for Real-Time Radiance Field Rendering"| | 342|meta-llama/codellama !2025-03-28162531|Inference code for CodeLlama models| | 343|TransformerOptimus/SuperAGI !2025-03-28161292 | SuperAGI - A dev-first open source autonomous AI agent framework. Enabling developers to build, manage & run useful autonomous agents quickly and reliably.| | 344|microsoft/onnxruntime !2025-03-28161169|ONNX Runtime: cross-platform, high-performance ML inferencing and training accelerator| | 345|IDEA-Research/Grounded-Segment-Anything !2025-03-281601411 |Marrying Grounding DINO with Segment Anything & Stable Diffusion & BLIP - Automatically Detect, Segment and Generate Anything with Image and Text Inputs| | 346|ddbourgin/numpy-ml !2025-03-28160054|Machine learning, in numpy| | 347|eosphoros-ai/DB-GPT !2025-03-281585225|Revolutionizing Database Interactions with Private LLM Technology| | 348|Stability-AI/StableLM !2025-03-28158310 |Stability AI Language Models| | 349|openai/evals !2025-03-28157935 |Evals is a framework for evaluating LLMs and LLM systems, and an open-source registry of benchmarks.| | 350|THUDM/ChatGLM2-6B !2025-03-28157500|ChatGLM2-6B: An Open Bilingual Chat LLM | | 351|sunner/ChatALL !2025-03-28156761 |Concurrently chat with ChatGPT, Bing Chat, Bard, Alpaca, Vincuna, Claude, ChatGLM, MOSS, iFlytek Spark, ERNIE and more, discover the best answers| | 352|abseil/abseil-cpp !2025-03-28156656|Abseil Common Libraries (C++)| | 353|NVIDIA/open-gpu-kernel-modules !2025-03-28156531|NVIDIA Linux open GPU kernel module source| | 354|letta-ai/letta !2025-03-281563718|Letta (formerly MemGPT) is a framework for creating LLM services with memory.| | 355|typescript-eslint/typescript-eslint !2025-03-28156211|✨ Monorepo for all the tooling which enables ESLint to support TypeScript| | 356|umijs/umi !2025-03-28156211|A framework in react community ✨| | 357|AI4Finance-Foundation/FinGPT !2025-03-281561215|Data-Centric FinGPT. Open-source for open finance! Revolutionize 🔥 We'll soon release the trained model.| | 358|amplication/amplication !2025-03-28156022|🔥🔥🔥 The Only Production-Ready AI-Powered Backend Code Generation| | 359|KindXiaoming/pykan !2025-03-28155477|Kolmogorov Arnold Networks| | 360|arc53/DocsGPT !2025-03-28154900|GPT-powered chat for documentation, chat with your documents| | 361|influxdata/telegraf !2025-03-28154502|Agent for collecting, processing, aggregating, and writing metrics, logs, and other arbitrary data.| | 362|microsoft/Bringing-Old-Photos-Back-to-Life !2025-03-28154084|Bringing Old Photo Back to Life (CVPR 2020 oral)| | 363|GaiZhenbiao/ChuanhuChatGPT !2025-03-2815394-2|GUI for ChatGPT API and many LLMs. Supports agents, file-based QA, GPT finetuning and query with web search. All with a neat UI.| | 364|Zeyi-Lin/HivisionIDPhotos !2025-03-281529710|⚡️HivisionIDPhotos: a lightweight and efficient AI ID photos tools. 一个轻量级的AI证件照制作算法。| | 365| mayooear/gpt4-pdf-chatbot-langchain !2025-03-281529518 | GPT4 & LangChain Chatbot for large PDF docs | | 366|1Panel-dev/MaxKB !2025-03-2815277148|? Based on LLM large language model knowledge base Q&A system. Ready to use out of the box, supports quick integration into third-party business systems. Officially produced by 1Panel| | 367|ai16z/eliza !2025-03-281526811|Conversational Agent for Twitter and Discord| | 368|apache/arrow !2025-03-28151684|Apache Arrow is a multi-language toolbox for accelerated data interchange and in-memory processing| | 369|princeton-nlp/SWE-agent !2025-03-281516119|SWE-agent: Agent Computer Interfaces Enable Software Engineering Language Models| | 370|mlc-ai/web-llm !2025-03-281509311 |Bringing large-language models and chat to web browsers. Everything runs inside the browser with no server support.| | 371|guillaumekln/faster-whisper !2025-03-281507117 |Faster Whisper transcription with CTranslate2| | 372|overleaf/overleaf !2025-03-28150316|A web-based collaborative LaTeX editor| | 373|triton-lang/triton !2025-03-28150169|Development repository for the Triton language and compiler| | 374|soxoj/maigret !2025-03-281500410|🕵️‍♂️ Collect a dossier on a person by username from thousands of sites| | 375|alibaba/lowcode-engine !2025-03-28149841|An enterprise-class low-code technology stack with scale-out design / 一套面向扩展设计的企业级低代码技术体系| | 376|espressif/esp-idf !2025-03-28148545|Espressif IoT Development Framework. Official development framework for Espressif SoCs.| | 377|pgvector/pgvector !2025-03-281484913|Open-source vector similarity search for Postgres| | 378|datawhalechina/leedl-tutorial !2025-03-28148246|《李宏毅深度学习教程》（李宏毅老师推荐👍），PDF下载地址：https://github.com/datawhalechina/leedl-tutorial/releases| | 379|xcanwin/KeepChatGPT !2025-03-28147972 |Using ChatGPT is more efficient and smoother, perfectly solving ChatGPT network errors. No longer do you need to frequently refresh the webpage, saving over 10 unnecessary steps| | 380|m-bain/whisperX !2025-03-281471313|WhisperX: Automatic Speech Recognition with Word-level Timestamps (& Diarization)| | 381|HumanAIGC/AnimateAnyone !2025-03-2814706-1|Animate Anyone: Consistent and Controllable Image-to-Video Synthesis for Character Animation| |!green-up-arrow.svg 382|naklecha/llama3-from-scratch !2025-03-281469024|llama3 implementation one matrix multiplication at a time| |!red-down-arrow 383| fauxpilot/fauxpilot !2025-03-28146871 | An open-source GitHub Copilot server | | 384|LlamaFamily/Llama-Chinese !2025-03-28145111|Llama Chinese Community, the best Chinese Llama large model, fully open source and commercially available| | 385|BradyFU/Awesome-Multimodal-Large-Language-Models !2025-03-281450121|Latest Papers and Datasets on Multimodal Large Language Models| | 386|vanna-ai/vanna !2025-03-281449819|🤖 Chat with your SQL database 📊. Accurate Text-to-SQL Generation via LLMs using RAG 🔄.| | 387|bleedline/aimoneyhunter !2025-03-28144845|AI Side Hustle Money Mega Collection: Teaching You How to Utilize AI for Various Side Projects to Earn Extra Income.| | 388|stefan-jansen/machine-learning-for-trading !2025-03-28144629|Code for Machine Learning for Algorithmic Trading, 2nd edition.| | 389|state-spaces/mamba !2025-03-28144139|Mamba: Linear-Time Sequence Modeling with Selective State Spaces| | 390|vercel/ai-chatbot !2025-03-281434614|A full-featured, hackable Next.js AI chatbot built by Vercel| | 391|steven-tey/novel !2025-03-281428410|Notion-style WYSIWYG editor with AI-powered autocompletions| | 392|unifyai/ivy !2025-03-281409348|Unified AI| | 393|chidiwilliams/buzz !2025-03-281402411 |Buzz transcribes and translates audio offline on your personal computer. Powered by OpenAI's Whisper.| | 394|lukas-blecher/LaTeX-OCR !2025-03-28139769|pix2tex: Using a ViT to convert images of equations into LaTeX code.| | 395|openai/tiktoken !2025-03-28139599|tiktoken is a fast BPE tokeniser for use with OpenAI's models.| | 396|nocobase/nocobase !2025-03-281391522|NocoBase is a scalability-first, open-source no-code/low-code platform for building business applications and enterprise solutions.| | 397|neonbjb/tortoise-tts !2025-03-28139010 |A multi-voice TTS system trained with an emphasis on quality| | 398|yamadashy/repomix !2025-03-281382036|📦 Repomix (formerly Repopack) is a powerful tool that packs your entire repository into a single, AI-friendly file. Perfect for when you need to feed your codebase to Large Language Models (LLMs) or other AI tools like Claude, ChatGPT, and Gemini.| | 399|adobe/react-spectrum !2025-03-28136766|A collection of libraries and tools that help you build adaptive, accessible, and robust user experiences.| | 400|THUDM/ChatGLM3 !2025-03-28136684|ChatGLM3 series: Open Bilingual Chat LLMs | | 401|NVIDIA/NeMo !2025-03-28134837|A scalable generative AI framework built for researchers and developers working on Large Language Models, Multimodal, and Speech AI (Automatic Speech Recognition and Text-to-Speech)| | 402|BlinkDL/RWKV-LM !2025-03-28134346 |RWKV is an RNN with transformer-level LLM performance. It can be directly trained like a GPT (parallelizable). So it combines the best of RNN and transformer - great performance, fast inference, saves VRAM, fast training, "infinite" ctx_len, and free sentence embedding.| | 403| fuergaosi233/wechat-chatgpt !2025-03-28133330 | Use ChatGPT On Wechat via wechaty | | 404|udecode/plate !2025-03-28133325|A rich-text editor powered by AI| | 405|xenova/transformers.js !2025-03-281331219|State-of-the-art Machine Learning for the web. Run 🤗 Transformers directly in your browser, with no need for a server!| | 406|stas00/ml-engineering !2025-03-281325615|Machine Learning Engineering Guides and Tools| | 407| wong2/chatgpt-google-extension !2025-03-2813241-1 | A browser extension that enhances search engines with ChatGPT, this repos will not be updated from 2023-02-20| | 408|mrdbourke/pytorch-deep-learning !2025-03-281317520|Materials for the Learn PyTorch for Deep Learning: Zero to Mastery course.| | 409|Koenkk/zigbee2mqtt !2025-03-28131544|Zigbee 🐝 to MQTT bridge 🌉, get rid of your proprietary Zigbee bridges 🔨| | 410|vercel-labs/ai !2025-03-281298528|Build AI-powered applications with React, Svelte, and Vue| | 411|netease-youdao/QAnything !2025-03-28129318|Question and Answer based on Anything.| | 412|huggingface/trl !2025-03-281289622|Train transformer language models with reinforcement learning.| | 413|microsoft/BitNet !2025-03-28128503|Official inference framework for 1-bit LLMs| | 414|mediar-ai/screenpipe !2025-03-281283915|24/7 local AI screen & mic recording. Build AI apps that have the full context. Works with Ollama. Alternative to Rewind.ai. Open. Secure. You own your data. Rust.| | 415|Skyvern-AI/skyvern !2025-03-281277612|Automate browser-based workflows with LLMs and Computer Vision| | 416|pytube/pytube !2025-03-28126591|A lightweight, dependency-free Python library (and command-line utility) for downloading YouTube Videos.| | 417|official-stockfish/Stockfish !2025-03-28126574|UCI chess engine| | 418|sgl-project/sglang !2025-03-281260143|SGLang is a structured generation language designed for large language models (LLMs). It makes your interaction with LLMs faster and more controllable.| | 419|plasma-umass/scalene !2025-03-28125535|Scalene: a high-performance, high-precision CPU, GPU, and memory profiler for Python with AI-powered optimization proposals| | 420|danswer-ai/danswer !2025-03-28125503|Ask Questions in natural language and get Answers backed by private sources. Connects to tools like Slack, GitHub, Confluence, etc.| | 421|OpenTalker/SadTalker !2025-03-28125226|[CVPR 2023] SadTalker：Learning Realistic 3D Motion Coefficients for Stylized Audio-Driven Single Image Talking Face Animation| | 422|facebookresearch/AnimatedDrawings !2025-03-28123693 |Code to accompany "A Method for Animating Children's Drawings of the Human Figure"| | 423|activepieces/activepieces !2025-03-28123609|Your friendliest open source all-in-one automation tool ✨ Workflow automation tool 100+ integration / Enterprise automation tool / Zapier Alternative| | 424|ggerganov/ggml !2025-03-28121992 |Tensor library for machine learning| | 425|bytebase/bytebase !2025-03-28121694|World's most advanced database DevOps and CI/CD for Developer, DBA and Platform Engineering teams. The GitLab/GitHub for database DevOps.| | 426| willwulfken/MidJourney-Styles-and-Keywords-Reference !2025-03-28120971 | A reference containing Styles and Keywords that you can use with MidJourney AI| | 427|Huanshere/VideoLingo !2025-03-281207013|Netflix-level subtitle cutting, translation, alignment, and even dubbing - one-click fully automated AI video subtitle team | | 428|OpenLMLab/MOSS !2025-03-28120330 |An open-source tool-augmented conversational language model from Fudan University| | 429|llmware-ai/llmware !2025-03-281200727|Providing enterprise-grade LLM-based development framework, tools, and fine-tuned models.| | 430|PKU-YuanGroup/Open-Sora-Plan !2025-03-28119362|This project aim to reproduce Sora (Open AI T2V model), but we only have limited resource. We deeply wish the all open source community can contribute to this project.| | 431|ShishirPatil/gorilla !2025-03-28119332 |Gorilla: An API store for LLMs| | 432|NVIDIA/Megatron-LM !2025-03-281192716|Ongoing research training transformer models at scale| | 433|illacloud/illa-builder !2025-03-28119192|Create AI-Driven Apps like Assembling Blocks| | 434|marimo-team/marimo !2025-03-281191521|A reactive notebook for Python — run reproducible experiments, execute as a script, deploy as an app, and version with git.| | 435|smol-ai/developer !2025-03-28119111 | With 100k context windows on the way, it's now feasible for every dev to have their own smol developer| | 436|Lightning-AI/litgpt !2025-03-28118878|Pretrain, finetune, deploy 20+ LLMs on your own data. Uses state-of-the-art techniques: flash attention, FSDP, 4-bit, LoRA, and more.| | 437|openai/shap-e !2025-03-28118474 |Generate 3D objects conditioned on text or images| | 438|eugeneyan/open-llms !2025-03-28118451 |A list of open LLMs available for commercial use.| | 439|andrewyng/aisuite !2025-03-28118124|Simple, unified interface to multiple Generative AI providers| | 440|hajimehoshi/ebiten !2025-03-28117816|Ebitengine - A dead simple 2D game engine for Go| | 441|kgrzybek/modular-monolith-with-ddd !2025-03-28117493|Full Modular Monolith application with Domain-Driven Design approach.| | 442|h2oai/h2ogpt !2025-03-2811736-1 |Come join the movement to make the world's best open source GPT led by H2O.ai - 100% private chat and document search, no data leaks, Apache 2.0| | 443|owainlewis/awesome-artificial-intelligence !2025-03-28117332|A curated list of Artificial Intelligence (AI) courses, books, video lectures and papers.| | 444|DataTalksClub/mlops-zoomcamp !2025-03-28116643|Free MLOps course from DataTalks.Club| | 445|Rudrabha/Wav2Lip !2025-03-281163410|This repository contains the codes of "A Lip Sync Expert Is All You Need for Speech to Lip Generation In the Wild", published at ACM Multimedia 2020.| | 446|aishwaryanr/awesome-generative-ai-guide !2025-03-281152810|A one stop repository for generative AI research updates, interview resources, notebooks and much more!| | 447|karpathy/micrograd !2025-03-28115146|A tiny scalar-valued autograd engine and a neural net library on top of it with PyTorch-like API| | 448|InstantID/InstantID !2025-03-28115111|InstantID : Zero-shot Identity-Preserving Generation in Seconds 🔥| | 449|facebookresearch/seamlesscommunication !2025-03-28114434|Foundational Models for State-of-the-Art Speech and Text Translation| | 450|anthropics/anthropic-cookbook !2025-03-281140112|A collection of notebooks/recipes showcasing some fun and effective ways of using Claude.| | 451|mastra-ai/mastra !2025-03-281139240|the TypeScript AI agent framework| | 452|NVIDIA/TensorRT !2025-03-28113864|NVIDIA® TensorRT™ is an SDK for high-performance deep learning inference on NVIDIA GPUs. This repository contains the open source components of TensorRT.| | 453|plandex-ai/plandex !2025-03-28113645|An AI coding engine for complex tasks| | 454|RUCAIBox/LLMSurvey !2025-03-28112735 |A collection of papers and resources related to Large Language Models.| | 455|kubeshark/kubeshark !2025-03-28112711|The API traffic analyzer for Kubernetes providing real-time K8s protocol-level visibility, capturing and monitoring all traffic and payloads going in, out and across containers, pods, nodes and clusters. Inspired by Wireshark, purposely built for Kubernetes| | 456|electric-sql/pglite !2025-03-28112617|Lightweight Postgres packaged as WASM into a TypeScript library for the browser, Node.js, Bun and Deno from https://electric-sql.com| | 457|lightaime/camel !2025-03-281124441 |🐫 CAMEL: Communicative Agents for “Mind” Exploration of Large Scale Language Model Society| | 458|huggingface/lerobot !2025-03-281120184|🤗 LeRobot: State-of-the-art Machine Learning for Real-World Robotics in Pytorch| | 459|normal-computing/outlines !2025-03-28111657|Generative Model Programming| | 460|libretro/RetroArch !2025-03-28110701|Cross-platform, sophisticated frontend for the libretro API. Licensed GPLv3.| | 461|THUDM/CogVideo !2025-03-28110599|Text-to-video generation: CogVideoX (2024) and CogVideo (ICLR 2023)| | 462|bentoml/OpenLLM !2025-03-28110495|An open platform for operating large language models (LLMs) in production. Fine-tune, serve, deploy, and monitor any LLMs with ease.| | 463|vosen/ZLUDA !2025-03-28110429|CUDA on AMD GPUs| | 464|dair-ai/ML-Papers-of-the-Week !2025-03-28110304 |🔥Highlighting the top ML papers every week.| | 465|WordPress/gutenberg !2025-03-28110212|The Block Editor project for WordPress and beyond. Plugin is available from the official repository.| | 466|microsoft/data-formulator !2025-03-281099827|🪄 Create rich visualizations with AI| | 467|LibreTranslate/LibreTranslate !2025-03-28109887|Free and Open Source Machine Translation API. Self-hosted, offline capable and easy to setup.| | 468|block/goose !2025-03-281097737|an open-source, extensible AI agent that goes beyond code suggestions - install, execute, edit, and test with any LLM| | 469|getumbrel/llama-gpt !2025-03-28109553|A self-hosted, offline, ChatGPT-like chatbot. Powered by Llama 2. 100% private, with no data leaving your device.| | 470|HigherOrderCO/HVM !2025-03-28109182|A massively parallel, optimal functional runtime in Rust| | 471|databrickslabs/dolly !2025-03-2810812-3 | A large language model trained on the Databricks Machine Learning Platform| | 472|srush/GPU-Puzzles !2025-03-28108014|Solve puzzles. Learn CUDA.| | 473|Z3Prover/z3 !2025-03-28107952|The Z3 Theorem Prover| | 474|UFund-Me/Qbot !2025-03-281079313 |Qbot is an AI-oriented quantitative investment platform, which aims to realize the potential, empower AI technologies in quantitative investment| | 475|langchain-ai/langgraph !2025-03-281077336|| | 476|lz4/lz4 !2025-03-28107647|Extremely Fast Compression algorithm| | 477|magic-research/magic-animate !2025-03-28107160|MagicAnimate: Temporally Consistent Human Image Animation using Diffusion Model| | 478|PaperMC/Paper !2025-03-281071410|The most widely used, high performance Minecraft server that aims to fix gameplay and mechanics inconsistencies| | 479|getomni-ai/zerox !2025-03-281071015|Zero shot pdf OCR with gpt-4o-mini| |!green-up-arrow.svg 480|🔥NirDiamant/GenAIAgents !2025-03-2810693318|This repository provides tutorials and implementations for various Generative AI Agent techniques, from basic to advanced. It serves as a comprehensive guide for building intelligent, interactive AI systems.| |!red-down-arrow 481|Unstructured-IO/unstructured !2025-03-28106889|Open source libraries and APIs to build custom preprocessing pipelines for labeling, training, or production machine learning pipelines.| | 482|apache/thrift !2025-03-28106610|Apache Thrift| | 483| TheR1D/shellgpt !2025-03-28106097 | A command-line productivity tool powered by ChatGPT, will help you accomplish your tasks faster and more efficiently | | 484|TheRamU/Fay !2025-03-281060312 |Fay is a complete open source project that includes Fay controller and numeral models, which can be used in different applications such as virtual hosts, live promotion, numeral human interaction and so on| | 485|zyronon/douyin !2025-03-28105566|Vue3 + Pinia + Vite5 仿抖音，Vue 在移动端的最佳实践 . Imitate TikTok ，Vue Best practices on Mobile| | 486|THU-MIG/yolov10 !2025-03-28105485|YOLOv10: Real-Time End-to-End Object Detection| | 487|idootop/mi-gpt !2025-03-281052522|? Transform XiaoAi speaker into a personal voice assistant with ChatGPT and DouBao integration.| | 488|SakanaAI/AI-Scientist !2025-03-281051310|The AI Scientist: Towards Fully Automated Open-Ended Scientific Discovery 🧑‍🔬| | 489|szimek/sharedrop !2025-03-28105101|Easy P2P file transfer powered by WebRTC - inspired by Apple AirDrop| | 490|salesforce/LAVIS !2025-03-28103942 |LAVIS - A One-stop Library for Language-Vision Intelligence| | 491|aws/amazon-sagemaker-examples !2025-03-28103654|Example 📓 Jupyter notebooks that demonstrate how to build, train, and deploy machine learning models using 🧠 Amazon SageMaker.| | 492|artidoro/qlora !2025-03-28103402 |QLoRA: Efficient Finetuning of Quantized LLMs| | 493|lllyasviel/stable-diffusion-webui-forge !2025-03-281029314| a platform on top of Stable Diffusion WebUI (based on Gradio) to make development easier, optimize resource management, and speed up inference| | 494|NielsRogge/Transformers-Tutorials !2025-03-28102487|This repository contains demos I made with the Transformers library by HuggingFace.| | 495|kedro-org/kedro !2025-03-28102371|Kedro is a toolbox for production-ready data science. It uses software engineering best practices to help you create data engineering and data science pipelines that are reproducible, maintainable, and modular.| | 496| chathub-dev/chathub !2025-03-28102301 | All-in-one chatbot client | | 497|microsoft/promptflow !2025-03-28101612|Build high-quality LLM apps - from prototyping, testing to production deployment and monitoring.| | 498|mistralai/mistral-src !2025-03-28101372|Reference implementation of Mistral AI 7B v0.1 model.| | 499|burn-rs/burn !2025-03-28101183|Burn - A Flexible and Comprehensive Deep Learning Framework in Rust| | 500|AIGC-Audio/AudioGPT !2025-03-28101150 |AudioGPT: Understanding and Generating Speech, Music, Sound, and Talking Head| | 501|facebookresearch/dinov2 !2025-03-281011210 |PyTorch code and models for the DINOv2 self-supervised learning method.| | 502|RockChinQ/LangBot !2025-03-281008455|😎丰富生态、🧩支持扩展、🦄多模态 - 大模型原生即时通信机器人平台 🤖 | | 503|78/xiaozhi-esp32 !2025-03-281008180|Build your own AI friend| | 504|cumulo-autumn/StreamDiffusion !2025-03-28100761|StreamDiffusion: A Pipeline-Level Solution for Real-Time Interactive Generation| | 505|DataTalksClub/machine-learning-zoomcamp !2025-03-28100664|The code from the Machine Learning Bookcamp book and a free course based on the book| | 506|nerfstudio-project/nerfstudio !2025-03-28100343|A collaboration friendly studio for NeRFs| | 507|cupy/cupy !2025-03-28100344|NumPy & SciPy for GPU| | 508|NVIDIA/TensorRT-LLM !2025-03-281000823|TensorRT-LLM provides users with an easy-to-use Python API to define Large Language Models (LLMs) and build TensorRT engines that contain state-of-the-art optimizations to perform inference efficiently on NVIDIA GPUs. TensorRT-LLM also contains components to create Python and C++ runtimes that execute those TensorRT engines.| | 509|wasp-lang/open-saas !2025-03-2899665|A free, open-source SaaS app starter for React & Node.js with superpowers. Production-ready. Community-driven.| | 510|huggingface/text-generation-inference !2025-03-2899383|Large Language Model Text Generation Inference| | 511|jxnl/instructor !2025-03-2899224|structured outputs for llms| | 512|GoogleCloudPlatform/generative-ai !2025-03-2899086|Sample code and notebooks for Generative AI on Google Cloud| | 513|manticoresoftware/manticoresearch !2025-03-2898799|Easy to use open source fast database for search | | 514|langfuse/langfuse !2025-03-28985134|🪢 Open source LLM engineering platform. Observability, metrics, evals, prompt management, testing, prompt playground, datasets, LLM evaluations -- 🍊YC W23 🤖 integrate via Typescript, Python / Decorators, OpenAI, Langchain, LlamaIndex, Litellm, Instructor, Mistral, Perplexity, Claude, Gemini, Vertex| | 515|keephq/keep !2025-03-2897949|The open-source alert management and AIOps platform| | 516|sashabaranov/go-openai !2025-03-2897843|OpenAI ChatGPT, GPT-3, GPT-4, DALL·E, Whisper API wrapper for Go| | 517|autowarefoundation/autoware !2025-03-2897766|Autoware - the world's leading open-source software project for autonomous driving| | 518|anthropics/courses !2025-03-2897269|Anthropic's educational courses| | 519|popcorn-official/popcorn-desktop !2025-03-2896853|Popcorn Time is a multi-platform, free software BitTorrent client that includes an integrated media player ( Windows / Mac / Linux ) A Butter-Project Fork| | 520|getmaxun/maxun !2025-03-28968515|🔥 Open-source no-code web data extraction platform. Turn websites to APIs and spreadsheets with no-code robots in minutes! [In Beta]| | 521|wandb/wandb !2025-03-2896763|🔥 A tool for visualizing and tracking your machine learning experiments. This repo contains the CLI and Python API.| | 522|karpathy/minbpe !2025-03-2895353|Minimal, clean, code for the Byte Pair Encoding (BPE) algorithm commonly used in LLM tokenization.| | 523|bigscience-workshop/petals !2025-03-2895142|🌸 Run large language models at home, BitTorrent-style. Fine-tuning and inference up to 10x faster than offloading| | 524|OthersideAI/self-operating-computer !2025-03-2894931|A framework to enable multimodal models to operate a computer.| | 525|mshumer/gpt-prompt-engineer !2025-03-2894911|| | 526| BloopAI/bloop !2025-03-2894710 | A fast code search engine written in Rust| | 527|BlinkDL/ChatRWKV !2025-03-289467-1 |ChatRWKV is like ChatGPT but powered by RWKV (100% RNN) language model, and open source.| | 528|timlrx/tailwind-nextjs-starter-blog !2025-03-2894677|This is a Next.js, Tailwind CSS blogging starter template. Comes out of the box configured with the latest technologies to make technical writing a breeze. Easily configurable and customizable. Perfect as a replacement to existing Jekyll and Hugo individual blogs.| | 529|google/benchmark !2025-03-2893634|A microbenchmark support library| | 530|facebookresearch/nougat !2025-03-2893603|Implementation of Nougat Neural Optical Understanding for Academic Documents| | 531|modelscope/facechain !2025-03-2893536|FaceChain is a deep-learning toolchain for generating your Digital-Twin.| | 532|DrewThomasson/ebook2audiobook !2025-03-2893388|Convert ebooks to audiobooks with chapters and metadata using dynamic AI models and voice cloning. Supports 1,107+ languages!| | 533|RayTracing/raytracing.github.io !2025-03-2893035|Main Web Site (Online Books)| | 534|QwenLM/Qwen2.5-VL !2025-03-28930249|Qwen2.5-VL is the multimodal large language model series developed by Qwen team, Alibaba Cloud.| | 535|WongKinYiu/yolov9 !2025-03-2892201|Implementation of paper - YOLOv9: Learning What You Want to Learn Using Programmable Gradient Information| | 536|alibaba-damo-academy/FunASR !2025-03-28920222|A Fundamental End-to-End Speech Recognition Toolkit and Open Source SOTA Pretrained Models.| | 537|Visualize-ML/Book4Power-of-Matrix !2025-03-2891931|Book4 'Power of Matrix' | | 538|dice2o/BingGPT !2025-03-289185-1 |Desktop application of new Bing's AI-powered chat (Windows, macOS and Linux)| | 539|browserbase/stagehand !2025-03-28917621|An AI web browsing framework focused on simplicity and extensibility.| | 540|FlagOpen/FlagEmbedding !2025-03-28914111|Dense Retrieval and Retrieval-augmented LLMs| | 541|Const-me/Whisper !2025-03-2890979|High-performance GPGPU inference of OpenAI's Whisper automatic speech recognition (ASR) model| | 542|lucidrains/denoising-diffusion-pytorch !2025-03-2890942|Implementation of Denoising Diffusion Probabilistic Model in Pytorch| | 543|Chainlit/chainlit !2025-03-28904422|Build Conversational AI in minutes ⚡️| | 544|togethercomputer/OpenChatKit !2025-03-2890160 |OpenChatKit provides a powerful, open-source base to create both specialized and general purpose chatbots for various applications| | 545|Stability-AI/StableStudio !2025-03-2889631 |Community interface for generative AI| | 546|voicepaw/so-vits-svc-fork !2025-03-2889482 |so-vits-svc fork with realtime support, improved interface and more features.| | 547|pymc-devs/pymc !2025-03-2889413|Bayesian Modeling and Probabilistic Programming in Python| | 548|espnet/espnet !2025-03-2889302|End-to-End Speech Processing Toolkit| | 549|kedacore/keda !2025-03-2888991|KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes| | 550|open-mmlab/Amphion !2025-03-28886911|Amphion (/æmˈfaɪən/) is a toolkit for Audio, Music, and Speech Generation. Its purpose is to support reproducible research and help junior researchers and engineers get started in the field of audio, music, and speech generation research and development.| | 551|gorse-io/gorse !2025-03-2888451|Gorse open source recommender system engine| | 552|adams549659584/go-proxy-bingai !2025-03-288768-1 |A Microsoft New Bing demo site built with Vue3 and Go, providing a consistent UI experience, supporting ChatGPT prompts, and accessible within China| | 553|open-mmlab/mmsegmentation !2025-03-2887513|OpenMMLab Semantic Segmentation Toolbox and Benchmark.| | 554|bytedance/monolith !2025-03-2887223|ByteDance's Recommendation System| | 555|LouisShark/chatgptsystemprompt !2025-03-2887216|store all agent's system prompt| | 556|brexhq/prompt-engineering !2025-03-2887080 |Tips and tricks for working with Large Language Models like OpenAI's GPT-4.| | 557|erincatto/box2d !2025-03-2886841|Box2D is a 2D physics engine for games| | 558|🔥microsoft/ai-agents-for-beginners !2025-03-288669323|10 Lessons to Get Started Building AI Agents| | 559|nashsu/FreeAskInternet !2025-03-2886102|FreeAskInternet is a completely free, private and locally running search aggregator & answer generate using LLM, without GPU needed. The user can ask a question and the system will make a multi engine search and combine the search result to the ChatGPT3.5 LLM and generate the answer based on search results.| | 560|goldmansachs/gs-quant !2025-03-2885981|Python toolkit for quantitative finance| | 561|srbhr/Resume-Matcher !2025-03-2885800|Open Source Free ATS Tool to compare Resumes with Job Descriptions and create a score to rank them.| | 562|facebookresearch/ImageBind !2025-03-2885681 |ImageBind One Embedding Space to Bind Them All| | 563|ashawkey/stable-dreamfusion !2025-03-2885481 |A pytorch implementation of text-to-3D dreamfusion, powered by stable diffusion.| | 564|meetecho/janus-gateway !2025-03-2885232|Janus WebRTC Server| | 565|google/magika !2025-03-2885003|Detect file content types with deep learning| | 566|huggingface/chat-ui !2025-03-2884871 |Open source codebase powering the HuggingChat app| | 567|EleutherAI/lm-evaluation-harness !2025-03-28843012|A framework for few-shot evaluation of autoregressive language models.| | 568|jina-ai/reader !2025-03-2884089|Convert any URL to an LLM-friendly input with a simple prefix https://r.jina.ai/| | 569|microsoft/TypeChat !2025-03-288406-1|TypeChat is a library that makes it easy to build natural language interfaces using types.| | 570|thuml/Time-Series-Library !2025-03-28839715|A Library for Advanced Deep Time Series Models.| | 571|OptimalScale/LMFlow !2025-03-2883882|An Extensible Toolkit for Finetuning and Inference of Large Foundation Models. Large Model for All.| | 572|baptisteArno/typebot.io !2025-03-2883845|💬 Typebot is a powerful chatbot builder that you can self-host.| | 573|jzhang38/TinyLlama !2025-03-2883504|The TinyLlama project is an open endeavor to pretrain a 1.1B Llama model on 3 trillion tokens.| | 574|fishaudio/Bert-VITS2 !2025-03-2883472|vits2 backbone with multilingual-bert| | 575|OpenBMB/XAgent !2025-03-2882683|An Autonomous LLM Agent for Complex Task Solving| | 576|Acly/krita-ai-diffusion !2025-03-2882387|Streamlined interface for generating images with AI in Krita. Inpaint and outpaint with optional text prompt, no tweaking required.| | 577|jasonppy/VoiceCraft !2025-03-2882151|Zero-Shot Speech Editing and Text-to-Speech in the Wild| | 578|SJTU-IPADS/PowerInfer !2025-03-2881693|High-speed Large Language Model Serving on PCs with Consumer-grade GPUs| | 579|modelscope/DiffSynth-Studio !2025-03-28814713|Enjoy the magic of Diffusion models!| | 580|o3de/o3de !2025-03-2881443|Open 3D Engine (O3DE) is an Apache 2.0-licensed multi-platform 3D engine that enables developers and content creators to build AAA games, cinema-quality 3D worlds, and high-fidelity simulations without any fees or commercial obligations.| | 581|zmh-program/chatnio !2025-03-2881325|🚀 Next Generation AI One-Stop Internationalization Solution. 🚀 下一代 AI 一站式 B/C 端解决方案，支持 OpenAI，Midjourney，Claude，讯飞星火，Stable Diffusion，DALL·E，ChatGLM，通义千问，腾讯混元，360 智脑，百川 AI，火山方舟，新必应，Gemini，Moonshot 等模型，支持对话分享，自定义预设，云端同步，模型市场，支持弹性计费和订阅计划模式，支持图片解析，支持联网搜索，支持模型缓存，丰富美观的后台管理与仪表盘数据统计。| | 582|leptonai/searchwithlepton !2025-03-2880632|Building a quick conversation-based search demo with Lepton AI.| | 583|sebastianstarke/AI4Animation !2025-03-2880620|Bringing Characters to Life with Computer Brains in Unity| | 584|wangrongding/wechat-bot !2025-03-2880528|🤖一个基于 WeChaty 结合 DeepSeek / ChatGPT / Kimi / 讯飞等Ai服务实现的微信机器人 ，可以用来帮助你自动回复微信消息，或者管理微信群/好友，检测僵尸粉等...| | 585|openvinotoolkit/openvino !2025-03-2880528|OpenVINO™ is an open-source toolkit for optimizing and deploying AI inference| | 586|steven2358/awesome-generative-ai !2025-03-28802610|A curated list of modern Generative Artificial Intelligence projects and services| | 587|adam-maj/tiny-gpu !2025-03-2880234|A minimal GPU design in Verilog to learn how GPUs work from the ground up| | 588| anse-app/chatgpt-demo !2025-03-2880180 | A demo repo based on OpenAI API (gpt-3.5-turbo) | | 589| acheong08/EdgeGPT !2025-03-288015-1 |Reverse engineered API of Microsoft's Bing Chat | | 590|ai-collection/ai-collection !2025-03-2879994 |The Generative AI Landscape - A Collection of Awesome Generative AI Applications| | 591|GreyDGL/PentestGPT !2025-03-2879953 |A GPT-empowered penetration testing tool| | 592|delta-io/delta !2025-03-2879112|An open-source storage framework that enables building a Lakehouse architecture with compute engines including Spark, PrestoDB, Flink, Trino, and Hive and APIs| | 593|dataelement/bisheng !2025-03-2879085|Bisheng is an open LLM devops platform for next generation AI applications.| | 594|e2b-dev/e2b !2025-03-2878447 |Vercel for AI agents. We help developers to build, deploy, and monitor AI agents. Focusing on specialized AI agents that build software for you - your personal software developers.| | 595|01-ai/Yi !2025-03-2878311|A series of large language models trained from scratch by developers @01-ai| | 596|Plachtaa/VALL-E-X !2025-03-287830-1|An open source implementation of Microsoft's VALL-E X zero-shot TTS model. The demo is available at https://plachtaa.github.io| | 597|abhishekkrthakur/approachingalmost !2025-03-2878204|Approaching (Almost) Any Machine Learning Problem| | 598|pydantic/pydantic-ai !2025-03-28781041|Agent Framework / shim to use Pydantic with LLMs| | 599|rany2/edge-tts !2025-03-2877901|Use Microsoft Edge's online text-to-speech service from Python WITHOUT needing Microsoft Edge or Windows or an API key| | 600|CASIA-IVA-Lab/FastSAM !2025-03-2877881|Fast Segment Anything| | 601|netease-youdao/EmotiVoice !2025-03-2877817|EmotiVoice 😊: a Multi-Voice and Prompt-Controlled TTS Engine| | 602|lllyasviel/IC-Light !2025-03-2877804|More relighting!| | 603|kroma-network/tachyon !2025-03-287774-1|Modular ZK(Zero Knowledge) backend accelerated by GPU| | 604|deep-floyd/IF !2025-03-2877731 |A novel state-of-the-art open-source text-to-image model with a high degree of photorealism and language understanding| | 605|oumi-ai/oumi !2025-03-2877705|Everything you need to build state-of-the-art foundation models, end-to-end.| | 606|reorproject/reor !2025-03-2877681|AI note-taking app that runs models locally.| | 607|lightpanda-io/browser !2025-03-28775813|Lightpanda: the headless browser designed for AI and automation| | 608|xiangsx/gpt4free-ts !2025-03-287755-1|Providing a free OpenAI GPT-4 API ! This is a replication project for the typescript version of xtekky/gpt4free| | 609|IDEA-Research/GroundingDINO !2025-03-28773311|Official implementation of the paper "Grounding DINO: Marrying DINO with Grounded Pre-Training for Open-Set Object Detection"| | 610|bunkerity/bunkerweb !2025-03-2877326|🛡️ Make your web services secure by default !| | 611|vikhyat/moondream !2025-03-2877057|tiny vision language model| | 612|firmai/financial-machine-learning !2025-03-287703-1|A curated list of practical financial machine learning tools and applications.| | 613|n8n-io/self-hosted-ai-starter-kit !2025-03-28765121|The Self-hosted AI Starter Kit is an open-source template that quickly sets up a local AI environment. Curated by n8n, it provides essential tools for creating secure, self-hosted AI workflows.| | 614|intel-analytics/ipex-llm !2025-03-2876507|Accelerate local LLM inference and finetuning (LLaMA, Mistral, ChatGLM, Qwen, Baichuan, Mixtral, Gemma, etc.) on Intel CPU and GPU (e.g., local PC with iGPU, discrete GPU such as Arc, Flex and Max). A PyTorch LLM library that seamlessly integrates with llama.cpp, HuggingFace, LangChain, LlamaIndex, DeepSpeed, vLLM, FastChat, ModelScope, etc.| | 615|jrouwe/JoltPhysics !2025-03-28764510|A multi core friendly rigid body physics and collision detection library. Written in C++. Suitable for games and VR applications. Used by Horizon Forbidden West.| | 616|THUDM/CodeGeeX2 !2025-03-2876270|CodeGeeX2: A More Powerful Multilingual Code Generation Model| | 617|meta-llama/llama-stack !2025-03-2875866|Composable building blocks to build Llama Apps| | 618|sweepai/sweep !2025-03-287530-1|Sweep is an AI junior developer| | 619|lllyasviel/Omost !2025-03-2875301|Your image is almost there!| | 620|ahmedbahaaeldin/From-0-to-Research-Scientist-resources-guide !2025-03-2875050|Detailed and tailored guide for undergraduate students or anybody want to dig deep into the field of AI with solid foundation.| | 621|dair-ai/ML-Papers-Explained !2025-03-2875050|Explanation to key concepts in ML| | 622|zaidmukaddam/scira !2025-03-28750110|Scira (Formerly MiniPerplx) is a minimalistic AI-powered search engine that helps you find information on the internet. Powered by Vercel AI SDK! Search with models like Grok 2.0.| | 623|Portkey-AI/gateway !2025-03-28749416|A Blazing Fast AI Gateway. Route to 100+ LLMs with 1 fast & friendly API.| | 624|web-infra-dev/midscene !2025-03-28748729|An AI-powered automation SDK can control the page, perform assertions, and extract data in JSON format using natural language.| | 625|zilliztech/GPTCache !2025-03-2874801 |GPTCache is a library for creating semantic cache to store responses from LLM queries.| | 626|niedev/RTranslator !2025-03-2874742|RTranslator is the world's first open source real-time translation app.| |!green-up-arrow.svg 627|roboflow/notebooks !2025-03-2874666|Examples and tutorials on using SOTA computer vision models and techniques. Learn everything from old-school ResNet, through YOLO and object-detection transformers like DETR, to the latest models like Grounding DINO and SAM.| |!red-down-arrow 628|openlm-research/openllama !2025-03-2874652|OpenLLaMA, a permissively licensed open source reproduction of Meta AI’s LLaMA 7B trained on the RedPajama dataset| | 629|LiheYoung/Depth-Anything !2025-03-2874155|Depth Anything: Unleashing the Power of Large-Scale Unlabeled Data| | 630|enso-org/enso !2025-03-2874040|Hybrid visual and textual functional programming.| | 631|bigcode-project/starcoder !2025-03-287401-1 |Home of StarCoder: fine-tuning & inference!| | 632|git-ecosystem/git-credential-manager !2025-03-2873975|Secure, cross-platform Git credential storage with authentication to GitHub, Azure Repos, and other popular Git hosting services.| | 633|OpenGVLab/InternVL !2025-03-2873634|[CVPR 2024 Oral] InternVL Family: A Pioneering Open-Source Alternative to GPT-4V. 接近GPT-4V表现的可商用开源模型| | 634|WooooDyy/LLM-Agent-Paper-List !2025-03-2873551|The paper list of the 86-page paper "The Rise and Potential of Large Language Model Based Agents: A Survey" by Zhiheng Xi et al.| | 635|lencx/Noi !2025-03-2873157|🦄 AI + Tools + Plugins + Community| | 636|udlbook/udlbook !2025-03-2873075|Understanding Deep Learning - Simon J.D. Prince| | 637|OpenBMB/MiniCPM !2025-03-2872841|MiniCPM-2B: An end-side LLM outperforms Llama2-13B.| | 638|jaywalnut310/vits !2025-03-2872815 |VITS: Conditional Variational Autoencoder with Adversarial Learning for End-to-End Text-to-Speech| | 639|xorbitsai/inference !2025-03-28727528|Replace OpenAI GPT with another LLM in your app by changing a single line of code. Xinference gives you the freedom to use any LLM you need. With Xinference, you're empowered to run inference with any open-source language models, speech recognition models, and multimodal models, whether in the cloud, on-premises, or even on your laptop.| | 640|PWhiddy/PokemonRedExperiments !2025-03-2872492|Playing Pokemon Red with Reinforcement Learning| | 641|Canner/WrenAI !2025-03-28723213|🤖 Open-source AI Agent that empowers data-driven teams to chat with their data to generate Text-to-SQL, charts, spreadsheets, reports, and BI. 📈📊📋🧑‍💻| | 642|miurla/morphic !2025-03-2872258|An AI-powered answer engine with a generative UI| | 643|ml-explore/mlx-examples !2025-03-2872168|Examples in the MLX framework| | 644|PKU-YuanGroup/ChatLaw !2025-03-2872010|Chinese Legal Large Model| | 645|NVIDIA/cutlass !2025-03-2871883|CUDA Templates for Linear Algebra Subroutines| | 646|FoundationVision/VAR !2025-03-28717444|[GPT beats diffusion🔥] [scaling laws in visual generation📈] Official impl. of "Visual Autoregressive Modeling: Scalable Image Generation via Next-Scale Prediction"| | 647|ymcui/Chinese-LLaMA-Alpaca-2 !2025-03-2871561|Chinese LLaMA-2 & Alpaca-2 LLMs| | 648|nadermx/backgroundremover !2025-03-2871514 |Background Remover lets you Remove Background from images and video using AI with a simple command line interface that is free and open source.| | 649|onuratakan/gpt-computer-assistant !2025-03-28714514|gpt-4o for windows, macos and ubuntu| | 650|graviraja/MLOps-Basics !2025-03-2871326|| | 651|Future-House/paper-qa !2025-03-287118-1|High accuracy RAG for answering questions from scientific documents with citations| | 652|open-mmlab/mmagic !2025-03-2871102 |OpenMMLab Multimodal Advanced, Generative, and Intelligent Creation Toolbox| | 653|bhaskatripathi/pdfGPT !2025-03-2870941 |PDF GPT allows you to chat with the contents of your PDF file by using GPT capabilities. The only open source solution to turn your pdf files in a chatbot!| | 654|ollama/ollama-python !2025-03-28709117|Ollama Python library| | 655|facebookresearch/DiT !2025-03-2870376|Official PyTorch Implementation of "Scalable Diffusion Models with Transformers"| | 656|geekyutao/Inpaint-Anything !2025-03-2870262 |Inpaint anything using Segment Anything and inpainting models.| | 657|AbdullahAlfaraj/Auto-Photoshop-StableDiffusion-Plugin !2025-03-2870160 |A user-friendly plug-in that makes it easy to generate stable diffusion images inside Photoshop using Automatic1111-sd-webui as a backend.| | 658|apple/corenet !2025-03-2869990|CoreNet: A library for training deep neural networks| | 659|openstatusHQ/openstatus !2025-03-2869926|🏓 The open-source synthetic monitoring platform 🏓| | 660|weaviate/Verba !2025-03-2869772|Retrieval Augmented Generation (RAG) chatbot powered by Weaviate| | 661|meshery/meshery !2025-03-2869630|Meshery, the cloud native manager| | 662|OpenTalker/video-retalking !2025-03-2869530|[SIGGRAPH Asia 2022] VideoReTalking: Audio-based Lip Synchronization for Talking Head Video Editing In the Wild| | 663|digitalinnovationone/dio-lab-open-source !2025-03-28689013|Repositório do lab "Contribuindo em um Projeto Open Source no GitHub" da Digital Innovation One.| | 664|jianchang512/ChatTTS-ui !2025-03-2868842|一个简单的本地网页界面，直接使用ChatTTS将文字合成为语音，同时支持对外提供API接口。| | 665|patchy631/ai-engineering-hub !2025-03-28686434|In-depth tutorials on LLMs, RAGs and real-world AI agent applications.| | 666|gunnarmorling/1brc !2025-03-2868512|1️⃣🐝🏎️ The One Billion Row Challenge -- A fun exploration of how quickly 1B rows from a text file can be aggregated with Java| | 667|Azure-Samples/azure-search-openai-demo !2025-03-2868482 |A sample app for the Retrieval-Augmented Generation pattern running in Azure, using Azure Cognitive Search for retrieval and Azure OpenAI large language models to power ChatGPT-style and Q&A experiences.| | 668|mit-han-lab/streaming-llm !2025-03-2868382|Efficient Streaming Language Models with Attention Sinks| | 669|InternLM/InternLM !2025-03-2868352|InternLM has open-sourced a 7 billion parameter base model, a chat model tailored for practical scenarios and the training system.| | 670|dependency-check/DependencyCheck !2025-03-2868191|OWASP dependency-check is a software composition analysis utility that detects publicly disclosed vulnerabilities in application dependencies.| | 671|Soulter/AstrBot !2025-03-28678643|✨易上手的多平台 LLM 聊天机器人及开发框架✨。支持 QQ、QQ频道、Telegram、微信平台(Gewechat, 企业微信)、内置 Web Chat，OpenAI GPT、DeepSeek、Ollama、Llama、GLM、Gemini、OneAPI、LLMTuner，支持 LLM Agent 插件开发，可视化面板。一键部署。支持 Dify 工作流、代码执行器、Whisper 语音转文字。| | 672|react-native-webview/react-native-webview !2025-03-2867792|React Native Cross-Platform WebView| | 673|modelscope/agentscope !2025-03-28676916|Start building LLM-empowered multi-agent applications in an easier way.| | 674|mylxsw/aidea !2025-03-2867381|AIdea is a versatile app that supports GPT and domestic large language models，also supports "Stable Diffusion" text-to-image generation, image-to-image generation, SDXL 1.0, super-resolution, and image colorization| | 675|langchain-ai/ollama-deep-researcher !2025-03-28668635|Fully local web research and report writing assistant| | 676|threestudio-project/threestudio !2025-03-2866653|A unified framework for 3D content generation.| | 677|gaomingqi/Track-Anything !2025-03-2866631 |A flexible and interactive tool for video object tracking and segmentation, based on Segment Anything, XMem, and E2FGVI.| | 678|spdustin/ChatGPT-AutoExpert !2025-03-2866570|🚀🧠💬 Supercharged Custom Instructions for ChatGPT (non-coding) and ChatGPT Advanced Data Analysis (coding).| | 679|HariSekhon/DevOps-Bash-tools !2025-03-2866463|1000+ DevOps Bash Scripts - AWS, GCP, Kubernetes, Docker, CI/CD, APIs, SQL, PostgreSQL, MySQL, Hive, Impala, Kafka, Hadoop, Jenkins, GitHub, GitLab, BitBucket, Azure DevOps, TeamCity, Spotify, MP3, LDAP, Code/Build Linting, pkg mgmt for Linux, Mac, Python, Perl, Ruby, NodeJS, Golang, Advanced dotfiles: .bashrc, .vimrc, .gitconfig, .screenrc, tmux..| | 680|modelscope/swift !2025-03-28661530|ms-swift: Use PEFT or Full-parameter to finetune 200+ LLMs or 15+ MLLMs| | 681|langchain-ai/opengpts !2025-03-2866080|This is an open source effort to create a similar experience to OpenAI's GPTs and Assistants API| | 682| yihong0618/xiaogpt !2025-03-2865131 | Play ChatGPT with xiaomi ai speaker | | 683| civitai/civitai !2025-03-2865111 | Build a platform where people can share their stable diffusion models | | 684|KoljaB/RealtimeSTT !2025-03-28649513|A robust, efficient, low-latency speech-to-text library with advanced voice activity detection, wake word activation and instant transcription.| | 685|qunash/chatgpt-advanced !2025-03-2864910 | A browser extension that augments your ChatGPT prompts with web results.| | 686|Licoy/ChatGPT-Midjourney !2025-03-2864850|🎨 Own your own ChatGPT+Midjourney web service with one click| | 687|friuns2/BlackFriday-GPTs-Prompts !2025-03-2864744|List of free GPTs that doesn't require plus subscription| | 688|PixarAnimationStudios/OpenUSD !2025-03-2864700|Universal Scene Description| | 689|linyiLYi/street-fighter-ai !2025-03-2864630 |This is an AI agent for Street Fighter II Champion Edition.| | 690|run-llama/rags !2025-03-2864380|Build ChatGPT over your data, all with natural language| | 691|frdel/agent-zero !2025-03-2864154|Agent Zero AI framework| | 692|microsoft/DeepSpeedExamples !2025-03-2863911 |Example models using DeepSpeed| | 693|k8sgpt-ai/k8sgpt !2025-03-2863882|Giving Kubernetes Superpowers to everyone| | 694|open-metadata/OpenMetadata !2025-03-2863514|OpenMetadata is a unified platform for discovery, observability, and governance powered by a central metadata repository, in-depth lineage, and seamless team collaboration.| | 695|google/gemma.cpp !2025-03-2863163|lightweight, standalone C++ inference engine for Google's Gemma models.| | 696|RayVentura/ShortGPT !2025-03-286314-1|🚀🎬 ShortGPT - An experimental AI framework for automated short/video content creation. Enables creators to rapidly produce, manage, and deliver content using AI and automation.| | 697|openai/consistencymodels !2025-03-2862940 |Official repo for consistency models.| | 698|yangjianxin1/Firefly !2025-03-2862924|Firefly: Chinese conversational large language model (full-scale fine-tuning + QLoRA), supporting fine-tuning of Llma2, Llama, Baichuan, InternLM, Ziya, Bloom, and other large models| | 699|enricoros/big-AGI !2025-03-2862665|Generative AI suite powered by state-of-the-art models and providing advanced AI/AGI functions. It features AI personas, AGI functions, multi-model chats, text-to-image, voice, response streaming, code highlighting and execution, PDF import, presets for developers, much more. Deploy on-prem or in the cloud.| | 700|aptos-labs/aptos-core !2025-03-2862633|Aptos is a layer 1 blockchain built to support the widespread use of blockchain through better technology and user experience.| | 701|wenda-LLM/wenda !2025-03-286262-1 |Wenda: An LLM invocation platform. Its objective is to achieve efficient content generation tailored to specific environments while considering the limited computing resources of individuals and small businesses, as well as knowledge security and privacy concerns| | 702|Project-MONAI/MONAI !2025-03-2862603|AI Toolkit for Healthcare Imaging| | 703|HVision-NKU/StoryDiffusion !2025-03-2862470|Create Magic Story!| | 704|deepseek-ai/DeepSeek-LLM !2025-03-2862463|DeepSeek LLM: Let there be answers| | 705|Tohrusky/Final2x !2025-03-2862393|2^x Image Super-Resolution| | 706|OpenSPG/KAG !2025-03-28619611|KAG is a logical form-guided reasoning and retrieval framework based on OpenSPG engine and LLMs. It is used to build logical reasoning and factual Q&A solutions for professional domain knowledge bases. It can effectively overcome the shortcomings of the traditional RAG vector similarity calculation model.| | 707|Moonvy/OpenPromptStudio !2025-03-2861861 |AIGC Hint Word Visualization Editor| | 708|levihsu/OOTDiffusion !2025-03-2861761|Official implementation of OOTDiffusion| | 709|tmc/langchaingo !2025-03-2861729|LangChain for Go, the easiest way to write LLM-based programs in Go| | 710|vladmandic/automatic !2025-03-2861374|SD.Next: Advanced Implementation of Stable Diffusion and other Diffusion-based generative image models| | 711|clovaai/donut !2025-03-2861231 |Official Implementation of OCR-free Document Understanding Transformer (Donut) and Synthetic Document Generator (SynthDoG), ECCV 2022| | 712|Shaunwei/RealChar !2025-03-286121-1|🎙️🤖Create, Customize and Talk to your AI Character/Companion in Realtime(All in One Codebase!). Have a natural seamless conversation with AI everywhere(mobile, web and terminal) using LLM OpenAI GPT3.5/4, Anthropic Claude2, Chroma Vector DB, Whisper Speech2Text, ElevenLabs Text2Speech🎙️🤖| | 713|microsoft/TinyTroupe !2025-03-2861142|LLM-powered multiagent persona simulation for imagination enhancement and business insights.| | 714| rustformers/llm !2025-03-2861010 | Run inference for Large Language Models on CPU, with Rust| | 715|firebase/firebase-ios-sdk !2025-03-2860950|Firebase SDK for Apple App Development| | 716|vespa-engine/vespa !2025-03-2860824|The open big data serving engine. https://vespa.ai| | 717|n4ze3m/page-assist !2025-03-28607610|Use your locally running AI models to assist you in your web browsing| | 718|Dooy/chatgpt-web-midjourney-proxy !2025-03-2860646|chatgpt web, midjourney, gpts,tts, whisper 一套ui全搞定| | 719|ethereum-optimism/optimism !2025-03-2860213|Optimism is Ethereum, scaled.| | 720|sczhou/ProPainter !2025-03-2859971|[ICCV 2023] ProPainter: Improving Propagation and Transformer for Video Inpainting| | 721|MineDojo/Voyager !2025-03-2859951 |An Open-Ended Embodied Agent with Large Language Models| | 722|lavague-ai/LaVague !2025-03-2859800|Automate automation with Large Action Model framework| | 723|SevaSk/ecoute !2025-03-2859770 |Ecoute is a live transcription tool that provides real-time transcripts for both the user's microphone input (You) and the user's speakers output (Speaker) in a textbox. It also generates a suggested response using OpenAI's GPT-3.5 for the user to say based on the live transcription of the conversation.| | 724|google/mesop !2025-03-2859661|| | 725|pengxiao-song/LaWGPT !2025-03-2859542 |Repo for LaWGPT, Chinese-Llama tuned with Chinese Legal knowledge| | 726|fr0gger/Awesome-GPT-Agents !2025-03-2859434|A curated list of GPT agents for cybersecurity| | 727|google-deepmind/graphcast !2025-03-2859412|| | 728|comet-ml/opik !2025-03-28594126|Open-source end-to-end LLM Development Platform| | 729|SciPhi-AI/R2R !2025-03-28594033|A framework for rapid development and deployment of production-ready RAG systems| | 730|SkalskiP/courses !2025-03-2859272 |This repository is a curated collection of links to various courses and resources about Artificial Intelligence (AI)| | 731|QuivrHQ/MegaParse !2025-03-2859122|File Parser optimised for LLM Ingestion with no loss 🧠 Parse PDFs, Docx, PPTx in a format that is ideal for LLMs.| | 732|pytorch-labs/gpt-fast !2025-03-2858971|Simple and efficient pytorch-native transformer text generation in !2025-03-2858886|Curated list of chatgpt prompts from the top-rated GPTs in the GPTs Store. Prompt Engineering, prompt attack & prompt protect. Advanced Prompt Engineering papers.| | 734|nilsherzig/LLocalSearch !2025-03-2858852|LLocalSearch is a completely locally running search aggregator using LLM Agents. The user can ask a question and the system will use a chain of LLMs to find the answer. The user can see the progress of the agents and the final answer. No OpenAI or Google API keys are needed.| | 735|kuafuai/DevOpsGPT !2025-03-285874-2|Multi agent system for AI-driven software development. Convert natural language requirements into working software. Supports any development language and extends the existing base code.| | 736|myshell-ai/MeloTTS !2025-03-2858486|High-quality multi-lingual text-to-speech library by MyShell.ai. Support English, Spanish, French, Chinese, Japanese and Korean.| | 737|OpenGVLab/LLaMA-Adapter !2025-03-2858421 |Fine-tuning LLaMA to follow Instructions within 1 Hour and 1.2M Parameters| | 738|volcengine/verl !2025-03-28582563|veRL: Volcano Engine Reinforcement Learning for LLM| | 739|a16z-infra/companion-app !2025-03-2858171|AI companions with memory: a lightweight stack to create and host your own AI companions| | 740|HumanAIGC/OutfitAnyone !2025-03-285816-1|Outfit Anyone: Ultra-high quality virtual try-on for Any Clothing and Any Person| | 741|josStorer/RWKV-Runner !2025-03-2857472|A RWKV management and startup tool, full automation, only 8MB. And provides an interface compatible with the OpenAI API. RWKV is a large language model that is fully open source and available for commercial use.| | 742|648540858/wvp-GB28181-pro !2025-03-2857414|WEB VIDEO PLATFORM是一个基于GB28181-2016标准实现的网络视频平台，支持NAT穿透，支持海康、大华、宇视等品牌的IPC、NVR、DVR接入。支持国标级联，支持rtsp/rtmp等视频流转发到国标平台，支持rtsp/rtmp等推流转发到国标平台。| | 743|ToonCrafter/ToonCrafter !2025-03-2857345|a research paper for generative cartoon interpolation| | 744|PawanOsman/ChatGPT !2025-03-2857191|OpenAI API Free Reverse Proxy| | 745|apache/hudi !2025-03-2857091|Upserts, Deletes And Incremental Processing on Big Data.| | 746| nsarrazin/serge !2025-03-2857081 | A web interface for chatting with Alpaca through llama.cpp. Fully dockerized, with an easy to use API| | 747|homanp/superagent !2025-03-2857021|🥷 Superagent - Build, deploy, and manage LLM-powered agents| | 748|ramonvc/freegpt-webui !2025-03-2856910|GPT 3.5/4 with a Chat Web UI. No API key is required.| | 749|baichuan-inc/baichuan-7B !2025-03-2856901|A large-scale 7B pretraining language model developed by BaiChuan-Inc.| | 750|Azure/azure-sdk-for-net !2025-03-2856792|This repository is for active development of the Azure SDK for .NET. For consumers of the SDK we recommend visiting our public developer docs at https://learn.microsoft.com/dotnet/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-net.| | 751|mnotgod96/AppAgent !2025-03-2856643|AppAgent: Multimodal Agents as Smartphone Users, an LLM-based multimodal agent framework designed to operate smartphone apps.| | 752|microsoft/TaskWeaver !2025-03-2856243|A code-first agent framework for seamlessly planning and executing data analytics tasks.| | 753| yetone/bob-plugin-openai-translator !2025-03-285600-1 | A Bob Plugin base ChatGPT API | | 754|PrefectHQ/marvin !2025-03-2855840 |A batteries-included library for building AI-powered software| | 755|microsoft/promptbase !2025-03-2855832|All things prompt engineering| | 756|fullstackhero/dotnet-starter-kit !2025-03-2855560|Production Grade Cloud-Ready .NET 8 Starter Kit (Web API + Blazor Client) with Multitenancy Support, and Clean/Modular Architecture that saves roughly 200+ Development Hours! All Batteries Included.| | 757|deepseek-ai/DeepSeek-Coder-V2 !2025-03-2855435|DeepSeek-Coder-V2: Breaking the Barrier of Closed-Source Models in Code Intelligence| | 758|aiwaves-cn/agents !2025-03-2855391|An Open-source Framework for Autonomous Language Agents| | 759|microsoft/Mastering-GitHub-Copilot-for-Paired-Programming !2025-03-2855158|A 6 Lesson course teaching everything you need to know about harnessing GitHub Copilot and an AI Paired Programing resource.| | 760|allenai/OLMo !2025-03-2854506|Modeling, training, eval, and inference code for OLMo| | 761|apify/crawlee-python !2025-03-2854493|Crawlee—A web scraping and browser automation library for Python to build reliable crawlers. Extract data for AI, LLMs, RAG, or GPTs. Download HTML, PDF, JPG, PNG, and other files from websites. Works with BeautifulSoup, Playwright, and raw HTTP. Both headful and headless mode. With proxy rotation.| | 762|k2-fsa/sherpa-onnx !2025-03-28541520|Speech-to-text, text-to-speech, and speaker recongition using next-gen Kaldi with onnxruntime without Internet connection. Support embedded systems, Android, iOS, Raspberry Pi, RISC-V, x86_64 servers, websocket server/client, C/C++, Python, Kotlin, C#, Go, NodeJS, Java, Swift| | 763|TEN-framework/TEN-Agent !2025-03-28541411|TEN Agent is a realtime conversational AI agent powered by TEN. It seamlessly integrates the OpenAI Realtime API, RTC capabilities, and advanced features like weather updates, web search, computer vision, and Retrieval-Augmented Generation (RAG).| | 764|google/gemmapytorch !2025-03-2854010|The official PyTorch implementation of Google's Gemma models| | 765|snakers4/silero-vad !2025-03-2853858|Silero VAD: pre-trained enterprise-grade Voice Activity Detector| | 766|livekit/agents !2025-03-2853836|Build real-time multimodal AI applications 🤖🎙️📹| | 767|pipecat-ai/pipecat !2025-03-28537811|Open Source framework for voice and multimodal conversational AI| | 768|EricLBuehler/mistral.rs !2025-03-28536324|Blazingly fast LLM inference.| | 769|asg017/sqlite-vec !2025-03-28535810|Work-in-progress vector search SQLite extension that runs anywhere.| | 770|albertan017/LLM4Decompile !2025-03-2853563|Reverse Engineering: Decompiling Binary Code with Large Language Models| | 771|Permify/permify !2025-03-2853235|An open-source authorization as a service inspired by Google Zanzibar, designed to build and manage fine-grained and scalable authorization systems for any application.| | 772|imoneoi/openchat !2025-03-2853171|OpenChat: Advancing Open-source Language Models with Imperfect Data| | 773|mosaicml/composer !2025-03-2853140|Train neural networks up to 7x faster| | 774|dsdanielpark/Bard-API !2025-03-285277-1 |The python package that returns a response of Google Bard through API.| | 775|lxfater/inpaint-web !2025-03-2852552|A free and open-source inpainting & image-upscaling tool powered by webgpu and wasm on the browser。| | 776|leanprover/lean4 !2025-03-2852441|Lean 4 programming language and theorem prover| | 777|AILab-CVC/YOLO-World !2025-03-2852415|Real-Time Open-Vocabulary Object Detection| | 778|openchatai/OpenChat !2025-03-2852260 |Run and create custom ChatGPT-like bots with OpenChat, embed and share these bots anywhere, the open-source chatbot console.| | 779|mufeedvh/code2prompt !2025-03-28519414|A CLI tool to convert your codebase into a single LLM prompt with source tree, prompt templating, and token counting.| | 780|biobootloader/wolverine !2025-03-2851700 |Automatically repair python scripts through GPT-4 to give them regenerative abilities.| | 781|huggingface/parler-tts !2025-03-2851671|Inference and training library for high-quality TTS models.| | 782|Akegarasu/lora-scripts !2025-03-2851308 |LoRA training scripts use kohya-ss's trainer, for diffusion model.| | 783|openchatai/OpenCopilot !2025-03-285128-3|🤖 🔥 Let your users chat with your product features and execute things by text - open source Shopify sidekick| | 784|e2b-dev/fragments !2025-03-2851228|Open-source Next.js template for building apps that are fully generated by AI. By E2B.| | 785|microsoft/SynapseML !2025-03-2851132|Simple and Distributed Machine Learning| | 786|aigc-apps/sd-webui-EasyPhoto !2025-03-285108-1|📷 EasyPhoto | | 787|ChaoningZhang/MobileSAM !2025-03-2850944|This is the official code for Faster Segment Anything (MobileSAM) project that makes SAM lightweight| | 788|huggingface/alignment-handbook !2025-03-2850932|Robust recipes for to align language models with human and AI preferences| | 789|alpkeskin/mosint !2025-03-2850920|An automated e-mail OSINT tool| | 790|TaskingAI/TaskingAI !2025-03-2850891|The open source platform for AI-native application development.| | 791|lipku/metahuman-stream !2025-03-28507615|Real time interactive streaming digital human| | 792|OpenInterpreter/01 !2025-03-2850530|The open-source language model computer| | 793|open-compass/opencompass !2025-03-28505111|OpenCompass is an LLM evaluation platform, supporting a wide range of models (InternLM2,GPT-4,LLaMa2, Qwen,GLM, Claude, etc) over 100+ datasets.| | 794|xxlong0/Wonder3D !2025-03-2850491|A cross-domain diffusion model for 3D reconstruction from a single image| | 795|pytorch/torchtune !2025-03-2850342|A Native-PyTorch Library for LLM Fine-tuning| | 796|SuperDuperDB/superduperdb !2025-03-2850192|🔮 SuperDuperDB: Bring AI to your database: Integrate, train and manage any AI models and APIs directly with your database and your data.| | 797|WhiskeySockets/Baileys !2025-03-2850057|Lightweight full-featured typescript/javascript WhatsApp Web API| | 798| mpociot/chatgpt-vscode !2025-03-2849890 | A VSCode extension that allows you to use ChatGPT | | 799|OpenGVLab/DragGAN !2025-03-2849880|Unofficial Implementation of DragGAN - "Drag Your GAN: Interactive Point-based Manipulation on the Generative Image Manifold" （DragGAN 全功能实现，在线Demo，本地部署试用，代码、模型已全部开源，支持Windows, macOS, Linux）| | 800|microsoft/LLMLingua !2025-03-2849824|To speed up LLMs' inference and enhance LLM's perceive of key information, compress the prompt and KV-Cache, which achieves up to 20x compression with minimal performance loss.| | 801|Zipstack/unstract !2025-03-2849745|No-code LLM Platform to launch APIs and ETL Pipelines to structure unstructured documents| | 802|OpenBMB/ToolBench !2025-03-2849621|An open platform for training, serving, and evaluating large language model for tool learning.| | 803|Fanghua-Yu/SUPIR !2025-03-2849593|SUPIR aims at developing Practical Algorithms for Photo-Realistic Image Restoration In the Wild| | 804|GaiaNet-AI/gaianet-node !2025-03-2849360|Install and run your own AI agent service| | 805|qodo-ai/qodo-cover !2025-03-284922-1|Qodo-Cover: An AI-Powered Tool for Automated Test Generation and Code Coverage Enhancement! 💻🤖🧪🐞| | 806|Zejun-Yang/AniPortrait !2025-03-2849042|AniPortrait: Audio-Driven Synthesis of Photorealistic Portrait Animation| | 807|lvwzhen/law-cn-ai !2025-03-2848901 |⚖️ AI Legal Assistant| | 808|developersdigest/llm-answer-engine !2025-03-2848740|Build a Perplexity-Inspired Answer Engine Using Next.js, Groq, Mixtral, Langchain, OpenAI, Brave & Serper| | 809|Plachtaa/VITS-fast-fine-tuning !2025-03-2848640|This repo is a pipeline of VITS finetuning for fast speaker adaptation TTS, and many-to-many voice conversion| | 810|espeak-ng/espeak-ng !2025-03-2848601|eSpeak NG is an open source speech synthesizer that supports more than hundred languages and accents.| | 811|ant-research/CoDeF !2025-03-2848581|[CVPR'24 Highlight] Official PyTorch implementation of CoDeF: Content Deformation Fields for Temporally Consistent Video Processing| | 812|deepseek-ai/DeepSeek-V2 !2025-03-2848512|| | 813|XRPLF/rippled !2025-03-2848210|Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++| | 814|AutoMQ/automq !2025-03-28478721|AutoMQ is a cloud-first alternative to Kafka by decoupling durability to S3 and EBS. 10x cost-effective. Autoscale in seconds. Single-digit ms latency.| | 815|AILab-CVC/VideoCrafter !2025-03-2847800|VideoCrafter1: Open Diffusion Models for High-Quality Video Generation| | 816|nautechsystems/nautilustrader !2025-03-2847702|A high-performance algorithmic trading platform and event-driven backtester| | 817|kyegomez/swarms !2025-03-2847563|The Enterprise-Grade Production-Ready Multi-Agent Orchestration Framework Join our Community: https://discord.com/servers/agora-999382051935506503| | 818|Deci-AI/super-gradients !2025-03-2847310 |Easily train or fine-tune SOTA computer vision models with one open source training library. The home of Yolo-NAS.| | 819|QwenLM/Qwen2.5-Coder !2025-03-2847236|Qwen2.5-Coder is the code version of Qwen2.5, the large language model series developed by Qwen team, Alibaba Cloud.| | 820|SCIR-HI/Huatuo-Llama-Med-Chinese !2025-03-2847191 |Repo for HuaTuo (华驼), Llama-7B tuned with Chinese medical knowledge| | 821|togethercomputer/RedPajama-Data !2025-03-2846841 |code for preparing large datasets for training large language models| | 822|mishushakov/llm-scraper !2025-03-2846704|Turn any webpage into structured data using LLMs| | 823|1rgs/jsonformer !2025-03-2846663 |A Bulletproof Way to Generate Structured JSON from Language Models| | 824|anti-work/shortest !2025-03-2846565|QA via natural language AI tests| | 825|dnhkng/GlaDOS !2025-03-2846510|This is the Personality Core for GLaDOS, the first steps towards a real-life implementation of the AI from the Portal series by Valve.| | 826|Nukem9/dlssg-to-fsr3 !2025-03-2846380|Adds AMD FSR3 Frame Generation to games by replacing Nvidia DLSS-G Frame Generation (nvngx_dlssg).| | 827|BuilderIO/ai-shell !2025-03-2846373 |A CLI that converts natural language to shell commands.| | 828|facebookincubator/AITemplate !2025-03-2846220 |AITemplate is a Python framework which renders neural network into high performance CUDA/HIP C++ code. Specialized for FP16 TensorCore (NVIDIA GPU) and MatrixCore (AMD GPU) inference.| | 829|terraform-aws-modules/terraform-aws-eks !2025-03-2846030|Terraform module to create AWS Elastic Kubernetes (EKS) resources 🇺🇦| | 830|timescale/pgai !2025-03-2845915|A suite of tools to develop RAG, semantic search, and other AI applications more easily with PostgreSQL| | 831|awslabs/multi-agent-orchestrator !2025-03-2845788|Flexible and powerful framework for managing multiple AI agents and handling complex conversations| | 832|sanchit-gandhi/whisper-jax !2025-03-2845771 |Optimised JAX code for OpenAI's Whisper Model, largely built on the Hugging Face Transformers Whisper implementation| | 833|NVIDIA/NeMo-Guardrails !2025-03-2845755|NeMo Guardrails is an open-source toolkit for easily adding programmable guardrails to LLM-based conversational systems.| | 834|PathOfBuildingCommunity/PathOfBuilding !2025-03-2845480|Offline build planner for Path of Exile.| | 835|UX-Decoder/Segment-Everything-Everywhere-All-At-Once !2025-03-2845412 |Official implementation of the paper "Segment Everything Everywhere All at Once"| | 836|build-trust/ockam !2025-03-2845171|Orchestrate end-to-end encryption, cryptographic identities, mutual authentication, and authorization policies between distributed applications – at massive scale.| | 837|google-research/timesfm !2025-03-2845135|TimesFM (Time Series Foundation Model) is a pretrained time-series foundation model developed by Google Research for time-series forecasting.| | 838|luosiallen/latent-consistency-model !2025-03-2844842|Latent Consistency Models: Synthesizing High-Resolution Images with Few-Step Inference| | 839|NVlabs/neuralangelo !2025-03-2844740|Official implementation of "Neuralangelo: High-Fidelity Neural Surface Reconstruction" (CVPR 2023)| | 840|kyegomez/tree-of-thoughts !2025-03-2844720 |Plug in and Play Implementation of Tree of Thoughts: Deliberate Problem Solving with Large Language Models that Elevates Model Reasoning by atleast 70%| | 841|sjvasquez/handwriting-synthesis !2025-03-2844720 |Handwriting Synthesis with RNNs ✏️| | 842| madawei2699/myGPTReader !2025-03-2844420 | A slack bot that can read any webpage, ebook or document and summarize it with chatGPT | | 843|OpenBMB/AgentVerse !2025-03-2844413|🤖 AgentVerse 🪐 provides a flexible framework that simplifies the process of building custom multi-agent environments for large language models (LLMs).| | 844|argmaxinc/WhisperKit !2025-03-2844395|Swift native speech recognition on-device for iOS and macOS applications.| | 845|landing-ai/vision-agent !2025-03-2844346|Vision agent| | 846|InternLM/xtuner !2025-03-2844273|An efficient, flexible and full-featured toolkit for fine-tuning large models (InternLM, Llama, Baichuan, Qwen, ChatGLM)| | 847|google-deepmind/alphageometry !2025-03-284421-1|Solving Olympiad Geometry without Human Demonstrations| | 848|ostris/ai-toolkit !2025-03-2844093|Various AI scripts. Mostly Stable Diffusion stuff.| | 849|LLM-Red-Team/kimi-free-api !2025-03-2844004|🚀 KIMI AI 长文本大模型白嫖服务，支持高速流式输出、联网搜索、长文档解读、图像解析、多轮对话，零配置部署，多路token支持，自动清理会话痕迹。| | 850|argilla-io/argilla !2025-03-2843991|Argilla is a collaboration platform for AI engineers and domain experts that require high-quality outputs, full data ownership, and overall efficiency.| | 851|spring-projects/spring-ai !2025-03-28438419|An Application Framework for AI Engineering| | 852|alibaba-damo-academy/FunClip !2025-03-2843555|Open-source, accurate and easy-to-use video clipping tool, LLM based AI clipping intergrated | | 853|yisol/IDM-VTON !2025-03-2843541|IDM-VTON : Improving Diffusion Models for Authentic Virtual Try-on in the Wild| | 854|fchollet/ARC-AGI !2025-03-2843368|The Abstraction and Reasoning Corpus| | 855|MahmoudAshraf97/whisper-diarization !2025-03-2843064|Automatic Speech Recognition with Speaker Diarization based on OpenAI Whisper| | 856|Speykious/cve-rs !2025-03-2843047|Blazingly 🔥 fast 🚀 memory vulnerabilities, written in 100% safe Rust. 🦀| | 857|Blealtan/efficient-kan !2025-03-2842770|An efficient pure-PyTorch implementation of Kolmogorov-Arnold Network (KAN).| | 858|smol-ai/GodMode !2025-03-284249-1|AI Chat Browser: Fast, Full webapp access to ChatGPT / Claude / Bard / Bing / Llama2! I use this 20 times a day.| | 859|openai/plugins-quickstart !2025-03-284235-4 |Get a ChatGPT plugin up and running in under 5 minutes!| | 860|Doriandarko/maestro !2025-03-2842260|A framework for Claude Opus to intelligently orchestrate subagents.| | 861|philz1337x/clarity-upscaler !2025-03-2842204|Clarity-Upscaler: Reimagined image upscaling for everyone| | 862|facebookresearch/co-tracker !2025-03-2842142|CoTracker is a model for tracking any point (pixel) on a video.| | 863|xlang-ai/OpenAgents !2025-03-2842031|OpenAgents: An Open Platform for Language Agents in the Wild| | 864|alibaba/higress !2025-03-28419514|🤖 AI Gateway | | 865|ray-project/llm-numbers !2025-03-2841920 |Numbers every LLM developer should know| | 866|fudan-generative-vision/champ !2025-03-2841820|Champ: Controllable and Consistent Human Image Animation with 3D Parametric Guidance| | 867|NVIDIA/garak !2025-03-2841795|the LLM vulnerability scanner| | 868|leetcode-mafia/cheetah !2025-03-2841740 |Whisper & GPT-based app for passing remote SWE interviews| | 869|ragapp/ragapp !2025-03-2841710|The easiest way to use Agentic RAG in any enterprise| | 870|collabora/WhisperSpeech !2025-03-2841692|An Open Source text-to-speech system built by inverting Whisper.| | 871|Facico/Chinese-Vicuna !2025-03-2841520 |Chinese-Vicuna: A Chinese Instruction-following LLaMA-based Model| | 872|openai/grok !2025-03-2841381|| | 873|CrazyBoyM/llama3-Chinese-chat !2025-03-2841361|Llama3 Chinese Repository with modified versions, and training and deployment resources| | 874|luban-agi/Awesome-AIGC-Tutorials !2025-03-2841301|Curated tutorials and resources for Large Language Models, AI Painting, and more.| | 875|damo-vilab/AnyDoor !2025-03-2841192|Official implementations for paper: Anydoor: zero-shot object-level image customization| | 876|raspberrypi/pico-sdk !2025-03-2841072|| | 877|mshumer/gpt-llm-trainer !2025-03-284097-1|| | 878|metavoiceio/metavoice-src !2025-03-284076-1|AI for human-level speech intelligence| | 879|intelowlproject/IntelOwl !2025-03-2840763|IntelOwl: manage your Threat Intelligence at scale| | 880|a16z-infra/ai-getting-started !2025-03-2840682|A Javascript AI getting started stack for weekend projects, including image/text models, vector stores, auth, and deployment configs| | 881|MarkFzp/mobile-aloha !2025-03-2840641|Mobile ALOHA: Learning Bimanual Mobile Manipulation with Low-Cost Whole-Body Teleoperation| | 882| keijiro/AICommand !2025-03-2840380 | ChatGPT integration with Unity Editor | | 883|Tencent/HunyuanDiT !2025-03-2840214|Hunyuan-DiT : A Powerful Multi-Resolution Diffusion Transformer with Fine-Grained Chinese Understanding| | 884|hengyoush/kyanos !2025-03-2840061|Visualize the time packets spend in the kernel, watch & analyze in command line.| | 885|agiresearch/AIOS !2025-03-2840045|AIOS: LLM Agent Operating System| | 886|truefoundry/cognita !2025-03-2839773|RAG (Retrieval Augmented Generation) Framework for building modular, open source applications for production by TrueFoundry| | 887|X-PLUG/MobileAgent !2025-03-2839557|Mobile-Agent: Autonomous Multi-Modal Mobile Device Agent with Visual Perception| | 888|jackMort/ChatGPT.nvim !2025-03-2839231|ChatGPT Neovim Plugin: Effortless Natural Language Generation with OpenAI's ChatGPT API| | 889|microsoft/RD-Agent !2025-03-28388422|Research and development (R&D) is crucial for the enhancement of industrial productivity, especially in the AI era, where the core aspects of R&D are mainly focused on data and models. We are committed to automate these high-value generic R&D processes through our open source R&D automation tool RD-Agent, which let AI drive data-driven AI.| | 890|Significant-Gravitas/Auto-GPT-Plugins !2025-03-283882-1 |Plugins for Auto-GPT| | 891|apple/ml-mgie !2025-03-2838770|| | 892|OpenDriveLab/UniAD !2025-03-2838727|[CVPR 2023 Best Paper] Planning-oriented Autonomous Driving| | 893|llSourcell/DoctorGPT !2025-03-2838640|DoctorGPT is an LLM that can pass the US Medical Licensing Exam. It works offline, it's cross-platform, & your health data stays private.| | 894|FlagAI-Open/FlagAI !2025-03-2838601|FlagAI (Fast LArge-scale General AI models) is a fast, easy-to-use and extensible toolkit for large-scale model.| | 895|krishnaik06/Roadmap-To-Learn-Generative-AI-In-2024 !2025-03-2838513|Roadmap To Learn Generative AI In 2024| | 896|SysCV/sam-hq !2025-03-2838491|Segment Anything in High Quality| | 897|google/security-research !2025-03-2838420|This project hosts security advisories and their accompanying proof-of-concepts related to research conducted at Google which impact non-Google owned code.| | 898|shroominic/codeinterpreter-api !2025-03-2838330|Open source implementation of the ChatGPT Code Interpreter 👾| | 899|Yonom/assistant-ui !2025-03-2838308|React Components for AI Chat 💬 🚀| | 900|nucleuscloud/neosync !2025-03-2838262|Open source data anonymization and synthetic data orchestration for developers. Create high fidelity synthetic data and sync it across your environments.| | 901|ravenscroftj/turbopilot !2025-03-2838230 |Turbopilot is an open source large-language-model based code completion engine that runs locally on CPU| | 902|NVlabs/Sana !2025-03-28380810|SANA: Efficient High-Resolution Image Synthesis with Linear Diffusion Transformer| | 903|huggingface/distil-whisper !2025-03-2838061|Distilled variant of Whisper for speech recognition. 6x faster, 50% smaller, within 1% word error rate.| | 904|Codium-ai/AlphaCodium !2025-03-2837971|code generation tool that surpasses most human competitors in CodeContests| | 905|fixie-ai/ultravox !2025-03-2837710|A fast multimodal LLM for real-time voice| | 906|unit-mesh/auto-dev !2025-03-28375715|🧙‍AutoDev: The AI-powered coding wizard with multilingual support 🌐, auto code generation 🏗️, and a helpful bug-slaying assistant 🐞! Customizable prompts 🎨 and a magic Auto Dev/Testing/Document/Agent feature 🧪 included! 🚀| | 907|Marker-Inc-Korea/AutoRAG !2025-03-2837432|AutoML tool for RAG| | 908|deepseek-ai/DeepSeek-VL !2025-03-283734-1|DeepSeek-VL: Towards Real-World Vision-Language Understanding| | 909|hiyouga/ChatGLM-Efficient-Tuning !2025-03-283692-1|Fine-tuning ChatGLM-6B with PEFT | | 910| Yue-Yang/ChatGPT-Siri !2025-03-2836921 | Shortcuts for Siri using ChatGPT API gpt-3.5-turbo model | | 911|0hq/WebGPT !2025-03-2836901 |Run GPT model on the browser with WebGPU. An implementation of GPT inference in less than ~2000 lines of vanilla Javascript.| | 912|cvg/LightGlue !2025-03-2836903|LightGlue: Local Feature Matching at Light Speed (ICCV 2023)| | 913|deanxv/coze-discord-proxy !2025-03-2836791|代理Discord-Bot对话Coze-Bot，实现API形式请求GPT4对话模型/微调模型| | 914|MervinPraison/PraisonAI !2025-03-2836764|PraisonAI application combines AutoGen and CrewAI or similar frameworks into a low-code solution for building and managing multi-agent LLM systems, focusing on simplicity, customisation, and efficient human-agent collaboration.| | 915|Ironclad/rivet !2025-03-2836345 |The open-source visual AI programming environment and TypeScript library| | 916|BasedHardware/OpenGlass !2025-03-2835851|Turn any glasses into AI-powered smart glasses| | 917|ricklamers/gpt-code-ui !2025-03-2835840 |An open source implementation of OpenAI's ChatGPT Code interpreter| | 918|whoiskatrin/chart-gpt !2025-03-2835830 |AI tool to build charts based on text input| | 919|github/CopilotForXcode !2025-03-2835788|Xcode extension for GitHub Copilot| | 920|hemansnation/God-Level-Data-Science-ML-Full-Stack !2025-03-2835570 |A collection of scientific methods, processes, algorithms, and systems to build stories & models. This roadmap contains 16 Chapters, whether you are a fresher in the field or an experienced professional who wants to transition into Data Science & AI| | 921|pytorch/torchchat !2025-03-2835461|Run PyTorch LLMs locally on servers, desktop and mobile| | 922| Kent0n-Li/ChatDoctor !2025-03-2835451 | A Medical Chat Model Fine-tuned on LLaMA Model using Medical Domain Knowledge | | 923|xtekky/chatgpt-clone !2025-03-283519-1 |ChatGPT interface with better UI| | 924|jupyterlab/jupyter-ai !2025-03-2835120|A generative AI extension for JupyterLab| | 925|pytorch/torchtitan !2025-03-2835064|A native PyTorch Library for large model training| | 926|minimaxir/simpleaichat !2025-03-2835031|Python package for easily interfacing with chat apps, with robust features and minimal code complexity.| | 927|srush/Tensor-Puzzles !2025-03-2834930|Solve puzzles. Improve your pytorch.| | 928|Helicone/helicone !2025-03-2834918|🧊 Open source LLM-Observability Platform for Developers. One-line integration for monitoring, metrics, evals, agent tracing, prompt management, playground, etc. Supports OpenAI SDK, Vercel AI SDK, Anthropic SDK, LiteLLM, LLamaIndex, LangChain, and more. 🍓 YC W23| | 929|run-llama/llama-hub !2025-03-2834740|A library of data loaders for LLMs made by the community -- to be used with LlamaIndex and/or LangChain| | 930|NExT-GPT/NExT-GPT !2025-03-2834700|Code and models for NExT-GPT: Any-to-Any Multimodal Large Language Model| | 931|souzatharsis/podcastfy !2025-03-2834661|An Open Source Python alternative to NotebookLM's podcast feature: Transforming Multimodal Content into Captivating Multilingual Audio Conversations with GenAI| | 932|Dataherald/dataherald !2025-03-2834450|Interact with your SQL database, Natural Language to SQL using LLMs| | 933|iryna-kondr/scikit-llm !2025-03-2834350 |Seamlessly integrate powerful language models like ChatGPT into scikit-learn for enhanced text analysis tasks.| | 934|Netflix/maestro !2025-03-2834230|Maestro: Netflix’s Workflow Orchestrator| | 935|CanadaHonk/porffor !2025-03-2833560|A from-scratch experimental AOT JS engine, written in JS| | 936|hustvl/Vim !2025-03-2833323|Vision Mamba: Efficient Visual Representation Learning with Bidirectional State Space Model| | 937|pashpashpash/vault-ai !2025-03-2833250 |OP Vault ChatGPT: Give ChatGPT long-term memory using the OP Stack (OpenAI + Pinecone Vector Database). Upload your own custom knowledge base files (PDF, txt, etc) using a simple React frontend.| | 938|tencentmusic/supersonic !2025-03-28330611|SuperSonic is the next-generation BI platform that integrates Chat BI (powered by LLM) and Headless BI (powered by semantic layer) paradigms.| | 939|billmei/every-chatgpt-gui !2025-03-2832981|Every front-end GUI client for ChatGPT| | 940|microsoft/torchgeo !2025-03-2832772|TorchGeo: datasets, samplers, transforms, and pre-trained models for geospatial data| | 941|LLMBook-zh/LLMBook-zh.github.io !2025-03-28326110|《大语言模型》作者：赵鑫，李军毅，周昆，唐天一，文继荣| | 942|dvlab-research/MiniGemini !2025-03-2832601|Official implementation for Mini-Gemini| | 943|rashadphz/farfalle !2025-03-2832460|🔍 AI search engine - self-host with local or cloud LLMs| | 944|Luodian/Otter !2025-03-2832450|🦦 Otter, a multi-modal model based on OpenFlamingo (open-sourced version of DeepMind's Flamingo), trained on MIMIC-IT and showcasing improved instruction-following and in-context learning ability.| | 945|AprilNEA/ChatGPT-Admin-Web !2025-03-2832370 | ChatGPT WebUI with user management and admin dashboard system| | 946|MarkFzp/act-plus-plus !2025-03-2832365|Imitation Learning algorithms with Co-traing for Mobile ALOHA: ACT, Diffusion Policy, VINN| | 947|ethen8181/machine-learning !2025-03-2832310|🌎 machine learning tutorials (mainly in Python3)| | 948|opengeos/segment-geospatial !2025-03-2832312 |A Python package for segmenting geospatial data with the Segment Anything Model (SAM)| | 949|iusztinpaul/hands-on-llms !2025-03-283225-2|🦖 𝗟𝗲𝗮𝗿𝗻 about 𝗟𝗟𝗠𝘀, 𝗟𝗟𝗠𝗢𝗽𝘀, and 𝘃𝗲𝗰𝘁𝗼𝗿 𝗗𝗕𝘀 for free by designing, training, and deploying a real-time financial advisor LLM system ~ 𝘴𝘰𝘶𝘳𝘤𝘦 𝘤𝘰𝘥𝘦 + 𝘷𝘪𝘥𝘦𝘰 & 𝘳𝘦𝘢𝘥𝘪𝘯𝘨 𝘮𝘢𝘵𝘦𝘳𝘪𝘢𝘭𝘴| | 950|ToTheBeginning/PuLID !2025-03-2832221|Official code for PuLID: Pure and Lightning ID Customization via Contrastive Alignment| | 951|neo4j-labs/llm-graph-builder !2025-03-2832164|Neo4j graph construction from unstructured data using LLMs| | 952|OpenGVLab/InternGPT !2025-03-2832150 |InternGPT (iGPT) is an open source demo platform where you can easily showcase your AI models. Now it supports DragGAN, ChatGPT, ImageBind, multimodal chat like GPT-4, SAM, interactive image editing, etc. Try it at igpt.opengvlab.com (支持DragGAN、ChatGPT、ImageBind、SAM的在线Demo系统)| | 953|PKU-YuanGroup/Video-LLaVA !2025-03-2832060 |Video-LLaVA: Learning United Visual Representation by Alignment Before Projection| | 954|DataTalksClub/llm-zoomcamp !2025-03-2832030|LLM Zoomcamp - a free online course about building an AI bot that can answer questions about your knowledge base| | 955|gptscript-ai/gptscript !2025-03-2832010|Natural Language Programming| |!green-up-arrow.svg 956|isaac-sim/IsaacLab !2025-03-28320113|Unified framework for robot learning built on NVIDIA Isaac Sim| |!red-down-arrow 957|ai-boost/Awesome-GPTs !2025-03-2832003|Curated list of awesome GPTs 👍.| | 958|huggingface/safetensors !2025-03-2831901|Simple, safe way to store and distribute tensors| | 959|linyiLYi/bilibot !2025-03-2831771|A local chatbot fine-tuned by bilibili user comments.| | 960| project-baize/baize-chatbot !2025-03-283168-1 | Let ChatGPT teach your own chatbot in hours with a single GPU! | | 961|Azure-Samples/cognitive-services-speech-sdk !2025-03-2831280|Sample code for the Microsoft Cognitive Services Speech SDK| | 962|microsoft/Phi-3CookBook !2025-03-2831231|This is a Phi-3 book for getting started with Phi-3. Phi-3, a family of open AI models developed by Microsoft. Phi-3 models are the most capable and cost-effective small language models (SLMs) available, outperforming models of the same size and next size up across a variety of language, reasoning, coding, and math benchmarks.| | 963|neuralmagic/deepsparse !2025-03-2831180|Sparsity-aware deep learning inference runtime for CPUs| | 964|sugarforever/chat-ollama !2025-03-2831000|ChatOllama is an open source chatbot based on LLMs. It supports a wide range of language models, and knowledge base management.| | 965|amazon-science/chronos-forecasting !2025-03-2830974|Chronos: Pretrained (Language) Models for Probabilistic Time Series Forecasting| | 966|damo-vilab/i2vgen-xl !2025-03-2830902|Official repo for VGen: a holistic video generation ecosystem for video generation building on diffusion models| | 967|google-deepmind/gemma !2025-03-2830733|Open weights LLM from Google DeepMind.| | 968|iree-org/iree !2025-03-2830733|A retargetable MLIR-based machine learning compiler and runtime toolkit.| | 969|NVlabs/VILA !2025-03-2830724|VILA - a multi-image visual language model with training, inference and evaluation recipe, deployable from cloud to edge (Jetson Orin and laptops)| | 970|microsoft/torchscale !2025-03-2830661|Foundation Architecture for (M)LLMs| | 971|openai/openai-realtime-console !2025-03-2830656|React app for inspecting, building and debugging with the Realtime API| | 972|daveshap/OpenAIAgentSwarm !2025-03-2830610|HAAS = Hierarchical Autonomous Agent Swarm - "Resistance is futile!"| | 973|microsoft/PromptWizard !2025-03-2830555|Task-Aware Agent-driven Prompt Optimization Framework| | 974|CVI-SZU/Linly !2025-03-2830490 |Chinese-LLaMA basic model; ChatFlow Chinese conversation model; NLP pre-training/command fine-tuning dataset| | 975|cohere-ai/cohere-toolkit !2025-03-2830130|Toolkit is a collection of prebuilt components enabling users to quickly build and deploy RAG applications.| | 976|adamcohenhillel/ADeus !2025-03-2830131|An open source AI wearable device that captures what you say and hear in the real world and then transcribes and stores it on your own server. You can then chat with Adeus using the app, and it will have all the right context about what you want to talk about - a truly personalized, personal AI.| | 977|Lightning-AI/LitServe !2025-03-2830132|Lightning-fast serving engine for AI models. Flexible. Easy. Enterprise-scale.| | 978|potpie-ai/potpie !2025-03-2829973|Prompt-To-Agent : Create custom engineering agents for your codebase| | 979|ant-design/x !2025-03-28299529|Craft AI-driven interfaces effortlessly 🤖| | 980|meta-llama/PurpleLlama !2025-03-2829832|Set of tools to assess and improve LLM security.| | 981|williamyang1991/RerenderAVideo !2025-03-2829800|[SIGGRAPH Asia 2023] Rerender A Video: Zero-Shot Text-Guided Video-to-Video Translation| | 982|baichuan-inc/Baichuan-13B !2025-03-2829790|A 13B large language model developed by Baichuan Intelligent Technology| | 983|Stability-AI/stable-audio-tools !2025-03-2829761|Generative models for conditional audio generation| | 984|li-plus/chatglm.cpp !2025-03-2829720|C++ implementation of ChatGLM-6B & ChatGLM2-6B & ChatGLM3 & more LLMs| | 985|NVIDIA/GenerativeAIExamples !2025-03-2829546|Generative AI reference workflows optimized for accelerated infrastructure and microservice architecture.| | 986|Josh-XT/AGiXT !2025-03-2829521 |AGiXT is a dynamic AI Automation Platform that seamlessly orchestrates instruction management and complex task execution across diverse AI providers. Combining adaptive memory, smart features, and a versatile plugin system, AGiXT delivers efficient and comprehensive AI solutions.| | 987|MrForExample/ComfyUI-3D-Pack !2025-03-2829515|An extensive node suite that enables ComfyUI to process 3D inputs (Mesh & UV Texture, etc) using cutting edge algorithms (3DGS, NeRF, etc.)| | 988|olimorris/codecompanion.nvim !2025-03-28295111|✨ AI-powered coding, seamlessly in Neovim. Supports Anthropic, Copilot, Gemini, Ollama, OpenAI and xAI LLMs| | 989|salesforce/CodeT5 !2025-03-282940-1 |Home of CodeT5: Open Code LLMs for Code Understanding and Generation| | 990|facebookresearch/ijepa !2025-03-2829391|Official codebase for I-JEPA, the Image-based Joint-Embedding Predictive Architecture. First outlined in the CVPR paper, "Self-supervised learning from images with a joint-embedding predictive architecture."| | 991|eureka-research/Eureka !2025-03-2829351|Official Repository for "Eureka: Human-Level Reward Design via Coding Large Language Models"| | 992|NVIDIA/trt-llm-rag-windows !2025-03-282934-1|A developer reference project for creating Retrieval Augmented Generation (RAG) chatbots on Windows using TensorRT-LLM| | 993|gmpetrov/databerry !2025-03-282930-1|The no-code platform for building custom LLM Agents| | 994|AI4Finance-Foundation/FinRobot !2025-03-28291946|FinRobot: An Open-Source AI Agent Platform for Financial Applications using LLMs 🚀 🚀 🚀| | 995|nus-apr/auto-code-rover !2025-03-2829013|A project structure aware autonomous software engineer aiming for autonomous program improvement| | 996|deepseek-ai/DreamCraft3D !2025-03-2828921|[ICLR 2024] Official implementation of DreamCraft3D: Hierarchical 3D Generation with Bootstrapped Diffusion Prior| | 997|mlabonne/llm-datasets !2025-03-2828848|High-quality datasets, tools, and concepts for LLM fine-tuning.| | 998|facebookresearch/jepa !2025-03-2828712|PyTorch code and models for V-JEPA self-supervised learning from video.| | 999|facebookresearch/habitat-sim !2025-03-2828604|A flexible, high-performance 3D simulator for Embodied AI research.| | 1000|xenova/whisper-web !2025-03-2828581|ML-powered speech recognition directly in your browser| | 1001|cvlab-columbia/zero123 !2025-03-2828530|Zero-1-to-3: Zero-shot One Image to 3D Object: https://zero123.cs.columbia.edu/| | 1002|yuruotong1/autoMate !2025-03-28285121|Like Manus, Computer Use Agent(CUA) and Omniparser, we are computer-using agents.AI-driven local automation assistant that uses natural language to make computers work by themselves| | 1003|muellerberndt/mini-agi !2025-03-282845-1 |A minimal generic autonomous agent based on GPT3.5/4. Can analyze stock prices, perform network security tests, create art, and order pizza.| | 1004|allenai/open-instruct !2025-03-2828432|| | 1005|CodingChallengesFYI/SharedSolutions !2025-03-2828360|Publicly shared solutions to Coding Challenges| | 1006|hegelai/prompttools !2025-03-2828220|Open-source tools for prompt testing and experimentation, with support for both LLMs (e.g. OpenAI, LLaMA) and vector databases (e.g. Chroma, Weaviate).| | 1007|mazzzystar/Queryable !2025-03-2828222|Run CLIP on iPhone to Search Photos.| | 1008|Doubiiu/DynamiCrafter !2025-03-2828173|DynamiCrafter: Animating Open-domain Images with Video Diffusion Priors| | 1009|SamurAIGPT/privateGPT !2025-03-282805-1 |An app to interact privately with your documents using the power of GPT, 100% privately, no data leaks| | 1010|facebookresearch/Pearl !2025-03-2827951|A Production-ready Reinforcement Learning AI Agent Library brought by the Applied Reinforcement Learning team at Meta.| | 1011|intuitem/ciso-assistant-community !2025-03-2827954|CISO Assistant is a one-stop-shop for GRC, covering Risk, AppSec and Audit Management and supporting +70 frameworks worldwide with auto-mapping: NIST CSF, ISO 27001, SOC2, CIS, PCI DSS, NIS2, CMMC, PSPF, GDPR, HIPAA, Essential Eight, NYDFS-500, DORA, NIST AI RMF, 800-53, 800-171, CyFun, CJIS, AirCyber, NCSC, ECC, SCF and so much more| | 1012|facebookresearch/audio2photoreal !2025-03-2827840|Code and dataset for photorealistic Codec Avatars driven from audio| | 1013|Azure/azure-rest-api-specs !2025-03-2827770|The source for REST API specifications for Microsoft Azure.| | 1014|SCUTlihaoyu/open-chat-video-editor !2025-03-2827690 |Open source short video automatic generation tool| | 1015|Alpha-VLLM/LLaMA2-Accessory !2025-03-2827642|An Open-source Toolkit for LLM Development| | 1016|johnma2006/mamba-minimal !2025-03-2827601|Simple, minimal implementation of the Mamba SSM in one file of PyTorch.| | 1017|nerfstudio-project/gsplat !2025-03-2827576|CUDA accelerated rasterization of gaussian splatting| | 1018|Physical-Intelligence/openpi !2025-03-28274617|| | 1019|leptonai/leptonai !2025-03-2827246|A Pythonic framework to simplify AI service building| |!green-up-arrow.svg 1020|joanrod/star-vector !2025-03-28271149|StarVector is a foundation model for SVG generation that transforms vectorization into a code generation task. Using a vision-language modeling architecture, StarVector processes both visual and textual inputs to produce high-quality SVG code with remarkable precision.| |!red-down-arrow 1021|jqnatividad/qsv !2025-03-2827092|CSVs sliced, diced & analyzed.| | 1022|FranxYao/chain-of-thought-hub !2025-03-2826991|Benchmarking large language models' complex reasoning ability with chain-of-thought prompting| | 1023|princeton-nlp/SWE-bench !2025-03-2826965|[ICLR 2024] SWE-Bench: Can Language Models Resolve Real-world Github Issues?| | 1024|elastic/otel-profiling-agent !2025-03-2826930|The production-scale datacenter profiler| | 1025|src-d/hercules !2025-03-2826900|Gaining advanced insights from Git repository history.| | 1026|lanqian528/chat2api !2025-03-2826695|A service that can convert ChatGPT on the web to OpenAI API format.| | 1027|ishan0102/vimGPT !2025-03-2826681|Browse the web with GPT-4V and Vimium| | 1028|TMElyralab/MuseV !2025-03-2826650|MuseV: Infinite-length and High Fidelity Virtual Human Video Generation with Visual Conditioned Parallel Denoising| | 1029|georgia-tech-db/eva !2025-03-2826600 |AI-Relational Database System | | 1030|kubernetes-sigs/controller-runtime !2025-03-2826590|Repo for the controller-runtime subproject of kubebuilder (sig-apimachinery)| | 1031|gptlink/gptlink !2025-03-2826550 |Build your own free commercial ChatGPT environment in 10 minutes. The setup is simple and includes features such as user management, orders, tasks, and payments| | 1032|pytorch/executorch !2025-03-2826534|On-device AI across mobile, embedded and edge for PyTorch| | 1033|NVIDIA/nv-ingest !2025-03-2826290|NVIDIA Ingest is an early access set of microservices for parsing hundreds of thousands of complex, messy unstructured PDFs and other enterprise documents into metadata and text to embed into retrieval systems.| | 1034|SuperTux/supertux !2025-03-2826081|SuperTux source code| | 1035|abi/secret-llama !2025-03-2826050|Fully private LLM chatbot that runs entirely with a browser with no server needed. Supports Mistral and LLama 3.| | 1036|liou666/polyglot !2025-03-2825841 |Desktop AI Language Practice Application| | 1037|janhq/nitro !2025-03-2825821|A fast, lightweight, embeddable inference engine to supercharge your apps with local AI. OpenAI-compatible API| | 1038|deepseek-ai/DeepSeek-Math !2025-03-2825825|DeepSeekMath: Pushing the Limits of Mathematical Reasoning in Open Language Models| | 1039|anthropics/prompt-eng-interactive-tutorial !2025-03-2825781|Anthropic's Interactive Prompt Engineering Tutorial| | 1040|microsoft/promptbench !2025-03-2825741|A unified evaluation framework for large language models| | 1041|baaivision/Painter !2025-03-2825580 |Painter & SegGPT Series: Vision Foundation Models from BAAI| | 1042|OpenPipe/OpenPipe !2025-03-2825581|Turn expensive prompts into cheap fine-tuned models| | 1043|TracecatHQ/tracecat !2025-03-2825531|😼 The AI-native, open source alternative to Tines / Splunk SOAR.| | 1044|JoshuaC215/agent-service-toolkit !2025-03-2825528|Full toolkit for running an AI agent service built with LangGraph, FastAPI and Streamlit| | 1045|databricks/dbrx !2025-03-2825460|Code examples and resources for DBRX, a large language model developed by Databricks| | 1046|lamini-ai/lamini !2025-03-2825271 |Official repo for Lamini's data generator for generating instructions to train instruction-following LLMs| | 1047|mshumer/gpt-author !2025-03-282510-1|| | 1048|TMElyralab/MusePose !2025-03-2824971|MusePose: a Pose-Driven Image-to-Video Framework for Virtual Human Generation| | 1049|Kludex/fastapi-tips !2025-03-2824974|FastAPI Tips by The FastAPI Expert!| | 1050|openai/simple-evals !2025-03-2824813|| | 1051|iterative/datachain !2025-03-2824732|AI-data warehouse to enrich, transform and analyze data from cloud storages| | 1052|girafe-ai/ml-course !2025-03-2824703|Open Machine Learning course| | 1053|kevmo314/magic-copy !2025-03-2824620 |Magic Copy is a Chrome extension that uses Meta's Segment Anything Model to extract a foreground object from an image and copy it to the clipboard.| | 1054|Eladlev/AutoPrompt !2025-03-2824432|A framework for prompt tuning using Intent-based Prompt Calibration| | 1055|OpenBMB/CPM-Bee !2025-03-282434-1 |A bilingual large-scale model with trillions of parameters| | 1056|IDEA-Research/T-Rex !2025-03-2824310|T-Rex2: Towards Generic Object Detection via Text-Visual Prompt Synergy| | 1057|microsoft/genaiscript !2025-03-2824202|Automatable GenAI Scripting| | 1058|paulpierre/RasaGPT !2025-03-2824090 |💬 RasaGPT is the first headless LLM chatbot platform built on top of Rasa and Langchain. Built w/ Rasa, FastAPI, Langchain, LlamaIndex, SQLModel, pgvector, ngrok, telegram| | 1059|ashishpatel26/LLM-Finetuning !2025-03-2823911|LLM Finetuning with peft| | 1060|SoraWebui/SoraWebui !2025-03-2823570|SoraWebui is an open-source Sora web client, enabling users to easily create videos from text with OpenAI's Sora model.| | 1061|6drf21e/ChatTTScolab !2025-03-2823491|🚀 一键部署（含离线整合包）！基于 ChatTTS ，支持音色抽卡、长音频生成和分角色朗读。简单易用，无需复杂安装。| | 1062|Azure/PyRIT !2025-03-2823343|The Python Risk Identification Tool for generative AI (PyRIT) is an open access automation framework to empower security professionals and machine learning engineers to proactively find risks in their generative AI systems.| | 1063|tencent-ailab/V-Express !2025-03-2823201|V-Express aims to generate a talking head video under the control of a reference image, an audio, and a sequence of V-Kps images.| | 1064|THUDM/CogVLM2 !2025-03-2823170|GPT4V-level open-source multi-modal model based on Llama3-8B| | 1065|dvmazur/mixtral-offloading !2025-03-2823001|Run Mixtral-8x7B models in Colab or consumer desktops| | 1066|semanser/codel !2025-03-2822950|✨ Fully autonomous AI Agent that can perform complicated tasks and projects using terminal, browser, and editor.| | 1067|mshumer/gpt-investor !2025-03-2822590|| | 1068|aixcoder-plugin/aiXcoder-7B !2025-03-2822550|official repository of aiXcoder-7B Code Large Language Model| | 1069|Azure-Samples/graphrag-accelerator !2025-03-2822503|One-click deploy of a Knowledge Graph powered RAG (GraphRAG) in Azure| | 1070|emcf/engshell !2025-03-2821830 |An English-language shell for any OS, powered by LLMs| | 1071|hncboy/chatgpt-web-java !2025-03-2821771|ChatGPT project developed in Java, based on Spring Boot 3 and JDK 17, supports both AccessToken and ApiKey modes| | 1072|openai/consistencydecoder !2025-03-2821692|Consistency Distilled Diff VAE| | 1073|Alpha-VLLM/Lumina-T2X !2025-03-2821681|Lumina-T2X is a unified framework for Text to Any Modality Generation| | 1074|bghira/SimpleTuner !2025-03-2821612|A general fine-tuning kit geared toward Stable Diffusion 2.1, Stable Diffusion 3, DeepFloyd, and SDXL.| | 1075|JiauZhang/DragGAN !2025-03-2821530 |Implementation of DragGAN: Interactive Point-based Manipulation on the Generative Image Manifold| | 1076|cgpotts/cs224u !2025-03-2821390|Code for Stanford CS224u| | 1077|PKU-YuanGroup/MoE-LLaVA !2025-03-2821300|Mixture-of-Experts for Large Vision-Language Models| | 1078|darrenburns/elia !2025-03-2820831|A snappy, keyboard-centric terminal user interface for interacting with large language models. Chat with ChatGPT, Claude, Llama 3, Phi 3, Mistral, Gemma and more.| | 1079|ageerle/ruoyi-ai !2025-03-28207898|RuoYi AI 是一个全栈式 AI 开发平台，旨在帮助开发者快速构建和部署个性化的 AI 应用。| | 1080|NVIDIA/gpu-operator !2025-03-2820510|NVIDIA GPU Operator creates/configures/manages GPUs atop Kubernetes| | 1081|BAAI-Agents/Cradle !2025-03-2820481|The Cradle framework is a first attempt at General Computer Control (GCC). Cradle supports agents to ace any computer task by enabling strong reasoning abilities, self-improvment, and skill curation, in a standardized general environment with minimal requirements.| | 1082|microsoft/aici !2025-03-2820080|AICI: Prompts as (Wasm) Programs| | 1083|PRIS-CV/DemoFusion !2025-03-2820040|Let us democratise high-resolution generation! (arXiv 2023)| | 1084|apple/axlearn !2025-03-2820012|An Extensible Deep Learning Library| | 1085|naver/mast3r !2025-03-2819685|Grounding Image Matching in 3D with MASt3R| | 1086|liltom-eth/llama2-webui !2025-03-281958-1|Run Llama 2 locally with gradio UI on GPU or CPU from anywhere (Linux/Windows/Mac). Supporting Llama-2-7B/13B/70B with 8-bit, 4-bit. Supporting GPU inference (6 GB VRAM) and CPU inference.| | 1087|GaParmar/img2img-turbo !2025-03-2819582|One-step image-to-image with Stable Diffusion turbo: sketch2image, day2night, and more| | 1088|Niek/chatgpt-web !2025-03-2819560|ChatGPT web interface using the OpenAI API| | 1089|huggingface/cookbook !2025-03-2819421|Open-source AI cookbook| | 1090|pytorch/ao !2025-03-2819241|PyTorch native quantization and sparsity for training and inference| | 1091|emcie-co/parlant !2025-03-2819053|The behavior guidance framework for customer-facing LLM agents| | 1092|ymcui/Chinese-LLaMA-Alpaca-3 !2025-03-2818980|中文羊驼大模型三期项目 (Chinese Llama-3 LLMs) developed from Meta Llama 3| | 1093|Nutlope/notesGPT !2025-03-2818811|Record voice notes & transcribe, summarize, and get tasks| | 1094|InstantStyle/InstantStyle !2025-03-2818791|InstantStyle: Free Lunch towards Style-Preserving in Text-to-Image Generation 🔥| | 1095|idaholab/moose !2025-03-2818771|Multiphysics Object Oriented Simulation Environment| | 1096|The-OpenROAD-Project/OpenROAD !2025-03-2818351|OpenROAD's unified application implementing an RTL-to-GDS Flow. Documentation at https://openroad.readthedocs.io/en/latest/| | 1097|alibaba/spring-ai-alibaba !2025-03-281831121|Agentic AI Framework for Java Developers| | 1098|ytongbai/LVM !2025-03-2817990|Sequential Modeling Enables Scalable Learning for Large Vision Models| | 1099|microsoft/sample-app-aoai-chatGPT !2025-03-2817981|[PREVIEW] Sample code for a simple web chat experience targeting chatGPT through AOAI.| | 1100|AI-Citizen/SolidGPT !2025-03-2817830|Chat everything with your code repository, ask repository level code questions, and discuss your requirements. AI Scan and learning your code repository, provide you code repository level answer🧱 🧱| | 1101|YangLing0818/RPG-DiffusionMaster !2025-03-2817784|Mastering Text-to-Image Diffusion: Recaptioning, Planning, and Generating with Multimodal LLMs (PRG)| | 1102|kyegomez/BitNet !2025-03-2817710|Implementation of "BitNet: Scaling 1-bit Transformers for Large Language Models" in pytorch| | 1103|eloialonso/diamond !2025-03-2817671|DIAMOND (DIffusion As a Model Of eNvironment Dreams) is a reinforcement learning agent trained in a diffusion world model.| | 1104|flowdriveai/flowpilot !2025-03-2817250|flow-pilot is an openpilot based driver assistance system that runs on linux, windows and android powered machines.| | 1105|xlang-ai/OSWorld !2025-03-2817200|OSWorld: Benchmarking Multimodal Agents for Open-Ended Tasks in Real Computer Environments| | 1106|linyiLYi/snake-ai !2025-03-2817031|An AI agent that beats the classic game "Snake".| | 1107|baaivision/Emu !2025-03-2816991|Emu Series: Generative Multimodal Models from BAAI| | 1108|kevmo314/scuda !2025-03-2816870|SCUDA is a GPU over IP bridge allowing GPUs on remote machines to be attached to CPU-only machines.| | 1109|SharifiZarchi/IntroductiontoMachineLearning !2025-03-2816701|دوره‌ی مقدمه‌ای بر یادگیری ماشین، برای دانشجویان| | 1110|google/maxtext !2025-03-2816670|A simple, performant and scalable Jax LLM!| | 1111|ml-explore/mlx-swift-examples !2025-03-2816471|Examples using MLX Swift| | 1112|unitreerobotics/unitreerlgym !2025-03-2816256|| | 1113|collabora/WhisperFusion !2025-03-2815901|WhisperFusion builds upon the capabilities of WhisperLive and WhisperSpeech to provide a seamless conversations with an AI.| | 1114|lichao-sun/Mora !2025-03-2815520|Mora: More like Sora for Generalist Video Generation| | 1115|GoogleCloudPlatform/localllm !2025-03-2815370|Run LLMs locally on Cloud Workstations| | 1116|TencentARC/BrushNet !2025-03-2815330|The official implementation of paper "BrushNet: A Plug-and-Play Image Inpainting Model with Decomposed Dual-Branch Diffusion"| | 1117|ai-christianson/RA.Aid !2025-03-2815288|Develop software autonomously.| | 1118|stephansturges/WALDO !2025-03-2815170|Whereabouts Ascertainment for Low-lying Detectable Objects. The SOTA in FOSS AI for drones!| | 1119|skills/copilot-codespaces-vscode !2025-03-2815112|Develop with AI-powered code suggestions using GitHub Copilot and VS Code| | 1120|andrewnguonly/Lumos !2025-03-2814920|A RAG LLM co-pilot for browsing the web, powered by local LLMs| | 1121|TeamNewPipe/NewPipeExtractor !2025-03-2814811|NewPipe's core library for extracting data from streaming sites| | 1122|mhamilton723/FeatUp !2025-03-2814770|Official code for "FeatUp: A Model-Agnostic Frameworkfor Features at Any Resolution" ICLR 2024| | 1123|AnswerDotAI/fsdpqlora !2025-03-2814671|Training LLMs with QLoRA + FSDP| | 1124|jgravelle/AutoGroq !2025-03-2814330|| | 1125|OpenGenerativeAI/llm-colosseum !2025-03-2814130|Benchmark LLMs by fighting in Street Fighter 3! The new way to evaluate the quality of an LLM| | 1126|microsoft/vscode-ai-toolkit !2025-03-2814000|| | 1127|McGill-NLP/webllama !2025-03-2813930|Llama-3 agents that can browse the web by following instructions and talking to you| | 1128|lucidrains/self-rewarding-lm-pytorch !2025-03-2813760|Implementation of the training framework proposed in Self-Rewarding Language Model, from MetaAI| | 1129|ishaan1013/sandbox !2025-03-2813650|A cloud-based code editing environment with an AI copilot and real-time collaboration.| | 1130|goatcorp/Dalamud !2025-03-2813275|FFXIV plugin framework and API| | 1131|Lightning-AI/lightning-thunder !2025-03-2813151|Make PyTorch models Lightning fast! Thunder is a source to source compiler for PyTorch. It enables using different hardware executors at once.| | 1132|PKU-YuanGroup/MagicTime !2025-03-2813052|MagicTime: Time-lapse Video Generation Models as Metamorphic Simulators| | 1133|SakanaAI/evolutionary-model-merge !2025-03-2813000|Official repository of Evolutionary Optimization of Model Merging Recipes| | 1134|a-real-ai/pywinassistant !2025-03-2812950|The first open source Large Action Model generalist Artificial Narrow Intelligence that controls completely human user interfaces by only using natural language. PyWinAssistant utilizes Visualization-of-Thought Elicits Spatial Reasoning in Large Language Models.| | 1135|TraceMachina/nativelink !2025-03-2812630|NativeLink is an open source high-performance build cache and remote execution server, compatible with Bazel, Buck2, Reclient, and other RBE-compatible build systems. It offers drastically faster builds, reduced test flakiness, and significant infrastructure cost savings.| | 1136|MLSysOps/MLE-agent !2025-03-2812500|🤖 MLE-Agent: Your intelligent companion for seamless AI engineering and research. 🔍 Integrate with arxiv and paper with code to provide better code/research plans 🧰 OpenAI, Ollama, etc supported. 🎆 Code RAG| | 1137|wpilibsuite/allwpilib !2025-03-2811610|Official Repository of WPILibJ and WPILibC| | 1138|elfvingralf/macOSpilot-ai-assistant !2025-03-2811470|Voice + Vision powered AI assistant that answers questions about any application, in context and in audio.| | 1139|langchain-ai/langchain-extract !2025-03-2811210|🦜⛏️ Did you say you like data?| | 1140|FoundationVision/GLEE !2025-03-2811120|【CVPR2024】GLEE: General Object Foundation Model for Images and Videos at Scale| | 1141|Profluent-AI/OpenCRISPR !2025-03-2810990|AI-generated gene editing systems| | 1142|zju3dv/EasyVolcap !2025-03-2810821|[SIGGRAPH Asia 2023 (Technical Communications)] EasyVolcap: Accelerating Neural Volumetric Video Research| | 1143|PaddlePaddle/PaddleHelix !2025-03-2810560|Bio-Computing Platform Featuring Large-Scale Representation Learning and Multi-Task Deep Learning “螺旋桨”生物计算工具集| | 1144|myshell-ai/JetMoE !2025-03-289800|Reaching LLaMA2 Performance with 0.1M Dollars| | 1145|likejazz/llama3.np !2025-03-289770|llama3.np is pure NumPy implementation for Llama 3 model.| | 1146|mustafaaljadery/gemma-2B-10M !2025-03-289500|Gemma 2B with 10M context length using Infini-attention.| | 1147|HITsz-TMG/FilmAgent !2025-03-289382|Resources of our paper "FilmAgent: A Multi-Agent Framework for End-to-End Film Automation in Virtual 3D Spaces". New versions in the making!| | 1148|aws-samples/amazon-bedrock-samples !2025-03-289362|This repository contains examples for customers to get started using the Amazon Bedrock Service. This contains examples for all available foundational models| | 1149|Akkudoktor-EOS/EOS !2025-03-2893154|This repository features an Energy Optimization System (EOS) that optimizes energy distribution, usage for batteries, heat pumps& household devices. It includes predictive models for electricity prices (planned), load forecasting& dynamic optimization to maximize energy efficiency & minimize costs. Founder Dr. Andreas Schmitz (YouTube @akkudoktor)| Tip: | symbol| rule | | :----| :---- | |🔥 | 256 1k| |!green-up-arrow.svg !red-down-arrow | ranking up / down| |⭐ | on trending page today| [Back to Top] Tools | No. | Tool | Description | | ----:|:----------------------------------------------- |:------------------------------------------------------------------------------------------- | | 1 | ChatGPT | A sibling model to InstructGPT, which is trained to follow instructions in a prompt and provide a detailed response | | 2 | DALL·E 2 | Create original, realistic images and art from a text description | | 3 | Murf AI | AI enabled, real people's voices| | 4 | Midjourney | An independent research lab that produces an artificial intelligence program under the same name that creates images from textual descriptions, used in Discord | 5 | Make-A-Video | Make-A-Video is a state-of-the-art AI system that generates videos from text | | 6 | Creative Reality™ Studio by D-ID| Use generative AI to create future-facing videos| | 7 | chat.D-ID| The First App Enabling Face-to-Face Conversations with ChatGPT| | 8 | Notion AI| Access the limitless power of AI, right inside Notion. Work faster. Write better. Think bigger. | | 9 | Runway| Text to Video with Gen-2 | | 10 | Resemble AI| Resemble’s AI voice generator lets you create human–like voice overs in seconds | | 11 | Cursor| Write, edit, and chat about your code with a powerful AI | | 12 | Hugging Face| Build, train and deploy state of the art models powered by the reference open source in machine learning | | 13 | Claude | A next-generation AI assistant for your tasks, no matter the scale | | 14 | Poe| Poe lets you ask questions, get instant answers, and have back-and-forth conversations with AI. Gives access to GPT-4, gpt-3.5-turbo, Claude from Anthropic, and a variety of other bots| [Back to Top] Websites | No. | WebSite |Description | | ----:|:------------------------------------------ |:---------------------------------------------------------------------------------------- | | 1 | OpenAI | An artificial intelligence research lab | | 2 | Bard | Base Google's LaMDA chatbots and pull from internet | | 3 | ERNIE Bot | Baidu’s new generation knowledge-enhanced large language model is a new member of the Wenxin large model family | | 4 | DALL·E 2 | An AI system that can create realistic images and art from a description in natural language | | 5 | Whisper | A general-purpose speech recognition model | | 6| CivitAI| A platform that makes it easy for people to share and discover resources for creating AI art| | 7|D-ID| D-ID’s Generative AI enables users to transform any picture or video into extraordinary experiences| | 8| Nvidia eDiff-I| Text-to-Image Diffusion Models with Ensemble of Expert Denoisers | | 9| Stability AI| The world's leading open source generative AI company which opened source Stable Diffusion | | 10| Meta AI| Whether it be research, product or infrastructure development, we’re driven to innovate responsibly with AI to benefit the world | | 11| ANTHROPIC| AI research and products that put safety at the frontier | [Back to Top] Reports&Papers | No. | Report&Paper | Description | |:---- |:-------------------------------------------------------------------------------------------------------------- |:---------------------------------------------------- | | 1 | GPT-4 Technical Report | GPT-4 Technical Report | | 2 | mli/paper-reading | Deep learning classics and new papers are read carefully paragraph by paragraph. | | 3 | labmlai/annotateddeeplearningpaperimplementations| A collection of simple PyTorch implementations of neural networks and related algorithms, which are documented with explanations | | 4 | Visual ChatGPT: Talking, Drawing and Editing with Visual Foundation Models | Talking, Drawing and Editing with Visual Foundation Models | | 5 | OpenAI Research | The latest research report and papers from OpenAI | | 6 | Make-A-Video: Text-to-Video Generation without Text-Video Data|Meta's Text-to-Video Generation| | 7 | eDiff-I: Text-to-Image Diffusion Models with Ensemble of Expert Denoisers| Nvidia eDiff-I - New generation of generative AI content creation tool | | 8 | Training an Assistant-style Chatbot with Large Scale Data Distillation from GPT-3.5-Turbo | 2023 GPT4All Technical Report | | 9 | Segment Anything| Meta Segment Anything | | 10 | LLaMA: Open and Efficient Foundation Language Models| LLaMA: a collection of foundation language models ranging from 7B to 65B parameters| | 11 | papers-we-love/papers-we-love |Papers from the computer science community to read and discuss| | 12 | CVPR 2023 papers |The most exciting and influential CVPR 2023 papers| [Back to Top] Tutorials | No. | Tutorial | Description| |:---- |:---------------------------------------------------------------- | --- | | 1 | Coursera - Machine Learning | The Machine Learning Specialization Course taught by Dr. Andrew Ng| | 2 | microsoft/ML-For-Beginners | 12 weeks, 26 lessons, 52 quizzes, classic Machine Learning for all| | 3 | ChatGPT Prompt Engineering for Developers | This short course taught by Isa Fulford (OpenAI) and Andrew Ng (DeepLearning.AI) will teach how to use a large language model (LLM) to quickly build new and powerful applications | | 4 | Dive into Deep Learning |Targeting Chinese readers, functional and open for discussion. The Chinese and English versions are used for teaching in over 400 universities across more than 60 countries | | 5 | AI Expert Roadmap | Roadmap to becoming an Artificial Intelligence Expert in 2022 | | 6 | Computer Science courses |List of Computer Science courses with video lectures| | 7 | Machine Learning with Python | Machine Learning with Python Certification on freeCodeCamp| | 8 | Building Systems with the ChatGPT API | This short course taught by Isa Fulford (OpenAI) and Andrew Ng (DeepLearning.AI), you will learn how to automate complex workflows using chain calls to a large language model| | 9 | LangChain for LLM Application Development | This short course taught by Harrison Chase (Co-Founder and CEO at LangChain) and Andrew Ng. you will gain essential skills in expanding the use cases and capabilities of language models in application development using the LangChain framework| | 10 | How Diffusion Models Work | This short course taught by Sharon Zhou (CEO, Co-founder, Lamini). you will gain a deep familiarity with the diffusion process and the models which carry it out. More than simply pulling in a pre-built model or using an API, this course will teach you to build a diffusion model from scratch| | 11 | Free Programming Books For AI |📚 Freely available programming books for AI | | 12 | microsoft/AI-For-Beginners |12 Weeks, 24 Lessons, AI for All!| | 13 | hemansnation/God-Level-Data-Science-ML-Full-Stack |A collection of scientific methods, processes, algorithms, and systems to build stories & models. This roadmap contains 16 Chapters, whether you are a fresher in the field or an experienced professional who wants to transition into Data Science & AI| | 14 | datawhalechina/prompt-engineering-for-developers |Chinese version of Andrew Ng's Big Model Series Courses, including "Prompt Engineering", "Building System", and "LangChain"| | 15 | ossu/computer-science |🎓 Path to a free self-taught education in Computer Science!| | 16 | microsoft/Data-Science-For-Beginners | 10 Weeks, 20 Lessons, Data Science for All! | |17 |jwasham/coding-interview-university !2023-09-29268215336 |A complete computer science study plan to become a software engineer.| [Back to Top] Thanks If this project has been helpful to you in any way, please give it a ⭐️ by clicking on the star.

#github#aitreasurebox

github

0.527

0.11594284776995417

robocorp•Mar 28, 2025

rpaframework

RPA Framework ============= REQUEST for user input! We are looking at improving our keyword usage to cover situations where developer might be struggling to smoothly write task for a Robot. Describe the situation where your implementation speed slows due to the lack of easier syntax. Comment HERE _ .. contents:: Table of Contents :local: :depth: 1 .. include-docs-readme Introduction RPA Framework is a collection of open-source libraries and tools for Robotic Process Automation (RPA), and it is designed to be used with both Robot Framework and Python. The goal is to offer well-documented and actively maintained core libraries for Software Robot Developers. Learn more about RPA at Robocorp Documentation_. The project is: 100% Open Source Sponsored by Robocorp_ Optimized for Robocorp Control Room and Developer Tools Accepting external contributions .. _Robot Framework: https://robotframework.org .. _Robot Framework Foundation: https://robotframework.org/foundation/ .. _Python: https://www.python.org/ .. _Robocorp: https://robocorp.com .. _Robocorp Documentation: https://robocorp.com/docs-robot-framework .. _Control Room: https://robocorp.com/docs/control-room .. _Developer Tools: https://robocorp.com/downloads .. _Installing Python Packages: https://robocorp.com/docs/setup/installing-python-package-dependencies Links ^^^^^ Homepage: `_ Documentation: _ PyPI: _ Release notes: _ RSS feed: _ .. image:: https://img.shields.io/github/actions/workflow/status/robocorp/rpaframework/main.yaml?style=for-the-badge :target: https://github.com/robocorp/rpaframework/actions/workflows/main.yaml :alt: Status .. image:: https://img.shields.io/pypi/dw/rpaframework?style=for-the-badge :target: https://pypi.python.org/pypi/rpaframework :alt: rpaframework .. image:: https://img.shields.io/pypi/l/rpaframework.svg?style=for-the-badge&color=brightgreen :target: http://www.apache.org/licenses/LICENSE-2.0.html :alt: License Packages .. image:: https://img.shields.io/pypi/v/rpaframework.svg?label=rpaframework&style=for-the-badge :target: https://pypi.python.org/pypi/rpaframework :alt: rpaframework latest version .. image:: https://img.shields.io/pypi/v/rpaframework-assistant.svg?label=rpaframework-assistant&style=for-the-badge :target: https://pypi.python.org/pypi/rpaframework-assistant :alt: rpaframework-assistant latest version .. image:: https://img.shields.io/pypi/v/rpaframework-aws.svg?label=rpaframework-aws&style=for-the-badge :target: https://pypi.python.org/pypi/rpaframework-aws :alt: rpaframework-aws latest version .. image:: https://img.shields.io/pypi/v/rpaframework-core.svg?label=rpaframework-core&style=for-the-badge :target: https://pypi.python.org/pypi/rpaframework-core :alt: rpaframework-core latest version .. image:: https://img.shields.io/pypi/v/rpaframework-google.svg?label=rpaframework-google&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-google :alt: rpaframework-google latest version .. image:: https://img.shields.io/pypi/v/rpaframework-hubspot.svg?label=rpaframework-hubspot&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-hubspot :alt: rpaframework-hubspot latest version .. image:: https://img.shields.io/pypi/v/rpaframework-openai.svg?label=rpaframework-openai&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-openai :alt: rpaframework-openai latest version .. image:: https://img.shields.io/pypi/v/rpaframework-pdf.svg?label=rpaframework-pdf&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-pdf :alt: rpaframework-pdf latest version .. image:: https://img.shields.io/pypi/v/rpaframework-recognition.svg?label=rpaframework-recognition&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-recognition :alt: rpaframework-recognition latest version .. image:: https://img.shields.io/pypi/v/rpaframework-windows.svg?label=rpaframework-windows&style=for-the-badge&color=blue :target: https://pypi.python.org/pypi/rpaframework-windows :alt: rpaframework-windows latest version From the above packages, rpaframework-core and rpaframework-recognition are support packages, which alone do not contain any libraries. Libraries The RPA Framework project currently includes the following libraries: The x in the PACKAGE column means that library is included in the rpaframework package and for example. x,pdf means that RPA.PDF library is provided in both the rpaframework and rpaframework-pdf packages. +----------------------------+-------------------------------------------------------+------------------------+ | LIBRARY NAME | DESCRIPTION | PACKAGE | +----------------------------+-------------------------------------------------------+------------------------+ | Archive_ | Archiving TAR and ZIP files | x | +----------------------------+-------------------------------------------------------+------------------------+ | Assistant_ | Display information to a user and request input. | assistant | +----------------------------+-------------------------------------------------------+------------------------+ | Browser.Selenium_ | Control browsers and automate the web | x | +----------------------------+-------------------------------------------------------+------------------------+ | Browser.Playwright_ | Newer way to control browsers | special (more below) | +----------------------------+-------------------------------------------------------+------------------------+ | Calendar_ | For date and time manipulations | x | +----------------------------+-------------------------------------------------------+------------------------+ | Cloud.AWS_ | Use Amazon AWS services | x,aws | +----------------------------+-------------------------------------------------------+------------------------+ | Cloud.Azure_ | Use Microsoft Azure services | x | +----------------------------+-------------------------------------------------------+------------------------+ | Cloud.Google_ | Use Google Cloud services | google | +----------------------------+-------------------------------------------------------+------------------------+ | Crypto_ | Common hashing and encryption operations | x | +----------------------------+-------------------------------------------------------+------------------------+ | Database_ | Interact with databases | x | +----------------------------+-------------------------------------------------------+------------------------+ | Desktop_ | Cross-platform desktop automation | x | +----------------------------+-------------------------------------------------------+------------------------+ | Desktop.Clipboard_ | Interact with the system clipboard | x | +----------------------------+-------------------------------------------------------+------------------------+ | Desktop.OperatingSystem_ | Read OS information and manipulate processes | x | +----------------------------+-------------------------------------------------------+------------------------+ | DocumentAI_ | Intelligent Document Processing wrapper | x | +----------------------------+-------------------------------------------------------+------------------------+ | DocumentAI.Base64AI_ | Intelligent Document Processing service | x | +----------------------------+-------------------------------------------------------+------------------------+ | DocumentAI.Nanonets_ | Intelligent Document Processing service | x | +----------------------------+-------------------------------------------------------+------------------------+ | Email.Exchange_ | E-Mail operations (Exchange protocol) | x | +----------------------------+-------------------------------------------------------+------------------------+ | Email.ImapSmtp_ | E-Mail operations (IMAP & SMTP) | x | +----------------------------+-------------------------------------------------------+------------------------+ | Excel.Application_ | Control the Excel desktop application | x | +----------------------------+-------------------------------------------------------+------------------------+ | Excel.Files_ | Manipulate Excel files directly | x | +----------------------------+-------------------------------------------------------+------------------------+ | FileSystem_ | Read and manipulate files and paths | x | +----------------------------+-------------------------------------------------------+------------------------+ | FTP_ | Interact with FTP servers | x | +----------------------------+-------------------------------------------------------+------------------------+ | HTTP_ | Interact directly with web APIs | x | +----------------------------+-------------------------------------------------------+------------------------+ | Hubspot_ | Access HubSpot CRM data objects | hubspot | +----------------------------+-------------------------------------------------------+------------------------+ | Images_ | Manipulate images | x | +----------------------------+-------------------------------------------------------+------------------------+ | JavaAccessBridge_ | Control Java applications | x | +----------------------------+-------------------------------------------------------+------------------------+ | JSON_ | Manipulate JSON objects | x | +----------------------------+-------------------------------------------------------+------------------------+ | MFA_ | Authenticate using one-time passwords (OTP) & OAuth2 | x | +----------------------------+-------------------------------------------------------+------------------------+ | Notifier_ | Notify messages using different services | x | +----------------------------+-------------------------------------------------------+------------------------+ | OpenAI_ | Artificial Intelligence service | openai | +----------------------------+-------------------------------------------------------+------------------------+ | Outlook.Application_ | Control the Outlook desktop application | x | +----------------------------+-------------------------------------------------------+------------------------+ | PDF_ | Read and create PDF documents | x,pdf | +----------------------------+-------------------------------------------------------+------------------------+ | Robocorp.Process_ | Use the Robocorp Process API | x | +----------------------------+-------------------------------------------------------+------------------------+ | Robocorp.WorkItems_ | Use the Robocorp Work Items API | x | +----------------------------+-------------------------------------------------------+------------------------+ | Robocorp.Vault_ | Use the Robocorp Secrets API | x | +----------------------------+-------------------------------------------------------+------------------------+ | Robocorp.Storage_ | Use the Robocorp Asset Storage API | x | +----------------------------+-------------------------------------------------------+------------------------+ | Salesforce_ | Salesforce operations | x | +----------------------------+-------------------------------------------------------+------------------------+ | SAP_ | Control SAP GUI desktop client | x | +----------------------------+-------------------------------------------------------+------------------------+ | Smartsheet_ | Access Smartsheet sheets | x | +----------------------------+-------------------------------------------------------+------------------------+ | Tables_ | Manipulate, sort, and filter tabular data | x | +----------------------------+-------------------------------------------------------+------------------------+ | Tasks_ | Control task execution | x | +----------------------------+-------------------------------------------------------+------------------------+ | Twitter_ | Twitter API interface | x | +----------------------------+-------------------------------------------------------+------------------------+ | Windows_ | Alternative library for Windows automation | x,windows | +----------------------------+-------------------------------------------------------+------------------------+ | Word.Application_ | Control the Word desktop application | x | +----------------------------+-------------------------------------------------------+------------------------+ .. _Archive: https://rpaframework.org/libraries/archive/ .. _Assistant: https://rpaframework.org/libraries/assistant/ .. Browser.Playwright: https://rpaframework.org/libraries/browserplaywright/ .. Browser.Selenium: https://rpaframework.org/libraries/browserselenium/ .. _Calendar: https://rpaframework.org/libraries/calendar/ .. Cloud.AWS: https://rpaframework.org/libraries/cloudaws/ .. Cloud.Azure: https://rpaframework.org/libraries/cloudazure/ .. Cloud.Google: https://rpaframework.org/libraries/cloudgoogle/ .. _Crypto: https://rpaframework.org/libraries/crypto/ .. _Database: https://rpaframework.org/libraries/database/ .. _Desktop: https://rpaframework.org/libraries/desktop/ .. Desktop.Clipboard: https://rpaframework.org/libraries/desktopclipboard/ .. Desktop.Operatingsystem: https://rpaframework.org/libraries/desktopoperatingsystem/ .. _DocumentAI: https://rpaframework.org/libraries/documentai .. DocumentAI.Base64AI: https://rpaframework.org/libraries/documentaibase64ai/ .. DocumentAI.Nanonets: https://rpaframework.org/libraries/documentainanonets/ .. Email.Exchange: https://rpaframework.org/libraries/emailexchange/ .. Email.ImapSmtp: https://rpaframework.org/libraries/emailimapsmtp/ .. Excel.Application: https://rpaframework.org/libraries/excelapplication/ .. Excel.Files: https://rpaframework.org/libraries/excelfiles/ .. _FileSystem: https://rpaframework.org/libraries/filesystem/ .. _FTP: https://rpaframework.org/libraries/ftp/ .. _HTTP: https://rpaframework.org/libraries/http/ .. _Hubspot: https://rpaframework.org/libraries/hubspot/ .. _Images: https://rpaframework.org/libraries/images/ .. _JavaAccessBridge: https://rpaframework.org/libraries/javaaccessbridge/ .. _JSON: https://rpaframework.org/libraries/json/ .. _MFA: https://rpaframework.org/libraries/mfa/ .. _Notifier: https://rpaframework.org/libraries/notifier/ .. _OpenAI: https://rpaframework.org/libraries/openai/ .. Outlook.Application: https://rpaframework.org/libraries/outlookapplication/ .. _PDF: https://rpaframework.org/libraries/pdf/ .. Robocorp.Process: https://rpaframework.org/libraries/robocorpprocess/ .. Robocorp.WorkItems: https://rpaframework.org/libraries/robocorpworkitems/ .. Robocorp.Vault: https://rpaframework.org/libraries/robocorpvault/ .. Robocorp.Storage: https://rpaframework.org/libraries/robocorpstorage/ .. _Salesforce: https://rpaframework.org/libraries/salesforce/ .. _SAP: https://rpaframework.org/libraries/sap/ .. _Smartsheet: https://rpaframework.org/libraries/smartsheet/ .. _Tables: https://rpaframework.org/libraries/tables/ .. _Tasks: https://rpaframework.org/libraries/tasks/ .. _Twitter: https://rpaframework.org/libraries/twitter/ .. _Windows: https://rpaframework.org/libraries/windows/ .. Word.Application: https://rpaframework.org/libraries/wordapplication/ Installation of RPA.Browser.Playwright The RPA.Browser.Playwright at the moment requires special installation, because of the package size and the post install step it needs to be fully installed. Minimum required conda.yaml to install Playwright: .. code-block:: yaml channels: conda-forge dependencies: python=3.10.14 nodejs=22.9.0 pip=24.0 pip: robotframework-browser==18.8.1 rpaframework==28.6.3 rccPostInstall: rfbrowser init Installation Learn about installing Python packages at Installing Python Packages_. Default installation method with Robocorp Developer Tools_ using conda.yaml: .. code-block:: yaml channels: conda-forge dependencies: python=3.10.14 pip=24.0 pip: rpaframework==28.6.3 To install all extra packages (including Playwright dependencies), you can use: .. code-block:: yaml channels: conda-forge dependencies: python=3.10.14 tesseract=5.4.1 nodejs=22.9.0 pip=24.0 pip: robotframework-browser==18.8.1 rpaframework==28.6.3 rpaframework-aws==5.3.3 rpaframework-google==9.0.2 rpaframework-recognition==5.2.5 rccPostInstall: rfbrowser init Separate installation of AWS, PDF and Windows libraries without the main rpaframework: .. code-block:: yaml channels: conda-forge dependencies: python=3.10.14 pip=24.0 pip: rpaframework-aws==5.3.3 included in the rpaframework as an extra rpaframework-pdf==7.3.3 included in the rpaframework by default rpaframework-windows==7.5.2 included in the rpaframework by default Installation method with pip using Python venv_: .. code-block:: shell python -m venv .venv source .venv/bin/activate pip install rpaframework .. note:: Python 3.8 or higher is required Example After installation the libraries can be directly imported inside Robot Framework_: .. code:: robotframework Settings Library RPA.Browser.Selenium Tasks Login as user Open available browser https://example.com Input text id:user-name ${USERNAME} Input text id:password ${PASSWORD} The libraries are also available inside Python_: .. code:: python from RPA.Browser.Selenium import Selenium lib = Selenium() lib.openavailablebrowser("https://example.com") lib.input_text("id:user-name", username) lib.input_text("id:password", password) Support and contact rpaframework.org _ for library documentation Robocorp Documentation_ for guides and tutorials #rpaframework channel in Robot Framework Slack_ if you have open questions or want to contribute Communicate with your fellow Software Robot Developers and Robocorp experts at Robocorp Developers Slack_ .. _Robot Framework Slack: https://robotframework-slack-invite.herokuapp.com/ .. _Robocorp Developers Slack: https://robocorp-developers.slack.com Contributing Found a bug? Missing a critical feature? Interested in contributing? Head over to the Contribution guide _ to see where to get started. Development Repository development is Python_ based and requires at minimum Python version 3.8+ installed on the development machine. The default Python version used in the Robocorp Robot template is 3.10.14 so it is a good choice for the version to install. Not recommended versions are 3.7.6 and 3.8.1, because they have issues with some of the dependencies related to rpaframework. At the time the newer Python versions starting from 3.12 are also not recommended, because some of the dependencies might cause issues. Repository development tooling is based on poetry and invoke. Poetry is the underlying tool used for compiling, building and running the package. Invoke is used for scripting purposes, for example for linting, testing and publishing tasks. Before writing any code, please read and acknowledge our extensive Dev Guide_. .. _Dev Guide: https://github.com/robocorp/rpaframework/blob/master/docs/source/contributing/development.md First steps to start developing: initial poetry configuration .. code:: shell poetry config virtualenvs.path null poetry config virtualenvs.in-project true poetry config repositories.devpi "https://devpi.robocorp.cloud/ci/test" git clone the repository #. create a new Git branch or switch to correct branch or stay in master branch some branch naming conventions feature/name-of-feature, hotfix/name-of-the-issue, release/number-of-release #. poetry install which install package with its dependencies into the .venv directory of the package, for example packages/main/.venv #. if testing against Robocorp Robot which is using devdata/env.json set environment variables or poetry build and use resulting .whl file (in the dist/ directory) in the Robot conda.yaml or poetry build and push resulting .whl file (in the dist/ directory) into a repository and use raw url to include it in the Robot conda.yaml another possibility for Robocorp internal development is to use Robocorp devpi instance, by poetry publish --ci and point conda.yaml to use rpaframework version in devpi #. poetry run python -m robot common ROBOT_ARGS from Robocorp Robot template: --report NONE --outputdir output --logtitle "Task log" #. poetry run python #. invoke lint to make sure that code formatting is according to rpaframework repository guidelines. It is possible and likely that Github action will fail the if developer has not linted the code changes. Code formatting is based on black and flake8 and those are run with the invoke lint. #. the library documentation can be created in the repository root (so called "meta" package level). The documentation is built by the docgen tools using the locally installed version of the project, local changes for the main package will be reflected each time you generate the docs, but if you want to see local changes for optional packages, you must utilize invoke install-local --package using the appropriate package name (e.g., rpaframework-aws). This will reinstall that package as a local editable version instead of from PyPI. Multiple such packages can be added by repeating the use of the --package option. In order to reset this, use invoke install --reset. poetry update and/or invoke install-local --package make docs open docs/build/html/index.html with the browser to view the changes or execute make local and navigate to localhost:8000 to view docs as a live local webpage. .. code-block:: toml Before [tool.poetry.dependencies] python = "^3.8" rpaframework = { path = "packages/main", extras = ["cv", "playwright", "aws"] } rpaframework-google = "^4.0.0" rpaframework-windows = "^4.0.0" After [tool.poetry.dependencies] python = "^3.8" rpaframework = { path = "packages/main", extras = ["cv", "playwright"] } rpaframework-aws = { path = "packages/aws" } rpaframework-google = "^4.0.0" rpaframework-windows = "^4.0.0" #. invoke test (this will run both Python unittests and robotframework tests defined in the packages tests/ directory) to run specific Python test: poetry run pytest path/to/test.py::test_function to run specific Robotframework test: inv testrobot -r -t #. git commit changes #. git push changes to remote #. create pull request from the branch describing changes included in the description #. update docs/source/releasenotes.rst with changes (commit and push) Packaging and publishing are done after changes have been merged into master branch. All the following steps should be done within master branch. #. git pull latest changes into master branch #. in the package directory containing changes execute invoke lint and invoke test #. update pyproject.toml with new version according to semantic versioning #. update docs/source/releasenotes.rst with changes #. in the repository root (so called "meta" package level) run command poetry update #. git commit changed poetry.lock files (on meta and target package level), releasenotes.rst and pyproject.toml with message "PACKAGE. version x.y.z" #. git push #. invoke publish after Github action on master branch is all green Some recommended tools for development Visual Studio Code_ as a code editor with following extensions: Sema4.ai_ Robot Framework Language Server_ GitLens_ Python extension_ GitHub Desktop_ will make version management less prone to errors .. _poetry: https://python-poetry.org .. _invoke: https://www.pyinvoke.org .. _Visual Studio Code: https://code.visualstudio.com .. _GitHub Desktop: https://desktop.github.com .. _Sema4.ai: https://marketplace.visualstudio.com/items?itemName=sema4ai.sema4ai .. _Robot Framework Language Server: https://marketplace.visualstudio.com/items?itemName=robocorp.robotframework-lsp .. _GitLens: https://marketplace.visualstudio.com/items?itemName=eamodio.gitlens .. _Python extension: https://marketplace.visualstudio.com/items?itemName=ms-python.python .. _black: https://pypi.org/project/black/ .. _flake8: https://pypi.org/project/flake8/ .. _venv: https://docs.python.org/3/library/venv.html License This project is open-source and licensed under the terms of the Apache License 2.0 `_.

#github#rpaframework

github

0.545

0.10175553624190911

obsei•Mar 27, 2025

obsei

Note: Obsei is still in alpha stage hence carefully use it in Production. Also, as it is constantly undergoing development hence master branch may contain many breaking changes. Please use released version. Obsei (pronounced "Ob see" | /əb-'sē/) is an open-source, low-code, AI powered automation tool. Obsei consists of - Observer: Collect unstructured data from various sources like tweets from Twitter, Subreddit comments on Reddit, page post's comments from Facebook, App Stores reviews, Google reviews, Amazon reviews, News, Website, etc. Analyzer: Analyze unstructured data collected with various AI tasks like classification, sentiment analysis, translation, PII, etc. Informer: Send analyzed data to various destinations like ticketing platforms, data storage, dataframe, etc so that the user can take further actions and perform analysis on the data. All the Observers can store their state in databases (Sqlite, Postgres, MySQL, etc.), making Obsei suitable for scheduled jobs or serverless applications. !Obsei diagram Future direction - Text, Image, Audio, Documents and Video oriented workflows Collect data from every possible private and public channels Add every possible workflow to an AI downstream application to automate manual cognitive workflows Use cases Obsei use cases are following, but not limited to - Social listening: Listening about social media posts, comments, customer feedback, etc. Alerting/Notification: To get auto-alerts for events such as customer complaints, qualified sales leads, etc. Automatic customer issue creation based on customer complaints on Social Media, Email, etc. Automatic assignment of proper tags to tickets based content of customer complaint for example login issue, sign up issue, delivery issue, etc. Extraction of deeper insight from feedbacks on various platforms Market research Creation of dataset for various AI tasks Many more based on creativity 💡 Installation Prerequisite Install the following (if not present already) - Install Python 3.7+ Install PIP Install Obsei You can install Obsei either via PIP or Conda based on your preference. To install latest released version - Install from master branch (if you want to try the latest features) - Note: all option will install all the dependencies which might not be needed for your workflow, alternatively following options are available to install minimal dependencies as per need - pip install obsei[source]: To install dependencies related to all observers pip install obsei[sink]: To install dependencies related to all informers pip install obsei[analyzer]: To install dependencies related to all analyzers, it will install pytorch as well pip install obsei[twitter-api]: To install dependencies related to Twitter observer pip install obsei[google-play-scraper]: To install dependencies related to Play Store review scrapper observer pip install obsei[google-play-api]: To install dependencies related to Google official play store review API based observer pip install obsei[app-store-scraper]: To install dependencies related to Apple App Store review scrapper observer pip install obsei[reddit-scraper]: To install dependencies related to Reddit post and comment scrapper observer pip install obsei[reddit-api]: To install dependencies related to Reddit official api based observer pip install obsei[pandas]: To install dependencies related to TSV/CSV/Pandas based observer and informer pip install obsei[google-news-scraper]: To install dependencies related to Google news scrapper observer pip install obsei[facebook-api]: To install dependencies related to Facebook official page post and comments api based observer pip install obsei[atlassian-api]: To install dependencies related to Jira official api based informer pip install obsei[elasticsearch]: To install dependencies related to elasticsearch informer pip install obsei[slack-api]:To install dependencies related to Slack official api based informer You can also mix multiple dependencies together in single installation command. For example to install dependencies Twitter observer, all analyzer, and Slack informer use following command - How to use Expand the following steps and create a workflow - Step 1: Configure Source/Observer Twitter Youtube Scrapper Facebook Email Google Maps Reviews Scrapper AppStore Reviews Scrapper Play Store Reviews Scrapper Reddit Reddit Scrapper Note: Reddit heavily rate limit scrappers, hence use it to fetch small data during long period Google News Web Crawler Pandas DataFrame Step 2: Configure Analyzer Note: To run transformers in an offline mode, check transformers offline mode. Some analyzer support GPU and to utilize pass device parameter. List of possible values of device parameter (default value auto): auto: GPU (cuda:0) will be used if available otherwise CPU will be used cpu: CPU will be used cuda:{id} - GPU will be used with provided CUDA device id Text Classification Text classification: Classify text into user provided categories. Sentiment Analyzer Sentiment Analyzer: Detect the sentiment of the text. Text classification can also perform sentiment analysis but if you don't want to use heavy-duty NLP model then use less resource hungry dictionary based Vader Sentiment detector. NER Analyzer NER (Named-Entity Recognition) Analyzer: Extract information and classify named entities mentioned in text into pre-defined categories such as person names, organizations, locations, medical codes, time expressions, quantities, monetary values, percentages, etc Translator PII Anonymizer Dummy Analyzer Dummy Analyzer: Does nothing. Its simply used for transforming the input (TextPayload) to output (TextPayload) and adding the user supplied dummy data. Step 3: Configure Sink/Informer Slack Zendesk Jira ElasticSearch Http Pandas DataFrame Logger This is useful for testing and dry running the pipeline. Step 4: Join and create workflow source will fetch data from the selected source, then feed it to the analyzer for processing, whose output we feed into a sink to get notified at that sink. Step 5: Execute workflow Copy the code snippets from Steps 1 to 4 into a python file, for example example.py and execute the following command - Demo We have a minimal streamlit based UI that you can use to test Obsei. !Screenshot Watch UI demo video Check demo at (Note: Sometimes the Streamlit demo might not work due to rate limiting, use the docker image (locally) in such cases.) To test locally, just run To run Obsei workflow easily using GitHub Actions (no sign ups and cloud hosting required), refer to this repo. Companies/Projects using Obsei Here are some companies/projects (alphabetical order) using Obsei. To add your company/project to the list, please raise a PR or contact us via email. Oraika: Contextually understand customer feedback 1Page: Giving a better context in meetings and calls Spacepulse: The operating system for spaces Superblog: A blazing fast alternative to WordPress and Medium Zolve: Creating a financial world beyond borders Utilize: No-code app builder for businesses with a deskless workforce Articles Sr. No. Title Author 1 AI based Comparative Customer Feedback Analysis Using Obsei Reena Bapna 2 LinkedIn App - User Feedback Analysis Himanshu Sharma Tutorials Sr. No. Workflow Colab Binder 1 Observe app reviews from Google play store, Analyze them by performing text classification and then Inform them on console via logger PlayStore Reviews → Classification → Logger 2 Observe app reviews from Google play store, PreProcess text via various text cleaning functions, Analyze them by performing text classification, Inform them to Pandas DataFrame and store resultant CSV to Google Drive PlayStore Reviews → PreProcessing → Classification → Pandas DataFrame → CSV in Google Drive 3 Observe app reviews from Apple app store, PreProcess text via various text cleaning function, Analyze them by performing text classification, Inform them to Pandas DataFrame and store resultant CSV to Google Drive AppStore Reviews → PreProcessing → Classification → Pandas DataFrame → CSV in Google Drive 4 Observe news article from Google news, PreProcess text via various text cleaning function, Analyze them via performing text classification while splitting text in small chunks and later computing final inference using given formula Google News → Text Cleaner → Text Splitter → Classification → Inference Aggregator 💡Tips: Handle large text classification via Obsei Documentation For detailed installation instructions, usages and examples, refer to our documentation. Support and Release Matrix Linux Mac Windows Remark Tests ✅ ✅ ✅ Low Coverage as difficult to test 3rd party libs PIP ✅ ✅ ✅ Fully Supported Conda ❌ ❌ ❌ Not Supported Discussion forum Discussion about Obsei can be done at community forum Changelogs Refer releases for changelogs Security Issue For any security issue please contact us via email Stargazers over time Maintainers This project is being maintained by Oraika Technologies. Lalit Pagaria and Girish Patel are maintainers of this project. License Copyright holder: Oraika Technologies Overall Apache 2.0 and you can read License file. Multiple other secondary permissive or weak copyleft licenses (LGPL, MIT, BSD etc.) for third-party components refer Attribution. To make project more commercial friendly, we void third party components which have strong copyleft licenses (GPL, AGPL etc.) into the project. Attribution This could not have been possible without these open source softwares. Contribution First off, thank you for even considering contributing to this package, every contribution big or small is greatly appreciated. Please refer our Contribution Guideline and Code of Conduct. Thanks so much to all our contributors

#github#obsei

github

0.537

0.038940878121795156

BytomDAO•Mar 14, 2025

bytom

Bytom ====== Official golang implementation of the Bytom protocol. Automated builds are available for stable releases and the unstable master branch. Binary archives are published at https://github.com/Bytom/bytom/releases. What is Bytom? Bytom is software designed to operate and connect to highly scalable blockchain networks confirming to the Bytom Blockchain Protocol, which allows partipicants to define, issue and transfer digitial assets on a multi-asset shared ledger. Please refer to the White Paper for more details. In the current state bytom is able to: Manage key, account as well as asset Send transactions, i.e., issue, spend and retire asset Installing with Homebrew Building from source Requirements Go version 1.8 or higher, with $GOPATH set to your preferred directory Installation Ensure Go with the supported version is installed properly: Get the source code Build source code When successfully building the project, the bytomd and bytomcli binary should be present in cmd/bytomd and cmd/bytomcli directory, respectively. Executables The Bytom project comes with several executables found in the cmd directory. | Command | Description | | ------------ | ------------------------------------------------------------ | | bytomd | bytomd command can help to initialize and launch bytom domain by custom parameters. bytomd --help for command line options. | | bytomcli | Our main Bytom CLI client. It is the entry point into the Bytom network (main-, test- or private net), capable of running as a full node archive node (retaining all historical state). It can be used by other processes as a gateway into the Bytom network via JSON RPC endpoints exposed on top of HTTP, WebSocket and/or IPC transports. bytomcli --help and the bytomcli Wiki page for command line options. | Running bytom Currently, bytom is still in active development and a ton of work needs to be done, but we also provide the following content for these eager to do something with bytom. This section won't cover all the commands of bytomd and bytomcli at length, for more information, please the help of every command, e.g., bytomcli help. Initialize First of all, initialize the node: There are three options for the flag --chain_id: mainnet: connect to the mainnet. testnet: connect to the testnet wisdom. solonet: standalone mode. After that, you'll see config.toml generated, then launch the node. launch available flags for bytomd node: Given the bytomd node is running, the general workflow is as follows: create key, then you can create account and asset. send transaction, i.e., build, sign and submit transaction. query all kinds of information, let's say, avaliable key, account, key, balances, transactions, etc. Dashboard Access the dashboard: In Docker Ensure your Docker version is 17.05 or higher. For the usage please refer to running-in-docker-wiki. Contributing Thank you for considering helping out with the source code! Any contributions are highly appreciated, and we are grateful for even the smallest of fixes! If you run into an issue, feel free to bytom issues in this repository. We are glad to help! License AGPL v3

#github#bytom

youtube

0.399

0.77

Cosmic Hippo•Jan 2, 2025

Best of Chillstep 2024 | Cosmic Hippo | Coding Session

You can get the artwork featured in this video as a digital download on Etsy here: https://www.etsy.com/listing/1858237715/best-of-2024 Thank you for tuning in to this selection of my most popular chillstep songs of 2024, designed to elevate your focus and creativity. Dive into an immersive experience with some of the most captivating tracks of the year, blending atmospheric beats and soothing rhythms to keep you in the zone. Whether you’re deep into a coding project, studying, or simply unwinding, this playlist will set the perfect tone for your session. Stay inspired, stay productive, and let these sounds guide your flow. Don’t forget to like, share, and subscribe for more chillstep vibes and focus-driven music from Cosmic Hippo. Tracklist 0:00 Neon Dreams From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 4:00 Crystal Nights From Playlist "Coding Alone" https://www.youtube.com/watch?v=8MUlk3qjByY&t=513s 8:01 Flowing Codes From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 11:00 Driftwood Dreams From Playlist "Coding by the Sea" https://www.youtube.com/watch?v=7dB9WI-OI8k&t=1553s 15:00 Code Flow From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 19:02 Magic in the Moonlight From Playlist "1 A.M Coding Sessions" https://www.youtube.com/watch?v=FUrRK_jMCqA&t=661s 23:06 Serene State From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 27:05 Icy Reverie From Playlist "Coding Session in the Snowy Mountains" https://www.youtube.com/watch?v=qDi65Kq88DY&t=717s 30:43 Lost Among Stars From Playlist Hyperfocus https://www.youtube.com/watch?v=wq0R46U9FpQ 34:16 Quantum Blanket From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 38:14 Echoes of Clarity From Playlist "Deep Chill" https://www.youtube.com/watch?v=tmgM00yas78&t=1447s 41:54 Ethereal Daydream From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 44:57 Snowlit Skies From Playlist " Winter Chillstep" https://www.youtube.com/watch?v=P4ZNQJyn_FA&t=91s 48:47 Neon Nights and Daydreams From Playlist "Coding All Night" https://www.youtube.com/watch?v=DayQ-a4YdSQ&t=1486s 51:04 Northern Chill From Playlist " Winter Chillstep" https://www.youtube.com/watch?v=P4ZNQJyn_FA&t=91s 54:24 Cinders in the Snow From Playlist "Broken Signal" https://www.youtube.com/watch?v=MQ0QPjl6aTs&t=14s 58:28 Voyage to Nowhere From Playlist "Infinite Focus" https://www.youtube.com/watch?v=EvcpNZHFBlQ&t=2040s 01:01:11 Almas en la Noche From Playlist "1 A.M Coding Sessions" https://www.youtube.com/watch?v=FUrRK_jMCqA&t=661s 01:04:28 Infinite Flow From playlist "3 A.M Coding Session" https://www.youtube.com/watch?v=Yd7vDterctQ 01:06:52 Xenon Lights From Playlist "Coding All Night" https://www.youtube.com/watch?v=DayQ-a4YdSQ&t=1486s 01:09:24 Galactic Journey From Playlist "Infinite Focus" https://www.youtube.com/watch?v=EvcpNZHFBlQ&t=2040s 01:11:36 Lost in the Cosmos From Playlist "Hyperfocus" https://www.youtube.com/watch?v=wq0R46U9FpQ&t=2323s 01:14:07 Siberian Silence From Playlist "Broken Signal" https://www.youtube.com/watch?v=MQ0QPjl6aTs&t=14s 01:17:48 Stardust Dreams From Playlist "Infinite Focus" https://www.youtube.com/watch?v=EvcpNZHFBlQ&t=2040s Tags: #Chillstep2024 #CodingMusic #CosmicHippo #FocusBeats #StudyMusic #RelaxingChillstep #BestOf2024 #ProductivityMusic #WorkBeats #ProgrammingPlaylist #ChillstepVibes #CreativeFocus #ElectronicBeats #codingmusic #codingsession #codingmotivation #programming #programmingbeats #chill #chillworkmusic #lofi #aesthetic #views #workinglate Disclaimer: This music has been created with the help of AI tools.

#Chillstep2024#CodingMusic#CosmicHippo