IThe symptom
The tell is almost always the same: somebody re-types information that already exists. A booking arrives by email and is copied into a calendar. A calendar entry is copied into a spreadsheet. The spreadsheet is copied into an invoice.
Each copy is a few minutes and an occasional error. Multiply by a year and you have the cost of the system nobody has built yet.
IIWhat a site can do
A website can present, persuade and capture. It can hold a form, send an email and rank in search. For a business whose work happens elsewhere — in a workshop, a courtroom, a kitchen — that is often genuinely enough.
It stops being enough the moment the website is where the work starts rather than where it is advertised.
IIIWhat replaces it
A system holds state. It knows which slots are free, who booked them, what was paid, what happens next, and who needs to be told. Its interface is the smaller half; the data model and the rules are the work.
In practice that means a database, authentication, an admin someone uses daily, and integrations with whatever the business already refuses to give up — the accounting tool, the payment provider, the messaging channel the customers actually use.
IVHow to decide
Count the hours the re-typing costs, and the revenue lost to the bookings that never got made because the form went unanswered overnight. Compare it to the build. If the build pays back inside a year, it is not a website decision — it is an operations decision with a website attached.