|
|
|
|
|
|
by DoubleFree
2244 days ago
|
|
|
I think the point here is that your MVP should behave like the actual product in the eyes of the customer, but you do not have to actually build the functionality. By providing a lot of the service manually, you can get your initial customers quickly. Having customers means getting feedback from the product's target audience. Getting this feedback before actually heavily investing in automating the product means when you do automate, you have a much better idea of what the final product should look like and which features you should prioritize, wasting less time and money on building the wrong things. |
|
|
A number of AI companies start out by outsourcing the "AI" to something like Amazon Turk or remote contractors. From the customer perspective, the system is working as intended. The system transcribes their videos, or schedules their appointment, or whatever.
In the backend, the system doesn't exist. It's just a bunch of people manually transcribing videos and manually creating Calendar links. And those companies are validating that customers will want to use the fake version before they spend the time building an AI-driven real version.
Do I understand correctly, or is that different from what you were trying to say?
But in that case, you're still building a product that does a thing. It's just that the product doesn't currently scale, and the business isn't being up-front telling any of its customers what they're actually buying. I wouldn't say you built a mockup in that situation, I would say you built a call-center, and you're thinking about whether or not to automate it based on demand.