DACH on site, worldwide remote: one team in Germany, two working languages.

No. We are one team in Germany working remotely. There are no branches, no local entities and no local phone numbers in these markets. What you get is the same people who do the work, reachable in an agreed window, plus a written handover on every working day. If your procurement requires a contracting party inside your country, we will say so in the first call.

About three to four. Our afternoon from 15:00 Central European Time is your morning from 09:00 Eastern. That is enough for a daily sync, design reviews and approvals. Everything before that we deliver asynchronously: you find yesterday's progress waiting in your morning, we find your comments waiting in ours. On the West Coast the window shrinks to one or two hours, so there we work deliberately in writing.

As a relay. The overlap is one to two hours in our early morning, and tighter still for New Zealand. So the daily written handover replaces the call: we hand over in the evening, you read and decide during your morning, we build on your answer the next day. One fixed weekly meeting stays for whatever genuinely needs to be spoken. And when an important call only works in your daytime, we take the meeting at night – a single late call is no problem, a permanent night shift would be. One clear step of progress per day beats ten scattered questions.

In writing and on video, not in a single meeting. You receive the repository with its full history, a README covering build, deployment and content or data model, plus recorded walkthroughs for editors and developers that your team watches in its own time. A live session for questions then sits inside the shared window. For ongoing website editing we can set up changes by chat – so a copy fix at three in the morning our time needs neither a CMS session nor us.

We invoice in euros. For business customers elsewhere in the EU with a valid VAT ID, the reverse-charge procedure normally applies, so the VAT liability shifts to you. Customers outside the EU are invoiced without German VAT. We do not invoice in foreign currency, which means the exchange rate and any bank charges sit with you. This is a general description and not tax advice – please confirm how your specific case should be treated with your own tax adviser.

That depends on your country. Some states require the client to withhold a share on services bought from abroad and remit it locally. Germany has double taxation treaties with many countries that reduce the rate or set it to zero; claiming that usually needs a certificate of tax residence, which we will apply for on request. Tell us before signing if a withholding is foreseen, so we settle it up front rather than at the first invoice. Assessing your case is a matter for your tax adviser.

The default is a works contract under German law with the place of jurisdiction at our registered seat in Germany. The contract language is German or English, bilingual on request with one version named as binding. Scope, acceptance criteria, payment plan and the grant of rights all sit in the same document so that nothing drifts apart later. A different governing law or a place of jurisdiction in your country is negotiable, but we do not assess foreign law ourselves – we have it reviewed. We do not provide legal advice.

No. We are based in Germany, with no subsidiary, branch or tax registration in your market, and we will not incorporate one for a single project. Two routes remain: your procurement grants an exception for software works contracts, which is possible more often than the policy first suggests. Or you engage us as a subcontractor to a prime contractor in your country. If neither can be arranged, a local agency is the right answer, and we will say that in the first call rather than in the proposal.

The repository sits in your name from the first week. On full payment you receive exclusive rights of use, unlimited in time, territory and purpose, to everything we create for you. One peculiarity is worth naming: German copyright law does not allow authorship itself to be transferred, only rights of use to be granted. So we do not sign an Anglo-American "assignment of copyright" word for word; we write in the economically equivalent grant instead. The frameworks underneath are open source – Astro and React Native under the MIT license, Flutter under BSD – and third-party components keep their own licenses, which we list.

Within the DACH region, yes: kick-off workshops, structure and content sessions, requirement workshops for an internal system or launch support are planned as travel days and quoted transparently. In Germany, Austria and Switzerland that is routine – the same way it runs in our projects as a Webflow agency. Outside Europe travel is possible in principle but becomes its own line item, and honestly it is rarely necessary: a well-prepared remote workshop reaches the same result. Working remote by default also keeps us travel-light and therefore CO₂-saving, which is a stance we hold rather than a cost cut.

Two layers that often get conflated. The delivered product: a static website build runs on any CDN and we pick the region to suit your users and your obligations – Germany, the EU or elsewhere; for an app or a web application the same logic applies to the backend. The development environment: repository hosting, continuous integration and communication tools run with providers we name to you, so your compliance team can assess them. If you have visitors from Europe we build accordingly – self-hosted fonts, cookie-free analytics, a deliberately chosen form endpoint; more on that under GDPR-compliant websites. The legal assessment stays with you.

