Question 1

What if it breaks after you hand it over?

Accepted Answer

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 $250 a month and I keep it alive. Plenty of people take neither, and their systems keep running.

Question 2

Why not just use Zapier, Make or n8n?

Accepted Answer

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.

Question 3

What does it cost to run once it is built?

Accepted Answer

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.

Question 4

How does payment work?

Accepted Answer

For a build: a fixed price, half up front and half when it is live. If it takes longer than I estimated, that is my problem, not your invoice. For smaller or open-ended work you can pay by the hour instead — $65 an hour, billed weekly, with an estimate up front and a check-in before it runs past it. Monthly cover is optional; most people do not need it.

Question 5

How quickly do you reply?

Accepted Answer

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.

What is your team still doing by hand?