How a consulting day works
I charge a flat 480 EUR for a consulting day. It is not hourly billing where every question costs money, and not a fixed bid where scope creep becomes the problem.
A day means focused work on your project. It does not mean eight hours logged to the minute: some days run longer when we are in flow, others end sooner when we have done what we set out to do.
- Rate
- 480 EUR a day
- Where
- Remote, European hours
- First call
- Free

What a consulting day includes
The engineering work itself, and what it takes for your team to keep it.
- Technical work
Writing code, refactoring existing systems, reviewing architecture, debugging, setting up infrastructure.
- Direct talk
I'm available through the day, from a quick message on Slack to a longer call about a design decision.
- Documentation
Notes on the decisions that need them, so your team knows what was done and why. Not pages of process nobody reads.
- Knowledge transfer
I work with your team, not in isolation. When I implement a pattern or solve a problem, the people who will maintain it understand it.
What I work on
My work is backend, and AI lets me move between languages.
- Today
Backend with PHP, mostly Laravel and Symfony, and with TypeScript.
- In the past
React, which I used in earlier work.
- With AI
Go and Rust, where AI helps me move between languages.
How engagements work
Most start with a conversation, and most are short.
- First conversation
You describe what you are dealing with and I ask questions to understand it. We find out whether I can help. It costs nothing.
- Scope and schedule
For a shorter job, such as a code review, an architectural assessment or one feature, we book a few days over a week or two. For work that runs over months, a monthly collaboration is the better fit.
- Focused blocks
I prefer whole days of concentrated work to scattered hours. The same hours spread across a week produce less.
- Remote
Most engagements are remote. I'm usually available during European business hours and can adapt to other time zones when needed.
What I don't do
Saying what I don't offer avoids misunderstandings.
- Fixed price on a vague scope.
I take fixed-price projects when they are well structured, with the scope and requirements agreed up front. When the scope is still moving, the day rate lets us adjust it as we learn what is needed.
- Work for equity alone.
I'm open to hybrid arrangements for the right project, but the days are paid in money.
- Pretend to know every stack.
If you need mainly mobile, or a stack I don't work in, I'll tell you, and probably point you to someone better suited.
- Disappear after delivery.
An engagement has a defined scope, and reasonable follow-up questions are part of the deal.
Why this rate
One flat rate keeps things simple: no argument about how many hours something took, no line items for every conversation, no reason for either of us to game the numbers.
Single days
A flat rate for a day of focused work. A review, an assessment or a feature fit in a few of them.
480 EUR / day
12 days a month
For continuing work, a set number of days reserved for you each month.
How a monthly collaboration works5,300 EUR / month5,000 EUR from six months
16 days a month
The same, with more days in the month.
7,000 EUR / month6,800 EUR from six months
Invoiced monthly, or at the end of a shorter engagement, due within 14 days. For a first engagement with a new client I usually ask for part of the payment upfront, after which we move to standard invoicing. The six-month price applies to engagements of six months or more.
Short answers
The questions people ask before booking a day.
What is the daily rate for a senior Laravel consultant?
I charge a flat 480 EUR for a consulting day. It is not hourly billing and not a fixed bid: one day of focused work, one price. What a day includes is listed above.
Is a day eight hours?
No. A day is focused work on your project, not hours logged to the minute. Some days run longer when we are in flow, others are shorter when we have done what we set out to do.
When is a monthly collaboration better than single days?
When the work runs over months. Single days suit a review, an assessment or one feature. For ongoing work, a monthly collaboration reserves a set number of days each month for you.
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.
Which languages and stacks do you work in?
Backend, with PHP (Laravel, Symfony) and TypeScript today. I worked with React in the past, and with AI I also work in Go and Rust. For anything outside that, I'll say so.
Do you take fixed-price projects?
Yes, when the project is well structured: a clear scope and requirements agreed up front. When the scope is still moving, the day rate works better, because it lets us adjust as we learn.
Is the first conversation free?
Yes. It usually gives us both enough to decide whether working together makes sense.