Area 03 · Simplify work

Custom software, when nothing off the shelf fits

Customer portals, internal apps, forms, dashboards, integrations or a small software product of your own – in the browser, built in stages.

with proof

Questions? Let's have a quick chat.

The problem

Spreadsheets nobody understands any more. A process that no off-the-shelf software covers. Or an idea for a small product of your own that has been sitting in a drawer for months.

What you get

The scope of a clearly defined starter project. Exactly what is included is set out in your proposal.

Included

Requirements: who uses it, what it must do and what it mustn't
A testable prototype early in the project – you click through it on your own device
Delivery in stages with interim results
Logins and roles, data in the EU where possible, connection to existing programs
Handover with code, access and documentation; the rights after full payment as set out in the proposal

Not included

Hardware and point-of-sale systems
Apps for the app stores without a separate agreement

Ongoing, if you want it

Operation
Updates
Further development

Always separate: third-party costs

Hosting and cloud costs
Third-party licences
SMS and email sending

Typical forms: Customer portalinternal appdigital formsoverviews and dashboardsintegrationssmall SaaS product

For the agreed scope you get a written proposal with a fixed price. Ongoing support only if you want it. How a proposal comes about

Examples – how it could look

Use cases for orientation – not customer projects.

Example – how it could look

Customer list instead of a spreadsheet

A business replaces its customer spreadsheet with a small web app with roles for the owner and the office.

Example – how it could look

Order status for customers

A service business gives its customers a portal where they can see the status of their order – instead of calling.

How it works

01
Requirements
Who works with it, what must it do, what explicitly not?
02
Prototype
An early, testable version on your device.
03
Stages
Step-by-step delivery with interim results that you check.
04
Handover
Code, access, documentation, training. If you want: operation and further development.

What I don't promise

I don't build large systems with many stakeholders on my own. If a project is too big, I'll tell you in our conversation.
Custom software needs maintenance. Who runs it after handover is something we clarify beforehand.

Proof: real work

Software I have developed and keep developing:

Goes well with

Process automation Capture enquiries, transfer data, keep customers informed, coordinate appointments, process receipts – automatically, with approvals wherever a person should decide. Learn more Taskly setup I set up Taskly for your business: your current paper form rebuilt, fields, notes and automations configured, your team trained. Learn more Company knowledge and internal AI assistants Make manuals, processes and documents easy to find – with an internal assistant that answers with sources and only shows what someone is allowed to see. Learn more

Frequently asked questions

Why not just use off-the-shelf software?

If there is a suitable one, it's often the better choice – and I'll tell you so. Custom software is worth it when your process doesn't fit anything ready-made or you want to offer a product of your own.

Who owns the code?

After full payment you receive the rights, files and access agreed in the proposal. Building blocks that I use generally remain mine; you may use them in the project.

Does it work on a phone too?

Yes, I build in the browser – on phone, tablet and computer, without installation. If you like, the app can be added to the home screen like a regular program.