What is a product?(roge.onwrite.app) |
What is a product?(roge.onwrite.app) |
Hard disagree. I think the articles goes in a good direction when it comes to the question but this ending is short of a satisfying answer
Building something like a YouTube competitor is theoretically doable by a small team. It’s vastly more possible with AI tools than it was a decade ago.
But the “muscle” of doing difficult things has atrophied for many people, in large part because the AI tools themselves reduce your ability to actually do the work. If day after day, you just prompt an AI to make things for you, do research for you, etc. then you gradually stop working that muscle yourself.
It makes me think that the ideal usage of AI tools might be a deliberately limited one: do everything on your own, but check in with the AI once a week for review.
I maintain half a dozen products, some of which enjoy only a handful of dedicated users, and I consider them all a resounding success. We are living in a new future of readily available custom software for extremely niche use cases.
> Don't feel bad if you don't have anything to show up with all the free intelligence available nowadays. Almost nobody has.
But I can empathize with the author's attempt at "vibe writing" something meaningful, considering that they seemingly don't have anything better to "show up with".
> I haven't seen any real competitor of YouTube, or Figma, or Google, or Instagram created solely with AI.
Is a ridiculous set of products to expect competitors for. First all but 1 rely heavily on network effects. YouTube is a low cost provider. Think about it, they provide unlimited high quality video storage for free. They process 500 hours of content every minute. Google and Instagram have a huge network all users benefit from. AI can't help you bootstrap this network.
The only one that's fair is Figma, and considering Figma is down 30% from IPO price (much lower from ending day close), it's fair to say there are competitors to Figma, including the LLMs themselves.
That begs the question: what is product? Is "an app for designers to change style and communicate with developers" the product? Or is the product "to make websites look pretty and well organized"? The former, Figma is great. But if the product is the latter, LLMs are a real threat. No one would bother building a "better Figma" today, why would they? They would just solve the problem Figma purports to solve
The next Google won't be a search engine with 10 blue links. Why would anyone create slightly better legacy apps.
For instance, Claude is 100% a competitor to Salesforce and there are go to market companies like Clay that manage outreach of a salesforce. Small companies can easily spin out a simple system that can source people to reach out, track follow ups, help w copy and even coordinate email.
Not in any academic sense, but in a real-world sense a software product is something that as a user you can rely on to solve a problem. Rely is doing the heavy lifting in that sentence.
You can rely on a vendor’s product if (a) they’re going to be around for a long time, otherwise the investment into adopting it isn’t worth it; (b) the vendor is committed to solving your problem in an ongoing way - meaning they understand enough of the domain (ideally more than you do) that they’re going to be a partner even as your own needs evolve; (c) they deliver the product in a dependable way - high uptime and security.
So it comes down to “can you depend on this software over time?”
The underlying point --that network effects exist and determine the success of a product-- has always been the case, long before AI made it possible to vibe code a rough Instagram clone in a weekend.
Anyway, if you want a successful new product, the path to success (obviously) isn't likely to be copying an existing behemoth, but offering something new, unique and valuable. That's always been the (exceptionally difficult) challenge, and AI doesn't help with this. But I think we can be confident that in the future, as humans do create new, unique, and valuable products, some of them will probably be vibe coded.
This misses the mark.
A product is something which can be exchanged with others, transferred into their agency, for them to own and use according to their free will.
They don't have to use it or indeed 'be a user' - it is up to them whether or not utility is derived. The only requirement is that it is exchangeable and that agency has been transferred in such a manner that all parties involved in the exchange are satisfied with the transfer of agency.
A project is some activity which has an expectation of changing state over time.
Project management means projecting the scope and sphere of that activity into the future, in order to change its state in such a way, hopefully, that something exchangeable is produced. Product management means, making sure a satisfactory exchange occurs between the creator of a product and its new owner.
So many people get this wrong.
It is not a product if it's a project. It is only a product once it has been exchanged with another entity for their purposes.
You can have many, many projects which will never become products, because they won't be exchanged with others. You can have products which are valued by their owner in ways unintended by their creators. The value and utility is arbitrary to whether or not something is a product - the only requirement for something to become a product is that it is exchanged.
Successful product(S) are exchanged at scale. A single product can be very successful if the scale of that exchange is high. A lot of products can be very successful if the number of exchanges is great.
Until the exchange occurs, it's not a product. It's a resource. Inventory.
Side projects become products only once they are exchanged.
There really are plenty of Google analogs. There are plenty of chatbot analogs. Any one of us can recreate Instagram or X. These competitive analogs simply have not become products, because they have not been exchanged. Products which harness human collectivity have the problem of not being exchanged at scale until the collective decides to participate in the exchange, i.e. recommend their friends sign up to join them.
The problem with easily started new side projects is that they are not so easily exchanged at sufficient scale.
It is not that we didn't have the expertise to do so to begin with, but it would simply have been too expensive and time consuming. That was solved once the models became good enough.
There's a lot of money in the SaaS world, where the products are both unglamorous and one-trick pony-ish. Making your product LLM-proof can be challenging today, unless you happen to own a lot of data or lots of compute, and those two are the drivers behind your product.
Another mistake everyone making is not building better and bigger products. What is used to take a month to develop is now possible in few days but most don't put the same effort as before to make bigger and better products. They just do they same as what they used to do before but quickly. This is a mistake. AI uplifted everything so products built with AI should go to next level.
I'm an indie mac app developer. My first product took me 6 months to develop without much AI. I just released my second app ( https://www.vinaa.ai/ ) but took the same time to develop as I wanted it to be the best AI chat app. So I spent a month building my own markdown renderer in TextKit as existing library are not fast enough. I wouldn't done this if I don't use AI.
I've found the opposite to be trie very often.
The vibe-coded demos everyone's tired of are code with no environmental need pulling on them.
So building is faster, but marketing—not so much
Also, dang ought to make a new tab "Trends" (or just name that "AI") and move all AI/LLM/etc posts there. We might possibly see something other than AI then.
> So building is faster, but marketing—not so much
Producers are AI/agents now but consumers are still human beings. Maybe it will be different when it will be: by the AI, for the AI, of the AI… etc and humans will be safely out of the consumption loop.
But the question of should I spin up my own website in a few minutes or use wordpress for my blog is now open. Your personal tools can compete with what's out there and you may decide what you build in one session is more compelling than what the "pros" are offering.
And for personal tools you are much more forgiving for the mistakes if it gets whatever task you want done.
E.g. it's now about the delivery of a service rather than the challenge of building it (e.g. the moat) and then the delivery of service of it afterwards. Non functional requirements like data management and security, legal requirements and hosting are still valuable things that aren't front of mind for most developers creating their own tooling.
Imo a better distinguisher of demos and products is: "is your thing CAPABLE of solving a real problem" (even if it isn't doing so at a scale atm). Google+ was a product (not a super successfull one), eventhough it didn't have many users. Conversely, a viral interactive gimmick can attract millions of users in a day without really being a product at all.
AI obviously is powerful and quick to build, but intellect, intelligence, and creativity will still lead to disproportional outcomes for users. After all, AI still relies on effective prompting to build well.
The real danger, then, is not AI churning out endless slop, it's actually that the slop degrades the perceived quality of actual products and legitimate effort.
Measuring by users is one metric, yes, and a good one. But, quality of output and performance beyond a simple prompt is what will make the difference. Products couldn't only be measured by the number of users, but also by quality and ingenuity.
Lastly, the products of tomorrow will not defy AI, but will build on top of them. AI will build and perform a higher level of compute, yes, but the products will orchestrate AI workflows, rather than deterministic outputs. Guided reasoning, orchestration, and value creation are human qualities, not AI.
The word ‘product just left everyone confused.
If one uses a word like platform, application, prototype, offering, ‘products’ this makes it clearer than just the generic ‘product’. It’s even better if goal is applied as well. For example Flight finder Application, or Video Playback Platform.
In that case (but IMO it applies to almost everything that's not selling a software or technical solution per se) the product IS the hotel/insurance/flights/excursions package. There is no other way. The website was never the product, it was just a channel. The difference is that especially back then the only way to use that channel was to build it by yourself. And that's something that actually happens for big enough brick&mortar stores: they do have an internal department that manages the stores, buy/rent the spaces, furnish and decorate them etc.
You can sell a single product for an enormous price, you can sell 1,000 products at a low price - the only thing that matters is that the two parties agree to conduct the exchange at any scale and, most importantly, that it actually occurs.
Common to both high-end scale and low-end scale scenarios, is that the exchange occurred and all parties agree to it. That's the only thing that makes something a product - the exchange.
I find that quite often teams responsible for part of the infrastructure speak of their part as the “product”, with the consumer of that product possibly being a different team in the same company, not necessarily outside of it. I can totally see how for the website team, the website is “the” product under most circumstances.
Nobody wants to know how the sausage is made. Vibe coding is just sausage-making.