How the work gets hidden
Most of what gets sold to small organizations runs on the opposite of visible labor.
A page builder suggests the site assembled itself while you dragged boxes around. A template marketplace prices a design at $59, as though the weeks somebody spent on it evaporated at checkout. An AI tool produces a site from a paragraph of description. The pitch underneath all three is that nobody had to make this, and it holds up right until you need something changed.
The handoff test
Pull up your site and ask what happens if you hand it to a new developer tomorrow with no explanation.
Can they open the code and tell what they're looking at? Is the contact form's logic somewhere they can find it? If the honest answer is that they'd need a subscription to the tool that generated it and a month to work out what it does, then the labor didn't disappear. It got buried somewhere nobody can reach it.
I opened a Church Plant Media site last year and there wasn't a codebase to read. Sermons, events, and the contact form lived behind the vendor's templates — a new developer would need that login, not a file. Hope Presbyterian in Columbus now owns the React and Sanity rebuild instead of renting that maze.
Semantic HTML gets talked about like a purity test. It's closer to a note left for whoever opens the file next, and sometimes that person is you at 11pm before a board meeting.
The cost moves, it doesn't vanish
Someone updates the plugin that broke the checkout. Someone works out why the mobile menu stopped opening after an automatic theme update. Every spring, someone rewrites the event page from scratch because last year's layout can't be reused.
On a cheap build, that someone is usually you, or a volunteer, or a staff member whose actual job is something else entirely.
Nobody invoices for those hours. They get spent anyway. A fixed price up front doesn't make the cost smaller, it just puts it somewhere you can see it before you agree to anything.
The tools aren't what I'm arguing about
I use AI tools every day. Claude and Codex are part of how I work, and they make me faster at the parts of this job that reward speed. It would be strange to hide that in a post about honesty.
What I'm arguing against is the pretense. There's a real difference between telling a client I used good tools and I stand behind the result, and letting them believe the site arrived on its own. The second one is a bet that nobody will ever need to look at how it was built.
What I owe a client is a site I can explain and a name to call when something breaks. The name is mine, because there's nobody else here.
Three questions worth asking
If you're hiring someone to build a site, these will tell you most of what you need to know.
Who specifically does the work? Not the company, the person. If the answer keeps moving, the accountability will move with it.
What do you own when it's finished? Ask whether the site keeps working if you stop paying that vendor. Ask it plainly and listen for hedging.
Who maintains it, and what does that cost? If nobody has a straight answer, the answer is you.
Ask them of me too. I'd rather answer now than have you find out later. The whole engagement is Listen, Plan, Build, and Tend— and it's the same person at every step.
A website is work somebody did, and work somebody will keep doing. Knowing who that is turns out to be most of what you're buying.
If you're hiring help and want a checklist for the conversation, read how to find a trustworthy web partner. Already stuck in a builder and wondering what it would take to leave? See website migration. The work itself is on Services.