
Yulo
882 posts

Sabitlenmiş Tweet

After 9 months of discovering what "SaaS" means and having launched Vidalgo 7 months ago,
here are the 13 mistakes I will avoid in the future 👇
1/ Using NoCode: Probably one of my biggest regrets today is thinking that because I haven't been coding since birth, it would be impossible to learn while launching an app (even though it is probably the best thing to do). We ended up using Bubble and spent just as much time understanding the app as we would have learning a typical stack.
2/ We lost an enormous amount of time learning a pseudo programming language (Bubble), and because we didn’t "understand" what we were doing, we were literally unable to launch certain features that users requested. The ecosystem is also much more limited than coding, and backend functionalities offer very few possibilities, making you heavily dependent on a vast number of APIs (which destroys your margins and makes you extremely vulnerable to a complete app interruption).
3/ Another huge mistake that cost us dearly (literally) was spending an obscene amount of cash on fixed costs (API and tools). You regret it bitterly when it's time to give money to Mark for Meta Ads or just to pay some influencers.
4/ As I mentioned earlier, we had to use many APIs, especially for video generation since we couldn't use Remotion with Bubble (or at least had no idea how to integrate it). We had to significantly reduce our margin and were limited in video generation since we couldn't have pre-rendering like with Remotion and didn’t have pay-per-use but subscription-based services.
5/ Our execution was disastrous. This is probably what cost us the most out of everything. We spent an infinite amount of time deciding whether to do this or that. No prioritization of important tasks, constantly seeking perfection. And then suddenly, we wake up and realize that boom, almost 8 months have passed, and we're far from achieving what we set out to do. Just to tell you, we had the idea to launch Vidalgo in December 2023 and released a beta version around February, well before a huge number of other competitors arrived (who did very well, by the way). They all came well after us but surpassed us by moving extremely quickly while we were literally struggling. Well played to them!
6/ Not defining our ICP. A very classic mistake, but I guess everyone goes through it. It cost us an infinite amount of time concentrating our energy on things that simply did not target our actual user base. Never again will we make this mistake. It's simple yet saves a huge amount of time. You stop talking to everyone foolishly, thinking you can reach 8 billion humans.
7/ Wanting to "innovate" in terms of UI. That's over for us as well. We learned the hard way that we are not designers and that from now on, it will be very simple: UI kit + designs that have already proven themselves. That's it. Too much mental energy wasted unnecessarily on a blank Figma page.
8/ Speaking of Figma, one thing I won’t do again is jumping into creating the interface for real, thinking I have a "brilliant plan in my head," only to spend hours and hours modifying everything, hoping to stumble upon the perfect design. Always start with a Figma mockup in the future before beginning.
9/ NOT TALKING TO YOUR CUSTOMERS!!! You might think this is another silly mistake and that everyone keeps repeating it. And yes, you're right! We did it very early on but quickly lost the habit, and it showed in the product. We started making modifications and releasing features that were not at all relevant. Even a small message from time to time to some customers on Discord, for example, doesn't hurt. And given our execution problem, I might place this mistake as equally important. The worst part is that it seems so cliché, but I think by doing completely useless things, we forget to focus on the fundamental pillars.
10/ Not directly related to the product itself, but not having installed @rize_io and an extension to block X and YouTube until 5 pm also cost us a lot of time. (Rize is really amazing; I'm literally in love with the product.)
11/ Paying for AI tool directories. While it might be a good idea, for us, honestly, aside from wasting money, it didn't do anything significant. I think it mainly depends on the product in the end, but I don’t think it’s the most worthwhile investment at the beginning (especially for expensive paid directories).
12/ Underestimating the power of organic content (TikTok, Shorts, Reels...) was also a fatal mistake for a B2C product like ours. In fact, for a very long period, we did the exact opposite of what we should have done in marketing by focusing more on B2B channels instead of B2C. It’s very stupid, I know, but oh well 🤷♂️
13/ Creating a full AI product, especially for our very first SaaS, is clearly suicidal ahaha 😅. The number of APIs and agents we have to manage, models becoming temperamental overnight and needing to be changed quickly, the new image models with their very strange prompting rules that need to be understood, in short, it’s a nightmare to manage. Moreover, all these little APIs have a cost that significantly reduces your margin, especially at the beginning when you stay on some very expensive entry-level plans (Elevenlabs...). And the "random" results are also difficult to tame while doing everything possible to have something relatively stable and functional.
----> All these cumulative mistakes made us miss an excellent opportunity and momentum that was right in front of our eyes.
But in the end, the most important and precious thing for us is all that we have learned during this journey. This product has mainly provided us with valuable resources that are now deeply ingrained in us and that we will be able to use for every new product. It has brought us much more than any training or other similar experiences. We learned everything from scratch about marketing and development thanks to this wonderful community, which is of inestimable value and constantly provides value daily. Thank you, indie hackers! 🤝
English

@yulo_tech Unit economics won’t allow them to win the market unless they own their own foundational model.
English

PostHog will destroy Claude Code and Codex
The moat they'll have from user behavior data and error logs will for the first time give AI tasks that are actually useful and not slop features or things that don't matter
Can't wait to try it
PostHog@posthog
Introducing PostHog Code, the product editor that: - Understands your product - Identifies usage patterns - Triages bugs and errors for you - Creates PRs to fix them - Continuously monitors and improves your product Join the waitlist: posthog.com/code
English

@MassExtract Acheter de l'equity d'une boite en lui refourguant des tokens
x.com/bosmeny/status…
Tyler Bosmeny@bosmeny
A mic drop moment @ycombinator tonight @sama just offered $2M in OpenAI tokens to EVERY YC startup in the current batch in exchange for equity Just like Yuri Milner offering to invest in every startup back when Sam was a YC partner I can't wait to see what's unlocked when you let the most driven, creative and formidable founders tokenmaxx
Français

@taka_shirasu Ask him to refactor the codebase in 3 different languages and you'll be done
English

@JaredDHardin Did the same with all mainstream news too and it's clearly one of the best things you can do for your lifespan
English

I am addicted to politics and i need to stop paying it any attention, at least for now.
I find it incredibly intellectually stimulating and it's obviously insanely consequential, but it's a net negative in my life.
I get so frustrated and mad about the current state of our country and our leaders blatant disrespect and disregard for America and Americans, and it throw off my entire day.
I am going to be doing my absolute best to focus solely on my relationship with God, my marriage, my health, and my business.
If any of you see me post something political please remind me that I'm wasting time and energy.
I love you all
<3
English

@ninepixelgrid Me: Is it secure?
Claude: Yes everything is fine
Me: Are you sure? Check again
Claude: You're right, I need to add auth to that route
🫠
English

i need to write a huge playbook with all the answers to these questions
have 0 time rn
if you find me a copywriter that spends 5h interviewing me, I can get the playbook out next week
Yulo@yulo_tech
@antinertia What do you use to calculate CAC? Or do you use another metric to decide whether to stop the collaboration?
English

Si tu as une agence ou tu fais de la presta pour des infopreneurs.
Voilà comment @Whoscale_io change ta façon de travailler :
→ Tu améliores les résultats de tes clients existants
Tu accèdes aux ads/tunnels des meilleurs de leur marché.
Tu vois ce qui tourne depuis longtemps, les angles qui convertissent, les tunnels qui scalent.
Tes recommandations sont backées par ce que le marché valide en ce moment.
→ Tu trouves de nouveaux clients dans ta cible
Tu filtres par niche.
Tu identifies les infopreneurs qui dépensent déjà sur Meta, ceux qui ont un budget et qui scalent ou alors ceux qui ont du mal à se développer.
Tu prospectes plus à l'aveugle.
Si tu as une agence ou tu es prestataire dans l'infoproduit et que tu veux arrêter de travailler sans data…
@Whoscale_io c'est clairement est l'outil qu'il te manquait
Français

I've been using GitHub for over 10 years.
what's been happening over the past weeks is a disaster.
is it Microsoft's fault?
is it AI?
I don't know.
What I do know is, software wouldn't be the same without them.
All my adult developer life I have spent on this platform: hosting my code, collaborating, finding open source projects that have saved me months of work?
The value we got from this platform is immeasurable.
I think we owe them some time to sort this out.
I honestly want the to land back on their feet and come stronger out of this.
Sending warm thoughts to the engineers having to put out all these fires, I hope you get some sleep soon 🫡

English

@om_patel5 You can't have a simple crisp/intercom chat like everyone else @AnthropicAI?
English

THIS GUY PAID $118 FOR CLAUDE MAX AND WHEN SUPPORT IGNORED HIM FOR DAYS HE SERVED A FORMAL LEGAL NOTICE TO ANTHROPIC'S OFFICE
paid for max, had issues, and contacted support.
got the classic AI bot loop and no human ever responded
so he drafted a formal legal notice and served it to anthropic's office himself
the funny thing is that he also used claude to draft the legal notice.
this is only one of many legal actions against anthropic this month. for example, an EU subscriber already filed a formal complaint under consumer protection law
a billion dollar company charging $118-200 a month with zero human support is becoming a pattern
their support bot is useless, their response time is days, and now paying customers are (finally) lawyering up
at some point anthropic has to decide if they want to be a premium product with premium support or a premium price with startup tier customer service
right now it's the second one

English

If you are a developer constantly switching between tools and models:
Just use @cursor_ai with Composer 2.5 and thank me later.
English














