Strategic Project work

E-Commerce & Systems
Transformation

For e-commerce businesses where operational infrastructure is limiting growth, and better marketing alone will not solve the underlying issues. Covers information architecture, product data structure, systems integration, platform evaluation, and phased transformation planning.

The problem this solves

When the infrastructure itself is the problem.

You know your e-commerce operation is not working the way it should. The store is a legacy of accumulated decisions. The ERP does not reliably talk to the storefront. Someone is manually updating prices. Product data is inconsistent. Every attempt to improve one area reveals additional operational dependencies, inconsistencies, or structural limitations elsewhere in the business.

These are not individual problems to be fixed one at a time. They are the cumulative result of a store built on foundations that were never designed to scale. Investing further in growth on top of those foundations produces more waste, not more revenue. This engagement rebuilds those foundations.

What the work involves

Architecture first, then build.

The engagement begins with a full operational review of the current state. Structural decisions creating inefficiency, complexity, or operational risk are identified, prioritised, and sequenced before recommendations are made.

Development costs, whether agency or freelance, are separate and not included. Percipient defines the architecture, specifies the operational requirements, oversees delivery, and ensures implementation aligns with the agreed strategic and operational standards. Development itself remains the responsibility of the chosen technical delivery partner.

01

Conduct a full operational audit of the current e-commerce infrastructure to identify the highest-impact operational and commercial issues.

02

Design a new information architecture: collection structure, navigation logic, product taxonomy, and buyer journey

03

Define a scalable product data structure designed to support operational consistency across systems and channels.

04

Evaluate and recommend the appropriate technology stack, including PIM, CRM, and ERP integration approaches, based on operational requirements and commercial objectives.

05

Build a phased transformation roadmap that sequences work by commercial impact and operational risk

06

Provide strategic oversight throughout implementation, working alongside development partners, agencies, or internal teams.

07

Establish ongoing governance and process standards so the systems remain operationally consistent and scalable after implementation.

What you receive

From audit to operating standard.

01

Infrastructure audit report

A detailed assessment of the structural issues affecting operational efficiency, scalability, and commercial performance, including prioritised recommendations.

02

Information architecture specification

Navigation, taxonomy, and collection logic designed for your catalogue and your buyers.

03

Product data structure specification

A clean, scalable data structure and metafield specification that works across your systems.

04

Technology recommendation

Platform and vendor recommendations grounded in operational requirements, scalability, and commercial fit rather than industry trends.

05

Phased transformation roadmap

Work sequenced by commercial priority and operational risk, with clear milestones.

06

Implementation oversight

Active oversight throughout delivery to maintain quality and catch problems before they compound.

07

Process documentation

Operating standards and governance frameworks so the operation stays clean after the engagement ends.

Who is this for

Types of businesses this engagement is designed for.​

01

E-commerce businesses whose infrastructure has not kept pace with their commercial ambition

02

Shopify or Shopify Plus operators managing large catalogues (1,000+ SKUs) without proper data architecture

03

B2B businesses where disconnected systems – ERP, CRM, PIM, and storefront – are creating ongoing operational inefficiency and complexity

04

Companies that have invested in growth but whose back-end cannot support it

05

Businesses preparing a platform migration or major rebuild and needing strategic direction before development begins

Investment and timeline

The most variable engagement in scope.

Investment

Investment varies depending on transformation scope, operational complexity, and level of implementation oversight required.

Timeline

6-12 weeks. Timeline varies with scope and implementation complexity, confirmed after discovery phase. 

How it starts

A pre-engagement conversation to establish the scope and confirm fit. For larger or more complex operations, a discovery session may be recommended before a full proposal is issued.

Not sure what you need?

Start with a conversation.

Tell us about your current e-commerce operation, what is no longer working efficiently, and where the biggest operational frustrations exist. We will give you an honest initial assessment of where the underlying issues may sit.