iWebest.1995Talk to an expert
Company

An employee-owned commerce consultancy. Built for the long programmes.

iWeb has worked on the same subject — enterprise commerce — since 1995. Long enough to have lived through several platform generations, and to have learned that platforms are part of the answer, not the identity. The value is judgement: commercially grounded, operationally aware, accountable in ten years' time.

Founded
1995
Programmes
600+
Engineers
42
Avg. tenure
11 yrs
Late deliveries
0 of last 8
Contents · 7 sections
  1. 01The kind of company iWeb is.
  2. 02Problem-led, platform-agnostic, commercially grounded.
  3. 03Commerce as an ecosystem, not a single platform.
  4. 04Operational and data maturity, not just websites.
  5. 05Long-term partnerships, by structure not by claim.
  6. 06Cross-functional, senior, employee-owned.
  7. 07What we are — and what we deliberately aren't.
01 · The kind of company we are

An enterprise commerce specialist — not a generic digital agency.

We are a senior, employee-owned team of commerce specialists. We've been doing the same job for thirty-one years — taking complex commerce businesses and making them work properly under real operational pressure. Across that time the platforms have changed, the rhetoric has changed, the trends have changed. The problem we solve has not.
We are not a "full-service digital agency". We don't run brand campaigns, we don't pitch innovation theatre, and we don't farm out delivery. We design, build, integrate and run enterprise commerce — and we say no to the parts that aren't ours.
Decade
What it was
Programmes
1995–2004
Founded
First wave of UK e-commerce. Custom platforms, hand-rolled integrations, learning the operational realities of trading online.
14
2005–2014
Specialism formed
Magento partner from 2009. Enterprise programmes for retail, B2B, manufacturers. Integration patterns harden.
180+
2015–2022
Scale & complexity
Adobe Commerce Gold. Multi-region, B2B, marketplaces, headless. The team learns where complexity actually breaks.
290+
2023–now
Platform-agnostic
Employee-owned. AI for commerce. Pragmatic replatforms. The platform is part of the answer, not the identity.
120+
The same problem, four decades. Every era reinforced the discipline beneath the platforms.
02 · How we think

Problem-led, platform-agnostic, commercially grounded.

A modern enterprise buyer does not want a vendor that's structurally biased toward one piece of software. They want a partner that recommends what fits — operationally, commercially, organisationally — and that's prepared to push back when a piece of work isn't worth doing. These are the principles that govern every recommendation we make.
01
Operational fit before software fit
A platform decision sits inside a wider operational reality — fulfilment, finance, service, governance. We start with the operation, not the catalogue of vendors.
02
Recommend what fits, not what we sell
Adobe Commerce is one option among several. So is staying. We will tell you when the answer is "fix what you have", and we will say no to a programme that should not run.
03
Maintainability over novelty
A system that the in-house team can keep healthy beats a more impressive one that depends on us forever. We optimise for the second year, not the launch week.
04
Governance, by default
Every decision has a named owner, an approval threshold and a rollback path. Audit and accessibility are designed in early — not retrofitted under deadline.
05
Evidence over opinion
We measure where the friction actually is — pages, queries, integrations, hand-offs — and prioritise from the data. Not from the loudest voice in the steering group.
06
Senior people, on the work
The architects on the brief are the architects on the build. No bait-and-switch. Decisions are made by people who have seen the same situation before.
03 · The connected commerce ecosystem

Commerce is an ecosystem, not a single platform.

Successful commerce sits on top of eight to twenty-four connected systems. The platform is one of them. Treating the website as the centre of gravity is the single most common cause of programmes that look good in demo and break in trading.
The matrix shows where we have practiced expertise — depth measured in named architects, programmes shipped, and years on production. The right shape of programme draws on several of these at once.
Capability
Layer
Depth
Shipped
Storefront & checkout
Customer-facing layer
180+
PIM & product data
Product information
60+
ERP integration
Operations
120+
OMS · order orchestration
Operations
70+
Search · vector + keyword
Discovery
40+
B2B commerce
Account & quoting
50+
Headless · composable
Architecture
24+
CDP · customer data
Marketing & service
18+
Marketplaces · syndication
Distribution
22+
Payments & tax
Operations
90+
AI for commerce
Intelligence layer
12
WCAG · accessibility
Cross-cutting
every
Depth · ●●●● architect-led practice · ●●● shipped repeatedly · ●● working knowledge · ● selective engagements

Commerce expertise compounds. Software comes and goes. The judgement that runs underneath stays.

The next sections cover what makes that judgement commercially credible — depth over breadth, partnership over churn, and a team built for the problem, not the trend.
31
Years on the same problem
Since 1995 — enterprise commerce, not pivots
8.4
Average client tenure (yrs)
Top 10 accounts · vs industry ~2.1 yrs
11
Avg engineer tenure (yrs)
Senior people stay. The team you meet delivers.
100%
Employee-owned
EOT structure · accountability built in
04 · Operational and data maturity

