// How we work
From first call to live system — in six steps
No black box, no "trust us, it's going well". You see working software on staging every week, you approve every scope change in writing, and you keep the code from day one.
// The process
What actually happens, week by week
Discovery
We sit down with the people who actually use the system — not only management. We map the current process, the systems involved (shop, ERP, warehouse, accounting), where data really lives and what breaks today. You leave this phase with a written scope and a realistic budget range, not a sales pitch.
Concept & architecture
Before production code is written we design the data model, the integration points and the screens. You approve wireframes and the API contract. This is the cheapest moment to change your mind — and the phase where a fixed estimate becomes possible.
Build sprints
We develop in short iterations. Every week something real lands on your staging environment and you can click it. Weekly call, written changelog, no surprises three months in. Priorities can be reordered between sprints — that is the point of working this way.
Quality assurance
Functional tests against the agreed scope, performance checks with realistic data volumes, a security pass (permissions, 2FA, input validation) and a user acceptance round with your team. Bugs found here are cheap; bugs found by your customers are not.
Launch
Go-live is a scripted, rehearsed deployment — not a Friday-evening adventure. Data migration is dry-run first, DNS and caches are planned, and there is a rollback path. We watch orders, logs and error rates closely for the first two weeks.
Support & evolution
Software is never finished. On a maintenance plan we keep Shopware, plugins and dependencies patched, watch performance, and pick up the next round of improvements. You always keep the code, the credentials and the freedom to leave.
// Engagement models
Three ways to work with us
Pick the one that matches how well defined the work is. We will say so if you picked the wrong one.
| Model | Best for | Billing | Typical duration |
|---|---|---|---|
| Fixed-scope project | Migration, plugin, integration, new shop | Fixed price, milestone-based | 2 weeks – 5 months |
| Monthly retainer | Continuous development & a growing roadmap | Fixed hours per month, transparent report | Ongoing, 3-month terms |
| Maintenance & SLA | Live shops that must simply keep running | Monthly flat rate + agreed response time | Ongoing |
// What you always get
Deliverables, not just working hours
Written scope
What is included, what is explicitly not, and what it costs if you want it later.
Staging access
Your own environment to click through, from the first sprint until go-live and beyond.
Documentation
Setup, architecture and integration docs in the repo — readable by a developer who is not us.
Handover
Credentials, repository, deployment scripts and a walkthrough session. No hostages.
// FAQ
Questions about working together
A focused plugin or integration is usually 2–4 weeks. A full B2B Shopware 6 store with ERP connection is typically 3–5 months from kickoff to go-live. We give you a range after the discovery call and a fixed estimate after the concept phase.
Both. Clearly scoped work — a migration, a plugin, an integration — is quoted as a fixed price. Ongoing development and support run on a monthly retainer with a transparent hour report. We will tell you which model fits your project.
Plan for one weekly call of 30–45 minutes plus quick answers on business rules. The clearer your answers to pricing, stock and process questions, the fewer assumptions we have to make — and assumptions are what makes projects expensive.
We stay. Directly after launch we watch logs, orders and performance closely for two weeks. After that you can move to a maintenance plan covering security updates, Shopware updates, monitoring and a guaranteed response time.
Yes, and we do it often. We start with a paid review: code, database, plugins, hosting and open issues. You get a written report with risks and a prioritised plan — even if you then decide to continue with someone else.
Let's start with a discovery call
30 minutes, no obligation. Tell us what should change — you get an honest assessment and a budget range.