We are – for what we built and what does not work as agreed. That we fix under statutory warranty without a new invoice. A change request is a different thing: a new page type, a new screen or a new feature is an order, not a defect – and which category a report falls into is something we state up front, not afterwards. Fixed response and restore times we agree in writing if your procurement needs them; they belong in the maintenance agreement, not in an email.

The honest answer: our response times sit inside Central European business hours. With a prerendered website the risk is smaller than with a classic CMS, because pages are served as static HTML from a CDN – there is no database and no plugin stack to fall over at 3 a.m. Where an app or an automation depends on a backend or a third-party API, we name that dependency in the plan rather than discovering it during an incident. For critical phases such as a launch or a campaign we agree a temporarily extended window. The details live on our page about support and maintenance.

Three concrete things. First, we need no access to your corporate network: the build runs against your repository and your hosting accounts, not behind your firewall. Second, access is personal, with two-factor authentication required and minimal permissions rather than shared passwords – after the project you revoke it in your own accounts. Third, the attack surface of a prerendered site is small: no admin login, no database and no plugin ecosystem in the delivery path. What does deserve review is repository and build permissions, package dependencies, form endpoints, API credentials for an automation, and a headless CMS as a system of its own.

Yes, and we would rather say so than hide it. AI-assisted tools speed up routine work; a human stays accountable. Every change passes review, type checking and a build in continuous integration before it lands anywhere. Credentials, personal customer data and confidential documents do not go into such tools – that is a rule here, not a judgement call. If your corporate policy restricts or forbids their use, we follow it and write it into the contract.

You keep everything that constitutes the project: the repository with its full history, hosting, store and CMS accounts in your name, the domain in any case. There is no license and no editor tied to us. An agency in your own city can take over as soon as somebody there works with HTML, CSS, TypeScript and Git – that is precisely what Astro components are, and interactive parts can be written in React, Preact, Svelte, Vue, SolidJS or Alpine.js. An app in Flutter, React Native or SwiftUI is ordinary open tooling in the same way. A switch stays unpleasant, but it is not a rebuild.

What exists, and nothing else. We do not have a public client reference for every stack we work in – for Astro, for instance, there is none we can show publicly yet, and we would rather say that than invent one. What we do have: a Webflow reference we built and still maintain, our own products that we developed and shipped ourselves, including the WhatsApp AI agent that runs in production here, and years of software development with a repository, continuous integration and live operations. Testing us is cheap: the first assessment costs nothing, the repository is yours from day one, and on request we cut the first stage small – one page type or one screen, one deployment, one handover. After that you decide on evidence rather than on trust.

When your project lives on daily presence in the building – a rebrand, say, or a rollout where several departments need to sit around one table. When your procurement requires a contracting party in your own country. When regulation requires operations or data processing to stay in-country in ways hosting location alone cannot solve. When you need support in a language we do not speak: we work in German and English. And when somebody has to turn up at the photo shoot, in the store or on the trade-show stand. Inside DACH we do that; on another continent we do not.

Central European Time: UTC+1 in winter and UTC+2 in summer. Our working day runs roughly from 9 to 18. Fixed call windows are placed at kick-off inside the overlap with your working day, and we re-check them after every daylight saving changeover.

Websites with Astro or Webflow, depending on who has to edit them afterwards. Apps with Flutter, React Native or SwiftUI. Custom web applications, AI automation and chat agents, IT and ERP project management, and the modernisation of grown legacy tooling such as Excel and VBA. We are not an official partner of any of these vendors – we simply build with them, and we pick the one that fits your case rather than the one we happen to sell.

Yes, and across borders it is often the more useful half of the job. Where several vendors, an internal IT department and a business unit have to be kept in step, someone has to hold the plan, chase the decisions and write the minutes that everybody reads in their own morning. That is what IT project management covers, and it works remotely by nature – the artefacts are documents, tickets and decisions, not corridor conversations.

Yes, within the two languages we write ourselves and with translations you supply for the rest. The technical side is the part we own: one URL per language, correct hreflang annotations in both directions, a sitemap that declares the alternates, and no automatic redirects that trap a user in the wrong version. The editorial side stays yours, because a market page reads badly when it is translated rather than written. Where something is stuck, an SEO audit finds it.