The hard part of commerce is operational — and that's where we work.

Most digital agencies stop at the website — UX, campaigns, the storefront layer. The serious problems sit underneath: ERP sync, order orchestration, product data quality, integrations, governance, fulfilment edge cases, B2B account complexity. The work that pays back over a decade is the work that gets that substrate right.
Layer
Where most agencies stop
Where iWeb works
Brand campaigns · innovation theatre
Where most "full-service" agencies position. Often where iWeb does not work at all.
●
Storefront UX · campaigns · creative
Visible layer. We do this when it serves the operational programme, not as a standalone deliverable.
●
Storefront engineering · checkout
Where most agency relationships end. We start here — never finish here.
●
Integrations · ERP · OMS · WMS
The systems trading actually depends on. Eight to twenty-four per programme.
●
Product data · PIM · taxonomy
Where most "AI in commerce" pilots quietly die. Get this right or nothing else compounds.
●
Operational data · governance · audit
Customer, order, inventory, fulfilment state. Audit trails. Reversibility. The unglamorous half.
●
Visible → operationalTypical "digital agency"iWeb · whole substrate
We treat the storefront as the visible tip. The judgement, integration depth and data hygiene underneath it are what make the storefront work — and what most procurement processes underweight at brief stage.
05 · Long-term partnership

We build long-term partnerships because we think long-term ourselves.

Employee ownership matters because of what it makes possible — accountability that survives staff changes, decisions made against a ten-year horizon, and a team that doesn't churn out from under a programme. The numbers below are the consequence: clients stay with us, and the engineers running their programme stay too.
Measure
iWeb
Industry baseline
Top-10 client tenure
Reported in years
8.4
2.1
Average engineer tenure
Reported in years
9.2
2.4
Architect tenure (≥10 yrs)
count of architects
7
1
Programmes with same lead end-to-end
Reported in %
92%
31%
iWeb figures · 2024–26 internal HR & account record · Industry baseline · published consultancy churn surveys 2023–25.
The same architect who designed an integration in 2019 is still around to extend it in 2026. That is not a minor convenience. It is the difference between a system that compounds and a system that gets re-explained to a new team every two years.
06 · The team

Cross-functional, senior, and the same people in year five.

We do not run a "designers and developers" model. The people most clients spend the most time with are architects, integration leads, commerce strategists and operational thinkers — supported by senior engineering, design and delivery practices.
Composition is deliberately weighted toward depth. Senior architects, principal engineers and commerce strategists outnumber generalist roles. The team you brief is the team that delivers, and stays.
042 engineering & specialist staff
Practice
Heads
Avg yrs
Solution & integration architects
7
12
Principal & senior engineers
11
10
Commerce strategists & analysts
5
11
Front-end & UX leads
6
9
Delivery, programme & QA leads
8
10
Platform · cloud · operations
5
11
42 engineers on staff · senior-led · employee-owned · weighted toward architects and operational specialists.
07 · What we are — and what we aren't

A specialist, not a generalist. A partner, not a vendor.

The clearest way to describe a company is by the work it deliberately doesn't take. We say no to programmes that don't fit, to platforms that won't pay back, to AI work without governance, and to relationships that need a sales team to keep them alive. The list below is what we are — and what we aren't, on purpose.
What iWeb is
What iWeb isn't
Enterprise commerce specialists
A "full-service digital agency" doing everything for everyone.
Operationally aware integrators
A storefront-only shop that hands the hard parts to "someone else".
Platform-agnostic — recommend what fits
Incentivised to push the platform we resell most of.
Long-term partners, employee-owned
A consultancy structured for short engagements and bench rotation.
Senior people on the work
Architects on the brief, juniors on the build.
Calm, evidence-led, governance-first
Trend-driven, demo-led, AI-hype merchants.
Transparent about what we don't do
Saying yes to anything to keep the pipeline open.
Accreditations & assurance
Gold Commerce Partner
Specialized in Commerce
ISO certified
27001 · 9001 · 42001
Cyber Essentials Plus
Independently verified security
WCAG 2.2 AA
Accessibility embedded by design
Employee-owned
The same team, long term
Next step

Brief us. We'll tell you what's worth doing, what isn't, and what we'd do.

You'll get a written response from a senior expert — sized, sequenced, with named owners and a phased plan. Not a pitch deck. Not a generic capability one-pager. Whoever responds is the person you'd work with.
Talk to an expertor re-read the seven sections →
Mature · Commercially grounded · Operationally aware · Governance-first · Long-term · Employee-owned