The people behind your software

The people on this page. There is nobody behind them: no junior bench, no offshore layer, no account manager translating between you and the developer. Tejas leads the company and still writes code every week. In practice you deal with whoever owns your project, and when a question is specific you get an answer from the person who wrote that exact piece of it.

Five, and all five are named above with their real jobs. We put it that plainly because it is the first thing a buyer should weigh, not something to discover in month three. It means low overhead and nothing getting relayed between you and the code. It also means there is no bench: if all five are busy, your start date moves. We would rather tell you that than double-book you.

Honestly, a specialist being away can push non-urgent work by a few days — a five-person team cannot pretend otherwise. What we do about it is structural rather than promotional: architecture is designed and reviewed before anyone opens an editor, and the code is written to be readable by whoever inherits it. At least one other developer knows your system well enough to step in. A broken shop gets picked up by whoever is there. A new feature may wait.

No. Every line is written by the five people above — that is what in-house means here, and it is meant literally. We would rather turn a project down than hand it to a stranger and add a margin on top. The trade-off is real: if your project needs something outside Shopware, Node.js, React and the systems around them, we will say so and point you elsewhere rather than learn it on your budget.