> The process of building an MVP includes the process of figuring out distribution.
As blindingly obvious as this is, I've never seen it put quite so concisely. Fantastic. I could've cut short so many bullshit discussions this way
As blindingly obvious as this is, I've never seen it put quite so concisely. Fantastic. I could've cut short so many bullshit discussions this way
Maybe I'm being picky here but I disagree a little bit with this. At the start, your MVP might just have been for you i.e. to scratch an itch you have and it is only later that you think about getting other people to use/pay for it. So maybe your above statement will (should??) apply if your MVP was targeted for the public
When I'm trying to scratch an itch, I try to get something 'rough' and then try to add the bells and whistles later on. Mentally, I always think of that 'rough' bit as 'my own MVP' i.e. what are the minimum features I need to build for this tool to solve my problem.
For example I needed a self hosted solution to convert svg images to png. I need a way to specify the image to be converted, code to convert it, and a place to store the output. My first build had a text field where I manually enter the path to the svg file I need to convert, and I hardcoded the output folder. I thought of that as my MVP. When I was sure the code was working and much later on when I had the time, I added a file picker to allow me pick the input file and another file picker for me to specify the output location.
You are setting yourself up for a hell of a sales problem.