Skip to content
Rascals

Services

Seven ways I am usually brought in.

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.

01

A web application, from nothing

The full path: working out what it actually has to do, modelling the domain properly, 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.

  • Domain modelling
  • Laravel · Livewire · Tailwind
  • Admin and back office
  • Deployment included

02

Rescuing what already exists

An application nobody dares deploy, a developer who has moved on, a framework four versions behind. I take it over, get a test suite and a deployment under it, and make the next change boring again.

  • Code and risk audit
  • Framework upgrades
  • Tests around the scary parts
  • Handover documentation

03

E-invoicing and Peppol

Structured invoicing that passes the official rule set — UBL 2.1, EN 16931, validated against the same artefacts the receiving Access Point runs. Either as an application of its own, or fitted into the one you have.

  • UBL generation
  • EN 16931 validation
  • Access Point integration
  • Archiving that holds up

04

Payments and subscriptions

Stripe done properly: webhooks as the source of truth, idempotent handling, refunds thought through before launch rather than after the first one. Marketplaces and payouts with Connect where money passes between parties.

  • Stripe · Cashier · Connect
  • Subscriptions and metering
  • Payouts and marketplace flows
  • Reconcilable records

05

Integrations and automation

The work that removes an afternoon from somebody's 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.

  • CRM and API integrations
  • PDF generation and signing
  • Queues and scheduled work
  • Import and migration

06

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 shop, taking a neglected one over, or wiring the one you have into the stock, invoicing and shipping systems it should have been talking to all along.

  • Magento
  • Shopify
  • WordPress · WooCommerce
  • ERP and stock integration

07

Hosting and staying alive

Docker for development, a scripted release for production, backups that have actually been restored at least once. Plus somebody to call when the thing you depend on stops behaving.

  • Docker · CI/CD
  • Zero-downtime releases
  • Backups and monitoring
  • Maintenance agreements

Tools I reach for

Back end

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

Front end

  • Blade
  • Tailwind CSS
  • Alpine
  • Vue 3
  • Vite

Money and compliance

  • Stripe
  • Cashier
  • Connect
  • Peppol
  • UBL 2.1
  • EN 16931

Running it

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

E-commerce

  • Magento
  • Shopify
  • WordPress
  • WooCommerce
  • PrestaShop

Also fluent in

  • REST APIs
  • GraphQL
  • PDFtk
  • Meilisearch

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.

Taking on new work