KEY TAKEAWAYS
Start here.
- Define the visitor's task first.
- Accounts, permissions, and workflows change scope.
- Agree on release and operating responsibilities.
Start with the visitor's task
A business website explains an offer and helps visitors enquire. A web application supports ongoing tasks with data, permissions, and workflow state. Your project can include both. Describe each journey separately: a public service page and an authenticated customer portal need different engineering and operating plans.
Compare the scope behind the screen
A dashboard mockup can hide substantial business logic. Use this comparison before requesting estimates.
| Question | Business website | Web application |
|---|---|---|
| User task | Read, compare, enquire | Create, update, transact, collaborate |
| Access | Mostly public | Accounts, roles, permissions |
| Changing information | Pages and content | Records, transactions, workflow state |
| Testing | Content, navigation, forms, devices | Plus access, data, and business logic |
| Operating owners | Content and website team | Product, engineering, support, systems |
Brief one complete journey
For example, comparing plans and requesting a demonstration needs content, a form, and reliable lead handling. Self-service billing or team administration adds application scope. For integrations, identify the data owner, access method, test environment, and approvals; investigate unknowns before committing.
- Audience: who uses the journey?
- Task: what must they complete?
- Information: which content or data, owned by whom?
- Access: public, signed-in, or role-restricted?
- Connections: which systems and available access?
- Acceptance: how will completion be demonstrated?
Choose the release and handover together
Prioritize one usable milestone over many partial features. Record who handles content, migration, analytics, integrations, and support, including exclusions and client inputs. An application also needs owners for its data and business behavior.
For a public site, define who can edit content and how enquiries reach the right team. For an application, identify support contacts and recovery steps when connected services fail. Include those responsibilities in the estimate rather than treating them as launch-day details.
Agree on hosting, accounts, repository access, documentation, updates, and incident responsibilities. Bring your priority journey, constraints, and open questions to Unanimous; we can shape a website or web application around a reviewable next step.