WEB APPS
Web Applications Built Around Your Workflow
Custom browser-based software for customer portals, dashboards, admin systems, workflow tools and business processes that need more than a normal website.
Web apps are quoted by scope. We define the users, core workflow, features, permissions, integrations and delivery boundaries before development begins.
Typical Web App Projects
- Customer portals
- Internal dashboards
- Admin systems
- Workflow tools
- Data-entry applications
- Booking/service systems
- Reporting tools
- Connected business applications
What Can a Web App Do?
A web app is useful when visitors or staff need to do more than read pages — they need to log in, manage information, complete workflows or interact with business data.
Customer Portals
Secure browser-based spaces where customers can access information, files, requests, status or services.
Dashboards
Interfaces that bring operational, reporting or management data into one usable place.
Admin Systems
Back-office applications for managing users, records, orders, content, approvals or internal operations.
Workflow Tools
Replace spreadsheets, disconnected forms and repetitive handoffs with a clearer software process.
Booking & Service Apps
Custom flows for intake, scheduling, service requests, progress tracking or customer coordination.
Data Tools
Applications for collecting, reviewing, editing, filtering or managing business data.
Common Web App Capabilities
The final feature set depends on the project. These are common building blocks, not a checklist that every application needs.
User Accounts
Authentication, profiles and account flows where the product requires user-specific access.
Roles & Permissions
Different levels of access for customers, staff, managers or administrators.
Forms & Records
Structured data entry, validation, editing and status-based workflows.
Search & Filters
Tools for finding, sorting and working with larger sets of records or content.
Dashboards & Reports
Useful summaries, status views, metrics or operational information.
Notifications
Email or in-app notifications where they support the workflow.
Payments
Payment or billing flows where the project requires them.
Integrations
Connections to APIs, email, CRM, AI services or other business systems.
File Handling
Uploads, documents, images or other file-based workflows where required.
We Start With the Core Workflow
Before building screens, we clarify what users are trying to accomplish and the steps the software needs to support.
- Who the users are
- What each user needs to do
- What information is created or changed
- Which steps need approvals or status changes
- What should happen automatically
- Which existing tools or systems must connect
The First Version Can Stay Focused
If the product has a long feature list, we can separate the essential workflow from later enhancements. This can reduce cost, shorten the first build and make the first release easier to validate.
This is especially useful for new internal tools, new customer portals and early-stage software concepts.
What We Pay Attention To
Clear Interface
Users should understand the application without needing to decode the design.
Responsive Layout
The interface should remain usable on the devices relevant to the project.
Predictable Data
Validation, statuses and records should behave consistently.
Useful Permissions
Access rules should match real user responsibilities.
Maintainable Structure
The software should be organised so future changes are not unnecessarily difficult.
Core Flow Testing
Important user journeys and functions are tested before release.
What Determines the Web App Quote?
A simple internal tool and a multi-role customer platform are both web apps, but they are not the same amount of work. The quote follows the actual scope.
Users & Roles
How many distinct user types, permissions and account flows are required.
Workflow Complexity
The number of steps, states, rules and exceptions in the core process.
Data Model
The amount and complexity of information the application needs to manage.
Integrations
Payments, APIs, email, CRM, AI services and third-party systems.
Interface Complexity
Custom dashboards, data-heavy screens and interaction requirements.
Migration & Legacy Data
Existing systems, spreadsheets or databases that need to be imported or replaced.
Scope First, Price Second
Before development begins, the written scope should make clear the main workflows, agreed features, integrations, responsibilities and quoted cost.
Building a New Web App?
We can help shape the initial workflow, decide what belongs in the first version and build a focused application around the real business need.
Already Have a Web App?
Existing applications may need new features, repairs, interface improvements, integrations or a broader rebuild. We review the current system before deciding the right route.
A Written-First Web App Workflow
Requirements, screenshots, preview links, progress updates, feedback and approvals can all be handled asynchronously in writing. Meetings are optional.
01
Share the Workflow
Explain the users, problem, current process and what the web app should improve.
02
Scope the Product
We define core features, roles, data, integrations and delivery boundaries.
03
Build in Stages
The agreed application is implemented with written updates and review points.
04
Review & Test
Core workflows, permissions, forms and important functions are checked before release.
05
Release & Improve
The agreed version is deployed or handed over, with later improvements handled separately.
Delivery Is Defined in the Scope
Repository access, deployment responsibilities, hosting/infrastructure, third-party services, credentials and handover expectations are confirmed according to the project rather than assumed.
Ongoing Web App Support
After release, SiteLumo can continue with fixes, maintenance, new features, integrations and iterative improvements when needed.
Web App Questions
What is a web app?
A web app is browser-based software where users interact with data or workflows rather than simply reading website pages. Examples include portals, dashboards, admin systems and internal tools.
How much does a web app cost?
Pricing depends on users, workflows, features, integrations, data requirements and interface complexity. We quote after clarifying the scope.
Can a web app have user accounts and permissions?
Yes. Authentication, roles and permissions can be included where the project requires them.
Can you connect payments or third-party APIs?
Yes, where technically appropriate. Payment systems, APIs, email, CRM and other services are scoped as part of the project.
Can you build an internal business tool?
Yes. Internal dashboards, admin tools and workflow systems are common web app use cases.
Can you improve an existing web app?
Yes, after reviewing the current application. The work may involve fixes, new features, integrations, interface improvements or selective rebuilding.
Do I need a full technical specification before contacting you?
No. Start with the problem, users and desired workflow. We can identify missing questions before the scope is confirmed.
Do we need meetings?
No. The normal SiteLumo process is written-first. Meetings are optional.
What should I send for a quote?
Describe the users, the main workflow, must-have features, existing systems or spreadsheets, required integrations and any examples or screenshots that help explain the idea.
Have a Web App Idea or Workflow to Improve?
Tell us who will use it, what they need to accomplish and what tools or processes you already use. We’ll reply in writing with the next questions needed to define the scope.