Who owns what you build?
You do, completely. The code goes in a repository you control, on infrastructure in your name, and you own the copyright to the work. There is no licence to keep paying and nothing to renew.
What if it breaks after you hand it over?
Thirty days of fixes are included at no charge. After that you can either fix it yourself — the runbook and the source are yours — or put it on Watch at $450 a month and I keep it alive. Plenty of people take neither, and their systems keep running.
What if you disappear?
You are not locked in and that is deliberate. Everything runs on your server, the code is in your repository, and the runbook explains how to start, stop and restart it in one page. Any competent developer can pick it up. That is the whole point of not renting it back to you.
Why not just use Zapier, Make or n8n?
For something small and stable, use them — genuinely. They fall down when the volume grows, when the cost per run adds up, when you need a step they do not have, or when a vendor changes a screen and the whole flow quietly stops. What I build is real code you own, with logging and alerts, so a failure reaches a person.
What does it cost to run once it is built?
Usually a small server, around $6 to $15 a month, paid by you directly to the provider. If the build calls a paid model or API, that cost is yours too and I will estimate it before we start. None of that money comes to me.
How does payment work?
Half up front, half when it is live and handed over. Fixed price. If the build takes longer than I estimated, that is my problem, not your invoice.
Can my data stay on my own hardware?
Yes. Several of these can run entirely on a machine you control with no external API calls, for work that cannot legally leave your building. It costs more because it is more work, and the price is on the service page.
How quickly do you reply?
The same day, usually within a few hours. If a job is not a good fit for me I will say so in that first reply rather than waste your week.