Faster selection
Three topic groups lead to the scenario closest to your task.
Case study overview
Twelve solution paths and one real client project.
Twelve transferable project scenarios across websites, commerce, AI and operations – plus the one real case study. Clearly separated so you can find the right example.
Premotion · ViennaStrategy, content, design and technology from one accountable teamSince 2003
A scenario is not a client reference.
Twelve of the thirteen pages in this section describe transferable solution paths: typical starting points, the decisions taken and their consequences. Client names and metrics are absent because a scenario does not represent a single engagement – any name here would be invented. Named references appear where we have approval to publish. The one real case study stands next to them, clearly labelled.
The result
What concretely improves.
No invented numbers
Where there is no solid basis for measurement, there is no percentage figure either.
Connected to services
Every scenario links to the service pages and guides that cover the path described.
Capability areasA clear framework.
A clear framework.
Concrete decisions.
Every building block has a defined job and feeds into the shared goal.
Websites and content
Four scenarios covering a B2B redesign, search visibility during a migration, a network of several websites under shared standards and a social content system. The entry point when structure and findability are the topic.
Commerce and customer access
Four scenarios covering product data from multiple sources, conversion levers in the shop, digital B2B ordering and access for existing customers.
Systems and operations
Four scenarios covering knowledge access with source citations, automated approvals, performance root causes and taking over business-critical operations.
The real case study
The Shopify connector links Intex ERP, Shopify and Fiege Logistics for over 7,000 products. As the only client project actually delivered, it deliberately stands apart from the twelve scenarios.
Working together
From first sketch to a solid system.
Transparent decisions and visible interim results keep the implementation under control.
Narrow down
Choose the topic group that matches your task instead of searching for an assumed technology.
Skim
A scenario's starting picture and decisions show within two paragraphs whether it fits your situation.
Distinguish
The twelve scenarios are constructed and transferable; the Shopify connector case study is a client project that was actually delivered.
Continue
From every example, related pages lead to the corresponding service and the matching guide.
Working basis
Results that keep being used.
Decisions, access and documentation stay transparent and available inside your company.
Typical results
- Twelve transferable project scenarios
- One real case study
- Typical starting points per task
- Reasoned architecture and content decisions
- Clear labelling instead of invented metrics
- Connections to services and guides
All case studies
All examples at a glance.
Transferable scenarios and the real case study – each with starting point, decisions and consequences.
Case Study
Case Study – Shopify Connector
Shopify Connector: Enterprise ERP-to-Shopify Middleware
↗Case studiesB2B website redesign
A typical project scenario for companies whose website shows many services but does not sufficiently support positioning and qualified enquiries.
↗Case studiesProduct Data & Commerce
A typical integration scenario for product ranges with variants, multiple data sources and high demands on data freshness.
↗Case studiesWordPress Performance
A typical approach for websites with themes that grew over time, too many plugins, unclear caching and recurring performance problems.
↗Case studiesAI knowledge assistant
A typical scenario for teams that want to find policies, manuals and project documentation faster and use them safely.
↗Case studiesWorkflow automation
A typical project scenario with forms, data validation, notifications, approvals and exception paths that are easy to follow.
↗Case studiesE-commerce CRO
A typical optimisation scenario for shops with enough traffic but uncertainty about the biggest levers across category, product and cart.
↗Case studiesDigital customer portal
A typical scenario for companies that want to reduce recurring requests and give customers secure self-service access.
↗Case studiesSEO migration
A typical migration scenario with a URL inventory, content evaluation, redirects, internal linking and launch monitoring.
↗Case studiesWordPress Multisite
A typical scenario for brands, countries or organisational units that need to combine central components with local content.
↗Case studiesB2B Commerce
A typical B2B scenario with company accounts, price lists, order approvals and integration with ERP and sales.
↗Case studiesSocial Content System
A typical scenario for brands that regularly need video and social content but have so far managed topics, approvals and production ad hoc.
↗Case studiesManaged Hosting
A typical operations scenario with hosting migration, monitoring, backups, an update process and clear escalation paths.
↗FAQ
Frequently asked questions.
Why are twelve of these pages not real client projects?
Because a credible reference needs approval, and we publish nothing we cannot substantiate. The twelve scenarios therefore describe solution paths rather than engagements: starting points, decisions and consequences come from real project work, while names and metrics are deliberately absent. Work actually delivered can be found in the case study and on the clients page.
Where do the scenarios come from if they are not references?
From actual project work, but condensed: recurring starting points, bottlenecks and decisions from several initiatives are distilled into one readable path. The questions described are therefore not fictional but typified. At no point is a result invented.
Which example fits my situation?
First assign your task to one of the three groups: websites and content, commerce and customer access, or systems and operations. Within the group, the deciding factor is the starting picture described, not the technology used. If two scenarios fit equally well, your initiative probably spans both – which is more the norm than the exception.
Ready?
Your next step should show impact.
In 30 minutes we clarify goal, starting point and the strongest lever – concrete, honest and with no obligation.
Discuss your project