We’re an engineering consultancy. We build AI systems and web platforms for startups and scale-ups in the DACH region and the EU, and we keep them running.

Somewhere in your company there’s a person who reads every incoming order, claim or request, works out what it means, and types the result into another system. A language model can do that job now. We build the software around it that reads the email, makes the call and writes the record, and we make it reliable enough that you stop checking on it. We’ve done this for a company in the German dental industry: order emails in, records their ERP accepts out.

Your product is more than the app. There’s the content someone has to edit without calling a developer, the payments, and the servers it all runs on. Those four usually got built at different times by different people, and most of what we get called about is where they don’t fit together. We fix that on what you already run, and when the stack is ours to choose we build on Next.js, PayloadCMS and PostgreSQL.

Sometimes your team is building fine and just needs more senior people on it. Sometimes nobody is deciding what to build, because the CTO left and the replacement is months away. We do both. Our engineers join your team and work in your repository, to your plan. Or one of us takes the technical lead’s seat for a while, owns the plan, and hands it back when your permanent hire arrives.

Every product has a login, and behind it a set of rules about who’s allowed to see what. Most companies get the login from Keycloak or Auth0 and write the rules themselves. Both outgrow you: you switch providers, a big customer wants to sign in with their own accounts, and the handful of roles you started with stops describing who does what. We’ve moved 3M+ users from Keycloak to Auth0, and we handle the smaller versions of the same problem.