Hi everyone,
I’m struggling, but I’m also incredibly proud.
Balancing a warehouse job with learning to code from scratch at 50 is… a lot. The technical terms, the acronyms, and the "brain fog" mean I have to write everything down or it’s gone. But then, there are the "magic moments."
The first time my app Onfoot’s map worked perfectly? Unbelievable. When I see Triply generating precise itineraries or Laura (my AI assistant) offering advice exactly as I envisioned? It makes the sleepless nights and the stress of starting this from zero feel worth it.
I started with a dream and a Celeron N4000. The idea evolved, but the PC… not so much! haha. I began with React Native, which was a nightmare of compilation errors (Java almost broke me). I spent so many nights wanting to quit. Then, I discovered Claude and Flutter, and the clouds finally cleared.
But now, I’m at a crossroads.
I need to scale. I need to ensure the backend can handle real traffic and that everything won't crash. I've received amazing advice here, and many of them make me believe that I need help. So, I have to ask:
How do I find the right person? How do you trust someone else with your "babies" (my projects)?
What are the legal/contractual terms? What "rights" does someone get the moment they touch my code?
Co-founder vs. Freelancer? I don't want someone just doing a job; I want someone to love these projects as much as I do. But is that even possible if they didn't suffer through the "Celeron phase" with me?
If you were in my shoes—balancing a physical job, 50 years of life experience, and a growing startup—what would you do? How do I protect what I’ve built while giving it the wings it needs to fly?
Would love to hear your thoughts.
I'm finally back! My trusty old PC decided to give me some serious trouble, which cost me days of not being able to do anything or push any code. But the setup is finally back alive, and I'm ready to get back to action. Time to make up for lost time!
Your journey sounds incredibly challenging, especially balancing everything. I actually know a few experienced solo founders who have scaled projects who would probably be happy to answer your questions, I could ask them for you.
That is incredibly kind of you, thank you so much! Honestly, navigating things as a solo founder is always a balancing act, so I would absolutely love to connect with them and hear their insights.
Right now, my biggest focus is sustainable growth and managing infrastructure risks (like API constraints), so chatting with founders who have been through the scaling phase would be invaluable. Whenever you have a chance, I’d deeply appreciate the intro! Thank you again.
Shipping Onfoot and Triply on a Celeron is the ultimate proof of your engineering grit, so ensure any collaborator signs a "Work Made for Hire" agreement to keep your IP secure. A freelancer can fix your immediate scaling issues without costing equity, whereas a co-founder must earn their way through the same "sleepless night" dedication you've shown. Start with small, isolated tasks to test their technical skills and cultural fit before handing over the keys to your ecosystem.
What is the biggest technical bottleneck currently stopping Onfoot or Triply from handling more users?
Haha, thank you for the engineering grit compliment! Shipping on a Celeron definitely builds character (and very optimized code). Also, I really appreciate the solid advice on IP and hiring freelancers vs. co-founders. That’s a great rule of thumb to protect what I've built.
To answer your question about the bottlenecks:
Right now, Onfoot is actually in the middle of its 5th review process for official approval. It's been a journey, but I truly believe it’s going to be approved this time!
As for Triply, the bottleneck isn't exactly code anymore, but budget and distribution. It's in a purely organic growth phase because I don't have a big budget for paid ads right now. I'm doing everything I can with what I have. Currently, I have 132 active daily users, but total revenue is only €35—and full disclosure: €27 of that came from a test booking I made myself just to test the system, haha!
So the real challenge right now is turning that organic user engagement into sustainable revenue before even worrying about server scaling. One step at a time!
Thanks for your reply. Our team's service, Bunzee, is in the exact same boat. It's been two months since we launched, but our total revenue is $0. A few days ago, a payment notification popped up. I got so excited and asked our CEO about it, only to hear, "I just did that for testing." It really feels like I've met a true comrade here.
Haha. Oh no! That 'test payment' excitement crash is too real! It really is an indie hacker rite of passage.
Thank you so much for sharing that, it definitely makes the journey feel less lonely knowing we are in the exact same boat. Hang in there with Bunzee—two months is just the beginning! Let's keep working hard. The real notifications are coming for both of us soon. Best of luck to you and your CEO!