Services
Software development & architecture
Software whose structure still makes sense after five years — because the decisions are documented and the structure carries them.
When we are the right fit — and when we are not
Not every project is a fit.
A fit when …
- The system is meant to run and evolve for years, not until handover.
- There is an existing estate that should be modernised rather than discarded.
- Architectural decisions have to remain traceable later — for an audit, a successor or an approval.
- You need someone who brings embedded, backend and interface together in one design.
Not a fit when …
- You are looking for pure staff augmentation without technical responsibility — then we are the wrong supplier.
- This is a standard software rollout without custom development.
- Below 10 person-days our ramp-up effort does not pay off for you.
- You need a pure design or marketing website.
What we actually do
- Architecture design and technology evaluation — microservices, event-driven design, API-first, or deliberately a monolith when that is the right answer. The decision is argued and documented, not asserted.
- Implementation across the whole stack — embedded systems, desktop software (Qt/QML), backend services (C#/.NET, Java, Go, Python), web interfaces (TypeScript/Angular) and mobile applications.
- Interfaces and system integration — REST/OpenAPI, gRPC, GraphQL, WebSocket and SignalR, plus connectivity to existing ERP, MES and specialist systems.
- Modernisation — analysis and stepwise refactoring of mature systems, migration of legacy stacks, performance optimisation.
- Architecture governance — reviews, guardrails for the development team, documentation to arc42.
Clean Code, SOLID, Clean Architecture
These three terms appear on many websites. Here is what they mean day to day for us:
Clean Code means intention-revealing names, one responsibility per module, no duplication and a binding style guide — enforced through code reviews and static analysis, not through appeals.
SOLID is not an end in itself but the reason why an extension later becomes a new class rather than another branch inside an existing one.
Clean Architecture separates business logic, infrastructure and presentation so that the logic stays testable in isolation. That is the precondition for our test architecture to work at all.
Approach & collaboration models
- Project development — a scoped engagement with a defined outcome, from requirements analysis to commissioning.
- Team reinforcement — an architect or developer inside your existing team, under the same quality gates we use.
- Architecture review — a targeted analysis with concrete recommendations, typically as an entry point.
- Maintenance & further development — long-term support, including for systems we did not build.
We work agile (Scrum or Kanban), remote, hybrid or on site, throughout Germany. Project languages German and English.
Technologies
Project reports from this field
Industrial data platform
Scalable platform for industrial data exchange with end-to-end secured communication. Industrial automation · metalsCondition monitoring migration
Migration of a mature C++ backend to .NET Core with Entity Framework, including a redesign of the data access layer. Industrial automationMedical laser system
Development, testing and documentation of the planning and treatment interfaces of a laser system in an approval-relevant setting. Medical technology · regulatedVehicle bus analysis
Central platform for analysing vehicle bus data — with project leadership, architecture modernisation, agile transition and training. AutomotiveTax software
Further development and quality assurance over several years: legislative updates, form logic, accessibility and GDPR. Public administration · financeTypical project size
What a project costs with us.
Day rate €480–960 depending on the type of engagement
Below 10 person-days our ramp-up effort does not pay off for you. Architecture reviews are the exception — they are deliberately short.
Frequently asked questions
What does “framework-independent” mean in practice?
The business logic knows neither the web framework nor the database. It sits in its own layer that can be tested without running infrastructure. A framework change then hits the outer layers, not the core.
Do you really document to arc42?
Yes, and cut to the project: not all twelve chapters, but the ones that carry decisions — context, building block view, runtime view for the critical flows, cross-cutting concepts and the architectural decisions with their rationale.
Do you take over existing systems?
Regularly. We migrated a mature C++ backend to .NET Core and redesigned the data access layer in the process, without pausing the product. The entry point is usually an architecture review with concrete recommendations.
Contact
Your contact
Software architecture & technical project management