VibeBuilders.ai Logo
VibeBuilders.ai

Finally

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

Finally Launched My First App Without Any Coding Experience
reddit
LLM Vibe Score0
Human Vibe Score1
Consistent_Access844This week

Finally Launched My First App Without Any Coding Experience

About Myself I am a structural engineer that are taught to design buildings in the day and I have been dreaming forever to build a SaaS business to get out of the rat race. However, as a structural engineer, coding is definitely not something I am capable of doing (I have some simple knowledge, but its no way close to building an app) The Journey As I've mentioned, I always wanted to build a SaaS business because in my mind the business model is most attractive to me, where you only need to build once and can sell to millions. So I started off searching and exploring on the internet and my first ever "SaaS" was from Wordpress. I am buying plugin from other user and then pluggin into my own Wordpress website. It was a project management tool SaaS. I was so excited about the website and can't even sleep well at night because I'm just so hype about it. But, the reality is because this is my first ever business, I totally didn't realise about the importance of UI UX or my business differentiation, thinking that everyone will be as excited as I am. Then, I went deeper and deeper into the journey (I can write more about this in another post if anyone is interested) and finally landed on Flutterflow to create my first ever app. No Code Journey Thanks to no code builder, I never thought that a non-coder like me can ever create an app and got accepted by the App Store/Play Store. Since that I am using a low-code builder, for any specific requirement that I need that are not covered natively, I will just talk to ChatGPT and boom I pretty much got most of the answer I needed. About The App As someone that always try to keep track of my expenses, I never able to find an app that are simple and interesting enough for me to continue on the journey. I realise that I could have incorporate AI into this journey and hence there go, I created an AI Money Tracker. Let me introduce Rolly: AI Money Tracker - a new AI expense tracker where you can easily record your transactions just by chatting with our bot Rolly and it will automatically record and categorise the transaction into the most suitable category (you can also create any of your own category and it will also take care of it in consideration). I am not sharing the app link here to avoid getting ban, but feel free to search up Rolly: AI Money Tracker on either App Store on Play Store. My Learnings As someone that can't code and never imagine that I could create a production app by myself and publish it on to the App Store and Play Store. Since I am not making any money yet and just at the beginning of my entrepreneur journey, I can't give any substantial advice, all I can say is just my own learnings and feelings. My advice is if you have a dream of building a business, just go for it, don't worry about all the problems that you can think of to convince yourself not making the start at all. From my point of view, as long as you're not giving up everything (eg, putting yourself in huge debt etc), why don't just go for it and you've got nothing much to lose. You'll only lose if you never even get started. And also, I believe that creating an app is always the easiest step out of the entreprenuership journey, marketing and distribution is the key to success. Even though you've spent days and nights on it and it might mean everything to you, the truth is people don't really cares and you'll need to market for it. I am still in journey to learn how to do marketing, content, building a business and everything. I think this is just a very beginning of my journey and hopefully there's more interesting one to share further down the road.

Finally Launched My First App Without Any Coding Experience
reddit
LLM Vibe Score0
Human Vibe Score1
Consistent_Access844This week

Finally Launched My First App Without Any Coding Experience

About Myself I am a structural engineer that are taught to design buildings in the day and I have been dreaming forever to build a SaaS business to get out of the rat race. However, as a structural engineer, coding is definitely not something I am capable of doing (I have some simple knowledge, but its no way close to building an app) The Journey As I've mentioned, I always wanted to build a SaaS business because in my mind the business model is most attractive to me, where you only need to build once and can sell to millions. So I started off searching and exploring on the internet and my first ever "SaaS" was from Wordpress. I am buying plugin from other user and then pluggin into my own Wordpress website. It was a project management tool SaaS. I was so excited about the website and can't even sleep well at night because I'm just so hype about it. But, the reality is because this is my first ever business, I totally didn't realise about the importance of UI UX or my business differentiation, thinking that everyone will be as excited as I am. Then, I went deeper and deeper into the journey (I can write more about this in another post if anyone is interested) and finally landed on Flutterflow to create my first ever app. No Code Journey Thanks to no code builder, I never thought that a non-coder like me can ever create an app and got accepted by the App Store/Play Store. Since that I am using a low-code builder, for any specific requirement that I need that are not covered natively, I will just talk to ChatGPT and boom I pretty much got most of the answer I needed. About The App As someone that always try to keep track of my expenses, I never able to find an app that are simple and interesting enough for me to continue on the journey. I realise that I could have incorporate AI into this journey and hence there go, I created an AI Money Tracker. Let me introduce Rolly: AI Money Tracker - a new AI expense tracker where you can easily record your transactions just by chatting with our bot Rolly and it will automatically record and categorise the transaction into the most suitable category (you can also create any of your own category and it will also take care of it in consideration). I am not sharing the app link here to avoid getting ban, but feel free to search up Rolly: AI Money Tracker on either App Store on Play Store. My Learnings As someone that can't code and never imagine that I could create a production app by myself and publish it on to the App Store and Play Store. Since I am not making any money yet and just at the beginning of my entrepreneur journey, I can't give any substantial advice, all I can say is just my own learnings and feelings. My advice is if you have a dream of building a business, just go for it, don't worry about all the problems that you can think of to convince yourself not making the start at all. From my point of view, as long as you're not giving up everything (eg, putting yourself in huge debt etc), why don't just go for it and you've got nothing much to lose. You'll only lose if you never even get started. And also, I believe that creating an app is always the easiest step out of the entreprenuership journey, marketing and distribution is the key to success. Even though you've spent days and nights on it and it might mean everything to you, the truth is people don't really cares and you'll need to market for it. I am still in journey to learn how to do marketing, content, building a business and everything. I think this is just a very beginning of my journey and hopefully there's more interesting one to share further down the road.

Finally launched my own app in the app store!
reddit
LLM Vibe Score0
Human Vibe Score0.429
ranftThis week

Finally launched my own app in the app store!

After reading on the sidelines here for about a year I just launched Kalo. My app is the 100th million ai powered calorie-counting app, hahaha. I know I know. Here it comes: Kalo Screenshots Despite being in a crowded space, Kalo has some caveats I am a bit proud of: \- I am a daily user of my app. Everything that bugs me will be gone ASAP. \- I have already lost 10kg with Kalo. I can't do any sports due to an energy-debilitating sickness (hello my me/cfs friends 👋), so this is huge. \- I HATE nudging. Hence, Kalo has no streaks, no notifications to rip off your valuable time. It’s just a tool to track calories and learn to get a feel for it. \- Ease of daily use and doing anything so it doesn't feel like a grind is Kalo's mission. I already implemented a lot of ways to quickly access tracking and leaving the app. \- Next feature will be tracking your own progress with some proper research based analytics is the one next step, that Im working on. \- Data: Minimal footprint as possible. Anything is currently saved only on the device, especially all health data. Check Kalo out here: https://apps.apple.com/de/app/kalo/id6739449751?l=en-GB Tech used to make it possible: There are some terrific security functions in here, and a robust paywall integration, both of which I could never have done without the MVP help of \- Claude and GPT \- Claude's Project function was basically my base project folder here. Claude is perfect when it comes to traditional features. Anything more recent than iOS14 can become a very difficult endeavour \- GPT 4o was great for error logging overview and general sorting measures. Claude's message restriction could be fended of many times here. \- GPT 1o became available more recently and its coding is a lot more robust than 4o. This helped me to not clog Claude with tedious bug fixing. Also it helped when Claude ran away in terrible directions Pre knowledge: I was a digital product designer way back, so I know a thing or two about making things easier to use, especially when it comes to the ease of daily use. Marketing: Will be my biggest focus now. I am quite shit at it, which means It can only get better. It's gonna be some rough weather to get eyes on my app. If anyone thinks they can help or knows how to, any tips are appreciated. Thats it for now. I'll try and keep you updated. I am happy. Let's see if this app will make me happy on a nicer bed, or a jet ski. Again, happy to get your impression of Kalo: https://apps.apple.com/de/app/kalo/id6739449751?l=en-GB

[D] Is the Covid-19 crisis the rock on which the ML hype wave finally crashes?
reddit
LLM Vibe Score0
Human Vibe Score1
AlexSnakeKingThis week

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

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

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

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

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

Practical tips on hiring the best people? Which country? Remote vs. In Person?
reddit
LLM Vibe Score0
Human Vibe Score0.5
corporateshill32This week

Practical tips on hiring the best people? Which country? Remote vs. In Person?

Hi Reddit, I run a tech startup that's grown to $20M ARR. While we are relatively big, we are incredibly cash strapped till Q3 due to debt we took on last year and are currently paying back. In Q3, I'll finally have a large budget to sit and focus on building out our team. Now I'm trying to figure out: what are the optimal circumstances? We really screwed it up with our first batch of key hires after our seed round: US Product Manager, US Head of Customer Success - quit; US Head of Sales, US Head of Engineering - fired. We've built a mostly B or C team, and it really annoys me. We are slow, we are not up for big challenges, and people are, on average, not that brilliant. Out of our nearly 150 employees, I think I have ONE A player. However, they are also functioning at 60%. We are building additional "brands" this year, so there might be a way to separate a higher performing culture into our second brand. I have 3 questions, might seem relatively basic, but as we did such a bad job the first time around, I'd love to learn what you all think! I'm trying to build an optimal team with A-players! Q1: Today we are fully remote, should I get an in person office going? In which city? Q2: In general, which city should I hire talent from? I live in San Francisco and sometimes LA, but find the culture here generally too laid back. New York? But to keep a high quality, let's say, marketer, interested long term, they're going to want $200-220k base (and that's not even that competitive). While that is fine, it will slow down my intended plan for hiring. London? Salaries are comparatively much lower, and talent quality is still pretty high, but I am a little unsure of the work culture. In terms of budget, I'd love to aim for $150-180k/key hire and to go as high as $300k if appropriate. Q3: Should I be hiring people with 20 years of relevant experience? 2-3 years with a hunger to prove themselves? Fresh grads we can mould into whatever we need? As for what exactly I'm trying to hire for, lots of key hires: department heads, digital marketers, content people, engineers, AI engineers, operations people, strategy people, and more. I don't know enough about all the working cultures in these places, but I want to find and incentivize people who are willing to own and take responsibility for an area of the business, be trusted to make good decisions, and view it as their responsibility to improve their areas drastically, more than the typical 9-5. I feel today's workforce is not content with base + light equity, and maybe we should consider tying an unlimited-upside incentive to a relevant KPI to incentivize people working harder than just "what is required"? (edit: I know might get some hate for this "work harder than 9-5" mentality, but to clarify, I'm trying to figure out what incentive structures will naturally attract the type of person that wants this type of working life) What do you think? Also, any other practical tips for finding awesome people like this? edit: hooooly! this thread blew up. I'll do my best to reply to everyone, thank you for all your responses!

Behind the scene : fundraising pre-seed of an AI startup
reddit
LLM Vibe Score0
Human Vibe Score1
Consistent-Wafer7325This week

Behind the scene : fundraising pre-seed of an AI startup

A bit of feedback from our journey at our AI startup. We started prototyping stuff around agentic AI last winter with very cool underlying tech research based on some academic papers (I can send you links if you're interested in LLM orchestration). I'm a serial entrepreneur with 2x exits, nothing went fancy but enough to keep going into the next topic. This time, running an AI project has been a bit different and unique due to the huge interest around the topic. Here are a few insights. Jan \~ Mar: Research Nothing was serious, just a side project with a friend on weekends (the guy became our lead SWE). Market was promising and we had the convinction that our tech can be game changer in computer systems workflows. March \~ April: Market Waking Up Devin published their pre-seed $20m fundraising led by Founders Fund; they paved the market with legitimacy. I decided to launch some coffee meetings with a few angels in my network. Interest confirmed. Back to work on some more serious early prototyping; hard work started here. April \~ May: YC S24 (Fail) Pumped up by our prospective angels and the market waking up on the agentic topic, I applied to YC as a solo founder (was still looking for funds and co-founders). Eventually got rejected (no co-founder and not US-based). May \~ July: VC Dance (Momentum 1) Almost randomly at the same time we got rejected from YC, I got introduced to key members of the VC community by one of our prospective angels. Interest went crazy... tons of calls. Brace yourself here, we probably met 30\~40 funds (+ angels). Got strong interests from 4\~5 of them (3 to 5 meetings each), ultimately closed 1 and some interests which might convert later in the next stage. The legend of AI being hype is true. Majority of our calls went only by word of mouth, lots of inbounds, people even not having the deck would book us a call in the next 48h after saying hi. Also lots of "tourists," just looking because of AI but with no strong opinion on the subject to move further. The hearsay about 90% rejection is true. You'll have a lot of nos, ending some days exhausted and unmotivated. End July: Closing, the Hard Part The VC roadshow is kind of an art you need to master. You need to keep momentum high enough and looking over-subscribed. Good pre-seed VC deals are over-competitive, and good funds only focus on them; they will have opportunities to catch up on lost chances at the seed stage later. We succeeded (arduously) to close our 18\~24mo budget with 1 VC, a few angels, and some state-guaranteed debt. Cash in bank just on time for payday in August (don't under-estimate time of processing) Now: Launching and Prepping the Seed Round We're now in our first weeks of go-to-market with a lot of uncertainty but a very ambitious plan ahead. The good part of having met TONS of VCs during the pre-seed roadshow is that we met probably our future lead investors in these. What would look like a loss of time in the initial pre-seed VC meetings has been finally very prolific, helping us to refine our strategy, assessing more in-depth the market (investors have a lot of insights, they meet a lot of people... that's their full-time job). We now have clear milestones and are heading to raise our seed round by end of year/Q1 if stars stay aligned :) Don't give up, the show must go on.

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

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

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

Behind the scene : fundraising pre-seed of an AI startup
reddit
LLM Vibe Score0
Human Vibe Score1
Consistent-Wafer7325This week

Behind the scene : fundraising pre-seed of an AI startup

A bit of feedback from our journey at our AI startup. We started prototyping stuff around agentic AI last winter with very cool underlying tech research based on some academic papers (I can send you links if you're interested in LLM orchestration). I'm a serial entrepreneur with 2x exits, nothing went fancy but enough to keep going into the next topic. This time, running an AI project has been a bit different and unique due to the huge interest around the topic. Here are a few insights. Jan \~ Mar: Research Nothing was serious, just a side project with a friend on weekends (the guy became our lead SWE). Market was promising and we had the convinction that our tech can be game changer in computer systems workflows. March \~ April: Market Waking Up Devin published their pre-seed $20m fundraising led by Founders Fund; they paved the market with legitimacy. I decided to launch some coffee meetings with a few angels in my network. Interest confirmed. Back to work on some more serious early prototyping; hard work started here. April \~ May: YC S24 (Fail) Pumped up by our prospective angels and the market waking up on the agentic topic, I applied to YC as a solo founder (was still looking for funds and co-founders). Eventually got rejected (no co-founder and not US-based). May \~ July: VC Dance (Momentum 1) Almost randomly at the same time we got rejected from YC, I got introduced to key members of the VC community by one of our prospective angels. Interest went crazy... tons of calls. Brace yourself here, we probably met 30\~40 funds (+ angels). Got strong interests from 4\~5 of them (3 to 5 meetings each), ultimately closed 1 and some interests which might convert later in the next stage. The legend of AI being hype is true. Majority of our calls went only by word of mouth, lots of inbounds, people even not having the deck would book us a call in the next 48h after saying hi. Also lots of "tourists," just looking because of AI but with no strong opinion on the subject to move further. The hearsay about 90% rejection is true. You'll have a lot of nos, ending some days exhausted and unmotivated. End July: Closing, the Hard Part The VC roadshow is kind of an art you need to master. You need to keep momentum high enough and looking over-subscribed. Good pre-seed VC deals are over-competitive, and good funds only focus on them; they will have opportunities to catch up on lost chances at the seed stage later. We succeeded (arduously) to close our 18\~24mo budget with 1 VC, a few angels, and some state-guaranteed debt. Cash in bank just on time for payday in August (don't under-estimate time of processing) Now: Launching and Prepping the Seed Round We're now in our first weeks of go-to-market with a lot of uncertainty but a very ambitious plan ahead. The good part of having met TONS of VCs during the pre-seed roadshow is that we met probably our future lead investors in these. What would look like a loss of time in the initial pre-seed VC meetings has been finally very prolific, helping us to refine our strategy, assessing more in-depth the market (investors have a lot of insights, they meet a lot of people... that's their full-time job). We now have clear milestones and are heading to raise our seed round by end of year/Q1 if stars stay aligned :) Don't give up, the show must go on.

We built a tool to help you find relevant grants. Would you pay for it?
reddit
LLM Vibe Score0
Human Vibe Score1
CliznitchThis week

We built a tool to help you find relevant grants. Would you pay for it?

Hi everyone, About a year ago, I asked you guys whether it would make sense to develop a tool to help entrepreneurs find relevant grants. Many of you provided incredibly valuable feedback, which we used to refine the concept. With this concept, we went through Techstars and finally launched a beta version of our grant scan tool last week! Along the way, we realized something interesting: when you ask a grant advisor which grants might be a great fit for you, they almost always recommend the ones they know well. This makes sense since most work on a success fee basis, and referring you to lesser-known grants (which take more time to write and have lower success rates) isn’t worth it for them. Plus, memorizing the details of 20,000+ grants is, understandably, pretty tough. Our platform uses AI to scan and analyze thousands of grants. It identifies the best matches, estimates your chances of success, and calculates how much time you might need for the application and reporting phases. We can then match you with a grant advisor with relevant expertise—whether to write the application for you or provide feedback on your draft. We’re considering launching both a free and a paid version. The free version would provide basic insights, while the paid version would include more comprehensive results, expert comments (such as explaining why certain grants are a good fit), and updates when new relevant grants become available. Both versions will allow you to connect with relevant experts. Would you pay for the paid version? And if so, which features should it include? Also, any general feedback is much appreciated! Thanks!

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

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

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

10y of product development, 2 bankruptcies, and 1 Exit — what next? [Extended Story]
reddit
LLM Vibe Score0
Human Vibe Score1
Slight-Explanation29This week

10y of product development, 2 bankruptcies, and 1 Exit — what next? [Extended Story]

10 years of obsessive pursuit from the bottom to impressive product-market fit and exit. Bootstrapping tech products as Software Developer and 3x Startup Founder (2 bankruptcies and 1 exit). Hi everyone, your motivation has inspired me to delve deeper into my story. So, as promised to some of you, I've expanded on it a bit more, along with my brief reflections. There are many founders, product creators, and proactive individuals, I’ve read many of your crazy stories and lessons so I decided to share mine and the lessons I learned from the bottom to impressive product-market fit and exit. I've spent almost the past 10 years building tech products as a Corporate Team Leader, Senior Software Developer, Online Course Creator, Programming Tutor, Head of Development/CTO, and 3x Startup Founder (2 bankruptcies, and 1 exit). And what next? good question... A brief summary of my journey: Chapter 1: Software Developer / Team Leader / Senior Software Developer I’ve always wanted to create products that win over users’ hearts, carry value, and influence users. Ever since my school days, I’ve loved the tech part of building digital products. At the beginning of school, I started hosting servers for games, blogs and internet forums, and other things that did not require much programming knowledge. My classmates and later even over 100 people played on servers that I hosted on my home PC. Later, as the only person in school, I passed the final exam in computer science. During my computer science studies, I started my first job as a software developer. It was crazy, I was spending 200–300 hours a month in the office attending also to daily classes. Yes, I didn’t have a life, but it truly was the fulfillment of my dreams. I was able to earn good money doing what I love, and I devoted fully myself to it. My key to effectively studying IT and growing my knowledge at rocket speed was learning day by day reading guides, building products to the portfolio, watching youtube channels and attending conferences, and even watching them online, even if I didn’t understand everything at the beginning. In one year we’ve been to every possible event within 400km. We were building healthcare products that were actually used in hospitals and medical facilities. It was a beautiful adventure and tons of knowledge I took from this place. That time I built my first product teams, hired many great people, and over the years became a senior developer and team leader. Even I convinced my study mates to apply to this company and we studied together and worked as well. Finally, there were 4 of us, when I left a friend of mine took over my position and still works there. If you’re reading this, I’m sending you a flood of love and appreciation. I joined as the 8th person, and after around 4 years, when I left hungry for change, there were already over 30 of us, now around 100. It was a good time, greetings to everyone. I finished my Master’s and Engineering degrees in Computer Science, and it was time for changes. Chapter 2: 1st time as a Co-founder — Marketplace In the meantime, there was also my first startup (a marketplace) with four of my friends. We all worked on the product, each of us spent thousands of hours, after hours, entire weekends… and I think finally over a year of work. As you might guess, we lacked the most important things: sales, marketing, and product-market fit. We thought users think like us. We all also worked commercially, so the work went very smoothly, but we didn’t know what we should do next with it… Finally, we didn’t have any customers, but you know what, I don’t regret it, a lot of learning things which I used many times later. The first attempts at validating the idea with the market and business activities. In the end, the product was Airbnb-sized. Landing pages, listings, user panels, customer panels, admin site, notifications, caches, queues, load balancing, and much more. We wanted to publish the fully ready product to the market. It was a marketplace, so if you can guess, we had to attract both sides to be valuable. “Marketplace” — You can imagine something like Uber, if you don’t have passengers it was difficult to convince taxi drivers, if you don’t have a large number of taxi drivers you cannot attract passengers. After a year of development, we were overloaded, and without business, marketing, sales knowledge, and budget. Chapter 3: Corp Team Lead / Programming Tutor / Programming Architecture Workshop Leader Working in a corporation, a totally different environment, an international fintech, another learning experience, large products, and workmates who were waiting for 5 pm to finish — it wasn’t for me. Very slow product development, huge hierarchy, being an ant at the bottom, and low impact on the final product. At that time I understood that being a software developer is not anything special and I compared my work to factory worker. Sorry for that. High rates have been pumped only by high demand. Friends of mine from another industry do more difficult things and have a bigger responsibility for lower rates. That’s how the market works. This lower responsibility time allowed for building the first online course after hours, my own course platform, individual teaching newbies programming, and my first huge success — my first B2C customers, and B2B clients for workshops. I pivoted to full focus on sales, marketing, funnels, advertisements, demand, understanding the market, etc. It was 10x easier than startups but allowed me to learn and validate my conceptions and ideas on an easier market and showed me that it’s much easier to locate their problem/need/want and create a service/product that responds to it than to convince people of your innovative ideas. It’s just supply and demand, such a simple and basic statement, in reality, is very deep and difficult to understand without personal experience. If you’re inexperienced and you think you understand, you don’t. To this day, I love to analyze this catchword in relation to various industries / services / products and rediscover it again and again... While writing this sentence, I’m wondering if I’m not obsessed. Chapter 4: Next try — 2nd time as a founder — Edtech Drawing upon my experiences in selling services, offering trainings, and teaching programming, I wanted to broaden my horizons, delve into various fields of knowledge, involve more teachers, and so on. We started with simple services in different fields of knowledge, mainly relying on teaching in the local area (without online lessons). As I had already gathered some knowledge and experience in marketing and sales, things were going well and were moving in the right direction. The number of teachers in various fields was growing, as was the number of students. I don’t remember the exact statistics anymore, but it was another significant achievement that brought me a lot of satisfaction and new experiences. As you know, I’m a technology lover and couldn’t bear to look at manual processes — I wanted to automate everything: lessons, payments, invoices, customer service, etc. That’s when I hired our first developers (if you’re reading this, I’m sending you a flood of love — we spent a lot of time together and I remember it as a very fruitful and great year) and we began the process of tool and automation development. After a year we had really extended tools for students, teachers, franchise owners, etc. We had really big goals, we wanted to climb higher and higher. Maybe I wouldn’t even fully call it Startup, as the client was paying for the lessons, not for the software. But it gave us positive income, bootstrap financing, and tool development for services provided. Scaling this model was not as costless as SaaS because customer satisfaction was mainly on the side of the teacher, not the quality of the product (software). Finally, we grew to nearly 10 people and dozens of teachers, with zero external funding, and almost $50k monthly revenue. We worked very hard, day and night, and by November 2019, we were packed with clients to the brim. And as you know, that’s when the pandemic hit. It turned everything upside down by 180 degrees. Probably no one was ready for it. With a drastic drop in revenues, society started to save. Tired from the previous months, we had to work even harder. We had to reduce the team, change the model, and save what we had built. We stopped the tool’s development and sales, and with the developers, we started supporting other product teams to not fire them in difficult times. The tool worked passively for the next two years, reducing incomes month by month. With a smaller team providing programming services, we had full stability and earned more than relying only on educational services. At the peak of the pandemic, I promised myself that it was the last digital product I built… Never say never… Chapter 5: Time for fintech — Senior Software Developer / Team Lead / Head of Development I worked for small startups and companies. Building products from scratch, having a significant impact on the product, and complete fulfillment. Thousands of hours and sacrifices. This article mainly talks about startups that I built, so I don’t want to list all the companies, products, and applications that I supported as a technology consultant. These were mainly start-ups with a couple of people up to around 100 people on board. Some of the products were just a rescue mission, others were building an entire tech team. I was fully involved in all of them with the hope that we would work together for a long time, but I wasn’t the only one who made mistakes when looking for a product-market fit. One thing I fully understood: You can’t spend 8–15 hours a day writing code, managing a tech team, and still be able to help build an audience. In marketing and sales, you need to be rested and very creative to bring results and achieve further results and goals. If you have too many responsibilities related to technology, it becomes ineffective. I noticed that when I have more free time, more time to think, and more time to bounce the ball against the wall, I come up with really working marketing/sales strategies and solutions. It’s impossible when you are focused on code all day. You must know that this chapter of my life was long and has continued until now. Chapter 6: 3rd time as a founder — sold Never say never… right?\\ It was a time when the crypto market was really high and it was really trending topic. You know that I love technology right? So I cannot miss the blockchain world. I had experience in blockchain topics by learning on my own and from startups where I worked before. I was involved in crypto communities and I noticed a “starving crowd”. People who did things manually and earned money(crypto) on it.I found potential for building a small product that solves a technological problem. I said a few years before that I don’t want to start from scratch. I decided to share my observations and possibilities with my good friend. He said, “If you gonna built it, I’m in”. I couldn’t stop thinking about it. I had thought and planned every aspect of marketing and sales. And you know what. On this huge mindmap “product” was only one block. 90% of the mindmap was focused on marketing and sales. Now, writing this article, I understood what path I went from my first startup to this one. In the first (described earlier) 90% was the product, but in the last one 90% was sales and marketing. Many years later, I did this approach automatically. What has changed in my head over the years and so many mistakes? At that time, the company for which I provided services was acquired. The next day I got a thank you for my hard work and all my accounts were blocked. Life… I was shocked. We were simply replaced by their trusted technology managers. They wanted to get full control. They acted a bit unkindly, but I knew that they had all my knowledge about the product in the documentation, because I’m used to drawing everything so that in the moment of my weakness (illness, whatever) the team could handle it. That’s what solid leaders do, right? After a time, I know that these are normal procedures in financial companies, the point is that under the influence of emotions, do not do anything inappropriate. I quickly forgot about it, that I was brutally fired. All that mattered was to bring my plan to life. And it has been started, 15–20 hours a day every day. You have to believe me, getting back into the game was incredibly satisfying for me. I didn’t even know that I would be so excited. Then we also noticed that someone was starting to think about the same product as me. So the race began a game against time and the market. I assume that if you have reached this point, you are interested in product-market fit, marketing, and sales, so let me explain my assumptions to you: Product: A very very small tool that allowed you to automate proper tracking and creation of on-chain transactions. Literally, the whole app for the user was located on only three subpages. Starving Crowd: We tapped into an underserved market. The crypto market primarily operates via communities on platforms like Discord, Reddit, Twitter, Telegram, and so on. Therefore, our main strategy was directly communicating with users and demonstrating our tool. This was essentially “free marketing” (excluding the time we invested), as we did not need to invest in ads, promotional materials, or convince people about the efficacy of our tool. The community could directly observe on-chain transactions executed by our algorithms, which were processed at an exceptionally fast rate. This was something they couldn’t accomplish manually, so whenever someone conducted transactions using our algorithm, it was immediately noticeable and stirred a curiosity within the community (how did they do that!). Tests: I conducted the initial tests of the application on myself — we had already invested significantly in developing the product, but I preferred risking my own resources over that of the users. I provided the tool access to my wallet, containing 0.3ETH, and went to sleep. Upon waking up, I discovered that the transactions were successful and my wallet had grown to 0.99ETH. My excitement knew no bounds, it felt like a windfall. But, of course, there was a fair chance I could have lost it too. It worked. As we progressed, some users achieved higher results, but it largely hinged on the parameters set by them. As you can surmise, the strategy was simple — buy low, sell high. There was considerable risk involved. Churn: For those versed in marketing, the significance of repeat visitors cannot be overstated. Access to our tool was granted only after email verification and a special technique that I’d prefer to keep confidential. And this was all provided for free. While we had zero followers on social media, we saw an explosion in our email subscriber base and amassed a substantial number of users and advocates. Revenue Generation: Our product quickly gained popularity as we were effectively helping users earn — an undeniable value proposition. Now, it was time to capitalize on our efforts. We introduced a subscription model charging $300 per week or $1,000 per month — seemingly high rates, but the demand was so intense that it wasn’t an issue. Being a subscriber meant you were prioritized in the queue, ensuring you were among the first to reap benefits — thus adding more “value”. Marketing: The quality of our product and its ability to continually engage users contributed to it achieving what can best be described as viral. It was both a source of pride and astonishment to witness users sharing charts and analyses derived from our tool in forum discussions. They weren’t actively promoting our product but rather using screenshots from our application to illustrate certain aspects of the crypto world. By that stage, we had already assembled a team to assist with marketing, and programming, and to provide round-the-clock helpdesk support. Unforgettable Time: Despite the hype, my focus remained steadfast on monitoring our servers, their capacity, and speed. Considering we had only been on the market for a few weeks, we were yet to implement alerts, server scaling, etc. Our active user base spanned from Japan to the West Coast of the United States. Primarily, our application was used daily during the evenings, but considering the variety of time zones, the only time I could afford to sleep was during the evening hours in Far Eastern Europe, where we had the least users. However, someone always needed to be on guard, and as such, my phone was constantly by my side. After all, we couldn’t afford to let our users down. We found ourselves working 20 hours a day, catering to thousands of users, enduring physical fatigue, engaging in talks with VCs, and participating in conferences. Sudden Downturn: Our pinnacle was abruptly interrupted by the war in Ukraine (next macroeconomic shot straight in the face, lucky guy), a precipitous drop in cryptocurrency value, and swiftly emerging competition. By this time, there were 5–8 comparable tools had infiltrated the market. It was a challenging period as we continually stumbled upon new rivals. They immediately embarked on swift fundraising endeavors — a strategy we overlooked, which in retrospect was a mistake. Although our product was superior, the competitors’ rapid advancement and our insufficient funds for expeditious scaling posed significant challenges. Nonetheless, we made a good decision. We sold the product (exit) to competitors. The revenue from “exit” compensated for all the losses, leaving us with enough rest. We were a small team without substantial budgets for rapid development, and the risk of forming new teams without money to survive for more than 1–2 months was irresponsible. You have to believe me that this decision consumed us sleepless nights. Finally, we sold it. They turned off our app but took algorithms and users. Whether you believe it or not, after several months of toiling day and night, experiencing burnout, growing weary of the topic, and gaining an extra 15 kg in weight, we finally found our freedom… The exit wasn’t incredibly profitable, but we knew they had outdone us. The exit covered all our expenses and granted us a well-deserved rest for the subsequent quarter. It was an insane ride. Despite the uncertainty, stress, struggles, and sleepless nights, the story and experience will remain etched in my memory for the rest of my life. Swift Takeaways: Comprehending User Needs: Do you fully understand the product-market fit? Is your offering just an accessory or does it truly satisfy the user’s needs? The Power of Viral Marketing: Take inspiration from giants like Snapchat, ChatGPT, and Clubhouse. While your product might not attain the same scale (but remember, never say never…), the closer your concept is to theirs, the easier your journey will be. If your user is motivated to text a friend saying, “Hey, check out how cool this is” (like sharing ChatGPT), then you’re on the best track. Really. Even if it doesn’t seem immediately evident, there could be a way to incorporate this into your product. Keep looking until you find it. Niche targeting — the more specific and tailored your product is to a certain audience, the easier your journey will be People love buying from people — establishing a personal brand and associating yourself with the product can make things easier. Value: Seek to understand why users engage with your product and keep returning. The more specific and critical the issue you’re aiming to solve, the easier your path will be. Consider your offerings in terms of products and services and focus on sales and marketing, regardless of personal sentiments. These are just a few points, I plan to elaborate on all of them in a separate article. Many products undergo years of development in search of market fit, refining the user experience, and more. And guess what? There’s absolutely nothing wrong with that. Each product and market follows its own rules. Many startups have extensive histories before they finally make their mark (for instance, OpenAI). This entire journey spanned maybe 6–8 months. I grasped and capitalized on the opportunity, but we understood from the start that establishing a startup carried a significant risk, and our crypto product was 10 times riskier. Was it worth it? Given my passion for product development — absolutely. Was it profitable? — No, considering the hours spent — we lose. Did it provide a stable, problem-free life — nope. Did this entire adventure offer a wealth of happiness, joy, and unforgettable experiences — definitely yes. One thing is certain — we’ve amassed substantial experience and it’s not over yet :) So, what lies ahead? Chapter 7: Reverting to the contractor, developing a product for a crypto StartupReturning to the past, we continue our journey… I had invested substantial time and passion into the tech rescue mission product. I came on board as the technical Team Leader of a startup that had garnered over $20M in seed round funding, affiliated with the realm of cryptocurrencies. The investors were individuals with extensive backgrounds in the crypto world. My role was primarily technical, and there was an abundance of work to tackle. I was fully immersed, and genuinely devoted to the role. I was striving for excellence, knowing that if we secured another round of financing, the startup would accelerate rapidly. As for the product and marketing, I was more of an observer. After all, there were marketing professionals with decades of experience on board. These were individuals recruited from large crypto-related firms. I had faith in them, kept an eye on their actions, and focused on my own responsibilities. However, the reality was far from satisfactory. On the last day, the principal investor for the Series A round withdrew. The board made the tough decision to shut down. It was a period of intense observation and gaining experience in product management. This was a very brief summary of the last 10 years. And what next? (Last) Chapter 8: To be announced — Product Owner / Product Consultant / Strategist / CTO After spending countless hours and days deliberating my next steps, one thing is clear: My aspiration is to continue traversing the path of software product development, with the hopeful anticipation that one day, I might ride the crest of the next big wave and ascend to the prestigious status of a unicorn company. I find myself drawn to the process of building products, exploring product-market fit, strategizing, engaging in software development, seeking out new opportunities, networking, attending conferences, and continuously challenging myself by understanding the market and its competitive landscape. Product Owner / Product Consultant / CTO / COO: I’m not entirely sure how to categorize this role, as I anticipate that it will largely depend on the product to which I will commit myself fully. My idea is to find one startup/company that wants to build a product / or already has a product, want to speed up, or simply doesn’t know what’s next. Alternatively, I could be a part of an established company with a rich business history, which intends to invest in digitization and technological advancements. The goal would be to enrich their customer experience by offering complementary digital products Rather than initiating a new venture from ground zero with the same team, I am receptive to new challenges. I am confident that my past experiences will prove highly beneficial for the founders of promising, burgeoning startups that already possess a product, or are in the initial phases of development. ‘Consultant’ — I reckon we interpret this term differently. My aim is to be completely absorbed in a single product, crafting funnels, niches, strategies, and all that is necessary to repeatedly achieve the ‘product-market fit’ and significant revenue. To me, ‘consultant’ resonates more akin to freelancing than being an employee. My current goal is to kickstart as a consultant and aide, dealing with facilitating startups in their journey from point A to B. Here are two theoretical scenarios to illustrate my approach: Scenario 1: (Starting from point A) You have a product but struggle with marketing, adoption, software, strategy, sales, fundraising, or something else. I conduct an analysis and develop a strategy to reach point B. I take on the “dirty work” and implement necessary changes, including potential pivots or shifts (going all-in) to guide the product to point B. The goal is to reach point B, which could involve achieving a higher valuation, expanding the user base, increasing sales, or generating monthly revenue, among other metrics. Scenario 2: (Starting from point A) You have a plan or idea but face challenges with marketing, adoption, strategy, software, sales, fundraising, or something else. I analyze the situation and devise a strategy to reach point B. I tackle the necessary tasks, build the team, and overcome obstacles to propel the product to point B. I have come across the view that finding the elusive product-market fit is the job of the founder, and it’s hard for me to disagree. However, I believe that my support and experiences can help save money, many failures, and most importantly, time. I have spent a great deal of time learning from my mistakes, enduring failure after failure, and even had no one to ask for support or opinion, which is why I offer my help. Saving even a couple of years, realistically speaking, seems like a value I’m eager to provide… I invite you to share your thoughts and insights on these scenarios :) Closing Remarks: I appreciate your time and effort in reaching this point. This has been my journey, and I wouldn’t change it for the world. I had an extraordinary adventure, and now I’m ready for the next exciting battle with the market and new software products. While my entire narrative is centered around startups, especially the ones I personally built, I’m planning to share more insights drawn from all of my experiences, not just those as a co-founder. If you’re currently developing your product or even just considering the idea, I urge you to reach out to me. Perhaps together, we can create something monumental :) Thank you for your time and insights. I eagerly look forward to engaging in discussions and hearing your viewpoints. Please remember to like and subscribe. Nothing motivates to write more than positive feedback :) Matt.

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

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

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

From Running a $350M Startup to Failing Big and Rediscovering What Really Matters in Life ❤️
reddit
LLM Vibe Score0
Human Vibe Score1
Disastrous-Airport88This week

From Running a $350M Startup to Failing Big and Rediscovering What Really Matters in Life ❤️

This is my story. I’ve always been a hustler. I don’t remember a time I wasn’t working since I was 14. Barely slept 4 hours a night, always busy—solving problems, putting out fires. After college (LLB and MBA), I was lost. I tried regular jobs but couldn’t get excited, and when I’m not excited, I spiral. But I knew entrepreneurship; I just didn’t realize it was an option for adults. Then, in 2017 a friend asked me to help with their startup. “Cool,” I thought. Finally, a place where I could solve problems all day. It was a small e-commerce idea, tackling an interesting angle. I worked 17-hour days, delivering on a bike, talking to customers, vendors, and even random people on the street. Things moved fast. We applied to Y Combinator, got in, and raised $18M before Demo Day even started. We grew 100% month-over-month. Then came another $40M, and I moved to NYC. Before I knew it, we had 1,000 employees and raised $80M more. I was COO, managing 17 direct reports (VPs of Ops, Finance, HR, Data, and more) and 800 indirect employees. On the surface, I was on top of the world. But in reality, I was at rock bottom. I couldn’t sleep, drowning in anxiety, and eventually ended up on antidepressants. Then 2022 hit. We needed to raise $100M, but we couldn’t. In three brutal months, we laid off 900 people. It was the darkest period of my life. I felt like I’d failed everyone—myself, investors, my company, and my team. I took a year off. Packed up the car with my wife and drove across Europe, staying in remote places, just trying to calm my nervous system. I couldn’t speak to anyone, felt ashamed, and battled deep depression. It took over a year, therapy, plant medicine, intense morning routines, and a workout regimen to get back on my feet, physically and mentally. Now, I’m on the other side. In the past 6 months, I’ve been regaining my mojo, with a new respect for who I am and why I’m here. I made peace with what I went through over those 7 years—the lessons, the people, the experiences. I started reconnecting with my community, giving back. Every week, I have conversations with young founders, offering direction, or even jumping in to help with their operations. It’s been a huge gift. I also began exploring side projects. I never knew how to code, but I’ve always had ideas. Recent advances in AI gave me the push I needed. I built my first app, as my first attempt at my true passion—consumer products for kids. Today, I feel wholesome about my journey. I hope others can see that too. ❤️ EDIT: Wow, I didn’t expect this post to resonate with so many people. A lot of you have DM’d me, and I’ll try to respond. Just a heads-up, though—I’m juggling consulting and new projects, so I can’t jump on too many calls. Since I’m not promoting anything, I won’t be funneling folks to my page, so forgive me if I don’t get back to everyone. Anyway, it’s amazing to connect with so many of you. I’d love to write more, so let me know what topics you’d be interested in!

The Birth of My First (and Hilariously Flawed) Voice Agent: A Tale of No-Code Chaos
reddit
LLM Vibe Score0
Human Vibe Score0.778
No-Understanding5609This week

The Birth of My First (and Hilariously Flawed) Voice Agent: A Tale of No-Code Chaos

Okay Reddit, buckle up. I'm about to tell you the saga of how I birthed my very first voice agent, a chaotic and frankly, slightly embarrassing journey involving Retell.ai, Make.com, and Zapier. Looking back, it's equal parts hilarious and traumatizing. The Naive Dream: Back then (it feels like ages ago!), I was convinced I could easily whip up a voice agent that would take restaurant orders over the phone. Elegant, efficient, and completely automated! I envisioned a world where my clients' restaurant never missed a beat, all thanks to my coding prowess... or rather, my no-code prowess. How wrong I was. The Gauntlet Begins: Retell.ai's Murky Depths Retell.ai was the starting point, the "voice" of my operation. Getting the phone number hooked up felt like a small victory, quickly overshadowed by the realization that their documentation was... well, let's just say it wasn't written for complete novices. I spent what felt like an eternity staring at API keys, convinced I'd entered them correctly, only to be greeted by cryptic error messages. The sheer frustration I felt wrestling with that initial setup is something I'll never forget. Make.com: From Pretty Picture to Painful Puzzle Then came Make.com, the orchestra conductor of my workflow. It looked so beautiful, so user-friendly! Drag and drop, visual modules... what could go wrong? Oh, so much could go wrong. Trying to decipher the JSON data stream from Retell was like trying to understand a foreign language I only knew a few words of. Mapping that data to a Google Sheet? A complete and utter disaster. I remember spending hours just trying to get the correct fields to populate, each failed attempt fueling my growing despair. Zapier: Briefly Considered, Quickly Dismissed I flirted with the idea of using Zapier instead, seduced by its simplicity. But its limitations became glaringly obvious when I tried to build the complex, multi-step process I needed. Make.com was the only real option, which meant diving headfirst into a whole new world of modules, triggers, and data transformations. The Infernal Testing Loop: The absolute WORST part of the entire process was the testing. Picture this: Calling the agent, rambling through a mock order, waiting for the workflow to execute, only to discover (yet another) error. Then, tweaking the scenario, pushing "save," and repeating the entire agonizing process. Each test call felt like a mini-marathon, a grueling race against time and my own dwindling patience. The AI's... Quirks: And then there was the AI itself. It was... let's just say it had a personality of its own. Sometimes, it perfectly understood my order. Other times, it decided I wanted to order 500 pizzas with extra anchovies. Debugging the AI's interpretation felt like negotiating with a stubborn toddler. Lessons Hard-Learned (And Forever Etched in My Memory): Start absurdly small: I tried to build a fully functional system right away. A HUGE mistake. If I could go back, I would have focused on just extracting one piece of information (like, say, just the quantity) and gotten that rock solid before adding anything else. JSON is your friend (or should be): Back then, JSON felt like alien code. Now, I have a slightly better grasp on it. Trust me, learn JSON. It will save you so much pain. Test like your sanity depends on it: Because it does. After every. Single. Change. Test the entire flow. It's tedious, but it's the only way to catch errors before they snowball into a catastrophe. Don't suffer in silence: I tried to be a lone wolf, figuring everything out myself. Big mistake. Retell.ai's forums and Make.com's documentation are goldmines. Use them! Embrace the struggle: This is the most important lesson. Building a voice agent, especially your first one, is hard. It's frustrating. It will test your limits. But don't give up. The feeling of finally making it work (even partially) is worth it. The Bot That (Barely) Lived: In the end, I did create a voice agent that could take orders and log them into a spreadsheet. It wasn't pretty. It was buggy. It occasionally ordered things that didn't make any sense. But it was mine. And it was the first step on a long and winding road. Looking back, I laugh (and cringe) at my naivety. But I also appreciate the lessons I learned and the sheer grit it took to bring my little AI Frankenstein to life. Anyone else have a similar "first bot" story? Let's hear them! Misery (and laughter) loves company. #RetellAI #Makecom #Zapier #FirstBot #NoCodeFail #VoiceAgentStruggles #StoryTime

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

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

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

My app has gone viral and I grew from 1k users (take 5months) to 100k user in 5 days
reddit
LLM Vibe Score0
Human Vibe Score1
Consistent_Access844This week

My app has gone viral and I grew from 1k users (take 5months) to 100k user in 5 days

I've always dreamt of building an online side business where I can build once and sell to millions. I love that business model but have never dreamt that I can achieve that, given that I am not a programmer in my career. I have been following side hustle school and some other business podcast for the past years as a drive and motivation to create my own business.  Over the years, I've delve a little on to web development using WordPress and in the hope of earning some money from that. I learnt in the hard way but is a good learning story and journey. I realised that what you put all your efforts building and excited for doesn't mean anything for anyone else and also learnt the importance of UI UX.  Fast forward to 5 months ago (July 2024), I've came across several low code app builder. With the help of the low code tools in combination with chatgpt, I've finally launched my first mobile app - Rolly: AI Money Tracker. But the business challenges doesn't end here, but it's just the beginning. I got no experience and skills on marketing but I've got my drive and passion that keep propelling me forward. By keep listening on people sharing their journey, looking at different apps to brainstorm etc, I've managed to now grow my user base from 1k (in 5 months) to 100k (in 5days). What's happening was my app somehow got viral in Vietnam when people are getting interest funny comments from my AI during entering the transaction and it has been sharing around in the social media and even featured on the news. What a crazy journey as the inflow of users has been too sudden, my server has been down for a few times until I progressively upgrade it until it got stable these couple of days. As for my advice to people dreaming the to be entreprenuer - Don't overthinking about all the problems you will face before starting. You will encounter hundreds of problems along the way and you just need to solve them one by one. You will never start if you think about what's not working and there will never be an answer for everything - even I don't have an answer for everything now.

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

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

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

Seeking co-founder to build LinkedIn’s biggest rival(curated version)
reddit
LLM Vibe Score0
Human Vibe Score1
ItzdreeThis week

Seeking co-founder to build LinkedIn’s biggest rival(curated version)

How do you connect with likeminded people? You see the polished wins everywhere, but what about the messy drafts , the awkward pitches and the moments you’re not sure you’ve got it right? Problem: The whole idea of founding and starting a business can be super intimidating for some people, specially those who don’t know any founders personally, those who don’t have a large network, those who don’t have rich parents with large networks, those not inserted in an entrepreneurial culture like in the US for example (which is my case). Sometimes all you need is the right support network, and too see others do what you want, to know that it’s possible! Everyone has an “ultimate guide” to make 7 figures or build a business on YouTube but NO ONE shoes you the HOW, just the results… I’ve tried joining founder communities, LinkedIn ,Reddit … you name it. Most of these founder communities are inaccessible for regular people and often ask for you to have an already existing business with a min ARR… or their simply geography based and if you’re not in a certain area you can’t really participate… As of LinkedIn… full of empty AI generated posts about how some random dude raised $10m in 7 days. Okay Jonathan, but what about the HOW?? How did you write your first pitch? How many rejection calls did you get? What is an MVP? There simply isn’t a platform out there to document your founding journey and find inspiration within a community of people who are doing the same as you. What better way to feel motivated then to see someone actually document their process? Solution: I’m working on building a social media platform for aspiring/founders to connect through the RAW, UNFILTERED process of turning ideas into reality in REAL time. It’s all gonna be around the “building in public “ concept and content creation. Picture an instagram/tiktok profile where instead of seeing someone’s dog you see them documenting their founding process—from the moment they had the idea, to the moment they launched, you’re going to see the successes, the fails, the rejected calls, all documented through actual content and not some AI generated LinkedIn post. Imagine if you wanted to learn about how Steve Jobs started Apple , you could simply go through his profile on this app—exactly. To make sure all interactions are meaningful people would have to apply. It’s a truly curated community, with REAL people, building REAL things in REAL time, and not just tell us the story of how they did it… Audience: I’m targeting people who have a burning desire of building a business and early stage founders starting their founder journeys, that don’t have a support network and simply don’t know where to start. People who are tired of watching 30 min “ultimate guides “ on how to make it on YouTube from “business gurus” selling courses. People who haven’t reached the min ARR required to join an “exclusive “ founder a community. People who can’t simply just move to the US to get into the “exclusive” YC combinator. People who want to connect with real people building real things and not anonymous people on Reddit, or LinkedIn influencers again trying to promote their services. I believe in the idea because I’m also part of my audience. Have always wanted to start my own thing just never knew how to and where to find a community of likeminded people . I don’t know any founders myself, I come from a non-entrepreneurial society and I’d pay good money to access a community of REAL passionate founders building REAL things, in REAL time. This would be my first ever business, and I want to share my journey building it and hopefully inspire others to just start so I’ve created a mailing list to keep anyone interested in the project updated on my fails , learnings and successes. I’m not worried about “making it” but just “starting” and hopefully reach the right audience and inspire anyone to start whatever they have marinating in their thoughts. If you’re a founder struggling with staying consistent or an aspiring founder with an insane desire of starting and don’t know how to start, I’d love to get your feedback on what’s stopping you, your challenges starting out and what you’d find useful in such platform. And finally would this be something that interests you?? PS: casually looking for a technical co-founder

I’ve Tested All the Image Generation Tools for My Small Business
reddit
LLM Vibe Score0
Human Vibe Score0.6
astronautlyraThis week

I’ve Tested All the Image Generation Tools for My Small Business

Personally I hate paying for subscriptions unless it was absolutely necessary. Given that I don't have the budget to hire a graphic designer I started playing with all the new Generative AI tools and these are the ones I've narrowed it down to that have made the most impact. I posted this breakdown on r/AIforBusinessFounders but will share it here as well. Hope this compilation helps a fellow entrepreneur. If you’ve been exploring AI tools for generating images, you’ve probably come across big names like DALL·E, Adobe Photoshop, and MidJourney (finally moved off the dreadful Discord prompting thankfully!)  While they each have their strengths, they also have their quirks. Here’s the breakdown: DALL·E by OpenAI Pros: It’s integrated directly into ChatGPT, so if you’re already on a paid plan, you’re good to go—no extra fees. It's also embedded in Canva which is convenient if you’re designing social media posts or quick mockups. Cons: The image quality isn’t amazing. It often looks a bit flat or off, but I think where I struggle is you only get one output per generation, so there’s not much variety. Adobe Photoshop Pros: If you’re already using Photoshop, this is a nice addition. It lets you partially generate images within your edits, which can be handy for things like background replacements. When it comes to generating full images though, I find this tool really struggles. Cons: The image quality still has room for improvement—hands and fingers, in particular, are a consistent issue. Plus, you need an Adobe Creative Cloud subscription to access it. MidJourney Pros: Hands down, this tool produces the best-quality images. You get multiple outputs per prompt, and what really sets it apart is the ability to refine your favorite image. You can subtly tweak or drastically change it, depending on your needs. It previously only operated on Discord but it now has migrated to it's own platform so that's been a huge pro for me. Cons: It’s not cheap—MidJourney requires its own paid membership and comes with limited tokens, so you’ll need to budget your usage. The biggest con for me in the past was that you had to prompt in a Discord channel but now that it has own platform, it's no longer an issue. After putting all three to the test, my personal favorite is MidJourney. If image quality and creative control are your priorities, it’s hard to beat. That said, DALL·E and Adobe are solid options if you’re already using their platforms and want to save money. Are there any hidden gems I might have missed? If so let me know, I'd love to give them a try.

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

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

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

What I learn from my $200 MRR App I built 4 months ago?
reddit
LLM Vibe Score0
Human Vibe Score0.857
ricky0603This week

What I learn from my $200 MRR App I built 4 months ago?

4 month ago, I am just a 10-years experienced product manager without any software development experience. I have an $3K/month job, but I am so tired, I don’t like my life, don’t like my boss, don’t like my daily work, that make me feeling I already died however I am still living. I yearn for freedom and want to live each day the way I want to. So I quit my job, and become a Indie developer to build my own business, my own app, even my own life. I am so grateful for this time and experience, now my app reach $200 MRR, still very little compared to my previous salary, but I never regret. I have learned lots of things from this time and experience, more than I had in last 10 years. Here is the time-line of my App: \- Sep 2023: Launch first version to iOS App store \- Oct 2023: Release in-app-purchase features and have first subscriber, the revenue in October is $154 \- Nov 2023: Change from subscription to pay per use, and I did lots of marketing jobs in November, however, the revenue reduced to only $40. \- Dec 2023: Change back to subscription, and stop some invalid marketing jobs, only keep the ones that actually work. I almost did nothing in December, and the revenue come to $243. During this process, I have learned lots of things, there are some of them that I think could help you as well. Web or App My App is an iOS app that only can running on Apple’s device such like iPhone/iPad or Mac with Apple silicon. Many people ask me why my product is an iOS app not a website, because they don’t have any Apple device. It's true that promoting an app is much harder than promoting a website. However I am now very glad I made an App and not a website! If I make a website, I don't think it's possible to make $100 in the first month. My App is about keyword research, to help people find some ideas from search keyword, because every keyword people searched in Google are representing a real need of them, also can be used in SEO field. However there are a lot of website tools about keyword research, some of them are famous like Ahrefs, SEMrush… I have no intention of competing with them. Actually I don’t have any chance. While in app store, there are little apps about keyword research, each of them have terrible data and user experience, that means if my app has better data and experience that could be my chance. In fact, the App store brings me 20 organic installs a day that Google would never have been able to bring me if I had a website, at least for the first few months. Furthermore, Apple nearly did everything for developer, I don’t need to care about user login, payment and so on, Apple did everything, I just need to call their API, that save lots of time, if I build a website, I need to implement login and payment by myself, that would add some extra work. Not to mention I'd need to buy servers and domains, that would cost me a lot of money. Although Apple will take 30% of the revenue, I can live with that in the early stages because the most important thing for me is to get the product to market as soon as possible. Actually thought Apple’s SMB program, the take rate is 15% now. So Web or App is not important in the early stage, time is important, if people need my product, it's easy to make a website one. More Users or More Valuable Users In November, I notice some users would like use my app, and they were meet paywall, but they never subscribe. I provided 7 day free trail, but it seem that they don’t like it. So I decide to change subscription to pay per use. Because as a user, I don’t like subscription as well, pay per use seem like more friendly. So I change from subscription to pay per use. People can afford $9.99 to subscribe monthly for unlimited use or pay $1.99 for each data they want(First purchase is $0.99 then $1.99). I was expecting more user to pay, but it was the complete opposite! Some users who would have paid a higher subscription fee are switching to a lower priced single payment. Users are encountering paywalls more often, and each time they need to make a decision about whether or not to pay, which increases the probability that they will abandon payment. This resulted in a 75% decrease in revenue in November. In fact, the mostly of my revenue comes from a handful of long-cycle subscribers, such as annual subscription. \\Few bring in most of the revenue,\\ that is the most important thing I learned. You don't need a lot of customers, you just need more valuable ones. That's why it's only right to design a mechanism to filter out high-value customers and focus on them, all the things you want do is just let more people into the filter, and from that point of view, subscription with free trial period is the best way, even if most people don't like it. The rule of 20/80 will always be there. The most important thing is always focus on the 20 percent things and people. Effort does not always guarantee rewards. Unless one engages in deep thinking, or most efforts are invalid. I have been working very hard to promote my product for a period of time. It’s about in November. I did a lot of job, such as write script to send message to my potential clients on Fiverr, post and write comments on others post on Reddit, find related questions and answer them on Quora, post and comments on Twitte, etc. During that period, I was exhausted every day, but the outcome did not meet my expectations. There is only little growth on App installation, even less revenue than before. That make me frustrated. I finally realized that If I need to put in a tremendous amount of effort just to make a little progress, there is must something wrong. So I stop 80% of promote work I have ever did, only keep app store search ad, which will bring a installation with less than $0.5 cost. Then I dive into long time and deeply thinking, I spent more time on reading books, investigate other product with great MRR, watch interviews with people who are already living the kind of life I aspire to live, for example, u/levelsio. These things have given me great inspiration, and my life has become easier. It seems that the life I anticipated when I resigned is getting closer. I also have a clearer understanding of my app. Meanwhile, MRR has been growing. This experience let me learn that effort does not always guarantee results. Many times, our efforts are just wishful thinking, they are invalid, do the right thing after deeply thinking is more important. What Next? My goal is reach $3K MRR, as same as my job payment, I will never stop to building things, and I will keep my currently lifestyle. I still don't know how to get more people to use my app, but levelsio's interviews give me some inspiration that I can verified something by manually instead of build a software. I plan to launch a trend analysis product based on the keyword data provided by my current app. I have always wanted to combine AI to build such a product, but I didn't know how to do it. Now I intend to manually complete it first and start software development once there are paying users. If you are interested to my App, you could try it.

How do byte-level language models work?
reddit
LLM Vibe Score0
Human Vibe Score1
Additional-Ad-7043This week

How do byte-level language models work?

I've recently been trying to pre-train my own small language model on the tiny-series datasets on huggingface: https://huggingface.co/collections/nampdn-ai/tiny-series-6503910fd491144159519c70. I also wanted to use a model similar to MEGABYTE: https://arxiv.org/pdf/2305.07185.pdf, but I don't understand how using bytes would work. The only implementation I could find: https://github.com/lucidrains/MEGABYTE-pytorch used str(chr(max(32, token))) to decode any token (byte) to a character and put the embedding size as 256. Firstly, why 256 and not 256-32 as any values below 32 are ignored? Also, many byte-level models including this and ByteT5 mention that they can process any text sequence even in a multilingual setting, however how would that be true if we are only using one byte, would we have to move to 2 bytes or use an UNK token, and if we did use 2 bytes that would make our embedding size around 65000 which defeats sort of the point as one of the advantages mentioned is that we are able to use a small embedding matrix? Furthermore, most language models add special tokens like bos, eos, unk and even for llama they use beginning of instruction, end of instruction, and more for system instructions, response, context... Should I use something like this as my dataset has some structures where there is a context, instruction and response, and if i did how would I add these if I'm using byte-level encodings? Final questions: Firstly, for the datasets mentioned including code,stories,webtext,... would I tokenise all of these datasets then concatenate them to then randomly sample from, or should i train seperately on each as some like code and webtext are much larger than the others? Finally, for the webtext part of the dataset, there is a passage of text then a passage analysing the text (main ideas,purpose,...), how should I encode this, should I use an extra ANALYSE token or just concatenate? Thank you for reading this far, I am sort of a beginner so if I said something stupid please point it out. Also, if there were unclear parts in my question I'm sorry as I struggled how to word these questions. Any help would be appreciated!

Study Plan for Learning Data Science Over the Next 12 Months [D]
reddit
LLM Vibe Score0
Human Vibe Score1
daniel-dataThis week

Study Plan for Learning Data Science Over the Next 12 Months [D]

In this thread, I address a study plan for 2021. In case you're interested, I wrote a whole article about this topic: Study Plan for Learning Data Science Over the Next 12 Months Let me know your thoughts on this. &#x200B; https://preview.redd.it/emg20nzhet661.png?width=1170&format=png&auto=webp&s=cf09e4dc5e82ba2fd7b57c706ba2873be57fe8de We are ending 2020 and it is time to make plans for next year, and one of the most important plans and questions we must ask is what do we want to study?, what do we want to enhance?, what changes do we want to make?, and what is the direction we are going to take (or continue) in our professional careers?. Many of you will be starting on the road to becoming a data scientist, in fact you may be evaluating it, since you have heard a lot about it, but you have some doubts, for example about the amount of job offers that may exist in this area, doubts about the technology itself, and about the path you should follow, considering the wide range of options to learn. I’m a believer that we should learn from various sources, from various mentors, and from various formats. By sources I mean the various virtual platforms and face-to-face options that exist to study. By mentors I mean that it is always a good idea to learn from different points of view and learning from different teachers/mentors, and by formats I mean the choices between books, videos, classes, and other formats where the information is contained. When we extract information from all these sources we reinforce the knowledge learned, but we always need a guide, and this post aims to give you some practical insights and strategies in this regard. To decide on sources, mentors and formats it is up to you to choose. It depends on your preferences and ease of learning: for example, some people are better at learning from books, while others prefer to learn from videos. Some prefer to study on platforms that are practical (following online code), and others prefer traditional platforms: like those at universities (Master’s Degree, PHDs or MOOCs). Others prefer to pay for quality content, while others prefer to look only for free material. That’s why I won’t give a specific recommendation in this post, but I’ll give you the whole picture: a study plan. To start you should consider the time you’ll spend studying and the depth of learning you want to achieve, because if you find yourself without a job you could be available full time to study, which is a huge advantage. On the other hand, if you are working, you’ll have less time and you’ll have to discipline yourself to be able to have the time available in the evenings, mornings or weekends. Ultimately, the important thing is to meet the goal of learning and perhaps dedicating your career to this exciting area! We will divide the year into quarters as follows First Quarter: Learning the Basics Second Quarter: Upgrading the Level: Intermediate Knowledge Third Quarter: A Real World Project — A Full-stack Project Fourth Quarter: Seeking Opportunities While Maintaining Practice First Quarter: Learning the Basics &#x200B; https://preview.redd.it/u7t9bthket661.png?width=998&format=png&auto=webp&s=4ad29cb43618e7acf793259243aa5a60a8535f0a If you want to be more rigorous you can have start and end dates for this period of study of the bases. It could be something like: From January 1 to March 30, 2021 as deadline. During this period you will study the following: A programming language that you can apply to data science: Python or R. We recommend Python due to the simple fact that approximately 80% of data science job offers ask for knowledge in Python. That same percentage is maintained with respect to the real projects you will find implemented in production. And we add the fact that Python is multipurpose, so you won’t “waste” your time if at some point you decide to focus on web development, for example, or desktop development. This would be the first topic to study in the first months of the year. Familiarize yourself with statistics and mathematics. There is a big debate in the data science community about whether we need this foundation or not. I will write a post later on about this, but the reality is that you DO need it, but ONLY the basics (at least in the beginning). And I want to clarify this point before continuing. We could say that data science is divided in two big fields: Research on one side and putting Machine Learning algorithms into production on the other side. If you later decide to focus on Research then you are going to need mathematics and statistics in depth (very in depth). If you are going to go for the practical part, the libraries will help you deal with most of it, under the hood. It should be noted that most job offers are in the practical part. For both cases, and in this first stage you will only need the basics of: Statistics (with Python and NumPy) Descriptive statistics Inferential Statistics Hypothesis testing Probability Mathematics (with Python and NumPy) Linear Algebra (For example: SVD) Multivariate Calculus Calculus (For example: gradient descent) Note: We recommend that you study Python first before seeing statistics and mathematics, because the challenge is to implement these statistical and mathematical bases with Python. Don’t look for theoretical tutorials that show only slides or statistical and/or mathematical examples in Excel/Matlab/Octave/SAS and other different to Python or R, it gets very boring and impractical! You should choose a course, program or book that teaches these concepts in a practical way and using Python. Remember that Python is what we finally use, so you need to choose well. This advice is key so you don’t give up on this part, as it will be the most dense and difficult. If you have these basics in the first three months, you will be ready to make a leap in your learning for the next three months. Second Quarter: Upgrading the Level: Intermediate Knowledge &#x200B; https://preview.redd.it/y1y55vynet661.png?width=669&format=png&auto=webp&s=bd3e12bb112943025c39a8975faf4d64514df275 If you want to be more rigorous you can have start and end dates for this period of study at the intermediate level. It could be something like: From April 1 to June 30, 2021 as deadline. Now that you have a good foundation in programming, statistics and mathematics, it is time to move forward and learn about the great advantages that Python has for applying data analysis. For this stage you will be focused on: Data science Python stack Python has the following libraries that you should study, know and practice at this stage Pandas: for working with tabular data and make in-depth analysis Matplotlib and Seaborn: for data visualization Pandas is the in-facto library for data analysis, it is one of the most important (if not the most important) and powerful tools you should know and master during your career as a data scientist. Pandas will make it much easier for you to manipulate, cleanse and organize your data. Feature Engineering Many times people don’t go deep into Feature Engineering, but if you want to have Machine Learning models that make good predictions and improve your scores, spending some time on this subject is invaluable! Feature engineering is the process of using domain knowledge to extract features from raw data using data mining techniques. These features can be used to improve the performance of machine learning algorithms. Feature engineering can be considered as applied machine learning itself. To achieve the goal of good feature engineering you must know the different techniques that exist, so it is a good idea to at least study the main ones. Basic Models of Machine Learning At the end of this stage you will start with the study of Machine Learning. This is perhaps the most awaited moment! This is where you start to learn about the different algorithms you can use, which particular problems you can solve and how you can apply them in real life. The Python library we recommend you to start experimenting with ML is: scikit-learn. However it is a good idea that you can find tutorials where they explain the implementation of the algorithms (at least the simplest ones) from scratch with Python, since the library could be a “Black Box” and you might not understand what is happening under the hood. If you learn how to implement them with Python, you can have a more solid foundation. If you implement the algorithms with Python (without a library), you will put into practice everything seen in the statistics, mathematics and Pandas part. These are some recommendations of the algorithms that you should at least know in this initial stage Supervised learning Simple Linear Regression Multiple Linear Regression K-nearest neighbors (KNN) Logistic Regression Decision Trees Random Forest Unsupervised Learning K-Means PCA Bonus: if you have the time and you are within the time ranges, you can study these others Gradient Boosting Algorithms GBM XGBoost LightGBM CatBoost Note: do not spend more than the 3 months stipulated for this stage. Because you will be falling behind and not complying with the study plan. We all have shortcomings at this stage, it is normal, go ahead and then you can resume some concepts that did not understand in detail. The important thing is to have the basic knowledge and move forward! If at least you succeed to study the mentioned algorithms of supervised and unsupervised learning, you will have a very clear idea of what you will be able to do in the future. So don’t worry about covering everything, remember that it is a process, and ideally you should have some clearly established times so that you don’t get frustrated and feel you are advancing. So far, here comes your “theoretical” study of the basics of data science. Now we’ll continue with the practical part! Third Quarter: A Real World Project — A Full-stack Project &#x200B; https://preview.redd.it/vrn783vqet661.png?width=678&format=png&auto=webp&s=664061b3d33b34979b74b10b9f8a3d0f7b8b99ee If you want to be more rigorous you can have start and end dates for this period of study at the intermediate level. It could be something like: From July 1 to September 30, 2021 as deadline. Now that you have a good foundation in programming, statistics, mathematics, data analysis and machine learning algorithms, it is time to move forward and put into practice all this knowledge. Many of these suggestions may sound out of the box, but believe me they will make a big difference in your career as a data scientist. The first thing is to create your web presence: Create a Github (or GitLab) account, and learn Git*. Being able to manage different versions of your code is important, you should have version control over them, not to mention that having an active Github account is very valuable in demonstrating your true skills. On Github, you can also set up your Jupyter Notebooks and make them public, so you can show off your skills as well. This is mine for example: https://github.com/danielmoralesp Learn the basics of web programming*. The advantage is that you already have Python as a skill, so you can learn Flask to create a simple web page. Or you can use a template engine like Github Pages, Ghost or Wordpress itself and create your online portfolio. Buy a domain with your name*. Something like myname.com, myname.co, myname.dev, etc. This is invaluable so you can have your CV online and update it with your projects. There you can make a big difference, showing your projects, your Jupyter Notebooks and showing that you have the practical skills to execute projects in this area. There are many front-end templates for you to purchase for free or for payment, and give it a more personalized and pleasant look. Don’t use free sub-domains of Wordpress, Github or Wix, it looks very unprofessional, make your own. Here is mine for example: https://www.danielmorales.dev/ Choose a project you are passionate about and create a Machine Learning model around it. The final goal of this third quarter is to create ONE project, that you are passionate about, and that is UNIQUE among others. It turns out that there are many typical projects in the community, such as predicting the Titanic Survivors, or predicting the price of Houses in Boston. Those kinds of projects are good for learning, but not for showing off as your UNIQUE projects. If you are passionate about sports, try predicting the soccer results of your local league. If you are passionate about finance, try predicting your country’s stock market prices. If you are passionate about marketing, try to find someone who has an e-commerce and implement a product recommendation algorithm and upload it to production. If you are passionate about business: make a predictor of the best business ideas for 2021 :) As you can see, you are limited by your passions and your imagination. In fact, those are the two keys for you to do this project: Passion and Imagination. However don’t expect to make money from it, you are in a learning stage, you need that algorithm to be deployed in production, make an API in Flask with it, and explain in your website how you did it and how people can access it. This is the moment to shine, and at the same time it’s the moment of the greatest learning. You will most likely face obstacles, if your algorithm gives 60% of Accuracy after a huge optimization effort, it doesn’t matter, finish the whole process, deploy it to production, try to get a friend or family member to use it, and that will be the goal achieved for this stage: Make a Full-stack Machine Learning project. By full-stack I mean that you did all the following steps: You got the data from somewhere (scrapping, open data or API) You did a data analysis You cleaned and transformed the data You created Machine Learning Models You deployed the best model to production for other people to use. This does not mean that this whole process is what you will always do in your daily job, but it does mean that you will know every part of the pipeline that is needed for a data science project for a company. You will have a unique perspective! Fourth Quarter: Seeking Opportunities While Maintaining Practice &#x200B; https://preview.redd.it/qd0osystet661.png?width=1056&format=png&auto=webp&s=2da456b15985b2793041256f5e45bca99a23b51a If you want to be more rigorous you can have start and end dates for this period of study at the final level. It could be something like: From October 1 to December 31, 2021 as deadline. Now you have theoretical and practical knowledge. You have implemented a model in production. The next step depends on you and your personality. Let’s say you are an entrepreneur, and you have the vision to create something new from something you discovered or saw an opportunity to do business with this discipline, so it’s time to start planning how to do it. If that’s the case, obviously this post won’t cover that process, but you should know what the steps might be (or start figuring them out). But if you are one of those who want to get a job as a data scientist, here is my advice. Getting a job as a data scientist “You’re not going to get a job as fast as you think, if you keep thinking the same way”.Author It turns out that all people who start out as data scientists imagine themselves working for the big companies in their country or region. Or even remote. It turns out that if you aspire to work for a large company like data scientist you will be frustrated by the years of experience they ask for (3 or more years) and the skills they request. Large companies don’t hire Juniors (or very few do), precisely because they are already large companies. They have the financial muscle to demand experience and skills and can pay a commensurate salary (although this is not always the case). The point is that if you focus there you’re going to get frustrated! Here we must return to the following advise: “You need creativity to get a job in data science”. Like everything else in life we have to start at different steps, in this case, from the beginning. Here are the scenarios If you are working in a company and in a non-engineering role you must demonstrate your new skills to the company you are working for*. If you are working in the customer service area, you should apply it to your work, and do for example, detailed analysis of your calls, conversion rates, store data and make predictions about it! If you can have data from your colleagues, you could try to predict their sales! This may sound funny, but it’s about how creatively you can apply data science to your current work and how to show your bosses how valuable it is and EVANGELIZE them about the benefits of implementation. You’ll be noticed and they could certainly create a new data related department or job. And you already have the knowledge and experience. The key word here is Evangelize. Many companies and entrepreneurs are just beginning to see the power of this discipline, and it is your task to nurture that reality. If you are working in an area related to engineering, but that is not data science*. Here the same applies as the previous example, but you have some advantages, and that is that you could access the company’s data, and you could use it for the benefit of the company, making analyses and/or predictions about it, and again EVANGELIZING your bosses your new skills and the benefits of data science. If you are unemployed (or do not want, or do not feel comfortable following the two examples above)*, you can start looking outside, and what I recommend is that you look for technology companies and / or startups where they are just forming the first teams and are paying some salary, or even have options shares of the company. Obviously here the salaries will not be exorbitant, and the working hours could be longer, but remember that you are in the learning and practice stage (just in the first step), so you can not demand too much, you must land your expectations and fit that reality, and stop pretending to be paid $ 10,000 a month at this stage. But, depending of your country $1.000 USD could be something very interesting to start this new career. Remember, you are a Junior at this stage. The conclusion is: don’t waste your time looking at and/or applying to offers from big companies, because you will get frustrated. Be creative, and look for opportunities in smaller or newly created companies. Learning never stops While you are in that process of looking for a job or an opportunity, which could take half of your time (50% looking for opportunities, 50% staying in practice), you have to keep learning, you should advance to concepts such as Deep Learning, Data Engineer or other topics that you feel were left loose from the past stages or focus on the topics that you are passionate about within this group of disciplines in data science. At the same time you can choose a second project, and spend some time running it from end-to-end, and thus increase your portfolio and your experience. If this is the case, try to find a completely different project: if the first one was done with Machine Learning, let this second one be done with Deep learning. If the first one was deployed to a web page, that this second one is deployed to a mobile platform. Remember, creativity is the key! Conclusion We are at an ideal time to plan for 2021, and if this is the path you want to take, start looking for the platforms and media you want to study on. Get to work and don’t miss this opportunity to become a data scientist in 2021! Note: we are building a private community in Slack of data scientist, if you want to join us write to the email: support@datasource.ai I hope you enjoyed this reading! you can follow me on twitter or linkedin Thank you for reading!

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

MMML | Deploy HuggingFace training model rapidly based on MetaSpore

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

6 principles to data architecture that facilitate innovation
reddit
LLM Vibe Score0
Human Vibe Score1
Competitive_Speech36This week

6 principles to data architecture that facilitate innovation

My team and I have been re-building our company's data architecture. In the process of doing so, I got together six key principles to transforming data architectures and thought I would share them, as a strong data architecture is crucial for businesses looking to stay competitive in the digital landscape, as it improves decision-making, time to market, and data security. When executed with efficiency, a resilient data architecture unleashes unparalleled degrees of agility. Principle 1: Agility and flexibility To quickly adjust to market fluctuations, businesses must create adaptable data infrastructures that can effortlessly manage an ever-growing influx of data. To accomplish this objective, we recommend to our clients to implement Enterprise Service Bus, Enterprise Data Warehouse, and Master Data Management integrated together. &#x200B; I believe the best option is this: \- By centralizing communication, ESB reduces the time and effort required to integrate new systems; \- EDW consolidates data from different sources, resulting in a 50% reduction in software implementation time; \- Finally, MDM ensures consistency and accuracy across the organization, leading to better decision-making and streamlined operations. Implementing these solutions can lead to reduced software implementation time, better ROI, and more manageable data architecture. By fostering a culture of collaboration and adopting modern technologies and practices, businesses can prioritize agility and flexibility in their data architecture to increase the pace of innovation. Principle 2: Modularity and reusability Data architecture that fosters modularity and reusability is essential for accelerating innovation within an organization. By breaking data architecture components into smaller, more manageable pieces, businesses can enable different teams to leverage existing architecture components, reducing redundancy and improving overall efficiency. MDM can promote modularity and reusability by creating a central repository for critical business data. This prevents duplication and errors, improving efficiency and decision-making. MDM enables a single source of truth for data, accessible across multiple systems, which promotes integration and scalability. MDM also provides standardized data models, rules, and governance policies that reduce development time, increase quality, and ensure proper management throughout the data’s lifecycle. Another way to achieve modularity in data architecture is through the use of microservices and scripts for Extract, Transform, and Load (ETL) processes. Adopting a structured methodology and framework can ensure these components are well-organized, making it easier for teams to collaborate and maintain the system. Microservices can also contribute to modularity and reusability in data architecture. These small, independent components can be developed, deployed, and scaled independently of one another. By utilizing microservices, organizations can update or replace individual components without affecting the entire system, improving flexibility and adaptability. Principle 3: Data quality and consistency The efficiency of operations depends on data’s quality, so a meticulously crafted data architecture plays a pivotal role in preserving it, empowering enterprises to make well-informed decisions based on credible information. Here are some key factors to consider that will help your company ensure quality: \- Implementing Master Data Management (MDM) – this way, by consolidating, cleansing, and standardizing data from multiple sources, your IT department will be able to create a single, unified view of the most important data entities (customers, products, and suppliers); \- Assigning data stewardship responsibilities to a small team or an individual specialist; \- Considering implementing data validation, data lineage, and data quality metrics; \- By implementing MDM and adopting a minimal data stewardship approach, organizations can maintain high-quality data that drives innovation and growth. Principle 4: Data governance Data governance is a strategic framework that goes beyond ensuring data quality and consistency. It includes ensuring data security, privacy, accessibility, regulatory compliance, and lifecycle management. Here are some key aspects of data governance: \- Implementing robust measures and controls to protect sensitive data from unauthorized access, breaches, and theft. This is only possible through including encryption, access controls, and intrusion detection systems into your company’s IT architecture; \- Adhering to data privacy regulations and guidelines, such as the General Data Protection Regulation (GDPR) and the California Consumer Privacy Act (CCPA); \- Defining stringent conditions for who has access to specific data assets to maintain control over data and ensure its accessibility only for legitimate purposes. Managing the entire lifecycle of data, from creation and storage to archiving and disposal, including defining policies for data retention, archiving, and deletion in compliance with legal and regulatory requirements. To facilitate effective data governance, organizations can leverage various tools and technologies, such as: \- Data cataloging tools: Solutions like Collibra, Alation, or Informatica Enterprise Data Catalog help organizations discover, understand, and manage their data assets. \- Data lineage tools: Tools like Talend, IBM InfoSphere, or Apache Atlas help track data’s origin, transformation, and usage, providing insights into data quality issues and potential areas for improvement. \- Data quality tools: Solutions like Informatica Data Quality, Trifacta, or SAS Data Quality help organizations maintain high-quality data by identifying and correcting errors, inconsistencies, and inaccuracies. \- Data security and privacy tools: Tools like Varonis, BigID, or Spirion help protect sensitive data and ensure compliance with data privacy regulations. Principle 5: Cloud-first approach A cloud-first approach prioritizes cloud-based solutions over on-premises ones when it comes to data management. Cloud-based data management pros: \- Virtually limitless scalability, so that organizations can grow and adapt to changing data requirements without significant infrastructure investments; \- The pay-as-you-go model of cloud services reduces maintenance costs usually associated with the on-premise choice; \- Greater flexibility for deploying and integrating new technologies and services; \- Cloud can be accessed from anywhere, at any time, turning team collaboration and remote work into a breeze; \- Built-in backup and disaster recovery capabilities, ensuring data safety and minimizing downtime in case of emergencies. Cloud-based data management cons: \- Cloud-first approach raises many data security, privacy, and compliance concerns; \- Transferring large data volumes to and from cloud is often time-consuming and results in increased latency for certain apps; \- Relying on a single cloud provider makes it difficult to switch them or move back to the on-premises option without significant funds and effort. Challenges that organizations that choose a cloud-first approach face: \- Integrating cloud-based systems with on-premises ones can be complex and time-consuming; \- Ensuring data governance and compliance in a multi-cloud or hybrid environment is also another problem reported by my clients. How EDW, ESB, and MDM promote cloud-first approach: A cloud-based EDW centralizes data from multiple sources, enabling a unified view of the organization’s data and simplifying data integration across cloud and on-premises systems. An ESB facilitates communication between disparate cloud and on-premises systems, streamlining data integration and promoting a modular architecture. Cloud-based MDM solutions are used for maintaining data quality and consistency across multiple data sources and environments. Principle 6: Automation and artificial intelligence Incorporating automation tools and AI technologies into data architecture can optimize processes and decision-making. Key Applications: \- Data ingestion and integration: Automation simplifies data schema updates and identifies data quality issues, while AI-assisted development helps create tailored connectors, scripts, and microservices. \- Data quality management: Machine learning algorithms improve data quality and consistency by automatically detecting and correcting inconsistencies and duplicates. \- Predictive analytics: AI and machine learning models analyze historical data to predict trends, identify opportunities, and uncover hidden patterns for better-informed decisions. How No-Code Tools and AI-Assisted Development Work: Business users define data requirements and workflows using no-code tools, enabling AI models to understand their needs. AI models process the information, generating recommendations for connector creation, ETL scripts, and microservices. Developers use AI-generated suggestions to accelerate development and tailor solutions to business needs. By combining automation, AI technologies, and no-code tools, organizations can streamline data architecture processes and bridge the gap between business users and developers, ultimately accelerating innovation. I share more tips on building an agile data architectures in my blog.

How I Built an Agentic Marketing Campaign Strategist
reddit
LLM Vibe Score0
Human Vibe Score1
AniketWorkThis week

How I Built an Agentic Marketing Campaign Strategist

Marketing at Scale: How One AI System Replaces Hundreds of Strategy Hours Article https://i.redd.it/uekqj3zmerme1.gif https://i.redd.it/30rk23zmerme1.gif https://preview.redd.it/fk1t53zmerme1.png?width=797&format=png&auto=webp&s=d07f473a9556fbd38885b3a2f862101d9b25424e https://preview.redd.it/n84113zmerme1.jpg?width=1914&format=pjpg&auto=webp&s=f42679269a1003e1c8d6501dd2d53e10db745bba https://preview.redd.it/l13ae3zmerme1.jpg?width=791&format=pjpg&auto=webp&s=ecab3c295c2a416bc0fed8c62fecbe3321e37093 TL;DR This article guides you through building an AI-powered marketing strategist using Python. It combines vector databases, language models, and PDF generation to create customized marketing strategies automatically. I’ll show you the complete system architecture, from storing marketing knowledge to generating professional strategy documents, with practical code examples you can implement today. Perfect for marketers and developers looking to leverage AI for business growth. Introduction Welcome to the exciting intersection of marketing and artificial intelligence! In today’s digital world, creating effective marketing campaigns requires deep expertise, market research, and creative thinking. But what if you could automate parts of this process? That’s exactly what I set out to build: an AI system that generates comprehensive marketing strategies tailored to specific products, audiences, and budgets. What’s This Article About? This article walks you through the creation of an AI-powered marketing strategist that combines the retrieval of relevant marketing knowledge with advanced language generation to produce detailed campaign strategies. The system I built uses Retrieval-Augmented Generation (RAG), which enhances AI outputs by grounding them in specific knowledge sources. Here’s how it works: You provide a simple campaign description (like “a new eco-friendly water bottle targeting millennials with a budget of $50,000”) The system searches a knowledge base of marketing principles and best practices It then uses a language model to craft a comprehensive strategy that includes campaign objectives, target audience analysis, channel selection, content ideas, budget allocation, and measurement KPIs Finally, it generates a professional PDF document with your complete marketing strategy The beauty of this approach is that it combines the creativity and adaptability of AI with established marketing frameworks, ensuring the strategies are both innovative and grounded in proven principles. Why Read It? AI is rapidly transforming how businesses operate, and marketing is at the forefront of this revolution. According to recent studies, companies that effectively leverage AI in their marketing efforts see significant improvements in customer engagement, conversion rates, and ROI. Even if you’re not building a system for a real company right now, understanding how to implement AI in marketing processes gives you valuable skills and insights. This article provides a practical example of how AI can: Save marketers countless hours of research and strategy development Ensure consistency in marketing approaches across different campaigns Generate creative ideas that might not have been considered otherwise Scale marketing expertise across an organization By following along, you’ll gain hands-on experience with technologies like vector databases, language models, and automated document generation — all skills that are increasingly valuable in today’s business environment.

How I Built an Agentic Marketing Campaign Strategist
reddit
LLM Vibe Score0
Human Vibe Score1
AniketWorkThis week

How I Built an Agentic Marketing Campaign Strategist

Marketing at Scale: How One AI System Replaces Hundreds of Strategy Hours Article https://i.redd.it/uekqj3zmerme1.gif https://i.redd.it/30rk23zmerme1.gif https://preview.redd.it/fk1t53zmerme1.png?width=797&format=png&auto=webp&s=d07f473a9556fbd38885b3a2f862101d9b25424e https://preview.redd.it/n84113zmerme1.jpg?width=1914&format=pjpg&auto=webp&s=f42679269a1003e1c8d6501dd2d53e10db745bba https://preview.redd.it/l13ae3zmerme1.jpg?width=791&format=pjpg&auto=webp&s=ecab3c295c2a416bc0fed8c62fecbe3321e37093 TL;DR This article guides you through building an AI-powered marketing strategist using Python. It combines vector databases, language models, and PDF generation to create customized marketing strategies automatically. I’ll show you the complete system architecture, from storing marketing knowledge to generating professional strategy documents, with practical code examples you can implement today. Perfect for marketers and developers looking to leverage AI for business growth. Introduction Welcome to the exciting intersection of marketing and artificial intelligence! In today’s digital world, creating effective marketing campaigns requires deep expertise, market research, and creative thinking. But what if you could automate parts of this process? That’s exactly what I set out to build: an AI system that generates comprehensive marketing strategies tailored to specific products, audiences, and budgets. What’s This Article About? This article walks you through the creation of an AI-powered marketing strategist that combines the retrieval of relevant marketing knowledge with advanced language generation to produce detailed campaign strategies. The system I built uses Retrieval-Augmented Generation (RAG), which enhances AI outputs by grounding them in specific knowledge sources. Here’s how it works: You provide a simple campaign description (like “a new eco-friendly water bottle targeting millennials with a budget of $50,000”) The system searches a knowledge base of marketing principles and best practices It then uses a language model to craft a comprehensive strategy that includes campaign objectives, target audience analysis, channel selection, content ideas, budget allocation, and measurement KPIs Finally, it generates a professional PDF document with your complete marketing strategy The beauty of this approach is that it combines the creativity and adaptability of AI with established marketing frameworks, ensuring the strategies are both innovative and grounded in proven principles. Why Read It? AI is rapidly transforming how businesses operate, and marketing is at the forefront of this revolution. According to recent studies, companies that effectively leverage AI in their marketing efforts see significant improvements in customer engagement, conversion rates, and ROI. Even if you’re not building a system for a real company right now, understanding how to implement AI in marketing processes gives you valuable skills and insights. This article provides a practical example of how AI can: Save marketers countless hours of research and strategy development Ensure consistency in marketing approaches across different campaigns Generate creative ideas that might not have been considered otherwise Scale marketing expertise across an organization By following along, you’ll gain hands-on experience with technologies like vector databases, language models, and automated document generation — all skills that are increasingly valuable in today’s business environment.

Browser Agents Real Example
reddit
LLM Vibe Score0
Human Vibe Score1
No_Information6299This week

Browser Agents Real Example

I made a Browser Price Matching Tool that uses browser automation and some clever skills to adjust your product prices based on real-time web searches data. If you're into scraping, automation, or just love playing with the latest in ML-powered tools like OpenAI's GPT-4, this one's for you. What My Project Does The tool takes your current product prices (think CSV) and finds similar products online (targeting Amazon for demo purposes). It then compares prices, allowing you to adjust your prices competitively. The magic happens in a multi-step pipeline: Generate Clean Search Queries: Uses a learned skill to convert messy product names (like "Apple iPhone14!<" or "Dyson! V11!!// VacuumCleaner") into clean, Google-like search queries. Browser Data Extraction: Launches asynchronous browser agents (leveraging Playwright) to search for those queries on Amazon, retrieves the relevant data, and scrapes the page text. Parse & Structure Results: Another custom skill parses the browser output to output structured info: product name, price, and a short description. Enrich Your Data: Finally, the tool combines everything to enrich your original data with live market insights! Full code link: Full code File Rundown learn\skill.py Learns how to generate polished search queries from your product names with GPT-4o-mini. It outputs a JSON file: makequery.json. learn\skill\select\best\product.py Trains another skill to parse web-scraped data and select the best matching product details. Outputs select_product.json. make\query.json The skill definition file for generating search queries (produced by learnskill.py). select\product.json The skill definition file for extracting product details from scraped results (produced by learnskillselectbest_product.py). product\price\matching.py The main pipeline script that orchestrates the entire process—from loading product data, running browser agents, to enriching your CSV. Setup & Installation Install Dependencies: pip install python-dotenv openai langchain\_openai flashlearn requests pytest-playwright Install Playwright Browsers: playwright install Configure OpenAI API: Create a .env file in your project directory with:OPENAI\API\KEY="sk-your\api\key\_here" Running the Tool Train the Query Skill: Run learnskill.py to generate makequery.json. Train the Product Extraction Skill: Run learnskillselectbestproduct.py to generate select_product.json. Execute the Pipeline: Kick off the whole process by running productpricematching.py. The script will load your product data (sample data is included for demo, but easy to swap with your CSV), generate search queries, run browser agents asynchronously, scrape and parse the data, then output the enriched product listings. Target Audience I built this project to automate price matching—a huge pain point for anyone running an e-commerce business. The idea was to minimize the manual labor of checking competitor prices while integrating up-to-date market insights. Plus, it was a fun way to combine automation,skill training, and browser automation! Customization Tweak the concurrency in productpricematching.py to manage browser agent load. Replace the sample product list with your own CSV for a real-world scenario. Extend the skills if you need more data points or different parsing logic. Ajudst skill definitions as needed Comparison With existing approaches you need to manually write parsing loginc and data transformation logic - here ai does it for you. If you like the tutorial - leave a star github

How I landed an internship in AI
reddit
LLM Vibe Score0
Human Vibe Score1
Any-Reserve-4403This week

How I landed an internship in AI

For motivational purposes only! I see a lot of posts on here from people without “traditional” machine learning, data science, etc.. backgrounds asking how they can break into the field, so I wanted to share my experience. EDIT Learning Resources and Side Project Ideas * My background: I graduated from a decent undergraduate school with a degree in Political Science several years ago. Following school I worked in both a client services role at a market research company and an account management role at a pretty notable fintech start-up. Both of these roles exposed me to ML, AI and more sophisticated software concepts in general, and I didn’t really care for the sales side of things, so I decided to make an attempt at switching careers into something more technical. While working full time I began taking night classes at a local community college, starting with pre calculus all the way up to Calc 2 and eventually more advanced classes like linear algebra and applied probability. I also took some programming courses including DSA. I took these classes for about two years while working, and on the side had been working through various ML books and videos on YouTube. What worked the best for me was Hands-on Machine Learning with Scikit Learn, Keara’s and Tensorflow. I eventually had enough credits where I was able to begin applying to MS in Data Science programs and was fortunate enough to get accepted into one and also get a position in their Robotics Lab doing Computer Vision work. When it came time to apply for internships, it was a BLOODBATH. I must have applied to over 100 roles with my only responses being video interviews and OA’s. Finally I got an interview for an AI Model Validation internship with a large insurance company and after completing the interviews was told I performed well but they were still interviewing several candidates. I ended up getting the offer and accepting the role where I’ll be working on a Computer Vision model and some LLM related tasks this summer and could not be more fortunate / excited. A couple things stood out to them during the interview process. 1, the fact that I was working and taking night classes with the intent to break into the field. It showed a genuine passion as opposed to someone who watched a YouTube video and claims they are now an expert. 2, side projects. I not only had several projects, but I had some that were relevant to the work I’d be doing this summer from the computer vision standpoint. 3, business sense. I emphasized during my interviews how working in a business role prior to beginning my masters would give me a leg up as intern because I would be able to apply the work of a data scientist to solving actual business challenges. For those of you trying to break into the field, keep pushing, keep building, and focus on what makes you unique and able to help a company! Please feel free to contact me if you would like any tips I can share, examples of projects, or anything that would be helpful to your journey.

Browser Agents Real Example
reddit
LLM Vibe Score0
Human Vibe Score1
No_Information6299This week

Browser Agents Real Example

I made a Browser Price Matching Tool that uses browser automation and some clever skills to adjust your product prices based on real-time web searches data. If you're into scraping, automation, or just love playing with the latest in ML-powered tools like OpenAI's GPT-4, this one's for you. What My Project Does The tool takes your current product prices (think CSV) and finds similar products online (targeting Amazon for demo purposes). It then compares prices, allowing you to adjust your prices competitively. The magic happens in a multi-step pipeline: Generate Clean Search Queries: Uses a learned skill to convert messy product names (like "Apple iPhone14!<" or "Dyson! V11!!// VacuumCleaner") into clean, Google-like search queries. Browser Data Extraction: Launches asynchronous browser agents (leveraging Playwright) to search for those queries on Amazon, retrieves the relevant data, and scrapes the page text. Parse & Structure Results: Another custom skill parses the browser output to output structured info: product name, price, and a short description. Enrich Your Data: Finally, the tool combines everything to enrich your original data with live market insights! Full code link: Full code File Rundown learn\skill.py Learns how to generate polished search queries from your product names with GPT-4o-mini. It outputs a JSON file: makequery.json. learn\skill\select\best\product.py Trains another skill to parse web-scraped data and select the best matching product details. Outputs select_product.json. make\query.json The skill definition file for generating search queries (produced by learnskill.py). select\product.json The skill definition file for extracting product details from scraped results (produced by learnskillselectbest_product.py). product\price\matching.py The main pipeline script that orchestrates the entire process—from loading product data, running browser agents, to enriching your CSV. Setup & Installation Install Dependencies: pip install python-dotenv openai langchain\_openai flashlearn requests pytest-playwright Install Playwright Browsers: playwright install Configure OpenAI API: Create a .env file in your project directory with:OPENAI\API\KEY="sk-your\api\key\_here" Running the Tool Train the Query Skill: Run learnskill.py to generate makequery.json. Train the Product Extraction Skill: Run learnskillselectbestproduct.py to generate select_product.json. Execute the Pipeline: Kick off the whole process by running productpricematching.py. The script will load your product data (sample data is included for demo, but easy to swap with your CSV), generate search queries, run browser agents asynchronously, scrape and parse the data, then output the enriched product listings. Target Audience I built this project to automate price matching—a huge pain point for anyone running an e-commerce business. The idea was to minimize the manual labor of checking competitor prices while integrating up-to-date market insights. Plus, it was a fun way to combine automation,skill training, and browser automation! Customization Tweak the concurrency in productpricematching.py to manage browser agent load. Replace the sample product list with your own CSV for a real-world scenario. Extend the skills if you need more data points or different parsing logic. Ajudst skill definitions as needed Comparison With existing approaches you need to manually write parsing loginc and data transformation logic - here ai does it for you. If you like the tutorial - leave a star github

What AI tools sounds best for you?
reddit
LLM Vibe Score0
Human Vibe Score1
gigicr1This week

What AI tools sounds best for you?

Hey, I'm a developer who's been lurking here for a while and I want to build something actually useful or at least fun(or both) that is AI-related. Here are 4 ideas (but I'm open to completely different ones): AGI Timeline Prediction Market (🎯 no real money, just bragging rights) Finally settle those "AGI by 2030?" debates with some skin in the game Watch your prediction accuracy score climb (or hilariously tank) Monthly milestone tracking to see who really knows their stuff Like fantasy football, but for the robot apocalypse AI Model Release Calendar Never miss another GPT launch again Compare models without diving into 50 different Discord servers Clear "what can it actually do?" benchmarks Get pinged when something wild drops Research Paper Difficulty Rater Browser extension that saves you from opening papers way above your pay grade Community ratings from "ELI5" to "PhD Required" Shows what you need to know before diving in "Time to comprehend" estimates (coffee breaks vs weekend projects) AI Progress Newsletter + Extension Track what you've actually read vs. saved for "later" (we all know how that goes) Weekly TL;DR of the important stuff Focus on real breakthroughs, not just PR Impact ratings from "neat trick" to "call Elon" Before I dive in and build one of these - has anyone seen something similar already? What would make these actually useful vs just another tool that collects dust? P.S. Open to wildly different ideas or improvements too. Maybe we need something completely different to track our march towards AGI?

Built a multi-agent AI mental health assistant (7 agents, backend automated, no-code stack)
reddit
LLM Vibe Score0
Human Vibe Score1
CapitalCategory4044This week

Built a multi-agent AI mental health assistant (7 agents, backend automated, no-code stack)

Been working on this little side project and finally got it to a working version. It’s an AI-powered mental health assistant — not just a chatbot, but a system that can retrieve user history, analyze input, access data in real-time, and suggest personalized treatment plans. UI Chat Tech stack: Loveable + Momen How it’s structured: It uses 7 specialized AI agents, each responsible for a niche task — chat, generate professional responses, summarize user info, classify intent, etc. Agent Team The main agent (the chat one) will call other agents in the backend via automated workflows. It keeps track of user data (symptoms, conversations, medical history) and updates it in real time — all triggered automatically. Everything runs in the backend to reduce manual steps and minimize errors. How it’s built: Started by drafting the UI with Loveable AI — it auto-generated a 7-page interface from a product brief, which saved me time. (Didn’t use it for the live app though — good for prototyping, but I wanted more control for complex backend workflows.) Rebuilt the UI and database in Momen, since I needed deeper control over data flow and backend logic. The entire AI agent system and backend workflows were built in Momen as well. So I can make the agents collaborate with each other. The main chat agent invokes backend workflows to call other agents when needed. Entire flow looks like this: the user sends a message, the system: → pulls in the latest user data→ triggers the right agent(s) based on the input→ responds in real-time→ quietly summarizes and updates everything in the background. FlowChart It’s still an MVP, but the multi-agent setup + automated backend feels pretty scalable.This was a super fun build and I learned a lot about orchestrating AI workflows. Would love any feedback or thoughts on how to improve this.

How I got 1000 users on day one.
reddit
LLM Vibe Score0
Human Vibe Score1
Human-Grape-8319This week

How I got 1000 users on day one.

This might sound like a small number, depending on who you ask, but you know it’s a start. I’ll just share my learnings so far. Introduction: The product is simple: you type what you want to build, like, let's say, a SaaS idea, and it generates the code using a framework of your choice (like NextJS). Currently, it only generates front-end code. The marketing strategy was mainly focused on social media. My social media stats are as follows: I have a whopping 14 followers on Twitter, and 10 of them are bot accounts, and on LinkedIn, it’s about 400 or so. Launching on LinkedIn: LinkedIn is unique in two different ways: The algorithm is friendly to the little guy. Your network (the people) aren’t always friendly to the little guy. Let me elaborate. This is something I learned today, actually. When I posted for the first time and asked about three of my friends to repost it, within the first hour there were about 200 views, and the click-through rate was around 40%. This was really good, given that it was in the morning. I don’t know the exact factors, but I did have a video in my post, and those three reposts probably amplified it. However, people don’t seem to like or comment on it as much as you would think. Most of my connections are CS students because I am a recent grad, so it seems like most people can relate to this product, but none of them would even put a comment or a like. At the same time, I see people liking posts from big brands like OpenAI, Microsoft, etc. I am really confused, to be honest. However, throughout the day, the view count was going up, and people were coming. Launching on Twitter: Twitter didn’t really work for me at all. I think you need a decent audience. But there are tweets like “What startup are you working on?” type questions, and from that, I find you get a couple of views on your profile. Even though Twitter didn’t really help with the views, one guy tweeted, “Keep posting on Twitter and one day this might become something like Notion.” That really made my day, to be honest. Launching on Discord: This worked really well, to be honest, especially given that I was in a lot of Discord servers where there are software devs. If you use the right language that resonates with them, it’s a home run. Not much to say, but don’t use marketing lingo; people don’t like it there. Instagram and TikTok didn’t really work. Mainly, I think my video didn’t really resonate much. Finally, Facebook Launch: The Facebook reels didn’t really do the trick. Then I posted in a bunch of groups, and still, it didn’t really do anything. But then I sent cold DMs on Facebook, and that had a pretty high open rate because I sent them to people who I saw commented on posts related to what my product was solving. Obviously, after a while, Facebook blocks the ability to send DMs. That’s all for now. Thanks I’ll post my promo video in the comment section just so that you know the video and why it might have resonated with some platforms. Also this is the first time I made a video and I’m actually proud of making that more than the product itself. To summarize, for this idea LinkedIn worked really well, because of the algorithm not the ppl commenting and liking which is what I thought should be the way. Followed by Discord groups and Facebook DMs. The video I made seemed to resonate really well with the LinkedIn audience (the engagement was around 60%) despite falling in TikTok and other video sharing platforms.

I retired at 32 from my side project. Here's the path I took.
reddit
LLM Vibe Score0
Human Vibe Score1
inputoriginThis week

I retired at 32 from my side project. Here's the path I took.

EDIT 2: Thanks for the award kind stranger! I've stopped responding to reddit comments for this post. I'm adding an FAQ to the original post based on the most common high quality questions. If you have a question that you're dying to know the answer to and that only I can help you with (vs. Google, ChatGPT, etc.), DM me. EDIT: I love how controversial this post has become (50% upvote rate), and only in this subreddit (vs. other subreddits that I posted the same content in). I trust that the open-minded half of you will find something useful in this post and my other posts and comments. I retired at 32 years old, in large part thanks to a B2C SaaS app that I developed on my own. Now, I don't have to work in order to cover my living expenses, and wouldn't have to work for quite a while. In other words, I can finally sip mai tais at the beach. I've condensed how I got there into this post. First, a super simplified timeline of events, followed by some critical details. Timeline 2013 Graduated college in the US 2013 Started first corporate job 2013 Started side project (B2C app) that would eventually lead to my retirement 2020 Started charging for use of my B2C app (was free, became freemium) 2021 Quit my last corporate job 2022 Retired: time freedom attained Details First, some summary statistics of my path to retirement: 9 years: time between graduating college and my retirement. 8 years: total length of my career where I worked at some corporate day job. 7 years: time it took my B2C app to make its first revenue dollar 2 years: time between my first dollar of SaaS revenue and my retirement. "Something something overnight success a decade in the making". I got extremely lucky on my path to retirement, both in terms of the business environment I was in and who I am as a person. I'd also like to think that some of the conscious decisions I made along the way contributed to my early retirement. Lucky Breaks Was born in the US middle class. Had a natural affinity for computer programming and entrepreneurial mindset (initiative, resourcefulness, pragmatism, courage, growth mindset). Had opportunities to develop these mindsets throughout life. Got into a good college which gave me the credentials to get high paying corporate jobs. Was early to a platform that saw large adoption (see "barnacle on whale" strategy). Business niche is shareworthy: my SaaS received free media. Business niche is relatively stable, and small enough to not be competitive. "Skillful" Decisions I decided to spend the nights and weekends of my early career working on side projects in the hopes that one would hit. I also worked a day job to support myself and build my savings. My launch funnel over roughly 7 years of working on side projects: Countless side projects prototyped. 5 side projects publically launched. 2 side projects made > $0. 1 side project ended up becoming the SaaS that would help me retire. At my corporate day jobs, I optimized for learning and work-life balance. My learning usually stalled after a year or two at one company, so I’d quit and find another job. I invested (and continute to do so) in physical and mental wellbeing via regular workouts, meditation, journaling, traveling, and good food. My fulfilling non-work-life re-energized me for my work-life, and my work-life supported my non-work-life: a virtuous cycle. I automated the most time-consuming aspects of my business (outside of product development). Nowadays, I take long vacations and work at most 20 hours a week / a three-day work week . I decided to keep my business entirely owned and operated by me. It's the best fit for my work-style (high autonomy, deep focus, fast decision-making) and need to have full creative freedom and control. I dated and married a very supportive and inspiring partner. I try not to succumb to outrageous lifestyle creep, which keeps my living expenses low and drastically extends my burn-rate. Prescription To share some aphorisms I’ve leaned with the wantrepreneurs or those who want to follow a similar path: Maximize your at bats, because you only need one hit. Bias towards action. Launch quickly. Get your ideas out into the real world for feedback. Perfect is the enemy of good. If you keep swinging and improving, you'll hit the ball eventually. Keep the big picture in mind. You don't necessarily need a home-run to be happy: a base hit will often do the job. Think about what matters most to you in life: is it a lot of money or status? Or is it something more satisfying, and often just as if not more attainable, like freedom, loving relationships, or fulfillment? Is what you’re doing now a good way to get what you want? Or is there a better way? At more of a micro-level of "keep the big picture in mind", I often see talented wantrepreneurs get stuck in the weeds of lower-level optimizations, usually around technical design choices. They forget (or maybe subconsciously avoid) the higher-level and more important questions of customer development, user experience, and distribution. For example: “Are you solving a real problem?” or “Did you launch an MVP and what did your users think?” Adopt a growth mindset. Believe that you are capable of learning whatever you need to learn in order to do what you want to do. The pain of regret is worse than the pain of failure. I’ve noticed that fear of failure is the greatest thing holding people back from taking action towards their dreams. Unless failure means death in your case, a debilitating fear of failure is a surmountable mental block. You miss 100% of the shots you don't take. When all is said and done, we often regret the things we didn't do in life than the things we did. There’s more to life than just work. Blasphemous (at least among my social circle)! But the reality is that many of the dying regret having worked too much in their lives. As Miss Frizzle from The Magic Schoolbus says: "Take chances, make mistakes, get messy!" Original post

Day 1 of my BIP for my AdonisJS Boilerplate (turbosaas) [Built in public]
reddit
LLM Vibe Score0
Human Vibe Score0.5
Ok_Bread_6005This week

Day 1 of my BIP for my AdonisJS Boilerplate (turbosaas) [Built in public]

Hello everyone, here is day 1 (not really, I started a bit earlier) of my project: A boilerplate using AdonisJS, Inertia What technologies are used/present? AdonisJS Inertia Stripe OpenAI TailwindCSS Vite (React) Why? Firstly, I want to save time when launching my projects, and I think you do too, so I've included as many relevant features as possible. I'm tired of seeing attitudes like 'develop your SaaS in 1 hour and produce terrible code!' The purpose of this codebase is to provide the highest quality code possible and to maintain that standard throughout the development process. You might spend an extra 20 minutes doing things right, but you'll save 2 hours on refactoring. And no, you won't have to pay for updates. (WTF by the way?) Why these technologies? I've seen a lot of NextJS for boilerplates, and I've also used NextJS before, but I quickly abandoned it. It quickly becomes a mess You lose track of what is what, and start doing anything Every update breaks your application Whereas with AdonisJS, life is beautiful. There are plenty of community packages already available, and everything you need is here. What am I offering? Authentication: Social authentication, OTP, Magic Links, and credentials, along with complete account management features like password recovery. Payment & Mailing Integration: Seamless integration from start to finish, with multiple options to choose from. Detailed Documentation: Thorough explanations of every aspect, covering even the smallest, potentially confusing details in the code. Maintainable & Scalable Code: Organized by features, allowing you to easily drag and drop features to extend functionality. Developer Tools: Handy commands for generating new features and automatically adding necessary imports; a complete config to enable/disable a feature in less than 10 seconds... Pre-made Pages: Ready-to-use pages such as an admin dashboard for tasks like automatically updating products on Stripe. Extensive Component Library: A variety of components to streamline development. I've designed this boilerplate to be as developer-friendly and robust as possible, aiming to support maintainability and scalability from the get-go. Summary of today and previous days Day 2 Stripe is a nightmare to set up if you've never done it before, it quickly becomes tedious. But I've finally finished setting everything up: one-time payments, subscriptions, and subscription updates. It was complicated. Today I finally implemented the 'forgot password' option, and I've completed all the authentication by adding magic links (working with OTP). I also set up automatic deployment with GitHub Actions, and everything works well. The build runs with the action to ensure everything goes smoothly, then using SSH, I pull the project, build it, and launch it. Tomorrow: What I want to do tomorrow Tomorrow, I want to create the blog, because yes, I want to include a blog as well, and especially complete it as soon as possible so it can be available on turbosaas(dot)dev, and write my build in public. It will probably use markdown. Thank you for reading this short build in public, you can also check out how it's going on turbosaas(dot)dev.

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

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

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

Looking for a technical co-founder to build LinkedIn’s rival
reddit
LLM Vibe Score0
Human Vibe Score1
ItzdreeThis week

Looking for a technical co-founder to build LinkedIn’s rival

How do you connect with likeminded people? You see the polished wins everywhere, but what about the messy drafts , the awkward pitches and the moments you’re not sure you’ve got it right? Problem: The whole idea of founding and starting a business can be super intimidating for some people, specially those who don’t know any founders personally, those who don’t have a large network, those who don’t have rich parents with large networks, those not inserted in an entrepreneurial culture like in the US for example (which is my case). Sometimes all you need is the right support network, and too see others do what you want, to know that it’s possible! Everyone has an “ultimate guide” to make 7 figures or build a business on YouTube but NO ONE shoes you the HOW, just the results… I’ve tried joining founder communities, LinkedIn ,Reddit … you name it. Most of these founder communities are inaccessible for regular people and often ask for you to have an already existing business with a min ARR… or their simply geography based and if you’re not in a certain area you can’t really participate… As of LinkedIn… full of empty AI generated posts about how some random dude raised $10m in 7 days. Okay Jonathan, but what about the HOW?? How did you write your first pitch? How many rejection calls did you get? What is an MVP? There simply isn’t a platform out there to document your founding journey and find inspiration within a community of people who are doing the same as you. What better way to feel motivated then to see someone actually document their process? Solution: I’m working on building a social media platform for aspiring/founders to connect through the RAW, UNFILTERED process of turning ideas into reality in REAL time. It’s all gonna be around the “building in public “ concept and content creation. Picture an instagram/tiktok profile where instead of seeing someone’s dog you see them documenting their founding process—from the moment they had the idea, to the moment they launched, you’re going to see the successes, the fails, the rejected calls, all documented through actual content and not some AI generated LinkedIn post. Imagine if you wanted to learn about how Steve Jobs started Apple , you could simply go through his profile on this app—exactly. To make sure all interactions are meaningful people would have to apply. It’s a truly curated community, with REAL people, building REAL things in REAL time, and not just tell us the story of how they did it… Audience: I’m targeting people who have a burning desire of building a business and early stage founders starting their founder journeys, that don’t have a support network and simply don’t know where to start. People who are tired of watching 30 min “ultimate guides “ on how to make it on YouTube from “business gurus” selling courses. People who haven’t reached the min ARR required to join an “exclusive “ founder a community. People who can’t simply just move to the US to get into the “exclusive” YC combinator. People who want to connect with real people building real things and not anonymous people on Reddit, or LinkedIn influencers again trying to promote their services. I believe in the idea because I’m also part of my audience. Have always wanted to start my own thing just never knew how to and where to find a community of likeminded people . I don’t know any founders myself, I come from a non-entrepreneurial society and I’d pay good money to access a community of REAL passionate founders building REAL things, in REAL time. This would be my first ever business, and I want to share my journey building it and hopefully inspire others to just start so I’ve created a mailing list to keep anyone interested in the project updated on my fails , learnings and successes. I’m not worried about “making it” but just “starting” and hopefully reach the right audience and inspire anyone to start whatever they have marinating in their thoughts. If you’re a founder struggling with staying consistent or an aspiring founder with an insane desire of starting and don’t know how to start, I’d love to get your feedback on what’s stopping you, your challenges starting out and what you’d find useful in such platform. And finally would this be something that interests you?? Feel free to subscribe to get new updates 🫶🏼 : https://mailchi.mp/037c56b89994/d-founder PS: casually looking for a technical co-founder

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

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

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

How I Automated Amazon Affiliate Marketing: A Developer's Journey
reddit
LLM Vibe Score0
Human Vibe Score1
siom_cThis week

How I Automated Amazon Affiliate Marketing: A Developer's Journey

From Manual Labor to 1000x Efficiency As a developer who ventured into affiliate marketing, I discovered a significant gap between technical possibilities and current practices. This revelation led me to create AutoPin, a tool that's now helping hundreds of affiliate marketers reclaim their time. The Problem: A Time-Consuming Reality Every affiliate marketer knows this scenario: you spend hours copying and pasting links, checking prices, and updating product information. I found myself dedicating 4-6 hours daily to these repetitive tasks. As a programmer, this felt fundamentally wrong. The typical affiliate marketing workflow looked like this: Find promising products Generate affiliate links one by one Monitor price changes manually Check product availability regularly Update content when things change Repeat this process daily This manual process had several critical issues: Time Waste: 20-30 hours weekly on repetitive tasks Missed Opportunities: Unable to scale beyond 100 products Human Error: Inevitable mistakes in manual updates Delayed Updates: Lost commissions due to outdated information The Solution: Building AutoPin After three months of development and six months of testing, I created a system that could: Generate hundreds of affiliate links in minutes Monitor price changes automatically Update product availability in real-time Export data in multiple formats Scale infinitely without additional effort Real Results, Real Impact The impact was immediate and significant: 📊 Efficiency Metrics: Link generation: From 2 minutes per link to 0.1 seconds Monitoring capacity: From 50 to 5000+ products Update frequency: From daily to real-time Error rate: Reduced by 99.9% 💡 User Success Stories: "Increased my product portfolio by 10x without adding work hours" "Revenue grew 300% in the first month" "Finally able to focus on content creation instead of link management" Technical Insights The system architecture focuses on three core components: Data Extraction Engine Efficient web scraping Rate limiting and proxy management Data validation and cleaning Real-time Monitoring System Websocket connections for instant updates Queue management for large-scale monitoring Smart scheduling based on price volatility Export Framework Multiple format support (CSV, HTML, Markdown) Custom templating engine Batch processing capabilities The Future of Affiliate Marketing Automation We're currently developing AI capabilities to: Generate product descriptions automatically Optimize link placement for conversion Predict price trends and best promotion times Create content variations for different platforms Key Learnings Automation is Essential The future of affiliate marketing lies in automation. Manual processes simply can't compete with automated systems in terms of efficiency and accuracy. Focus on Value Creation When marketers spend less time on repetitive tasks, they can focus on strategy and content quality. Scale Matters With automation, the difference between managing 10 products and 1000 products becomes minimal. Getting Started If you're an affiliate marketer spending hours on manual tasks, it's time to automate. Here's what you can do: Analyze your current workflow Identify repetitive tasks Start with basic automation Scale gradually Monitor and optimize Conclusion The transformation from manual to automated affiliate marketing isn't just about saving time—it's about unlocking potential. When you remove the tedious aspects of affiliate marketing, you create space for creativity, strategy, and growth. Want to experience the difference? Visit AutoPin at autopin.pro and join the automation revolution. Remember: The best time to automate was yesterday. The second best time is now. About the Author: A developer turned affiliate marketer who believes in the power of automation to transform digital marketing. #AffiliateMarketing #Automation #Programming #DigitalMarketing #SaaS #ProductivityTools

I retired at 32 from my side project. Here's the path I took.
reddit
LLM Vibe Score0
Human Vibe Score1
inputoriginThis week

I retired at 32 from my side project. Here's the path I took.

EDIT 2: Thanks for the award kind stranger! I've stopped responding to reddit comments for this post. I'm adding an FAQ to the original post based on the most common high quality questions. If you have a question that you're dying to know the answer to and that only I can help you with (vs. Google, ChatGPT, etc.), DM me. EDIT: I love how controversial this post has become (50% upvote rate), and only in this subreddit (vs. other subreddits that I posted the same content in). I trust that the open-minded half of you will find something useful in this post and my other posts and comments. I retired at 32 years old, in large part thanks to a B2C SaaS app that I developed on my own. Now, I don't have to work in order to cover my living expenses, and wouldn't have to work for quite a while. In other words, I can finally sip mai tais at the beach. I've condensed how I got there into this post. First, a super simplified timeline of events, followed by some critical details. Timeline 2013 Graduated college in the US 2013 Started first corporate job 2013 Started side project (B2C app) that would eventually lead to my retirement 2020 Started charging for use of my B2C app (was free, became freemium) 2021 Quit my last corporate job 2022 Retired: time freedom attained Details First, some summary statistics of my path to retirement: 9 years: time between graduating college and my retirement. 8 years: total length of my career where I worked at some corporate day job. 7 years: time it took my B2C app to make its first revenue dollar 2 years: time between my first dollar of SaaS revenue and my retirement. "Something something overnight success a decade in the making". I got extremely lucky on my path to retirement, both in terms of the business environment I was in and who I am as a person. I'd also like to think that some of the conscious decisions I made along the way contributed to my early retirement. Lucky Breaks Was born in the US middle class. Had a natural affinity for computer programming and entrepreneurial mindset (initiative, resourcefulness, pragmatism, courage, growth mindset). Had opportunities to develop these mindsets throughout life. Got into a good college which gave me the credentials to get high paying corporate jobs. Was early to a platform that saw large adoption (see "barnacle on whale" strategy). Business niche is shareworthy: my SaaS received free media. Business niche is relatively stable, and small enough to not be competitive. "Skillful" Decisions I decided to spend the nights and weekends of my early career working on side projects in the hopes that one would hit. I also worked a day job to support myself and build my savings. My launch funnel over roughly 7 years of working on side projects: Countless side projects prototyped. 5 side projects publically launched. 2 side projects made > $0. 1 side project ended up becoming the SaaS that would help me retire. At my corporate day jobs, I optimized for learning and work-life balance. My learning usually stalled after a year or two at one company, so I’d quit and find another job. I invested (and continute to do so) in physical and mental wellbeing via regular workouts, meditation, journaling, traveling, and good food. My fulfilling non-work-life re-energized me for my work-life, and my work-life supported my non-work-life: a virtuous cycle. I automated the most time-consuming aspects of my business (outside of product development). Nowadays, I take long vacations and work at most 20 hours a week / a three-day work week . I decided to keep my business entirely owned and operated by me. It's the best fit for my work-style (high autonomy, deep focus, fast decision-making) and need to have full creative freedom and control. I dated and married a very supportive and inspiring partner. I try not to succumb to outrageous lifestyle creep, which keeps my living expenses low and drastically extends my burn-rate. Prescription To share some aphorisms I’ve leaned with the wantrepreneurs or those who want to follow a similar path: Maximize your at bats, because you only need one hit. Bias towards action. Launch quickly. Get your ideas out into the real world for feedback. Perfect is the enemy of good. If you keep swinging and improving, you'll hit the ball eventually. Keep the big picture in mind. You don't necessarily need a home-run to be happy: a base hit will often do the job. Think about what matters most to you in life: is it a lot of money or status? Or is it something more satisfying, and often just as if not more attainable, like freedom, loving relationships, or fulfillment? Is what you’re doing now a good way to get what you want? Or is there a better way? At more of a micro-level of "keep the big picture in mind", I often see talented wantrepreneurs get stuck in the weeds of lower-level optimizations, usually around technical design choices. They forget (or maybe subconsciously avoid) the higher-level and more important questions of customer development, user experience, and distribution. For example: “Are you solving a real problem?” or “Did you launch an MVP and what did your users think?” Adopt a growth mindset. Believe that you are capable of learning whatever you need to learn in order to do what you want to do. The pain of regret is worse than the pain of failure. I’ve noticed that fear of failure is the greatest thing holding people back from taking action towards their dreams. Unless failure means death in your case, a debilitating fear of failure is a surmountable mental block. You miss 100% of the shots you don't take. When all is said and done, we often regret the things we didn't do in life than the things we did. There’s more to life than just work. Blasphemous (at least among my social circle)! But the reality is that many of the dying regret having worked too much in their lives. As Miss Frizzle from The Magic Schoolbus says: "Take chances, make mistakes, get messy!" Original post

What I learn from my $200 MRR App I built 4 months ago
reddit
LLM Vibe Score0
Human Vibe Score0.857
ricky0603This week

What I learn from my $200 MRR App I built 4 months ago

4 month ago, I am just a 10-years experienced product manager without any software development experience. I have an $3K/month job, but I am so tired, I don’t like my life, don’t like my boss, don’t like my daily work, that make me feeling I already died however I am still living. I yearn for freedom and want to live each day the way I want to. So I quit my job, and become a Indie developer to build my own business, my own app, even my own life. I am so grateful for this time and experience, now my app reach $200 MRR, still very little compared to my previous salary, but I never regret. I have learned lots of things from this time and experience, more than I had in last 10 years. Here is the time-line of my App: &#x200B; Sep 2023: Launch first version to iOS App store Oct 2023: Release in-app-purchase features and have first subscriber, the revenue in October is $154 Nov 2023: Change from subscription to pay per use, and I did lots of marketing jobs in November, however, the revenue reduced to only $40. Dec 2023: Change back to subscription, and stop some invalid marketing jobs, only keep the ones that actually work. I almost did nothing in December, and the revenue come to $243. During this process, I have learned lots of things, there are some of them that I think could help you as well. Web or App My App is an iOS app that only can running on Apple’s device such like iPhone/iPad or Mac with Apple silicon. Many people ask me why my product is an iOS app not a website, because they don’t have any Apple device. It's true that promoting an app is much harder than promoting a website. However I am now very glad I made an App and not a website! If I make a website, I don't think it's possible to make $100 in the first month. My App is about keyword research, to help people find some ideas from search keyword, because every keyword people searched in Google are representing a real need of them, also can be used in SEO field. However there are a lot of website tools about keyword research, some of them are famous like Ahrefs, SEMrush… I have no intention of competing with them. Actually I don’t have any chance. While in app store, there are little apps about keyword research, each of them have terrible data and user experience, that means if my app has better data and experience that could be my chance. In fact, the App store brings me 20 organic installs a day that Google would never have been able to bring me if I had a website, at least for the first few months. Furthermore, Apple nearly did everything for developer, I don’t need to care about user login, payment and so on, Apple did everything, I just need to call their API, that save lots of time, if I build a website, I need to implement login and payment by myself, that would add some extra work. Not to mention I'd need to buy servers and domains, that would cost me a lot of money. Although Apple will take 30% of the revenue, I can live with that in the early stages because the most important thing for me is to get the product to market as soon as possible. Actually thought Apple’s SMB program, the take rate is 15% now. So Web or App is not important in the early stage, time is important, if people need my product, it's easy to make a website one. More Users or More Valuable Users In November, I notice some users would like use my app, and they were meet paywall, but they never subscribe. I provided 7 day free trail, but it seem that they don’t like it. So I decide to change subscription to pay per use. Because as a user, I don’t like subscription as well, pay per use seem like more friendly. So I change from subscription to pay per use. People can afford $9.99 to subscribe monthly for unlimited use or pay $1.99 for each data they want(First purchase is $0.99 then $1.99). I was expecting more user to pay, but it was the complete opposite! Some users who would have paid a higher subscription fee are switching to a lower priced single payment. Users are encountering paywalls more often, and each time they need to make a decision about whether or not to pay, which increases the probability that they will abandon payment. This resulted in a 75% decrease in revenue in November. In fact, the mostly of my revenue comes from a handful of long-cycle subscribers, such as annual subscription. Few bring in most of the revenue, that is the most important thing I learned. You don't need a lot of customers, you just need more valuable ones. That's why it's only right to design a mechanism to filter out high-value customers and focus on them, all the things you want do is just let more people into the filter, and from that point of view, subscription with free trial period is the best way, even if most people don't like it. The rule of 20/80 will always be there. The most important thing is always focus on the 20 percent things and people. Effort does not always guarantee rewards. Unless one engages in deep thinking, or most efforts are invalid. I have been working very hard to promote my product for a period of time. It’s about in November. I did a lot of job, such as write script to send message to my potential clients on Fiverr, post and write comments on others post on Reddit, find related questions and answer them on Quora, post and comments on Twitte, etc. During that period, I was exhausted every day, but the outcome did not meet my expectations. There is only little growth on App installation, even less revenue than before. That make me frustrated. I finally realized that If I need to put in a tremendous amount of effort just to make a little progress, there is must something wrong. So I stop 80% of promote work I have ever did, only keep app store search ad, which will bring a installation with less than $0.5 cost. Then I dive into long time and deeply thinking, I spent more time on reading books, investigate other product with great MRR, watch interviews with people who are already living the kind of life I aspire to live, for example, u/levelsio. These things have given me great inspiration, and my life has become easier. It seems that the life I anticipated when I resigned is getting closer. I also have a clearer understanding of my app. Meanwhile, MRR has been growing. This experience let me learn that effort does not always guarantee results. Many times, our efforts are just wishful thinking, they are invalid, do the right thing after deeply thinking is more important. What Next? My goal is reach $3K MRR, as same as my job payment, I will never stop to building things, and I will keep my currently lifestyle. I still don't know how to get more people to use my app, but levelsio's interviews give me some inspiration that I can verified something by manually instead of build a software. I plan to launch a trend analysis product based on the keyword data provided by my current app. I have always wanted to combine AI to build such a product, but I didn't know how to do it. Now I intend to manually complete it first and start software development once there are paying users. If you are interested to my App, you could try it. Gotrends

How I'm automating all my SEO research & writing with AI by building an open source software
reddit
LLM Vibe Score0
Human Vibe Score1
frazrasThis week

How I'm automating all my SEO research & writing with AI by building an open source software

I make most of my current recurring income from writing articles for a few blogs. Over the years I have developed strategies and writing techniques that increase my chances of landing at the top of Google search results. I’m a writer, but I also write code. With the advent of AI I have been itching to codify many of my previous activities. I tried writing content with the general LLMs like ChatGPT and Claude but the results were terrible, especially for niches with technical information. I didn’t want to lose hope in AI because I realised with A LOT of hand-holding, it got better results. THEN IT HIT ME!  What if I could create a Human-Guided AI for Better AI-Written Articles: enter Building ContentScribe After months of coding with AI tools and trying different approaches, I’m excited to share that ContentScribe is finally taking shape. The journey to this point has been challenging but incredibly rewarding. Over the past six months, we’ve been using ContentScribe ourselves to automate blog content creation. We found other tools in the AI article generation space such as Koala AI and Cuppa that left us wanting more. They basically took a topic from you and let the AI loose. We consider this to be a better Koala AI and Cuppa alternative. I wanted to have more control and freedom from the expense of the credit system most of them use. Even after generation, every article required significant human input to make it truly SEO-friendly, and existing tools couldn’t handle the specific strategies we needed for our niche. So, we decided to build something new: an AI-powered, open-source tool that doesn’t just spit out generic articles, but actually allows users to shape how the content is written. ContentScribe is designed to integrate the SEO techniques that we’ve developed over years of building profitable blogs. It codifies our best practices and turns them into a process that anyone can use to create researched, optimized content, every time. The product works, and it’s live! We’ve been populating our latest blog with human-guided AI-written articles, and the results are already impressive. The coolest part? This project scratches our own itch and addresses the pain points we faced when using other tools. Plus there is nothing to lose because it’s free and open source, you can run it locally or in the cloud. It’s still early days, but I’m excited to share more as we keep building in public. We’re working on tutorials, and adding more features. The feedback we’ve gotten so far from our in-house team has been invaluable, and I’m looking forward to sharing this with more content creators out there. For anyone struggling to get their ideas off the ground: keep experimenting, keep building. ContentScribe is proof that when you combine persistence with innovation, the results can be something you’re genuinely proud of. This is just the beginning!

[P] How I found & fixed 4 bugs in Microsoft's Phi-4 model
reddit
LLM Vibe Score0
Human Vibe Score1
danielhanchenThis week

[P] How I found & fixed 4 bugs in Microsoft's Phi-4 model

Hey r/MachineLearning! Last week, Microsoft released Phi-4, a 14B open-source model that rivals OpenAI's GPT-4-o-mini. I managed to find & fix 4 bugs impacting its output quality. You might remember me previously from fixing 8 bugs in Google's Gemma model! :) I'm going to walk you through how I found & fixed the bugs. Phi-4's benchmarks were amazing, however many users reported weird or just wrong outputs. Since I maintain the open-source project called 'Unsloth' (fine-tuning LLMs 2x faster with 70% less VRAM) with my brother, I firstly tested Phi-4 for inference and found many errors. Our GitHub repo: https://github.com/unslothai/unsloth This time, the model had no implementation issues (unlike Gemma 2) but did have problems in the model card. For my first inference run, I randomly found an extra token which is obviously incorrect (2 eos tokens is never a good idea). Also during more runs, I found there was an extra assistant prompt which is once again incorrect. And, lastly, from past experience with Unsloth's bug fixes, I already knew fine-tuning was wrong when I read the code. These bugs caused Phi-4 to have some drop in accuracy and also broke fine-tuning runs. Our fixes are now under review by Microsoft to be officially added to Hugging Face. We uploaded the fixed versions to https://huggingface.co/unsloth/phi-4-GGUF Here’s a breakdown of the bugs and their fixes: Tokenizer bug fixes The Phi-4 tokenizer interestingly uses as the BOS (beginning of sentence), EOS (end of sentence) and PAD (padding) tokens. The main issue is the EOS token is wrong - it should be . Otherwise, you will get in generations. Fine-tuning bug fixes The padding token should be a designated pad token like in Llama () or we can use an untrained token - for example we use , fixing infinite generations and outputs. Chat template issues The Phi-4 tokenizer always adds an assistant prompt - it should only do this if prompted by add\generation\prompt. Most LLM serving libraries expect non auto assistant additions, and this might cause issues during serving. We dive deeper into the bugs in our blog: https://unsloth.ai/blog/phi4 Do our Fixes Work? Yes! Our fixed Phi-4 uploads show clear performance gains, with even better scores than Microsoft's original uploads on the Open LLM Leaderboard. https://preview.redd.it/d8hew26e06ce1.png?width=2366&format=png&auto=webp&s=173c23feacc625566271470839fe7a5e25eb860e Some redditors even tested our fixes to show greatly improved results in: Example 1: Multiple-choice tasks https://preview.redd.it/qx50pkq706ce1.png?width=1579&format=png&auto=webp&s=437da2cabdbf98ef5a8b8cbdc5592907a20e2316 Example 2: ASCII art generation https://preview.redd.it/sw1o3a3yt4de1.png?width=2326&format=png&auto=webp&s=fc6bfc45d14134d45f332ba58bbd1de049f5776b We also made a Colab notebook fine-tune Phi-4 completely for free using Google's free Tesla T4 (16GB) GPUs: https://colab.research.google.com/github/unslothai/notebooks/blob/main/nb/Phi\4-Conversational.ipynb Thank you for reading this long post and hope you all found this insightful! If you have any questions, please feel free to ask! :) How I found the bugs: I first downloaded the original Phi-4 from https://huggingface.co/microsoft/phi-4, and tested inference out. Weirdly I found assistant to be appended at the even with addgenerationprompt = False in Hugging Face, so I theorized there was a chat template problem. Adding assistant prompts by default can break serving libraries. And yes, https://huggingface.co/microsoft/phi-4/blob/f957856cd926f9d681b14153374d755dd97e45ed/tokenizer\config.json#L774 had by default added the assistant prompt - I first fixed this! I then found ` to be used for the BOS, EOS and PAD tokens, which is a common issue amongst models - I ignored the BOS, since Phi-4 did not have one anyways, but changed the PAD token to `. You can select any of the tokens since they're empty and not trained. This counteracts issues of infinite generations during finetuning. For Llama-fication, I used torch.allclose to confirm all tensors are in fact equivalent. I also used some fake random data to check all activations are also mostly similar bitwise. I also uploaded the model to the HF Open LLM Leaderboard to confirm if the original Phi-4 arch and the new Llama-fied models are equivalent. Finally I verified all finetuning runs with Unsloth in a Colab Notebook to confirm all runs were correct.

[D] The machine learning community has a toxicity problem
reddit
LLM Vibe Score0
Human Vibe Score1
yusuf-bengioThis week

[D] The machine learning community has a toxicity problem

It is omnipresent! First of all, the peer-review process is broken. Every fourth NeurIPS submission is put on arXiv. There are DeepMind researchers publicly going after reviewers who are criticizing their ICLR submission. On top of that, papers by well-known institutes that were put on arXiv are accepted at top conferences, despite the reviewers agreeing on rejection. In contrast, vice versa, some papers with a majority of accepts are overruled by the AC. (I don't want to call any names, just have a look the openreview page of this year's ICRL). Secondly, there is a reproducibility crisis. Tuning hyperparameters on the test set seem to be the standard practice nowadays. Papers that do not beat the current state-of-the-art method have a zero chance of getting accepted at a good conference. As a result, hyperparameters get tuned and subtle tricks implemented to observe a gain in performance where there isn't any. Thirdly, there is a worshiping problem. Every paper with a Stanford or DeepMind affiliation gets praised like a breakthrough. For instance, BERT has seven times more citations than ULMfit. The Google affiliation gives so much credibility and visibility to a paper. At every ICML conference, there is a crowd of people in front of every DeepMind poster, regardless of the content of the work. The same story happened with the Zoom meetings at the virtual ICLR 2020. Moreover, NeurIPS 2020 had twice as many submissions as ICML, even though both are top-tier ML conferences. Why? Why is the name "neural" praised so much? Next, Bengio, Hinton, and LeCun are truly deep learning pioneers but calling them the "godfathers" of AI is insane. It has reached the level of a cult. Fourthly, the way Yann LeCun talked about biases and fairness topics was insensitive. However, the toxicity and backlash that he received are beyond any reasonable quantity. Getting rid of LeCun and silencing people won't solve any issue. Fifthly, machine learning, and computer science in general, have a huge diversity problem. At our CS faculty, only 30% of undergrads and 15% of the professors are women. Going on parental leave during a PhD or post-doc usually means the end of an academic career. However, this lack of diversity is often abused as an excuse to shield certain people from any form of criticism. Reducing every negative comment in a scientific discussion to race and gender creates a toxic environment. People are becoming afraid to engage in fear of being called a racist or sexist, which in turn reinforces the diversity problem. Sixthly, moral and ethics are set arbitrarily. The U.S. domestic politics dominate every discussion. At this very moment, thousands of Uyghurs are put into concentration camps based on computer vision algorithms invented by this community, and nobody seems even remotely to care. Adding a "broader impact" section at the end of every people will not make this stop. There are huge shitstorms because a researcher wasn't mentioned in an article. Meanwhile, the 1-billion+ people continent of Africa is virtually excluded from any meaningful ML discussion (besides a few Indaba workshops). Seventhly, there is a cut-throat publish-or-perish mentality. If you don't publish 5+ NeurIPS/ICML papers per year, you are a looser. Research groups have become so large that the PI does not even know the name of every PhD student anymore. Certain people submit 50+ papers per year to NeurIPS. The sole purpose of writing a paper has become to having one more NeurIPS paper in your CV. Quality is secondary; passing the peer-preview stage has become the primary objective. Finally, discussions have become disrespectful. Schmidhuber calls Hinton a thief, Gebru calls LeCun a white supremacist, Anandkumar calls Marcus a sexist, everybody is under attack, but nothing is improved. Albert Einstein was opposing the theory of quantum mechanics. Can we please stop demonizing those who do not share our exact views. We are allowed to disagree without going for the jugular. The moment we start silencing people because of their opinion is the moment scientific and societal progress dies. Best intentions, Yusuf

[D]Stuck in AI Hell: What to do in post LLM world
reddit
LLM Vibe Score0
Human Vibe Score1
Educational_News_371This week

[D]Stuck in AI Hell: What to do in post LLM world

Hey Reddit, I’ve been in an AI/ML role for a few years now, and I’m starting to feel disconnected from the work. When I started, deep learning models were getting good, and I quickly fell in love with designing architectures, training models, and fine-tuning them for specific use cases. Seeing a loss curve finally converge, experimenting with layers, and debugging training runs—it all felt like a craft, a blend of science and creativity. I enjoyed implementing research papers to see how things worked under the hood. Backprop, gradients, optimization—it was a mental workout I loved. But these days, it feels like everything has shifted. LLMs dominate the scene, and instead of building and training models, the focus is on using pre-trained APIs, crafting prompt chains, and setting up integrations. Sure, there’s engineering involved, but it feels less like creating and more like assembling. I miss the hands-on nature of experimenting with architectures and solving math-heavy problems. It’s not just the creativity I miss. The economics of this new era also feel strange to me. Back when I started, compute was a luxury. We had limited GPUs, and a lot of the work was about being resourceful—quantizing models, distilling them, removing layers, and squeezing every bit of performance out of constrained setups. Now, it feels like no one cares about cost. We’re paying by tokens. Tokens! Who would’ve thought we’d get to a point where we’re not designing efficient models but feeding pre-trained giants like they’re vending machines? I get it—abstraction has always been part of the field. TensorFlow and PyTorch abstracted tensor operations, Python abstracts C. But deep learning still left room for creation. We weren’t just abstracting away math; we were solving it. We could experiment, fail, and tweak. Working with LLMs doesn’t feel the same. It’s like fitting pieces into a pre-defined puzzle instead of building the puzzle itself. I understand that LLMs are here to stay. They’re incredible tools, and I respect their potential to revolutionize industries. Building real-world products with them is still challenging, requiring a deep understanding of engineering, prompt design, and integrating them effectively into workflows. By no means is it an “easy” task. But the work doesn’t give me the same thrill. It’s not about solving math or optimization problems—it’s about gluing together APIs, tweaking outputs, and wrestling with opaque systems. It’s like we’ve traded craftsmanship for convenience. Which brings me to my questions: Is there still room for those of us who enjoy the deep work of model design and training? Or is this the inevitable evolution of the field, where everything converges on pre-trained systems? What use cases still need traditional ML expertise? Are there industries or problems that will always require specialized models instead of general-purpose LLMs? Am I missing the bigger picture here? LLMs feel like the “kernel” of a new computing paradigm, and we don’t fully understand their second- and third-order effects. Could this shift lead to new, exciting opportunities I’m just not seeing yet? How do you stay inspired when the focus shifts? I still love AI, but I miss the feeling of building something from scratch. Is this just a matter of adapting my mindset, or should I seek out niches where traditional ML still thrives? I’m not asking this to rant (though clearly, I needed to get some of this off my chest). I want to figure out where to go next from here. If you’ve been in AI/ML long enough to see major shifts—like the move from feature engineering to deep learning—how did you navigate them? What advice would you give someone in my position? And yeah, before anyone roasts me for using an LLM to structure this post (guilty!), I just wanted to get my thoughts out in a coherent way. Guess that’s a sign of where we’re headed, huh? Thanks for reading, and I’d love to hear your thoughts! TL;DR: I entered AI during the deep learning boom, fell in love with designing and training models, and thrived on creativity, math, and optimization. Now it feels like the field is all about tweaking prompts and orchestrating APIs for pre-trained LLMs. I miss the thrill of crafting something unique. Is there still room for people who enjoy traditional ML, or is this just the inevitable evolution of the field? How do you stay inspired amidst such shifts? Update: Wow, this blew up. Thanks everyone for your comments and suggestions. I really like some of those. This thing was on my mind for a long time, glad that I put it here. Thanks again!

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

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

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

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

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

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

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

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

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

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

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

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

[P] I built an open SotA image tagging model to do what CLIP won't
reddit
LLM Vibe Score0
Human Vibe Score1
fpgaminerThis week

[P] I built an open SotA image tagging model to do what CLIP won't

I'm a hobbyist ML researcher and finally, after a year of work, built a state of the art machine vision model from scratch. It's ViT-B/16 based, 448x448x3 input, 91M parameters, trained for 660M samples, with multi-label classification as the target task, on over 5000 unique tags. All the big foundation vision models today were trained on heavily filtered datasets, greatly limiting the concepts they can represent, in line with arbitrary sets of rules for what is deemed "wholesome" by leading tech companies. Everything from innocuous to spicy is on the chopping block of those filters. And because CLIP pervades the industry, from StableDiffusion to LLaVA, so does OpenAI's sensibilities. My goal was to build a vision model for tagging images, mainly for labelling images for SD finetunes, but which wasn't as heavily filtered and handicapped as CLIP/BLIP/LLaVA. Something more inclusive, diverse, and sex positive. Starting from the wonderful work of SmilingWolf (https://github.com/SmilingWolf/SW-CV-ModelZoo) and the Danbooru2021 dataset, I iterated for a year on the model, training, and manually labeling a thousand images to help the model generalize beyond the danbooru domain. I'm releasing the first version of this model, dubbed JoyTag, today: https://github.com/fpgaminer/joytag It achieves a mean F1 score of 0.578 across all of its over 5000 tags and across both the anime/manga styled images of the original danbooru dataset, but also photographs and other mediums thanks to the auxiliary training data I provided to it. It was quite the struggle getting to this point, and I probably spent more time and money than any sane person should have. I learned a lot about dealing with datasets as large as danbooru2021, training models at scale, and how to keep yourself awake all night so your 8xA100 rental doesn't crash and blow all your money. In my manual testing outside of even the validation set, the model has generalized well to unseen images, so I'm quite happy with the results thus far. There's plenty more work to do expanding its dataset to improve that F1 score further, and roundout its weak points. With inclusivity and diversity being a major goal of this project, I'm disappointed by some of its remaining limitations (as documented in the GitHub README). But I'm already busy manually tagging more images using my model-augmented workflow. I'm happy to answer questions about the project, the training procedure, anything. All the training parameters are documented on GitHub, but there are so many little details that were hard won over the year. Like that damned loss multiplier. Ugh. Github: https://github.com/fpgaminer/joytag Model download: https://huggingface.co/fancyfeast/joytag/tree/main Demo: https://huggingface.co/spaces/fancyfeast/joytag

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

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

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

I run an AI automation agency (AAA). My honest overview and review of this new business model
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Scout_OfficialThis week

I run an AI automation agency (AAA). My honest overview and review of this new business model

I started an AI tools directory in February, and then branched off that to start an AI automation agency (AAA) in June. So far I've come across a lot of unsustainable "ideas" to make money with AI, but at the same time a few diamonds in the rough that aren't fully tapped into yet- especially the AAA model. Thought I'd share this post to shine light into this new business model and share some ways you could potentially start your own agency, or at the very least know who you are dealing with and how to pick and choose when you (inevitably) get bombarded with cold emails from them down the line. Foreword Running an AAA does NOT involve using AI tools directly to generate and sell content directly. That ship has sailed, and unless you are happy with $5 from Fiverr every month or so, it is not a real business model. Cry me a river but generating generic art with AI and slapping it onto a T-shirt to sell on Etsy won't make you a dime. At the same time, the AAA model will NOT require you to have a deep theoretical knowledge of AI, or any academic degree, as we are more so dealing with the practical applications of generative AI and how we can implement these into different workflows and tech-stacks, rather than building AI models from the ground up. Regardless of all that, common sense and a willingness to learn will help (a shit ton), as with anything. Keep in mind - this WILL involve work and motivation as well. The mindset that AI somehow means everything can be done for you on autopilot is not the right way to approach things. The common theme of businesses I've seen who have successfully implemented AI into their operations is the willingess to work with AI in a way that augments their existing operations, rather than flat out replace a worker or team. And this is exactly the train of thought you need when working with AI as a business model. However, as the field is relatively unsaturated and hype surrounding AI is still fresh for enterprises, right now is the prime time to start something new if generative AI interests you at all. With that being said, I'll be going over three of the most successful AI-adjacent businesses I've seen over this past year, in addition to some tips and resources to point you in the right direction. so.. WTF is an AI Automation Agency? The AI automation agency (or as some YouTubers have coined it, the AAA model) at its core involves creating custom AI solutions for businesses. I have over 1500 AI tools listed in my directory, however the feedback I've received from some enterprise users is that ready-made SaaS tools are too generic to meet their specific needs. Combine this with the fact virtually no smaller companies have the time or skills required to develop custom solutions right off the bat, and you have yourself real demand. I would say in practice, the AAA model is quite similar to Wordpress and even web dev agencies, with the major difference being all solutions you develop will incorporate key aspects of AI AND automation. Which brings me to my second point- JUST AI IS NOT ENOUGH. Rather than reducing the amount of time required to complete certain tasks, I've seen many AI agencies make the mistake of recommending and (trying to) sell solutions that more likely than not increase the workload of their clients. For example, if you were to make an internal tool that has AI answer questions based on their knowledge base, but this knowledge base has to be updated manually, this is creating unnecessary work. As such I think one of the key components of building successful AI solutions is incorporating the new (Generative AI/LLMs) with the old (programmtic automation- think Zapier, APIs, etc.). Finally, for this business model to be successful, ideally you should target a niche in which you have already worked and understand pain points and needs. Not only does this make it much easier to get calls booked with prospects, the solutions you build will have much greater value to your clients (meaning you get paid more). A mistake I've seen many AAA operators make (and I blame this on the "Get Rich Quick" YouTubers) is focusing too much on a specific productized service, rather than really understanding the needs of businesses. The former is much done via a SaaS model, but when going the agency route the only thing that makes sense is building custom solutions. This is why I always take a consultant-first approach. You can only build once you understand what they actually need and how certain solutions may impact their operations, workflows, and bottom-line. Basics of How to Get Started Pick a niche. As I mentioned previously, preferably one that you've worked in before. Niches I know of that are actively being bombarded with cold emails include real estate, e-commerce, auto-dealerships, lawyers, and medical offices. There is a reason for this, but I will tell you straight up this business model works well if you target any white-collar service business (internal tools approach) or high volume businesses (customer facing tools approach). Setup your toolbox. If you wanted to start a pressure washing business, you would need a pressure-washer. This is no different. For those without programming knowledge, I've seen two common ways AAA get setup to build- one is having a network of on-call web developers, whether its personal contacts or simply going to Upwork or any talent sourcing agency. The second is having an arsenal of no-code tools. I'll get to this more in a second, but this works beecause at its core, when we are dealing with the practical applications of AI, the code is quite simple, simply put. Start cold sales. Unless you have a network already, this is not a step you can skip. You've already picked a niche, so all you have to do is find the right message. Keep cold emails short, sweet, but enticing- and it will help a lot if you did step 1 correctly and intimately understand who your audience is. I'll be touching base later about how you can leverage AI yourself to help you with outreach and closing. The beauty of gen AI and the AAA model You don't need to be a seasoned web developer to make this business model work. The large majority of solutions that SME clients want is best done using an API for an LLM for the actual AI aspect. The value we create with the solutions we build comes with the conceptual framework and design that not only does what they need it to but integrates smoothly with their existing tech-stack and workflow. The actual implementation is quite straightforward once you understand the high level design and know which tools you are going to use. To give you a sense, even if you plan to build out these apps yourself (say in Python) the large majority of the nitty gritty technical work has already been done for you, especially if you leverage Python libraries and packages that offer high level abstraction for LLM-related functions. For instance, calling GPT can be as little as a single line of code. (And there are no-code tools where these functions are simply an icon on a GUI). Aside from understanding the capabilities and limitations of these tools and frameworks, the only thing that matters is being able to put them in a way that makes sense for what you want to build. Which is why outsourcing and no-code tools both work in our case. Okay... but how TF am I suppposed to actually build out these solutions? Now the fun part. I highly recommend getting familiar with Langchain and LlamaIndex. Both are Python libraires that help a lot with the high-level LLM abstraction I mentioned previously. The two most important aspects include being able to integrate internal data sources/knowledge bases with LLMs, and have LLMs perform autonomous actions. The two most common methods respectively are RAG and output parsing. RAG (retrieval augmented Generation) If you've ever seen a tool that seemingly "trains" GPT on your own data, and wonder how it all works- well I have an answer from you. At a high level, the user query is first being fed to what's called a vector database to run vector search. Vector search basically lets you do semantic search where you are searching data based on meaning. The vector databases then retrieves the most relevant sections of text as it relates to the user query, and this text gets APPENDED to your GPT prompt to provide extra context to the AI. Further, with prompt engineering, you can limit GPT to only generate an answer if it can be found within this extra context, greatly limiting the chance of hallucination (this is where AI makes random shit up). Aside from vector databases, we can also implement RAG with other data sources and retrieval methods, for example SQL databses (via parsing the outputs of LLM's- more on this later). Autonomous Agents via Output Parsing A common need of clients has been having AI actually perform tasks, rather than simply spitting out text. For example, with autonomous agents, we can have an e-commerce chatbot do the work of a basic customer service rep (i.e. look into orders, refunds, shipping). At a high level, what's going on is that the response of the LLM is being used programmtically to determine which API to call. Keeping on with the e-commerce example, if I wanted a chatbot to check shipping status, I could have a LLM response within my app (not shown to the user) with a prompt that outputs a random hash or string, and programmatically I can determine which API call to make based on this hash/string. And using the same fundamental concept as with RAG, I can append the the API response to a final prompt that would spit out the answer for the user. How No Code Tools Can Fit In (With some example solutions you can build) With that being said, you don't necessarily need to do all of the above by coding yourself, with Python libraries or otherwise. However, I will say that having that high level overview will help IMMENSELY when it comes to using no-code tools to do the actual work for you. Regardless, here are a few common solutions you might build for clients as well as some no-code tools you can use to build them out. Ex. Solution 1: AI Chatbots for SMEs (Small and Medium Enterprises) This involves creating chatbots that handle user queries, lead gen, and so forth with AI, and will use the principles of RAG at heart. After getting the required data from your client (i.e. product catalogues, previous support tickets, FAQ, internal documentation), you upload this into your knowledge base and write a prompt that makes sense for your use case. One no-code tool that does this well is MyAskAI. The beauty of it especially for building external chatbots is the ability to quickly ingest entire websites into your knowledge base via a sitemap, and bulk uploading files. Essentially, they've covered the entire grunt work required to do this manually. Finally, you can create a inline or chat widget on your client's website with a few lines of HTML, or altneratively integrate it with a Slack/Teams chatbot (if you are going for an internal Q&A chatbot approach). Other tools you could use include Botpress and Voiceflow, however these are less for RAG and more for building out complete chatbot flows that may or may not incorporate LLMs. Both apps are essentially GUIs that eliminate the pain and tears and trying to implement complex flows manually, and both natively incoporate AI intents and a knowledge base feature. Ex. Solution 2: Internal Apps Similar to the first example, except we go beyond making just chatbots but tools such as report generation and really any sort of internal tool or automations that may incorporate LLM's. For instance, you can have a tool that automatically generates replies to inbound emails based on your client's knowledge base. Or an automation that does the same thing but for replies to Instagram comments. Another example could be a tool that generates a description and screeenshot based on a URL (useful for directory sites, made one for my own :P). Getting into more advanced implementations of LLMs, we can have tools that can generate entire drafts of reports (think 80+ pages), based not only on data from a knowledge base but also the writing style, format, and author voice of previous reports. One good tool to create content generation panels for your clients would be MindStudio. You can train LLM's via prompt engineering in a structured way with your own data to essentially fine tune them for whatever text you need it to generate. Furthermore, it has a GUI where you can dictate the entire AI flow. You can also upload data sources via multiple formats, including PDF, CSV, and Docx. For automations that require interactions between multiple apps, I recommend the OG zapier/make.com if you want a no-code solution. For instance, for the automatic email reply generator, I can have a trigger such that when an email is received, a custom AI reply is generated by MyAskAI, and finally a draft is created in my email client. Or, for an automation where I can create a social media posts on multiple platforms based on a RSS feed (news feed), I can implement this directly in Zapier with their native GPT action (see screenshot) As for more complex LLM flows that may require multiple layers of LLMs, data sources, and APIs working together to generate a single response i.e. a long form 100 page report, I would recommend tools such as Stack AI or Flowise (open-source alternative) to build these solutions out. Essentially, you get most of the functions and features of Python packages such as Langchain and LlamaIndex in a GUI. See screenshot for an example of a flow How the hell are you supposed to find clients? With all that being said, none of this matters if you can't find anyone to sell to. You will have to do cold sales, one way or the other, especially if you are brand new to the game. And what better way to sell your AI services than with AI itself? If we want to integrate AI into the cold outreach process, first we must identify what it's good at doing, and that's obviously writing a bunch of text, in a short amount of time. Similar to the solutions that an AAA can build for its clients, we can take advantage of the same principles in our own sales processes. How to do outreach Once you've identified your niche and their pain points/opportunities for automation, you want to craft a compelling message in which you can send via cold email and cold calls to get prospects booked on demos/consultations. I won't get into too much detail in terms of exactly how to write emails or calling scripts, as there are millions of resources to help with this, but I will tell you a few key points you want to keep in mind when doing outreach for your AAA. First, you want to keep in mind that many businesses are still hesitant about AI and may not understand what it really is or how it can benefit their operations. However, we can take advantage of how mass media has been reporting on AI this past year- at the very least people are AWARE that sooner or later they may have to implement AI into their businesses to stay competitive. We want to frame our message in a way that introduces generative AI as a technology that can have a direct, tangible, and positive impact on their business. Although it may be hard to quantify, I like to include estimates of man-hours saved or costs saved at least in my final proposals to prospects. Times are TOUGH right now, and money is expensive, so you need to have a compelling reason for businesses to get on board. Once you've gotten your messaging down, you will want to create a list of prospects to contact. Tools you can use to find prospects include Apollo.io, reply.io, zoominfo (expensive af), and Linkedin Sales Navigator. What specific job titles, etc. to target will depend on your niche but for smaller companies this will tend to be the owner. For white collar niches, i.e. law, the professional that will be directly benefiting from the tool (i.e. partners) may be better to contact. And for larger organizations you may want to target business improvement and digital transformation leads/directors- these are the people directly in charge of projects like what you may be proposing. Okay- so you have your message, and your list, and now all it comes down to is getting the good word out. I won't be going into the details of how to send these out, a quick Google search will give you hundreds of resources for cold outreach methods. However, personalization is key and beyond simple dynamic variables you want to make sure you can either personalize your email campaigns directly with AI (SmartWriter.ai is an example of a tool that can do this), or at the very least have the ability to import email messages programmatically. Alternatively, ask ChatGPT to make you a Python Script that can take in a list of emails, scrape info based on their linkedin URL or website, and all pass this onto a GPT prompt that specifies your messaging to generate an email. From there, send away. How tf do I close? Once you've got some prospects booked in on your meetings, you will need to close deals with them to turn them into clients. Call #1: Consultation Tying back to when I mentioned you want to take a consultant-first appraoch, you will want to listen closely to their goals and needs and understand their pain points. This would be the first call, and typically I would provide a high level overview of different solutions we could build to tacke these. It really helps to have a presentation available, so you can graphically demonstrate key points and key technologies. I like to use Plus AI for this, it's basically a Google Slides add-on that can generate slide decks for you. I copy and paste my default company messaging, add some key points for the presentation, and it comes out with pretty decent slides. Call #2: Demo The second call would involve a demo of one of these solutions, and typically I'll quickly prototype it with boilerplate code I already have, otherwise I'll cook something up in a no-code tool. If you have a niche where one type of solution is commonly demanded, it helps to have a general demo set up to be able to handle a larger volume of calls, so you aren't burning yourself out. I'll also elaborate on how the final product would look like in comparison to the demo. Call #3 and Beyond: Once the initial consultation and demo is complete, you will want to alleviate any remaining concerns from your prospects and work with them to reach a final work proposal. It's crucial you lay out exactly what you will be building (in writing) and ensure the prospect understands this. Furthermore, be clear and transparent with timelines and communication methods for the project. In terms of pricing, you want to take this from a value-based approach. The same solution may be worth a lot more to client A than client B. Furthermore, you can create "add-ons" such as monthly maintenance/upgrade packages, training sessions for employeees, and so forth, separate from the initial setup fee you would charge. How you can incorporate AI into marketing your businesses Beyond cold sales, I highly recommend creating a funnel to capture warm leads. For instance, I do this currently with my AI tools directory, which links directly to my AI agency and has consistent branding throughout. Warm leads are much more likely to close (and honestly, much nicer to deal with). However, even without an AI-related website, at the very least you will want to create a presence on social media and the web in general. As with any agency, you will want basic a professional presence. A professional virtual address helps, in addition to a Google Business Profile (GBP) and TrustPilot. a GBP (especially for local SEO) and Trustpilot page also helps improve the looks of your search results immensely. For GBP, I recommend using ProfilePro, which is a chrome extension you can use to automate SEO work for your GBP. Aside from SEO optimzied business descriptions based on your business, it can handle Q/A answers, responses, updates, and service descriptions based on local keywords. Privacy and Legal Concerns of the AAA Model Aside from typical concerns for agencies relating to service contracts, there are a few issues (especially when using no-code tools) that will need to be addressed to run a successful AAA. Most of these surround privacy concerns when working with proprietary data. In your terms with your client, you will want to clearly define hosting providers and any third party tools you will be using to build their solution, and a DPA with these third parties listed as subprocessors if necessary. In addition, you will want to implement best practices like redacting private information from data being used for building solutions. In terms of addressing concerns directly from clients, it helps if you host your solutions on their own servers (not possible with AI tools), and address the fact only ChatGPT queries in the web app, not OpenAI API calls, will be used to train OpenAI's models (as reported by mainstream media). The key here is to be open and transparent with your clients about ALL the tools you are using, where there data will be going, and make sure to get this all in writing. have fun, and keep an open mind Before I finish this post, I just want to reiterate the fact that this is NOT an easy way to make money. Running an AI agency will require hours and hours of dedication and work, and constantly rearranging your schedule to meet prospect and client needs. However, if you are looking for a new business to run, and have a knack for understanding business operations and are genuinely interested in the pracitcal applications of generative AI, then I say go for it. The time is ticking before AAA becomes the new dropshipping or SMMA, and I've a firm believer that those who set foot first and establish themselves in this field will come out top. And remember, while 100 thousand people may read this post, only 2 may actually take initiative and start.

I Quit My Tech Job 6 Months Ago. Built 10+ Products. Made $0. Here's Everything I Learned.
reddit
LLM Vibe Score0
Human Vibe Score1
WaynedevvvThis week

I Quit My Tech Job 6 Months Ago. Built 10+ Products. Made $0. Here's Everything I Learned.

I quit my tech job 6 months ago to go full indie. Had enough savings and didn't want to miss the AI wave. Since then, I've built 10+ products - B2C, B2B, mobile apps, directories, marketplaces, you name it. But I keep repeating the same cycle: have an idea, dream big, build for weeks, "launch" (and by launch, I mean just deploy and go live with zero promotion), then get bored and lose motivation to market it. Then I start looking for new ideas to build. Is it just me, or does anyone else face something similar? Maybe coding is my comfort zone and marketing isn't, that's why... I knew entrepreneurship was hard, but it's MUCH harder than I thought. After these failures, here's everything I've learned: Lessons Learned The Hard Way Don't build something you don't have passion for. Pushing a product is hard and takes tremendous effort. If you don't have passion for it, you won't push through the initial "no interest" zone. Think carefully: would you be proud of what you build after building it? If yes, proceed. If not, don't waste time. Build your audience/network first. This isn't new advice, but it's 100% key for entrepreneurs to succeed. I'm still figuring this out, but one thing is clear: "Value" is the key. Stop posting random stuff and instead give value. People don't care about you and your life, but they do care about what you can offer them. Don't rush. Entrepreneurship isn't a sprint; it's a marathon. Don't rush to build stuff. Take a step back to think, plan, and learn. Coding for 16 hours a day won't do you any good - you'll end up building something people don't want. What I'm Doing Differently Next Time After all these failures, I finally took time with myself to think about how I can approach things differently. Here's my new plan: I will not start a new project if I know I'll ditch it after building it. I will follow best practices: validate the idea, research competitors, look for beta users, and ship fast. I will start building my audience and personal brand through documenting the journey. I've already decided what I'm building next, and yes, this time I'm going all in. I'll apply everything I've learned so far, and hopefully, this time will be different. Will update you all soon. Keep shipping, folks! Hopefully we'll see your "I reached 10k MRR for my SaaS" post soon.

Jinxed - $0 month after bragging about my first $10k month here. (PROGRESS UPDATE)
reddit
LLM Vibe Score0
Human Vibe Score1
swagamoneyThis week

Jinxed - $0 month after bragging about my first $10k month here. (PROGRESS UPDATE)

A month ago I made a post in this sub about my first $10k month. It went viral. And guess what - I didn't make another dollar since. Honestly, I shouldn't have made any money that first month also. Because I didn't have an offer. If you're familiar with Alex Hormozi you know that the offer is what makes or breaks a business. And I simply didn't have it. I managed to close my first clients just because I rode the AI hype train and managed to capture a couple of CEOs who were riding it too. Took whatever I could get for installment without thinking about the future. (It also helped that I wasn't bullshitting and had a legit enterprise-grade custom GPT framework ready). But that's not a business strategy at all. You can't base your business solely off hype. So the last month was dedicated to crafting a proper offer. No selling involved. Purely discovery chats with as many people as possible. The viral post helped because I connected with some badass people I wouldn't have reached otherwise. Even managed to add a new team member from Reddit. But most importantly, we now have the offer: Enterprise-grade AI assistant trained on your data for a fraction of the market cost. Basically a custom GPT for companies that want a secure assistant "trained" on their data but are not willing to spend millions on OpenAI's Custom Models or hundreds of thousands on Enterprise ChatGPT. (OpenAI's introduction of exclusive business GPTs for $2-3M is an incredibly good leverage for this offer). Also got rid of the big installment fee and switched to a $1k/month starting price for attractiveness and simplicity for companies (that covers their Azure fees also). The key offer points here are: Data security (as there are cheap, but not enterprise-grade tools like PDF.ai) Good price (as not all businesses can afford to pay 6 figure premiums for their data security) So the lesson here (I suppose) is that it's okay to take a step back sometimes. Reevaluate your direction. It's not worth sprinting when you're running in circles. P.S. finally made a website https://jongri.tech

The delicate balance of building an online community business
reddit
LLM Vibe Score0
Human Vibe Score0.895
matthewbarbyThis week

The delicate balance of building an online community business

Hey /r/Entrepreneur 👋 Just under two years ago I launched an online community business called Traffic Think Tank with two other co-founders, Nick Eubanks and Ian Howells. As a Traffic Think Tank customer you (currently) pay $119 a month to get access to our online community, which is run through Slack. The community is focused on helping you learn various aspects of marketing, with a particular focus on search engine optimization (SEO). Alongside access to the Slack community, we publish new educational video content from outside experts every week that all customers have access to. At the time of writing, Traffic Think Tank has around 650 members spanning across 17 of the 24 different global time zones. I was on a business trip over in Sydney recently, and during my time there I met up with some of our Australia-based community members. During dinner I was asked by several of them how the idea for Traffic Think Tank came about and what steps we took to validate that the idea was worth pursuing.  This is what I told them… How it all began It all started with a personal need. Nick, an already successful entrepreneur and owner of a marketing agency, had tested out an early version Traffic Think Tank in early 2017. He offered real-time consulting for around ten customers that he ran from Slack. He would publish some educational videos and offer his advice on projects that the members were running. The initial test went well, but it was tough to maintain on his own and he had to charge a fairly high price to make it worth his time. That’s when he spoke to me and Ian about turning this idea into something much bigger. Both Ian and I offered something slightly different to Nick. We’ve both spent time in senior positions at marketing agencies, but currently hold senior director positions in 2,000+ public employee companies (HubSpot and LendingTree). Alongside this, as a trio we could really ramp up the quality and quantity of content within the community, spread out the administrative workload and just generally have more resources to throw at getting this thing off the ground. Admittedly, Nick was much more optimistic about the potential of Traffic Think Tank – something I’m very thankful for now – whereas Ian and I were in the camp of “you’re out of your mind if you think hundreds of people are going to pay us to be a part of a Slack channel”. To validate the idea at scale, we decided that we’d get an initial MVP of the community up and running with a goal of reaching 100 paying customers in the first six months. If we achieved that, we’d validated that it was a viable business and we would continue to pursue it. If not, we’d kill it. We spent the next month building out the initial tech stack that enabled us to accept payments, do basic user management to the Slack channel, and get a one-page website up and running with information on what Traffic Think Tank was all about.  After this was ready, we doubled down on getting some initial content created for members – I mean, we couldn’t have people just land in an empty Slack channel, could we? We created around ten initial videos, 20 or so articles and then some long threads full of useful information within the Slack channel so that members would have some content to pour into right from the beginning.  Then, it was time to go live. The first 100 customers Fortunately, both Nick and I had built a somewhat substantial following in the SEO space over the previous 5-10 years, so we at least had a large email list to tap into (a total of around 40,000 people). We queued up some launch emails, set an initial price of $99 per month and pressed send. [\[LINK\] The launch email I sent to my subscribers announcing Traffic Think Tank](https://mailchi.mp/matthewbarby/future-of-marketing-1128181) What we didn’t expect was to sell all of the initial 100 membership spots in the first 72 hours. “Shit. What do we do now? Are we ready for this many people? Are we providing them with enough value? What if something breaks in our tech stack? What if they don’t like the content? What if everyone hates Slack?” All of these were thoughts running through my head. This brings me to the first great decision we made: we closed down new membership intake for 3 months so that we could focus completely on adding value to the first cohort of users. The right thing at the right time SEO is somewhat of a dark art to many people that are trying to learn about it for the first time. There’s hundreds of thousands (possibly millions) of articles and videos online that talk about how to do SEO.  Some of it’s good advice; a lot of it is very bad advice.  Add to this that the barrier to entry of claiming to be an “expert” in SEO is practically non-existent and you have a recipe for disaster. This is why, for a long time, individuals involved in SEO have flocked in their masses to online communities for information and to bounce ideas off of others in the space. Forums like SEObook, Black Hat World, WickedFire, Inbound.org, /r/BigSEO, and many more have, at one time, been called home by many SEOs.  In recent times, these communities have either been closed down or just simply haven’t adapted to the changing needs of the community – one of those needs being real-time feedback on real-world problems.  The other big need that we all spotted and personally had was the ability to openly share the things that are working – and the things that aren’t – in SEO within a private forum. Not everyone wanted to share their secret sauce with the world. One of the main reasons we chose Slack as the platform to run our community on was the fact that it solved these two core needs. It gave the ability to communicate in real-time across multiple devices, and all of the information shared within it was outside of the public domain. The other problem that plagued a lot of these early communities was spam. Most of them were web-based forums that were free to access. That meant they became a breeding ground for people trying to either sell their services or promote their own content – neither of which is conducive to building a thriving community. This was our main motivation for charging a monthly fee to access Traffic Think Tank. We spent a lot of time thinking through pricing. It needed to be enough money that people would be motivated to really make use of their membership and act in a way that’s beneficial to the community, but not too much money that it became cost prohibitive to the people that would benefit from it the most. Considering that most of our members would typically spend between $200-800 per month on SEO software, $99 initially felt like the perfect balance. Growing pains The first three months of running the community went by without any major hiccups. Members were incredibly patient with us, gave us great feedback and were incredibly helpful and accommodating to other members. Messages were being posted every day, with Nick, Ian and myself seeding most of the engagement at this stage.  With everything going smoothly, we decided that it was time to open the doors to another intake of new members. At this point we’d accumulated a backlog of people on our waiting list, so we knew that simply opening our doors would result in another large intake. Adding more members to a community has a direct impact on the value that each member receives. For Traffic Think Tank in particular, the value for members comes from three areas: The ability to have your questions answered by me, Nick and Ian, as well as other members of the community. The access to a large library of exclusive content. The ability to build connections with the wider community. In the early stages of membership growth, there was a big emphasis on the first of those three points. We didn’t have an enormous content library, nor did we have a particularly large community of members, so a lot of the value came from getting a lot of one-to-one time with the community founders. [\[IMAGE\] Screenshot of engagement within the Traffic Think Tank Slack community](https://cdn.shortpixel.ai/client/qglossy,retimg,w_1322/https://www.matthewbarby.com/wp-content/uploads/2019/08/Community-Engagement-in-Traffic-Think-Tank.png) The good thing about having 100 members was that it was just about feasible to give each and every member some one-to-one time within the month, which really helped us to deliver those moments of delight that the community needed early on. Two-and-a-half months after we launched Traffic Think Tank, we opened the doors to another 250 people, taking our total number of members to 350. This is where we experienced our first growing pains.  Our original members had become used to being able to drop us direct messages and expect an almost instant response, but this wasn’t feasible anymore. There were too many people, and we needed to create a shift in behavior. We needed more value to come from the community engaging with one another or we’d never be able to scale beyond this level. We started to really pay attention to engagement metrics; how many people were logging in every day, and of those, how many were actually posting messages within public channels.  We asked members that were logging in a lot but weren’t posting (the “lurkers”) why that was the case. We also asked the members that engaged in the community the most what motivated them to post regularly. We learned a lot from doing this. We found that the large majority of highly-engaged members had much more experience in SEO, whereas most of the “lurkers” were beginners. This meant that most of the information being shared in the community was very advanced, with a lot of feedback from the beginners in the group being that they “didn’t want to ask a stupid question”.  As managers of the community, we needed to facilitate conversations that catered to all of our members, not just those at a certain level of skill. To tackle this problem, we created a number of new channels that had a much deeper focus on beginner topics so novice members had a safe place to ask questions without judgment.  We also started running live video Q&As each month where we’d answer questions submitted by the community. This gave our members one-on-one time with me, Nick and Ian, but spread the value of these conversations across the whole community rather than them being hidden within private messages. As a result of these changes, we found that the more experienced members in the community were really enjoying sharing their knowledge with those with less experience. The number of replies within each question thread was really starting to increase, and the community started to shift away from just being a bunch of threads created by me, Nick and Ian to a thriving forum of diverse topics compiled by a diverse set of individuals. This is what we’d always wanted. A true community. It was starting to happen. [\[IMAGE\] Chart showing community engagement vs individual member value](https://cdn.shortpixel.ai/client/qglossy,retimg,w_1602/https://www.matthewbarby.com/wp-content/uploads/2019/08/Community-Engagement-Balance-Graph.jpg) At the same time, we started to realize that we’ll eventually reach a tipping point where there’ll be too much content for us to manage and our members to engage with. When we reach this point, the community will be tough to follow and the quality of any given post will go down. Not only that, but the community will become increasingly difficult to moderate. We’re not there yet, but we recognize that this will come, and we’ll have to adjust our model again. Advocating advocacy As we started to feel more comfortable about the value that members were receiving, we made the decision to indefinitely open for new members. At the same time, we increased the price of membership (from $99 a month to $119) in a bid to strike the right balance between profitability as a business and to slow down the rate at which we were reaching the tipping point of community size. We also made the decision to repay all of our early adopters by grandfathering them in to the original pricing – and committing to always do this in the future. Despite the price increase, we saw a continued flow of new members come into the community. The craziest part about this was that we were doing practically no marketing activities to encourage new members– this was all coming from word of mouth. Our members were getting enough value from the community that they were recommending it to their friends, colleagues and business partners.  The scale at which this was happening really took us by surprise and it told us one thing very clearly: delivering more value to members resulted in more value being delivered to the business. This is a wonderful dynamic to have because it perfectly aligns the incentives on both sides. We’d said from the start that we wouldn’t sacrifice value to members for more revenue – this is something that all three of us felt very strongly about. First and foremost, we wanted to create a community that delivered value to its members and was run in a way that aligned with our values as people. If we could find a way to stimulate brand advocacy, while also tightening the bonds between all of our individual community members, we’d be boosting both customer retention and customer acquisition in the same motion. This became our next big focus. [\[TWEET\] Adam, one of our members wore his Traffic Think Tank t-shirt in the Sahara desert](https://twitter.com/AdamGSteele/status/1130892481099382784) We started with some simple things: We shipped out Traffic Think Tank branded T-shirts to all new members. We’d call out each of the individuals that would submit questions to our live Q&A sessions and thank them live on air. We set up a new channel that was dedicated to sharing a quick introduction to who you are, what you do and where you’re based for all new members. We’d created a jobs channel and a marketplace for selling, buying and trading services with other members. Our monthly “blind dates” calls were started where you’d be randomly grouped with 3-4 other community members so that you could hop on a call to get to know each other better. The Traffic Think Tank In Real Life (IRL)* channel was born, which enabled members to facilitate in-person meetups with each other. In particular, we saw that as members started to meet in person or via calls the community itself was feeling more and more like a family. It became much closer knit and some members started to build up a really positive reputation for being particularly helpful to other members, or for having really strong knowledge in a specific area. [\[TWEET\] Dinner with some of the Traffic Think Tank members in Brighton, UK](https://twitter.com/matthewbarby/status/1117175584080134149) Nick, Ian and I would go out of our way to try and meet with members in real life wherever we could. I was taken aback by how appreciative people were for us doing this, and it also served as an invaluable way to gain honest feedback from members. There was another trend that we’d observed that we didn’t really expect to happen. More and more members were doing business with each another. We’ve had people find new jobs through the community, sell businesses to other members, launch joint ventures together and bring members in as consultants to their business. This has probably been the most rewarding thing to watch, and it was clear that the deeper relationships that our members were forming were resulting in an increased level of trust to work with each other. We wanted to harness this and take it to a new level. This brought us to arguably the best decision we’ve made so far running Traffic Think Tank… we were going to run a big live event for our members. I have no idea what I’m doing It’s the first week of January 2019 and we’re less than three weeks away from Traffic Think Tank LIVE, our first ever in-person event hosting 150 people, most of which are Traffic Think Tank members. It's like an ongoing nightmare I can’t wake up from. That was Nick’s response in our private admin channel to myself and Ian when I asked if they were finding the run-up to the event as stressful as I was. I think that all three of us were riding on such a high from how the community was growing that we felt like we could do anything. Running an event? How hard can it be? Well, turns out it’s really hard. We had seven different speakers flying over from around the world to speak at the event, there was a pre- and after event party, and we’d planned a charity dinner where we would take ten attendees (picked at random via a raffle) out for a fancy meal. Oh, and Nick, Ian and I were hosting a live Q&A session on stage. It wasn’t until precisely 48 hours before the event that we’d realized we didn’t have any microphones, nor had a large amount of the swag we’d ordered arrived. Plus, a giant storm had hit Philly causing a TON of flight cancellations. Perfect. Just perfect. This was honestly the tip of the iceberg. We hadn’t thought about who was going to run the registration desk, who would be taking photos during the event and who would actually field questions from the audience while all three of us sat on stage for our live Q&A panel. Turns out that the answer to all of those questions were my wife, Laura, and Nick’s wife, Kelley. Thankfully, they were on hand to save our asses. The weeks running up to the event were honestly some of the most stressful of my life. We sold around 50% of our ticket allocation within the final two weeks before the event. All of the event organizers told us this would happen, but did we believe them? Hell no!  Imagine having two weeks until the big day and as it stood half of the room would be completely empty. I was ready to fly most of my extended family over just to make it look remotely busy. [\[IMAGE\] One of our speakers, Ryan Stewart, presenting at Traffic Think Tank LIVE](https://cdn.shortpixel.ai/client/qglossy,retimg,w_1920/https://www.matthewbarby.com/wp-content/uploads/2019/08/Traffic-Think-Tank-LIVE-Ryan-Presenting.jpg) Thankfully, if all came together. We managed to acquire some microphones, the swag arrived on the morning of the event, all of our speakers were able to make it on time and the weather just about held up so that our entire allocation of ticket holders was able to make it to the event. We pooled together and I’m proud to say that the event was a huge success. While we made a substantial financial loss on the event itself, January saw a huge spike in new members, which more than recouped our losses. Not only that, but we got to hang out with a load of our members all day while they said really nice things about the thing we’d built. It was both exhausting and incredibly rewarding. Bring on Traffic Think Tank LIVE 2020! (This time we’re hiring an event manager...)   The road ahead Fast forward to today (August 2019) and Traffic Think Tank has over 650 members. The biggest challenges that we’re tackling right now include making sure the most interesting conversations and best content surfaces to the top of the community, making Slack more searchable (this is ultimately one of its flaws as a platform) and giving members a quicker way to find the exclusive content that we create. You’ll notice there’s a pretty clear theme here. In the past 30 days, 4,566 messages were posted in public channels inside Traffic Think Tank. If you add on any messages posted inside private direct messages, this number rises to 21,612. That’s a lot of messages. To solve these challenges and enable further scale in the future, we’ve invested a bunch of cash and our time into building out a full learning management system (LMS) that all members will get access to alongside the Slack community. The LMS will be a web-based portal that houses all of the video content we produce. It will also  provide an account admin section where users can update or change their billing information (they have to email us to do this right now, which isn’t ideal), a list of membership perks and discounts with our partners, and a list of links to some of the best threads within Slack – when clicked, these will drop you directly into Slack. [\[IMAGE\] Designs for the new learning management system (LMS)](https://cdn.shortpixel.ai/client/qglossy,retimg,w_2378/https://www.matthewbarby.com/wp-content/uploads/2019/08/Traffic-Think-Tank-LMS.png) It’s not been easy, but we’re 95% of the way through this and I’m certain that it will have a hugely positive impact on the experience for our members. Alongside this we hired a community manager, Liz, who supports with any questions that our members have, coordinates with external experts to arrange webinars for the community, helps with new member onboarding, and has tightened up some of our processes around billing and general accounts admin. This was a great decision. Finally, we’ve started planning next year’s live event, which we plan to more than double in size to 350 attendees, and we decided to pick a slightly warmer location in Miami this time out. Stay tuned for me to have a complete meltdown 3 weeks from the event. Final thoughts When I look back on the journey we’ve had so far building Traffic Think Tank, there’s one very important piece to this puzzle that’s made all of this work that I’ve failed to mention so far: co-founder alignment. Building a community is a balancing act that relies heavily on those in charge being completely aligned. Nick, Ian and I completely trust each other and more importantly, are philosophically aligned on how we want to run and grow the community. If we didn’t have this, the friction between us could tear apart the entire community. Picking the right people to work with is important in any company, but when your business is literally about bringing people together, there’s no margin for error here.  While I’m sure there will be many more challenges ahead, knowing that we all trust each other to make decisions that fall in line with each of our core values makes these challenges dramatically easier to overcome. Finally, I’d like to thank all of our members for making the community what it is today – it’d be nothing without you and I promise that we’ll never take that for granted. &#x200B; I originally posted this on my blog here. Welcoming all of your thoughts, comments, questions and I'll do my best to answer them :)

Started a content marketing agency 6 years ago - $0 to $5,974,324 (2023 update)
reddit
LLM Vibe Score0
Human Vibe Score1
mr_t_forhireThis 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.

I got fired due to automation — lessons learned. Two-month overview.
reddit
LLM Vibe Score0
Human Vibe Score1
WebsterPepsterThis week

I got fired due to automation — lessons learned. Two-month overview.

UPD: Guys, I'm not promoting myself as some of the redditors decided. That's why to deal with contradictions I'll do next things: make additional post with short review and description of the general tools and processes you could apply. help only those who have already written me. So I won't answer on new offers or DMs. As mentioned, damn robots have taken my job. PRE-HISTORY During Covid times, I found myself without my offline job, and since I was interested in marketing and SMM, I began searching for a job there. Completed free Google and Udemy courses and finally landed my first SMM manager position with a business owner. He had several projects so, finally, I started managing three Twitter accounts, two Facebook accs, two IGs, and one TikTok. I handled posting, content editing and responding routine, while freelancers usually took care of video creation for IG and TT. THE STORY ITSELF Things took a turn for the worse in April when my employer introduced ChatGPT and Midjourney, tools I was already using. The owner insisted on integrating them into the workflow, and my wages took a 20% hit. I thought I could roll with it, but it was just the beginning. By midsummer, the owner implemented second-layer AI tools like Visla, Pictory, and Woxo for video (bye freelancers, lol), as well as TweetHunter, Jasper, and Perplexity for content. Midjourney and Firefly joined for image generation. All together, my paycheck was slashed by 50%. Finally, at the end of October, my boss told me he automated stuff with Zapier, cutting costs that way. Additionally, he adopted MarketOwl, autoposting tool for Twitter, and SocialBee for Facebook. He stated that he didn’t need me, as by now he could manage the social media accounts himself. I feel so pissed then and even thought that there's no point in searching for similar jobs. HOW I SPENT TWO MONTHS Well, for the first two weeks, I did nothing but being miserable, drinking and staring at the wall. My gf said it's unbearable and threatened to leave if I not pull myself together. It was not the final push, but definitely made me rethink things. So I decided to learn more about the capabilities of these automation covers and eventually became an AI adviser for small businesses. It's ironic that now I sometimes earn money advising on how to optimize marketing, possibly contributing to other people's job loss. FINAL THOUGHTS I am fully aware of the instability of such a job and have invested my last savings in taking an online marketing course at Columbia to gain more marketing experience and got something more stable afterwards. Message for mods: I'm not promoting myself or anything mentioned here; just sharing the experience that someone might find helpful.

Recently hit 6,600,000 monthly organic traffic for a B2C SaaS website. Here's the 40 tips that helped me make that happen.
reddit
LLM Vibe Score0
Human Vibe Score1
DrJigsawThis week

Recently hit 6,600,000 monthly organic traffic for a B2C SaaS website. Here's the 40 tips that helped me make that happen.

Hey guys! So as title says, we recently hit 6,600,000 monthly organic traffic / month for a B2C SaaS website (screenshot. Can't give name publicly, but can show testimonial to a mod). Here's 40 tips that "helped" me make this happen. If you get some value of the post, I write an SEO tip every other day on /r/seogrowth. There's around 10 more tips already up there other than the ones I mention here. If you want to give back for all my walls of text, I'd appreciate a sub <3 Also, there are a bunch of free stuff I mention in the article: content outline, writer guidelines, SEO checklist, and other stuff. Here's the Google Doc with all that! Tip #1. Take SEO With a Grain of Salt A lot of the SEO advice and best practices on the internet are based on 2 things: Personal experiences and case studies of companies that managed to make SEO work for them. Google or John Mueller (Google’s Senior Webmaster Trends Analyst). And, unfortunately, neither of these sources are always accurate. Personal SEO accounts are simply about what worked for specific companies. Sometimes, what worked for others, won’t work for you. For example, you might find a company that managed to rank with zero link-building because their website already had a very strong backlink profile. If you’re starting with a fresh website, chances are, you won’t be able to get the same results. At the same time, information from Google or John Mueller is also not 100% accurate. For example, they’ve said that guest posting is against Google’s guidelines and doesn’t work… But practically, guest posting is a very effective link-building strategy. So the takeaway is this: Take all information you read about SEO with a grain of salt. Analyze the information yourself, and make your conclusions. SEO Tip #2. SEO Takes Time You’ve already heard this one before, but considering how many people keep asking, thought I'd include this anyway. On average, it’s going to take you 6 months to 2 years to get SEO results, depending on the following factors: Your backlink profile. The more quality backlinks you have (or build), the faster you’ll rank. Age of your website. If your website is older (or you purchased an aged website), you can expect your content to rank faster. Amount of content published. The more quality content you publish on your website, the more “authoritative” it is in the eyes of Google, and thus more likely to rank faster. SEO work done on the website. If a lot of your pages are already ranking on Google (page 2-3), it’s easier to get them to page #1 than if you just published the content piece. Local VS global SEO. Ranking locally is (sometimes) easier and faster than ranking globally. That said, some marketing agencies can use “SEO takes time” as an excuse for not driving results. Well, fortunately, there is a way to track SEO results from month #2 - #3 of work. Simply check if your new content pieces/pages are getting more and more impressions on Google Search Console month-to-month. While your content won’t be driving traffic for a while after being published, they’ll still have a growing number of impressions from month #2 or #3 since publication. SEO Tip #3. SEO Might Not Be The Best Channel For You In theory, SEO sounds like the best marketing channel ever. You manage to rank on Google and your marketing seemingly goes on auto-pilot - you’re driving new leads every day from existing content without having to lift a finger… And yet, SEO is not for everyone. Avoid SEO as a marketing channel if: You’re just getting started with your business and need to start driving revenue tomorrow (and not in 1-2 years). If this is you, try Google ads, Facebook ads, or organic marketing. Your target audience is pretty small. If you’re selling enterprise B2B software and have around 2,000 prospects in total worldwide, then it’s simply easier to directly reach out to these prospects. Your product type is brand-new. If customers don’t know your product exists, they probably won’t be Googling it. SEO Tip #4. Traffic Can Be a Vanity Metric I've seen hundreds of websites that drive 6-7 digits of traffic but generate only 200-300 USD per month from those numbers. “What’s the deal?” You might be thinking. “How can you fail to monetize that much traffic?” Well, that brings us to today’s tip: traffic can be a vanity metric. See, not all traffic is created equal. Ranking for “hormone balance supplement” is a lot more valuable than ranking for “Madagascar character names.” The person Googling the first keyword is an adult ready to buy your product. Someone Googling the latter, on the other hand, is a child with zero purchasing power. So, when deciding on which keywords to pursue, always keep in mind the buyer intent behind and don’t go after rankings or traffic just because 6-digit traffic numbers look good. SEO Tip #5. Push Content Fast Whenever you publish a piece of content, you can expect it to rank within 6 months to a year (potentially less if you’re an authority in your niche). So, the faster you publish your content, the faster they’re going to age, and, as such, the faster they’ll rank on Google. On average, I recommend you publish a minimum of 10,000 words of content per month and 20,000 to 30,000 optimally. If you’re not doing link-building for your website, then I’d recommend pushing for even more content. Sometimes, content velocity can compensate for the lack of backlinks. SEO Tip #6. Use Backlink Data to Prioritize Content You might be tempted to go for that juicy, 6-digit traffic cornerstone keyword right from the get-go... But I'd recommend doing the opposite. More often than not, to rank for more competitive, cornerstone keywords, you’ll need to have a ton of supporting content, high-quality backlinks, website authority, and so on. Instead, it’s a lot more reasonable to first focus on the less competitive keywords and then, once you’ve covered those, move on to the rest. Now, as for how to check keyword competitiveness, here are 2 options: Use Mozbar to see the number of backlinks for top-ranking pages, as well as their Domain Authority (DA). If all the pages ranking on page #1 have <5 backlinks and DA of 20 - 40, it’s a good opportunity. Use SEMrush or Ahrefs to sort your keywords by difficulty, and focus on the less difficult keywords first. Now, that said, keep in mind that both of these metrics are third-party, and hence not always accurate. SEO Tip #7. Always Start With Competitive Analysis When doing keyword research, the easiest way to get started is via competitive analysis. Chances are, whatever niche you’re in, there’s a competitor that is doing great with SEO. So, instead of having to do all the work from scratch, run their website through SEMrush or Ahrefs and steal their keyword ideas. But don’t just stop there - once you’ve borrowed keyword ideas from all your competitors, run the seed keywords through a keyword research tool such as UberSuggest or SEMrush Keyword Magic Tool. This should give you dozens of new ideas that your competitors might’ve missed. Finally, don’t just stop at borrowing your competitor’s keyword ideas. You can also borrow some inspiration on: The types of graphics and images you can create to supplement your blog content. The tone and style you can use in your articles. The type of information you can include in specific content pieces. SEO Tip #8. Source a LOT of Writers Content writing is one of those professions that has a very low barrier to entry. Anyone can take a writing course, claim to be a writer, and create an UpWork account… This is why 99% of the writers you’ll have to apply for your gigs are going to be, well, horrible. As such, if you want to produce a lot of content on the reg, you’ll need to source a LOT of writers. Let’s do the math: If, by posting a job ad, you source 100 writers, you’ll see that only 5 of them are a good fit. Out of the 5 writers, 1 has a very high rate, so they drop out. Another doesn’t reply back to your communication, which leaves you with 3 writers. You get the 3 writers to do a trial task, and only one turns out to be a good fit for your team. Now, since the writer is freelance, the best they can do is 4 articles per month for a total of 5,000-words (which, for most niches, ain’t all that much). So, what we’re getting at here is, to hire quality writers, you should source a LOT of them. SEO Tip #9. Create a Process for Filtering Writers If you follow the previous tip, you'll end up with a huge database of hundreds of writers. This creates a whole new problem: You now have a database of 500+ writers waiting for you to sift through them and decide which ones are worth the hire. It would take you 2-3 days of intense work to go through all these writers and vet them yourself. Let’s be real - you don’t have time for that. Here’s what you can do instead: When sourcing writers, always get them to fill in a Google form (instead of DMing or emailing you). In this form, make sure to ask for 3 relevant written samples, a link to the writer’s portfolio page, and the writer’s rate per word. Create a SOP for evaluating writers. The criteria for evaluation should be: Level of English. Does the writer’s sample have any English mistakes? If so, they’re not a good fit. Quality of Samples. Are the samples long-form and engaging 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. Get your VA to evaluate the writer’s samples as per the criteria above and short-list writers that seem competent. If you sourced 500 writers, the end result of this process should be around 50 writers. You or your editor goes through the short-list of 50 writers and invites 5-10 for a (paid) trial task. The trial task is very important - you’ll sometimes find that the samples provided by the writer don’t match their writing level. SEO Tip #10. Use the Right Websites to Find Writers Not sure where to source your writers? Here are some ideas: ProBlogger \- Our #1 choice - a lot of quality writers frequent this website. LinkedIn \- You can headhunt content writers in specific locations. Upwork \- If you post a content gig, most writers are going to be awful. Instead, I recommend headhunting top writers instead. WeWorkRemotely \- Good if you’re looking to make a full-time remote hire. Facebook \- There are a ton of quality Facebook groups for writers. Some of our faves are Cult of Copy Job Board and Content Marketing Lounge. SEO Tip #11. Always Use Content Outlines When giving tasks to your writing team, you need to be very specific about the instructions you give them. Don’t just provide a keyword and tell them to “knock themselves out.” The writer isn’t a SEO expert; chances are, they’re going to mess it up big-time and talk about topics that aren’t related to the keyword you’re targeting. Instead, when giving tasks to writers, do it through content outlines. A content outline, in a nutshell, is a skeleton of the article they’re supposed to write. It includes information on: Target word count (aim for the same or 50% more the word count than that of the competition). Article title. Article structure (which sections should be mentioned and in what order). Related topics of keywords that need to be mentioned in the article. Content outline example in the URL in the post intro. SEO Tip #12. Focus on One Niche at a Time I used to work with this one client that had a SaaS consisting of a mixture of CRM, Accounting Software, and HRS. I had to pick whether we were going to focus on topics for one of these 3 niches or focus on all of them at the same time. I decided to do the former. Here’s why: When evaluating what to rank, Google considers the authority of your website. If you have 60 articles about accounting (most of which link to each other), you’re probably an authority in the niche and are more likely to get good rankings. If you have 20 sales, 20 HR, and 20 accounting articles, though, none of these categories are going to rank as well. It always makes more sense to first focus on a single niche (the one that generates the best ROI for your business), and then move on to the rest. This also makes it easier to hire writers - you hire writers specialized in accounting, instead of having to find writers who can pull off 3 unrelated topics. SEO Tip #13. Just Hire a VA Already It’s 2021 already guys—unless you have a virtual assistant, you’re missing out big-time. Since a lot of SEO tasks are very time-consuming, it really helps to have a VA around to take over. As long as you have solid SOPs in place, you can hire a virtual assistant, train them, and use them to free up your time. Some SEO tasks virtual assistants can help with are: Internal linking. Going through all your blog content and ensuring that they link to each other. Backlink prospecting. Going through hundreds of websites daily to find link opportunities. Uploading content on WordPress and ensuring that the content is optimized well for on-page SEO. SEO Tip #14. Use WordPress (And Make Your Life Easier) 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. It’s cheap, efficient, extremely easy to learn, and comes jam-packed with different plugins and features. Wix, SiteGround, and similar drag & drops are pure meh. SEO Tip #15. Use These Nifty WordPress Plugins There are a lot of really cool WordPress plugins that can make your (SEO) life so much easier. Some of our favorites include: RankMath. A more slick alternative to YoastSEO. Useful for on-page SEO. Smush. App that helps you losslessly compress all images on your website, as well as enables lazy loading. WP Rocket. This plugin helps speed up your website pretty significantly. Elementor. Not a techie? This drag & drop plugin makes it significantly easier to manage your website. WP Forms. Very simple form builder. Akismet Spam Protection. Probably the most popular anti-spam WP plugin. Mammoth Docx. A plugin that uploads your content from a Google doc directly to WordPress. SEO Tip #16. No, Voice Search Is Still Not Relevant Voice search is not and will not be relevant (no matter what sensationalist articles might say). Sure, it does have its application (“Alexa, order me toilet paper please”), but it’s pretty niche and not relevant to most SEOs. After all, you wouldn’t use voice search for bigger purchases (“Alexa, order me a new laptop please”) or informational queries (“Alexa, teach me how to do accounting, thanks”). SEO Tip #17. SEO Is Obviously Not Dead I see these articles every year - “SEO is dead because I failed to make it work.” SEO is not dead and as long as there are people looking up for information/things online, it never will be. And no, SEO is not just for large corporations with huge budgets, either. Some niches are hypercompetitive and require a huge link-building budget (CBD, fitness, VPN, etc.), but they’re more of an exception instead of the rule. SEO Tip #18. Doing Local SEO? Focus on Service Pages If you’re doing local SEO, you’re better off focusing on local service pages than blog 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. Or alternatively, if you’re a personal injury law firm, you’d want to create pages like /car-accident-law-firm/, /truck-accident-law-firm/, /wrongful-death-law-firm/, and the like. 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. SEO Tip #19. Engage With the SEO Community The SEO community is (for the most part) composed of extremely helpful and friendly people. There are a lot of online communities (including this sub) where you can ask for help, tips, case studies, and so on. Some of our faves are: This sub :) SEO Signals Lab (FB Group) Fat Graph Content Ops (FB Group) Proper SEO Group (FB Group) BigSEO Subreddit SEO Tip #20. Test Keywords Before Pursuing Them You can use Google ads to test how profitable any given keyword is before you start trying to rank for it. The process here is: Create a Google Ads account. Pick a keyword you want to test. Create a landing page that corresponds to the search intent behind the keyword. Allocate an appropriate budget. E.g. if you assume a conversion rate of 2%, you’d want to buy 100+ clicks. If the CPC is 2 USD, then the right budget would be 200 USD plus. Run the ads! If you don’t have the budget for this, you can still use the average CPC for the keyword to estimate how well it’s going to convert. If someone is willing to bid 10 USD to rank for a certain keyword, it means that the keyword is most probably generating pretty good revenue/conversions. SEO Tip #21. Test & Improve SEO Headlines Sometimes, you’ll see that you’re ranking in the top 3 positions for your search query, but you’re still not driving that much traffic. “What’s the deal?” you might be asking. Chances are, your headline is not clickable enough. Every 3-4 months, go through your Google Search Console and check for articles that are ranking well but not driving enough traffic. Then, create a Google sheet and include the following data: Targeted keyword Page link CTR (for the last 28 days) Date when you implemented the new title Old title New title New CTR (for the month after the CTR change was implemented) From then on, implement the new headline and track changes in the CTR. If you don’t reach your desired result, you can always test another headline. SEO Tip #22. Longer Content Isn’t Always Better Content You’ve probably heard that long-form content is where it’s at in 2021. Well, this isn’t always the case. Rather, this mostly depends on the keyword you’re targeting. If, for example, you’re targeting the keyword “how to tie a tie,” you don’t need a long-ass 5,000-word mega-guide. In such a case, the reader is looking for something that can be explained in 200-300 words and if your article fails to do this, the reader will bounce off and open a different page. On the other hand, if you’re targeting the keyword “how to write a CV,” you’ll need around 4,000 to 5,000 words to adequately explain the topic and, chances are, you won’t rank with less. SEO Tip #23. SEO is Not All About Written Content More often than not, when people talk about SEO they talk about written blog content creation. It’s very important not to forget, though, that blog content is not end-all-be-all for SEO. Certain keywords do significantly better with video content. For example, if the keyword is “how to do a deadlift,” video content is going to perform significantly better than blog content. Or, if the keyword is “CV template,” you’ll see that a big chunk of the rankings are images of the templates. So, the lesson here is, don’t laser-focus on written content—keep other content mediums in mind, too. SEO Tip #24. Write For Your Audience It’s very important that your content resonates well with your target audience. If, for example, you’re covering the keyword “skateboard tricks,” you can be very casual with your language. Heck, it’s even encouraged! Your readers are Googling the keyword in their free time and are most likely teens or in their early 20s. Meaning, you can use informal language, include pop culture references, and avoid complicated language. Now, on the other hand, if you’re writing about high-level investment advice, your audience probably consists of 40-something suit-and-ties. If you include Rick & Morty references in your article, you'll most likely lose credibility and the Googler, who will go to another website. Some of our best tips on writing for your audience include: Define your audience. Who’s the person you’re writing for? Are they reading the content at work or in their free time? Keep your reader’s level of knowledge in mind. If you’re covering an accounting 101 topic, you want to cover the topic’s basics, as the reader is probably a student. If you’re writing about high-level finance, though, you don’t have to teach the reader what a balance sheet is. More often than not, avoid complicated language. The best practice is to write on a 6th-grade level, as it’s understandable for anyone. Plus, no one wants to read Shakespeare when Googling info online (unless they’re looking for Shakespeare's work, of course). SEO Tip #25. Create Compelling Headlines Want to drive clicks to your articles? You’ll need compelling headlines. Compare the following headline: 101 Productivity Tips \[To Get Things Done in 2021\] With this one: Productivity Tips Guide Which one would you click? Data says it’s the first! To create clickable headlines, I recommend you include the following elements: Keyword. This one’s non-negotiable - you need to include the target keyword in the headline. Numbers. If Buzzfeed taught us anything, it’s that people like to click articles with numbers in their titles. Results. If I read your article, what’s going to be the end result? E.g. “X Resume tips (to land the job)”.* Year (If Relevant). Adding a year to your title shows that the article is recent (which is relevant for some specific topics). E.g. If the keyword is “Marketing Trends,” I want to know marketing trends in 2021, not in 2001. So, adding a year in the title makes the headline more clickable. SEO Tip #26. Make Your Content Visual How good your content looks matters, especially if you're in a competitive niche. Here are some tips on how to make your content as visual as possible: Aim for 2-4 sentences per paragraph. Avoid huge blocks of text. Apply a 60-65% content width to your blog pages. Pick a good-looking font. I’d recommend Montserrat, PT Sans, and Roboto. Alternatively, you can also check out your favorite blogs, see which fonts they’re using, and do the same. Use a reasonable font size. Most top blogs use font sizes ranging from 16 pt to 22 pt. Add images when possible. Avoid stock photos, though. No one wants to see random “office people smiling” scattered around your blog posts. Use content boxes to help convey information better. Content boxes example in the URL in the intro of the post. SEO Tip #27. Ditch the Skyscraper Technique Already Brian Dean’s skyscraper technique is awesome and all, but the following bit really got old: “Hey \[name\], I saw you wrote an article. I, too, wrote an article. Please link to you?” The theory here is, if your content is good, the person will be compelled to link to it. In practice, though, the person really, really doesn’t care. At the end of the day, there’s no real incentive for the person to link to your content. They have to take time out of their day to head over to their website, log in to WordPress, find the article you mentioned, and add a link... Just because some stranger on the internet asked them to. Here’s something that works much better: Instead of fake compliments, be very straightforward about what you can offer them in exchange for that link. Some things you can offer are: A free version of your SaaS. Free product delivered to their doorstep. Backlink exchange. A free backlink from your other website. Sharing their content to your social media following. Money. SEO Tip #28. Get the URL Slug Right for Seasonal Content If you want to rank on a seasonal keyword, there are 2 ways to do this. If you want your article to be evergreen (i.e. you update it every year with new information), then your URL should not contain the year. E.g. your URL would be /saas-trends/, and you simply update the article’s contents+headline each year to keep it timely. If you’re planning on publishing a new trends report annually, though, then you can add a year to the URL. E.g. /saas-trends-2020/ instead of /saas-trends/. SEO Tip #29. AI Content Tools Are a Mixed Bag Lots of people are talking about AI content tools these days. Usually, they’re either saying: “AI content tools are garbage and the output is horrible,” Or: “AI content tools are a game-changer!” So which one is it? The truth is somewhere in-between. In 2021, AI content writing tools are pretty bad. The output you’re going to get is far from something you can publish on your website. That said, some SEOs use such tools to get a very, very rough draft of the article written, and then they do intense surgery on it to make it usable. Should you use AI content writing tools? If you ask me, no - it’s easier to hire a proficient content writer than spend hours salvaging AI-written content. That said, I do believe that such tools are going to get much better years down the line. This one was, clearly, more of a personal opinion than a fact. I’d love to hear YOUR opinion on AI content tools! Are they a fad, or are they the future of content creation? Let me know in the comments. SEO Tip #30. Don’t Overdo it With SEO Tools There are a lot of SEO tools out there for pretty much any SEO function. Keyword research, link-building, on-page, outreach, technical SEO, you name it! If you were to buy most of these tools for your business, you’d easily spend 4-figures on SEO tools per month. Luckily, though, you don’t actually need most of them. At the end of the day, the only must-have SEO tools are: An SEO Suite (Paid). Basically SEMrush or Ahrefs. Both of these tools offer an insane number of features - backlink analysis, keyword research, and a ton of other stuff. Yes, 99 USD a month is expensive for a tool. But then again, if you value your time 20 USD/hour and this tool saves you 6 hours, it's obviously worth it, right? On-Page SEO Tool (Free). RankMath or Yoast. Basically, a tool that's going to help you optimize web pages or blog posts as per SEO best practices. Technical SEO Tool (Freemium). You can use ScreamingFrog to crawl your entire website and find technical SEO problems. There are probably other tools that also do this, but ScreamingFrog is the most popular option. The freemium version of the tool only crawls a limited number of pages (500 URLs, to be exact), so if your website is relatively big, you'll need to pay for the tool. Analytics (Free). Obviously, you'll need Google Analytics (to track website traffic) and Google Search Console (to track organic traffic, specifically) set up on your website. Optionally, you can also use Google Track Manager to better track how your website visitors interact with the site. MozBar (Free). Chrome toolbar that lets you simply track the number of backlinks on Google Search Queries, Domain Authority, and a bunch of other stuff. Website Speed Analysis (Free). You can use Google Page Speed Insights to track how fast your website loads, as well as how mobile-friendly it is. Outreach Tool (Paid). Tool for reaching out to prospects for link-building, guest posting, etc. There are about a dozen good options for this. Personally, I like to use Snov for this. Optimized GMB Profile (Free). Not a tool per se, but if you're a local business, you need to have a well-optimized Google My Business profile. Google Keyword Planner (Free). This gives you the most reliable search volume data of all the tools. So, when doing keyword research, grab the search volume from here. Tool for Storing Keyword Research (Free). You can use Google Sheets or AirTable to store your keyword research and, at the same time, use it as a content calendar. Hemingway App (Free). Helps keep your SEO content easy to read. Spots passive voice, complicated words, etc. Email Finder (Freemium). You can use a tool like Hunter to find the email address of basically anyone on the internet (for link-building or guest posting purposes). Most of the tools that don’t fit into these categories are 100% optional. SEO Tip #31. Hiring an SEO? Here’s How to Vet Them Unless you’re an SEO pro yourself, hiring one is going to be far from easy. There’s a reason there are so many “SEO experts” out there - for the layman, it’s very hard to differentiate between someone who knows their salt and a newbie who took an SEO course, like, last week. Here’s how you can vet both freelance and full-time SEOs: Ask for concrete traffic numbers. The SEO pro should give you the exact numbers on how they’ve grown a website in the past - “100% SEO growth in 1 year” doesn’t mean much if the growth is from 10 monthly traffic to 20. “1,000 to 30,000” traffic, on the other hand, is much better. Ask for client names. While some clients ask their SEOs to sign an NDA and not disclose their collaboration, most don’t. If an SEO can’t name a single client they’ve worked with in the past, that’s a red flag. Make sure they have the right experience. Global and local SEO have very different processes. Make sure that the SEO has experience with the type of SEO you need. Make sure you’re looking for the right candidate. SEO pros can be content writers, link-builders, web developers, or all of the above simultaneously. Make sure you understand which one you need before making the hire. If you’re looking for someone to oversee your content ops, you shouldn’t hire a technical SEO expert. Look for SEO pros in the right places. Conventional job boards are overrated. Post your job ads on SEO communities instead. E.g. this sub, bigseo, SEO Signals Facebook group, etc. SEO Tip #32. Blog Post Not Ranking? Follow This Checklist I wanted to format the post natively for Reddit, but it’s just SO much better on Notion. Tl;dr, the checklist covers every reason your post might not be ranking: Search intent mismatch. Inferior content. Lack of internal linking. Lack of backlinks. And the like. Checklist URL at the intro of the post. SEO Tip #33. Avoid BS Link-Building Tactics The only type of link-building that works is building proper, quality links from websites with a good backlink profile and decent organic traffic. Here’s what DOESN’T work: Blog comment links Forum spam links Drive-by Reddit comment/post links Web 2.0 links Fiverr “100 links for 10 bucks” bs If your “SEO agency” says they’re doing any of the above instead of actually trying to build you links from quality websites, you’re being scammed. SEO Tip #34. Know When to Use 301 and 302 Redirects When doing redirects, it’s very important to know the distinction between these two. 301 is a permanent page redirect and passes on link juice. If you’re killing off a page that has backlinks, it’s better to 301 it to your homepage so that you don’t lose the link juice. If you simply delete a page, it’s going to be a 404, and the backlink juice is lost forever. 302 is a temporary page redirect and doesn’t pass on link juice. If the redirect is temporary, you do a 302. E.g. you want to test how well a new page is going to perform w/ your audience. SEO Tip #35. Social Signals Matter (But Not How You Think) Social signals are NOT a ranking factor. And yet, they can help your content rank on Google’s front page. Wondering what the hell am I talking about? Here’s what’s up: As I said, social signals are not a ranking factor. It’s not something Google takes into consideration to decide whether your article should rank or not. That said, social signals CAN lead to your article ranking better. Let’s say your article goes viral and gets around 20k views within a week. A chunk of these viewers are going to forget your domain/link and they’re going to look up the topic on Google via your chosen keyword + your brand name. The amount of people looking for YOUR keyword and exclusively picking your result over others is going to make Google think that your content is satisfying search intent better than the rest, and thus, reward you with better ranking. SEO Tip #36. Run Remarketing Ads to Lift Organic Traffic Conversions Not satisfied with your conversion rates? You can use Facebook ads to help increase them. Facebook allows you to do something called “remarketing.” This means you can target anyone that visited a certain page (or multiple pages) on your website and serve them ads on Facebook. There are a TON of ways you can take advantage of this. For example, you can target anyone that landed on a high buyer intent page and serve them ads pitching your product or a special offer. Alternatively, you can target people who landed on an educational blog post and offer them something to drive them down the funnel. E.g. free e-book or white paper to teach them more about your product or service. SEO Tip #37. Doing Local SEO? Follow These Tips Local SEO is significantly different from global SEO. Here’s how the two differ (and what you need to do to drive local SEO results): You don’t need to publish content. For 95% of local businesses, you only want to rank for keywords related to your services/products, you don’t actually need to create educational content. You need to focus more on reviews and citation-building. One of Google Maps’ biggest ranking factors is the of reviews your business has. Encourage your customers to leave a review if they enjoyed your product/service through email or real-life communication. You need to create service pages for each location. As a local business, your #1 priority is to rank for keywords around your service. E.g. If you're a personal injury law firm, you want to optimize your homepage for “personal injury law firm” and then create separate pages for each service you provide, e.g. “car accident lawyer,” “motorcycle injury law firm,” etc. Focus on building citations. Being listed on business directories makes your business more trustworthy for Google. BrightLocal is a good service for this. You don’t need to focus as much on link-building. As local SEO is less competitive than global, you don’t have to focus nearly as much on building links. You can, in a lot of cases, rank with the right service pages and citations. SEO Tip #38. Stop Ignoring the Outreach Emails You’re Getting (And Use Them to Build Your Own Links) Got a ton of people emailing you asking for links? You might be tempted to just send them all straight to spam, and I don’t blame you. Outreach messages like “Hey Dr Jigsaw, your article is A+++ amazing! ...can I get a backlink?” can get hella annoying. That said, there IS a better way to deal with these emails: Reply and ask for a link back. Most of the time, people who send such outreach emails are also doing heavy guest posting. So, you can ask for a backlink from a 3rd-party website in exchange for you mentioning their link in your article. Win-win! SEO Tip #39. Doing Internal Linking for a Large Website? This’ll Help Internal linking can get super grueling once you have hundreds of articles on your website. Want to make the process easier? Do this: Pick an article you want to interlink on your website. For the sake of the example, let’s say it’s about “business process improvement.” Go on Google and look up variations of this keyword mentioned on your website. For example: Site:\[yourwebsite\] “improve business process” Site:\[yourwebsite\] “improve process” Site:\[yourwebsite\] “process improvement” The above queries will find you the EXACT articles where these keywords are mentioned. Then, all you have to do is go through them and include the links. SEO Tip #40. Got a Competitor Copying Your Content? File a DMCA Notice Fun fact - if your competitors are copying your website, you can file a DMCA notice with Google. That said, keep in mind that there are consequences for filing a fake notice.

I run an AI automation agency (AAA). My honest overview and review of this new business model
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Scout_OfficialThis week

I run an AI automation agency (AAA). My honest overview and review of this new business model

I started an AI tools directory in February, and then branched off that to start an AI automation agency (AAA) in June. So far I've come across a lot of unsustainable "ideas" to make money with AI, but at the same time a few diamonds in the rough that aren't fully tapped into yet- especially the AAA model. Thought I'd share this post to shine light into this new business model and share some ways you could potentially start your own agency, or at the very least know who you are dealing with and how to pick and choose when you (inevitably) get bombarded with cold emails from them down the line. Foreword Running an AAA does NOT involve using AI tools directly to generate and sell content directly. That ship has sailed, and unless you are happy with $5 from Fiverr every month or so, it is not a real business model. Cry me a river but generating generic art with AI and slapping it onto a T-shirt to sell on Etsy won't make you a dime. At the same time, the AAA model will NOT require you to have a deep theoretical knowledge of AI, or any academic degree, as we are more so dealing with the practical applications of generative AI and how we can implement these into different workflows and tech-stacks, rather than building AI models from the ground up. Regardless of all that, common sense and a willingness to learn will help (a shit ton), as with anything. Keep in mind - this WILL involve work and motivation as well. The mindset that AI somehow means everything can be done for you on autopilot is not the right way to approach things. The common theme of businesses I've seen who have successfully implemented AI into their operations is the willingess to work with AI in a way that augments their existing operations, rather than flat out replace a worker or team. And this is exactly the train of thought you need when working with AI as a business model. However, as the field is relatively unsaturated and hype surrounding AI is still fresh for enterprises, right now is the prime time to start something new if generative AI interests you at all. With that being said, I'll be going over three of the most successful AI-adjacent businesses I've seen over this past year, in addition to some tips and resources to point you in the right direction. so.. WTF is an AI Automation Agency? The AI automation agency (or as some YouTubers have coined it, the AAA model) at its core involves creating custom AI solutions for businesses. I have over 1500 AI tools listed in my directory, however the feedback I've received from some enterprise users is that ready-made SaaS tools are too generic to meet their specific needs. Combine this with the fact virtually no smaller companies have the time or skills required to develop custom solutions right off the bat, and you have yourself real demand. I would say in practice, the AAA model is quite similar to Wordpress and even web dev agencies, with the major difference being all solutions you develop will incorporate key aspects of AI AND automation. Which brings me to my second point- JUST AI IS NOT ENOUGH. Rather than reducing the amount of time required to complete certain tasks, I've seen many AI agencies make the mistake of recommending and (trying to) sell solutions that more likely than not increase the workload of their clients. For example, if you were to make an internal tool that has AI answer questions based on their knowledge base, but this knowledge base has to be updated manually, this is creating unnecessary work. As such I think one of the key components of building successful AI solutions is incorporating the new (Generative AI/LLMs) with the old (programmtic automation- think Zapier, APIs, etc.). Finally, for this business model to be successful, ideally you should target a niche in which you have already worked and understand pain points and needs. Not only does this make it much easier to get calls booked with prospects, the solutions you build will have much greater value to your clients (meaning you get paid more). A mistake I've seen many AAA operators make (and I blame this on the "Get Rich Quick" YouTubers) is focusing too much on a specific productized service, rather than really understanding the needs of businesses. The former is much done via a SaaS model, but when going the agency route the only thing that makes sense is building custom solutions. This is why I always take a consultant-first approach. You can only build once you understand what they actually need and how certain solutions may impact their operations, workflows, and bottom-line. Basics of How to Get Started Pick a niche. As I mentioned previously, preferably one that you've worked in before. Niches I know of that are actively being bombarded with cold emails include real estate, e-commerce, auto-dealerships, lawyers, and medical offices. There is a reason for this, but I will tell you straight up this business model works well if you target any white-collar service business (internal tools approach) or high volume businesses (customer facing tools approach). Setup your toolbox. If you wanted to start a pressure washing business, you would need a pressure-washer. This is no different. For those without programming knowledge, I've seen two common ways AAA get setup to build- one is having a network of on-call web developers, whether its personal contacts or simply going to Upwork or any talent sourcing agency. The second is having an arsenal of no-code tools. I'll get to this more in a second, but this works beecause at its core, when we are dealing with the practical applications of AI, the code is quite simple, simply put. Start cold sales. Unless you have a network already, this is not a step you can skip. You've already picked a niche, so all you have to do is find the right message. Keep cold emails short, sweet, but enticing- and it will help a lot if you did step 1 correctly and intimately understand who your audience is. I'll be touching base later about how you can leverage AI yourself to help you with outreach and closing. The beauty of gen AI and the AAA model You don't need to be a seasoned web developer to make this business model work. The large majority of solutions that SME clients want is best done using an API for an LLM for the actual AI aspect. The value we create with the solutions we build comes with the conceptual framework and design that not only does what they need it to but integrates smoothly with their existing tech-stack and workflow. The actual implementation is quite straightforward once you understand the high level design and know which tools you are going to use. To give you a sense, even if you plan to build out these apps yourself (say in Python) the large majority of the nitty gritty technical work has already been done for you, especially if you leverage Python libraries and packages that offer high level abstraction for LLM-related functions. For instance, calling GPT can be as little as a single line of code. (And there are no-code tools where these functions are simply an icon on a GUI). Aside from understanding the capabilities and limitations of these tools and frameworks, the only thing that matters is being able to put them in a way that makes sense for what you want to build. Which is why outsourcing and no-code tools both work in our case. Okay... but how TF am I suppposed to actually build out these solutions? Now the fun part. I highly recommend getting familiar with Langchain and LlamaIndex. Both are Python libraires that help a lot with the high-level LLM abstraction I mentioned previously. The two most important aspects include being able to integrate internal data sources/knowledge bases with LLMs, and have LLMs perform autonomous actions. The two most common methods respectively are RAG and output parsing. RAG (retrieval augmented Generation) If you've ever seen a tool that seemingly "trains" GPT on your own data, and wonder how it all works- well I have an answer from you. At a high level, the user query is first being fed to what's called a vector database to run vector search. Vector search basically lets you do semantic search where you are searching data based on meaning. The vector databases then retrieves the most relevant sections of text as it relates to the user query, and this text gets APPENDED to your GPT prompt to provide extra context to the AI. Further, with prompt engineering, you can limit GPT to only generate an answer if it can be found within this extra context, greatly limiting the chance of hallucination (this is where AI makes random shit up). Aside from vector databases, we can also implement RAG with other data sources and retrieval methods, for example SQL databses (via parsing the outputs of LLM's- more on this later). Autonomous Agents via Output Parsing A common need of clients has been having AI actually perform tasks, rather than simply spitting out text. For example, with autonomous agents, we can have an e-commerce chatbot do the work of a basic customer service rep (i.e. look into orders, refunds, shipping). At a high level, what's going on is that the response of the LLM is being used programmtically to determine which API to call. Keeping on with the e-commerce example, if I wanted a chatbot to check shipping status, I could have a LLM response within my app (not shown to the user) with a prompt that outputs a random hash or string, and programmatically I can determine which API call to make based on this hash/string. And using the same fundamental concept as with RAG, I can append the the API response to a final prompt that would spit out the answer for the user. How No Code Tools Can Fit In (With some example solutions you can build) With that being said, you don't necessarily need to do all of the above by coding yourself, with Python libraries or otherwise. However, I will say that having that high level overview will help IMMENSELY when it comes to using no-code tools to do the actual work for you. Regardless, here are a few common solutions you might build for clients as well as some no-code tools you can use to build them out. Ex. Solution 1: AI Chatbots for SMEs (Small and Medium Enterprises) This involves creating chatbots that handle user queries, lead gen, and so forth with AI, and will use the principles of RAG at heart. After getting the required data from your client (i.e. product catalogues, previous support tickets, FAQ, internal documentation), you upload this into your knowledge base and write a prompt that makes sense for your use case. One no-code tool that does this well is MyAskAI. The beauty of it especially for building external chatbots is the ability to quickly ingest entire websites into your knowledge base via a sitemap, and bulk uploading files. Essentially, they've covered the entire grunt work required to do this manually. Finally, you can create a inline or chat widget on your client's website with a few lines of HTML, or altneratively integrate it with a Slack/Teams chatbot (if you are going for an internal Q&A chatbot approach). Other tools you could use include Botpress and Voiceflow, however these are less for RAG and more for building out complete chatbot flows that may or may not incorporate LLMs. Both apps are essentially GUIs that eliminate the pain and tears and trying to implement complex flows manually, and both natively incoporate AI intents and a knowledge base feature. Ex. Solution 2: Internal Apps Similar to the first example, except we go beyond making just chatbots but tools such as report generation and really any sort of internal tool or automations that may incorporate LLM's. For instance, you can have a tool that automatically generates replies to inbound emails based on your client's knowledge base. Or an automation that does the same thing but for replies to Instagram comments. Another example could be a tool that generates a description and screeenshot based on a URL (useful for directory sites, made one for my own :P). Getting into more advanced implementations of LLMs, we can have tools that can generate entire drafts of reports (think 80+ pages), based not only on data from a knowledge base but also the writing style, format, and author voice of previous reports. One good tool to create content generation panels for your clients would be MindStudio. You can train LLM's via prompt engineering in a structured way with your own data to essentially fine tune them for whatever text you need it to generate. Furthermore, it has a GUI where you can dictate the entire AI flow. You can also upload data sources via multiple formats, including PDF, CSV, and Docx. For automations that require interactions between multiple apps, I recommend the OG zapier/make.com if you want a no-code solution. For instance, for the automatic email reply generator, I can have a trigger such that when an email is received, a custom AI reply is generated by MyAskAI, and finally a draft is created in my email client. Or, for an automation where I can create a social media posts on multiple platforms based on a RSS feed (news feed), I can implement this directly in Zapier with their native GPT action (see screenshot) As for more complex LLM flows that may require multiple layers of LLMs, data sources, and APIs working together to generate a single response i.e. a long form 100 page report, I would recommend tools such as Stack AI or Flowise (open-source alternative) to build these solutions out. Essentially, you get most of the functions and features of Python packages such as Langchain and LlamaIndex in a GUI. See screenshot for an example of a flow How the hell are you supposed to find clients? With all that being said, none of this matters if you can't find anyone to sell to. You will have to do cold sales, one way or the other, especially if you are brand new to the game. And what better way to sell your AI services than with AI itself? If we want to integrate AI into the cold outreach process, first we must identify what it's good at doing, and that's obviously writing a bunch of text, in a short amount of time. Similar to the solutions that an AAA can build for its clients, we can take advantage of the same principles in our own sales processes. How to do outreach Once you've identified your niche and their pain points/opportunities for automation, you want to craft a compelling message in which you can send via cold email and cold calls to get prospects booked on demos/consultations. I won't get into too much detail in terms of exactly how to write emails or calling scripts, as there are millions of resources to help with this, but I will tell you a few key points you want to keep in mind when doing outreach for your AAA. First, you want to keep in mind that many businesses are still hesitant about AI and may not understand what it really is or how it can benefit their operations. However, we can take advantage of how mass media has been reporting on AI this past year- at the very least people are AWARE that sooner or later they may have to implement AI into their businesses to stay competitive. We want to frame our message in a way that introduces generative AI as a technology that can have a direct, tangible, and positive impact on their business. Although it may be hard to quantify, I like to include estimates of man-hours saved or costs saved at least in my final proposals to prospects. Times are TOUGH right now, and money is expensive, so you need to have a compelling reason for businesses to get on board. Once you've gotten your messaging down, you will want to create a list of prospects to contact. Tools you can use to find prospects include Apollo.io, reply.io, zoominfo (expensive af), and Linkedin Sales Navigator. What specific job titles, etc. to target will depend on your niche but for smaller companies this will tend to be the owner. For white collar niches, i.e. law, the professional that will be directly benefiting from the tool (i.e. partners) may be better to contact. And for larger organizations you may want to target business improvement and digital transformation leads/directors- these are the people directly in charge of projects like what you may be proposing. Okay- so you have your message, and your list, and now all it comes down to is getting the good word out. I won't be going into the details of how to send these out, a quick Google search will give you hundreds of resources for cold outreach methods. However, personalization is key and beyond simple dynamic variables you want to make sure you can either personalize your email campaigns directly with AI (SmartWriter.ai is an example of a tool that can do this), or at the very least have the ability to import email messages programmatically. Alternatively, ask ChatGPT to make you a Python Script that can take in a list of emails, scrape info based on their linkedin URL or website, and all pass this onto a GPT prompt that specifies your messaging to generate an email. From there, send away. How tf do I close? Once you've got some prospects booked in on your meetings, you will need to close deals with them to turn them into clients. Call #1: Consultation Tying back to when I mentioned you want to take a consultant-first appraoch, you will want to listen closely to their goals and needs and understand their pain points. This would be the first call, and typically I would provide a high level overview of different solutions we could build to tacke these. It really helps to have a presentation available, so you can graphically demonstrate key points and key technologies. I like to use Plus AI for this, it's basically a Google Slides add-on that can generate slide decks for you. I copy and paste my default company messaging, add some key points for the presentation, and it comes out with pretty decent slides. Call #2: Demo The second call would involve a demo of one of these solutions, and typically I'll quickly prototype it with boilerplate code I already have, otherwise I'll cook something up in a no-code tool. If you have a niche where one type of solution is commonly demanded, it helps to have a general demo set up to be able to handle a larger volume of calls, so you aren't burning yourself out. I'll also elaborate on how the final product would look like in comparison to the demo. Call #3 and Beyond: Once the initial consultation and demo is complete, you will want to alleviate any remaining concerns from your prospects and work with them to reach a final work proposal. It's crucial you lay out exactly what you will be building (in writing) and ensure the prospect understands this. Furthermore, be clear and transparent with timelines and communication methods for the project. In terms of pricing, you want to take this from a value-based approach. The same solution may be worth a lot more to client A than client B. Furthermore, you can create "add-ons" such as monthly maintenance/upgrade packages, training sessions for employeees, and so forth, separate from the initial setup fee you would charge. How you can incorporate AI into marketing your businesses Beyond cold sales, I highly recommend creating a funnel to capture warm leads. For instance, I do this currently with my AI tools directory, which links directly to my AI agency and has consistent branding throughout. Warm leads are much more likely to close (and honestly, much nicer to deal with). However, even without an AI-related website, at the very least you will want to create a presence on social media and the web in general. As with any agency, you will want basic a professional presence. A professional virtual address helps, in addition to a Google Business Profile (GBP) and TrustPilot. a GBP (especially for local SEO) and Trustpilot page also helps improve the looks of your search results immensely. For GBP, I recommend using ProfilePro, which is a chrome extension you can use to automate SEO work for your GBP. Aside from SEO optimzied business descriptions based on your business, it can handle Q/A answers, responses, updates, and service descriptions based on local keywords. Privacy and Legal Concerns of the AAA Model Aside from typical concerns for agencies relating to service contracts, there are a few issues (especially when using no-code tools) that will need to be addressed to run a successful AAA. Most of these surround privacy concerns when working with proprietary data. In your terms with your client, you will want to clearly define hosting providers and any third party tools you will be using to build their solution, and a DPA with these third parties listed as subprocessors if necessary. In addition, you will want to implement best practices like redacting private information from data being used for building solutions. In terms of addressing concerns directly from clients, it helps if you host your solutions on their own servers (not possible with AI tools), and address the fact only ChatGPT queries in the web app, not OpenAI API calls, will be used to train OpenAI's models (as reported by mainstream media). The key here is to be open and transparent with your clients about ALL the tools you are using, where there data will be going, and make sure to get this all in writing. have fun, and keep an open mind Before I finish this post, I just want to reiterate the fact that this is NOT an easy way to make money. Running an AI agency will require hours and hours of dedication and work, and constantly rearranging your schedule to meet prospect and client needs. However, if you are looking for a new business to run, and have a knack for understanding business operations and are genuinely interested in the pracitcal applications of generative AI, then I say go for it. The time is ticking before AAA becomes the new dropshipping or SMMA, and I've a firm believer that those who set foot first and establish themselves in this field will come out top. And remember, while 100 thousand people may read this post, only 2 may actually take initiative and start.

Seeking co-founder to build LinkedIn’s biggest rival(curated version)
reddit
LLM Vibe Score0
Human Vibe Score1
ItzdreeThis week

Seeking co-founder to build LinkedIn’s biggest rival(curated version)

How do you connect with likeminded people? You see the polished wins everywhere, but what about the messy drafts , the awkward pitches and the moments you’re not sure you’ve got it right? Problem: The whole idea of founding and starting a business can be super intimidating for some people, specially those who don’t know any founders personally, those who don’t have a large network, those who don’t have rich parents with large networks, those not inserted in an entrepreneurial culture like in the US for example (which is my case). Sometimes all you need is the right support network, and too see others do what you want, to know that it’s possible! Everyone has an “ultimate guide” to make 7 figures or build a business on YouTube but NO ONE shoes you the HOW, just the results… I’ve tried joining founder communities, LinkedIn ,Reddit … you name it. Most of these founder communities are inaccessible for regular people and often ask for you to have an already existing business with a min ARR… or their simply geography based and if you’re not in a certain area you can’t really participate… As of LinkedIn… full of empty AI generated posts about how some random dude raised $10m in 7 days. Okay Jonathan, but what about the HOW?? How did you write your first pitch? How many rejection calls did you get? What is an MVP? There simply isn’t a platform out there to document your founding journey and find inspiration within a community of people who are doing the same as you. What better way to feel motivated then to see someone actually document their process? Solution: I’m working on building a social media platform for aspiring/founders to connect through the RAW, UNFILTERED process of turning ideas into reality in REAL time. It’s all gonna be around the “building in public “ concept and content creation. Picture an instagram/tiktok profile where instead of seeing someone’s dog you see them documenting their founding process—from the moment they had the idea, to the moment they launched, you’re going to see the successes, the fails, the rejected calls, all documented through actual content and not some AI generated LinkedIn post. Imagine if you wanted to learn about how Steve Jobs started Apple , you could simply go through his profile on this app—exactly. To make sure all interactions are meaningful people would have to apply. It’s a truly curated community, with REAL people, building REAL things in REAL time, and not just tell us the story of how they did it… Audience: I’m targeting people who have a burning desire of building a business and early stage founders starting their founder journeys, that don’t have a support network and simply don’t know where to start. People who are tired of watching 30 min “ultimate guides “ on how to make it on YouTube from “business gurus” selling courses. People who haven’t reached the min ARR required to join an “exclusive “ founder a community. People who can’t simply just move to the US to get into the “exclusive” YC combinator. People who want to connect with real people building real things and not anonymous people on Reddit, or LinkedIn influencers again trying to promote their services. I believe in the idea because I’m also part of my audience. Have always wanted to start my own thing just never knew how to and where to find a community of likeminded people . I don’t know any founders myself, I come from a non-entrepreneurial society and I’d pay good money to access a community of REAL passionate founders building REAL things, in REAL time. This would be my first ever business, and I want to share my journey building it and hopefully inspire others to just start so I’ve created a mailing list to keep anyone interested in the project updated on my fails , learnings and successes. I’m not worried about “making it” but just “starting” and hopefully reach the right audience and inspire anyone to start whatever they have marinating in their thoughts. If you’re a founder struggling with staying consistent or an aspiring founder with an insane desire of starting and don’t know how to start, I’d love to get your feedback on what’s stopping you, your challenges starting out and what you’d find useful in such platform. And finally would this be something that interests you?? PS: casually looking for a technical co-founder

101 best SEO tips to help you drive traffic in 2k21
reddit
LLM Vibe Score0
Human Vibe Score0.543
DrJigsawThis 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.

I Quit My Tech Job 6 Months Ago. Built 10+ Products. Made $0. Here's Everything I Learned.
reddit
LLM Vibe Score0
Human Vibe Score1
WaynedevvvThis week

I Quit My Tech Job 6 Months Ago. Built 10+ Products. Made $0. Here's Everything I Learned.

I quit my tech job 6 months ago to go full indie. Had enough savings and didn't want to miss the AI wave. Since then, I've built 10+ products - B2C, B2B, mobile apps, directories, marketplaces, you name it. But I keep repeating the same cycle: have an idea, dream big, build for weeks, "launch" (and by launch, I mean just deploy and go live with zero promotion), then get bored and lose motivation to market it. Then I start looking for new ideas to build. Is it just me, or does anyone else face something similar? Maybe coding is my comfort zone and marketing isn't, that's why... I knew entrepreneurship was hard, but it's MUCH harder than I thought. After these failures, here's everything I've learned: Lessons Learned The Hard Way Don't build something you don't have passion for. Pushing a product is hard and takes tremendous effort. If you don't have passion for it, you won't push through the initial "no interest" zone. Think carefully: would you be proud of what you build after building it? If yes, proceed. If not, don't waste time. Build your audience/network first. This isn't new advice, but it's 100% key for entrepreneurs to succeed. I'm still figuring this out, but one thing is clear: "Value" is the key. Stop posting random stuff and instead give value. People don't care about you and your life, but they do care about what you can offer them. Don't rush. Entrepreneurship isn't a sprint; it's a marathon. Don't rush to build stuff. Take a step back to think, plan, and learn. Coding for 16 hours a day won't do you any good - you'll end up building something people don't want. What I'm Doing Differently Next Time After all these failures, I finally took time with myself to think about how I can approach things differently. Here's my new plan: I will not start a new project if I know I'll ditch it after building it. I will follow best practices: validate the idea, research competitors, look for beta users, and ship fast. I will start building my audience and personal brand through documenting the journey. I've already decided what I'm building next, and yes, this time I'm going all in. I'll apply everything I've learned so far, and hopefully, this time will be different. Will update you all soon. Keep shipping, folks! Hopefully we'll see your "I reached 10k MRR for my SaaS" post soon.

I run an AI automation agency (AAA). My honest overview and review of this new business model
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Scout_OfficialThis week

I run an AI automation agency (AAA). My honest overview and review of this new business model

I started an AI tools directory in February, and then branched off that to start an AI automation agency (AAA) in June. So far I've come across a lot of unsustainable "ideas" to make money with AI, but at the same time a few diamonds in the rough that aren't fully tapped into yet- especially the AAA model. Thought I'd share this post to shine light into this new business model and share some ways you could potentially start your own agency, or at the very least know who you are dealing with and how to pick and choose when you (inevitably) get bombarded with cold emails from them down the line. Foreword Running an AAA does NOT involve using AI tools directly to generate and sell content directly. That ship has sailed, and unless you are happy with $5 from Fiverr every month or so, it is not a real business model. Cry me a river but generating generic art with AI and slapping it onto a T-shirt to sell on Etsy won't make you a dime. At the same time, the AAA model will NOT require you to have a deep theoretical knowledge of AI, or any academic degree, as we are more so dealing with the practical applications of generative AI and how we can implement these into different workflows and tech-stacks, rather than building AI models from the ground up. Regardless of all that, common sense and a willingness to learn will help (a shit ton), as with anything. Keep in mind - this WILL involve work and motivation as well. The mindset that AI somehow means everything can be done for you on autopilot is not the right way to approach things. The common theme of businesses I've seen who have successfully implemented AI into their operations is the willingess to work with AI in a way that augments their existing operations, rather than flat out replace a worker or team. And this is exactly the train of thought you need when working with AI as a business model. However, as the field is relatively unsaturated and hype surrounding AI is still fresh for enterprises, right now is the prime time to start something new if generative AI interests you at all. With that being said, I'll be going over three of the most successful AI-adjacent businesses I've seen over this past year, in addition to some tips and resources to point you in the right direction. so.. WTF is an AI Automation Agency? The AI automation agency (or as some YouTubers have coined it, the AAA model) at its core involves creating custom AI solutions for businesses. I have over 1500 AI tools listed in my directory, however the feedback I've received from some enterprise users is that ready-made SaaS tools are too generic to meet their specific needs. Combine this with the fact virtually no smaller companies have the time or skills required to develop custom solutions right off the bat, and you have yourself real demand. I would say in practice, the AAA model is quite similar to Wordpress and even web dev agencies, with the major difference being all solutions you develop will incorporate key aspects of AI AND automation. Which brings me to my second point- JUST AI IS NOT ENOUGH. Rather than reducing the amount of time required to complete certain tasks, I've seen many AI agencies make the mistake of recommending and (trying to) sell solutions that more likely than not increase the workload of their clients. For example, if you were to make an internal tool that has AI answer questions based on their knowledge base, but this knowledge base has to be updated manually, this is creating unnecessary work. As such I think one of the key components of building successful AI solutions is incorporating the new (Generative AI/LLMs) with the old (programmtic automation- think Zapier, APIs, etc.). Finally, for this business model to be successful, ideally you should target a niche in which you have already worked and understand pain points and needs. Not only does this make it much easier to get calls booked with prospects, the solutions you build will have much greater value to your clients (meaning you get paid more). A mistake I've seen many AAA operators make (and I blame this on the "Get Rich Quick" YouTubers) is focusing too much on a specific productized service, rather than really understanding the needs of businesses. The former is much done via a SaaS model, but when going the agency route the only thing that makes sense is building custom solutions. This is why I always take a consultant-first approach. You can only build once you understand what they actually need and how certain solutions may impact their operations, workflows, and bottom-line. Basics of How to Get Started Pick a niche. As I mentioned previously, preferably one that you've worked in before. Niches I know of that are actively being bombarded with cold emails include real estate, e-commerce, auto-dealerships, lawyers, and medical offices. There is a reason for this, but I will tell you straight up this business model works well if you target any white-collar service business (internal tools approach) or high volume businesses (customer facing tools approach). Setup your toolbox. If you wanted to start a pressure washing business, you would need a pressure-washer. This is no different. For those without programming knowledge, I've seen two common ways AAA get setup to build- one is having a network of on-call web developers, whether its personal contacts or simply going to Upwork or any talent sourcing agency. The second is having an arsenal of no-code tools. I'll get to this more in a second, but this works beecause at its core, when we are dealing with the practical applications of AI, the code is quite simple, simply put. Start cold sales. Unless you have a network already, this is not a step you can skip. You've already picked a niche, so all you have to do is find the right message. Keep cold emails short, sweet, but enticing- and it will help a lot if you did step 1 correctly and intimately understand who your audience is. I'll be touching base later about how you can leverage AI yourself to help you with outreach and closing. The beauty of gen AI and the AAA model You don't need to be a seasoned web developer to make this business model work. The large majority of solutions that SME clients want is best done using an API for an LLM for the actual AI aspect. The value we create with the solutions we build comes with the conceptual framework and design that not only does what they need it to but integrates smoothly with their existing tech-stack and workflow. The actual implementation is quite straightforward once you understand the high level design and know which tools you are going to use. To give you a sense, even if you plan to build out these apps yourself (say in Python) the large majority of the nitty gritty technical work has already been done for you, especially if you leverage Python libraries and packages that offer high level abstraction for LLM-related functions. For instance, calling GPT can be as little as a single line of code. (And there are no-code tools where these functions are simply an icon on a GUI). Aside from understanding the capabilities and limitations of these tools and frameworks, the only thing that matters is being able to put them in a way that makes sense for what you want to build. Which is why outsourcing and no-code tools both work in our case. Okay... but how TF am I suppposed to actually build out these solutions? Now the fun part. I highly recommend getting familiar with Langchain and LlamaIndex. Both are Python libraires that help a lot with the high-level LLM abstraction I mentioned previously. The two most important aspects include being able to integrate internal data sources/knowledge bases with LLMs, and have LLMs perform autonomous actions. The two most common methods respectively are RAG and output parsing. RAG (retrieval augmented Generation) If you've ever seen a tool that seemingly "trains" GPT on your own data, and wonder how it all works- well I have an answer from you. At a high level, the user query is first being fed to what's called a vector database to run vector search. Vector search basically lets you do semantic search where you are searching data based on meaning. The vector databases then retrieves the most relevant sections of text as it relates to the user query, and this text gets APPENDED to your GPT prompt to provide extra context to the AI. Further, with prompt engineering, you can limit GPT to only generate an answer if it can be found within this extra context, greatly limiting the chance of hallucination (this is where AI makes random shit up). Aside from vector databases, we can also implement RAG with other data sources and retrieval methods, for example SQL databses (via parsing the outputs of LLM's- more on this later). Autonomous Agents via Output Parsing A common need of clients has been having AI actually perform tasks, rather than simply spitting out text. For example, with autonomous agents, we can have an e-commerce chatbot do the work of a basic customer service rep (i.e. look into orders, refunds, shipping). At a high level, what's going on is that the response of the LLM is being used programmtically to determine which API to call. Keeping on with the e-commerce example, if I wanted a chatbot to check shipping status, I could have a LLM response within my app (not shown to the user) with a prompt that outputs a random hash or string, and programmatically I can determine which API call to make based on this hash/string. And using the same fundamental concept as with RAG, I can append the the API response to a final prompt that would spit out the answer for the user. How No Code Tools Can Fit In (With some example solutions you can build) With that being said, you don't necessarily need to do all of the above by coding yourself, with Python libraries or otherwise. However, I will say that having that high level overview will help IMMENSELY when it comes to using no-code tools to do the actual work for you. Regardless, here are a few common solutions you might build for clients as well as some no-code tools you can use to build them out. Ex. Solution 1: AI Chatbots for SMEs (Small and Medium Enterprises) This involves creating chatbots that handle user queries, lead gen, and so forth with AI, and will use the principles of RAG at heart. After getting the required data from your client (i.e. product catalogues, previous support tickets, FAQ, internal documentation), you upload this into your knowledge base and write a prompt that makes sense for your use case. One no-code tool that does this well is MyAskAI. The beauty of it especially for building external chatbots is the ability to quickly ingest entire websites into your knowledge base via a sitemap, and bulk uploading files. Essentially, they've covered the entire grunt work required to do this manually. Finally, you can create a inline or chat widget on your client's website with a few lines of HTML, or altneratively integrate it with a Slack/Teams chatbot (if you are going for an internal Q&A chatbot approach). Other tools you could use include Botpress and Voiceflow, however these are less for RAG and more for building out complete chatbot flows that may or may not incorporate LLMs. Both apps are essentially GUIs that eliminate the pain and tears and trying to implement complex flows manually, and both natively incoporate AI intents and a knowledge base feature. Ex. Solution 2: Internal Apps Similar to the first example, except we go beyond making just chatbots but tools such as report generation and really any sort of internal tool or automations that may incorporate LLM's. For instance, you can have a tool that automatically generates replies to inbound emails based on your client's knowledge base. Or an automation that does the same thing but for replies to Instagram comments. Another example could be a tool that generates a description and screeenshot based on a URL (useful for directory sites, made one for my own :P). Getting into more advanced implementations of LLMs, we can have tools that can generate entire drafts of reports (think 80+ pages), based not only on data from a knowledge base but also the writing style, format, and author voice of previous reports. One good tool to create content generation panels for your clients would be MindStudio. You can train LLM's via prompt engineering in a structured way with your own data to essentially fine tune them for whatever text you need it to generate. Furthermore, it has a GUI where you can dictate the entire AI flow. You can also upload data sources via multiple formats, including PDF, CSV, and Docx. For automations that require interactions between multiple apps, I recommend the OG zapier/make.com if you want a no-code solution. For instance, for the automatic email reply generator, I can have a trigger such that when an email is received, a custom AI reply is generated by MyAskAI, and finally a draft is created in my email client. Or, for an automation where I can create a social media posts on multiple platforms based on a RSS feed (news feed), I can implement this directly in Zapier with their native GPT action (see screenshot) As for more complex LLM flows that may require multiple layers of LLMs, data sources, and APIs working together to generate a single response i.e. a long form 100 page report, I would recommend tools such as Stack AI or Flowise (open-source alternative) to build these solutions out. Essentially, you get most of the functions and features of Python packages such as Langchain and LlamaIndex in a GUI. See screenshot for an example of a flow How the hell are you supposed to find clients? With all that being said, none of this matters if you can't find anyone to sell to. You will have to do cold sales, one way or the other, especially if you are brand new to the game. And what better way to sell your AI services than with AI itself? If we want to integrate AI into the cold outreach process, first we must identify what it's good at doing, and that's obviously writing a bunch of text, in a short amount of time. Similar to the solutions that an AAA can build for its clients, we can take advantage of the same principles in our own sales processes. How to do outreach Once you've identified your niche and their pain points/opportunities for automation, you want to craft a compelling message in which you can send via cold email and cold calls to get prospects booked on demos/consultations. I won't get into too much detail in terms of exactly how to write emails or calling scripts, as there are millions of resources to help with this, but I will tell you a few key points you want to keep in mind when doing outreach for your AAA. First, you want to keep in mind that many businesses are still hesitant about AI and may not understand what it really is or how it can benefit their operations. However, we can take advantage of how mass media has been reporting on AI this past year- at the very least people are AWARE that sooner or later they may have to implement AI into their businesses to stay competitive. We want to frame our message in a way that introduces generative AI as a technology that can have a direct, tangible, and positive impact on their business. Although it may be hard to quantify, I like to include estimates of man-hours saved or costs saved at least in my final proposals to prospects. Times are TOUGH right now, and money is expensive, so you need to have a compelling reason for businesses to get on board. Once you've gotten your messaging down, you will want to create a list of prospects to contact. Tools you can use to find prospects include Apollo.io, reply.io, zoominfo (expensive af), and Linkedin Sales Navigator. What specific job titles, etc. to target will depend on your niche but for smaller companies this will tend to be the owner. For white collar niches, i.e. law, the professional that will be directly benefiting from the tool (i.e. partners) may be better to contact. And for larger organizations you may want to target business improvement and digital transformation leads/directors- these are the people directly in charge of projects like what you may be proposing. Okay- so you have your message, and your list, and now all it comes down to is getting the good word out. I won't be going into the details of how to send these out, a quick Google search will give you hundreds of resources for cold outreach methods. However, personalization is key and beyond simple dynamic variables you want to make sure you can either personalize your email campaigns directly with AI (SmartWriter.ai is an example of a tool that can do this), or at the very least have the ability to import email messages programmatically. Alternatively, ask ChatGPT to make you a Python Script that can take in a list of emails, scrape info based on their linkedin URL or website, and all pass this onto a GPT prompt that specifies your messaging to generate an email. From there, send away. How tf do I close? Once you've got some prospects booked in on your meetings, you will need to close deals with them to turn them into clients. Call #1: Consultation Tying back to when I mentioned you want to take a consultant-first appraoch, you will want to listen closely to their goals and needs and understand their pain points. This would be the first call, and typically I would provide a high level overview of different solutions we could build to tacke these. It really helps to have a presentation available, so you can graphically demonstrate key points and key technologies. I like to use Plus AI for this, it's basically a Google Slides add-on that can generate slide decks for you. I copy and paste my default company messaging, add some key points for the presentation, and it comes out with pretty decent slides. Call #2: Demo The second call would involve a demo of one of these solutions, and typically I'll quickly prototype it with boilerplate code I already have, otherwise I'll cook something up in a no-code tool. If you have a niche where one type of solution is commonly demanded, it helps to have a general demo set up to be able to handle a larger volume of calls, so you aren't burning yourself out. I'll also elaborate on how the final product would look like in comparison to the demo. Call #3 and Beyond: Once the initial consultation and demo is complete, you will want to alleviate any remaining concerns from your prospects and work with them to reach a final work proposal. It's crucial you lay out exactly what you will be building (in writing) and ensure the prospect understands this. Furthermore, be clear and transparent with timelines and communication methods for the project. In terms of pricing, you want to take this from a value-based approach. The same solution may be worth a lot more to client A than client B. Furthermore, you can create "add-ons" such as monthly maintenance/upgrade packages, training sessions for employeees, and so forth, separate from the initial setup fee you would charge. How you can incorporate AI into marketing your businesses Beyond cold sales, I highly recommend creating a funnel to capture warm leads. For instance, I do this currently with my AI tools directory, which links directly to my AI agency and has consistent branding throughout. Warm leads are much more likely to close (and honestly, much nicer to deal with). However, even without an AI-related website, at the very least you will want to create a presence on social media and the web in general. As with any agency, you will want basic a professional presence. A professional virtual address helps, in addition to a Google Business Profile (GBP) and TrustPilot. a GBP (especially for local SEO) and Trustpilot page also helps improve the looks of your search results immensely. For GBP, I recommend using ProfilePro, which is a chrome extension you can use to automate SEO work for your GBP. Aside from SEO optimzied business descriptions based on your business, it can handle Q/A answers, responses, updates, and service descriptions based on local keywords. Privacy and Legal Concerns of the AAA Model Aside from typical concerns for agencies relating to service contracts, there are a few issues (especially when using no-code tools) that will need to be addressed to run a successful AAA. Most of these surround privacy concerns when working with proprietary data. In your terms with your client, you will want to clearly define hosting providers and any third party tools you will be using to build their solution, and a DPA with these third parties listed as subprocessors if necessary. In addition, you will want to implement best practices like redacting private information from data being used for building solutions. In terms of addressing concerns directly from clients, it helps if you host your solutions on their own servers (not possible with AI tools), and address the fact only ChatGPT queries in the web app, not OpenAI API calls, will be used to train OpenAI's models (as reported by mainstream media). The key here is to be open and transparent with your clients about ALL the tools you are using, where there data will be going, and make sure to get this all in writing. have fun, and keep an open mind Before I finish this post, I just want to reiterate the fact that this is NOT an easy way to make money. Running an AI agency will require hours and hours of dedication and work, and constantly rearranging your schedule to meet prospect and client needs. However, if you are looking for a new business to run, and have a knack for understanding business operations and are genuinely interested in the pracitcal applications of generative AI, then I say go for it. The time is ticking before AAA becomes the new dropshipping or SMMA, and I've a firm believer that those who set foot first and establish themselves in this field will come out top. And remember, while 100 thousand people may read this post, only 2 may actually take initiative and start.

Only 2 months of cash in the Bank for my business but was able to save it with the help of AI.
reddit
LLM Vibe Score0
Human Vibe Score1
CALLIRDAN90This week

Only 2 months of cash in the Bank for my business but was able to save it with the help of AI.

Hi there! I’m excited to share something very personal with you. We needed to book at least 2 appointments per day in the next 60 days, or my business would fail. We were already trying two acquisition channels, LinkedIn and email. The problem with these channels was that the positive response rate was very low in both. So I decided to focus on LinkedIn and get the attention of the lead by sending videos directly to them via LinkedIn messages. (You can send videos to your connections on LinkedIn if you use your cell phone.) This wasn’t new, but I added a small twist to get the lead’s attention. All the covers of the videos had a picture of me holding a sign with the person’s name and an interesting phrase. This showed some okay results, but the rest of the video was not personalized. Only the picture on the cover was. I even developed a Chrome extension for this because I thought this would be the answer and that I would book tons of appointments.  But after more trial and outreach, my leads responded, telling me that because the video itself wasn’t personalized for them, they felt like I didn’t put enough effort in, so they would not book a call with me. So after investing time and effort into my “new bright idea” and getting developers to make the Chrome extension, I was back to square one with no results. A few weeks went by, and after researching online, I found an online course from a guy who promised to teach me how to book 30+ appointments per month, guaranteed (at the time, I was making 2 or 3 appointments per week, maximum). He promised that I would only pay if he actually booked appointments for me and even offered to give me money if his course didn’t work for me. I never paid attention to internet gurus, but the offer was actually not bad, so I looked into this guy’s website. I found out he had hundreds of reviews from people who had taken his course and were talking amazing things about it. The more I read, the more excited I got. I booked a call that day and talked to a salesperson. The call was very short, and he promised I would get at least 2 appointments per day, easily. He seemed a bit cocky and told me that I just needed to trust him and the 100+ reviews from people who had taken the course. He didn’t share details, a proposal, or anything. I asked the price, and he told me it was close to $10k. (Not kidding, this was the price.) Then he told me that I would make the money back in no time with the clients I would get following his course, and that if it didn’t work, he would give me the money back. But I needed to follow everything the course said for at least 6 months. I had never paid $10k for anything in my life; it was extremely expensive for me. Also, my salary from my business was not in dollars but in a currency that was worth much less than the dollar. I continued to research more and more, but no other course was close to the number of reviews and promises that this guy had. I got desperate and told myself that I would bet everything on this course. If it worked for so many others, surely it would work for me. I got a loan from the bank and paid for the course. You might read this and think it was the most stupid thing ever, but the reality is that after 2 months in the course (I did the course as fast as I could), I learned a lot. The course was not bad; it was very extensive—probably more than 200 hours or so—and they taught a lot of things. I don’t think it was worth $10k for me, but I can see how for other people it might be worth that. Now, to the question you’re all thinking: did it get me the 2 appointments I needed per day? The answer is no. Here’s the thing: most of the techniques they taught were innovative and disruptive, but the focus was always on personalization, and they didn’t teach any way to automate the personalization. (I think, at the time they made the course, the tools didn’t exist yet.) So they taught how to do everything manually, and it took a lot—a lot of time and effort. And most annoyingly: an incredible amount of time doing operational things. I did get 2 appointments on some days, but it wasn’t consistent, and I didn’t have the time to spend 14 hours a day doing everything manually or the money to hire someone to do this for me. (I needed to also spend time delivering our service to our current clients; otherwise, they would leave.) I told them this, and they were very reasonable. After some negotiation, they gave me part of the money back. (To be fair, there was a lot of value in the course, so asking for the full $10k back would have been excessive because, in the end, it really taught me a lot of things I didn’t know.) So in the end, I spent $10k and 200+ hours on an online course, spent time and effort developing a Chrome extension, and was still not able to hit the meetings I needed. Money in the business was running out, and I needed to do something fast, or I was doomed. After investing time and effort in tools, research, and spending $10k and over 200 hours on a course that didn’t deliver the consistent results I needed, I was at a crossroads. My businesses were running out of money, and I knew I needed to find a solution quickly, or everything I had worked for would collapse. It was during this time of desperation that I started exploring other options. One night, while scrolling through the internet, I stumbled upon a 2024 article about how AI was being used to revolutionize various industries. It wasn’t directly related to appointment booking, but it sparked an idea in my mind. What if I could use AI to automate the personalization process that I had learned in the course? It seemed like a long shot, but I had nothing to lose. I started researching AI tools and technologies—YouTube videos, podcasts, pretty much everything related to AI—desperate to find something that could help me scale my outreach without investing too much time, while still maintaining the personalization that was so important. After a lot of trial and error, I found a few tools that showed promise. All of these tools were extremely new. Some of them had just launched the versions I needed just weeks ago. I can say I researched and tested more than 50 AI startups, experimenting with them, testing different approaches, checking prices (the problem was that most of them were cheap but became very expensive when applying the volume I needed to get results), and gradually refining my process. It wasn’t an overnight success, but for the first time, I felt like I was onto something that could truly work. The idea of combining AI personalization with volume was something new, and it gave me hope that I could finally book the meetings I needed without burning out. One day, I sent a video of myself talking—completely AI-generated—to my family chat group and waited for their response. None of them noticed it wasn’t actually me. At that moment, I said to myself: “Okay, I am ready to test this in the real world and see if it works.” Like everything in life, focus is key. As I mentioned earlier, we were already trying outbound strategies on LinkedIn and email, but I decided to narrow my focus to LinkedIn and specifically to video outreach. My goal was to stand out from the crowd, where most people were using text or sending generic videos. I knew that if my videos were 100% personalized, it would make a strong impression on my leads. I focused on two key metrics during my tests: Time spent on manual personalized outreach vs. AI-generated personalized outreach. Positive reply rate for non-personalized manual outreach vs. AI-generated personalized outreach. I ran a test using a sample of 50 one-minute videos sent to 50 leads, and here are the results: Time Spent to Make the Videos: Manual Process: It took me up to 10 hours to create and send 50 personalized videos. This included looking good on camera, brushing my hair, choosing appropriate clothing, ensuring proper lighting, not messing up the script, using a camera holder, recharging the phone, pausing to drink water, avoiding external sounds, being in an appropriate room, downloading the videos, deleting the videos that were not good, and sending the final ones. On average, it took me at least 12.5 minutes per one-minute video. AI Process: With AI, it took me just 32 seconds to create the exact same one-minute personalized video—without saying a word or recording a second of footage. In total, I could make and send the same 50 personalized videos in just 27 minutes. Result: The AI process was 24 times faster. Completely crazy! Positive Reply Rate: Non-Personalized Script (Manual): Using a good script without personalization (no name, job title, city, company, etc.) resulted in a positive reply rate of 4-6% on LinkedIn, including follow-ups. Personalized Script (AI): Using the same script but adding personalized details like the lead's name, company, city, and job title resulted in a positive reply rate of 15-20%, including follow-ups. Result: AI personalization led to 3x (three times) more replies. The best part was the responses. Almost everyone who replied thanked me for taking the time to research them, congratulated me on my speech, and appreciated the personalization and eloquence of my message.  These metrics were a complete breakthrough for me. I researched online to see if anyone else had done something similar, but I couldn’t find anything close. After achieving these metrics, booking the two appointments I desperately needed became easy. In fact, in the last 10 weeks, I’ve been able to consistently book 3-4 appointments per day. This success allowed me to train someone in my company to handle the process, freeing me up to focus on other aspects of the business and ultimately saving it. With the AI appointment machine we built, I even have free time now—time that I’ve been using to develop a methodology and tech tools that I now teach to others. I named the methodology Clip2Lead as a reference to the first Chrome extension I developed that didn’t work but ended up being the first step toward everything that followed. I’ve condensed everything I learned and throughout my experiences into a simple and short FREE training where I cover the entire AI appointment booking process. This includes how to find leads, create scripts, set up follow-up sequences, generate AI videos, clone your voice, compare non-AI metrics with AI metrics, and even navigate AI safety controls. I also offer Chrome extensions that helped me automate the process even further, so you can spend your time closing deals or focusing on other acquisition channels, while your AI machine for booking appointments runs with minimal effort from you. If you’re interested please get in touch with me and thank you for taking the time to read my personal story.

I run an AI automation agency (AAA). My honest overview and review of this new business model
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Scout_OfficialThis week

I run an AI automation agency (AAA). My honest overview and review of this new business model

I started an AI tools directory in February, and then branched off that to start an AI automation agency (AAA) in June. So far I've come across a lot of unsustainable "ideas" to make money with AI, but at the same time a few diamonds in the rough that aren't fully tapped into yet- especially the AAA model. Thought I'd share this post to shine light into this new business model and share some ways you could potentially start your own agency, or at the very least know who you are dealing with and how to pick and choose when you (inevitably) get bombarded with cold emails from them down the line. Foreword Running an AAA does NOT involve using AI tools directly to generate and sell content directly. That ship has sailed, and unless you are happy with $5 from Fiverr every month or so, it is not a real business model. Cry me a river but generating generic art with AI and slapping it onto a T-shirt to sell on Etsy won't make you a dime. At the same time, the AAA model will NOT require you to have a deep theoretical knowledge of AI, or any academic degree, as we are more so dealing with the practical applications of generative AI and how we can implement these into different workflows and tech-stacks, rather than building AI models from the ground up. Regardless of all that, common sense and a willingness to learn will help (a shit ton), as with anything. Keep in mind - this WILL involve work and motivation as well. The mindset that AI somehow means everything can be done for you on autopilot is not the right way to approach things. The common theme of businesses I've seen who have successfully implemented AI into their operations is the willingess to work with AI in a way that augments their existing operations, rather than flat out replace a worker or team. And this is exactly the train of thought you need when working with AI as a business model. However, as the field is relatively unsaturated and hype surrounding AI is still fresh for enterprises, right now is the prime time to start something new if generative AI interests you at all. With that being said, I'll be going over three of the most successful AI-adjacent businesses I've seen over this past year, in addition to some tips and resources to point you in the right direction. so.. WTF is an AI Automation Agency? The AI automation agency (or as some YouTubers have coined it, the AAA model) at its core involves creating custom AI solutions for businesses. I have over 1500 AI tools listed in my directory, however the feedback I've received from some enterprise users is that ready-made SaaS tools are too generic to meet their specific needs. Combine this with the fact virtually no smaller companies have the time or skills required to develop custom solutions right off the bat, and you have yourself real demand. I would say in practice, the AAA model is quite similar to Wordpress and even web dev agencies, with the major difference being all solutions you develop will incorporate key aspects of AI AND automation. Which brings me to my second point- JUST AI IS NOT ENOUGH. Rather than reducing the amount of time required to complete certain tasks, I've seen many AI agencies make the mistake of recommending and (trying to) sell solutions that more likely than not increase the workload of their clients. For example, if you were to make an internal tool that has AI answer questions based on their knowledge base, but this knowledge base has to be updated manually, this is creating unnecessary work. As such I think one of the key components of building successful AI solutions is incorporating the new (Generative AI/LLMs) with the old (programmtic automation- think Zapier, APIs, etc.). Finally, for this business model to be successful, ideally you should target a niche in which you have already worked and understand pain points and needs. Not only does this make it much easier to get calls booked with prospects, the solutions you build will have much greater value to your clients (meaning you get paid more). A mistake I've seen many AAA operators make (and I blame this on the "Get Rich Quick" YouTubers) is focusing too much on a specific productized service, rather than really understanding the needs of businesses. The former is much done via a SaaS model, but when going the agency route the only thing that makes sense is building custom solutions. This is why I always take a consultant-first approach. You can only build once you understand what they actually need and how certain solutions may impact their operations, workflows, and bottom-line. Basics of How to Get Started Pick a niche. As I mentioned previously, preferably one that you've worked in before. Niches I know of that are actively being bombarded with cold emails include real estate, e-commerce, auto-dealerships, lawyers, and medical offices. There is a reason for this, but I will tell you straight up this business model works well if you target any white-collar service business (internal tools approach) or high volume businesses (customer facing tools approach). Setup your toolbox. If you wanted to start a pressure washing business, you would need a pressure-washer. This is no different. For those without programming knowledge, I've seen two common ways AAA get setup to build- one is having a network of on-call web developers, whether its personal contacts or simply going to Upwork or any talent sourcing agency. The second is having an arsenal of no-code tools. I'll get to this more in a second, but this works beecause at its core, when we are dealing with the practical applications of AI, the code is quite simple, simply put. Start cold sales. Unless you have a network already, this is not a step you can skip. You've already picked a niche, so all you have to do is find the right message. Keep cold emails short, sweet, but enticing- and it will help a lot if you did step 1 correctly and intimately understand who your audience is. I'll be touching base later about how you can leverage AI yourself to help you with outreach and closing. The beauty of gen AI and the AAA model You don't need to be a seasoned web developer to make this business model work. The large majority of solutions that SME clients want is best done using an API for an LLM for the actual AI aspect. The value we create with the solutions we build comes with the conceptual framework and design that not only does what they need it to but integrates smoothly with their existing tech-stack and workflow. The actual implementation is quite straightforward once you understand the high level design and know which tools you are going to use. To give you a sense, even if you plan to build out these apps yourself (say in Python) the large majority of the nitty gritty technical work has already been done for you, especially if you leverage Python libraries and packages that offer high level abstraction for LLM-related functions. For instance, calling GPT can be as little as a single line of code. (And there are no-code tools where these functions are simply an icon on a GUI). Aside from understanding the capabilities and limitations of these tools and frameworks, the only thing that matters is being able to put them in a way that makes sense for what you want to build. Which is why outsourcing and no-code tools both work in our case. Okay... but how TF am I suppposed to actually build out these solutions? Now the fun part. I highly recommend getting familiar with Langchain and LlamaIndex. Both are Python libraires that help a lot with the high-level LLM abstraction I mentioned previously. The two most important aspects include being able to integrate internal data sources/knowledge bases with LLMs, and have LLMs perform autonomous actions. The two most common methods respectively are RAG and output parsing. RAG (retrieval augmented Generation) If you've ever seen a tool that seemingly "trains" GPT on your own data, and wonder how it all works- well I have an answer from you. At a high level, the user query is first being fed to what's called a vector database to run vector search. Vector search basically lets you do semantic search where you are searching data based on meaning. The vector databases then retrieves the most relevant sections of text as it relates to the user query, and this text gets APPENDED to your GPT prompt to provide extra context to the AI. Further, with prompt engineering, you can limit GPT to only generate an answer if it can be found within this extra context, greatly limiting the chance of hallucination (this is where AI makes random shit up). Aside from vector databases, we can also implement RAG with other data sources and retrieval methods, for example SQL databses (via parsing the outputs of LLM's- more on this later). Autonomous Agents via Output Parsing A common need of clients has been having AI actually perform tasks, rather than simply spitting out text. For example, with autonomous agents, we can have an e-commerce chatbot do the work of a basic customer service rep (i.e. look into orders, refunds, shipping). At a high level, what's going on is that the response of the LLM is being used programmtically to determine which API to call. Keeping on with the e-commerce example, if I wanted a chatbot to check shipping status, I could have a LLM response within my app (not shown to the user) with a prompt that outputs a random hash or string, and programmatically I can determine which API call to make based on this hash/string. And using the same fundamental concept as with RAG, I can append the the API response to a final prompt that would spit out the answer for the user. How No Code Tools Can Fit In (With some example solutions you can build) With that being said, you don't necessarily need to do all of the above by coding yourself, with Python libraries or otherwise. However, I will say that having that high level overview will help IMMENSELY when it comes to using no-code tools to do the actual work for you. Regardless, here are a few common solutions you might build for clients as well as some no-code tools you can use to build them out. Ex. Solution 1: AI Chatbots for SMEs (Small and Medium Enterprises) This involves creating chatbots that handle user queries, lead gen, and so forth with AI, and will use the principles of RAG at heart. After getting the required data from your client (i.e. product catalogues, previous support tickets, FAQ, internal documentation), you upload this into your knowledge base and write a prompt that makes sense for your use case. One no-code tool that does this well is MyAskAI. The beauty of it especially for building external chatbots is the ability to quickly ingest entire websites into your knowledge base via a sitemap, and bulk uploading files. Essentially, they've covered the entire grunt work required to do this manually. Finally, you can create a inline or chat widget on your client's website with a few lines of HTML, or altneratively integrate it with a Slack/Teams chatbot (if you are going for an internal Q&A chatbot approach). Other tools you could use include Botpress and Voiceflow, however these are less for RAG and more for building out complete chatbot flows that may or may not incorporate LLMs. Both apps are essentially GUIs that eliminate the pain and tears and trying to implement complex flows manually, and both natively incoporate AI intents and a knowledge base feature. Ex. Solution 2: Internal Apps Similar to the first example, except we go beyond making just chatbots but tools such as report generation and really any sort of internal tool or automations that may incorporate LLM's. For instance, you can have a tool that automatically generates replies to inbound emails based on your client's knowledge base. Or an automation that does the same thing but for replies to Instagram comments. Another example could be a tool that generates a description and screeenshot based on a URL (useful for directory sites, made one for my own :P). Getting into more advanced implementations of LLMs, we can have tools that can generate entire drafts of reports (think 80+ pages), based not only on data from a knowledge base but also the writing style, format, and author voice of previous reports. One good tool to create content generation panels for your clients would be MindStudio. You can train LLM's via prompt engineering in a structured way with your own data to essentially fine tune them for whatever text you need it to generate. Furthermore, it has a GUI where you can dictate the entire AI flow. You can also upload data sources via multiple formats, including PDF, CSV, and Docx. For automations that require interactions between multiple apps, I recommend the OG zapier/make.com if you want a no-code solution. For instance, for the automatic email reply generator, I can have a trigger such that when an email is received, a custom AI reply is generated by MyAskAI, and finally a draft is created in my email client. Or, for an automation where I can create a social media posts on multiple platforms based on a RSS feed (news feed), I can implement this directly in Zapier with their native GPT action (see screenshot) As for more complex LLM flows that may require multiple layers of LLMs, data sources, and APIs working together to generate a single response i.e. a long form 100 page report, I would recommend tools such as Stack AI or Flowise (open-source alternative) to build these solutions out. Essentially, you get most of the functions and features of Python packages such as Langchain and LlamaIndex in a GUI. See screenshot for an example of a flow How the hell are you supposed to find clients? With all that being said, none of this matters if you can't find anyone to sell to. You will have to do cold sales, one way or the other, especially if you are brand new to the game. And what better way to sell your AI services than with AI itself? If we want to integrate AI into the cold outreach process, first we must identify what it's good at doing, and that's obviously writing a bunch of text, in a short amount of time. Similar to the solutions that an AAA can build for its clients, we can take advantage of the same principles in our own sales processes. How to do outreach Once you've identified your niche and their pain points/opportunities for automation, you want to craft a compelling message in which you can send via cold email and cold calls to get prospects booked on demos/consultations. I won't get into too much detail in terms of exactly how to write emails or calling scripts, as there are millions of resources to help with this, but I will tell you a few key points you want to keep in mind when doing outreach for your AAA. First, you want to keep in mind that many businesses are still hesitant about AI and may not understand what it really is or how it can benefit their operations. However, we can take advantage of how mass media has been reporting on AI this past year- at the very least people are AWARE that sooner or later they may have to implement AI into their businesses to stay competitive. We want to frame our message in a way that introduces generative AI as a technology that can have a direct, tangible, and positive impact on their business. Although it may be hard to quantify, I like to include estimates of man-hours saved or costs saved at least in my final proposals to prospects. Times are TOUGH right now, and money is expensive, so you need to have a compelling reason for businesses to get on board. Once you've gotten your messaging down, you will want to create a list of prospects to contact. Tools you can use to find prospects include Apollo.io, reply.io, zoominfo (expensive af), and Linkedin Sales Navigator. What specific job titles, etc. to target will depend on your niche but for smaller companies this will tend to be the owner. For white collar niches, i.e. law, the professional that will be directly benefiting from the tool (i.e. partners) may be better to contact. And for larger organizations you may want to target business improvement and digital transformation leads/directors- these are the people directly in charge of projects like what you may be proposing. Okay- so you have your message, and your list, and now all it comes down to is getting the good word out. I won't be going into the details of how to send these out, a quick Google search will give you hundreds of resources for cold outreach methods. However, personalization is key and beyond simple dynamic variables you want to make sure you can either personalize your email campaigns directly with AI (SmartWriter.ai is an example of a tool that can do this), or at the very least have the ability to import email messages programmatically. Alternatively, ask ChatGPT to make you a Python Script that can take in a list of emails, scrape info based on their linkedin URL or website, and all pass this onto a GPT prompt that specifies your messaging to generate an email. From there, send away. How tf do I close? Once you've got some prospects booked in on your meetings, you will need to close deals with them to turn them into clients. Call #1: Consultation Tying back to when I mentioned you want to take a consultant-first appraoch, you will want to listen closely to their goals and needs and understand their pain points. This would be the first call, and typically I would provide a high level overview of different solutions we could build to tacke these. It really helps to have a presentation available, so you can graphically demonstrate key points and key technologies. I like to use Plus AI for this, it's basically a Google Slides add-on that can generate slide decks for you. I copy and paste my default company messaging, add some key points for the presentation, and it comes out with pretty decent slides. Call #2: Demo The second call would involve a demo of one of these solutions, and typically I'll quickly prototype it with boilerplate code I already have, otherwise I'll cook something up in a no-code tool. If you have a niche where one type of solution is commonly demanded, it helps to have a general demo set up to be able to handle a larger volume of calls, so you aren't burning yourself out. I'll also elaborate on how the final product would look like in comparison to the demo. Call #3 and Beyond: Once the initial consultation and demo is complete, you will want to alleviate any remaining concerns from your prospects and work with them to reach a final work proposal. It's crucial you lay out exactly what you will be building (in writing) and ensure the prospect understands this. Furthermore, be clear and transparent with timelines and communication methods for the project. In terms of pricing, you want to take this from a value-based approach. The same solution may be worth a lot more to client A than client B. Furthermore, you can create "add-ons" such as monthly maintenance/upgrade packages, training sessions for employeees, and so forth, separate from the initial setup fee you would charge. How you can incorporate AI into marketing your businesses Beyond cold sales, I highly recommend creating a funnel to capture warm leads. For instance, I do this currently with my AI tools directory, which links directly to my AI agency and has consistent branding throughout. Warm leads are much more likely to close (and honestly, much nicer to deal with). However, even without an AI-related website, at the very least you will want to create a presence on social media and the web in general. As with any agency, you will want basic a professional presence. A professional virtual address helps, in addition to a Google Business Profile (GBP) and TrustPilot. a GBP (especially for local SEO) and Trustpilot page also helps improve the looks of your search results immensely. For GBP, I recommend using ProfilePro, which is a chrome extension you can use to automate SEO work for your GBP. Aside from SEO optimzied business descriptions based on your business, it can handle Q/A answers, responses, updates, and service descriptions based on local keywords. Privacy and Legal Concerns of the AAA Model Aside from typical concerns for agencies relating to service contracts, there are a few issues (especially when using no-code tools) that will need to be addressed to run a successful AAA. Most of these surround privacy concerns when working with proprietary data. In your terms with your client, you will want to clearly define hosting providers and any third party tools you will be using to build their solution, and a DPA with these third parties listed as subprocessors if necessary. In addition, you will want to implement best practices like redacting private information from data being used for building solutions. In terms of addressing concerns directly from clients, it helps if you host your solutions on their own servers (not possible with AI tools), and address the fact only ChatGPT queries in the web app, not OpenAI API calls, will be used to train OpenAI's models (as reported by mainstream media). The key here is to be open and transparent with your clients about ALL the tools you are using, where there data will be going, and make sure to get this all in writing. have fun, and keep an open mind Before I finish this post, I just want to reiterate the fact that this is NOT an easy way to make money. Running an AI agency will require hours and hours of dedication and work, and constantly rearranging your schedule to meet prospect and client needs. However, if you are looking for a new business to run, and have a knack for understanding business operations and are genuinely interested in the pracitcal applications of generative AI, then I say go for it. The time is ticking before AAA becomes the new dropshipping or SMMA, and I've a firm believer that those who set foot first and establish themselves in this field will come out top. And remember, while 100 thousand people may read this post, only 2 may actually take initiative and start.

My AI tools system to get things done 5x faster, after trying 100+ AI tools
reddit
LLM Vibe Score0
Human Vibe Score1
looking-everywhereThis week

My AI tools system to get things done 5x faster, after trying 100+ AI tools

Sorry for the long post, but I just had to share this with you all. After starting my own business, I realized I needed to get more work done and take my productivity to the next level. A few days ago, I asked people in this community to recommend AI tools, and that kicked off my journey to include as many AI apps in my system as possible. In my quest, I've tried over 100 AI tools to find the best ones. It wasn't easy, but thanks to the awesome suggestions from this community, I finally nailed down a setup that works for me. I am in search of more fun tools, so please share if you have some suggestions. So here's the breakdown of my whole system, totaling $194 per month: Content Creation: Text ($20): I use ChatGPT for brainstorming, content creation, marketing, and even legal work. I've been going back to it more often after their O1-preview. Video ($20): Captions Ai is my go-to for video editing. I mainly use self-recorded videos and auto-edit them with this app. Graphics ($14): I mix Gamma and Canva. I've got Gamma's Plus subscription and Canva's Pro subscription. I start by prompting my requirements in Gamma and then edit them later in Canva. Plus, Canva's templates are super handy for other stuff. Productivity: FastTrackr AI ($20): This AI assistant helps me manage emails, reply to them, set up meetings, prepare for them, transcribe notes on my phone, and even do basic research when I'm on WhatsApp. I'm thinking of upgrading to their Pro plan to add other emails. ARC Browser + Perplexity ($0): I snagged a 6-month deal for Perplexity Pro, which will cost $20 later on, including $5 credit for API. Sana AI ($0): This one's amazing for meeting assistance. I love how it understands context and key action items. Not sure when they'll start charging, but I can't recommend it enough. Wispr Flow ($15): Lets me use my voice to command apps. It's amazing how accurately it picks up complex names. Might save some cash if I switch to the annual plan. Sales and Marketing: Lead Enrichment ($67): I'm using Clay and share it with a friend to cut costs. People say there are other options, but this one's the best despite the learning curve. Instantly AI($37): I've tried other tools for cold emails, but Instantly's warm-up feature is top-notch. For other tasks like social media automation and trigger-based automations, I use a mix of Make and Perplexity APIs ($11). Total Cost: $194 per month. I know hiring someone could help me get more done, but I'm thinking of bringing someone onboard with this system already in place. That way, a new hire could potentially lead to 2x or 3x the work output. Thanks for reading through this! Hope this helps anyone looking to boost their productivity with AI tools. Feel free to ask me anything or share your own experiences! Couldn't add links as this gets flagged by mods.

I run an AI automation agency (AAA). My honest overview and review of this new business model
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Scout_OfficialThis week

I run an AI automation agency (AAA). My honest overview and review of this new business model

I started an AI tools directory in February, and then branched off that to start an AI automation agency (AAA) in June. So far I've come across a lot of unsustainable "ideas" to make money with AI, but at the same time a few diamonds in the rough that aren't fully tapped into yet- especially the AAA model. Thought I'd share this post to shine light into this new business model and share some ways you could potentially start your own agency, or at the very least know who you are dealing with and how to pick and choose when you (inevitably) get bombarded with cold emails from them down the line. Foreword Running an AAA does NOT involve using AI tools directly to generate and sell content directly. That ship has sailed, and unless you are happy with $5 from Fiverr every month or so, it is not a real business model. Cry me a river but generating generic art with AI and slapping it onto a T-shirt to sell on Etsy won't make you a dime. At the same time, the AAA model will NOT require you to have a deep theoretical knowledge of AI, or any academic degree, as we are more so dealing with the practical applications of generative AI and how we can implement these into different workflows and tech-stacks, rather than building AI models from the ground up. Regardless of all that, common sense and a willingness to learn will help (a shit ton), as with anything. Keep in mind - this WILL involve work and motivation as well. The mindset that AI somehow means everything can be done for you on autopilot is not the right way to approach things. The common theme of businesses I've seen who have successfully implemented AI into their operations is the willingess to work with AI in a way that augments their existing operations, rather than flat out replace a worker or team. And this is exactly the train of thought you need when working with AI as a business model. However, as the field is relatively unsaturated and hype surrounding AI is still fresh for enterprises, right now is the prime time to start something new if generative AI interests you at all. With that being said, I'll be going over three of the most successful AI-adjacent businesses I've seen over this past year, in addition to some tips and resources to point you in the right direction. so.. WTF is an AI Automation Agency? The AI automation agency (or as some YouTubers have coined it, the AAA model) at its core involves creating custom AI solutions for businesses. I have over 1500 AI tools listed in my directory, however the feedback I've received from some enterprise users is that ready-made SaaS tools are too generic to meet their specific needs. Combine this with the fact virtually no smaller companies have the time or skills required to develop custom solutions right off the bat, and you have yourself real demand. I would say in practice, the AAA model is quite similar to Wordpress and even web dev agencies, with the major difference being all solutions you develop will incorporate key aspects of AI AND automation. Which brings me to my second point- JUST AI IS NOT ENOUGH. Rather than reducing the amount of time required to complete certain tasks, I've seen many AI agencies make the mistake of recommending and (trying to) sell solutions that more likely than not increase the workload of their clients. For example, if you were to make an internal tool that has AI answer questions based on their knowledge base, but this knowledge base has to be updated manually, this is creating unnecessary work. As such I think one of the key components of building successful AI solutions is incorporating the new (Generative AI/LLMs) with the old (programmtic automation- think Zapier, APIs, etc.). Finally, for this business model to be successful, ideally you should target a niche in which you have already worked and understand pain points and needs. Not only does this make it much easier to get calls booked with prospects, the solutions you build will have much greater value to your clients (meaning you get paid more). A mistake I've seen many AAA operators make (and I blame this on the "Get Rich Quick" YouTubers) is focusing too much on a specific productized service, rather than really understanding the needs of businesses. The former is much done via a SaaS model, but when going the agency route the only thing that makes sense is building custom solutions. This is why I always take a consultant-first approach. You can only build once you understand what they actually need and how certain solutions may impact their operations, workflows, and bottom-line. Basics of How to Get Started Pick a niche. As I mentioned previously, preferably one that you've worked in before. Niches I know of that are actively being bombarded with cold emails include real estate, e-commerce, auto-dealerships, lawyers, and medical offices. There is a reason for this, but I will tell you straight up this business model works well if you target any white-collar service business (internal tools approach) or high volume businesses (customer facing tools approach). Setup your toolbox. If you wanted to start a pressure washing business, you would need a pressure-washer. This is no different. For those without programming knowledge, I've seen two common ways AAA get setup to build- one is having a network of on-call web developers, whether its personal contacts or simply going to Upwork or any talent sourcing agency. The second is having an arsenal of no-code tools. I'll get to this more in a second, but this works beecause at its core, when we are dealing with the practical applications of AI, the code is quite simple, simply put. Start cold sales. Unless you have a network already, this is not a step you can skip. You've already picked a niche, so all you have to do is find the right message. Keep cold emails short, sweet, but enticing- and it will help a lot if you did step 1 correctly and intimately understand who your audience is. I'll be touching base later about how you can leverage AI yourself to help you with outreach and closing. The beauty of gen AI and the AAA model You don't need to be a seasoned web developer to make this business model work. The large majority of solutions that SME clients want is best done using an API for an LLM for the actual AI aspect. The value we create with the solutions we build comes with the conceptual framework and design that not only does what they need it to but integrates smoothly with their existing tech-stack and workflow. The actual implementation is quite straightforward once you understand the high level design and know which tools you are going to use. To give you a sense, even if you plan to build out these apps yourself (say in Python) the large majority of the nitty gritty technical work has already been done for you, especially if you leverage Python libraries and packages that offer high level abstraction for LLM-related functions. For instance, calling GPT can be as little as a single line of code. (And there are no-code tools where these functions are simply an icon on a GUI). Aside from understanding the capabilities and limitations of these tools and frameworks, the only thing that matters is being able to put them in a way that makes sense for what you want to build. Which is why outsourcing and no-code tools both work in our case. Okay... but how TF am I suppposed to actually build out these solutions? Now the fun part. I highly recommend getting familiar with Langchain and LlamaIndex. Both are Python libraires that help a lot with the high-level LLM abstraction I mentioned previously. The two most important aspects include being able to integrate internal data sources/knowledge bases with LLMs, and have LLMs perform autonomous actions. The two most common methods respectively are RAG and output parsing. RAG (retrieval augmented Generation) If you've ever seen a tool that seemingly "trains" GPT on your own data, and wonder how it all works- well I have an answer from you. At a high level, the user query is first being fed to what's called a vector database to run vector search. Vector search basically lets you do semantic search where you are searching data based on meaning. The vector databases then retrieves the most relevant sections of text as it relates to the user query, and this text gets APPENDED to your GPT prompt to provide extra context to the AI. Further, with prompt engineering, you can limit GPT to only generate an answer if it can be found within this extra context, greatly limiting the chance of hallucination (this is where AI makes random shit up). Aside from vector databases, we can also implement RAG with other data sources and retrieval methods, for example SQL databses (via parsing the outputs of LLM's- more on this later). Autonomous Agents via Output Parsing A common need of clients has been having AI actually perform tasks, rather than simply spitting out text. For example, with autonomous agents, we can have an e-commerce chatbot do the work of a basic customer service rep (i.e. look into orders, refunds, shipping). At a high level, what's going on is that the response of the LLM is being used programmtically to determine which API to call. Keeping on with the e-commerce example, if I wanted a chatbot to check shipping status, I could have a LLM response within my app (not shown to the user) with a prompt that outputs a random hash or string, and programmatically I can determine which API call to make based on this hash/string. And using the same fundamental concept as with RAG, I can append the the API response to a final prompt that would spit out the answer for the user. How No Code Tools Can Fit In (With some example solutions you can build) With that being said, you don't necessarily need to do all of the above by coding yourself, with Python libraries or otherwise. However, I will say that having that high level overview will help IMMENSELY when it comes to using no-code tools to do the actual work for you. Regardless, here are a few common solutions you might build for clients as well as some no-code tools you can use to build them out. Ex. Solution 1: AI Chatbots for SMEs (Small and Medium Enterprises) This involves creating chatbots that handle user queries, lead gen, and so forth with AI, and will use the principles of RAG at heart. After getting the required data from your client (i.e. product catalogues, previous support tickets, FAQ, internal documentation), you upload this into your knowledge base and write a prompt that makes sense for your use case. One no-code tool that does this well is MyAskAI. The beauty of it especially for building external chatbots is the ability to quickly ingest entire websites into your knowledge base via a sitemap, and bulk uploading files. Essentially, they've covered the entire grunt work required to do this manually. Finally, you can create a inline or chat widget on your client's website with a few lines of HTML, or altneratively integrate it with a Slack/Teams chatbot (if you are going for an internal Q&A chatbot approach). Other tools you could use include Botpress and Voiceflow, however these are less for RAG and more for building out complete chatbot flows that may or may not incorporate LLMs. Both apps are essentially GUIs that eliminate the pain and tears and trying to implement complex flows manually, and both natively incoporate AI intents and a knowledge base feature. Ex. Solution 2: Internal Apps Similar to the first example, except we go beyond making just chatbots but tools such as report generation and really any sort of internal tool or automations that may incorporate LLM's. For instance, you can have a tool that automatically generates replies to inbound emails based on your client's knowledge base. Or an automation that does the same thing but for replies to Instagram comments. Another example could be a tool that generates a description and screeenshot based on a URL (useful for directory sites, made one for my own :P). Getting into more advanced implementations of LLMs, we can have tools that can generate entire drafts of reports (think 80+ pages), based not only on data from a knowledge base but also the writing style, format, and author voice of previous reports. One good tool to create content generation panels for your clients would be MindStudio. You can train LLM's via prompt engineering in a structured way with your own data to essentially fine tune them for whatever text you need it to generate. Furthermore, it has a GUI where you can dictate the entire AI flow. You can also upload data sources via multiple formats, including PDF, CSV, and Docx. For automations that require interactions between multiple apps, I recommend the OG zapier/make.com if you want a no-code solution. For instance, for the automatic email reply generator, I can have a trigger such that when an email is received, a custom AI reply is generated by MyAskAI, and finally a draft is created in my email client. Or, for an automation where I can create a social media posts on multiple platforms based on a RSS feed (news feed), I can implement this directly in Zapier with their native GPT action (see screenshot) As for more complex LLM flows that may require multiple layers of LLMs, data sources, and APIs working together to generate a single response i.e. a long form 100 page report, I would recommend tools such as Stack AI or Flowise (open-source alternative) to build these solutions out. Essentially, you get most of the functions and features of Python packages such as Langchain and LlamaIndex in a GUI. See screenshot for an example of a flow How the hell are you supposed to find clients? With all that being said, none of this matters if you can't find anyone to sell to. You will have to do cold sales, one way or the other, especially if you are brand new to the game. And what better way to sell your AI services than with AI itself? If we want to integrate AI into the cold outreach process, first we must identify what it's good at doing, and that's obviously writing a bunch of text, in a short amount of time. Similar to the solutions that an AAA can build for its clients, we can take advantage of the same principles in our own sales processes. How to do outreach Once you've identified your niche and their pain points/opportunities for automation, you want to craft a compelling message in which you can send via cold email and cold calls to get prospects booked on demos/consultations. I won't get into too much detail in terms of exactly how to write emails or calling scripts, as there are millions of resources to help with this, but I will tell you a few key points you want to keep in mind when doing outreach for your AAA. First, you want to keep in mind that many businesses are still hesitant about AI and may not understand what it really is or how it can benefit their operations. However, we can take advantage of how mass media has been reporting on AI this past year- at the very least people are AWARE that sooner or later they may have to implement AI into their businesses to stay competitive. We want to frame our message in a way that introduces generative AI as a technology that can have a direct, tangible, and positive impact on their business. Although it may be hard to quantify, I like to include estimates of man-hours saved or costs saved at least in my final proposals to prospects. Times are TOUGH right now, and money is expensive, so you need to have a compelling reason for businesses to get on board. Once you've gotten your messaging down, you will want to create a list of prospects to contact. Tools you can use to find prospects include Apollo.io, reply.io, zoominfo (expensive af), and Linkedin Sales Navigator. What specific job titles, etc. to target will depend on your niche but for smaller companies this will tend to be the owner. For white collar niches, i.e. law, the professional that will be directly benefiting from the tool (i.e. partners) may be better to contact. And for larger organizations you may want to target business improvement and digital transformation leads/directors- these are the people directly in charge of projects like what you may be proposing. Okay- so you have your message, and your list, and now all it comes down to is getting the good word out. I won't be going into the details of how to send these out, a quick Google search will give you hundreds of resources for cold outreach methods. However, personalization is key and beyond simple dynamic variables you want to make sure you can either personalize your email campaigns directly with AI (SmartWriter.ai is an example of a tool that can do this), or at the very least have the ability to import email messages programmatically. Alternatively, ask ChatGPT to make you a Python Script that can take in a list of emails, scrape info based on their linkedin URL or website, and all pass this onto a GPT prompt that specifies your messaging to generate an email. From there, send away. How tf do I close? Once you've got some prospects booked in on your meetings, you will need to close deals with them to turn them into clients. Call #1: Consultation Tying back to when I mentioned you want to take a consultant-first appraoch, you will want to listen closely to their goals and needs and understand their pain points. This would be the first call, and typically I would provide a high level overview of different solutions we could build to tacke these. It really helps to have a presentation available, so you can graphically demonstrate key points and key technologies. I like to use Plus AI for this, it's basically a Google Slides add-on that can generate slide decks for you. I copy and paste my default company messaging, add some key points for the presentation, and it comes out with pretty decent slides. Call #2: Demo The second call would involve a demo of one of these solutions, and typically I'll quickly prototype it with boilerplate code I already have, otherwise I'll cook something up in a no-code tool. If you have a niche where one type of solution is commonly demanded, it helps to have a general demo set up to be able to handle a larger volume of calls, so you aren't burning yourself out. I'll also elaborate on how the final product would look like in comparison to the demo. Call #3 and Beyond: Once the initial consultation and demo is complete, you will want to alleviate any remaining concerns from your prospects and work with them to reach a final work proposal. It's crucial you lay out exactly what you will be building (in writing) and ensure the prospect understands this. Furthermore, be clear and transparent with timelines and communication methods for the project. In terms of pricing, you want to take this from a value-based approach. The same solution may be worth a lot more to client A than client B. Furthermore, you can create "add-ons" such as monthly maintenance/upgrade packages, training sessions for employeees, and so forth, separate from the initial setup fee you would charge. How you can incorporate AI into marketing your businesses Beyond cold sales, I highly recommend creating a funnel to capture warm leads. For instance, I do this currently with my AI tools directory, which links directly to my AI agency and has consistent branding throughout. Warm leads are much more likely to close (and honestly, much nicer to deal with). However, even without an AI-related website, at the very least you will want to create a presence on social media and the web in general. As with any agency, you will want basic a professional presence. A professional virtual address helps, in addition to a Google Business Profile (GBP) and TrustPilot. a GBP (especially for local SEO) and Trustpilot page also helps improve the looks of your search results immensely. For GBP, I recommend using ProfilePro, which is a chrome extension you can use to automate SEO work for your GBP. Aside from SEO optimzied business descriptions based on your business, it can handle Q/A answers, responses, updates, and service descriptions based on local keywords. Privacy and Legal Concerns of the AAA Model Aside from typical concerns for agencies relating to service contracts, there are a few issues (especially when using no-code tools) that will need to be addressed to run a successful AAA. Most of these surround privacy concerns when working with proprietary data. In your terms with your client, you will want to clearly define hosting providers and any third party tools you will be using to build their solution, and a DPA with these third parties listed as subprocessors if necessary. In addition, you will want to implement best practices like redacting private information from data being used for building solutions. In terms of addressing concerns directly from clients, it helps if you host your solutions on their own servers (not possible with AI tools), and address the fact only ChatGPT queries in the web app, not OpenAI API calls, will be used to train OpenAI's models (as reported by mainstream media). The key here is to be open and transparent with your clients about ALL the tools you are using, where there data will be going, and make sure to get this all in writing. have fun, and keep an open mind Before I finish this post, I just want to reiterate the fact that this is NOT an easy way to make money. Running an AI agency will require hours and hours of dedication and work, and constantly rearranging your schedule to meet prospect and client needs. However, if you are looking for a new business to run, and have a knack for understanding business operations and are genuinely interested in the pracitcal applications of generative AI, then I say go for it. The time is ticking before AAA becomes the new dropshipping or SMMA, and I've a firm believer that those who set foot first and establish themselves in this field will come out top. And remember, while 100 thousand people may read this post, only 2 may actually take initiative and start.

Using AI to Streamline JTBD Interviews and Analysis
reddit
LLM Vibe Score0
Human Vibe Score1
marcocelloThis week

Using AI to Streamline JTBD Interviews and Analysis

Hello everyone! 👋 I wanted to share a personal project I have worked on in the last months that uses LLMs together with Jobs-to-be-Done to make product development easier and more efficient. The idea is to automate identifying key jobs, figuring out who performs them, creating synthetic users, and conducting interviews. By doing this, we cut down on the time and resources usually spent on manual user research, making it quicker and simpler to gather the insights needed for your product roadmap. Here’s how it works: Discovering Main Jobs and Job Performers: Starting with a rough vision, the code helps you identify and suggest potential main jobs and the people who typically perform them, based on your vision and skillset. Creating Synthetic Users: I use LLMs to build user archetypes that reflect real needs, goals, and pain points. Automated Interviews: Using GPT’s language capabilities, I’ve set up a system that runs interviews with these synthetic personas, pulling out key insights on customer motivations and needs. Analyzing Interviews and Extract Needs: Finally, we break down all the information from these interviews into actionable insights—covering everything from job steps to emotional and social jobs. This project lays the groundwork for a user-centered product design strategy, helping me make smarter decisions on what features to prioritize, how to improve user experience, and how to drive overall product development. Would love to hear your thoughts! 💬

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey
reddit
LLM Vibe Score0
Human Vibe Score0.778
benfromwhereThis week

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey

Update on February 22th: I changed my AI influencer's names because it caused some problems on my business. One year, two AI-powered influencers, and $250K in revenue. Sounds unreal? It’s not. Today, I’m pulling back the curtain on the strategies, tools, and hard-won lessons that took me from concept to a six-figure success story in the AI influencer space. Hey, I'm Ben—a 32-year-old designer who spent the past year navigating the world of AI influencers. Let me clear up any confusion right from the start: I’m not here to sell you anything. This is purely a case study to share what worked, what didn’t, and what I’ve learned along the way. I’ll also make sure to answer all your questions in the comments for free whenever I can, so don’t hesitate to ask. Links to Past Topics: If you're curious about some of the groundwork I covered, check out a few of my earlier posts here: How I Make $10,000 Monthly | AI Influencer Management How I Earned $7000+ in 15 Days | AI Influencer Business Update These earlier posts cover a lot of the backstory, so feel free to explore them before diving into this one. So if you're ready, here is the full story: \---- The idea of creating an AI influencer was one of those “what if” moments that wouldn’t leave my mind. At first, it sounded futuristic—even a bit too ambitious. It all started when I stumbled upon an AI influencer on Instagram with the handle AnnaMaes2000. Her content blew me away—the quality, the detail, and just how real everything looked. I was instantly hooked and ended up going through every post, just trying to figure out how she was pulling this off. That’s when I knew I had to learn how this was done. The next step? YouTube. I dived into videos on Stable Diffusion, soaking up everything I could about creating AI-generated images. Those tutorials taught me the basics and got me up to speed. Then, I created my first AI influencer, let's call her Mel for now. Right after that, to complete the storyline and boost engagement, I introduced Mel's “mother,” Jess. Adding Jess gave the whole project depth and a narrative that drew people in, creating a unique family dynamic that instantly elevated traffic and interest. After thousands of bad photos, hundreds of deleted posts, and months of trial and error, you can now see the quality that defines my current accounts. Here’s a rundown of the tools and checkpoints I’ve used from day one, in order: Fooocus on RunDiffusion — Juggernaut V8 Fooocus on RunDiffusion — Juggernaut V9 Fooocus on PC (locally) — Juggernaut V9 Fooocus on PC (locally) —Lyuyang Mix + Juggernaut V9 Flux on PC (couple of photos only since it's so slow even on RTX 4090) Flux on Fal.ai. \---- There’s no magic Instagram hack that guarantees success, despite what everyone thinks and keeps asking me. Quality content, consistent uploads, and solid craftsmanship are what actually help your photos hit trends and show up on the Explore page. Unlike 95% of low-quality AI accounts out there, I don’t rely on faceswap videos, spam Reels, or go around liking comments on other accounts. My approach is fully organic, focused solely on creating my own unique content. By following Instagram's guidelines to the letter, I've managed to direct some of Mel and Jess' fans over to Patreon and Fanvue. There, for a small subscription fee, fans can access exclusive lingerie content. For those looking for more, higher-tier subscriptions give access to even more premium content. Some possible questions and their answers: No, you can't share hardcore NSFW content on Patreon. You can do that on Fanvue. Yes, you can create AI creators on Fanvue — OnlyFans doesn't allow it. Yes, you can use your own ID to get KYC. Yes, we're telling both Mel and Jess is (or use) AI to generate content. And yes, some people leave and some people still have fun with chatting, having a good time and get perfect content for their needs. And yes, we have a chatter team to work on these accounts. \---- This journey wasn’t all smooth sailing. I faced unexpected roadblocks, like platform restrictions that limited certain types of content, and managing fan expectations was more challenging than anticipated. Staying within guidelines while keeping fans engaged required constant adaptation. These hurdles forced me to get creative, adjust my approach, and learn fast. Once I saw Mel and Jess gaining traction, I knew it was time to scale up. Expanding meant finding new ways to keep content fresh, creating deeper narratives, and considering how to bring even more followers into the fold. My focus turned to building a sustainable model that could grow without sacrificing quality or authenticity. If you’re thinking about diving into AI content creation, here’s my advice: patience, consistency, and a focus on quality are key. Don’t cut corners or rely on quick-fix hacks. Invest time in learning the right tools, creating engaging stories, and building an audience that values what you bring to the table. This approach took me from zero to six figures, and it’s what makes the journey worth it. \---- And finally, here’s the income breakdown that everyone’s curious about: Mel on Fanvue: $82,331.58 (Gross earnings because we have chatter cuts like 15%) Mel on Patreon: $50,865.98 (Net earnings) Jess on Fanvue: $89,068.26 (Gross earnings because we have chatter cuts like 15%) Jess on Patreon: $39,040.70 And thanks to Reddit and my old posts, I got a perfect investor like after 5 months, so this is a "payback" for that. Like I said, I'll answer every question in the comments — take care and let me know.

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey
reddit
LLM Vibe Score0
Human Vibe Score0.778
benfromwhereThis week

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey

Update on February 22th: I changed my AI influencer's names because it caused some problems on my business. One year, two AI-powered influencers, and $250K in revenue. Sounds unreal? It’s not. Today, I’m pulling back the curtain on the strategies, tools, and hard-won lessons that took me from concept to a six-figure success story in the AI influencer space. Hey, I'm Ben—a 32-year-old designer who spent the past year navigating the world of AI influencers. Let me clear up any confusion right from the start: I’m not here to sell you anything. This is purely a case study to share what worked, what didn’t, and what I’ve learned along the way. I’ll also make sure to answer all your questions in the comments for free whenever I can, so don’t hesitate to ask. Links to Past Topics: If you're curious about some of the groundwork I covered, check out a few of my earlier posts here: How I Make $10,000 Monthly | AI Influencer Management How I Earned $7000+ in 15 Days | AI Influencer Business Update These earlier posts cover a lot of the backstory, so feel free to explore them before diving into this one. So if you're ready, here is the full story: \---- The idea of creating an AI influencer was one of those “what if” moments that wouldn’t leave my mind. At first, it sounded futuristic—even a bit too ambitious. It all started when I stumbled upon an AI influencer on Instagram with the handle AnnaMaes2000. Her content blew me away—the quality, the detail, and just how real everything looked. I was instantly hooked and ended up going through every post, just trying to figure out how she was pulling this off. That’s when I knew I had to learn how this was done. The next step? YouTube. I dived into videos on Stable Diffusion, soaking up everything I could about creating AI-generated images. Those tutorials taught me the basics and got me up to speed. Then, I created my first AI influencer, let's call her Mel for now. Right after that, to complete the storyline and boost engagement, I introduced Mel's “mother,” Jess. Adding Jess gave the whole project depth and a narrative that drew people in, creating a unique family dynamic that instantly elevated traffic and interest. After thousands of bad photos, hundreds of deleted posts, and months of trial and error, you can now see the quality that defines my current accounts. Here’s a rundown of the tools and checkpoints I’ve used from day one, in order: Fooocus on RunDiffusion — Juggernaut V8 Fooocus on RunDiffusion — Juggernaut V9 Fooocus on PC (locally) — Juggernaut V9 Fooocus on PC (locally) —Lyuyang Mix + Juggernaut V9 Flux on PC (couple of photos only since it's so slow even on RTX 4090) Flux on Fal.ai. \---- There’s no magic Instagram hack that guarantees success, despite what everyone thinks and keeps asking me. Quality content, consistent uploads, and solid craftsmanship are what actually help your photos hit trends and show up on the Explore page. Unlike 95% of low-quality AI accounts out there, I don’t rely on faceswap videos, spam Reels, or go around liking comments on other accounts. My approach is fully organic, focused solely on creating my own unique content. By following Instagram's guidelines to the letter, I've managed to direct some of Mel and Jess' fans over to Patreon and Fanvue. There, for a small subscription fee, fans can access exclusive lingerie content. For those looking for more, higher-tier subscriptions give access to even more premium content. Some possible questions and their answers: No, you can't share hardcore NSFW content on Patreon. You can do that on Fanvue. Yes, you can create AI creators on Fanvue — OnlyFans doesn't allow it. Yes, you can use your own ID to get KYC. Yes, we're telling both Mel and Jess is (or use) AI to generate content. And yes, some people leave and some people still have fun with chatting, having a good time and get perfect content for their needs. And yes, we have a chatter team to work on these accounts. \---- This journey wasn’t all smooth sailing. I faced unexpected roadblocks, like platform restrictions that limited certain types of content, and managing fan expectations was more challenging than anticipated. Staying within guidelines while keeping fans engaged required constant adaptation. These hurdles forced me to get creative, adjust my approach, and learn fast. Once I saw Mel and Jess gaining traction, I knew it was time to scale up. Expanding meant finding new ways to keep content fresh, creating deeper narratives, and considering how to bring even more followers into the fold. My focus turned to building a sustainable model that could grow without sacrificing quality or authenticity. If you’re thinking about diving into AI content creation, here’s my advice: patience, consistency, and a focus on quality are key. Don’t cut corners or rely on quick-fix hacks. Invest time in learning the right tools, creating engaging stories, and building an audience that values what you bring to the table. This approach took me from zero to six figures, and it’s what makes the journey worth it. \---- And finally, here’s the income breakdown that everyone’s curious about: Mel on Fanvue: $82,331.58 (Gross earnings because we have chatter cuts like 15%) Mel on Patreon: $50,865.98 (Net earnings) Jess on Fanvue: $89,068.26 (Gross earnings because we have chatter cuts like 15%) Jess on Patreon: $39,040.70 And thanks to Reddit and my old posts, I got a perfect investor like after 5 months, so this is a "payback" for that. Like I said, I'll answer every question in the comments — take care and let me know.

The Weekly Brief for anyone looking to incorporate AI into their business.
reddit
LLM Vibe Score0
Human Vibe Score1
AI_Business_BriefThis week

The Weekly Brief for anyone looking to incorporate AI into their business.

Good morning and happy Sunday. Today is Sunday and you know what that means. The weekly brief. Covering all of last week’s most important AI business related stories. Here are some of the biggest stories: Claude the newest generative AI. Amazon to change up its search. AI leaders Testify. Meta Open sources its LLM. Voice Actors Struggle Growing AI innovations has led to a struggle for many voice actors. As AI powered voice technology is progressing everyday jobs are becoming more and more scarce. With many publishers already leaning towards replacing many of their voice actors for faster, cheaper, and more efficient AI voices. Meet Claude Anthropic, an AI company founded by ex-OpenAI employee released their generative AI called Claude. Some key aspects of their model is the ability to give more correct and less harmful answers, and perform similar tasks that many other generative AI’s can do. A keynote is that Google has invested 300milloion into the company, which is a direct competitor to their AI Bard. Interesting to see how that will play out. Amazon Changes to Change up Search A new job description at Amazon may have hinted towards their future plans for AI. The description under software developer read “reimagining Amazon Search with an interactive conversational experience”. This may hint towards a generative AI search experience in Amazon for customers. ChatGPT User Get More Access Premium ChatGPT users got access to Web browsing and plugins. This is a crucial step for OpenAI as they plan to pivot to a more assist type AI. While at the same time continuing to research and develop their AI models. This move puts a lot of pressure on Google to hopefully step up their game. AI Leaders Testify This Wednesday AI leaders (Sam Altman, Christina Montgomery and Gary Marcus) all testified before congress about AI regulation. They were asked many questions about AI regulation but came up with two solutions. FDA-Like Approval Processing: AI developing companies are open to safety checks, audits, licensing and risk review. Precision Approach: Develop risk rules, provide explanations and provide guidelines for risks, encourage transparency around AI companies, finally assess impact of AI technologies. Meta Open Sourcing Thursday Meta open sourced this coding for their LLM. As the company wants to see the use of its LLM to help drive innovation, inspire smaller companies, and overall develop better AI technologies. Comes as an interesting move as competitors try and keep their AI’s an insider secret.

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey
reddit
LLM Vibe Score0
Human Vibe Score0.778
benfromwhereThis week

How I Made $250.000+ in a Year: A Case Study of My AI Influencer Journey

Update on February 22th: I changed my AI influencer's names because it caused some problems on my business. One year, two AI-powered influencers, and $250K in revenue. Sounds unreal? It’s not. Today, I’m pulling back the curtain on the strategies, tools, and hard-won lessons that took me from concept to a six-figure success story in the AI influencer space. Hey, I'm Ben—a 32-year-old designer who spent the past year navigating the world of AI influencers. Let me clear up any confusion right from the start: I’m not here to sell you anything. This is purely a case study to share what worked, what didn’t, and what I’ve learned along the way. I’ll also make sure to answer all your questions in the comments for free whenever I can, so don’t hesitate to ask. Links to Past Topics: If you're curious about some of the groundwork I covered, check out a few of my earlier posts here: How I Make $10,000 Monthly | AI Influencer Management How I Earned $7000+ in 15 Days | AI Influencer Business Update These earlier posts cover a lot of the backstory, so feel free to explore them before diving into this one. So if you're ready, here is the full story: \---- The idea of creating an AI influencer was one of those “what if” moments that wouldn’t leave my mind. At first, it sounded futuristic—even a bit too ambitious. It all started when I stumbled upon an AI influencer on Instagram with the handle AnnaMaes2000. Her content blew me away—the quality, the detail, and just how real everything looked. I was instantly hooked and ended up going through every post, just trying to figure out how she was pulling this off. That’s when I knew I had to learn how this was done. The next step? YouTube. I dived into videos on Stable Diffusion, soaking up everything I could about creating AI-generated images. Those tutorials taught me the basics and got me up to speed. Then, I created my first AI influencer, let's call her Mel for now. Right after that, to complete the storyline and boost engagement, I introduced Mel's “mother,” Jess. Adding Jess gave the whole project depth and a narrative that drew people in, creating a unique family dynamic that instantly elevated traffic and interest. After thousands of bad photos, hundreds of deleted posts, and months of trial and error, you can now see the quality that defines my current accounts. Here’s a rundown of the tools and checkpoints I’ve used from day one, in order: Fooocus on RunDiffusion — Juggernaut V8 Fooocus on RunDiffusion — Juggernaut V9 Fooocus on PC (locally) — Juggernaut V9 Fooocus on PC (locally) —Lyuyang Mix + Juggernaut V9 Flux on PC (couple of photos only since it's so slow even on RTX 4090) Flux on Fal.ai. \---- There’s no magic Instagram hack that guarantees success, despite what everyone thinks and keeps asking me. Quality content, consistent uploads, and solid craftsmanship are what actually help your photos hit trends and show up on the Explore page. Unlike 95% of low-quality AI accounts out there, I don’t rely on faceswap videos, spam Reels, or go around liking comments on other accounts. My approach is fully organic, focused solely on creating my own unique content. By following Instagram's guidelines to the letter, I've managed to direct some of Mel and Jess' fans over to Patreon and Fanvue. There, for a small subscription fee, fans can access exclusive lingerie content. For those looking for more, higher-tier subscriptions give access to even more premium content. Some possible questions and their answers: No, you can't share hardcore NSFW content on Patreon. You can do that on Fanvue. Yes, you can create AI creators on Fanvue — OnlyFans doesn't allow it. Yes, you can use your own ID to get KYC. Yes, we're telling both Mel and Jess is (or use) AI to generate content. And yes, some people leave and some people still have fun with chatting, having a good time and get perfect content for their needs. And yes, we have a chatter team to work on these accounts. \---- This journey wasn’t all smooth sailing. I faced unexpected roadblocks, like platform restrictions that limited certain types of content, and managing fan expectations was more challenging than anticipated. Staying within guidelines while keeping fans engaged required constant adaptation. These hurdles forced me to get creative, adjust my approach, and learn fast. Once I saw Mel and Jess gaining traction, I knew it was time to scale up. Expanding meant finding new ways to keep content fresh, creating deeper narratives, and considering how to bring even more followers into the fold. My focus turned to building a sustainable model that could grow without sacrificing quality or authenticity. If you’re thinking about diving into AI content creation, here’s my advice: patience, consistency, and a focus on quality are key. Don’t cut corners or rely on quick-fix hacks. Invest time in learning the right tools, creating engaging stories, and building an audience that values what you bring to the table. This approach took me from zero to six figures, and it’s what makes the journey worth it. \---- And finally, here’s the income breakdown that everyone’s curious about: Mel on Fanvue: $82,331.58 (Gross earnings because we have chatter cuts like 15%) Mel on Patreon: $50,865.98 (Net earnings) Jess on Fanvue: $89,068.26 (Gross earnings because we have chatter cuts like 15%) Jess on Patreon: $39,040.70 And thanks to Reddit and my old posts, I got a perfect investor like after 5 months, so this is a "payback" for that. Like I said, I'll answer every question in the comments — take care and let me know.

SaaS, Agency, or job?
reddit
LLM Vibe Score0
Human Vibe Score0.818
SlowageAIThis week

SaaS, Agency, or job?

Recently, I was fired, and since I have some savings, I decided it’s finally time to start my own venture. After a couple of weeks of research and trying to figure out what I should do, here are my thoughts and some questions at the end. I’d appreciate any feedback or opinions. It’s not that I expect to wake up a multimillionaire, but I see how people make money without working the typical 9-5. Some of the worst examples are on YouTube—those agency, OFM, dropshipping hustle bros. I know it’s naive to believe all of it because they’re just selling courses, but some of them do seem to have built impressive income streams. Anyway, let’s dive into two categories and compare. Agency (providing services, development, consultation): I’ll talk about AI automation because of my background in ML Engineering and Generative AI, but this could apply to any other agency niche. It seems like a good business idea for someone who knows generative AI and can do some impressive things with LLMs, agents, etc. I even started working on it—built a website—but I stopped when I couldn’t define exactly what services to offer. I could do heavy backend tasks with infrastructure, like real machine learning and AI with fine-tuning, but I couldn’t find any examples of agencies doing this. Almost 100% of them are doing simple automations with tools like Zapier or Make. When it comes to business owners, it’s really hard to find clients in general. After reading Reddit threads, articles, and watching videos, it seems like nearly everyone struggles with client acquisition. For a one-person agency offering more complex services like real ML, it would likely be even harder to find clients, compared to big outsourcing companies with sales teams. Even without focusing on the client challenge, which is obvious in any business, looking at what successful agency owners earn, it’s usually around $100k–$200k a year. I’m not talking about the high end, just regular people. I got this information from reading, and a simple example is from interviews with people who claim to make $10k/month. But many others in these communities struggle to even reach that point. It seems like this is a difficult target for most people. SaaS: This area seems more straightforward, and with my background, it feels like a good fit. However, from reading different sources, I’ve found stories like, “It took me six months to get my first client,” or “I worked on a simple SaaS for nine months and just reached my first $1k.” There are also warnings not to believe those who claim to make $10k/month easily, and many people report struggling to grow after getting their first 10 clients. So, it’s clear to me that even with good tech skills, you’re not going to make massive amounts of money overnight, which I understand. However, with so many people becoming startup founders and indie hackers, many seem to struggle despite thinking it’s the way to go. I know both paths can potentially skyrocket, but here’s where I need help: Am I wrong about agencies? Am I wrong about SaaS? The toughest question for me: I don’t want to go back to a 9-5 job, even if I could earn $300k a year. Even if my own business takes more time and I earn less in the first few years, I still believe it will be more profitable long term, and I will be happier. So, should I pursue an agency, SaaS, or a traditional job?

I single-handedly built the world’s best AI investing platform. Here’s NexusTrade’s 2024 year in review
reddit
LLM Vibe Score0
Human Vibe Score1
No-Definition-2886This 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.

I had over 1000 visitors in 24h thanks to a post on HN and generated 0$ revenue but here is what I learned:
reddit
LLM Vibe Score0
Human Vibe Score1
sow4codeThis week

I had over 1000 visitors in 24h thanks to a post on HN and generated 0$ revenue but here is what I learned:

I litteraly just have 39 followers ont Twitter, I don't have an audience at all and a vice that entrepreneurs and indie hackers often fall into is looking at others who have an audience and to start hating it and telling themselves that even if their products are crap they will still have traffic on their site given their number of subscribers and their audiences. This thought is just a limiting thought because. Yes, obviously it's easier for the person who already has an andience to bring traffic to their site and acquire these first users but these people have to work to build this audience, it wasn't easy, it required a lot of effort but we quickly forget that when we don't even have a tenth of what this person has and despite this facility it's not an excuse to fill up and abandon your project, telling yourself that no one will ever see my product if I don't already have a built audience. That's not an excuse ! I am proof of this on a small scale, yesterday I launched my new product (EduHunt, a site that helps you find the most relevant educational content that you are looking for to avoid paying for online courses that are worth a fortune but to be honest in the end it was rubbish, the idea seemed good but the market is what it is and there is NO need for a site like that, I still learn lessons from it, failure is necessary to succeed ! ). So I launched EduHunt on Hacker News and on Reddit but Reddit didn't bring me much in the end. 1 hour after the launch I had around fifty visitors and 3 registered (trial period), I told myself that it was going to continue like this and I hoped to have 200 visitors at the end of the day no more. I can't tell you what a surprise it was when I opened Vercel and saw 800 visitors for 50 online as I looked, I went crazy lol. My post on Hacker News "exploded", I had more than 400 people who had just come from Hacker News and other sites linked to Hacker News, I told myself that it was finally the right one but reality quickly caught up with me , I went to see my post and this is the kind of comment I had ( Above the text ) As you see, my product sucks and it's not the end of the world, I learn a lot of lessons from it, I failed in the design of the product in directly reflecting what the idea of the product is (most of the comments do not really target my basic idea, I wanted to create a site to help search for educational content on YouTube with filters that are not in the usual YouTube search and this in text format analyzed by AI, I was told that I monetize free videos, I do not appropriate the videos that I put on my site and that you have to pay to have access, what is monetized here is the means of 'access to the content, not the content itself, but yes I failed in this and in many others of this project but I come out better) Despite this, I attracted more than 1000 visitors to my site in less than 24 hours with a simple post on Hacker News, a good title, a sincere story to go with it and that was it, I have no audience nothing at all. If the product had been much better who knows where I would be today. All this to say and remind you that there are no excuses to hide behind, building an audience requires hard work and takes time ! But just because you don't have one doesn't mean you can never bring traffic to your site. Be honest in what you do, learn from your mistakes, repeat and you should find your happiness.

I built an OCR powered by Mistral AI that extracts text, tables, formulas from docs (20+ languages & JSON output!)
reddit
LLM Vibe Score0
Human Vibe Score0
hhe_kkmThis week

I built an OCR powered by Mistral AI that extracts text, tables, formulas from docs (20+ languages & JSON output!)

Hi everyone 👋 Most OCR tools struggle with complex documents—crumbling tables, garbled formulas, or unstructured text. Need clean data for RAG or apps? Good luck. So I built Mistral OCR (https://www.mistralocr.app/) using Mistral AI’s document understanding models. It doesn’t just scan—it understands the document’s structure, and extracts: ✅ Text (plain/formatted) ✅ Tables (pixel-perfect JSON with headers 🧮) ✅ Math formulas (LaTeX-ready via Mistral’s ML pipeline) ✅ Images (preserved or extracted) Why Mistral AI? Their models nail context-aware parsing—unlike rigid OCRs, Mistral’s tech handles: Cursed PDFs(scanned/watermarked/warped text) Mixed layouts (research papers with tables + formulas) 20+ languages (English, Japanese, Mandarin, Spanish...) Structured JSON output (directly feeds into RAG/APIs) See examples → https://www.mistralocr.app/ Why build this? I needed an OCR that could extract RAG-ready data without regex nightmares. Mistral AI’s models finally made this possible—they preserve relationships between text, tables, and formulas, something traditional OCRs butcher. Who’s using it? Devs automating document workflows Researchers digitizing datasets from papers Teams processing multilingual forms/contracts Anyone frustrated by copying tables from PDFs Challenge me: Send your worst documents (scanned receipts? handwritten tables?) and I’ll run them through Mistral OCR live. Try it here → https://www.mistralocr.app/ Let me know what you think! 🙏 Let me know if bugs🐛!🙏

freeciv-web
github
LLM Vibe Score0.567
Human Vibe Score0.5875819302299989
freecivMar 28, 2025

freeciv-web

THE FREECIV-WEB PROJECT Freeciv-web is an open-source turn-based strategy game. It can be played in any HTML5 capable web-browser and features in-depth game-play and a wide variety of game modes and options. Your goal is to build cities, collect resources, organize your government, and build an army, with the ultimate goal of creating the best civilization. You can play online against other players (multiplayer) or play by yourself against the computer. There is both a HTML5 2D version with isometric graphics and a 3D WebGL version of Freeciv-web. Freeciv-web is free and open source software. The Freeciv C server is released under the GNU General Public License, while the Freeciv-web client is released under the GNU Affero General Public License. See License for the full license document. Live servers Currently known servers based on Freeciv-web, which are open source in compliance with the AGPL license: FCIV.NET [https://github.com/fciv-net/fciv-net] freecivweb.org [https://github.com/Lexxie9952/fcw.org-server] moving borders [https://github.com/lonemadmax/freeciv-web] (Everything except longturn and real-Earth) Freeciv Tactics & Triumph [https://github.com/Canik05/freeciv-tnt] Freeciv Games & Mods (No PBEM) Freeciv-web screenshots: Freeciv WebGL 3D: !Freeciv-web Freeciv-web HTML5 version: !Freeciv-web Overview Freeciv-Web consists of these components: Freeciv-web - a Java web application for the Freeciv-web client. This application is a Java web application which make up the application viewed in each user's web browser. The Metaserver is also a part of this module. Implemented in Javascript, Java, JSP, HTML and CSS. Built with maven and runs on Tomcat 10 and nginx. Freeciv - the Freeciv C server, which is checked out from the official Git repository, and patched to work with a WebSocket/JSON protocol. Implemented in C. Freeciv-proxy - a WebSocket proxy which allows WebSocket clients in Freeciv-web to send socket requests to Freeciv servers. WebSocket requests are sent from Javascript in Freeciv-web to nginx, which then proxies the WebSocket messages to freeciv-proxy, which finally sends Freeciv socket requests to the Freeciv servers. Implemented in Python. Publite2 - a process launcher for Freeciv C servers, which manages multiple Freeciv server processes and checks capacity through the Metaserver. Implemented in Python. pbem is play-by-email support. Freeciv WebGL Freeciv WebGL is the 3D version, which uses the Three.js 3D engine. More info about the WebGL 3D version can be found for developers and 3D artists. Developer: Andreas Røsdal @andreasrosdal Running Freeciv-web on your computer The recommended and probably easiest way is to use Vagrant on VirtualBox. Whatever the method you choose, you'll have to check out Freeciv-web to a directory on your computer, by installing Git and running this command: You may also want to change some parameters before installing, although it's not needed in most cases. If you have special requirements, have a look at config.dist, copy it without the .dist extension and edit to your liking. :warning: Notice for Windows users Please keep in mind that the files are to be used in a Unix-like system (some Ubuntu version with the provided Vagrant file). Line endings for text files are different in Windows, and some editors "correct" them, making the files unusable in the VM. There's some provision to recode the main configuration files when installing, but not afterwards. If you touch shared files after installation, please use an editor that respect Unix line endings or transform them with a utility like dos2unix after saving them. Running Freeciv-web with Vagrant on VirtualBox Freeciv-web can be setup using Vagrant on VirtualBox to quickly create a local developer image running Freeciv-web on latest Ubuntu on your host operating system such as Windows, OSX or Linux. This is the recommended way to build Freeciv-web on your computer. Install VirtualBox: https://www.virtualbox.org/ - Install manually on Windows, and with the following command on Linux: Install Vagrant: http://www.vagrantup.com/ - Install manually on Windows , and with the following command on Linux: Run Vagrant with the following commands in your Freeciv-web directory: This will build, compile, install and run Freeciv-web on the virtual server image. Wait for the installation process to complete, watching for any error messages in the logs. If you get an error message about Virtualization (VT) not working, then enable Virtualization in the BIOS. Test Freeciv-web by pointing your browser to http://localhost if you run Windows or http://localhost:8080 if you run Linux or macOS. To log in to your Vagrant server, run the command: The Vagrant guest machine will mount the Freeciv-web source repository in the /vagrant directory. Note that running Freeciv-web using Vagrant requires about 4Gb of memory and 3 Gb of harddisk space. System Requirements for manual install Install this software if you are not running Freeciv-web with Vagrant: Tomcat 10 - https://tomcat.apache.org/ Java 11 JDK - https://adoptopenjdk.net/ Python 3.6 - http://www.python.org/ Pillow v2.3.0 (PIL fork) - http://pillow.readthedocs.org/ (required for freeciv-img-extract) MariaDB - https://mariadb.org/ Maven 3 - http://maven.apache.org/download.html Firebug for debugging - http://getfirebug.com/ curl-7.19.7 - http://curl.haxx.se/ OpenSSL - http://www.openssl.org/ nginx 1.11.x or later - http://nginx.org/ MySQL Connector/Python - https://github.com/mysql/mysql-connector-python pngcrush, required for freeciv-img-extract. http://pmt.sourceforge.net/pngcrush/ Tornado 6.1 or later - http://www.tornadoweb.org/ Jansson 2.6 - http://www.digip.org/jansson/ liblzma-dev - http://tukaani.org/xz/ - for XZ compressed savegames. When in a tested system, you may run scripts/install/install.sh and it will fetch and configure what's needed. Start and stop Freeciv-web with the following commands: start-freeciv-web.sh stop-freeciv-web.sh status-freeciv-web.sh All software components in Freeciv-web will log to the /logs sub-directory of the Freeciv-web installation. Running Freeciv-web on Docker Freeciv-web can easily be built and run from Docker using docker-compose. Make sure you have both Docker and Docker Compose installed. Run the following from the freeciv-web directory: Connect to docker via host machine using standard browser http://localhost:8080/ Enjoy. The overall dockerfile and required changes to scripts needs some further improvements. Freeciv-Web continuous integration on GitHub actions Freeciv-Web is built on GitHub actions on every commit. This is the current build status: Developers interested in Freeciv-web If you want to contibute to Freeciv-web, see the issues on GibHub and the TODO file for some tasks you can work on. Pull requests on Github are welcome! Contributors to Freeciv-web Andreas Røsdal @andreasrosdal Marko Lindqvist @cazfi Sveinung Kvilhaugsvik @kvilhaugsvik Gerik Bonaert @adaxi Lmoureaux @lmoureaux Máximo Castañeda @lonemadmax and the Freeciv.org project!

Ultimate-Data-Science-Toolkit---From-Python-Basics-to-GenerativeAI
github
LLM Vibe Score0.555
Human Vibe Score0.3470230117125603
bansalkanavMar 27, 2025

Ultimate-Data-Science-Toolkit---From-Python-Basics-to-GenerativeAI

Getting started with Machine Learning and Deep Learning Star this repo if you find it useful :star: Module 1 - Python Programming | Topic Name | What's Covered | | :---: | :---: | | Intro to Python | Applications and Features of Python, Hello World Program, Identifiers and Rules to define identifiers, Data Types (numeric, boolean, strings, list, tuple, set and dict), Comments, Input and Output, Operators - Arithmatic, Reltaional, Equality, Logical, Bitwise, Assignment, Ternary, Identity and Membership | | Data Structures in Python (Strings, List, Tuple, Set, Dictionary) | Strings - Creating a string, Indexing, Slicing, Split, Join, etc, List - Initialization, Indexing, Slicing, Sorting, Appending, etc, Tuple - Initialization, Indexing, Slicing, Count, Index, etc, Set - Initialization, Unordered Sequence, Set Opertaions, etc, Dictionary - Initialization, Updating, Keys, Values, Items, etc | | Control Statements (Conditionals and Loops) | Conditional Statements - Introducing Indentation, if statement, if...else statement, if..elif...else statement, Nested if else statement, Loops - while loops, while...else loop, Membership operator, for loop, for...else loop, Nested Loops, Break and Continue Statement, Why else? | | Functions and Modules | Functions - Introduction to Python Functions, Function Definition and Calling, Functions with Arguments/Parameters, Return Statement, Scope of a Variable, Global Variables, Modules - Introduction to Modules, Importing a Module, Aliasing, from...import statement, import everything, Some important modules - math, platform, random, webbrowser, etc | | Object Oriented Programming | Classes and Objects - Creating a class, Instantiating an Object, Constructor, Class Members - Variables and Mentods, Types of Variables - Instance, Static and Local Variables, Types of Methods - Instance, Class and Static Methods, Access Modifiers - Public, Private and Protected, Pillars of Object Oriented Programming - Inheritance, Polymorphism, Abstraction and Encapsulation, Setters and Getters, Inheritance vs Association | | Exception Handling | Errors vs Exception, Syntax and Indentation Errors, try...except block, Control Flow in try...except block, try with multiple except, finally block, try...except...else, Nested try...except...finally, User Defined Exception | | File Handling | Introduction to File Handling, Opening and Closing a File, File Object Properties, Read Data from Text Files, Write Data to Text Files, with statement, Renaming and Deleting Files | | Web API | Application Programming Interface, Indian Space Station API, API Request, Status Code, Query Parameters, Getting JSON from an API Request, Working with JSON - dump and load, Working with Twitter API | | Databases | Introduction to Databases, SQLite3 - Connecting Python with SQLite3, Performing CRUD Opertations, MySQL - Connecting Python with MySQL, Performing CRUD Opertations, MongoDB - Connecting Python with MongoDB, Performing CRUD Opertations, Object Relation Mapping - SQLAlchemy ORM, CRUD operations and Complex DB operations | | List Comprehension, Lambda, Filter, Map, Reduce) | List Comprehension, Anonymous Functions, Filter, Map, Reduce, Function Aliasing | | Problem Solving for Interviews | Swapping two numbers, Factorial of a number, Prime Number, Fibbonnacci Sequence, Armstrong Number, Palindrome Number, etc | Module 2 - Python for Data Analysis | Topic Name | What's Covered | | :---: | :---: | | Data Analytics Framework | Data Collection, Business Understanding, Exploratory Data Analysis, Data Preparation, Model Building, Model Evaluation, Deployment, Understanding Cross Industry Standard Process for Data Mining (CRISP-DM) and Microsoft's Team Data Science Process (TDSP) | | Numpy | Array Oriented Numerical Computations using Numpy, Creating a Numpy Array, Basic Operations on Numpy Array - Check Dimensions, Shape, Datatypes and ItemSize, Why Numpy, Various ways to create Numpy Array, Numpy arange() function, Numpy Random Module - rand(), randn(), randint(), uniform(), etc, Indexing and Slicing in Numpy Arrays, Applying Mathematical Operations on Numpy Array - add(), subtract(), multiply(), divide(), dot(), matmul(), sum(), log(), exp(), etc, Statistical Operations on Numpy Array - min(), max(), mean(), median(), var(), std(), corrcoef(), etc, Reshaping a Numpy Array, Miscellaneous Topics - Linspace, Sorting, Stacking, Concatenation, Append, Where and Numpy Broadcasting | | Pandas for Beginners | Pandas Data Structures - Series, Dataframe and Panel, Creating a Series, Data Access, Creating a Dataframe using Tuples and Dictionaries, DataFrame Attributes - columns, shape, dtypes, axes, values, etc, DataFrame Methods - head(), tail(), info(), describe(), Working with .csv and .xlsx - readcsv() and readexcel(), DataFrame to .csv and .xlsx - tocsv() and toexcel() | | Advance Pandas Operations | What's Covered | | Case Study - Pandas Manipulation | What's Covered | | Missing Value Treatment | What's Covered | | Visuallization Basics - Matplotlib and Seaborn | What's Covered | | Case Study - Covid19TimeSeries | What's Covered | | Plotly and Express | What's Covered | | Outliers - Coming Soon | What's Covered | Module 3 - Statistics for Data Analysis | Topic Name | What's Covered | | :---: | :---: | | Normal Distribution | What's Covered | | Central Limit Theorem | What's Covered | | Hypothesis Testing | What's Covered | | Chi Square Testing | What's Covered | | Performing Statistical Test | What's Covered | Module 4 - Machine Learning Data Preparation and Modelling with SKLearn Working with Text Data Working with Image Data Supervised ML Algorithms K - Nearest Neighbours Linear Regression Logistic Regression Gradient Descent Decision Trees Support Vector Machines Models with Feature Engineering Hyperparameter Tuning Ensembles Unsupervised ML Algorithms Clustering Principal Component Analysis Module 5 - MLOPs | Topic Name | What's Covered | | :---: | :---: | | Model Serialization and Deserialization | What's Covered | | Application Integration | What's Covered | | MLFlow - Experiment Tracking and Model Management | What's Covered | | Prefect - Orchestrate ML Pipeline | What's Covered | Module 6 - Case Studies | Topic Name | What's Covered | | :---: | :---: | | Car Price Prediction (Regression) | What's Covered | | Airline Sentiment Analysis (NLP - Classification) | What's Covered | | Adult Income Prediction (Classification) | What's Covered | | Web App Development + Serialization and Deserialization | What's Covered | | AWS Deployment | What's Covered | | Streamlit Heroku Deployment | What's Covered | | Customer Segmentation | What's Covered | | Web Scrapping | What's Covered | Module 7 - Deep Learning | Topic Name | What's Covered | | :---: | :---: | | Introduction to Deep Learning | What's Covered | | Training a Deep Neural Network + TensorFlow.Keras | What's Covered | | Convolutional Neural Network + TensorFlow.Keras | What's Covered | | Auto Encoders for Image Compression) | What's Covered | | Recurrent Neural Network (Coming Soon) | What's Covered |

eiten
github
LLM Vibe Score0.549
Human Vibe Score0.754375921646308
tradyticsMar 27, 2025

eiten

Eiten - Algorithmic Investing Strategies for Everyone Eiten is an open source toolkit by Tradytics that implements various statistical and algorithmic investing strategies such as Eigen Portfolios, Minimum Variance Portfolios, Maximum Sharpe Ratio Portfolios, and Genetic Algorithms based Portfolios. It allows you to build your own portfolios with your own set of stocks that can beat the market. The rigorous testing framework included in Eiten enables you to have confidence in your portfolios. If you are looking to discuss these tools in depth and talk about more tools that we are working on, please feel free to join our Discord channel where we have a bunch of more tools too. Files Description | Path | Description | :--- | :---------- | eiten | Main folder. | &boxur; figures | Figures for this github repositories. | &boxur; stocks | Folder to keep your stock lists that you want to use to create your portfolios. | &boxur; strategies | A bunch of strategies implemented in python. | backtester.py | Backtesting module that both backtests and forward tests all portfolios. | data_loader.py | Module for loading data from yahoo finance. | portfolio_manager.py | Main file that takes in a bunch of arguments and generates several portfolios for you. | simulator.py | Simulator that uses historical returns and monte carlo to simulate future prices for the portfolios. | strategy_manager.py | Manages the strategies implemented in the 'strategies' folder. Required Packages You will need to install the following package to train and test the models. Scikit-learn Numpy Tqdm Yfinance Pandas Scipy You can install all packages using the following command. Please note that the script was written using python3. Build your portfolios Let us see how we can use all the strategies given in the toolkit to build our portfolios. The first thing you need to do is modify the stocks.txt file in the stocks folder and add the stocks of your choice. It is recommended to keep the list small i.e anywhere between 5 to 50 stocks should be fine. We have already put a small stocks list containing a bunch of tech stocks like AAPL, MSFT, TSLA etc. Let us build our portfolios now. This is the main command that you need to run. This command will use last 5 years of daily data excluding the last 90 days and build several portfolios for you. Based on those portfolios, it will then test them on the out of sample data of 90 days and show you the performance of each portfolio. Finally, it will also compare the performance with your choice of market index which is QQQ here. Let's dive into each of the parameters in detail. istest: The value determined if the program is going to keep some separate data for future testing. When this is enabled, the value of futurebars should be larger than 5. future_bars: These are the bars that the tool will exclude during portfolio building and will forward test the portfolios on the excluded set. This is also called out of sample data. datagranularityminutes: How much granular data do you want to use to build your portfolios. For long term portfolios, you should use daily data but for short term, you can use hourly or minute level data. The possible values here are 3600, 60, 30, 15, 5, 1. 3600 means daily. historytouse: Whether to use a specific number of historical bars or use everything that we receive from yahoo finance. For minute level data, we only receive up to one month of historical data. For daily, we receive 5 years worth of historical data. If you want to use all available data, the value should be all but if you want to use smaller history, you can set it to an integer value e.g 100 which will only use the last 100 bars to build the portfolios. applynoisefiltering: This uses random matrix theory to filter out the covariance matrix from randomness thus yielding better portfolios. A value of 1 will enable it and 0 will disable it. market_index: Which index do you want to use to compare your portfolios. This should mostly be SPY but since we analyzed tech stocks, we used QQQ. only_long: Whether to use long only portfolio or enable short selling as well. Long only portfolios have shown to have better performance using algorithmic techniques. eigenportfolionumber: Which eigen portfolio to use. Any value between 1-5 should work. The first eigen portfolio (1) represents the market portfolio and should act just like the underlying index such as SPY or QQQ. The second one is orthogonal and uncorrelated to the market and poses the greatest risk and reward. The following ones have reduced risk and reward. Read more on eigen-portfolios. stocksfilepath: File that contains the list of stocks that you want to use to build your portfolio. Some Portfolio Building Examples Here are a few examples for building different types of portfolios. Both long and short portfolios by analyzing last 90 days data and keeping the last 30 days as testing data. This will give us 60 days of portfolio construction data and 30 days of testing. Only long portfolio on 60 minute bars of the last 30 days. No future testing. Compare the results with SPY index instead of QQQ. Do not apply noise filtering on the covariance matrix. Use the first eigen portfolio (market portfolio) and compare with SQQQ, Portfolio Strategies Four different portfolio strategies are currently supported by the toolkit. Eigen Portfolios These portfolios are orthogonal and uncorrelated to the market in general thus yielding high reward and alpha. However, since they are uncorrelated to the market, they can also provide great risk. The first eigen portfolio is considered to be a market portfolio which is often ignored. The second one is uncorrelated to the others and provides the highest risk and reward. As we go down the numbering, the risk as well as the reward are reduced. Minimum Variance Portfolio (MVP) MVP tries to minimize the variance of the portfolio. These portfolios are lowest risk and reward. Maximum Sharpe Ratio Portfolio (MSR) MSR solves an optimization problem that tries to maximize the sharpe ratio of the portfolio. It uses past returns during the optimization process which means if past returns are not the same as future returns, the results can vary in future. Genetic Algorithm (GA) based Portfolio This is our own implementation of a GA based portfolio that again tries to maximize the sharpe ratio but in a slightly more robust way. This usually provides more robust portfolios than the others. When you run the command above, our tool will generate portfolios from all these strategies and give them to you. Let us look at some resulting portfolios. Resulting Portfolios For the purpose these results, we will use the 9 stocks in the stocks/stocks.txt file. When we run the above command, we first get the portfolio weights for all four strategies. For testing purposes, the above command used last five years of daily data up till April 29th. The remaining data for this year was used for forward testing i.e the portfolio strategies had no access to it when building the portfolios. What if my portfolio needs different stocks?: All you need to do is change the stocks in the stocks.txt file and run the tool again. Here is the final command again that we run in order to get our portfolios: Portfolio Weights We can see that the eigen portfolio is giving a large weight to TSLA while the others are dividing their weights more uniformly. An interesting phenomena happening here is the hedging with SQQQ that all the strategies have learned automatically. Every tool is assigning some positive weight to SQQQ while also assigning positive weights to other stocks which indicates that the strategies are automatically trying to hedge the portfolios from risk. Obviously this is not perfect, but just the fact that it's happening is fascinating. Let us look at the backtest results on the last five years prior to April 29, 2020. Backtest Results The backtests look pretty encouraging. The black dotted line is the market index i.e QQQ. Other lines are the strategies. Our custom genetic algorithm implementation seems to have the best backtest results because it's an advanced version of other strategies. The eigen portfolio that weighed TSLA the most have the most volatility but its profits are also very high. Finally, as expected, the MVP has the minimum variance and ultimately the least profits. However, since the variance is extremely low, it is a good portfolio for those who want to stay safe. The most interesting part comes next, let us look at the forward or future test results for these portfolios. Forward Test Results These results are from April 29th, 2020 to September 4th, 2020. The eigen portfolio performed the best but it also had a lot of volatility. Moreover, most of those returns are due to TSLA rocketing in the last few months. After that, our GA algorithm worked quite effectively as it beat the market index. Again, as expected, the MVP had the lowest risk and reward and slowly went up in 4-5 months. This shows the effectiveness and power of these algorithmic portfolio optimization strategies where we've developed different portfolios for different kinds of risk and reward profiles. Conclusion and Discussion We are happy to share this toolkit with the trading community and hope that people will like and contribute to it. As is the case with everything in trading, these strategies are not perfect but they are based on rigorous theory and some great empirical results. Please take care when trading with these strategies and always manage your risk. The above results were not cherry picked but the market has been highly bullish in the last few months which has led to the strong results shown above. We would love for the community to try out different strategies and share them with us. Special Thanks Special thanks to Scott Rome's blog. The eigen portfolios and minimum variance portfolio concepts came from his blog posts. The code for filtering eigen values of the covariance matrix was also mostly obtained from one of his posts. License A product by Tradytics Copyright (c) 2020-present, Tradytics.com

OpenAI-CLIP
github
LLM Vibe Score0.507
Human Vibe Score0.015912940499642817
moein-shariatniaMar 27, 2025

OpenAI-CLIP

Update (December 2023) I am happy to find out that this code has been used and cited in the following papers: Domino: Discovering Systematic Errors with Cross-Modal Embeddings by Eyuboglu et. al. at ICLR 2022 GSCLIP : A Framework for Explaining Distribution Shifts in Natural Language by Zhu et. al. at ICML 2022 UIC-NLP at SemEval-2022 Task 5: Exploring Contrastive Learning for Multimodal Detection of Misogynistic Memes by Cuervo et. al. at SemEval-2022 cdsBERT - Extending Protein Language Models with Codon Awareness by Hallee et. al. from University of Delaware (Sep 2023) ENIGMA-51: Towards a Fine-Grained Understanding of Human-Object Interactions in Industrial Scenarios by Ragusa et. al. (Nov 2023) You can find the citation info on the right section of this GitHub repo page named: Cite this repository or use the below citation info. Introduction It was in January of 2021 that OpenAI announced two new models: DALL-E and CLIP, both multi-modality models connecting texts and images in some way. In this article we are going to implement CLIP model from scratch in PyTorch. OpenAI has open-sourced some of the code relating to CLIP model but I found it intimidating and it was far from something short and simple. I also came across a good tutorial inspired by CLIP model on Keras code examples and I translated some parts of it into PyTorch to build this tutorial totally with our beloved PyTorch! What does CLIP do? Why is it fun? In Learning Transferable Visual Models From Natural Language Supervision paper, OpenAI introduces their new model which is called CLIP, for Contrastive Language-Image Pre-training. In a nutshell, this model learns the relationship between a whole sentence and the image it describes; in a sense that when the model is trained, given an input sentence it will be able to retrieve the most related images corresponding to that sentence. The important thing here is that it is trained on full sentences instead of single classes like car, dog, etc. The intuition is that when trained on whole sentences, the model can learn a lot more things and finds some pattern between images and texts. They also show that when this model is trained on a huge dataset of images and their corresponding texts, it can also act as a classifier too. I encourage you to study the paper to learn more about this exciting model and their astonishing results on benchmarking datasets . To mention just one, CLIP model trained with this strategy classifies ImageNet better than those SOTA models trained on the ImageNet itself optimized for the only task of classification! As a teaser (!), let's see what the final model that we will build in this article from scratch is capable of: given a query (raw text) like "a boy jumping with skateboard" or "a girl jumping from swing", the model will retrieve the most relevant images: !title_img Let's see some more outputs: Config A note on config and CFG: I wrote the codes with python scripts and then converted it into a Jupyter Notebook. So, in case of python scripts, config is a normal python file where I put all the hyperparameters and in the case of Jupyter Notebook, its a class defined in the beginning of the notebook to keep all the hyperparameters. Utils Dataset As you can see in the tittle image of this article, we need to encode both images and their describing texts. So, the dataset needs to return both images and texts. Of course we are not going to feed raw text to our text encoder! We will use DistilBERT model (which is smaller than BERT but performs nearly as well as BERT) from HuggingFace library as our text encoder; so, we need to tokenize the sentences (captions) with DistilBERT tokenizer and then feed the token ids (input_ids) and the attention masks to DistilBERT. Therefore, the dataset needs to take care of the tokenization as well. Below you can see the dataset's code. Below that I'll explain the most important things that is happening in the code. In the \\init\\ we receive a tokenizer object which is actually a HuggingFace tokinzer; this tokenizer will be loaded when running the model. We are padding and truncating the captions to a specified maxlength. In the \\getitem\\ we will first load an encoded caption which is a dictionary with keys inputids and attention_mask, make tensors out of its values and after that we will load the corresponding image, transform and augment it (if there is any!) and then we make it a tensor and put it in the dictionary with "image" as the key. Finally we put the raw text of the caption with the key "caption" in the dictionary only for visualization purposes. I did not use additional data augmentations but you can add them if you want to improve the model's performance. Image Encoder The image encoder code is straight forward. I'm using PyTorch Image Models library (timm) here which makes a lot of different image models available from ResNets to EfficientNets and many more. Here we will use a ResNet50 as our image encoder. You can easily use torchvision library to use ResNets if you don't want to install a new library. The code encodes each image to a fixed size vector with the size of the model's output channels (in case of ResNet50 the vector size will be 2048). This is the output after the nn.AdaptiveAvgPool2d() layer. Text Encoder As I mentioned before, I'll use DistilBERT as the text encoder. Like its bigger brother BERT, two special tokens will be added to the actual input tokens: CLS and SEP which mark the start and end of a sentence. To grab the whole representation of a sentence (as the related BERT and DistilBERT papers point out) we use the final representations of the CLS token and we hope that this representation captures the overall meaning of the sentence (caption). Thinking it in this way, it is similar to what we did to images and converted them into a fixed size vector. In the case of DistilBERT (and also BERT) the output hidden representation for each token is a vector with size 768. So, the whole caption will be encoded in the CLS token representation whose size is 768. Projection Head I used Keras code example implementation of projection head to write the following in PyTorch. Now that we have encoded both our images and texts into fixed size vectors (2048 for image and 768 for text) we need to bring (project) them into a new world (!) with similar dimensions for both images and texts in order to be able to compare them and push apart the non-relevant image and texts and pull together those that match. So, the following code will bring the 2048 and 768 dimensional vectors into a 256 (projection_dim) dimensional world, where we can compare them. "embeddingdim" is the size of the input vector (2048 for images and 768 for texts) and "projectiondim" is the the size of the output vector which will be 256 for our case. For understanding the details of this part you can refer to the CLIP paper. CLIP This part is where all the fun happens! I'll also talk about the loss function here. I translated some of the code from Keras code examples into PyTorch for writing this part. Take a look at the code and then read the explanation below this code block. Here we will use the previous modules that we built to implement the main model. The \\init\\ function is self-explanatory. In the forward function, we first encode the images and texts separately into fixed size vectors (with different dimensionalities). After that, using separate projection modules we project them to that shared world (space) that I talked about previously. Here the encodings will become of similar shape (256 in our case). After that we will compute the loss. Again I recommend reading CLIP paper to get it better but I'll try my best to explain this part. In Linear Algebra, one common way to measure if two vectors are of similar characteristics (they are like each other) is to calculate their dot product (multiplying the matching entries and take the sum of them); if the final number is big, they are alike and if it is small they are not (relatively speaking)! Okay! What I just said is the most important thing to have in mind to understand this loss function. Let's continue. We talked about two vectors, but, what do we have here? We have imageembeddings, a matrix with shape (batchsize, 256) and textembeddings with shape (batchsize, 256). Easy enough! it means we have two groups of vectors instead of two single vectors. How do we measure how similar two groups of vectors (two matrices) are to each other? Again, with dot product (@ operator in PyTorch does the dot product or matrix multiplication in this case). To be able to multiply these two matrices together, we transpose the second one. Okay, we get a matrix with shape (batchsize, batchsize) which we will call logits. (temperature is equal to 1.0 in our case, so, it does not make a difference. You can play with it and see what difference it makes. Also look at the paper to see why it is here!). I hope you are still with me! If not it's okay, just review the code and check their shapes. Now that we have our logits, we need targets. I need to say that there is a more straight forward way to obtain targets but I had to do this for our case (I'll talk about why in a next paragraph). Let's consider what we hope that this model learns: we want it to learn "similar representations (vectors)" for a given image and the caption describing it. Meaning that either we give it an image or the text describing it, we want it to produce same 256 sized vectors for both. Check the cell below this code block for the continue of the explanations So, in the best case scenario, textembeddings and imageembedding matricies should be the same because they are describing similar things. Let's think now: if this happens, what would the logits matrix be like? Let's see with a simple example! So logits, in the best case, will be a matrix that if we take its softmax, will have 1.0s in the diagonal (An identity matrix to call it with fancy words!). As the loss function's job is to make model's predictions similar to targets (at least in most cases!), we want such a matrix as our target. That's the reason why we are calculating imagessimilarity and textssimilarity matrices in the code block above. Now that we've got our targets matrix, we will use simple cross entropy to calculate the actual loss. I've written the full matrix form of cross entropy as a function which you can see in the bottom of the code block. Okay! We are done! Wasn't it simple?! Alright, you can ignore the next paragraph but if you are curious, there is an important note in that. Here's why I didn't use a simpler approach: I need to admit that there's a simpler way to calculate this loss in PyTorch; by doing this: nn.CrossEntropyLoss()(logits, torch.arange(batch_size)). Why I did not use it here? For 2 reasons. 1- The dataset we are using has multiple captions for a single image; so, there is the possibility that two identical images with their similar captions exist in a batch (it is rare but it can happen). Taking the loss with this easier method will ignore this possibility and the model learns to pull apart two representations (assume them different) that are actually the same. Obviously, we don't want this to happen so I calculated the whole target matrix in a way that takes care of these edge cases. 2- Doing it the way I did, gave me a better understanding of what is happening in this loss function; so, I thought it would give you a better intuition as well! Train Here are some funtions to help us load train and valid dataloaders, our model and then train and evaluate our model on those. There's not much going on here; just simple training loop and utility functions Here's a handy function to train our model. There's not much happening here; just loading the batches, feeding them to the model and stepping the optimizer and lr_scheduler. Running the next cell start training the model. Put the kernel on GPU mode. Every epoch should take about 24 minutes on GPU (even one epoch is enough!). It can take one minute before training actually starts because we are going to encode all the captions once in the train and valid dataset, so please don't stop it! Every thing is working fine. Inference Okay! We are done with training the model. Now, we need to do inference which in our case will be giving the model a piece of text and want it to retrieve the most relevant images from an unseen validation (or test) set. Getting Image Embeddings In this function, we are loading the model that we saved after training, feeding it images in validation set and returning the imageembeddings with shape (validset_size, 256) and the model itself. Finding Matches This function does the final task that we wished our model would be capable of: it gets the model, image_embeddings, and a text query. It will display the most relevant images from the validation set! Isn't it amazing? Let's see how it performs after all! This is how we use this function. Aaaannnndddd the results: Final words I hope you have enjoyed this article. Implementing this paper was a really interesting experience for me. I want to thank Khalid Salama for the great Keras code example he provided which inspired me to write something similar in PyTorch.

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

machine-learning-blackjack-solution

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

Overmind
github
LLM Vibe Score0.469
Human Vibe Score0.20474237922306593
bencbartlettMar 23, 2025

Overmind

[](https://github.com/bencbartlett/Overmind/releases) [](https://github.com/bencbartlett/Overmind/blob/master/CHANGELOG.md) [](https://bencbartlett.github.io/overmind-docs/) [](https://github.com/bencbartlett/Overmind/wiki) [](https://screeps.slack.com/messages/overmind) [](https://github.com/bencbartlett/Overmind/issues/new) [](https://github.com/bencbartlett/Overmind/issues/new?template=feature_request.md) Current release: Overmind v0.5.2 - Evolution See the changelog for patch notes Documentation is available at the documentation site and the wiki Join the discussion in the #overmind Slack channel! Read blog posts about development Submit an issue here or request a feature here Find me in game here About Overmind What is Screeps? Screeps is an MMO strategy game for programmers. The core objective is to expand your colony, gathering resources and fighting other players along the way. To control your units, you code an AI in JavaScript; everything from moving, mining, building, fighting, and trading is entirely driven by your code. Because Screeps is an MMO, it takes place on a single server that runs 24/7, populated by every other player and their army of creeps. When you log off, your population continues buzzing away with whatever task you set them. Screeps pits your programming prowess head-to-head with other people to see who can think of the most efficient methods of completing tasks or imagine new ways to defeat enemies. What is Overmind? Overmind is my personal codebase that I run on the public server. The structure of the AI is themed loosely around the Zerg's swarm intelligence from Starcraft. Overlords orchestrate Creep actions within each Colony, and the colony Overseer places Directives to adapt to stimuli. Finally, the Assimilator allows all players running Overmind to act as a collective hivemind, sharing creeps and resources and responding jointly to a master ledger of all directives shared by all players. The AI is entirely automated, although it can also run in manual or semiautomatic mode. The latest release should work right out of the box; however, if you find something broken, please submit an issue and I'll try to fix it. Can I use Overmind as my bot? If you're new to Screeps, I would definitely recommend writing your own AI: most of the fun of the game is programming your own bot and watching your little ant farm run! However, I've tried to make the codebase readable and well-documented, so feel free to fork the project or use it as inspiration when writing your AI. If you still want to use Overmind on the public server, that's okay too - there are a number of people already doing this. But please realize that using a mature AI like this gives you a huge advantage over other new players, so don't go out of your way to ruin someone else's fun. In the future, I will be implementing methods for novice players to opt out of excessive aggression by Overmind bots (as long as they don't start a conflict and stay out of its way). Installation Out of the box If you just want to run Overmind without modification, you can copy the compiled main.js file attached to the latest release into your script. While Overmind is fully automated by default, it can be run with varying levels of autonomy; refer to the Overmind wiki for how to configure and operate the bot. Compiling from source To install the full codebase, download or clone the repository. (Please note that while the latest release of Overmind should always be stable, the latest commit may contain unstable features.) Navigate to the Overmind root directory and run . To compile and deploy the codebase, create a screeps.json file from the example file, then do one of the following actions: Compile and deploy to public server: npm run push-main Compile and deploy to private server: npm run push-pserver Compile without deploying: npm run compile Overmind uses rollup to bundle the compiled TypeScript into a single main.js file. The codebase includes functionality to compute checksums for internal validation - if you have a different version of rollup installed globally, different checksums may be computed and some functionality will be disabled. Please ensure the local installation of rollup found in node_modules is used. Setting up the Grafana dashboard Overmind includes a Grafana dashboard (shown below) which tracks detailed operating statistics. To set up the dashboard: Register for grafana service at screepspl.us Setup the ScreepsPlus hosted agent (simpler) or use the NodeJS agent on a free micro instance of Google Compute. Import the dashboard from Overmind.json and change $User to your username. Enjoy your pretty graphs! Design overview Check out the Overmind wiki for in-depth explanations of parts of the design of the AI. (Click the diagram below to see a higher-resolution version.)

Karpathy Vibe Coding Full Tutorial with Cursor (Zero Coding)
youtube
LLM Vibe Score0.193
Human Vibe Score0.37
Riley BrownFeb 6, 2025

Karpathy Vibe Coding Full Tutorial with Cursor (Zero Coding)

Today we talked about the concept and execution of vibe coding, a method where you speak your coding ideas into existence using cutting‐edge AI tools. We explored how to use Cursor Composer alongside Sonnet and WhisperFlow to generate, edit, and run code with minimal manual intervention. The tutorial guided viewers through setting up a project from a Next.js template, cloning a repository, and managing API keys through an .env file to maintain secure credentials. Additionally, the video detailed the process of building a ChatGPT clone using the latest OpenAI API, complete with real-time debugging and iterative improvements on design elements such as input fields, sidebars, and smooth text animations. The discussion also emphasized the importance of keeping the AI prompt context minimal for optimal performance, and it provided insights on how to save and upload projects to GitHub effortlessly. Finally, we touched on integrating real-time voice interaction using the 11Labs API to further enhance the coding experience and pay homage to AI pioneers like Karpathy Footnotes Perplexity Spaces (Just like Custom GPT's) Prompt: i am making app in nextjs: user is going to give input that they want to put in their site: you're job is to find a method to do that: describe what the api does, then output example code. then put a direct link to find the api key. Links: Whispr Flow - https://wisprflow.ai/ Cursor - https://www.cursor.com/ Cursor for Writing: https://app.yapthread.com/ Community of Vibe Coders: https://www.softwarecomposer.com/ Time Stamps: 00:00 Intro to Vibe Coding 03:02 Opening Cursor 04:07 Starting Your First Project 05:12 Building a ChatGPT Clone 06:38 Prompting, API's and Documentation Explanation 08:49 Using Perplexity 12:07 Vibe Code Prompt 1 13:58 Result of Vibe Coding Prompt 1 15:22 Seeing Prompt 2 15:43 Managing Cursor Composer Context Length 16:25 Prompt 3 - Designing 17:21 Debugging with Inspect on Web View 18:20 Fixing Formatting 19:04 More Vibing, Lol 20:51 Saving and Uploading Projects to GitHub 21:59 Enhancing the User Experience 22:33 Honoring Karpathy 26:26 Implementing Real Time Karpathy Voice 28:30 Getting Karpathys Voice (Don't Do this It's Illegal)

airflow-tutorial
github
LLM Vibe Score0.508
Human Vibe Score0.13240553426231688
hgrifJan 19, 2025

airflow-tutorial

Airflow tutorial This tutorial is loosely based on the Airflow tutorial in the official documentation. It will walk you through the basics of setting up Airflow and creating an Airflow workflow. This tutorial was published on the blog of GoDataDriven. Setup You can skip this section if Airflow is already set up. Make sure that you can run airflow commands, know where to put your DAGs and have access to the web UI. Install Airflow Airflow is installable with pip via a simple pip install apache-airflow. Either use a separate python virtual environment or install it in your default python environment. To use the conda virtual environment as defined in environment.yml in this git-repo: Install miniconda. Make sure that conda is on your path: Create the virtual environment from environment.yml: Activate the virtual environment: You should now have an (almost) working Airflow installation. Alternatively, install Airflow yourself by running: Airflow used to be packaged as airflow but is packaged as apache-airflow since version 1.8.1. Make sure that you install any extra packages with the right Python package: e.g. use pip install apache-airflow[dask] if you've installed apache-airflow and do not use pip install airflow[dask]. Leaving out the prefix apache- will install an old version of Airflow next to your current version, leading to a world of hurt. You may run into problems if you don't have the right binaries or Python packages installed for certain backends or operators. When specifying support for e.g. PostgreSQL when installing extra Airflow packages, make sure the database is installed; do a brew install postgresql or apt-get install postgresql before the pip install apache-airflow[postgres]. Similarly, when running into HiveOperator errors, do a pip install apache-airflow[hive] and make sure you can use Hive. Run Airflow Before you can use Airflow you have to initialize its database. The database contains information about historical & running workflows, connections to external data sources, user management, etc. Once the database is set up, Airflow's UI can be accessed by running a web server and workflows can be started. The default database is a SQLite database, which is fine for this tutorial. In a production setting you'll probably be using something like MySQL or PostgreSQL. You'll probably want to back it up as this database stores the state of everything related to Airflow. Airflow will use the directory set in the environment variable AIRFLOW_HOME to store its configuration and our SQlite database. This directory will be used after your first Airflow command. If you don't set the environment variable AIRFLOW_HOME, Airflow will create the directory ~/airflow/ to put its files in. Set environment variable AIRFLOW_HOME to e.g. your current directory $(pwd): or any other suitable directory. Next, initialize the database: Now start the web server and go to localhost:8080 to check out the UI: It should look something like this: With the web server running workflows can be started from a new terminal window. Open a new terminal, activate the virtual environment and set the environment variable AIRFLOW_HOME for this terminal as well: Make sure that you're an in the same directory as before when using $(pwd). Run a supplied example: And check in the web UI that it has run by going to Browse -> Task Instances. This concludes all the setting up that you need for this tutorial. Tips Both Python 2 and 3 are be supported by Airflow. However, some of the lesser used parts (e.g. operators in contrib) might not support Python 3. For more information on configuration check the sections on Configuration and Security of the Airflow documentation. Check the Airflow repository for upstart and systemd templates. Airflow logs extensively, so pick your log folder carefully. Set the timezone of your production machine to UTC: Airflow assumes it's UTC. Workflows We'll create a workflow by specifying actions as a Directed Acyclic Graph (DAG) in Python. The tasks of a workflow make up a Graph; the graph is Directed because the tasks are ordered; and we don't want to get stuck in an eternal loop so the graph also has to be Acyclic. The figure below shows an example of a DAG: The DAG of this tutorial is a bit easier. It will consist of the following tasks: print 'hello' wait 5 seconds print 'world and we'll plan daily execution of this workflow. Create a DAG file Go to the folder that you've designated to be your AIRFLOWHOME and find the DAGs folder located in subfolder dags/ (if you cannot find, check the setting dagsfolder in $AIRFLOW_HOME/airflow.cfg). Create a Python file with the name airflow_tutorial.py that will contain your DAG. Your workflow will automatically be picked up and scheduled to run. First we'll configure settings that are shared by all our tasks. Settings for tasks can be passed as arguments when creating them, but we can also pass a dictionary with default values to the DAG. This allows us to share default arguments for all the tasks in our DAG is the best place to set e.g. the owner and start date of our DAG. Add the following import and dictionary to airflow_tutorial.py to specify the owner, start time, and retry settings that are shared by our tasks: Configure common settings These settings tell Airflow that this workflow is owned by 'me', that the workflow is valid since June 1st of 2017, it should not send emails and it is allowed to retry the workflow once if it fails with a delay of 5 minutes. Other common default arguments are email settings on failure and the end time. Create the DAG We'll now create a DAG object that will contain our tasks. Name it airflowtutorialv01 and pass default_args: With schedule_interval='0 0 *' we've specified a run at every hour 0; the DAG will run each day at 00:00. See crontab.guru for help deciphering cron schedule expressions. Alternatively, you can use strings like '@daily' and '@hourly'. We've used a context manager to create a DAG (new since 1.8). All the tasks for the DAG should be indented to indicate that they are part of this DAG. Without this context manager you'd have to set the dag parameter for each of your tasks. Airflow will generate DAG runs from the startdate with the specified scheduleinterval. Once a DAG is active, Airflow continuously checks in the database if all the DAG runs have successfully ran since the start_date. Any missing DAG runs are automatically scheduled. When you initialize on 2016-01-04 a DAG with a startdate at 2016-01-01 and a daily scheduleinterval, Airflow will schedule DAG runs for all the days between 2016-01-01 and 2016-01-04. A run starts after the time for the run has passed. The time for which the workflow runs is called the execution_date. The daily workflow for 2016-06-02 runs after 2016-06-02 23:59 and the hourly workflow for 2016-07-03 01:00 starts after 2016-07-03 01:59. From the ETL viewpoint this makes sense: you can only process the daily data for a day after it has passed. This can, however, ask for some juggling with date for other workflows. For Machine Learning models you may want to use all the data up to a given date, you'll have to add the scheduleinterval to your executiondate somewhere in the workflow logic. Because Airflow saves all the (scheduled) DAG runs in its database, you should not change the startdate and scheduleinterval of a DAG. Instead, up the version number of the DAG (e.g. airflowtutorialv02) and avoid running unnecessary tasks by using the web interface or command line tools Timezones and especially daylight savings can mean trouble when scheduling things, so keep your Airflow machine in UTC. You don't want to skip an hour because daylight savings kicks in (or out). Create the tasks Tasks are represented by operators that either perform an action, transfer data, or sense if something has been done. Examples of actions are running a bash script or calling a Python function; of transfers are copying tables between databases or uploading a file; and of sensors are checking if a file exists or data has been added to a database. We'll create a workflow consisting of three tasks: we'll print 'hello', wait for 10 seconds and finally print 'world'. The first two are done with the BashOperator and the latter with the PythonOperator. Give each operator an unique task ID and something to do: Note how we can pass bash commands in the BashOperator and that the PythonOperator asks for a Python function that can be called. Dependencies in tasks are added by setting other actions as upstream (or downstream). Link the operations in a chain so that sleep will be run after printhello and is followed by printworld; printhello -> sleep -> printworld: After rearranging the code your final DAG should look something like: Test the DAG First check that DAG file contains valid Python code by executing the file with Python: You can manually test a single task for a given execution_date with airflow test: This runs the task locally as if it was for 2017-07-01, ignoring other tasks and without communicating to the database. Activate the DAG Now that you're confident that your dag works, let's set it to run automatically! To do so, the scheduler needs to be turned on; the scheduler monitors all tasks and all DAGs and triggers the task instances whose dependencies have been met. Open a new terminal, activate the virtual environment and set the environment variable AIRFLOW_HOME for this terminal, and type Once the scheduler is up and running, refresh the DAGs page in the web UI. You should see airflowtutorialv01 in the list of DAGs with an on/off switch next to it. Turn on the DAG in the web UI and sit back while Airflow starts backfilling the dag runs! Tips Make your DAGs idempotent: rerunning them should give the same results. Use the the cron notation for schedule_interval instead of @daily and @hourly. @daily and @hourly always run after respectively midnight and the full hour, regardless of the hour/minute specified. Manage your connections and secrets with the Connections and/or Variables. Exercises You now know the basics of setting up Airflow, creating a DAG and turning it on; time to go deeper! Change the interval to every 30 minutes. Use a sensor to add a delay of 5 minutes before starting. Implement templating for the BashOperator: print the executiondate instead of 'hello' (check out the original tutorial and the example DAG). Implement templating for the PythonOperator: print the executiondate with one hour added in the function printworld() (check out the documentation of the PythonOperator). Resources Data Pipelines with Apache Airflow Airflow documentation ETL best practices with Airflow Airflow: Tips, Tricks, and Pitfalls Kubernetes Custom controller for deploying Airflow

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

teach-AI-in-business

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

ai_primer
github
LLM Vibe Score0.347
Human Vibe Score0.0036202231602591754
trokasNov 20, 2024

ai_primer

Welcome to AI primer course INTERACTIVE BOOK LINK Main aim of this course is to give you enough information so that you can start exploring field of AI on your own and maybe even start searching for DS role. We have only 5 main chapters and one bonus lecture to cover. Unsupervised learning SVD (Singular Value Decomposition) - it’s a good tool to introduce both technical tools we will be working with as well as giving us a glimpse at unsupervised learning. Supervised learning RF (Random Forests) - one of the first “silver bullets” out there. Our discussion will also cover Shannon’s work on entropy as it’s one of the key ingredients. Deep learning DNN (Deep Neural Networks) - we will build our own Perceptron from scratch, thus focusing on gradient descent and backprop on the way. By changing activation function logistic regression will be introduced and finally we will explore what a stack of layers (deep NN) can offer. CNN (Convolutional Neural Networks) - even though different techniques come and go in deep learning world I strongly believe that CNN’s will be around for quite some time to come. We will use them not only for images, but also for time series prediction. Attention - powerful idea that stands behind Transformers and one of the enablers for GPT-3, DALL-E 2 and others. Reinforcement Learning (bonus lecture) TD (Temporal Difference) - one of the core principles in reinforcement learning. We will apply it to play tic-tac-toe. Also we will cover following toolset, which hopefully will be useful for your future projects: numpy (mainly in SVD and FCN lectures) - will help us store vectors, matrices and perform operations on them. matplotlib (in all lectures) - nice and simple plotting lib. scikit-learn - ML library. pandas (mainly in RF lecture) - structured way of looking at tabular data. PyTorch (FCN and CNN lectures) - simple deep learning library based on tensorflow. git (final project) - version control tool. Toolset will be presented only in lectures, thus it’s up to you to learn them on your own if you do not plan to attend. There are a lot of resources, but I highly suggest to read intros in corresponding docs. What to expect from a single lecture? There will be no clear distinction between theory and practice, thus you should have your PC ready for small assignments that you will encounter on the way. Most important material will be listed here, but during lectures you will hear and see a lot of complementary material. Each lecture will end with a list of resources (some of them mandatory). We will start a new lecture with a recap of what was done last time and discussion regarding mentioned resources in the hope to deepen understanding in the subject and inspire you to search for sources and publications yourself. Launching notebooks You can launch notebooks while in interactive book by simply pressing the rocket logo and choosing Colab. To get faster run times click Runtime and Change runtime type, then select GPU or TPU. If necessary you can install missing packages by running !pip install [package name] directly in the notebook. NOTE: Colab will not save your changes between sessions! Download the notebook or save a copy in Google Drive before closing the browser. If you want to open notebooks locally (for a quick preview) you might find nteract useful. As an alternative you can use non free, but cheap options like Jarvislabs or Paperspace. Actually Paperspace has free GPU option, but often it is not available. (re)Sources Each chapter will have a list of resources, but for now I highly recommend to start listening/watching following resources on your spare time: Data Skeptic podcast Artificial Intelligence podcast Two Minute Papers youtube channel If I had to recommend a single book for beginner it will be this one - Hands-On Machine Learning with Scikit-Learn, Keras, and TensorFlow, 2nd Edition.

Google’s AI Course for Beginners (in 10 minutes)!
youtube
LLM Vibe Score0.444
Human Vibe Score0.91
Jeff SuNov 14, 2023

Google’s AI Course for Beginners (in 10 minutes)!

Grab my AI Toolkit for free: https://academy.jeffsu.org/ai-toolkit?utmsource=youtube&utmmedium=video&utm_campaign=146 Grab my free Workspace Toolkit: https://academy.jeffsu.org/workspace-toolkit?utmsource=youtube&utmmedium=video&utm_campaign=146 🔍 In this video, we unravel the layers of AI, Machine Learning, Deep Learning, and their applications in tools like #ChatGPT and Google #Bard We first go through how AI is a broad field of study that encompasses #MachineLearning as a sub-field. We then break down Machine Learning into supervised and unsupervised models, using real-world examples to illustrate their functions and differences. We move deeper into Deep Learning: Learn about artificial neural networks and the power of semi-supervised learning in applications like fraud detection in banking. Then we delve into Generative AI, differentiating it from discriminative models and demonstrating its capabilities in creating new, innovative outputs. Finally we walk through Large Language Models (LLMs) and uncover the significance of LLMs in AI, their pre-training processes, and their customization for specific industry applications TIMESTAMPS 00:00 Google’s AI Course in 10 Minutes 00:38 What is Artificial Intelligence? 01:27 What is Machine Learning? 03:28 What is Deep Learning? 05:15 What is Generative AI? 07:05 What are Large Language Models? RESOURCES I MENTION IN THE VIDEO Google’s full course: https://www.cloudskillsboost.google/course_templates/536 Grab my free Workspace Toolkit: https://academy.jeffsu.org/workspace-toolkit?utmsource=youtube&utmmedium=video&utm_campaign=146 MY FAVORITE GEAR 🎬 My YouTube Gear - https://www.jeffsu.org/yt-gear/ 🎒 Everyday Carry - https://www.jeffsu.org/my-edc/ MY TOP 3 FAVORITE SOFTWARE ❎ CleanShot X - https://geni.us/cleanshotx ✍️ Skillshare - https://geni.us/skillshare-jeff 📖 Readwise - https://readwise.io/jeffsu/ BE MY FRIEND: 📧 Subscribe to my Productivity newsletter - https://www.jeffsu.org/productivity-ping/ 📸 Instagram - https://instagram.com/j.sushie 🤝 LinkedIn - https://www.linkedin.com/in/jsu05/ 👨🏻‍💻 WHO AM I: I'm Jeff, a tech professional trying to figure life out. What I do end up figuring out, I share! PS: Some of the links in this description are affiliate links I get a kickback from and my opinions are my own and may not reflect that of my employer 😇