A request portal: what can be included
A customer submits a request and follows its status. Your team assigns it, asks for missing information and records completion. The first release can focus on this journey before adding invoicing or a complete business management system.
- Client area: submit and review their own requests.
- Team area: lists, filters, assignment and status updates.
- Shared rules: access, required information and completion criteria.
- Attachments, emails and integrations: separate items to agree in the quote.
Interface, backend and access
A clickable screen is a prototype. An operational service also needs rules, persistent data, error handling and, where required, accounts and permissions. These are separate parts of the scope.
For each role, we define what users may see and change. Missing data, duplicates, expired sessions and interrupted operations need explicit behaviour. Integrations depend on the capabilities and terms of external systems.
Web app, PWA or mobile application
A web app is accessed through an address and can adapt to phones and computers. A PWA can add installation and offline behaviour, subject to target device capabilities. Naming a project PWA does not automatically make it work offline.
If specific device capabilities or store distribution are central, dedicated mobile development may be appropriate. Publication, developer accounts, notifications and maintenance should be included explicitly.
Delivery and acceptance
Acceptance describes observable outcomes: a saved request remains after signing in again, one user cannot access another user’s records, or an export has the agreed columns. These examples become project checks.
- A first version covering the main workflow and roles.
- Normal paths, errors and permission checks.
- Environment configuration, publication and recovery instructions.
- Source code and documentation, with maintenance and external costs separated.
What determines the scope
Rules, roles, data and integrations often determine more work than screen count. A simple-looking dashboard may involve complex processing. Complete applications receive tailored quotes, separate from the EUR 790 First Result task package.
Describe users, frequency, devices, starting data and existing systems. Do not include passwords or real customer records in an initial enquiry; a description and synthetic example are enough.
Explore an example
ServiceBot demonstrates guided request collection using synthetic data. Explore the interaction in your browser: this is not a client portal with production accounts and a backend.
Try the request collection demo ↗Prepare your project brief
A reusable text template: objectives, users, features, materials and acceptance checks. Download it without registration and edit it with your team.
Download the project brief (.txt) ↓