I
ITPER
CUSTOM SOLUTIONS

When off-the-shelf systems stop being enough

A B2B panel with individual pricing, a product configurator, a booking system, a customer portal, a quote calculator. I build what you cannot buy as a subscription, because your process is different from everyone else's.

See the scope
Your processinstead of bending the company to a template
The code and data stay yours

What I build most often

  • B2B panels: individual pricing, credit limits, deferred payments
  • Product configurators that price an order live
  • Booking systems with a calendar and reminders
  • Customer portals with order history and documents
  • Quote calculators that turn a price question into an enquiry
  • Internal tools: job flows, reports, task lists

Before I propose anything custom, I check whether it can be done with existing tools. Custom code gives more freedom, but it is also something that has to be maintained afterwards.

B2B panels
Configurators and calculators
Bookings
Customer portals
Internal tools

When is building something custom worth it?

When yet another plugin solves half the problem and leaves the other half for you to finish by hand.

The process stays yours

You do not trim the way you work to fit the limits of an off-the-shelf tool. The tool adapts to how you actually sell.

No more subscriptions for everything

Ready-made solutions cost every month for as long as you use them. A custom rollout costs more upfront, but without a meter running in the background.

The code and data stay with you

You get the repository, the credentials and the documentation. You can develop the solution with me or with anyone else.

What I can build

Each of these tools is built for a specific process, not picked from a feature catalogue.

B2B / wholesale panel

Per-customer pricing, volume discounts, credit limits, deferred payment terms and fast ordering from a file.

Individual pricingCredit limitsCart import

Configurators and calculators

The customer assembles a product from options and sees the price live, instead of sending a question and waiting a day for an answer.

Live pricingVariantsEnquiries

Photo watermarking (AI watermark)

Product and portfolio photos marked automatically on upload — with the placement chosen so the mark does not cover the important part of the frame.

GalleriesProduct photosImage protection

Customer portal

Order history, downloadable invoices, delivery statuses and documents in one place — without phone calls to ask.

HistoryDocumentsStatuses

Internal tools

Job flows, task lists for the team and reports that used to be built in a spreadsheet copied every month.

Job flowsReportsPermissions

A mailing system on your own mailbox

Newsletters and transactional e-mails sent from your own domain — through Google Workspace or your hosting mailbox, with no subscription to an outside tool and no stranger's sender address.

Google WorkspaceDomain mailboxNewsletter

I also deploy into sites that already run

You do not have to rebuild your website to get automation. Most modules go into new projects and into sites that have been running for years alike — on WordPress, WooCommerce or a custom engine.

New project

Modules are planned together with the project, so they become part of the site's structure instead of being bolted on later.

  • Scope agreed before we start
  • One consistent look and one way of working
  • Cheaper than adding the same thing six months later

Existing site

I work on your current site: I check what can be connected and deploy the module without pausing your sales.

  • An audit of what is technically possible
  • Deployment without downtime
  • A backup and a rollback plan

How a custom tool is built

In stages, with a working version to try out as early as possible.

01

A conversation about the process

You describe how it works today and where it gets stuck. At this stage I ask questions more often than I propose solutions.

02

Scope and quote

I write down exactly what will be built, in what order and what it costs. No line item called 'and other work'.

03

Building in stages

First the smallest working version, which you test on real data. Then further features, in order of usefulness.

04

Rollout and growth

Go-live, training for the team, fixes after the first weeks and a development plan for the months ahead.

Custom solutions — questions

Upfront, usually yes. What counts is the total: subscriptions for several tools plus the time lost working around their limits can exceed the cost of a custom rollout within two or three years. If the numbers work out differently in your case, I will say so plainly.
Most often WordPress with WooCommerce when sales are the core, or Next.js when speed and an unusual interface matter. I explain the choice of technology before we start, not after the fact.
You keep the code, the data, the credentials and the documentation. I deliberately do not build solutions that only I can maintain.
Yes, and that is usually what we do. The first stage is there to prove the solution works in practice — only then does adding features make sense.
A simple configurator or calculator is usually 2–4 weeks. A B2B panel with integrations is a two to three month project. We set the schedule together with the scope.

Got a case that does not fit a template?

Describe how you work today and what holds you back. I will come back with a proposed scope and a quote — or with the news that an off-the-shelf tool is enough in your situation.

Describe your project

I reply within 24 hours