Essential
Focused delivery
One journey with up to 5 screens.
Price confirmed after discovery
Discuss EssentialDigital Product & Web Solutions
Mobile Application UX & Prototype
Explore a mobile-first service journey with an interactive prototype.
Discovery & prototype first · Quotation-based
Who this is for
A defined brief. A usable output.
Teams testing a mobile concept before selecting a production platform.
Included in the agreed delivery
- Mobile task map and screen hierarchy
- Responsive or clickable prototype
- Error, offline and notification specifications
- Platform decision brief and development handover
Scope options
Start with the right level of work.
These are starting scope configurations, not instant purchases. The selected option is checked against your requirements and confirmed in a statement of work.
Professional
Broader business scope
Up to 3 journeys and 12 screens with component guidance.
Price confirmed after discovery
Discuss ProfessionalExtended
Expanded requirements
Discovery for a pilot with up to 20 screens; production estimate separate.
Price confirmed after discovery
Discuss ExtendedWhat we need from you
- Device and audience priorities
- Approved task rules and content
- Notification and account requirements
Nominate one approver and provide consolidated feedback. Delays in content, access or decisions can change the schedule. Share credentials only through an approved secure process.
Outside the baseline scope
- App-store submission and native production build
- Real push notifications or background services
- Hardware integrations without review
Any additional work, subscription, licensed asset or third-party service must be itemized and approved before commitment.
From first brief to handover
01
Discover
Confirm the audience, purpose, source material, platform, owner and desired outcome. Identify anything that requires further capability or risk review.
02
Agree
Select a scope option and issue a written proposal covering quantities, exclusions, schedule, fees, dependencies, ownership and acceptance.
03
Create
Prepare the first agreed output in a controlled workspace. Keep approved content and creative or technical decisions traceable.
04
Review
Collect one consolidated feedback list from the nominated approver. Complete the agreed correction rounds and log any new scope.
05
Accept & hand over
Review the acceptance checklist, deliver the contracted formats, explain how to use or maintain them and record sign-off.
Acceptance criteria
Know what completion means.
- Primary journey can be completed in prototype
- Touch targets and labels are reviewed
- Offline and failure behavior specified
- Platform risks and next steps documented
Files, ownership & aftercare
Your proposal identifies final exports, editable source files, repositories, account ownership and any licensed components. Third-party assets remain subject to their licenses. Agree ownership and usage rights in writing before work begins.
Handover includes the contracted outputs and relevant operating notes. A defect-correction window, maintenance allowance, support hours and response targets are specified in the agreement; ongoing support is included only when expressly scoped.
See the work
PocketService Co • Service Request Prototype
A local mobile-format demonstration for choosing a service and reviewing a synthetic request. No request is sent.
VSPO-authored demonstration based on VSPA-SIM-017. Fictional organization and synthetic data; not client work or an assessed learner submission. The sample is representative, not every deliverable in the package.