Some briefs arrive looking like a website and turn out to be an application. Agencies that spot that early win; agencies that spot it halfway through do not.
The distinction matters commercially more than technically. A website shows content; an application processes a workflow, calculates something, holds records people act on, or enforces who may do what. The moment the second description fits, a CMS becomes something you fight.
The expensive version is finding this out after quoting. A brief described as "a site with a members area" turns into permissions, data models, state and an audit trail — and the price agreed at the start no longer covers it.
We would rather help you tell the difference before you quote. Sometimes the answer is that it is genuinely a website with a login and the simple approach is right. When it is not, better to know while the client conversation is still open.
Where signed-in users see their own data — documents, orders, history — pulled from systems that already hold it.
The quoting, scheduling or tracking system currently run as a spreadsheet only one person fully understands.
Capacity, availability and the awkward cases: cancellations, changes, overlapping resources.
Bringing numbers together from several systems into something a non-technical person can act on.
Services other software consumes, documented and versioned so changing them later does not break everybody.
Multi-step processes with states, permissions and a record of who did what.
The scale you set, not approximated. If a typeface cannot be licensed for web we tell you before the build rather than substituting it.
A layout that breaks at 900px, an interaction that will be painful on a phone. You hear about it while it is still cheap to change.
Designs rarely cover every width. Rather than invent the in-between states we agree them with you.
So your client can update content without the design falling apart, which is what protects your work after handover.
No credit in the footer, nothing in the code, nothing in the documentation. Your client sees your agency.
A fixed price on an application brief nobody has mapped is a guess. We would rather do a short paid discovery than watch you absorb the difference.
Custom applications have no automatic updates. Framework and dependency upkeep is real and should be in the proposal.
If the brief is mostly content with a login, say so and keep it simple. We will tell you when that is the case.
Some effects cost ten times what they look like they should. We will tell you the price rather than absorb it or drop it silently.
Contrast below AA, or an interaction that cannot be used by keyboard. We will say so, and propose an alternative that keeps the intent.
We will tell you whether it is a website or an application, roughly what it would cost, and what needs pinning down with the client first.