From Products to Outcomes: Rethinking Design in India

Design is often understood in narrow terms—form, engineering precision, or product features. In physical industries, it is typically treated as the stage where a product is shaped, optimised, and readied for production. Once built, the product is expected to find its place in the market, and the company’s responsibility largely ends at the point of sale.

But in several fast-scaling sectors in India, this understanding is quietly becoming inadequate.

The real shift is not in how products look or function. It is in how they are deployed, used, and sustained over time. Design, as a result, is moving beyond the product—towards the system in which the product operates.

This is not a theoretical shift. It is already visible in India's green energy linked sectors. What is emerging is a new logic: design is no longer about creating products; it is about delivering real-world outcomes.

Signals from the Market: The E-Bus Turn

According to a recent report by Marqstats (released on 25 March), the Gross Cost Contract (GCC) model makes up for over 90% of e-bus procurement in India — shifting vehicle ownership, operations, and maintenance to OEMs, and thereby de-risking adoption for state transport undertakings. The report further says that recent large-scale government tenders have seen relatively new and specialised players such as PMI Electro Mobility, Switch Mobility, EKA Mobility, and Olectra Greentech outperform established incumbents like Tata Motors. Further, a recent report by BusinessLine (published on 30 March) says that this sector is undergoing substantial churn: the top three e-bus makers in FY26 are entirely different from the top three in FY25. 

This is striking at first glance. Legacy companies possess deeper manufacturing capabilities, established supply chains, and decades of experience. Yet, in competitive electric-mobility tenders, they have not always been the winners. 

The reason lies in what is being evaluated. These tenders are not simply assessing who can build the best bus. They are assessing who can:

- deploy fleets at scale,

- operate them reliably over years,

- manage charging infrastructure,

- and guarantee uptime under contractual obligations.

In other words, they are evaluating systems, not just products.

Newer players, unburdened by legacy structures, have built themselves around:

- contract execution,

- fleet operations,

- and lifecycle accountability.

Incumbents, by contrast, are often still optimised for:

- manufacturing scale,

- and one-time sales.

The result is a reversal of expectations:

In a system-oriented market, the best product maker does not automatically become the best system operator.

The Limits of Product-Centric Design

The traditional industrial model is straightforward:

design → manufacture → sell.

The product is the endpoint. Once it leaves the factory and reaches the customer, the company’s role diminishes. Feedback loops exist, but they are indirect and often delayed. The real-world performance of the product—how it is used, maintained, or stressed—is largely outside the designer’s control.

This model worked well in environments where:

- usage was relatively uniform,

- customers were fragmented, and

- lifecycle accountability was limited.

But it carries an inherent limitation:

A well-designed product can still fail if its use is poorly structured.

A vehicle engineered to high standards may underperform in fleet conditions. A solar installation may degrade if maintenance cycles are irregular. A machine optimised for ideal conditions may struggle in real-world environments.

In all such cases, the failure is not of the product alone—but of the system in which the product is placed. And that system was never designed.

Application Comes First

The first visible shift, therefore, is conceptual:

Design is beginning not with the product, but with the application.

Consider electric mobility. A two-wheeler designed for personal commuting has very different requirements from one used for last-mile delivery. The former prioritises comfort, aesthetics, and flexible usage. The latter demands durability, payload capacity, predictable range, and minimal downtime.

Similarly, a passenger vehicle designed for individual ownership is fundamentally different from one used in a taxi fleet. A solar installation for a household differs significantly from one serving a commercial or industrial load.

In each case, the category remains the same—but the application reshapes the design constraints.

This leads to a fragmentation not of products, but of use-case systems. The question is no longer: “What should we build?”; but: “How will it be used, repeatedly, at scale?”

Lifecycle as a Design Constraint

Once application becomes central, the lifecycle of the product moves from the periphery to the core of design.

Design must now anticipate:

- uptime requirements,

- maintenance cycles,

- operating environments,

- and cost over time, rather than upfront cost alone.

In other words:

Design is no longer about what works—it is about what keeps working.

A fleet vehicle is not judged by its initial performance, but by its ability to operate reliably across thousands of kilometres. A solar energy system is not evaluated at installation, but over years of consistent generation.

This shifts the design process itself. Engineering decisions are no longer isolated from operational realities. They are shaped by them.

The New Unit of Design

These changes point to a deeper transformation:

The unit of design is no longer the product. It is the system in which the product operates.

This system has multiple layers:

- the product itself,

