What can you really build in a weekend?
The core functionality with happy path? Probably, yes.
But will it be useful? I doubt it.
Can you add support for settings so users can customize the workflow in that weekend?
What about error states when things go awry?
What about security?
The mobile or desktop optimized version?
What about compliances needed to serve?
And onboarding, so users can actually get some value out of it?
Admin panel? Customer support tool integration? Handling weird payment flows? Marketing site?
Converting a weekend hacked up prototype, to a proper functioning business takes a lot of time and effort.
Yes, you can come up with a prototype that users can use and play around with, and you should to reduce time to feedback!
But don't belittle other people's work of turning prototypes to a proper business with a flippant attitude.
Originally written on my site. Would love to hear your opinion! :)
Counter-intuitively I think the most impactful opportunity to "build it within a weekend" is in the context of large existing products where a lot of edge cases are already accounted for and you get the chance to focus in on one hyper-productive use case.
Bigger companies and larger user bases naturally have higher bars for security, user experience, business needs, QA, product sign off, etc. So actually threading that needle is nearly impossible in practice — but that is where the opportunity really lies — vs greenfield projects where you can build the happy path in a week and are left with a gigantic uphill battle to actually deliver value.