Development
Laravel development for business systems
A lot of Danish business systems run on Laravel: customer portals, booking, invoicing, and internal tools that outgrew a spreadsheet. I build them, extend them, and take them over when the person who wrote them has moved on.
When this makes sense
- A Laravel system runs part of the business and exactly one person understands it
- You need a feature that touches the database, the queue and the billing at the same time
- The framework upgrade has been postponed long enough that upgrading is now its own project
How it works
- 01
Map it
I read the codebase, the schema and the jobs before touching anything, and tell you what I found — including the parts you did not ask about.
- 02
Build it
Feature work or upgrade work, in small pieces that can go live on their own. You see it running on staging rather than in a status report.
- 03
Hand it over
Migrations, environment variables and deployment written down. The alerts point at you, not at me, so nothing depends on my staying.
What the work covers
- New features, refactoring, and paying down the parts that slow every change
- Framework and PHP version upgrades, done incrementally rather than as one jump
- Queues, scheduled jobs, and the background work that fails quietly
- Tests around the parts where a mistake costs money
Common questions
- What does Laravel development cost?
- Hourly work is DKK 600 an hour ex. VAT. A defined build starts at DKK 48,000, which is 80 hours, at an agreed scope and delivery date. Danish agencies typically quote from around DKK 150,000 for an MVP and DKK 250,000 to 600,000 for a mid-sized web application — scope drives that far more than the hourly rate does.
- Can you upgrade an old Laravel version?
- Yes, and it is worth doing before it becomes urgent. I upgrade in steps with the test suite and staging in between, rather than jumping several majors at once and spending the savings on debugging. If there is no test suite, writing a thin one around the critical paths comes first.
- Can you work alongside our existing developer?
- Yes. Reviewing pull requests, taking the pieces nobody has time for, or being the second senior opinion is a normal arrangement. I am not trying to become the only person who understands your system — that is the situation most clients call me about.
- What about the database?
- It is usually where the real problem is. Missing indexes, a schema that fit the original idea and not the current one, and queries that were fine at a tenth of the data. I work in Postgres and MySQL and will tell you when a slow page is a database problem wearing a frontend costume.
- Laravel or WordPress for my project?
- If the main job is publishing content you want to edit yourself, WordPress. If the main job is logic — users, permissions, calculations, a workflow with states — Laravel, and you will spend less over three years than you would forcing the other one. I will give you the honest answer even when it is the cheaper one.
Other stacks I work in
Not sure which one to pick?
Send a couple of lines about what you are trying to achieve. You get a reply within 24 hours, and an honest yes or no.