Field Notes
Working notes from the practice. What we measure on the sites we maintain, what a template build actually costs, and why the boring option usually wins. Numbers come off our own servers, not from a vendor deck.
Mark Cuban says off the shelf software is finished. For a small business the useful question is smaller: which of your tools still fit, and who helps you replace the ones that never did?
Christian schools pay for more software than they use and face AI questions nobody on staff was hired to answer. Scripture has a name for the kind of help that fits.
From the Ottoman court to the Rosetta Stone, history keeps producing the same figure: the person who carries a great power across to ordinary life. Small businesses facing AI need that figure again.
A working checklist for owners. Five kinds of work a machine can take today, four it should stay away from, and the questions to ask before any customer data leaves the building.
A working sequence for bringing a clinic website up to WCAG 2.1 AA without a rebuild, ordered by how much risk each step removes per hour of effort.
Three separate federal rules can reach a clinic website, and the deadlines just moved. Here is which ones apply to you, what standard they point to, and where the real risk sits.
You do not need an audit tool to spot most accessibility failures on a clinic website. Here are the ten I find on nearly every first visit, and what each one costs you.
An audit of fifteen live client sites. Nine have no meta description, two have structured data, and the median site ships 93 kilobytes to deliver 331 words. What a machine can actually read, and what earns a citation now.
One site on my server takes up 1,233 megabytes. The words on it would fit in forty kilobytes. The thirteen layers of a template build, counted, and why new work is written in Go.
