Aka, you are a small business. Aka, never do hourly and fixed cost projects only.
Too many people get caught up contract and deliverables and hour counting.
It sucks but you are a service worker essentially in a very high referral industry. Every project should be above and beyond with little push back. If it's unreasonable, everyone will know.
Know how to sell different processes to different people. Small ma and pa businesses are PITA but are also customers. Give them a different process than your big budget customers who always tend to be more easy going.
> Yeah I mean a general lesson here is that you want to be in the sort of business that sends one-line invoices, not the sort of business that bills by the sixth of the hour.
> Aka, you are a small business. Aka, never do hourly and fixed cost projects only.
My reading is “never charge hourly, and never charge fixed cost”. Am I misunderstanding? What is the third alternative? Retainer + hourly? Something else?
One strategy I've seen used is a fixed cost for the project (delivered to spec) combined with an hourly retainer for support and changes. Sometimes there is even an explicit carve out for changes during the development so you can avoid scope creep derailing the project (and the relationship with the client).
You don't want to get into nickel and diming the client: "why did it take X hours to set up a DNS? and what is a DNS? Do we even need a DNS?" etc.
In personal respects, I'm also not sure if I can stomach that kind of pipeline myself where I'm doing more plumbing than problem solving.
How do you manage the crons and monitor for uptime?
The first one you lose a bunch of money, the second you might break even if you are lucky, and the tenth onward you make a bunch of money.
He has a lot of friends and is well loved in his community.
What a chump.
He's a very humble guy, almost to a fault. He could easily make a killing if he hired some guys and took on traditional clients but he refuses. It's nice to know there are many people like him out there.
Maybe as a handyman I could see the good I am doing in people’s lives and that would make me happy. But as a developer I mostly do tasks to make companies more money and thus I feel some of that money is the only relevant compensation.
I am certainly not the most recognized expert in the world.
> If your tools and data are at all business critical to a real company you are vastly undercharging
I make around 90% of my revenue from flat rate prices. The hourly rates are an additional service. The majority of my clients pay quarterly flat rates. For the typical client, I only have to set up a generation script once, which takes around 30 minutes. I usually never touch that script again for years.
> [...] hardly a business achievement [...] That is a third less than a random handyman will charge where I live.
Sorry, but I really couldn't care less. I never actively planned to do this side gig. I got into it because people cold-contacted me and asked me for it. I very much enjoy doing it, I like the industry contacts it generates, it's only a few hours work each month, and it pays off my mortgage. It's mostly a paid fun hobby project.
Your approach flies in the face of that, but you don't care! I happen to love that stance and applaud your ability to recognize the enjoyment/comfort in it. You enjoy what you do, but don't seek to attempt to make it more than it currently is.
The body shops that spam me for data software contract work quote well below that.