Delivered
is not
resolved.

You don't buy hours from us but a working result — embedded in your operations, and measured in hours and euros from week one.

Understand · Prove · Build · Stay
Trusted by
Verduurzaamnu

Client stories

OneMinded is not a traditional IT supplier for us, but truly an extension of our organisation.
Gert-Jan KouwenbergIT Director · Basiq Dental
Read the story

The work nobody counts

Retyping.Correcting.Double-checking.

It is budgeted nowhere, and every week it costs your best people hours. Projects don't fail on technology, but between question and build.

Two people at a table with a laptop and papers, in conversation

// 01 never-budgeted

Zero hours budgeted. Six hours per annual report gone.

At an accountancy firm one annual report took six hours of retyping, year after year, because nobody had ever counted it.

// 02 good-people-wrong-work

Your best people do the dullest work.

Specialists gather information that already exists instead of doing the work you hired them for.

// 03 errors-found-late

You meet the errors at the customer.

What was copied by hand gets checked only once it is out the door, and fixing it then costs more than catching it.

// 04 process-not-understood

Earlier attempts failed on understanding.

A vendor built what the document said, not what happened on the floor. That is why we spend a day on your floor first.

Our position

“That wasn’t in the specs” is not something you will hear from us. Software only pays off when someone feels responsible for what is different on Monday. So every engagement opens with one question: what should this deliver?

What that means

  1. We do not build what already exists, and if standard software does the job, we say so.
  2. The team that understands your problem also builds and maintains the solution, with no handover.
  3. The code and documentation are yours, even if you stop.

The week

How a week can run.

An example, not a fixed schedule: every bottleneck runs differently.

  1. Choose

    Together we pick one bottleneck and agree what must be different by the end of the week.

    Together with you

  2. Observe

    We sit with the people doing the work and measure what it costs today.

    With the people who do the work

  3. Build

    The first working version, built around your existing systems.

    Our team in Eindhoven and Jakarta

  4. Try it out

    Your people work with it; whatever chafes, we adjust.

    With your team

  5. It runs

    It works in your operation and the sums are done, after which you decide whether we build on.

    You decide

Impact

Every project we build contributes to education in Indonesia, the country our build team works from.

See where it goes

Open the project from its pin on the map.

Seven children sit on the wooden veranda of the school eating noodles and an egg from green bowls, the valley visible behind them.

Jakarta

This is where you start

Start with one bottleneck.

Work out what one bottleneck costs you today; the calculation runs in your browser, so nothing reaches us until you press the button.

Retyping, correcting, double-checking: an estimate is enough.

By default we use the Dutch average according to CBS, the Dutch statistics office, and if you know your own figure, you can enter it here.

This bottleneck costs you per year

… hours × … people × €47.60 × 46 working weeks

We count 46 working weeks a year: 52 minus holidays and public holidays.

Enter hours and people to see the sum.

What one week delivers

After one week something that works is running on this bottleneck and the difference is there in hours and euros; that week is paid and credited against what follows.

An estimate, not a quote and not a promise of savings.

One bottleneck, one week

Labour cost source: CBS, De arbeidsmarkt in cijfers 2025: an average of €47.60 per hour worked in 2025, including employer contributions (provisional figure). See the figure at CBS