A website isn't a purchase. It's an operation.

Most businesses buy a website the way they buy signage. It’s a project: a scope, an invoice, a launch, a round of congratulations. Then it sits. The average small-business website is a photograph of the company as it was the year it launched — the services offered then, the prices quoted then, the pride of whoever approved it, preserved.

That model used to be rational. A website was a brochure; changing it was slow and expensive, and nothing about it was measurable, so no one could tell whether changing it mattered. If a thing can’t be measured and can’t be cheaply changed, treating it as a one-time capital purchase is exactly right. That’s how you buy a sign.

Then the job changed underneath the purchase. For a growing business, the website stopped being a brochure and started doing work every day: getting found, answering the questions a customer asks before they’re willing to call, and asking for the business. And at the same time, the economics around it became software economics — a change ships in minutes, and what visitors do can be recorded, event by event.

In other words: the website became software. The way businesses buy it didn’t. Most of what’s wrong with my industry lives in that gap.

Software is operated. Anyone who has bought a CRM and watched it turn into shelfware knows the corollary firsthand: a system that does a daily job has its value in the operating — watching what it does, fixing what underperforms, improving what already works — and without the operating, it’s a license fee. The moment a website took on a daily job, it crossed the same line. It just kept its old price tag format, so nobody noticed.

None of this makes the build matter less. The build is where you decide what can be true later: whether the structure matches how customers search, whether the measurement is wired in from the first day, whether the thing is fast and legible on the phone in a customer’s hand. Get the foundation wrong and everything after is capped.

The alternative to operating is one everyone in business has lived through: the rebuild cycle. Every three or four years, the site is embarrassing again, so you commission the big redo. Rebuilding buys the new site and forfeits, invisibly, everything the old one never got the chance to learn. An operated site runs the opposite loop — small changes, chosen from evidence, kept when they work, reversed when they don’t. It compounds. The rebuilt site starts over; the operated site gets better.

This is the model Pruvara runs, and it’s the reason the company is shaped the way it is: build the foundation once, properly — then operate it like the software it is, the measurement always on, changes made from what it shows.

A sign is finished the day it’s hung. A website is just getting started.