How a project actually goes.
Four steps. The short ones take a couple of days. The longer ones take a couple of weeks. There's no discovery phase, no statement of work template, no twelve-page deck. The rate comes up in the call.
-
You tell me the boring thing.
Email, phone, or the form. Whichever is easiest. No questionnaire, no proposal template. The first conversation is you describing what's on the list and me asking actual questions until I understand it. If it turns out to be something I'm not the right person for, I'll say so.
-
I tell you whether it's a 2-day job or a 2-week job.
Honest scoping after one or two calls. Some things are smaller than they look. Some are bigger. Either way you hear it from me before you commit, not three weeks in. The rate is whatever it is, and we talk about it on the call.
-
I build it.
You see progress as it goes, not at the end. Short loops. If something I assumed turns out wrong, you find out the day I find out. The same person who scoped it builds it, so nothing gets translated through a project manager.
-
You use it. If it breaks, I fix it.
No handover meeting that quietly becomes your problem. Most builds need a few tweaks once people actually start using them. That's part of the job, not a separate engagement. If it stops working in six months, you tell me and I look at it.
What this isn't.
-
Not a retainer.
One thing at a time. You bring the next thing when there is a next thing. If there isn't, there isn't.
-
Not a tool you have to learn.
What I build fits into how you already work. Email, a sheet, a page you open once a week. If it needs training to use, I built the wrong thing.
-
Not a discovery exercise.
No three-week audit before anything ships. The first thing we build is small enough that you can judge whether it's worth doing the next thing.
Got a thing in mind?
Tell me what it is. I read every one myself.