Internal tools
Used by your team every day, built around how they actually work.
Custom business applications
Software built around your process, not the other way round
I build business systems for companies that have outgrown spreadsheets, or bought software that does not fit, and now spend part of every day closing the gaps by hand.
ItemStatus
Order from a clientApproved
Production planIn review
Delivery noteGenerated
New clientWaiting on you
Price list updateDraft
3 to 4 weeksto the first usable version
Two environmentsyou approve every change before it goes live
Yoursthe code, the data and the accounts
Recognise this
You need this if
- Your process lives in spreadsheets, chat threads and email, and nobody has the whole picture.
- The software you already pay for forces your team to work around it.
- The same information exists in three places and none of them agrees.
- Growth means hiring someone to coordinate the work, not to do it.
- Answering one customer question takes two colleagues and a search.
What I build
Seven kinds of system, one way of working
Each one is shaped around the process you already have, not around a template.
Client portals
Your customers see their own orders and documents, without asking anyone.
Approval workflows
Every step has an owner, and nothing waits on a message being noticed.
Onboarding flows
What people enter is checked as they type it, not after it is wrong.
Generated documents
Produced from data you already have, instead of written again.
Per client terms
Agreed once in the negotiation, applied on their own from the first order.
Multi company platforms
Each company has its own users, access and commercial terms, whether the system is your internal tool or the product you sell.
Approvals
Every step has an owner
Work moves through the people who have to see it, in the order you set. Nothing waits because a message was not noticed, and nobody has to ask where something stands.
- Steps and owners you define, not a fixed template
- Status visible to everyone who needs it
- A reminder when something has been sitting too long
- A record of who approved what, and when
ItemStatus
Purchase requestApproved
New clientWaiting on you
Price changeIn review
Delivery noteApproved
Discount requestDraft
Documents
Written once, produced automatically
Delivery notes, contracts and invoices come out of the data already in the system, in your own format, at the moment they are needed.
- Generated from records, never retyped
- Your layout and your numbering
- Produced as PDF, ready to send
- The document and the system always say the same thing
From data to document
Already in the system
Client and address
Items and quantities
Agreed terms
Delivery date
Delivery note
Header and numbering
Lines and totals
Signature block
PDF, ready to send
Onboarding
New clients enrolled without a phone call
A new client fills in their own details, the system checks them while they type, and the paperwork comes out at the end. You approve, and they can order.
- Invitation by email, filled in by them
- Company data checked in real time, against the official register
- The agreement generated from what was actually agreed
- Terms applied on their own, from the first order
Enrolment
Invitedemail sent
Detailschecked live
Agreementwaiting on you
Company dataValid
Commercial termsTo approve
Messages that send themselves, and get checked
Reminders, confirmations and daily reports go out on their own. What bounces is caught and reported, instead of disappearing quietly.
- Scheduled reports, daily or weekly
- A reminder before something is due, not after
- A confirmation at every change of status
- Bounced messages detected, so an offer is never lost in silence
Sent and accounted for
Daily production reportSent
Delivery reminderSent
Order confirmationSent
Offer to a new addressBounced, flagged
Weekly summaryScheduled
How it runs
From first look to a system in daily use
Map
We look at what you have and agree what should be built, and what should not.
First version
The smallest system your team can use every day, in real work, not in a demo.
Extend
What comes next is added in steps, once the first version is in real use.
Run
It stays online, updated and backed up, by the person who built it.
First usable version in three to four weeks
How long and how much
Two numbers, before you ask
3 to 4 weeksto the first usable version: the smallest system your team can use every day. What comes after is added in steps.
Scoped with youCustom systems are scoped individually, so there is no figure that would mean anything before we have talked. After scoping you get a fixed price, and it does not move while the work runs. The first conversation costs nothing.
Questions
Frequently asked questions
Custom software or off-the-shelf: how do I decide?
Off-the-shelf is usually cheaper and faster when your process fits it. Custom pays off when the tool would otherwise force your team to work around it. I will tell you honestly which case you are in.
How long does it take?
The first usable version is typically ready in three to four weeks. What comes after is added in steps, once the first version is in real use.
How much does it cost?
Custom systems are scoped individually, so there is no figure that would mean anything before we have talked. After scoping you get a fixed price, and it does not move while the work runs. The first conversation costs nothing.
What is it built on?
On what fits the job. I work across the full stack, so the choice is not made for you in advance. If you have a technical team, we decide it together and stay inside what they can maintain. If you do not, I make the recommendation and explain it in plain terms, including what it costs you later and who else could take it over. What never changes: the source code is yours, and another developer can pick it up.
Who owns the code and the data?
You do. Your code, your data, your accounts, with a clear handover and no lock-in.
What happens after launch?
The system is documented and maintainable. I can support, fix and extend it on an ongoing basis, or hand it to your team.
Need a business application built around your workflow?
Before anything is built, we map what you have and agree what should be built.