Skip to content

Custom web applications

Browser-based software built around your process, such as client portals, internal tools and dashboards, estimated after an assessment and built in phases, each ending with a review.

  • Proposal after an assessment
  • One-off project
Get a quote

Software that follows how your team already works

Sounds familiar? Off-the-shelf software doesn't fit how we work, or we need a portal our customers or staff log into.

Ready-made tools stop fitting once your process has its own roles and records. A custom web application is software people sign in to from a browser, with a database and connections to your other tools built around that process. Custom software varies too much to price from a description, so an assessment or discovery comes before any estimate. Developers then build in phases. Each phase is tested and ends with a review on a private test copy of the app. The project ends with a handover of logins, files and documentation, with accounts set up for transfer to you where each provider allows.

What you get

  • Architecture plan and data model, which set how the app's information is structured and stored
  • User accounts, sign-in and permissions by role, such as admin, staff or client
  • Builds delivered in phases, each ending with a review on a test environment
  • Connections to the tools named in the scope, such as payments, email or your CRM (customer database)
  • Admin area to manage users and records
  • Automated tests for the most critical features, where agreed
  • Deployment to live hosting, with backups set up
  • Source code, setup documentation and a handover walkthrough

Is this right for you?

  • You run a core process on spreadsheets and email because standard tools don't fit it
  • You need a portal where customers, partners or staff log in to see their own records
  • You run a SaaS product (subscription software) that has outgrown its first version
  • You need an internal dashboard or workflow tool built on your own data

What it changes

Software shaped around your process

The app follows the steps your team or customers actually take. Each role sees only the records and actions that belong to it.

A build you watched take shape

Each phase ended with a review, so you saw the work running on the test environment as it grew.

Code another developer can pick up

The code is documented and built on mainstream tools. With the logins and setup notes, a new developer can continue without starting over.

Scope and delivery

How we deliver it, what we need from you, what is not included. Timeline: Estimated after an assessment

How we deliver it

  1. Assess and plan

    The technical lead reviews the scope, settles the architecture and data model, and splits the work into phases. The code repository and test environment (a private copy of the app) are set up here.

  2. Build in reviewed phases

    Features arrive phase by phase. Each phase ends with a review on the test environment.

  3. Test as you go

    Each feature is tested as it lands. Before launch, the whole app is checked for correct data handling, speed and basic security settings. A penetration test is a separate job for qualified partners.

  4. Launch with backups running

    The app goes live with backups in place. Your team gets the code, the documentation and a walkthrough.

What we need from you

  • A written scope with user flows, or time for discovery first
  • Approved designs, or a plan to design the screens first
  • A product owner, the person who makes product decisions on your side, to review each phase
  • Sample data and access to the systems the app must connect to
  • Accounts for hosting, domain and outside services, or approval to set them up

What's not included

Complex work that is estimated only after a technical or business assessment.

Not included

Where it fits

What usually follows, what may already be in place, and what is planned alongside, with the reason for each.

This service: Custom web applications

5 connected services

After this

What usually follows once this is done.

  • Ongoing development & improvement

    When the app keeps growing, a monthly capacity works through the next features.

You may already have this

Skip it if it's already in place.

Keeps it running

Keeps it working after launch.

Part of these packages

  • Digital product & MVP launch

    Build and test: The first version, or the portal or tool, is built in stages, each ending with a review, and tested before each release.

All packages

Common questions

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

A website mainly presents information. A web app lets people do things with their own data, such as log in, manage records, book or pay. That extra logic and security work is why web apps are scoped and estimated on their own.

Which technologies do you build with?

The technical lead recommends a stack, meaning the languages and frameworks, based on your features, budget and future hiring. Mainstream tools with large developer communities are the usual choice, because more developers can maintain them later.

Can you take over a half-built web app?

Start with Code review & app rescue. It checks access and code quality, then sets out whether to fix, restructure or rebuild, with an estimate for each. New build work is quoted after that.

What do we get at handover, and who runs the app after?

Logins, files and documentation are all part of the handover, with accounts set up for transfer to you where each provider allows. App support & maintenance then covers updates, monitoring and fixes. When the app keeps growing, Ongoing development & improvement works through the next features each month.

Want this scoped?

Tell us what you need and anything else the project involves.

Get a quote
Get a quote
Back to top