04What Nomuw Is Building
An operating layer that connects intelligence with execution.
Nomuw is developing an AI-native operating layer designed to coordinate commercial decisions and execution across e-commerce businesses.
The objective is not simply to help merchants understand their operations. It is to progressively enable the work required to operate those businesses to be performed through integrated, intelligent systems.
We believe that achieving this requires a fundamentally different architecture from conventional analytics software or collections of independent automation tools.
The ambition is to move from software that informs commercial decisions toward infrastructure capable of coordinating and executing them.
This describes the intended operating architecture, not a claim that Nomuw has already achieved comprehensive autonomous execution.
- Commercial information
- Coordinated intelligence
- Authorized execution
02 — The execution loop
Closing the execution loop.
At the center of our technology strategy is a continuously operating cycle:
Observe. Diagnose. Execute. Learn.
- 01Observe
- Collect, reconcile, and interpret relevant information about the merchant's business and competitive environment.
- 02Diagnose
- Identify developments requiring attention, evaluate possible responses, and determine their implications across interconnected commercial functions.
- 03Execute
- Carry out appropriate actions through authorized systems and workflows, subject to defined permissions, constraints, and human oversight.
- 04Learn
- Measure what happened following execution, assess performance against expectations, and use those observations to improve subsequent decisions.
This is an intended operating architecture, not a claim that Nomuw has already achieved fully autonomous execution across these functions.
Importantly, measuring an outcome is not the same as establishing causality. The system will need suitable analytical methods and, where feasible, experimentation to assess the effects of its decisions.
Exhibit
Inside the operating layer.
From market signal to coordinated action.
Choose a market event, then select a stage of the loop.
Market eventA competitor lowers the price of a comparable product.
01 Observe · Competitor price cut
The system identifies the competitor's price change and assembles relevant information about the merchant's current price, cost structure, inventory, advertising performance, and commercial objectives.
Control requirement
Information quality and completeness
03 — Coordination across functions
The operation is interconnected. The system should be too.
We envision the operating layer coordinating activities that are commonly managed through separate workflows.
These include pricing and competitive intelligence, advertising, inventory planning, sourcing, product and catalog management, and financial performance.
The value of this architecture would come not merely from performing each task individually, but from understanding how the tasks affect one another.
For example, a pricing decision should account for contribution margins, advertising economics, inventory availability, and the merchant's broader commercial objectives.
Similarly, a replenishment delay might require coordinated adjustments to advertising, promotional activity, purchasing plans, and cash allocation.
The relevant unit of optimization is therefore not an individual task or software module, but the commercial operation within the scope of the system's available information and permissions.
04 — Progressive autonomy
Autonomy must be earned.
Giving software the ability to act introduces risks beyond those associated with providing analysis or recommendations.
Incorrect decisions can create financial losses, operational disruption, and damage to marketplace accounts or customer relationships.
For that reason, we intend to approach autonomy progressively.
Early capabilities may emphasize monitoring, interpretation, recommendations, and the execution of clearly defined workflows.
More consequential decisions should remain subject to appropriate human approval until the underlying systems demonstrate sufficient reliability.
Greater autonomy should depend on measured performance, operational safeguards, permission boundaries, and the ability to detect and respond to errors.
The objective is not maximum autonomy at any cost.
It is economically valuable execution at an acceptable level of risk.
- 01
Observe and recommend
The system interprets information and proposes actions. Humans retain execution responsibility.
- 02
Human-approved execution
The system prepares and executes permitted workflows following explicit authorization.
- 03
Bounded autonomous execution
The system performs validated, low-risk activities within merchant-defined permissions, financial limits, and escalation rules.
- 04
Broader coordinated autonomy
Additional interconnected workflows may be executed autonomously after evidence demonstrates appropriate reliability and economic value.
A longer-term ambition.
05 — Operating foundation
Built from the realities of operating commerce businesses.
Our technology strategy did not begin with the current platform concept.
It evolved from internal tools developed to support our own e-commerce operations and was subsequently explored through Deep Pulse as a potential standalone software business.
We have since decided that this technology should become fundamental to Nomuw's broader commercial strategy.
Our existing operating expertise informs the workflows we intend to automate, while our managed-services activities offer a potential environment for observing operational requirements, testing capabilities, and validating their commercial usefulness.
This relationship between operations and technology is central to our development approach.
However, familiarity with a workflow does not, by itself, establish that it can be automated reliably or economically. Those properties must be demonstrated through implementation and testing.
What exists. What we're developing. What we intend to achieve.
Exists
Historical operating foundation
Internal tools were developed to support Nomuw's owned-brand operations.
Management-reported historical experience.
Developing
Planned and developing capabilities
The intended operating layer includes integrated commercial context, cross-functional decision coordination, and increasingly software-executed workflows.
The production readiness of individual modules has not yet been established within this investor prototype.
Intended
Longer-term ambition
Reliable, economically attractive, coordinated autonomous execution across an expanding set of commercial functions.
Subject to technical, operational, and commercial validation.
06 — Services-as-Software
Transforming how commercial operations are delivered.
Our longer-term ambition is to change how e-commerce operating services are delivered.
Today, managed operations depend heavily on human expertise and labor.
We intend to develop technology that performs an increasing share of this work, reducing the human effort required for routine execution while preserving oversight where judgment and accountability remain necessary.
This progression forms the basis of our Services-as-Software strategy.
Rather than asking customers merely to purchase access to another application, we intend to provide increasingly technology-enabled execution capabilities.
Initially, we expect the value proposition to center on the speed, consistency, and efficiency of execution.
As the system matures and its commercial effects become measurable, additional pricing arrangements tied to verified outcomes may become appropriate.
This transition remains a strategic objective, not an established operating result.
01
Managed Operations
Execution led by human expertise and labor.
02
Technology-Enabled Execution
Technology performs a growing share of routine work, with human oversight.
03
Services-as-Software
Commercially valuable execution delivered increasingly through technology.
Not simply: Managed Operations → Conventional SaaS.
Our economic ambition concerns the delivery of commercially valuable execution, not merely recurring access to software.
07 — What must be demonstrated
The next phase is about proof.
The long-term opportunity depends on more than our ability to develop functioning software.
We must demonstrate that the operating layer can acquire and reconcile the necessary information, make sufficiently reliable decisions, and execute within appropriate operational boundaries.
We must also establish that its capabilities produce meaningful economic value for merchants, that customers are willing to pay for them, and that Nomuw can deliver them at attractive marginal costs.
The economics of integration, inference, monitoring, exception handling, and human oversight will matter alongside technical performance.
These are central development and commercialization questions, not secondary implementation details.
- Technical reliability
- Can the system interpret information and execute correctly?
- Commercial usefulness
- Does the work performed create value customers recognize?
- Delivery economics
- Can execution be delivered at an attractive incremental cost?
- Willingness to pay
- Will customers pay enough for the capabilities to support a sustainable business?
Our conviction is that coordinated execution represents a valuable problem to solve.
Our responsibility is to demonstrate that Nomuw can solve it reliably, economically, and at commercially meaningful scale.
The intended operating model
From understanding commerce to executing it.
Nomuw's proposed operating layer is intended to connect information, decisions, and execution across the commercial operation.
The opportunity lies not in adding another source of information, but in making commercially valuable execution more coordinated, responsive, and increasingly technology-enabled.
Our next challenge is to demonstrate that these capabilities can be delivered reliably and economically.
Next chapter
05The Commercial Model
Who Nomuw intends to serve, how it creates and captures value, and the economics of its transition toward Services-as-Software.