Imagine an organization that has genuinely decided it wants to become a force for good. Its leaders have come to understand that long-term success cannot be separated from the health of the wider ecosystem in which the organization operates. Customers need to benefit from the relationship, employees need to be able to grow and contribute meaningfully, suppliers need to remain viable, communities need to be strengthened rather than depleted, and the natural systems on which all economic activity ultimately depends need to be protected and, wherever possible, restored.
This organization is not merely trying to reduce harm. It wants to become regenerative: to create the conditions through which the people, relationships and systems around it can become healthier because the organization exists.
The ambition is admirable. The difficulty begins when the organization tries to put it into practice.
Almost immediately, it discovers that the infrastructure on which it depends was built for a very different idea of business. Its commerce platform is designed to attract visitors, convert them into customers and process transactions. Its CRM records leads, contacts and opportunities. Its ERP manages products, inventory and orders. Finance records revenue, margin, liabilities and cash. Customer service manages cases and tickets. Marketing measures attention, conversion and retention. Procurement manages suppliers. Human Resources manages employees. Sustainability, where it has become formalized, often operates through yet another set of reporting systems.
Each of these systems may be highly capable in its own domain, yet together they reproduce the very fragmentation the organization is trying to overcome. They can tell the company a great deal about its parts, but very little about the health of the whole.
That becomes apparent as soon as something happens that crosses the boundaries between those systems.
Suppose a customer buys a product that ultimately fails to deliver what was promised. Customer service sees the complaint and tries to resolve it. Finance sees the refund or replacement cost. Operations sees another shipment. Marketing may never learn that the original promise contributed to the disappointment. Procurement may never discover that the supplier has been encountering the same underlying issue elsewhere. Product development may not see the pattern until enough cases accumulate to trigger an investigation. The supplier may possess knowledge that could have prevented the problem but has no meaningful way of feeding it into the organization’s learning process.
From the perspective of each function, the work may still be completed correctly. The ticket is closed, the replacement is shipped, the refund is processed and the customer is marked as retained or lost. Yet the organization as a whole may have learned almost nothing.
This is where the gap between regenerative ambition and operational reality becomes visible.
Regeneration depends on understanding relationships, consequences and feedback. It requires an organization to notice not merely that a transaction occurred, but what that exchange did to the people and systems involved. Did the customer become better off? Did the employee encounter an obstacle worth learning from? Did the supplier relationship become stronger or weaker? Did the transaction create unnecessary waste? Did the organization discover something that should change the way it designs, communicates or delivers value next time?
Those questions cannot easily be answered when the experience of the organization is scattered across departments, databases and applications that were never designed to understand one another as parts of a living system.
For years, this has been one of the central concerns behind RoundMap. We have been exploring why organizations that employ intelligent and committed people still struggle to act collectively, why knowledge becomes trapped inside functional boundaries, why locally sensible decisions can produce undesirable consequences elsewhere, and why organizations so often optimize their own performance at the expense of the systems on which they depend.
The more I explored these questions, the harder it became to ignore an uncomfortable implication. We can develop better models of whole-system leadership. We can teach people to recognize interdependencies. We can encourage collaboration, stakeholder orientation and regenerative thinking. But sooner or later those intentions collide with an operational infrastructure that still assumes a fragmented, transactional organization.
We are asking people to think systemically while asking them to operate through systems that are not systemic.
That realization is what led me to start developing VenduSys.
VenduSys is my attempt to explore what commerce infrastructure might look like if we started from a different assumption about the organization itself. Instead of treating the enterprise as a collection of functions coordinating transactions, what if we treated it as a participant in a network of relationships through which value, knowledge, resources and consequences continuously circulate?
That shift changes what the system needs to be able to see.
A customer can no longer be understood merely as an account, an order history or a lifetime value score. A supplier cannot simply be a vendor record. An employee is not merely a user with permissions. A partner is more than an integration endpoint. Each is a participant in a wider value system, carrying information, capabilities, expectations and experiences that may matter to the health of the whole.
The transaction changes meaning as well. Instead of being the endpoint toward which commerce is organized, it becomes one event in an ongoing relationship. What happens before, during and after that event becomes part of what the organization needs to understand.
The customer complaint in our earlier example would therefore not simply disappear into a service queue until somebody closes it. It could become a case through which the organization learns. The customer’s experience provides the initial signal, but understanding that signal requires context: what was promised, what was purchased, what happened during fulfilment, which product or supplier was involved, whether similar cases already exist and what other people across the organization know about the situation.
Responding appropriately requires care, but the process should not end there. The experience should also be capable of producing change. What the organization learns from this case may need to influence the product, the supplier relationship, the sales process, the marketing promise, the fulfilment procedure or even the assumptions embedded in the organization itself.
This is the reasoning behind one of the mechanisms we are developing within VenduSys, which I call Case-to-Core™. The purpose is not simply to resolve cases more efficiently. It is to create a pathway through which lived experience can inform organizational learning and through which that learning can improve future action.
In that sense, commerce begins to become something more than a mechanism for exchanging products and money. It becomes a learning system.
That distinction matters because a regenerative organization cannot be managed entirely through intentions, policies and annual impact reports. It needs to be able to sense what is actually happening in the relationships through which it creates value. It needs to detect patterns, connect perspectives and understand how actions in one part of the system affect another. It needs to remember what it has learned and allow that learning to influence how it behaves next time.
None of this means that technology can make an organization regenerative. It cannot. Regeneration still depends on leadership, judgment, trust, agency, responsibility and the willingness to confront difficult trade-offs. No platform can decide what people ought to care about or guarantee that competing interests will suddenly align.
Infrastructure does, however, shape what an organization is capable of seeing, connecting, remembering and acting upon.
If our systems primarily see transactions, we will tend to optimize transactions. If they divide customers, employees, suppliers and partners into unrelated records, we will struggle to understand the relationships between them. If important consequences remain outside the systems through which everyday decisions are made, those consequences can remain invisible even while everyone sincerely claims to care about them.
This is why VenduSys has gradually become more than a software project for me. It is becoming the practical counterpart to questions I have been exploring through RoundMap for more than a decade.
RoundMap asks what happens when we stop looking at an organization as a collection of isolated parts and begin looking at the whole system through which value is created, exchanged and renewed. VenduSys asks what kind of infrastructure that organization would actually need if it wanted to operate accordingly.
That is the bridge I am now beginning to cross.
The ambition is not simply to build another commerce platform with additional sustainability features. It is to investigate whether commerce itself can be organized differently: whether the systems through which organizations sell, fulfil, support, collaborate and learn can help them understand the effects they create across their wider ecosystem, and whether those insights can continually improve the way value is created and circulated.
For years, RoundMap has helped me develop a map of what a more connected, adaptive and regenerative organization might look like.
With VenduSys, I have begun asking the inevitable next question: what would we have to build to make that organization possible in practice?
