Websites and products
When is a website not enough?
Direct answer
A website is not enough when the questions after the enquiry — what is my status, what is still missing, is this available, which version did you send — are answered by a person searching an inbox. The site can still be the front door, but the work behind it needs a record. Building a larger brochure does not create that record.
The inbox has become the application
You can see it in the questions staff answer all day. A patient asks what to bring. A client asks whether the papers arrived. A buyer asks if the configuration on the website is the one the sales team will stand behind. A guest orders from a PDF that was wrong by Thursday. Each answer is assembled by hand from a chat, a sheet and a memory.
A redesign can make the front door clearer, and often should. It does not give two colleagues the same list. If the pain continues after the page is beautiful, the pain was never the page.
Signs the website has done its job and the system has not started
The same facts are maintained twice, once for the public and once for the team, and they drift. Status is a sentence someone types, not a state the record holds. A new staff member cannot see the work without asking the person who received the original message. Walk-ins, exceptions and “just this once” never make it back to the page or the sheet.
None of these require a large product on day one. They require a record the website can create, and that the team will agree to use. The industry pages for clinics, cafes, real estate and coaching describe what that record tends to be.
What the website should still do
Explain who the work is for, answer the questions that block a first contact, and hand the person into the record: a booking request, an upload link, a visit request, an application with a reference number. Performance, clear language and a page that works on a phone still matter, because that is how the record gets its first honest input.
Keep public pages and private records apart. The website can invite a document. It should not be the place the document is stored for the whole firm to browse. That split is both a privacy choice and an operational one.
How to sequence the work
If strangers cannot understand the offer, fix the website first. If they understand it and the team then loses them in a chat thread, build the record next and let the site feed it. Doing both in one undifferentiated project is how a marketing site acquires a login nobody wanted, or an internal tool launches with no public explanation.
Sunbeam scopes these as related and distinct. The comparison of a website and a web application is the short form. This guide is the operational form: look at where the answer is currently being typed.