“To be, or not to be” is the never-ending challenge Shakespeare asked every one of us in life. “To B, or not to B” is the equivalent challenge every person interested in startup life faces: should I work on a 2B domain, or a 2C domain? To state the obvious that everyone probably already knows, 2B or 2C is defined based on who’s the
Regarding how to make the choices, I totally agree with the hustle part. You can always negotiate with your customers as a 2B business to smooth the hustle. This is not possible in 2C.
> Because engineers tend not to resonate with 2B company customer needs
However, this is too strong an assumption to me. In 2C business, the problems space is a lot wider and there are more potential designs and solutions out there, while in 2B, the problem and solution is narrower.
“people won’t stop telling you how much they love or hate your product.” — lol, so true!
In 2c, we often have a lot more data for decision making while 2b requires higher judgement due to the lack of data.
Regarding how to make the choices, I totally agree with the hustle part. You can always negotiate with your customers as a 2B business to smooth the hustle. This is not possible in 2C.
> Because engineers tend not to resonate with 2B company customer needs
However, this is too strong an assumption to me. In 2C business, the problems space is a lot wider and there are more potential designs and solutions out there, while in 2B, the problem and solution is narrower.