u/No-Sink1088

Not necessarily the “best” one. I mean the one that tastes like school breaks, grandparents’ houses, train rides, tea time, or childhood chaos.

Name, country, and what does it taste like?

I'll kick it off: Cardamom rusk, india, best dunked in hot chai.

I’m looking for honest advice from founders who have been through this.

I’m building a B2C femtech product. I have angel investment in place, a validated problem space, beta users ready, and a strong GTM/customer understanding. My background is in growth, ops, and strategy at Silicon Valley tech companies, so I’m not coming at this from “I have an idea, someone build it for me.” I know the market, the user, the distribution problem, and the pain point deeply.

But I’ll be honest. I think I’ve been a little brainwashed by the YC-style advice that I NEED a technical co-founder before launching.

The technical co-founder search has been exhausting.

A few patterns I’m seeing:

1. Since this is femtech, I initially preferred a woman co-founder. But the pool of senior technical women interested in early-stage femtech is painfully small.
2. It’s surprisingly hard to get men who haven’t experienced hormonal or metabolic health issues to truly understand why this problem matters. Some intellectually get it, but the urgency is not always there.
3. When I do find technically strong people, many are very passive. I understand that conviction takes time, but if someone agrees to a work trial, I expect some real energy and ownership. Instead, it often feels like I’m trying to drag excitement out of them.
4. Most technical people say, “This is technically easy to build; GTM is the hard part.” Fair enough. But then they still want cash comp from the angel money, equal equity, and less downside risk, while I’m carrying the fundraising, customer validation, GTM, product direction, and early operating risk.

I’m starting to wonder if I should stop searching for the mythical perfect technical co-founder, hire a strong founding engineer, launch the beta, prove traction, and revisit the co-founder question later.

I know the standard advice is that B2C is hard, femtech is hard, and you want a true technical partner early. I get that. But at what point does waiting for the “right” technical co-founder become more damaging than just moving?

Would love advice from founders who have faced this decision.

• Did you wait for a technical co-founder?
• Did you hire a founding engineer instead?
• Did you regret either path?

And for non-technical founders who raised or built the first version without a technical co-founder, what would you do differently?

I’m looking for honest advice from founders who have been through this.

I’m building a B2C femtech product. I have angel investment in place, a validated problem space, beta users ready, and a strong GTM/customer understanding. My background is in growth, ops, and strategy at Silicon Valley tech companies, so I’m not coming at this from “I have an idea, someone build it for me.” I know the market, the user, the distribution problem, and the pain point deeply.

But I’ll be honest. I think I’ve been a little brainwashed by the YC-style advice that I NEED a technical co-founder before launching.

The technical co-founder search has been exhausting.

A few patterns I’m seeing:

1. Since this is femtech, I initially preferred a woman co-founder. But the pool of senior technical women interested in early-stage femtech is painfully small.
2. It’s surprisingly hard to get men who haven’t experienced hormonal or metabolic health issues to truly understand why this problem matters. Some intellectually get it, but the urgency is not always there.
3. When I do find technically strong people, many are very passive. I understand that conviction takes time, but if someone agrees to a work trial, I expect some real energy and ownership. Instead, it often feels like I’m trying to drag excitement out of them.
4. Most technical people say, “This is technically easy to build; GTM is the hard part.” Fair enough. But then they still want cash comp from the angel money, equal equity, and less downside risk, while I’m carrying the fundraising, customer validation, GTM, product direction, and early operating risk.

I’m starting to wonder if I should stop searching for the mythical perfect technical co-founder, hire a strong founding engineer, launch the beta, prove traction, and revisit the co-founder question later.

I know the standard advice is that B2C is hard, femtech is hard, and you want a true technical partner early. I get that. But at what point does waiting for the “right” technical co-founder become more damaging than just moving?

Would love advice from founders who have faced this decision.

