For agencies and in-house teams
Magento depth that ships under your name
Most of my work does not appear under my name. It appears under the name of the agency that brought me in. That is not a sideline, it is the normal case.
When agencies call
A project has stalled
An upgrade is half finished, a module breaks the checkout, and nobody on the team has three days free to read in. Reading in is the job.
The depth is missing
Your people know Magento. The question sits lower down: indexers, caching, custom modules, the data model. For that you bring in somebody who is in it every day.
Somebody has left
The developer who knew the project is no longer reachable. I work in through the code, the repository and the deployment history, and make the next steps plannable again.
Capacity at short notice
There is a date and the team is full. I take a bounded piece rather than the whole project, and I work in your setup.
How the arrangement works
-
Settle who owns what
Before I touch code: what is mine, what stays yours, who decides architecture. Without that you get exactly the friction nobody has time for later.
-
Read in
Code, repository, deployment history, ticket history. I ask a lot at the start so that I ask very little later.
-
Work in your setup
Your git, your conventions, your review. I do not bring a toolchain of my own that your team then has to maintain.
-
Hand it over
What I build should be something your team can carry on. Architecture decisions get explained, not just committed.
White-label means white-label
I do not appear in front of your clients unless you want me to. No logo, no mention, no reference. This page names agencies only where I am allowed to.
The other way round works too: if you want me talking to your client directly, I will. Both work, as long as it is clear beforehand which one applies.
From partnerships
-
Diglin, Zürich
My first Hyvä migration ran through this partnership, for Brentford Computers. The project in detail.
Alongside it, Openstream in Switzerland, Head New Media, Studio Mitte in Austria and WilMa Digital in Germany. Very little of that work is public, and that is exactly the point.
Availability
I will not make a blanket claim about availability. Whether there is time next week depends on what is running. Ask, and you get an honest answer, including no.
I work from Austria on central European time, which is worth knowing if your team is in London or on the US east coast: there is a working overlap either way.
Frequently Asked Questions
Do you work under our name?
Yes, that is the normal case. Your clients see your agency, not me.
Can you work inside our review process?
Yes. At Vitafy I worked inside the internal team for years and reviewed other developers’ tasks and code there. Working inside your process suits me better than working alongside it.
Would you take technical responsibility for a whole project?
It happens. At Kaufhaus der Berge I have been technically responsible for the platform since 2016. For agency projects the bounded role is the more common and usually the better one.
What if we only need you for one task?
Then it is one task. A bounded problem is a good start, and the most honest test for both sides of whether the arrangement works.
One Person, From the Question to the Code
I work out what is needed, write the requirement, organise whoever else works on it, and then build it myself. Usually that is three companies, and something is lost at every handover between them. Here there is nobody between your question and the running system.
Related services
What is your project stuck on?
Describe briefly what has stalled and what setup you work in. I will tell you whether I am the right person, and if I am not, I will say that too.