Hi, I'm Julien.
I have been shipping software since 2010, and for most of that time the job was to be the person who gets woken up when production breaks. ITzWorking is what I built when the models got good enough that I could keep that job and drop everything around it.
I built the team. Then I stopped.
I started in fintech in Luxembourg, where nobody finds a production incident charming. Then I co-founded kodehyve and became its CTO: sole developer on day one, answering for a team of twenty by the end. I learned to hire, to review, to say no, and to carry a product I had not written line by line.
Building that team is also what taught me to leave it. A team is not how you get quality, it is how you get capacity, and capacity charges rent: coordination, onboarding, handovers, and the slow drift of everyone knowing the product a little less well than the person who wrote it.
Then the models got good enough that capacity stopped being the scarce thing. What stayed scarce was judgment, and the willingness to put a name on it. So I stopped hiring and built a delivery system instead. ITzWorking is what came out.
Everything that is not judgment already runs on a system.
I can answer for several products at once for one reason, and it is not that I work more hours. The business around the work is not mine to run by hand. It runs on Nexus, the internal OS I built for this agency and ship to myself before I ship anything to anyone else.
- Leads and salesEvery lead, conversation, proposal and contract in one place, with the movement between them automated rather than remembered.
- DeliveryProjects, sprints, specs and tasks, with agents taking the first pass on analysis, decomposition and implementation. I review, I decide, and I answer for the result.
- Client commsThe Friday digest, the monthly statement, the page showing what is live and what is waiting on you. Written by the system, on a rhythm, not when I happen to remember.
- ProductionErrors from every product I run land in the same place the second they fire, and on the priority tier an agent is diagnosing before I am even awake.
- Even the videosWhat gets captured, what gets published, what performed. The content side runs on the same OS as the code.
None of that is a chatbot parked on top of a CRM. It is this agency, encoded, and about 90% of it runs there today. What is left on my desk is the part that does not delegate: deciding what to build, deciding what to refuse, and answering when something breaks.
What I answer for, and what I do not.
I answer for the products I run. Not for advice I gave once, not for a report I handed over: for the thing still working on Monday morning. That is the whole reason the client list is short, and the reason every seat starts with me reading your code down to the last line.
What I do not do: I do not take on a product I have not read. I do not take one on and hand it to someone else. And I do not sell capacity. If what you actually need is a team of developers and a project manager, I am the wrong door, and the audit will tell you so before you have committed to anything.
Everything is in your name from day one: your code, your infrastructure, your accounts. If you ever want to take it in-house, La Passation is a documented, priced handover with an architecture walkthrough and thirty days of questions. You leave with everything, because everything was already yours.