Replace the spreadsheet everyone is scared to touch.
Internal tools for clinics, agencies and property firms. Tell me the hours it eats. I build the tool that gives them back.
Sold in two steps: a prototype week you can stop after, then the build.
| What you buy | From | Usual time |
|---|---|---|
| Internal toolOne workflow off spreadsheets, built around how your team works | €18k | 3–5 weeks |
Week one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full. Prices excl. VAT.
Old and new
Drag the spreadsheet into the tool.
The problem
It works until it doesn’t.
Five people edit it. Three versions exist. One person knows how it works.
It started as a quick sheet and became the system. Now a new hire needs a week to learn it, one sorted column can wreck a month, and nobody tidies it up because nobody is sure what depends on what.
It costs you twice. Hours, because people copy the same facts from an email to the sheet to an invoice. And errors, because a typo in a cell looks exactly like a correct number.
You could buy a product, and sometimes you should. A custom tool earns its price when your process is what makes you money and nothing on the shelf fits it.
The arithmetic
What it costs you now, on your numbers.
What that adds up to
- Hours a year
- –
- Worth a year
- –
- Covers the from-price (€18,000) in
- –
Three numbers and the sum appears here. Nothing is filled in for you.
How it’s counted: people × hours × 46 working weeks a year, at your hourly cost. The hours are your own estimate of what the tool gives back. An estimate, not a promise.
Your numbers, your estimate. They stay in this tab: nothing is saved or sent.
- Sheet
- IT-02
- Title
- Hours-saved worksheet
- Inputs
- Yours
Vendor survey
9 hours
a week or more is what people said they spend transferring data by hand, on average.
Source: Parseur, Manual data entry report (opens in a new tab), 2025. 500 US professionals, a vendor survey. A reference, not your number. The worksheet above only uses what you type.
Vendor survey
50.4%
of the same people said entering data by hand had led to costly errors.
Source: Parseur, Manual data entry report (opens in a new tab), 2025. 500 US professionals, a vendor survey. A reference, not a result of mine.
How it’s sold
A prototype week, then the build.
Step one
A prototype week.
I sit with the people who live in the spreadsheet, pick the one workflow that hurts most, and build a prototype you can click, with your own column names in it. Fixed fee of €3,000, counted toward the project. If it’s wrong, or you’d rather stop, I refund the week in full.
How week one worksStep two
Then the build.
Accounts and roles, the workflow itself, an audit log, your data moved over from the sheet, and a handover. Usually 3–5 weeks from the first day to launch, at a fixed price from €18,000.
Proof
Two tools I built, and one I defined.
- Private work
Clinic platform
One workspace per clinic, patient and project records, insole design in the browser from a pair of 3D scans, and output to a 3D printer or a mill.
Internal tool. Screens recreated for confidentiality. No public link.
- Private work
Custom CRM
A browser power dialer with contacts, a call log and call scoring. It calls down a list, one lead after the next, and logs each outcome.
Internal tool. Screens recreated for confidentiality. No public link.
- Own product · Definition and prototype
Rental application desk
A rental application desk for letting agencies: the terms, the rules per region, every screen and clickable prototypes. It checks whether a file is complete and never rates the person.
My own product. Defined and prototyped. It has not shipped.
There are no client logos here and no hours-saved figures, because I don’t have ones I can stand behind yet. What I can do is open these on the call and show you how they work.
AI inside the tool
Software that reads, sorts and drafts. A person still decides.
Most of what eats hours in an office is reading something and typing it somewhere else. Software can do that part now, if the tool is built around it and someone signs off on what it produces. Anything a model wrote is labelled as such in the interface.
- Concept
Intake that sorts itself
Requests arrive by mail, form or phone note. The tool reads each one, fills in the fields and puts it in the right queue, with the reason shown. Someone approves it with one key.
- Concept
An assistant that shows its source
Ask where something stands and get an answer with the paragraph it came from next to it. When it isn’t sure, it says so and names who to ask.
- Concept
A desk for the agents
If software acts for you, you need to see what it is about to do. A queue of proposed actions, each showing what would change, with Approve, Edit and Reject.
These three are concepts I drew to show the idea. They are not client work. See the concepts in Explorations
Six ideas I’ve drawn for agencies, property firms and trades
- Concept
Lease reader and deadline calendar
Drop in a signed lease and it is read clause by clause. Every date the law hangs on it lands on one calendar, and the one that is close turns red.
- Concept
Internal knowledge assistant
Ask where something stands and the answer arrives with numbered sources, each lighting the paragraph it came from. When the sources disagree, it says so and names who to ask.
- Concept
Enquiry-to-viewing desk
Forty portal enquiries for one flat fold into one group viewing, in the order people wrote. Replies are drafted in each person’s language. Nobody is ranked.
- Concept
Client portal with live status
The client sees one status line and the one thing waiting on them. Approving a stage unlocks the next one and drafts its invoice.
- Concept
Spreadsheet-to-ops board
Drop in the planning sheet everyone is scared to touch. Each column gets a type, and the rows where the total does not match its parts light up before anything moves.
- Concept
Quote builder for trades
Change one measurement and the price, the margin and the PDF the customer gets move together. A margin under your floor turns amber before the quote leaves.
Public benchmark
67%
of AI tools bought from a specialist vendor worked out, in MIT’s 2025 study of company AI projects. Tools built in-house succeeded about a third as often.
Source: Fortune, reporting the MIT study (opens in a new tab), 2025. A public figure, shown because it argues against hiring me when a product fits.
Buy it or build it
- Buy, when a product fits your process as it is.It costs less and you can start today.
- Buy, when you’re still finding out what the process is.A custom tool freezes a guess.
- Build, when the process is what you sell.And nothing on the shelf does it your way.
- Build, when the interface is the problem.The people who use it every day lose time to it.
I’ll tell you on the call which side you’re on.
Scope
What you get, and what you don’t.
Included
- One team and one core workflow
- Accounts, roles and an audit log
- Your data moved over from the spreadsheet
- A prototype you can click at the end of week one
- A handover: a recorded walkthrough and written notes
- The code in your repository, the hosting in your accounts
Not included
- Hosting and third-party fees, which you pay the providers directly
- More teams or more workflows. Each one is quoted
- Integrations beyond the ones we agree on
- Running it for you after launch, unless you take the care plan
- A larger system. That is the product scope
Anything under “Not included” can be added. It changes the quote, and you see the new number before I start on it.
- Sheet
- IT-04
- Title
- Scope
- Team
- One
- Workflow
- One
After launch.
A tool your team uses every day needs someone to call. There is a care plan for fixes, small changes and updates. It is quoted on the call, because it depends on the tool. You own the code either way, so any developer can pick it up from the handover notes.
Price
What moves the price.
From
€18,000
Moves the price up
- A second team or a second workflow
- Integrations with other systems: accounting, calendar, phone
- Data that needs cleaning before it can move
- Rules that differ per location or region
- Features that read documents or draft replies
Keeps it at the from-price
- One workflow, one team
- A spreadsheet with clear columns
- One person on your side who decides
FAQ
Questions people ask before the call.
If one of them fits, use it. They cost less and you can start today. A custom tool makes sense when your process is what you sell, when the interface is what your team struggles with, or when per-seat fees have grown past the price of owning it. I’ll tell you on the call which side you’re on.
You own the code, so anyone can. There is a care plan for fixes, small changes and updates, quoted on the call. If you have a developer, the handover notes are written for them.
Then it takes longer at the same price. The quote is fixed. If I underestimated, that is my cost.
Yes. The code is in your repository, the data is in your database and the hosting is in your accounts, from the day you carry on past week one.
Where it saves real time: reading documents, sorting requests, drafting replies. Those features are labelled as AI in the interface, and a person approves what they produce.
Its data moves into the tool before launch. The sheet stays as a read-only archive, so nothing is lost and nobody keeps working in it.
With a 20-minute call, then the prototype week. At the end of that week you have something to click and a fixed price for the build, usually 3–5 weeks in all. If you stop there, I refund the week.
Guarantees
Four promises, in writing.
Fixed price
No overrunsThe price on the quote is the price. If I underestimated, that is my cost.
Staged payments
Stop after any stageYou pay per stage and can stop after any stage.
Week one
Refunded if you stopWeek one is a fixed fee of €3,000, counted toward the project. Stop at the end of it and I refund it in full.
Revisions
Until you sign offChanges inside the agreed scope of a stage are included until you sign it off.
An internal tool starts at €18k. Week one costs €3,000, and you get it back if you stop there.
Book a 20-min call