|
|
|
|
|
by jrvarela56
1256 days ago
|
|
Not to be dismissive, but if I were you, I would leave the technical aspects of a B2B/Enterprise product for later. The main problem is figuring out a sales process/gtm strategy. As others have mentioned, you would benefit from partnering with someone who knows about the problem/industry and has experience selling to enterprises. Keep in mind this will be the core competence of your company (if you want to make lots of money). The job as the technical lead will look more like consulting than just building and shipping product. If you're going at it alone, talk to a lot of people involved in the business process you're trying to fix to make sure you understand specifics about why they do things the way they do right now. Sometimes as developers we tend to view company problems as technical issues but they're most likely org/political/social issues. Don't build much just yet, make a visual prototype you can show/pitch and charge for demos/integrating/making-it-work-for-them-to-test-it. |
|
The best feedback I got was a sr guy who I quite respected just commented “can you link the client’s LinkedIn?”
That’s when I realized I was never going to be specific enough, and starting from the tech was working backwards