N
Four specialisations

I do not solve technology questions. I solve process questions.

Four areas where custom software makes a difference you notice on the next working day. Each one begins not with a technology, but with a process that today takes more manual work than it needs to.

01

Custom Business Software

When an important process in your organisation only works around the standard software you have: extra spreadsheets, emails and verbal agreements.

Input
  • spreadsheets
  • scattered tools
  • coordination by email
  • paper forms
  • conventions without a system
Result
  • one central application
  • roles and permissions
  • approvals with a record
  • reporting from live operations
  • traceable changes

When standard software does not map an important business process properly, I build the software that does.

  • A central process runs on spreadsheets although a system ought to exist for it.
  • The same information is maintained in several tools in parallel.
02

AI Process Automation

When the same clerical work starts over every day: read, transfer, check, forward.

Input
  • emails with attachments
  • orders and forms
  • recurring enquiries
  • receipts and supporting documents
  • data from existing systems
Result
  • pre-sorted cases
  • captured and checked data
  • prepared replies
  • approval by a member of staff
  • a traceable record

I automate the steps that are repeated by hand every day, and leave the decision with a person at one deliberately chosen point.

  • Cases arrive by email and are transferred into a system by hand.
  • The same check runs every day against the same rules.
03

AI Assistants, Knowledge & Document Intelligence

When the same everyday questions get researched from scratch again and again although the answer already sits in documents and systems.

Input
  • PDF documents and manuals
  • contracts, quotations and invoices
  • email threads and enquiries
  • technical documentation
  • approved company knowledge
Result
  • an answer with a source reference
  • the passage instead of the file name
  • a summary across several documents
  • an answer that does not depend on who happens to be available
  • an assistant inside the daily process

I build assistants that answer questions from your own documents — and say which document the answer came from.

  • The same question is asked regularly and researched from scratch each time.
  • Information is transferred from documents into a system by hand.
04

Technical Operations

When the work happens at the machine, in the vehicle or at the customer's site — while the documents needed for it sit back in the office.

Input
  • asset and site data
  • service history
  • technical manuals
  • photos from the job
  • inspection and maintenance rules
Result
  • work instructions at the asset
  • service report from the job
  • photo documentation attached to the case
  • inspection record with time and person
  • feedback into the authoritative system

Whoever is out on the job has everything with them: the work order, the documentation for the asset and the data from your systems — in one application built to keep working without a network connection.

  • Technicians phone the office to get information that is already documented.
  • Reports are added later in the evening, long after the job is over.

You cannot buy this ready-made. What gets built follows the way your company works.

The means

And the technical side?

These eight capabilities are means, not offerings. Which of them are used follows from the process — not the other way round. If you are not sure which ones you need, that is the normal case and not a problem.

Do you recognise your process in more than one area?

That is the normal case. Most projects begin in one area and touch two others. Describe the process — sorting it into place is my job, not yours.