Foundation · Platforms, integrations and migrations

First the foundation. Then AI.

I have been building and integrating the platforms organisations run on for over twenty-five years: websites, portals, business software, integrations and migrations. On Laravel and .NET, with Statamic or Sitefinity. That foundation is still there, and it is what you need before you put AI on top of it.

The portal is fifteen years old and nobody dares touch it.

The editors work around the CMS instead of with it.

Three packages, and none of them talks to the other two.

01 · Four kinds of work, on Laravel and .NET

What I build

Four kinds of work that keep coming back, in two stacks. Laravel with Statamic on one side, .NET with Sitefinity on the other. Which one it becomes is decided by what is already there and who will maintain it, not by my preference.

A monitor showing a portal: a sidebar, a few panels and one red button.

Work 01

Platforms and portals

Business-critical web applications and portals on Laravel and .NET, built to last for years. Customer portals, member environments and internal business software, with the permissions and the reporting that come with them.

Laravel · .NET

A laptop with a page being edited, and a hand holding a red pencil to the screen.

Work 02

Content and CMS

Statamic, Laravel and Sitefinity. A CMS editors can actually operate, with a structure that grows with you. Statamic when it has to be light and fast, Sitefinity when it has to fit a .NET landscape.

Statamic · Sitefinity

Two different plugs joined by a red adapter.

Work 03

Integrations

Two packages do not know each other, so your people move the data by hand. I build the integration between them, including to AFAS, Exact and Moneybird. With queues, retries and monitoring, built to run unattended.

AFAS · Exact · Moneybird · Peppol

As a product: The Connector

An old, weathered server cabinet and a new one beside it, with a red arrow carrying a small crate from the old to the new.

Work 04

Migrations

From an outdated system to a modern platform. New alongside old, moving over component by component, with a way back. Boring and predictable, the way a migration should be.

From old to new · from .NET to Laravel · from custom code to a CMS

As a product: The Build

02 · Why this work comes first

The foundation under AI

AI systems do not run in a vacuum. Once you trust AI with work, it has to reach your data, fit your processes and connect to systems that have sometimes been in place for twenty years. Most AI projects do not fail on the model but on that connection.

Foundation 01

Reaching your data

A model is only as good as what it gets to see. That takes a platform where the data is in order and can be opened up safely, with permissions that are right.

Foundation 02

Fitting your processes

AI that sits next to the work does not get used. It belongs in the portal, the CMS or the business software people already work in.

Foundation 03

Connecting to what is there

Integrations with packages that do not know each other, and migrations away from what has grown too old. That work comes first, or you build on sand.

That is the work I have been doing for over twenty-five years, and that is why it sits here, ahead of the AI offer.

03 · Where this comes from

What can you verify?

Enterprise environments through Progress Software, for organisations including WHO. Financial services at Van Lanschot. Member platforms at Vereniging Eigen Huis. Plus fifteen years of independent work for smaller organisations, where the same principles apply on smaller budgets.

Enterprise on .NET and Sitefinity

Through Progress Software, the maker of Sitefinity, I worked in enterprise environments for organisations such as WHO and Van Lanschot. Renewing outdated systems without downtime, on .NET, in landscapes with dozens of other systems around them.

About Daniel

Verify · The full career is on the About page.

A pipe fitting with two flanges, one of them red.

At Concent the integration and migration are delivered

The Cockpit of Stichting Concent pulls authorisations and reports from over fifty AFAS environments. AFAS is retiring the connection method it ran on, so without work that Cockpit would stop for every affiliated organisation. I migrated it to OAuth, took the keys out of the source code and extended the authorisation checks. The connection now runs on OAuth, both at Concent and at the affiliated organisations. Quoted in phases, with a fixed price per phase.

Delivered · I will walk you through the approach, the phasing and what is running now.

A bench vice with a red handle, clamping a circuit board.

This site and my own products run on Laravel and Statamic

What I build for clients, I use myself. This site runs on Statamic. Expensio, Cranely and Dotmap run on Laravel, built in my own delivery pipeline and in use by real users.

Visit the Lab

Verify · Everything in the Lab runs in production.

04 · Three products, from small to large

Which step fits?

Which step it becomes depends on what is on the table. Prices and scope are on the page of the product itself.

A pipe coupling with a red valve wheel on top.

The Connector

Do two systems need to talk to each other?

Then The Connector builds one integration in six steps that runs unattended: with queues, retries and a safety net, for a fixed price.

See The Connector

A scaffold of blue tubes with one red plank on the top level.

The Build

Does something need renewing or migrating?

Then it is a Build: a fixed scope, a fixed price per phase, new alongside old, and you can stop after every phase.

See The Build

A small device under a glass bell jar, with a red tag on a thread.

The Sprint

Is the question still broad?

Then The Sprint proves in ten working days what can be done with what is already there: working code on the critical part and a decision with a path.

See The Sprint

05 · What people want to know

Any questions?

The questions that always come up, with short answers. If yours is not here, a half-hour call is the fastest route.

Laravel or .NET?

Both, and I have no preference that outranks your situation. If there is already a .NET landscape with a team maintaining it, I build within it. If you are starting fresh, or it has to be light and fast, Laravel is usually the better choice.

Statamic or Sitefinity?

Statamic is light, fast and pleasant for editors, and belongs with Laravel. Sitefinity is an enterprise CMS on .NET, with the governance and the integrations large organisations need. I have worked with both for years and choose based on what is already there.

Can a migration run without downtime?

Yes, if you do it component by component. New alongside old, moving over each component separately, and only switching off the old one once the new one is proven. There is a way back at every point.

What does it cost?

That depends on what is there. A Connector and a Build have a fixed price per step or per phase; it is on the product page. For a migration or a new platform you get a proposal with a price after a call or a Sprint.

Do you also work with our own team or agency?

Gladly. As an architect alongside your developers or an agency, or as the builder of the hard part. The knowledge then stays with you, and the build afterwards needs no handover.

A small house with a red roof, standing firmly on a large stone foundation.

Who builds this

Building this since 1999 and still doing it in person.

Every AI system I build rests on a platform, a CMS or an integration that was already there. I have done that work since 1999, and it has never once bored me. Precisely because it should be boring and predictable: a portal that lasts for years, an integration that runs unattended, a migration without downtime. That is what you build AI on, not the other way around.

Daniel Plomp · AI Architect & Builder

Something that needs renewing, connecting or migrating?

Send a link or describe the situation. You will get an honest picture of the route and what it costs.