From Interface to Operating Position: Where Technology Builds Durable Advantage

From a useful tool to an operating position

A product does not need to do everything to be valuable. In fact, many successful companies begin with a narrow, clear use case. They solve one frustrating problem well enough that customers are willing to change an existing habit.

The more durable opportunity emerges when that initial use case gives the company a way to understand – and improve – the workflow around it.

Consider what happens when a task is completed in a business. Someone needs information, another person makes a decision, a service is delivered, a record is updated, and the next action follows. A product becomes more important when it helps connect these steps rather than improving only one isolated moment.

This is what we mean by an operating position. It is not a claim to own every part of a customer’s business. It is a place in the workflow where the company can consistently make work more reliable, more visible or easier to manage.

Tyred, one of the companies in our portfolio, is a good illustration. It started with a simple promise: a mobile mechanic who comes to the bike, rather than the other way round. But a micromobility operator running hundreds of e-bikes and cargo bikes does not ultimately buy repairs. It buys uptime. By combining scheduled maintenance, fleet software and telemetry, Tyred stops being a supplier called when something breaks and becomes part of how the fleet is planned and kept on the road. The commercial relationship follows the same path – from paying per job towards multi-year contracts with service levels. That is a very different position to hold.

The customer should feel the benefit in practical terms: fewer handoffs, less uncertainty, quicker resolution or a better understanding of what needs to happen next.

Where durable advantage actually comes from

A strong interface may help a company acquire customers, but the design itself is rarely the reason they stay.

Customers stay when the product holds useful context, supports important decisions or coordinates activity that would otherwise be fragmented. That value can build over time, provided the company uses each new interaction to improve the experience rather than simply collect more data.

The key is relevance. More information is not automatically useful. The company needs to turn information into something that helps the customer act: a clearer recommendation, a better-timed intervention, a more reliable service or a simpler process.

Zinit, another portfolio company, shows the difference in corporate procurement. A tool that helps a buyer find suppliers faster is useful. Zinit’s AI-native platform goes further: it runs sourcing, RFPs and competitive tenders end to end for large buyers. Because it sits across the full cycle, it learns which suppliers deliver, which categories run over budget and where decisions stall. Each new purchase then starts from a better position than the last. The value is not the size of the supplier database; it is how much better the next decision becomes.

Trust is equally important. Companies that sit close to important workflows are often entrusted with sensitive information, payments, assets, customer relationships or service histories. They need to earn that role through reliable execution and clear communication. A customer will not make a product part of their operations simply because it has more features.

This is also why complexity should not be mistaken for defensibility. A growing list of capabilities can make a product harder to use without making it more valuable. The strongest systems have an internal logic: each additional capability strengthens the core outcome the customer already values.

The questions behind the product demo

Product demonstrations are useful, but they rarely show how a company fits into the customer’s real environment. To understand that, we return to a smaller set of practical questions.

1. How important is the underlying workflow?

   A product can be used often and still be non-essential. We want to know what changes if it disappears. Does the customer lose a convenience, or does an important process become slower, riskier or harder to manage?

2. What improves beyond the user interface?

   The answer should be tangible. It may be better uptime, lower cost, stronger service quality, improved visibility or faster decision-making. A product experience matters, but it must lead to a meaningful result.

3. Does the company build useful context over time?

   Some products become more valuable as they learn how a customer operates. The test is whether that context makes future actions better for the customer – not whether it simply adds another layer of data or reporting.

4. Why should a customer trust the company with a larger role?

   Trust may come from product reliability, domain expertise, strong support, transparent pricing or responsible data practices. It cannot be assumed; it has to be built into the operating model.

5. Does scale strengthen the business?

   Growth is valuable when it improves the product, service model or economics in a way that benefits the next customer. It is less meaningful when scale merely adds volume and operational complexity.

What this means for founders

For founders, moving from a product to an operating position usually takes discipline.

It requires staying close to the real work rather than designing around an idealised user journey. The exceptions often matter as much as the standard flow: where does information get lost, who is forced to make a manual decision, and what happens when something goes wrong?

It also means choosing what not to build. The goal is not to create the largest possible product suite. It is to make the core workflow more effective and add capabilities only when they deepen that advantage.

The companies that do this well often start with a simple promise. They then earn the right to do more by delivering that promise consistently.

What this means for capital

For investors, the challenge is to look beyond early adoption and product quality.

Revenue growth, customer engagement and a strong interface are important signals. But they do not fully explain whether a company can become difficult to replace. That requires a view of the customer relationship: where the product sits, what it enables and whether its role becomes more valuable as the business develops.

The most interesting companies are often those that make an existing process feel less like a series of disconnected tasks and more like a coherent system. They do not need to capture every part of the workflow. They need to own a part that matters enough to improve the whole.

That is where technology can create durable advantage: not by being more visible than everything else, but by becoming reliably useful when the real work needs to get done.