• Did you wait for a technical co-founder?
• Did you hire a founding engineer instead?
• Did you regret either path?

And for non-technical founders who raised or built the first version without a technical co-founder, what would you do differently?

I’m looking for honest advice from founders who have been through this.

I’m building a B2C femtech product. I have angel investment in place, a validated problem space, beta users ready, and a strong GTM/customer understanding. My background is in growth, ops, and strategy at Silicon Valley tech companies, so I’m not coming at this from “I have an idea, someone build it for me.” I know the market, the user, the distribution problem, and the pain point deeply.

But I’ll be honest. I think I’ve been a little brainwashed by the YC-style advice that I NEED a technical co-founder before launching.

The technical co-founder search has been exhausting.

A few patterns I’m seeing:

1. Since this is femtech, I initially preferred a woman co-founder. But the pool of senior technical women interested in early-stage femtech is painfully small.
2. It’s surprisingly hard to get men who haven’t experienced hormonal or metabolic health issues to truly understand why this problem matters. Some intellectually get it, but the urgency is not always there.
3. When I do find technically strong people, many are very passive. I understand that conviction takes time, but if someone agrees to a work trial, I expect some real energy and ownership. Instead, it often feels like I’m trying to drag excitement out of them.
4. Most technical people say, “This is technically easy to build; GTM is the hard part.” Fair enough. But then they still want cash comp from the angel money, equal equity, and less downside risk, while I’m carrying the fundraising, customer validation, GTM, product direction, and early operating risk.

I’m starting to wonder if I should stop searching for the mythical perfect technical co-founder, hire a strong founding engineer, launch the beta, prove traction, and revisit the co-founder question later.

I know the standard advice is that B2C is hard, femtech is hard, and you want a true technical partner early. I get that. But at what point does waiting for the “right” technical co-founder become more damaging than just moving?

Would love advice from founders who have faced this decision.

• Did you wait for a technical co-founder?
• Did you hire a founding engineer instead?
• Did you regret either path?

And for non-technical founders who raised or built the first version without a technical co-founder, what would you do differently?

I’m looking for honest advice from founders who have been through this.

I’m building a B2C femtech product. I have angel investment in place, a validated problem space, beta users ready, and a strong GTM/customer understanding. My background is in growth, ops, and strategy at Silicon Valley tech companies, so I’m not coming at this from “I have an idea, someone build it for me.” I know the market, the user, the distribution problem, and the pain point deeply.

But I’ll be honest. I think I’ve been a little brainwashed by the YC-style advice that I NEED a technical co-founder before launching.

The technical co-founder search has been exhausting.

A few patterns I’m seeing:

1. Since this is femtech, I initially preferred a woman co-founder. But the pool of senior technical women interested in early-stage femtech is painfully small.
2. It’s surprisingly hard to get men who haven’t experienced hormonal or metabolic health issues to truly understand why this problem matters. Some intellectually get it, but the urgency is not always there.
3. When I do find technically strong people, many are very passive. I understand that conviction takes time, but if someone agrees to a work trial, I expect some real energy and ownership. Instead, it often feels like I’m trying to drag excitement out of them.
4. Most technical people say, “This is technically easy to build; GTM is the hard part.” Fair enough. But then they still want cash comp from the angel money, equal equity, and less downside risk, while I’m carrying the fundraising, customer validation, GTM, product direction, and early operating risk.

I’m starting to wonder if I should stop searching for the mythical perfect technical co-founder, hire a strong founding engineer, launch the beta, prove traction, and revisit the co-founder question later.

I know the standard advice is that B2C is hard, femtech is hard, and you want a true technical partner early. I get that. But at what point does waiting for the “right” technical co-founder become more damaging than just moving?

Would love advice from founders who have faced this decision.

• Did you wait for a technical co-founder?
• Did you hire a founding engineer instead?
• Did you regret either path?

And for non-technical founders who raised or built the first version without a technical co-founder, what would you do differently?