Skip to content
Rascals

Services

Eight ways I am usually brought in.

A website or a webshop, custom software for what your business actually does, or taking over what is already there. Most projects are a couple of these at once. If yours is none of them, say so anyway — the answer is either yes or a name worth calling.

What it costs E-invoicing, mandatory since 2026

01

A web application, from nothing

The full path: working out what it actually has to do, pinning down what the words mean — what a customer is, when an order counts as paid, what happens next — building it, and putting it on a server that stays up. Laravel and Livewire, because a small team maintaining one codebase beats a large one maintaining three.

  • Working out what it must do
  • Laravel · Livewire
  • Admin screens included
  • Put live and kept running

02

Rescuing what already exists

An application nobody dares change, a developer who has moved on, a system that has gone years without an update. I take it over, get a test suite and a deployment under it, and make the next change boring again. If you are on the other side of that story — an agency holding a client's codebase with no Laravel people free — it is the same work, bought by the hour instead of by the project.

  • A survey of what is there
  • Updates and security brought current
  • Tests around the scary parts
  • Written down for the next person
Hiring a freelance Laravel developer

03

E-invoicing and Peppol

E-invoicing has been mandatory for Belgian B2B invoices since 1 January 2026, and a PDF by email no longer counts. Structured invoicing that passes the official rule set — Peppol, UBL 2.1, EN 16931, checked against exactly the same rules the receiving end applies, before it leaves. Either as an application of its own, or fitted into the software you already use.

  • Invoices in the required format
  • Checked against the rules first
  • Connected to the Peppol network
  • An archive that holds up
The obligation and the options in full

04

Payments and subscriptions

Stripe done properly: an order counts as paid when the payment provider confirms it, not when the customer clicks the button, and a duplicate notification is never booked twice. Refunds thought through before launch rather than after the first one. Marketplaces and payouts with Connect where money passes between parties.

  • Stripe · Connect
  • Subscriptions and metering
  • Payouts and marketplace flows
  • Figures you can reconcile

05

Integrations and automation

The work that gives somebody back an afternoon, every week: a CRM that fills itself, provider PDFs generated and signed, documents filed where they belong, mail that goes out on time and can be resent. Zendesk, HubSpot, Shopify, amoCRM and anything else with an API — built before, and built to survive the other side changing it.

  • Zendesk · HubSpot · amoCRM
  • Connected to your webshop
  • PDFs generated and signed
  • Work that runs by itself
  • Existing data brought across

06

Websites and webshops, on the platform that fits

Next to Laravel there is Magento, Shopify, WordPress and WooCommerce — standard work here, not a favour on the side. Building a website or a webshop from scratch, taking a neglected one over, or wiring the shop you have into the stock, invoicing and shipping systems it should have been talking to all along.

  • Magento
  • Shopify
  • WordPress · WooCommerce
  • Websites and landing pages
  • ERP and stock integration
What a website or webshop costs

07

Hosting and staying alive

One repeatable way to put a change live, so an update is not an adventure. Backups that have actually been restored at least once — a backup nobody has tested is a hope. Plus somebody to call when the thing you depend on stops behaving.

  • Live without taking the site down
  • Backups that have been tested
  • Watched, day and night
  • Maintenance agreements

08

Risk management and security audits

A read of the application the way somebody with bad intentions would read it: authentication, authorisation, dependencies, what the server exposes and what happens on the worst day. You get findings ranked by what they would actually cost you, not a scanner report with two hundred lines of noise.

  • A survey of the application
  • Old parts with known holes
  • Who may do what, and why
  • A recovery that has been rehearsed

Tools I reach for

Back end

  • PHP
  • Laravel
  • Livewire
  • MySQL
  • PostgreSQL
  • Redis
  • Horizon

Front end

  • Blade
  • Tailwind CSS
  • Alpine
  • Vue
  • Vite

Money and compliance

  • Stripe
  • Cashier
  • Connect
  • Peppol

Running it

  • Docker
  • GitLab CI
  • Hetzner
  • DigitalOcean
  • AWS S3
  • Mailgun

E-commerce

  • Magento
  • Shopify
  • WordPress
  • WooCommerce
  • PrestaShop

Also fluent in

  • REST APIs
  • GraphQL
  • Zendesk
  • HubSpot
  • amoCRM
  • PDFtk
  • Meilisearch

Where this gets built

Everything above is written in Roeselare, for companies across West Flanders, the rest of Belgium and beyond. If you are nearby I am glad to start at your table — for an application, an hour at a table turns up more than three emails. The rest of the work runs online, including for clients around the corner.

A web developer in Roeselare

Not sure which of these you need?

That is normal, and working it out is the first thing I do anyway. Describe the problem in your own words.

Start a project Or just send an email

Taking on new work