02 · Software Development
Web Applications & Portals
Secure, usable web experiences for customers, teams and partners.
What this service is
Create one secure digital front door for the tasks customers, teams or partners repeatedly need to complete.
Web applications and portals provide a structured digital route for customers, employees or partners to complete repeatable tasks without relying on email, telephone calls or disconnected forms. The work covers the visible user journey and the operational system behind it: authentication, permissions, records, status, notifications, administration and the way submitted information reaches the people responsible for action.
A successful portal does more than publish information. It reduces uncertainty for the user and prevents the organisation from creating a second manual process behind the interface. The scope therefore considers both sides of the service: what an external user can request or view, and how staff validate, respond, escalate and report on that activity.
Typical situations
When this service is usually considered.
The examples below help frame suitability. The actual requirement, risks and intended outcome are confirmed during the initial review.
- 01
Customers repeatedly contact staff to submit routine requests or ask for progress updates.
- 02
External users send documents and information through inconsistent email threads.
- 03
Staff and customers use separate records, creating synchronisation and status problems.
- 04
An existing website describes the service but does not allow users to complete meaningful tasks.
- 05
Mobile users abandon a process because forms, accounts or dashboards are difficult to use on smaller screens.
Scope of work
What the engagement may include.
Every item is selected and bounded in the written proposal. Inclusion here describes capability, not an automatic promise that all activities fit the starting price.
User journeys and information architecture
Detailed routes for registration, sign-in, requests, account activity, status checks and recovery, based on the users and tasks in scope.
Secure account and access model
Appropriate authentication, role separation, session behaviour and privacy controls for customers, staff and partner users.
Forms and self-service workflows
Structured data capture, validation, document references, confirmations and clear next steps rather than untracked free-form messages.
Staff administration workspace
A controlled internal view for reviewing submissions, managing status, responding to users and maintaining agreed content or settings.
Notifications and service updates
Agreed email or in-application messages triggered by meaningful events without exposing confidential information.
Responsive delivery and quality checks
Interfaces designed and checked for modern desktop, tablet and mobile browsers, with accessibility and performance considered in scope.
Expected outputs
Useful artefacts, decisions and working results.
The output is designed to support operation, delivery or a clearly defined next decision—not to create presentation volume without practical value.
Journey maps and functional specification
Mapped user journeys, role definitions and functional requirements for the external and internal sides of the service.
Interface system and responsive page flows
Responsive interface flows and a technical plan for accounts, records, workflow and any agreed connections.
Web application or portal implementation
A working application or portal implementing the accepted priority journeys and administration functions.
Quality checks, launch plan and support notes
Release checks, operating guidance, known limitations and a documented route for later enhancement.
Application
Common use cases.
These examples show how the service can be applied. They are illustrative and do not represent claims of completed client engagements.
Customer account portal
Give customers one place to view details, submit requests, check progress and retrieve documents relevant to their relationship.
Partner or supplier workspace
Provide controlled access to shared cases, jobs, files or actions without exposing the organisation's full internal system.
Booking and membership services
Support availability, reservations, account records, renewals and communications around a recurring customer relationship.
Employee service portal
Structure internal requests, policies, approvals and status updates for staff working across locations or departments.
Service-specific approach
How NORYVIA approaches Web Applications.
The method is adapted to the service rather than repeating one generic project formula across every requirement.
Design the complete service journey
The user interface and the staff handling process are treated as one service so a convenient front end does not create hidden manual work.
Make status understandable
Users should know what has been received, what is happening next and when human contact is required.
Protect access by role
Customer, partner and staff permissions are separated deliberately, with sensitive actions and records limited to appropriate users.
Test on the devices people use
Critical journeys are reviewed across realistic screen sizes, input methods and connection conditions rather than desktop alone.
Engagement sequence
Six stages with visible decisions.
Activities can overlap where appropriate, but each stage has a clear purpose and produces evidence for the next one.
Audience discovery
Identify user groups, priority tasks, current contact routes and the operational team handling each request.
Journey and scope definition
Agree account behaviour, pages, forms, statuses, integrations, exclusions and acceptance criteria.
Interface and system design
Develop responsive flows, data structure, permissions and staff administration behaviour.
Application build
Implement the agreed journeys and back-office functions in reviewable releases.
Usability and acceptance
Check critical tasks, devices, validation, access levels and operational handling with the client team.
Launch and handover
Release the portal, provide administration guidance and record support or improvement priorities.
Relevant capabilities
The disciplines brought into the work.
The precise technical or advisory depth depends on the accepted scope, available evidence and client environment.
User experience
- Responsive account journeys
- Accessible forms and validation
- Status and activity views
- Search and document access
- Recovery and support routes
Access and workflow
- Authentication and session controls
- Customer, partner and staff roles
- Submission review and approval
- Notifications and reminders
- Administration and configuration
Platform delivery
- API and service connections
- Privacy-aware logging
- Performance and browser checks
- Staged release environments
- Operational handover documentation
Client contribution
Information and access needed from the client.
Good delivery depends on timely, authorised access to relevant people and evidence. Missing inputs are surfaced as assumptions or constraints rather than quietly filled with guesses.
- 01
The user groups and priority tasks the portal must support.
- 02
Examples of current forms, emails, documents and status communications.
- 03
The staff process that begins after a user submits or changes information.
- 04
Identity, privacy, accessibility and integration requirements.
- 05
Content and policy material supplied in an approved form.
Scope, price and timing
A defined starting point—not a blank cheque.
The displayed price is an indicative starting guide for a bounded initial engagement. Before work begins, a written proposal confirms the selected activities, deliverables, assumptions, client responsibilities, exclusions, timetable, payment schedule and any third-party costs.
Indicative engagement shapes
Focused request or account portalTypically 5–8 weeks
Multi-journey customer platformTypically 8–14 weeks
Portal with substantial integrationsPlanned as phased delivery
Factors that may change scope, price or duration
- 01
Number and complexity of user journeys, roles and account states.
- 02
Authentication, identity verification or payment-provider requirements.
- 03
Staff administration, workflow, reporting and configuration depth.
- 04
Content migration, document handling and external system connections.
- 05
Accessibility, performance, testing and release requirements.
Scope boundaries
What is not automatically included.
Boundaries protect both parties from assumptions. A separate requirement can still be assessed and included where it is suitable and confirmed in writing.
Native mobile applications
The standard scope covers responsive browser-based delivery. Dedicated iOS or Android applications require a separate scope.
Third-party identity or payment responsibility
External providers remain responsible for their service, terms, availability and charges.
Unapproved content production
The client remains responsible for providing accurate, lawful and approved service content unless content work is expressly included.
Service FAQ
Questions about Web Applications.
Project-specific answers depend on the current environment, intended outcome and evidence available during review.
Yes where suitable access, documentation and interfaces are available. Each connection is reviewed for ownership, security, error handling and ongoing supplier dependency before it is included.
The application is designed responsively for agreed modern browsers and critical journeys are checked at relevant screen sizes. A separate native application is not included automatically.
It can be considered, but file type, size, purpose, malware protection, retention and staff access must be defined before upload functionality is accepted into scope.
Yes. The first release can establish accounts, records and workflow foundations, with later journeys added as separate, controlled releases.
Related capabilities
Other ways to move the requirement forward.
01Software Development
Custom Business Software
Purpose-built software shaped around the way your organisation actually works.
Explore service · from £2,500
03Software Development
Workflow Automation
Reduce repetitive work without losing visibility or control.
Explore service · from £1,800
04Software Development
API & System Integrations
Connect essential systems so information moves accurately and securely.
Explore service · from £1,900
Start with clarity
Start a conversation about Web Applications.
Use the structured questionnaire to explain the current situation. NORYVIA will review suitability and respond with questions or a proposed next step.