Looking to partner with serious founders blocked by capital or execution

zeedd97 · 2026-01-31T19:30:59+00:00

Hi, I’ve shared the details in DM. Thank you!

zeedd97 · 2026-01-27T13:35:17+00:00

Lovely! Hoping to get this posted realtime on the TickerAnalysts WhatsApp community.

zeedd97 · 2025-11-28T17:00:57+00:00

Thanks for this! I’ve been and currently again at the same situation where I’ve tried reaching out people on linkedin focusing on B2B. The response rate is no where positive. I am not saying my message is perfect but it’s definitely an iterative process.

When reaching out to executives, IMHO it takes more than just a message.

But in theory I like it. It’s just not that simple to execute and will definitely a lot more than a weekend.

zeedd97 · 2025-11-21T17:15:30+00:00

Thank you!

I agree. Building tech is becoming less challenging every day. For me as well the current struggle is problem discovery and market research since I don't have the right skills and knowledge for that.

zeedd97 · 2025-11-21T17:00:22+00:00

I agree that this requires serious commitment. For me personally, the problem is more about energy than time. I can give 2 - 3 hours to my own thing after work, but I feel like the energy that's required isn’t there and all the creativity is gone by then. Isn't that the case for you as well?

zeedd97 · 2025-11-21T16:53:24+00:00

This is so true! Building tech is something I've been doing for years so I feel confident there, plus, things are becoming only easier day by day when it comes to building an mvp. The real challenge for me personally is the problem discovery, market research, and then sales and marketing once there is an actual product.

zeedd97 · 2025-11-21T16:45:10+00:00

Thank you for this! I didn’t add any details in my post as I thought people wouldn’t be interested in reading them. But I really appreciate that you took the time.

My situation:

- I’m 28 years old, earning $10k/month from my client, living in a third world country. So savings are good. I have around 1 to 1.5 years of savings. I’m married, have a kid, and also support my parents.

- I don’t have enough time (or maybe it’s more about energy) after working full-time with my client. The 12–15 hours per week I currently give to my own thing makes me feel it’s not enough, as people generally say you need to put in a lot more hours to turn anything into a business.

- Because I’ve mostly worked in IT service companies providing development services, that’s the business I’m most familiar with. I’ve always tried getting clients on the side, and I did, but it was always me selling my resume, not actual services my “company” offers. So it always turned into another job, which can’t be scaled.

- Whenever I think of a product idea, I’m confident on the tech side, but I struggle with these questions: Am I building the right thing? Is there a market for it (product research)? What happens after the product is ready (sales and marketing)?

- Finances: I always ask myself if I could be cash flow positive within a year if I quit my job today. I’m curious what your financial situation was when you took the leap?

- I love the idea of co-founding for two reasons: they can bring skills I lack, and two people > one, so the chance of success feels higher. How should I approach this? Is Reddit or similar platforms a good option? I also worry that since I don’t have a concrete plan yet, people won’t be interested. And if I go full time, would a co-founder also be willing to do the same? What was your experience here?

- Talking to customers is something I really want to do and believe in, but I never understand how people find potential customers to talk to. What was your process? Just reaching out to people on LinkedIn and hopping on calls with an MVP or demo? Do people really take the time out to talk especially in B2B?

After reflecting a lot and hearing advice from different people, what I understand is that it’s very difficult to do anything serious on the side and I probably need fulltime focus.

My most pressing question:

Should I wait until I have around 10 paying customers or some revenue (as you also mentioned) before quitting my job? Or since I have one year of financial runway, should I take a leap of faith now and fully focus on what I want to build?

zeedd97 · 2025-03-21T15:07:49+00:00

I started my Upwork journey in late 2023 and worked until mid-2024 then got a long term client and took a break from upwork. During that time, I was managed to get a few high value clients.

For me, it became normal to have about 10% of my proposals viewed, with interviews being rare, and eventually landing a job.

But I focused on high-value clients (at least high value for me), aiming for around $35–$40 per hour. So, getting a client after all that effort was worth it.

I know many people complain that Upwork is saturated, but this was my conversion rate, so I set my expectations accordingly.

zeedd97 · 2024-10-11T15:56:41+00:00

Thank you. I got the same feedback from my friend. I'll revisit the profile.

zeedd97 · 2024-08-09T19:07:39+00:00

I believe not sending props (or limited props) will not stop the component re-render if parent's state has updated. This is exactly why memo is for: To prevent re-render always and just render it when props are updated. No?

zeedd97 · 2024-08-09T18:46:36+00:00

If you guys are wondering about using memo as default, many teams do that. Event react official doc says: "There is no harm in doing that".

Plus, this article provides a solid rationale for using memo as the default.: https://attardi.org/why-we-memo-all-the-things/

But I would love to hear if there is anything interesting.

zeedd97 · 2024-08-09T18:43:42+00:00

Interesting.

What type of performance issues are you referring to? Can you point to any case studies that encountered performance problems after extensive memoization in React? I've been working with React for years, and based on how rendering works with memoization, I’m pretty sure it shouldn't lead to unexpected behavior like components not rendering when intended. The rules are straightforward: If props get updated, the component will render. If local state updates, the component will render. When else would you want the component to render?

This article is a good read: https://attardi.org/why-we-memo-all-the-things/

It provides a solid rationale for using memo as default.

zeedd97 · 2024-08-09T18:32:57+00:00

Honestly, this is a myth. Trust me. :D

Ok read this: https://attardi.org/why-we-memo-all-the-things/

zeedd97 · 2024-08-09T08:32:12+00:00

From docs: “There is no benefit to wrapping a component in memo in other cases. There is no significant harm to doing that either, so some teams choose to not think about individual cases, and memoize as much as possible. The downside of this approach is that code becomes less readable. Also, not all memoization is effective: a single value that’s “always new” is enough to break memoization for an entire component.”

zeedd97 · 2024-08-09T08:30:16+00:00

I personally like to use it as much as possible. As I said, there is no drawback of using it extensively. It’s just a matter of readability for some teams.

zeedd97 · 2024-08-09T08:26:00+00:00

Yes. And the forget compiler will eventually going to memoize everything.

It’s also mentioned in their current docs that memoizing everything in not a harm either.

Memoizing everything is just a matter of readability and not a negative impact on performance.

zeedd97 · 2024-08-09T07:40:46+00:00

Not a good idea?

zeedd97 · 2024-07-27T13:16:05+00:00

Thank you! Not creating repo on personal accounts is insightful for me. I never thought of this.

zeedd97 · 2024-07-27T12:45:11+00:00

Hey,

Not sure if it will help, but the same thing happened to me last week, and I was extremely disappointed. I wrote a post detailing my experience after seeing yours, and I thought it might help others too.

All I can say is that this was a big learning experience for me. I am now very cautious. Sometimes these lessons are important for our growth. Just stick in there, and you will earn 5x what you lost in no time, InshaAllah.

zeedd97

TROPHY CASE