Skip to content
Project management · Systems integration · E-commerce

Running ERP projects, connecting systems,integrating stores — from Zurich.

One point of contact from the requirement through to live operation. So that change lasts.

Responsibility, not recommendation.

Our perspective
Project status, schematic: 72 per cent progress, milestones, risks, decisions and budget of an ERP integration
Fig. 01 Project status — schematic representation.

We have sat on both sides of the table — as the client and as the project management.

That is why we plan
from operation onwards —
not from go‑live.

A project has succeeded when it lasts without us.

Services

Four disciplines,
one responsibility.

01  ·  Governance

Project management

External project management for ERP rollouts, SAP migrations and system replacements — for companies and public administration.

Project management for ERP rollouts→

Fig. 02 →Programme plan — the go / no-go decision for operation stays visibly open.
PROGRAMME PLAN · ERP CONSOLIDATIONSCHEMATIC REPRESENTATIONCOMMITTEESteering CommitteeGATEG3 · RealisationOWNERom3 programme managementQ1Q2Q3Q4ConceptRealisationTestOperationM-01 concept sign-offM-02 test acceptanceM-03 go / no-goM-04 go-liveIDDECISIONCOMMITTEESTATUSE-07Platform sign-offSteering CommitteeApprovedE-09Go / no-go for operationExecutive BoardPendingREVISIONTest window scheduled before go-live · gate G3 addedSIGN-OFFQA gate passed · om3 programme management
Fig. 02 Programme plan with gates and decision log — schematic representation.
INTEGRATION LANDSCAPE · TARGET ARCHITECTURESCHEMATIC REPRESENTATIONOWNERom3 integration architecturePATTERNHub-and-SpokeINTERFACES6 activeOrderOrders · stockIF-01 · REST · CRITICALCustomer dataIF-02 · REST · REAL TIMEProduct dataIF-03 · DELTAPaymentsIF-04 · ISO 20022Dispatch adviceIF-05 · EDIFACT · HOURLYCustomerActor · externalShop / PortalHub · orchestrationERPleading systemCRMCustomer masterPIMProduct masterPaymentPSP · settlementWarehouseWMS · dispatchPRINCIPLE: exactly one defined path per business object · no point-to-point connectionsREVISIONV2.1 · 3 April: IF-05 dispatch advice added (E-04) · V2.0 · 12 February: target picture consolidatedSIGN-OFFArchitecture board 8 April · interface catalogue, annex B
CustomerShop / PortalCommerce platformERPCRMPIMPaymentWarehouse
Fig. 03Target architecture of an integration landscape — schematic representation; for example Shopify, Plenty and PayPal to Business Central, via Alumio.
02  ·  Interfaces

Systems integration

Shopware, Shopify or WooCommerce connected to SAP, Odoo, Business Central or Abacus. So that data is entered only once.

Interfaces between store and ERP→

← Fig. 03Integration landscape — one defined path per business object.
03  ·  Platform

E-commerce

B2B and consumer stores on Shopware, Shopify, WooCommerce or Ecwid, connected to your leading system.

Online store development→

Fig. 04 →Conversion concept — every step backed by a measuring point.
CONVERSION CONCEPT · FROM ENTRY TO COMPLETIONSCHEMATIC REPRESENTATIONOWNERom3 UX designFUNNELF-01 · 3 stagesSTATUSIn deliveryS-01 · ENTRYS-02 · DECISIONS-03 · COMPLETIONIA-01IA-04E-12VALCP-01SelectionMP-1PurchaseMP-2Product listProduct detailCheckoutIA-01 · filters: max. two levelsA11Y · grid operable by keyboardKPI · entry → product rateIA-04 · price visible without scrollingE-12 · one primary action per screenKPI · basket rateIA-07 · guest checkout as standardVAL · inline validation per fieldKPI · checkout completion rateUSER PATH F-01VisitorSelectionDecisionPurchaseTransactionMP-3 · revenue-relevantPRINCIPLE: every interaction leads to exactly one measurable business outcomeREVISIONV1.1 · 21 May: checkout reduced to 3 steps (E-12) · V1.0 · 2 May: first versionSIGN-OFFUX review 26 May · om3 UX design
Fig. 04Conversion concept of a purchase path with measuring points — schematic representation.
SITE PLAN · FROM EXISTING ADDRESSES TO THE NEW SITESCHEMATIC REPRESENTATIONOWNERom3 web developmentROUTESR-01 · 4 groupsSTATUSIn deliveryS-01 · EXISTINGS-02 · MAPPINGS-03 · NEW SITEA-01A-14NO TARGET1:1Z-09 · INTENT301 · ONE HOPR-07CP-01ACCEPTANCE BEFORE SWITCHIntentMP-1StructureMP-2Existing addressesRedirect mapSite structureA-01 · every address recordedSEO · position before the rebuildKPI · impressions per addressZ-09 · target with the same intent301 · one hop, no chainKPI · hops per addressR-07 · structured by serviceA11Y · structure keyboard-operableKPI · findability after go-liveROUTE PATH R-01RecordMapBuildAcceptSwitchMP-3 · no downtimePRINCIPLE: every existing address leads in one hop to the page with the same intentREVISIONV1.0 · 12 Oct. first versionAPPROVALRoute acceptance before the switch · om3 web development
Fig. 05Site plan of a relaunch with its redirect map — schematic representation.
04  ·  Development