- the environment in which it is deployed,

- the processes through which it is operated and maintained,

- and the outcomes it is expected to deliver.

The product is becoming one component within a larger architecture.

Design, therefore, is no longer confined to shaping an object. It now involves structuring a system that can deliver performance continuously in the real world.

Modularity Reimagined

In this context, modularity is also taking on a different meaning.

Traditionally, modularity refers to interchangeable components—parts that can be replaced or upgraded independently. 

While this remains important, a new layer of modularity is emerging: Application-level modularity. Instead of designing entirely different products for each use-case, companies can develop:

- a standardised core,

- with configurations adapted to specific applications.

For instance, a base vehicle platform may be adapted differently for delivery fleets and personal users. A solar energy system may be configured differently depending on load patterns and site sizes/conditions.

This allows companies to balance:

- standardisation (for scale and efficiency),

- and differentiation (for application-specific performance).

When Design Expands, Companies Must Expand

Once design extends beyond the product, company themselves must evolve.

A company that designs for deployment and lifecycle performance cannot remain a pure manufacturing entity. It must engage with:

- how the product is deployed,

- how it is operated,

- and how it performs over time.

This is leading to a structural shift:

From: build → sell → exit

To: design → deploy → operate → optimise

The company, in this model, is no longer a seller of products. It is a manager of systems.

The Emerging Company Architecture

This expanded role cannot be absorbed within a single organisational structure without friction. Manufacturing and operations require different capabilities, cultures, and time horizons.

A more viable model is a dual structure:

- a core entity focused on product design, engineering, and manufacturing,

- and an operational arm responsible for deployment, maintenance, and performance management.

This separation allows:

- precision and efficiency in production,

- adaptability and responsiveness in operations,

- and a continuous feedback loop between the two.

Design, in this structure, is not a one-time activity. It becomes an evolving process, informed by real-world data.

Demand Is Now Asking for Outcomes

This transformation at the company level is not occurring in isolation. It is being shaped by how demand itself is structured.

Across several sectors, especially in green energy linked domains, demand is shifting from products to outcomes.

Instead of purchasing assets, large procurers—public and private—are increasingly contracting out bundles, consisting of:

- manufacturing,

- deployment,

- operations,

- and maintenance.

For green product companies, this is changing the nature of competition. It is no longer sufficient to build a better product. They must deliver reliable performance over the lifecycle.

Where This Model Applies—and Where It Does Not

This model is not universal. It works best in sectors characterised by:

- high utilisation,

- institutional or aggregated demand,

- and measurable outputs over time.

These include:

- electric mobility fleets,

- commercial and industrial RE systems,

- and similar green energy linked domains.

It is less applicable in:

- fragmented consumer markets,

- low-frequency usage products,

- and environments where usage patterns are highly unpredictable.

The emerging shift, therefore, would not be economy-wide—but sector-specific.

Competitive Advantage of the Model

As this model matures, the basis of competition would also change. Product features alone would become insufficient. Advantage would shift towards:

- operational excellence: the ability to deliver consistent performance at low cost

- system design capability: integrating product, deployment, and operations effectively

- data advantage: using real-world performance data to optimise and improve systems

Over time, products tend to standardise, but systems would become the differentiator.

Why This Model Would Work in India

India is the unique place where make this model is likely to work and expand, because:-

First, demand can be aggregated at scale—by state governments, municipal bodies, logistics players, and industrial enterprises. This enables large, structured deployments.

Second, long-term contracts make financing viable. Companies can invest in assets, systems, and workforces with greater confidence.

Third, the model aligns with India’s need for employment and skilling. Deployment and operations create sustained demand for technicians, operators, and maintenance personnel.

Finally, India’s federal structure ensures that demand is not singular or saturated. Multiple states, cities, and industries generate a layered and continuous pipeline of projects.

Adoption, therefore, is would be sequential rather than simultaneous—allowing companies to scale without immediately saturating the market.

Conclusion: Design as System Architecture

What is emerging from this shift is a new understanding of design itself.

Design is no longer confined to shaping products. It is about:

structuring applications,

anticipating lifecycle realities,

and enabling continuous performance.

It is, in effect, a form of system architecture.

India’s industrial transition, particularly in green energy linked sectors, is not just about adopting new technologies. It is about adopting a new logic of design — one that begins with application, extends through deployment, and remains accountable through operation.

In this logic, products are no longer endpoints. They are components of systems that must work—reliably, repeatedly, and at scale—in the real world.