Skip to content

I build custom online platforms: bookings, client areas and internal dashboards connected to your CRM and invoicing.

Scope: In phases, with partial deliveries

Online platforms

When you need a platform, not a website

A website presents the offer. A platform is where people do something: book, log in, manage an order, see their data, or run an internal process.

If a page and a plugin would do, a platform is not the right answer. The diagnosis says which it is, and why.

What I build: bookings, catalogue, client area, panels

Typical builds are a booking flow, a catalogue with accounts, a client area, and internal panels for the team. The exact product is the one the diagnosis describes, not a fixed template.

Product architecture, UX and integrations

I design the product structure, the interface and the connections to the tools you already use: CRM, calendar, invoicing, or others listed in the scope.

The architecture is meant to be extended later, because a platform that can only do the first version will have to be rebuilt.

How I work in phases, with partial delivery

The work is split into phases with something usable at the end of each one. You can start running part of the product while the next phase is being built.

What each phase includes is written down before that phase starts. You can stop after any phase.

What's included

  • 01Bookings and catalogue
  • 02Customer area
  • 03Internal dashboards
  • 04Several languages
  • 05Product architecture and UX
  • 06Integrations with CRM, calendar and invoicing

Process

  1. 01

    Diagnosis

    A short review of your website, your shop, the migration you have in mind or the process you want to improve. You get: what to change, risks and scope, in writing.

  2. 02

    Project

    Design, build and testing with real use. Scope, milestones and budget agreed in writing before work starts.

  3. 03

    Support

    An optional monthly fee after launch: issues, SEO monitoring after a migration, improvements and new workflows.

A real project

A real project will be published here when I can share it. Nothing is invented in the meantime.

How I can help

If you need a product rather than a brochure site, the first step is a diagnosis: what to build first, how it connects and the phases, in writing.

Ask for a diagnosis →

Related guides

Other services

Frequently asked questions

When do I need a custom platform instead of a website or a plugin?

When people need to do something in the product — book, log in, manage an account, run an internal process — and a page or a plugin will not cover it cleanly. If they would, a platform is not the right answer. The diagnosis says which.

What kinds of platform do you build?

Bookings, catalogues with accounts, client areas and internal panels are typical. I build the product the diagnosis describes, not a single template I reuse for everyone.

What tools does it integrate with (CRM, calendar, invoicing)?

Those are common connections. The diagnosis lists which ones your product needs. I do not connect any system that has not been agreed.

How does working in phases and partial delivery work?

The product is split into phases, each with something you can start using. The scope of each phase is written down before it starts. You can stop after any phase.

Can it have more than one language?

Yes, when the project needs it. Languages are part of the scope written down after the diagnosis.

Who maintains the platform after launch?

That is agreed in the project. I can stay on for optional monthly support, or hand the product over so you or another team can maintain it. Nothing is assumed either way.

Tell me where your website, shop or process stands. A few lines are enough, and I'll suggest a first step.