Service guides / Web & mobile apps
Scope & boundaries · Web & mobile appsBusiness service websites: scope & boundaries
Define the outcome before requesting a price. Start with service descriptions and approved brand assets and plan a responsive service-to-enquiry journey.
Available remotely for local and international enquiries. Platform choice and final scope depend on your requirements.
The project in view
- Start with
- service descriptions and approved brand assets.
- Proposed result
- a responsive service-to-enquiry journey.
- A decision to resolve
- unclear calls to action and inaccessible forms.
This is a planning example. It does not describe a completed client engagement.
Scope & boundaries for this project
- Choose devices and the main user task first. Decide whether browser access, offline work or device features are required.
- Use “a responsive service-to-enquiry journey” as the proposed deliverable; confirm what is included in that description.
- Resolve this boundary early: unclear calls to action and inaccessible forms.
Questions to answer together
- Who uses the result, and what decision does it support?
- Which part of the current process is included?
- Which exceptions and adjacent tasks are excluded?
What to have at the end
A bounded scope with an owner, an intended result and explicit exclusions.
Record the decision on unclear calls to action and inaccessible forms alongside the source material. If it is still unresolved, identify who can answer it and what work depends on the answer.
Prepare your enquiry
Use this as a starting point. Add your current process, available examples and constraints before sharing.
Send your completed brief to hello@iansamonte.com or visit the main page to discuss your project.