Recently, AI-assisted efforts to recreate the functionality of several Adobe applications have sparked considerable discussion. At the same time, developers have used AI to build and open-source a compatibility layer for TradingViewâs Pine Script.
These projects are different. The first focuses on recreating software features; the second deals with runtime compatibility and migration. Yet both point to a trend worth watching: AI is substantially reducing the cost of developing software.
Work that once might have taken a team months can now sometimes be done by one person using AI in far less time. The cost of building software may fall enough to make us reconsider where its value lies.
So where do we go as software becomes cheaper to build?
Iâm a software engineer and designer exploring entrepreneurship. Iâm still validating ideas rather than running an established company. Iâve been looking for the connection between technology, products, and market needs. Through hands-on projects, Iâm also trying to understand the business opportunities created by technological change and where an ordinary developer might fit in.
This article brings together some of my recent observations, experiments, and thoughts.
1. AI Is Changing the Old Order, but a New One Has Yet to Emerge
When GPT and large language models first entered the public conversation, many people were skeptical of AIâs ability to write code or create designs.
The common criticisms were understandable: AI-generated code often could not be used as it was, the design quality was uneven, and the results still required extensive human revision. But I have never been comfortable using a modelâs capabilities at one moment in time to define AIâs long-term potential.
Technology keeps improving. What it cannot do today may be possible next year. Judging its future solely by its present abilities makes it easy to underestimate the pace of change. AIâs progress over the past few years has already exceeded many peopleâs expectations.
I think the anxiety and debate around AI run deeper than differing opinions about a new technology. AI is beginning to unsettle arrangements that once felt established.
For individuals, accumulated skills and experience may lose some of their former scarcity. For companies, advantages built on team size, technical barriers, and development costs may also come under pressure.
But as old advantages weaken, a new order does not appear overnight. New ways of distributing value, new business models, and new rules of competition are still taking shape. We cannot yet say exactly where this will lead. What seems clear is that uncertainty itself can create new needs, markets, and business opportunities.
That uncertainty is where my exploration of entrepreneurship began.
2. Some Business Principles Will Not Change Because of AI
Through this exploration, Iâve also encountered problems that remain familiar despite all the technological change.
Technical people can become absorbed in their own perspective. Two assumptions are especially common:
âThe technology behind my product is impressive, so it must solve a real user need.â
âThe product isnât perfect yet, so I canât release it.â Development continues, but the product never reaches the market.
A technical implementation does not validate demand, and building a product does not guarantee commercial success. A feature you find valuable may not be something users need. A product you spend months polishing may attract few usersâand even fewer people willing to pay.
Eventually, the product has to meet the market. Are there real users? Do they experience this problem? How do they handle it today? How much time or money have they spent dealing with it, or what have they lost because of it?
Developers cannot answer these questions through imagination alone. AI can help us implement ideas faster, but it cannot validate demand for us. Those answers still have to come from real users and market feedback.
3. My Experiment with X Account Risk Monitor
Iâm going through that process myself.
I began sharing observations about prediction markets and quantitative trading on X. After subscribing to X Premium, my account was restricted for what the platform described as ânon-human behavior.â I had not used automation tools, and I could not tell which action had triggered the decision.
X publishes platform rules, but it can be difficult for an ordinary user to know which of their actions might deserve attention. Its internal risk assessments are even less visible.
That led me to build a Chrome extension called X Account Risk Monitor. Its purpose is not to predict Xâs internal enforcement decisions or promise that an account will remain safe. It uses information visible on X pages open in the current Chrome profile to record some of a userâs own activity. When it observes certain repeated behaviors, it provides the recorded evidence and relevant public rules to help the user review what happened.
I deliberately kept the projectâs initial scope small. I did not add AI at the outset or rush to include every feature I could imagine. Instead, I built a version that addressed the basic problem, tested it, released it, and began watching for feedback from real users.
I published the extension on the Chrome Web Store and tried reaching users through channels including Reddit and Product Hunt. Some people responded positively, and others suggested improvements. The overall feedback sample, however, is still small.
I also began to see how difficult it is to interpret feedback. Some comments may reveal a genuine product need; others may express the frustration someone feels after losing access to an account. Identifying which problems are worth solvingâand whether they represent a large enough marketâis not straightforward.
That experience brought another reality into focus: the speed of acquiring users has not increased alongside the speed of building products.
Without enough exposure, it is hard to reach enough users. Without enough users, it is hard to gather meaningful feedback. And without meaningful feedback, it is hard to know whether a product solves a real market problem.
So I began improving the extension, built a separate product website, and reconsidered how I talked about it. Promotion should do more than list features. It should begin with a problem people recognize, then help them understand what the product can do.
At a local Startup Week event, I heard a related piece of advice: early-stage founders should make it as easy as possible for people to try a product, then keep improving it based on actual use. That matches what Iâm trying to do. Rather than adding features without market feedback, I want to put the product in usersâ hands and learn from what happens.
X Account Risk Monitor is still in an early validation stage. I cannot claim that it has proven a sustainable business need. But building it has shown me how much there is to learn between having an idea, releasing a product, and reaching real users.
4. AI Changes the Tools, but It Does Not Remove the Business Challenges
My experience has made one thing clearer: AI can reduce the cost of implementing a product without making its path to market simple.
As development becomes less of an obstacle, discovering needs, reaching users, and delivering lasting value deserve even more attention. At the same time, changes in how software is built and used may open up new opportunities.
5. Where Might New Opportunities Emerge?
AIâs effect on software may extend well beyond lowering development costs. As AI agents develop, they may change how software is produced and usedâand perhaps how parts of the internet operate commercially.
From Applications to Agents
We are used to general-purpose applications. A software company builds a standard set of features and offers the same product to a large number of users.
With the help of vibe coding, individuals and small teams can now build software tailored to their own needs much more quickly. Meanwhile, AI agents are moving beyond the role of assistants. They can interpret goals, call tools, retrieve information, and carry out tasks.
That could change the relationship between software and its users. Today, people operate software directly. In the future, an agent may operate it on a personâs behalf. Agents may also collaborate, call one anotherâs services, or transact directly.
Some needs may no longer require a dedicated application at all. A user might send an instruction to an agent from their phone, and the agent could call an API, run a script, or use a remote environment to complete the task. It might connect to a home computer or server to organize files, process data, or run a scheduled job.
In that model, some software could become infrastructure behind the agent rather than a product the user opens directly. The user may care less about which application was used and more about whether the task was completed reliably.
If both software production and software use change, the internetâs traffic sources, business models, and ways of exchanging value may change with them.
From an Attention Economy to an Economy of Service Calls
Much of todayâs internet is organized around human visitors. Websites use SEO to attract traffic, content to hold attention, and advertising, subscriptions, or sales to generate revenue.
Agents may become another important kind of visitor. They can query data, call services, obtain resources, and potentially complete transactions. Websites might then need to offer more than pages designed for people to browse. They may also need structured data, service interfaces, access rules, and pricing for agent use.
Some requests could become paid service calls rather than simple information retrieval. Mechanisms such as HTTP 402, x402, and pay-per-use micropayments may find new applications.
If that develops into a substantial market, companies may track agent calls, request success rates, revenue per call, and repeat usage alongside page views, visitors, and click-through rates. SEO may also evolve toward answer engine optimization (AEO) and agent discoverability. Businesses may need agents to understand what their services provide and when to use them.
None of this means advertising will disappear. It does suggest that who uses the internetâand how value is exchanged thereâmay become more varied.
6. The Gap Between Technical Capability and Real Needs
Seeing a possible future does not mean its opportunities are ready to be captured today.
During Startup Week, I was struck by a gap between how quickly AI tools are developing and how many people actually use them. Models, agent frameworks, and developer tools continue to improve. Tools such as Hermes and OpenClaw are gaining attention. Yet some people set up an agent and then find they have few clear tasks for it. They may use it to read the news or look up information, then struggle to think of what else to do.
Many people still use AI primarily through a chat box: they ask questions, provide context, and receive answers. AI can already call tools, operate software, connect to external services, and carry out more complex tasks, but those capabilities have not become part of most peopleâs daily workflows.
I see a gap between what AI can do and what users know they needâor know how to accomplish with it. That gap is both a challenge and a possible opportunity.
For many users, the missing piece may not be a stronger model or an agent framework with more features. It may be a simple, reliable way to hand over a real task and get it done.
If someone first has to research tools, configure an environment, connect services, and work out what to ask an agent to do, the complexity of the technology becomes a barrier. One opportunity worth exploring is to lower that barrier: let users express a need naturally, while AI works out the goal, calls the appropriate tools, and completes the task reliably.
A valuable product may help users identify and understand what they need, then turn AIâs capabilities into a useful result.
The technology is moving forward. Making it useful in ordinary work and daily life will take much more effort.
7. Finding My Place in What Comes Next
This wave of AI development has made me reconsider where an individual should focus when technical implementation is no longer the largest barrier.
AI is shortening the journey from idea to product. That does not make building a successful product easy. As more people can quickly implement their ideas, the harder challenge may be finding problems worth solving and continuing to create value for the people who have them.
That is the direction Iâm exploring. I donât want to build around a technology simply because it is popular. I would rather use projects and market observations to find problems that genuinely exist and remain poorly solved, then consider whether software and AI can offer a better answer.
Iâm still experimenting, and I donât yet know where this path will lead. But one point has become clearer to me: as AI lowers the barrier to creating products, it also makes us think harder about what is worth creating.
The old order is beginning to loosen, and a new one has yet to take shape. For developers still finding their way, this may be a chance to reconsider where we fitâand what we want to build next.