From Technical Breakthrough to Commercial Value
What building FlowLift, Canada Oilfield Equipment, and ENG R&D taught me about governing innovation
By Reinaldo Varela
Innovation is often described as the moment when a new idea takes shape. In practice, the idea is usually the easy part.
The harder work begins afterward: determining whether the idea addresses a meaningful problem, whether customers will adopt it, whether it can perform reliably under real operating conditions, and whether the organization can build a sustainable business around it.
My experience with FlowLift, Canada Oilfield Equipment, and ENG R&D has given me a close view of that journey. Together, these businesses span equipment transactions, customer relationships, engineering, and technology development in the oil and gas sector. Their evolution reinforced a lesson that applies far beyond energy:
A technical breakthrough creates possibility. Commercial discipline turns that possibility into value.
Begin with the problem, not the invention
FlowLift began in Alberta with a focus on water-lifting challenges in gas wells. Like many entrepreneurial ventures, its direction evolved as we gained a better understanding of the market.
That experience taught me that leaders must distinguish between being committed to a purpose and being attached to a particular solution. The purpose may remain constant while the commercial approach changes significantly.
Customers rarely begin by asking for an innovation. They describe an operating constraint: production is declining, equipment is unavailable, information is incomplete, costs are rising, or an existing process is not reliable enough. The innovator’s first responsibility is therefore not to promote a technology. It is to understand the underlying problem well enough to determine whether a new solution is warranted.
For boards evaluating innovation investments, this leads to a fundamental question:
Are we funding a technology in search of a market, or solving a costly and persistent customer problem?
The distinction matters. A technically elegant solution can still fail if the problem is not urgent, the economic benefit is unclear, or adoption requires more change than the customer is willing to accept.
Market access is a source of intelligence
Through Canada Oilfield Equipment, we developed an international business helping customers locate, evaluate, acquire, and move new and used oilfield equipment.
At first glance, equipment trading and advanced research and development may appear to be separate activities. In reality, the commercial business created an important learning environment.
Every transaction revealed something about the market. Customer requests showed where equipment was difficult to obtain. Inspections exposed recurring reliability and maintenance issues. Negotiations clarified what customers valued and what they were prepared to pay for. International transactions also demonstrated how geography, logistics, regulation, technical standards, and local operating practices affect purchasing decisions.
This type of proximity to the customer is strategically valuable. It produces information that rarely appears in a laboratory or financial model.
For an innovation organization, an established commercial network can serve as more than a sales channel. It can become an early-warning system for changing customer needs, a source of product requirements, and a practical testing ground for commercial assumptions.
Boards should therefore look beyond conventional research metrics and ask:
How close is the innovation team to the customer?
What evidence supports the stated market need?
Are commercial teams informing product development?
What has the company learned from customers who chose not to buy?
Does the organization understand the customer’s full adoption cost?
These questions help prevent innovation from becoming isolated from the market it is intended to serve.
Build across disciplines
As our understanding of industry needs expanded, ENG R&D brought together mechanical, electronic, and software engineering capabilities to develop oilfield technologies, including production-logging, cement-bond-logging, and ultrasonic-integrity systems.
Creating a complex industrial product requires much more than a strong technical concept. The product must operate under demanding physical conditions, generate dependable information, integrate multiple engineering disciplines, and fit the customer’s existing workflow.
The greatest challenge is often at the boundaries between disciplines.
A mechanical component may perform as designed while creating limitations for the electronics. A sensor may generate high-quality data that software cannot process efficiently. A product may succeed in controlled testing but prove too difficult, expensive, or time-consuming to deploy in the field.
These are not purely engineering problems. They are leadership and organizational-design problems.
Successful development requires teams to share a common definition of the customer outcome. Each discipline must understand how its decisions affect the complete system—not simply its own component. Leaders must also create an environment in which technical concerns surface early, assumptions are challenged constructively, and unfavorable test results are treated as information rather than failure.
For directors, interdisciplinary execution is an important indicator of innovation maturity. A company may employ exceptional specialists, but commercial success depends on their ability to operate as one system.
Treat commercialization as part of product design
Commercialization should not begin after engineering is complete. It should influence development from the beginning.
A product’s value is determined not only by what it can do, but by the economic result it can produce for the customer. That may include better information, fewer operational interruptions, reduced risk, greater recovery, lower deployment costs, or faster decision-making.
The business case must be credible and understandable. Customers need to know:
What problem the product addresses.
How its performance compares with existing alternatives.
What operational changes adoption requires.
How the expected benefit will be measured.
What support exists if field conditions differ from expectations.
This is particularly important in oil and gas, where new tools may be deployed in high-pressure, high-temperature, corrosive, or otherwise demanding environments. Reliability is not an added feature. It is a prerequisite for trust.
The same principle applies in other industries. A technical specification may attract attention, but customers ultimately purchase outcomes. Product teams that cannot translate engineering performance into operational and financial value will struggle to move beyond demonstrations and pilot projects.
Stage capital around evidence
Innovation requires patience, but patience should not mean unlimited investment without clear learning milestones.
Boards can help management create a staged path from concept to commercial deployment. At each stage, the organization should retire a different category of risk:
Problem risk: Is the customer need real and sufficiently important?
Technical risk: Can the solution perform as intended?
Integration risk: Can the complete system operate reliably?
Adoption risk: Can customers incorporate it into field operations?
Economic risk: Does the value justify the total cost?
Scale risk: Can the company manufacture, support, and deliver it consistently?
Capital should follow evidence. Early investment may validate the underlying principle. Subsequent investment can support prototypes, field testing, certification, manufacturing, and commercial expansion.
This approach does not eliminate uncertainty. It makes uncertainty visible and manageable.
It also gives directors a better basis for oversight. Rather than asking only whether a project is on time and on budget, a board can ask what the company has learned, which assumptions have been validated, which risks remain unresolved, and what evidence is required before the next investment decision.
The board’s role in innovation
Boards should support ambition while maintaining discipline. Too much caution can prevent a company from pursuing meaningful opportunities; too little scrutiny can allow enthusiasm to outrun evidence.
Effective oversight requires a balance of strategic questions:
Does the innovation reinforce the company’s purpose and capabilities?
Is management candid about both technical and commercial uncertainty?
Are incentives tied to learning and customer outcomes, rather than activity alone?
Is intellectual property protected appropriately?
Can the organization support the product after the initial sale?
What conditions would cause the company to accelerate, redesign, partner, or stop?
The willingness to stop or redirect a project is particularly important. A pivot is not necessarily a failure. It can be evidence that leadership is responding intelligently to the market.
Our own evolution—from addressing a specific production challenge, to building an equipment marketplace, to developing integrated engineering capabilities—was not a straight line. It was a process of listening, adapting, and connecting market knowledge with technical capability.
Innovation is a system
The most durable lesson from FlowLift, Canada Oilfield Equipment, and ENG R&D is that commercialization does not result from invention alone.
It emerges from a system: a real customer problem, multidisciplinary talent, market access, technical validation, economic clarity, disciplined capital, and leadership willing to adapt.
When these elements work together, research and development can become more than a cost centre or collection of promising ideas. It can become a repeatable capability for creating strategic and commercial value.
That is the standard boards should apply when evaluating innovation. The central question is not simply, “Is the technology impressive?”
It is:
Does the organization have the insight, discipline, and execution capability to turn this breakthrough into an outcome customers will trust—and a business that can endure?
