One task. Five days. Yours to keep.
It starts with a task and ends with you holding the keys.
Pick the task
A thirty-minute call, six questions: walk me through the task, how often it happens, what kicks it off, what "done" looks like, what breaks it today, and who else needs to be able to run it. I say the price out loud on the call.
You hold: a one-page scope note within two hours, including what's not included.
Before we talk: ten minutes on the intake, so the thirty start sharp.
Five days
Day one I get access and do the task by hand once, end to end. Day two the main flow works on real-shaped data and you get a screen recording. Day three the edge cases and the failure rule: it stops, it emails you, it never half-completes. Day four it runs beside your person on the same inputs, timed. Day five, handover.
You hold: a note or a recording at the end of every day.
You own it
Code, credentials and configuration transfer on the handover call, and I remove my access. The runbook is written for your least technical person: what it does, when it runs, how to check it, how to turn it off.
You hold: ownership, in writing. Paperwork, not a shrug.
If you want more
A second task is the easiest thing to add. The full map is the audit. And if you'd rather I keep running what I built, that's managed, from $2,500 a month.
You hold: the choice, with nothing pitched on day five.
The spec, plainly.
| Where it runs | On the accounts and tools you already own. Nothing runs on mine. |
|---|---|
| The tools | Whatever the job needs, on your accounts and your bill. If you'd rather hold everything yourself, in your own building, we write it into the scope. |
| Access | The automation touches only the files its job needs. Nothing else. |
| When it fails | It stops, it emails you, it never half-completes. One switch turns it off without calling me. |
| Anything sent under your name | A person approves; nothing sends itself, unless the scope note says otherwise. |
| Proof | Day four: it runs beside your person on the same inputs. You see both outputs, timed, before you accept. |
| Paper trail | A one-page runbook: what it does, when it runs, how to check it, how to turn it off. Paperwork, not a shrug. |
| Running cost | Stated in the runbook before you ask, including any usage fees. Usually a few dollars a month. |
| If we part ways | You keep the automation and your data. Removing my access is the whole offboarding. |
The spec doesn't change as the builds get bigger. That's the point.