Web development

Websites on open systems, custom built where the standard is not enough.

Website development→

← Fig. 05Site plan — every existing address with one target and one hop.
How we work

Four steps that give certainty.

  1. Understand

    Clarify the starting point, the objectives and who is involved.

    DELIVERABLES:Stakeholder map STK-01 · As-is analysis IST-01 · Requirements catalogue REQ-01

  2. Plan

    Set out the approach, the milestones and the risks.

    DELIVERABLES:Programme plan PLN-01 · Target architecture ARC-01 · Risk register RSK-02

  3. Deliver

    Steer, decide, deliver — week by week.

    DELIVERABLES:Status reports STA-04 · Decision log DEC-05 · Quality Gates QG-03

  4. Anchor

    Handover, operation and knowledge that stays.

    DELIVERABLES:Operational handover OPS-01 · Runbook OPS-02 · Knowledge transfer KT-01
Case studies

Projects that last.

See all case studies→

Project management · administrationPublic sector (canton)→
Integration · large enterpriseBlueBioTech International→
E-commerce · SMESpyk Bänder AG→
E-commerce · large enterpriseHeld AG→
Project management · administrationPublic sector (canton)
PROJECT SHEET · REF-01om3 PROJECT REGISTER
Project management in a cantonal administration
ROLEOverall project managementCONTEXTA project of a cantonal administrationSECTORPublic administrationMETHODHERMESSTATUSongoing
CLIENT
Public sector (canton)
Summary
details in the case study

View case study: public administration→

Integration · large enterpriseBlueBioTech International
PROJECT SHEET · REF-02om3 PROJECT REGISTER
Systems integration via central middleware
ROLEIntegration architectureCONTEXTData flows between shop, payment and ERPSECTORBiotechnology · tradeSYSTEMSShopify · Plenty · PayPal → Business CentralMIDDLEWAREAlumioSTATUSin production
CLIENT
BlueBioTech International
Summary
details in the case study

View case study: BlueBioTech→

E-commerce · SMESpyk Bänder AG
PROJECT SHEET · REF-03om3 PROJECT REGISTER
Online shop with thousands of variants
ROLEDesign and deliveryCONTEXTShop and ERP connection in an SME settingSECTORSME · manufacturingCONCEPTtwo purchase paths, one platformSTATUSbefore go-live
CLIENT
Spyk Bänder AG
Summary
details in the case study

View case study: Spyk Bänder→

E-commerce · large enterpriseHeld AG
PROJECT SHEET · REF-04om3 PROJECT REGISTER
E-commerce for a large enterprise
ROLEE-commerce project managementCONTEXTPlatform build and rolloutSECTORLarge enterpriseMETHODhybrid · Scrum in deliverySTATUSin operation
CLIENT
Held AG
Summary
details in the case study

View case study: Held AG→

Key figures
Substance, not promises
25
years of project experience
since 2001 · SAP · ERP · integration · e-commerce
30
people
led in project teams — led, not staffed by us
5
certifications
PMP® · HERMES · CPRE (IREB®) · PSM I · ITIL®
2
project languages
German · English
Thomas Weber in conversation at a flip chart.
Contact

Where does your project stand right now?

From the first conversation you speak with the person who will also be answerable for your project. No sales team in between, no handover once the contract is signed.

You describe your situation — I tell you how I assess your project and which next steps make sense.

If you would rather start with a number than a conversation: the SEO check examines your site for technical health, content and visibility, and returns a list of actions.

30 minutes · confidential · video or phone