Fractional tech lead for Laravel and PHP teams
I join your team for part of every month and stay for months, not weeks. It sits between hiring a senior engineer and calling in a consultant: I get to know your codebase, your people and the history behind that odd workaround in the payment module, and I help you make the technical decisions that will still hold up in a year.
A fractional tech lead is a senior engineer who leads a team's technical work for part of the month instead of full time. The role covers what a permanent tech lead would do: architecture decisions, code review, coding standards and the technical side of planning.
AI helps me read an unfamiliar codebase quickly, so the first weeks go into decisions rather than archaeology.
- Time
- 12 or 16 days a month
- Where
- Remote, European hours

Who it's for
Teams that already ship, with capable developers, and decisions that will be expensive to undo.
- No senior lead
A growing team of capable mid-level developers without the architectural guidance to scale. I fill the gap while you build your permanent team.
- Fast growth
A product that is taking off, where today's technical choices have long-term consequences.
- Old debt
Legacy code that won't clean up in a single sprint. Months of steady attention from someone who knows both the debt and the business work better than a short burst.
- Not yet a hire
You need staff-level experience, but not full time and not yet as a permanent role.
A month with me in the team
I block the days for you, so you're not competing with other clients for them. What counts is the monthly total: if one week needs more and the next less, we adjust.
16 days
about four a week
12 days
about three a week
- Start of the week
We agree on what I'll be tackling, by week or by sprint, whichever way you already work.
- Standups, planning
I join the ones that matter, help prioritize and estimate, point out risks and sequence features sensibly.
- Pull requests
I review the significant ones, help set coding standards and give architectural guidance on new features.
- Hard problems
I pair with your developers or take the problem on directly. I ship code alongside the team.
- Weekly check-in
Priorities, progress, and what to change in our focus.
- In between
I'm in your Slack for the questions that can't wait.
How it usually goes
A steep start while I learn the terrain, a long stretch where most of the work gets done, and an arrival where the team carries on with less of me.
- 1. Month one
Assessment
Understanding the codebase, the team and the business. I'm productive from day one, and I'm also laying the ground for faster work later.
- 2. Months two to four
Stabilization
Usually the most productive stretch. We have our patterns, I know where things are, and the major progress happens here.
- 3. After that
Handover
Feature work, refactoring and mentorship. Once the intense phase is over, we scale the commitment down or move to single days.
What I don't do
Fractional work asks for commitment on both sides. I reserve a real share of my month for your team, so a few things are off the table.
- Parachute in, fix one thing and leave.
That's a consulting job, and it's fine: for a review or an assessment, book single consulting days.
- Sit on call waiting for tickets.
The days are planned, focused work, agreed at the start of each week.
- Fixed price on a moving scope.
Fractional work follows a team whose priorities change. A fixed price fits a well structured project with an agreed scope, not an ongoing role.
- Work for equity alone.
I'm open to hybrid arrangements for the right project, but the days are paid in money.
What it costs
Fractional work runs on a monthly collaboration, or retainer. Prices are public.
16 days a month
About four days a week. The usual arrangement for a fractional tech lead.
7,000 EUR / month6,800 EUR from six months
12 days a month
About three days a week. Enough for ongoing improvements, architectural guidance with implementation, or support for an existing team.
5,300 EUR / month5,000 EUR from six months
Single days
For a focused piece of work rather than ongoing leadership.
How a consulting day works480 EUR / day
The six-month price applies to engagements of six months or more. Invoiced monthly, due within 14 days. For a first engagement with a new client I usually ask for part of the payment upfront.
Short answers
The questions people ask before the first call.
How is this different from hiring a consultant?
Consulting is built around a project: a problem, an expert, a solution, done. Fractional work is built around the team. The problems change as the product changes, and the value grows as I understand your system more deeply.
Fractional tech lead or full-time hire?
Hire full time if you need someone in the team every day, in a permanent role. Choose fractional if you need senior technical leadership but not full time, or not yet. I reserve 12 or 16 days a month for your team, and the price is a monthly total.
Do you write code, or only review it?
Both. I review and set direction, and when a problem is hard I pair with a developer or take it on myself.
Do you work remotely?
Most of my engagements are remote. I'm usually available during European business hours and can adapt to other time zones when needed.
What happens when you're no longer needed every week?
We check regularly whether the arrangement still makes sense. When it doesn't, we lower the commitment or move to single consulting days.
Is the first conversation free?
Yes. It's how we find out whether this model fits your situation, or whether a few focused days would help more.
How do I choose a Laravel consultant?
Look at what you can check. Public code: my open source packages are on Packagist. Prices written down: they are on this page. And a plain list of what the person won't do: it is above. The first conversation is free.
Tech lead or CTO?
Tech lead. I work inside the engineering team on architecture, reviews and code. Hiring plans, budgets and board reporting stay with you, and if that's what you need, it's better to say so in the first conversation.