brochure site or web app? the question behind the quote
business · 2026-10-22 · 4 min
"we need an app" is one of the most expensive sentences in a first meeting. sometimes it is true. often it means "the website is confusing and we think software will fix it".
the honest distinction
a brochure site (sito vetrina) publishes: who you are, what you sell, how to contact you. it is read. it can have a form, a map, a gallery, a price list. its job is to turn a search into a phone call.
a web app does something for the user: it stores their data, applies rules, returns a result. a booking system, a customer portal, an online course, a quote calculator, a dashboard. its job is to replace a manual process.
the difference is not the number of pages or the design. it is whether the site has state: something that persists between visits, belongs to a specific user, and changes what the next person sees.
the three signs you need an app
- people log in, or should be able to see something different from everyone else.
- the site must remember something across sessions: an order, a booking, a progress, a document.
- a manual process is consuming hours every week and the rules are stable enough to automate.
if none of the three is true, an app is a website with extra cost and extra failure modes.
what a brochure site can do that people forget
a well-built brochure site with a form, a calendar link and a clear offer handles most local businesses. the booking can live in an external tool; the payment can be a link; the quote can be a form that sends an email. you do not need to own the software to use it.
the trap is calling this "just a website" and buying a template that cannot be extended. the other trap is calling it "an app" and paying for custom software that reproduces a calendar.
cost and time, honestly
a brochure site: 1,500-3,500 euro and four to eight weeks. a small app: from 8,000 and two to four months. the gap is not the code; it is the states, the testing, the maintenance and the fact that software has to keep working when you are on holiday.
the question to ask before choosing
"what does the visitor do that a piece of paper could not?" if the answer is "read, trust, call", you need a brochure site. if the answer is "log in and see their order", you need an app. if the answer is "nothing yet", you need a clearer offer before either.
what a web app costs goes deeper on the numbers. for the brochure side in parma, website design and development in parma.
faq
what is the difference between a brochure site and a web app?
a brochure site publishes information and asks for contact. a web app stores state and does something for the user: accounts, bookings, orders, calculations. the difference is state, not design.
do i need an app for online bookings?
usually not. a calendar tool embedded in a good website handles bookings, payments and reminders. build an app when the booking rules are yours and no tool fits them.
can a brochure site grow into an app later?
yes, if it was built with that door open: a real codebase you own, a database, no page builder that cannot be extended. ask about this before signing.