Four ways I tend to work. No fixed price list, because real scope sets the price. Tell me the problem and I will tell you how I would approach it and what it costs.
A clear read on an existing codebase or site: performance, security, accessibility, and the risks hiding in the architecture.
From a brief to a site in production. Laravel or WordPress or PrestaShop depending on what fits, with the infrastructure to run it.
For a site that works but should be faster and safer. Caching, queries, headers, and the boring details that move the numbers.
For juniors and small teams. Code review, architecture decisions, and the habits that keep a codebase readable as it grows.
Senior capacity inside your team for a defined stretch, not a fixed deliverable. I work in your sprints and tools, billed at my day rate and invoiced monthly.
The same shape every time, scaled to the work. Clear at the start, no surprises at the end.
| Included | Audit | Build | Hardening | Mentoring |
|---|---|---|---|---|
| Written report | ● | ● | ● | · |
| Design & build | · | ● | · | · |
| Performance & security pass | ● | ● | ● | · |
| CI/CD & tests | · | ● | ● | ● |
| Pairing & review | · | · | · | ● |
| Post-launch support | · | ● | ● | ● |
A senior freelance full-stack developer in Belgium costs €600 to €750 a day direct, compared to the market average of €450 to €500 (agencies add 15 to 40 percent markup). I charge at the senior end due to eleven years in production, work on national election platforms, and the Pulsar framework. A quick quote calculator gives your range, then a firm quote follows enquiry. On-site work adds travel from Huy at €0.42 per kilometre.
A code audit identifies security vulnerabilities, performance bottlenecks, technical debt, dependency risks and architectural weaknesses from source through production. You receive a prioritised, actionable report with clear next steps, not just a list of issues.
Inherited code builds technical debt, security blind spots and performance drag that compound over time. With eleven years in production I trace bugs to root cause, assess whether the architecture scales, and flag compliance or security risks before they become costly.
Yes. Alongside audits, builds and hardening, I work as a senior contributor in your sprints, tools and processes, billed at my day rate with monthly invoicing. This suits teams needing senior capacity for a defined period rather than a single deliverable.
Walk through a recent project end to end with them, asking about tradeoffs and what they'd change. Look for verifiable work you can visit live and references from teams they worked with, not just logos. My portfolio links to live projects and I welcome a detailed walkthrough of how each was built.
Yes. Security hardening prioritises high-impact fixes first: authentication, input validation, error handling and dependency updates. The engagement ranks risks and fixes what matters most, so you improve security without rewriting the application.
For most small to mid projects, one senior full-stack developer is faster: a single owner of the whole stack, no handoffs, fewer meetings and clear accountability. Separate specialists make sense at large scale or when front and back workloads run in parallel. For focused builds, audits or product work, full-stack keeps momentum and budget tight.
Clear communication matters more than time zones. Pair programming, regular syncs, documentation and async updates sustain momentum. I work remote-first across BE, LU, FR, NL and DE teams, with optional on-site meetings billed separately for travel.
Yes. While auditing or hardening your codebase, I teach your team to spot issues, review code effectively and improve practice, so capability outlasts the engagement.
Laravel patterns, database design, API architecture and PHP 8.x are essential. Beyond that: payment systems, multi-tenancy, performance tuning and OWASP-grade security. I bring eleven years in production with PHP 8.5, Laravel and Symfony.
Current architecture, team size, scale expectations, known pain points, compliance needs and timeline. A quote without understanding your context is a red flag. I give firm quotes on enquiry, once I understand what you need.
Most audits run from a few days to two weeks depending on codebase size and complexity. You receive a structured report with prioritised findings and clear next steps, with scope and timeline agreed up front.