Business before technology. What does that actually mean?

At GENE, we talk frequently about putting business before technology. It's a principle that influences how we approach partnerships, evaluate opportunities and recommend investment.

It's also a claim that deserves some explanation. Most eCommerce agencies will tell you they understand commercial objectives and align development with business goals. These are reasonable expectations of any competent agency, so what actually distinguishes a business-led approach?

For us, the difference lies in the decisions that follow. It means understanding a business well enough to challenge its assumptions, recognise when technical work needs to take priority and question whether a proposed investment will genuinely deliver value.

It also means accepting that the most technically impressive solution isn't necessarily the most commercially valuable one.

Understanding the business before defining the work

When we inherit an established Adobe Commerce or Magento platform, there's rarely a shortage of potential improvements.

Performance issues, technical debt, outdated integrations and growing development backlogs are familiar territory. It's entirely possible to begin addressing these problems and demonstrate progress without developing a particularly deep understanding of the business itself.

The difficulty is knowing whether that work represents the best use of the merchant's investment.

Before making recommendations, we need to understand how the business operates, where its revenue comes from, what matters to its customers and what its leadership team wants to achieve over the next few years.

An organisation focused on improving profitability within its existing customer base will have different priorities from one preparing for international expansion. A B2B distributor looking to increase digital adoption among trade customers faces different challenges from a direct-to-consumer retailer trying to increase purchase frequency.

These distinctions influence the technology required, the way success should be measured and the order in which improvements should be delivered.

Our onboarding process reflects this. Alongside technical discovery, we undertake a dedicated business discovery process, documenting the merchant's commercial context, products and objectives in a shared client context board. This gives everyone involved in the partnership a common understanding of what the business is trying to achieve.

That understanding continues to inform decisions long after onboarding is complete.

Making technology decisions with commercial context

Once we understand where the business wants to go, we assess whether its existing eCommerce operation can support that direction.

An Adobe Commerce platform may serve current requirements perfectly well while presenting significant obstacles to future plans. Architecture, integrations and customisations that made sense several years ago can become constraints as the business evolves.

Technical debt is a good example. Although often discussed as an engineering problem, its commercial consequences can be substantial. Development takes longer, changes become harder to estimate and an increasing proportion of the budget is spent navigating existing limitations.

Our technical assessments examine architecture, code quality, security, performance and third-party extensions, identifying which issues present immediate risks and which could restrict future development.

The findings are then considered against the business's priorities.

For a merchant planning international expansion, architectural improvements may be essential before entering new markets. For one focused on conversion, addressing persistent performance problems could offer a more immediate return than introducing additional functionality.

The same commercial scrutiny applies to new technology.

Adobe Commerce and Mageto already provide considerable capabilities, particularly for businesses managing complex catalogues, customer-specific pricing, multiple websites and B2B purchasing processes. Yet merchants don't always make full use of the functionality they already own.

Before recommending another extension, integration or bespoke solution, we consider whether the requirement can be addressed through existing capabilities or improved configuration.

Every additional technology introduces costs beyond its initial implementation, including licensing, maintenance, compatibility and ongoing management. Those responsibilities need to be justified by the value they create.

Sometimes the right recommendation is to introduce something new. Sometimes it's to simplify what already exists.

What this looks like in practice

For Vivactive Group, customer retention and repeat purchasing are important commercial priorities. Many customers regularly purchase essential healthcare products, creating an opportunity to improve convenience while developing recurring revenue.

The solution involved subscription functionality that gave customers meaningful control over their orders, including the ability to pause deliveries, skip purchases, change products and update account details.

The commercial objective shaped the technical requirements. A subscription model would only deliver lasting value if it accommodated how customers actually wanted to purchase.

Our work with Krispy Kreme illustrates a different challenge.

Increasing digital sales required more than improving the website. The business needed closer connections between its digital channels, physical stores, fulfilment operations and loyalty systems.

The resulting Magento development programme addressed those wider operational requirements, supporting a significant increase in online sales.

These projects involved very different technical solutions, but the underlying principle was consistent: understanding the commercial opportunity first, then determining what technology was needed to realise it.

A roadmap should explain why the work matters

A development backlog and a business-aligned roadmap are not the same thing.

A backlog captures requirements from different stakeholders. A roadmap establishes which deserve investment, in what order and for what commercial reason.

Consider a merchant whose marketing team wants greater content flexibility, customer services needs better account management and technical teams have identified architectural improvements. Each request may be entirely valid, but the business still needs to decide where its limited budget will deliver the greatest value.

Our approach is to build a shared roadmap with the merchant, considering likely investment, expected returns, technical dependencies and commercial priorities.

That sometimes involves challenging the order of proposed work, questioning the value of a feature or recommending foundational improvements before more visible changes.

Technical recommendations should be subject to the same scrutiny. An architectural improvement may be sound engineering, but the merchant deserves to understand what it will enable and why the investment matters.

The roadmap also needs to evolve. Regular reviews, performance analysis and experimentation allow priorities to change as the business learns more about its customers and the results of previous investments.

The objective is to move the conversation beyond whether development has been completed to whether it has achieved what the business needed.

Protecting the capacity to move forward

Even a well-considered roadmap achieves little if the resources allocated to it are continually absorbed by platform maintenance.

Security updates, upgrades, monitoring and incident response are essential responsibilities for any established eCommerce operation. Problems arise when this work repeatedly competes with strategic development for the same agency hours.

Our Unlimited Support model is designed to address that challenge, helping merchants maintain a secure, reliable platform while protecting the capacity needed for ongoing improvement.

We organise this work around three connected areas: Platform Management, eCommerce Evolution, and Transformation. Platform Management covers the operational responsibilities of maintaining the platform, eCommerce Evolution focuses on continuous improvement and the roadmap, while Transformation addresses larger strategic initiatives.

Separating these responsibilities helps ensure that keeping the business running doesn't continually come at the expense of making it better.

Business before technology, in practice

Putting business before technology doesn't make technical expertise less important. It gives that expertise a clearer purpose.

A well-architected platform, effective integrations and carefully chosen functionality can create substantial commercial value. Understanding the business determines where those investments will make the greatest difference.

For GENE, this means knowing enough about our clients to recognise what needs to change, what should be preserved and where investment is most likely to deliver a meaningful return.

It means being prepared to challenge priorities, recommend a simpler solution or explain why less visible technical work deserves attention.

Above all, it means ensuring there's a clear commercial reason behind the work we're recommending.

The starting point remains the same two questions.

Where are you now? Where do you want to go?

Everything between those two points should be about making the right decisions to get there.

Talk is cheap. Proof is priceless.

Your eCommerce roadmap should reflect where your business wants to go, not simply what your platform needs next.