Worked Example: The Math Behind Inquiry Automation for Shopware Retailers
A transparent model calculation for automating inquiry handling at a DACH Shopware retailer – with disclosed assumptions, the arithmetic, and the break-even point.
Summary
---
1. Assumptions Behind the Calculation
All assumptions are disclosed and can be replaced with your own numbers.
Assumption | Value | Basis |
|---|---|---|
Incoming inquiries per week | 120 | typical order of magnitude for a Shopware retailer with 3–8 support staff (assumption) |
Handling time per inquiry | 9 minutes | assumption for inquiries requiring both Shopware and ERP lookups |
Fully loaded support hour | 45 EUR | assumption: gross salary + employer costs + workstation |
Share of unstructured inquiries | 70 % | assumption: free-text email with mixed requests |
Share of automatable reply drafts | 60 % | assumption: recurring request types with clear rules |
Residual time per prepared inquiry | 2 minutes | assumption: human review and approval |
One-off implementation | 14,000 EUR | assumption: process analysis, interfaces, pilot operation |
Monthly operation | 320 EUR | assumption: hosting and monitoring on EU infrastructure |
---
2. The Arithmetic
Current state per week
120 inquiries × 9 minutes = 1,080 minutes ≈ 18 hours per week 18 hours × 45 EUR = 810 EUR per week ≈ 3,510 EUR per month
After automation (with 60 % draftable inquiries)
- 72 inquiries prepared: 72 × 2 minutes = 144 minutes
- 48 inquiries handled manually: 48 × 9 minutes = 432 minutes
- Total: 576 minutes ≈ 9.6 hours per week ≈ 432 EUR per week ≈ 1,872 EUR per month
Monthly saving: 3,510 − 1,872 − 320 (operation) = 1,318 EUR per month
Break-even on the one-off implementation: 14,000 EUR ÷ 1,318 EUR ≈ 10.6 months
---
3. What the Model Makes Visible
- Sensitivity sits in inquiry volume. Halve the number of inquiries and the saving halves – operating cost does not. Low volumes do not pay off.
- The strongest lever is not speed but system switching. Almost all of the 9 minutes come from moving between email, Shopware, and ERP – not from writing the reply.
- The volume threshold: from roughly 60 inquiries per week the break-even lands under 24 months as soon as an ERP system is involved. Below that, plain workflow automation without AI is usually the cheaper answer.
- Not included: error costs, customer retention, and scaling without adding staff. They move the result upward but are not quantified here.
---
4. When Automation Does Not Make Sense
The honest limitation belongs in the model:
- fewer than roughly 40 inquiries per week
- mostly one-off cases without recurring patterns
- no machine-readable systems behind Shopware (no API access to ERP or inventory)
- no defined escalation path for exceptions – without an approval point, operations are risky
In these cases the effort exceeds the benefit. That statement is part of the consulting, not its marketing.
---
5. Verifiability
- The arithmetic is fully disclosed and reproducible with your own numbers.
- No results of a customer project are claimed.
- Background on Nils Abegg's experience: 15 years in software development, about ten of them in e-commerce, agentic AI since 2023 – stated on the homepage under "Agentic AI seit 2023 / 15 Jahre Softwareentwicklung".
---
6. Next Steps
- Request a potential analysis → – 45 minutes, a technical assessment using your own numbers instead of model values
- AI automation overview → – the automation fields at a glance
- E-commerce automation → – integration with Shopware, ERP, and PIM
Related comparison: AI Agent vs. Workflow Automation vs. ChatGPT.
Frequently asked questions
Is this a customer project?
No. It is a model calculation with every assumption disclosed. Real results depend on inquiry volume, system landscape and data quality – none of those outcomes are claimed here.
From what inquiry volume does automation pay off?
In the model, break-even falls below 24 months from roughly 60 inquiries per week once an ERP system is involved. Below about 40 inquiries per week the effort outweighs the benefit, and plain workflow automation without AI is often the cheaper route.
Which assumption drives the result most?
Inquiry volume. Halve it and the saving halves while operating costs stay flat. The largest time sink in the model is switching between email, Shopware and ERP – not writing the reply.
What is not included in the calculation?
Error costs, customer retention and scaling without adding headcount. They push the outcome upward but are not quantified in the model.
---
*Last updated: September 2026 | EinfachAI – AI automation for the DACH mid-market*
Written by
Nils
Nils Abegg is a developer with more than 15 years of experience, including around ten years in e-commerce. Since 2023, he has focused on agentic AI and enjoys building practical AI solutions for small and medium-sized businesses.