Four things I build,
three of them one click away.
Most of what is on this page ends in links you can open before you reply to me: not case studies, not logos, just software that is up right now. 27 years, 300+ projects, and fifteen live properties, nine of them on this page.
What you can actually buy
Each one starts as the same conversation: what is broken, what “fixed” would look like, and what that is worth to you. Under every card is the work that says I have done it before.
AI Development
A model doing the job nobody wants to do (reading the documents, answering the same forty questions, writing the first draft) wired into the systems you already run, not sitting in a notebook on my laptop.
- A working prototype on a sample of your own data before the full build is priced
- Model choice, prompt and pipeline design: Gemini, Llama, DeepSeek, or a LoRA fine-tuned on what only you have
- Document extraction that turns PDFs into fields, with OCR and NLP rather than re-typing
- Hosted, logged in and live, with a defined behaviour for when the model is wrong, because sometimes it will be
The fine-tuning work (a merged LoRA on Hugging Face, a Gradio chat front end, and a PHP UI calling Python inference) needs a GPU and access rather than a link. I will walk you through it on a call.
Full Stack Development
Most businesses I meet run on a spreadsheet, an email thread and one person’s memory. This is the thing that replaces all three: the screens your customers see, the admin view you open on Monday, and the logic underneath that keeps the two honest.
- Front end, back end, database and deployment, not three suppliers pointing at each other
- Next.js, React and TypeScript where they earn their keep; plain PHP where that is the honest answer
- Accounts, permissions, payments, emails: the unglamorous parts that decide whether it survives
- On a domain you own, working on a phone as well as a desktop, with the code handed over to you
UltraCompress and ZeroDataUpload run on their own domains, and ZeroDataUpload does its whole job inside the browser. Nothing is uploaded anywhere. None of these are demos I stood up for this page.
Process Automation
Someone in your business spends Tuesday morning copying numbers between two systems. That work stays invisible right up until it stops, and then everyone sees how many hours it was quietly eating. I find those jobs and take them off your people.
- A map of the process as it really runs, not as the manual says, before anything is automated
- Python and Selenium against the systems that were never given an API
- Reporting automation where the record already lives: Excel and VBA, SAP, Tally
- Logging, failure alerts and a runbook, so nobody finds out in March that it stopped in January
One you can open, two that need access rather than a link. I will demonstrate those on a call. The SAP and financial-reporting automation from my audit-manager years is on the resume.
Database Solutions
It was fine when it was small. Now a report takes a minute, the hosting bill climbs every quarter, and somebody has suggested starting again. Usually you do not need a rebuild. You need someone to read the queries on a system they did not write.
- A written read of the schema, the queries and the indexes before anything is touched
- PostgreSQL and MySQL design, indexing and query tuning; Supabase for real-time data
- The slow queries ranked by what they are costing you, then fixed in that order
- Data pipelines feeding the models and dashboards that sit on top
This is the one offer with no headline demo, and I would rather say so than dress one up. Database work shows up as the thing that stopped being a problem. Every AI platform above is sitting on it. If you want proof first, send me a slow query and its plan. You will get an opinion, not an invoice.
Those are the ones I picked. There are twenty-eight on the projects page. Anything marked live you can open and use right now.
From first conversation to handover
No agency, no account manager, no hand-off to someone you have never met. Four steps, and you can stop after any of them.
We talk once, properly
You describe what is broken. I ask the questions that actually move the estimate: where the data lives, who else touches it, who on your side can say yes without a committee, and what happens when it is wrong. You leave that call with my honest read on whether it is worth building at all.
Written scope, quoted price
You get it in writing: what I will build, what I will not build, what I need from you, and the price against it. If the scope moves, the price moves before the work does, never after.
You see it running early
Short cycles, working software at the end of each one, on a URL rather than in a slide. If an idea turns out to be the wrong one, we find that out while it is still cheap to change.
Yours, with the lights on
I test the paths that matter and the ones users take by accident, then hand over the code, the credentials and a plain-English runbook. The oldest code on this site still runs exactly as it did in 2000. I build things to outlast my involvement in them.
The one thing I will not do is disappear into a black box for six weeks and come back with a reveal. If a project is going badly you will hear it from me on a Friday, not from a missed deadline in a month.
What working with me looks like
Price depends on scope, and I would rather quote your actual problem than publish a number that fits nobody. Tell me what you need in two lines and we will get you a real figure quickly, after one call rather than three meetings.
Fixed-scope project
You know what you want built. We write the scope together, agree the number, and I build to it. The number does not move unless you move the scope, and if you do, you see the new one before I start.
Audit and rescue
A build has stalled, a database has slowed to a crawl, or you have inherited a system nobody can explain. I read it, test it, and give you a written assessment with the fixes ranked by cost and payoff. The report is yours. Hand it to anyone, including a different engineer.
Ongoing retainer
Something is already live and needs someone who knows it, or your team needs an engineer with 27 years behind him a few days a month. Same person every time, so nobody has to re-explain the business.
Two things worth knowing up front. Small jobs are welcome (a slow query, a report that should not be manual, a second opinion on someone else’s architecture) and they are usually how the longer work starts. And I am one engineer, not an agency: your project never gets handed down to a junior, but I take a small number at a time. If you need thirty people by Monday, I am the wrong call.
Know what you need? Let’s scope it.
Tell me the problem in two lines and I’ll tell you what it takes, what it costs, and whether you should build it at all.