Skip to content

Web app development · portals, platforms & tools

Web apps that make work simpler.

Turn a process spread across emails and spreadsheets into a browser-based product. Dialedbase designs and develops web apps for customers and teams, with a defined first release and a clear plan for what comes next.

See pricing and inclusions

Best for

Customer portals, booking platforms, SaaS products and internal tools used through a browser.

Investment

A fixed quote for the agreed first release. Priced around workflows, roles, data and integrations.

Delivery

Milestones agreed after discovery; complexity and third-party dependencies determine the schedule.

A useful first release

Give people a better way to get a task done.

For example, a customer portal could let a customer sign in, submit a request and check its progress while your team manages updates. We would scope that complete workflow first, then decide which extra features belong in a later release.

Your agreed deliverables

  • User journeys, roles and a prioritised first-release feature list
  • Interface design and responsive web development
  • Accounts, permissions and data storage specified in your proposal
  • Agreed integrations, validation and loading and error states
  • Testing of core workflows, deployment and source-code handover

Payments, data imports, reporting, admin tools and external APIs are scoped individually. Hosting, email delivery, API usage and other paid services are separate from the build fee.

Customer portals and shared workflows

A customer portal can bring requests, documents and progress updates into one place. Internal tools can help teams manage work without passing spreadsheets between people. We define each role, the information it can see and the actions it can take before building screens.

Integrations with a purpose

If your product needs bookings, payments, email or an external system, we review the provider and the data flow during discovery. Your scope identifies API access, costs, error handling and which service is responsible for each step. Existing data imports and complex integrations are quoted explicitly.

Design for more than the happy path

A working app needs validation, useful empty states and clear feedback when an action fails. We agree the core acceptance criteria and check the relevant account, permission and workflow paths before deployment. Performance and security requirements are scoped to the product and its data.

Ownership and ongoing operation

Handover includes the agreed source code and access information. We identify who manages hosting, data backups and external services after launch. Builds include 30 days of fixes for defects in the agreed scope. Optional App Development Support is priced separately from the initial build.

From brief to handover

  1. 01

    Map the workflow

    Define who uses the product, what they need to do and which information each role can access.

  2. 02

    Build the core release

    Start with the smallest useful end-to-end workflow. Review working screens against agreed acceptance criteria.

  3. 03

    Launch and learn

    Test the core journeys, hand over access and documentation, and prioritise later features using real feedback.

Questions before you start

What is the difference between a website and a web app?

A website mainly explains your business and helps people contact you. A web app lets users perform tasks, often with accounts, stored data and workflows. If you only need service pages and an enquiry form, a standard website may be the right scope.

Does a web app also work on a phone?

We design responsive browser layouts for the devices in your scope. An installable iOS or Android app is a separate platform decision; it is not automatically included in a web app build.

How much does a custom web app cost?

We provide a fixed quote after defining the first-release workflows, roles, data and integrations. There is no universal app-build price. Hosting and paid-service usage are separate.

Can we start small and add features?

Yes. We can scope a useful first release and prioritise additional features later. New features are separately agreed rather than assumed to be part of the original build.

How long will the project take?

We confirm a milestone schedule in the written proposal after reviewing the scope, available content and integrations. Delayed content or feedback can move the schedule. Mobile release plans also need to allow for Apple or Google review.

What happens after launch?

Builds include 30 days of fixes for defects in the agreed scope. New features are separate work. You can choose optional ongoing support, with responsibilities for hosting, third-party services and maintenance confirmed at handover.

Bring the problem. We’ll work out the scope.

Tell Rhys who will use it, what they need to do and any budget or launch date you have in mind. We’ll discuss a sensible first release and the information needed for a written quote.

Free 30-minute call · choose a time directly · no project commitment