Your way of working, turned into a tool.
I build tools that take the routine work off your hands, and hand you the code at the end.
You already know how your business should run. The problem is usually that no software matches it, so the work gets done around the software instead: in a spreadsheet, in a second spreadsheet, and in somebody's head.
01
Two things I build
A simple app instead of the spreadsheet the whole team edits.
The one everybody has open, where two people save at once and Friday's version is the one nobody can find.
One button instead of a routine with ten steps.
The job someone does the same way every week, copying between screens, where step six is the one that gets forgotten.
A good tool saves you time, money, or both. What that is worth in your business, I will not put a figure on before I have seen how you work.
02
Two things I do not build
Platforms that only work once a lot of strangers join.
A social network, or a marketplace matching buyers with sellers. They need an audience before they are worth anything, and that is a different business from yours.
A replacement for your whole business system, in one project.
One person cannot do that well, and anybody who says otherwise is selling you the first six months of it.
03
Where AI fits, and where it does not
AI is worth using inside a tool when it does something a person would otherwise do by hand and dislike.
- reading what arrives and pulling out the part that matters
- sorting things into the right place
- turning a pile of text into a short summary
- drafting something a person then checks
04
How it works
A free conversation first, and two or three sentences start it. Mostly: do we match. If what you are describing is a platform or a replacement for everything at once, I will say so then rather than three months in.
A free written quote, when one meeting settles it.
What it does, what is left out, where it runs, the price, and an estimate in weeks.
Or roadmapping, €350, plus VAT where applicable, when one meeting is not enough.
How it should work still has to be settled, or something has to be investigated before anyone can put a price on it. It is credited against the first stage, and what you get is a written plan you keep either way.
The build runs in stages, each paid in full before it starts.
The price is fixed for what the plan describes. The weeks are an estimate, and they move mostly with how quickly the back-and-forth goes.
At handover the tool is yours.
Including its source code, running on your own accounts.
Thirty days to hold me to it.
Anything that does not do what was written is a bug, and I fix it. Something new or different is a change, and a change is quoted before I start it.
If you want a sense of the number before you write, what a project costs explains what drives it.
05
Four I built, and run
Webtools
A private intranet application, and the closest thing here to what this page sells. Three of the things it does.
- One button builds a new version of the software, so somebody who does not know the build system can put out a release without first learning one.
- It translates the product's text into other languages, with AI, inside the tool, instead of spreadsheets going back and forth.
- It puts Azure into plain tables: the files, the builds, and the finished work listed against each build, instead of moving between a separate Azure tool for every one of those jobs.
There is no public link to it, which is rather the point of an intranet.
How it's built, and what it's built with, is on its own page.
AmplyDigest
My own product. People send it the newsletters they subscribe to and the channels they follow, and every morning it sends back one email with the day in it.
The summarising is the AI part: it reads everything that arrived overnight, works out what is worth that person's attention, and writes it short enough to get through over coffee. The originals are kept only so the summary can be written, and I do not read them.
Behind that the tool schedules itself, delivers the mail, takes the payments and manages the accounts, and nobody operates it by hand.
It is the same shape as a business tool: one person built it, one person keeps it running, and it is where I found out what it takes to make AI output safe enough to send a paying customer every single morning.
How it's built, and what it's built with, is on its own page.
AmplyViewer, shown as a demo
It is where two kinds of work I have done come together: a 3D scene on one side, a web application on the other. Each unit in a building can be clicked in the picture, and what comes back is live data rather than a page somebody keeps up to date. Every deployment is built for one client and licensed to them.
The demo is a made-up company, built to show how it behaves.
How it's built, and what it's built with, is on its own page.
Electrix
Tracks a country's electricity prices. My own product, and I use it every day myself.
How it's built, and what it's built with, is on its own page.
Tell me what slows you down
Not sure where yours fits? You don't have to decide. Tell me what slows your business down, and we'll work it out together.