Technical leadership and mentoring for small development teams
You have developers, but nobody senior enough to review their work, set the standards, and get them through the hard parts. I do that: code review, pairing, decisions, and getting a team through an upgrade or a rescue while they learn how.
A big part of this today is showing a team how to work with AI tools properly. I'm all in on AI myself, and I know how to get the speed without turning the codebase into a mess: review, tests, and someone who checks what ships.
I usually reply within one working day.
What I do with your team
Hands-on, on your actual codebase, not a workshop.
Code review that teaches
I review the pull requests that matter and explain why, not just what. Over time the team writes code that needs less review, which is the point.
Pairing on the hard parts
The tricky migration, the integration nobody wants to touch, the performance problem. We do it together, so next time they can do it alone.
Working AI-first without the mess
Which tools, how to use them for everyday development work, how to review what they produce, where they should not be trusted. Done right, a small team ships several times faster. Done wrong, you get a codebase nobody understands.
Standards the team can actually follow
How code is structured, how it is tested, how it gets deployed. Written down short enough that people read it, and enforced in review rather than in a document nobody opens.
Getting through an upgrade or a rescue together
A big Laravel upgrade or a messy takeover is a good moment to learn. I lead it, the team does most of the work, and they come out the other side knowing the codebase.
Turning customer talk into technical work
Sitting in on customer conversations and turning them into clear requirements the team can build, with the edge cases written down before the code is.
How I work
You don't need to have everything figured out before we talk. An idea, access to the repo, a screen recording or a list of problems is enough. I look at what is there, tell you what I would do and what it costs, and then I build it.
I use Claude Code, Codex and my own agent workflows for reading code, planning changes, writing tests, refactoring and debugging. It is not vibe coding. It is senior engineering with a much faster loop.
AI-first, taught by someone who works that way every day
I use Claude Code, Codex and my own agent workflows for my own work, so what I teach a team is what I do myself: fast, with tests, with review, and with a person who stays in control of what ships.
I stay in control
AI writes a lot of my code. I still make every technical decision, read every change before it ships, and test it. Fast, but meticulous: the speed is only worth something if what goes live is right.
The way you want to work
Some clients want to look at every change before it goes live, others want me to deploy. Some want a weekly call, most prefer written updates. I work well asynchronously, and I still ask the important questions when they come up.
I think like an owner
I still run my own online products. So when I build or fix yours, I think about traffic, conversion, revenue and support as much as about the code, and I tell you when something is not worth building.
Ways to work with me
Fixed price, a flat monthly rate, or hourly. It's always me doing the work, not an agency. If you're not sure, describe what you need and I'll suggest one.
Examples of my work
Work where the team had to be able to carry on afterwards.
Requirements the team could build on
Inside a large Laravel learning platform I built custom reporting and certification workflows, turned customer conversations into clear technical requirements, and documented the work so the rest of the team could carry it forward.
Documented so others could work on it
A decade-old SaaS on an undocumented custom PHP framework. After the urgent fixes I wrote down how the system actually works and set up a Docker development environment, so the next developer did not have to start from zero.
Made a live product safer to extend
I refactored the access model of a running healthcare SaaS, moved a booking integration onto a clean pattern, and added tests, so the team could keep shipping without touching the risky parts by accident.
What clients say
"He also turned customer discussions into clear technical requirements and documented his work so the rest of the team could build on it. Vincent does not just close tickets, he thinks through the product, the edge cases, and the customer impact."
"Vincent works very well asynchronously: communication stays focused, there is little unnecessary back-and-forth, and he still raises the important questions when needed."
"We especially value how quickly he gets into mature projects and finds solutions that fit the existing state of the codebase."
Questions
Do you replace our lead developer?
No. I work alongside your team and make them better at what they do. If you need a lead developer, I can help you hire one.
What does this look like day to day?
Code review on the pull requests that matter, pairing sessions on hard problems, written standards your team can follow, and a regular call to go through decisions.
Can you help our team use AI tools well?
Yes. That is a large part of the work now: which tools, how to use them for everyday development work, how to review what they produce, and where they should not be trusted.
Our developers are junior. Is that a problem?
No, that is the usual case. Junior developers with a senior reviewer and good tooling get very productive. Junior developers without either produce a codebase that costs a lot later.
Do you work remotely?
Yes. I am in Germany and work with teams across Europe and the US, mostly in writing, with calls where they help.
How do you charge?
Fixed price for a job with a clear outcome, a flat monthly rate for ongoing work, or hourly. Describe what you need and I'll suggest one.
Get in touch
How big your team is, what they are working on, and where you feel they need help. A few sentences are enough.
If you would rather talk first, book a 30-minute call.