About
I am Paul Milliken. I build automation and software for small service businesses, on my own, from Massachusetts.
Most of what I build is unglamorous. A form that reaches an actual person. An agent that answers at 2am and books the job. A follow-up that fires when a lead has sat untouched for a day. Two systems that never spoke to each other, now speaking.
I work spec first. Before anything gets built you get half a page saying exactly what fires and when, and you approve it. Then I build it, and you drive it yourself against real input before I call it delivered. I have shipped code that passed every test it had and still did the wrong thing on the live site. That is why the run-through happens on every release, with you watching.
Three of the systems I have built are public, and you can operate them yourself. That is deliberate. Go and use them before you decide anything about me.
01 How I work
- One person
- You are talking to the person who writes the code. No account manager, no team to hand the work off to, and no "we" when I mean me.
- Spec first
- Half a page, approved by you, before anything is built. An idea that was wrong costs you an afternoon at this stage.
- Fixed price
- Quoted from the spec. Half up front, half on delivery. Anything outside it gets written up and priced first.
- Read before shipped
- Nothing touching money, authentication or personal data goes live until a human has read it line by line. That includes anything a model wrote.
- You own it
- The build is yours. Accounts in your name, credentials yours, and you can hand the whole thing to somebody else whenever you like.
What I will tell you not to buy
If what you want already exists as a $40 a month product, I will point you at it. If the real problem is that two people in your office are not talking, software will not fix that, and I will tell you so on the call.