- business
- pricing
- craft
Here is the structural problem with technical work, and once you see it you cannot unsee it.
When it is done well, nothing happens.
Nothing breaks. Nobody gets locked out. The site does not go down during the launch. The payment goes through. There is no incident, no drama, no visible save. The absence of events is the entire product.
Which means the better you are, the less there is to point at.
Why this bites harder than it should
Every other kind of work leaves a mark. A room gets painted. A car gets fixed and it was making a noise before and now it is not. Even bad work is visible.
Invisible work has no before and after. The client's experience is: I paid someone, and then my week was normal.
So a predictable thing happens. The value gets estimated from the visible artifact — a few pages, a form, some text — and the visible artifact took the smallest share of the time. The parts that took the longest are precisely the parts that are now invisible because they are working.
This is not clients being cheap. It is a perception problem baked into the shape of the job.
What actually helps
Complaining about it does not work and neither does explaining it after the fact. What works is making the invisible visible while it is still happening.
- Show the broken state first. If you find something wrong during the audit, screenshot it before you fix it. The gap between those two images is the only proof you will ever have.
- Send the boring updates. "Found that the contact form has been silently failing since March" is worth more than a week of clean work nobody hears about.
- Name the thing you prevented. Not dramatically. One line: this is why logins cannot be locked out, here is what would have happened.
- Keep a list of what did not go wrong. At the end of a project it reads as a list of things you did.
Price the risk, not the hours
The deeper fix is to stop pricing the artifact.
What someone is buying is not the form. It is that the form works on a phone, that the submissions arrive, that the thing does not become a liability, and that when it breaks at an inconvenient time there is somebody who knows how it is built.
That is closer to insurance than to manufacturing, and insurance is not priced by how long the paperwork took.
The practical version: quote the outcome and the ongoing, not the build. "This will cost X and then Y a month to stay correct" is an honest description of reality, and it prices the invisible part explicitly instead of hoping someone infers it.
The one line worth keeping
If your job is making problems stop existing, you will spend your career being paid for the wrong thing unless you get deliberate about it.
Nobody is going to notice on your behalf.
← All writing