TYPO3 freelancers who move your website forward

The effort depends almost entirely on the extensions in use, not on the number of pages. A website with 800 pages and nothing but maintained extensions is updated faster than one with 40 pages and three home-grown extensions from the TYPO3 6 era.

As a rough guide: an upgrade across one LTS step with a manageable set of extensions usually takes between two and five working days. Where several version jumps, custom extensions and a PHP update come together, it can turn into ten to fifteen days. That is why we always run an audit first and give you a dependable range before you have to decide anything.

From sign-off on the concept to go-live, we reckon on six to ten weeks for a typical corporate website. In our experience the biggest time factor is not us but the content: writing copy, clearing images, internal sign-offs.

We therefore plan a content schedule from the outset and make the editing environment available early, so your team can fill it while development is still running rather than afterwards.

Yes, frequently. We take on individual TYPO3 topics inside existing teams as freelancers — from extension development through the upgrade to code review — working in your processes, your repository and your ticket system.

For agencies this is often the most pragmatic solution: specialist TYPO3 knowledge exactly when it is needed, without having to create a permanent position for it.

We build to WCAG 2.2 at level AA. In practice that means visible focus indicators on every operable element, contrast well above the minimum values, full keyboard operation including menus and dialogues, a clean heading structure, and forms with real labels and error messages that do not rely on colour alone.

On request we also accompany an external audit. For public bodies and larger companies that is the rule anyway these days.

A fair question to ask a freelancer. Our answer is organisational rather than rhetorical: all the code lives in your repository, the deployment is scripted and documented, and there are no credentials known to only one person.

Any TYPO3 developer can therefore take the project over. On top of that we work within a network of several experienced TYPO3 freelancers and can bring someone in at short notice if needed.

We are based in Winterthur and work throughout Switzerland, in Germany and in Austria. Day-to-day work is remote — video call, shared test environment, short written minutes. When a workshop on site gets there faster, we travel.

Then we say so — and we do not leave you standing there. We are a small outfit, and some undertakings simply need more heads than we can provide: a portal with several editorial departments, a tender with hard availability guarantees, a project with app development running alongside.

In those cases we actively look for the right partner agency for you. We have worked with several TYPO3 agencies across the German-speaking market for years and know fairly precisely who is good at what and who currently has capacity. You get one or two reasoned recommendations, and we make the introduction if you want us to.

If it helps, we stay in the project as TYPO3 specialists — either on your side as technical support or within the agency team. A good introduction is worth more to us than a contract we could only just manage.

Yes, that is the rule rather than the exception. It starts with an inventory: TYPO3 version, extensions, PHP, hosting, deployment, backups, open security advisories, and a look into the code of any custom extensions.

You receive the result in writing, with an assessment of what is urgent and what can wait — even if you decide against working with us afterwards. We write nothing disparaging about your previous developer in that report; more often than not their decisions had good reasons at the time.

Both, depending on how well the scope can be determined in advance. Clearly delimited packages — an upgrade after a completed audit, a code review, a training session — we offer at a fixed price.

Development projects are billed by time and materials, with a binding cap per stage. After each stage you can see what has been used and what is still open. What we do not do is name a fixed price before we have looked inside the installation. Numbers like that are never right, and someone always pays the difference in the end.

Yes. A common arrangement is a fixed allowance per month — two days, say — that your team can use as it sees fit: for further development, for reviews, or simply as cover when something jams.

Individual, self-contained jobs work just as well: building an extension, implementing a form, connecting an interface, running a performance analysis.

The current LTS. It has the longest support horizon, and every intermediate version picked up along the way only makes the journey longer.

There is one exception: if a business-critical extension does not yet support the current LTS and no alternative exists, a stop at the previous LTS can make sense. We check that in the audit and tell you before we start.

You write, you call or you open a ticket — every route reaches someone who built the project. There is no first-level desk that passes the question on.

Our ticket system is not a filter but a memory: every request can be traced, nothing disappears into an email thread, and you can see at any time what is being worked on. That makes handling faster, not more impersonal.

With a maintenance contract there are agreed response times: critical faults within four working hours, everything else on the next working day. Without a contract we still help, but then according to availability.

You do. The sitepackage, any custom extensions, the deployment scripts and the documentation live in your repository, and you get all the credentials. There is no licence fee on our work and no part that stays with us.

The reason is self-interested: we want you to come back because the collaboration works — not because leaving would be too expensive.