yishanl

At first glance, it sounds like you may be overfitting an overly-comprehensive technical solution to an extremely cost-sensitive/archaic/offline-centered industry.

Explaining the stack you used to build this platform will likely come off as pure alien speak to the restaurant owners you try to sell to.

But that being said, I only understand restaurants in the US, and not Sicily.[0]

Research is a good place to start - first with your own product, then the larger market (how is it being used, how much value does it bring prestofood, how many orders do they process per day).

If the metrics give you conviction, start by talking to some restaurants.

There was a YC company (Trackin) that focused on this exact concept in the US that went through enough trouble that they've since pivoted to catering like Zesty, Zerocater, etc...

Oh, and effort != good product.

[0] Started/ran www.eatmise.com in SF, grossed 35K+, achieved ramen profit in 7 months solely on organic WOM.

I'll be interning in SF and study on the East Coast as well.

Shoot me an email!

Ylin 5*2 [@] Boston university

I feel for you.

Don't do it.

Money brings out the worst in people.

Arguing is healthy. Just depends on how it comes & what it's over. Obviously, if your relationship deteriorates to the point that you are arguing for little value then that's bad - I do think arguing early is better than arguing late. It'll be insightful for you and him, to be honest. You'll learn a little more about yourself and a lot more about him in how the argument progresses and more importantly, how it ends.

All non-tech founders are insecure about their position in the business. I think any competent non-tech founder should be insecure about their position imo, if there is a component of technology to the business.

I was too, so I just kept working and supporting in as many ways as I could think of.

Thankfully, our product was online-to-offline, so there was plenty of work to be done.

But don't do it.

Eek, went through the same thing except we did it for a whole year. Skillset or not, sharing core values/beliefs is most important. Because when shit goes south, if you have someone who is just as committed as you are (for the right reasons), there is nothing you can't overcome when the core values align.

Although this is really hard because people show their truest faces when shit goes south. So you won't know for sure unless this is someone who you've spent and enjoyed spending lots of time with for a while.

After spending time thinking critically about the past year, here are some rough open-ended questions I've come up with that I think would shed light into one's core values.

How do you approach solving a problem (any size, scope)? What locus of control do you believe in? Is there value in rolling up your sleeves?

Emailed.

Hope the rest of the team benefited.

Cool, thanks Jennifer! That was some serious dedication, super admirable. :)

One more question, although I've already asked a lot of you. How did you make sure you conceptually understood what you were learning at every stage, not just simply taking code and just replacing bits of it here and there?

This is super awesome and inspirational. What was the most frustrating experience you had in your 180 day challenge?

Thanks! Means a lot. It's a good idea - one day, I hope when we're successful, perhaps then writing such findings then may be more meaningful and valuable as learnings for others.