Service 08 — Business software

Software shaped around your business — rather than the other way round.

Business software here means software for exactly one company: jobs, fault reports, deadlines, shift plans, inspection records — your own process, the way it actually runs. It pays off when that process IS the business and no off-the-shelf product fits it. If one does fit, take it; and a spreadsheet carries some things for longer than people expect. Which of the three cases you are in is the first thing we settle — not after the contract is signed.

Who it's forFor businesses whose work hangs on a process of their own — and whose knowledge of it currently lives in spreadsheets that grew over years, in binders, and in a few people's heads.

Scope your project — date and guide figure

Price: Fixed price

Starting point

Where it usually goes wrong

The truth is spread over four files

One list in sales, one in scheduling, one in accounts, and a binder on the shelf. Each is looked after, and none of them is the right one — which one counts depends on who you ask. If that person is away, their file is away too. That, not the wish for a report, is what sets most of these projects off.

A shared file has no idea who you are

Anyone who can open it sees all of it and may change all of it — margins next to sick days, hourly rates next to supplier prices. And when a row reads differently than it did yesterday, nothing records who changed it. That is not carelessness on anyone's part; it is a property of the filing.

The new program ends up standing next to the old one

An application that knows nothing about your inventory system, your accounting and your time recording has to be fed twice. After a few weeks nobody feeds it, the old spreadsheet is back, and the verdict is that the software did not fit.

Demonstration

One case, one version of it

From the moment it arrives to the record it leaves behind — and at every point it is visible who holds it and what they are allowed to do.

01
The case gets a number
A fault report, a job, an inspection: it comes into being somewhere everybody knows to look — instead of as a row in the file of whoever happened to take the call.
02
Each role gets its own screen
Scheduling sees dates and engineers, accounts sees amounts and deadlines. The same application shows two different views because two different people are sitting in front of it.
03
The neighboring systems supply it
Parts and prices from the inventory system, hours from time recording, the document into accounting. What is kept there is not typed again here.
04
What is left behind is evidence
Who changed what, and when, stays attached to the case. When a customer, an auditor or a court asks, the answer is already there — nobody has to reconstruct it.

Pause the motion

Scope

What you get

First the question of whether it has to be built at all: If a tidied-up spreadsheet will do, we say so. If there is a standard product that fits your process, we name it — building your own because an industry package pinches in two places is the most expensive route to two solved places. What we do NOT take on: accounting, inventory and payroll stay where they are. We connect to them rather than replace them.
The process you actually have: We watch how the work is done today, including where people work around the official procedure. Those shortcuts are rarely sloppiness; usually they are the step the procedure forgot. Software that only models the procedure gets worked around exactly like the procedure.
Roles and permissions, before the first screen exists: Who may look, who may change, who may approve. This is not laid over a finished application afterwards — it sits underneath it: every list, every field and every button knows its role. And every change to a record stays traceable with a time and a person. That is the difference from a file, which has a latest state but no history.
Migrating what you already have — often half the work: Merging spreadsheets that grew over years is frequently the larger share of the effort: duplicates, three spellings of the same customer, records that belong to nothing, amounts stored as text. We migrate them together with you and show BEFORE the migration what will merge, what will be left behind and what somebody has to decide by hand. Nothing is migrated quietly.
Connected to what is already running: Inventory, accounting, time recording, calendars: whatever is kept there comes from there and is not typed a second time. Which system is the authority for a given figure is settled up front — two systems calculating the same price are the most reliable source of two different quotes under one number. Where no interface exists, we say so at the start rather than at the end.
The cut: what deliberately stays out: Every application comes with a list of what it does not do. Vehicle tracking, an algorithm that writes the shift plan, text recognition that reads notice periods out of contracts: each is tempting, and each drags in a question of its own — the union contract, data protection, or liability for a deadline that looks like a fact and is a guess. What is excluded is written into the proposal.
Running it, teaching it — and who owns it in-house: An application nobody feels responsible for falls into disrepair. Before launch we name the person inside your business, train each role separately — scheduling needs something different from accounts — and leave documentation their successor can read. Hosted on our servers or on yours, whichever you prefer.
Handover without strings: Source code, database and credentials are yours. No per-seat license, no dependency on us. Anyone who wants it developed further later — by us or by somebody else — can do that without asking our permission.

Process

How it runs

01
Watch it happen, rather than ask about it
We follow the work and write it down: which lists exist, who keeps them, where something is entered twice and at which point things currently fall through.
02
Scope & fixed price
Screens, roles, interfaces — and the data migration priced as its own line, because it is the item people underestimate most easily. Then a binding proposal with a fixed date.
03
Build, migrate, test on your own data
The core first, then your existing records. You work one case through from beginning to end, with your own data, before anybody switches over.
04
Switchover & handover
Cutover, training per role, documentation, credentials. After that the source code, the database and the operation are yours.

Walkable demos

Don’t describe it — look at it

Invented businesses, real interaction. Click your way through before you ask what something like this costs.

All demos

The businesses in the demos are invented. They are not client references.

Price

What it costs

An application for exactly one business — with roles, permissions and the data you already have.

Fixed price

Data migration priced separately

Scope your project See all pricing

Deciding whether a standard product or a spreadsheet would do
Recording the process the way it actually runs
Role and permission model before the first screen exists
Migration of your existing records, reconciled for review first
Connection to inventory, accounting and time recording
Traceability: who changed what, and when
Training per role and documentation their successor can read
Source code, database and credentials are yours

Questions

What gets asked about this most

What does a website cost with you?

We quote fixed prices, not hourly rates. After the call you get a proposal with one number and one date — what's in it, stands. Starting prices per package are on the pricing page. If something new comes up mid-project, we discuss it first rather than quietly adding it to the invoice.

How long does a project take?

A company website typically runs three to five weeks, an app six to ten weeks plus the store review, a single automated workflow one to two weeks, an AI agent two to four weeks. The biggest variable isn't on our side — it's how quickly copy, images and access credentials arrive. The proposal states exactly what we need from you and when.

Do I need technical knowledge?

No. You need to know your business — the technical side is our job. We explain decisions in plain language, including what they imply down the line. After launch you get a short walkthrough and written documentation so you can maintain content yourself.

What happens after launch?

Your choice. Either you take over — code, content and all credentials are fully yours, with no dependency on us. Or you take the retainer: updates, monitoring, security patches and ongoing development at a fixed monthly price, cancellable monthly. No annual contract, no notice period.

Other services

A handful of building blocks. One system.

All services

You'll hear back within 24 hours