All services

Service

Web application development

A web application is software your customers or your team use in the browser: a portal, a dashboard, a quote builder, a booking or ordering tool, a place where requests are handled from start to finish. We build them around how your business actually works, in stages, with a fixed price for each stage agreed before it starts. Pricing starts at $6,000.

What you get

  • A written map of the workflow first: who does what, what the app replaces, what it has to hand to other systems
  • Interface designed for the people who will use it every day, tested with them before it is final
  • Accounts, roles and permissions where the app needs them
  • Integrations with the tools you already pay for, wired and tested through their documented APIs
  • An admin side for your team to manage what comes in
  • Installable on a phone home screen as a progressive web app, where that helps the people using it
  • You own the code, the data, the hosting account and every login

How it works

  1. 01

    Workflow map

    before any build

    We sit down with the people who will use the app and write down the job it does, step by step. That document decides the first stage, and it is yours even if we part ways there.

  2. 02

    First stage

    fixed price, fixed date

    The smallest version that does the core job for real users. You see it working in the browser as it is built, not at the end.

  3. 03

    Next stages

    one at a time

    Each further stage is scoped and priced on its own, based on what the first one showed. You can stop after any stage and keep everything built so far.

  4. 04

    Handover and care

    after each stage

    Code, access and notes on how it is built are handed over. If you want us to keep it running and updated, that is a monthly plan.

What it costs

Ranges, not a single number: the final figure is fixed in writing before we start. Responsive design and on page SEO are included, not add ons.

Web app or portal

A tool, dashboard, portal or member area. The range covers a first stage through a fuller build.

$6,000 to $18,000
Care and updates

Updates, backups, monitoring and fixes when something breaks.

$95 / month
Hosting

If you do not have hosting yet. The account can be in your name.

$25 / month

When a web app of your own is the right call

  • Your team does the same job by hand, in spreadsheets or over email, many times a day.
  • Customers keep asking questions the page could answer, such as what fits, what it costs or whether it is available.
  • Off the shelf tools cover most of the job but force your process into their shape.

When not to hire us

  • You need an app in the App Store and Google Play. We build for the browser, not native mobile apps.
  • An existing product already does the job for a monthly fee you are happy with. Building your own will cost more than that subscription for a long time, and we will say so.
  • The workflow is not settled yet and changes every week. Then the first job is to settle it, and we can help with that map before anything is built.

Questions

How much does a web application cost?
Our range is $6,000 to $18,000, and it depends on how many roles, screens and integrations the app has. We price one stage at a time, so the first number you approve covers a working first version, not a guess at the whole thing.
What is the difference between a website and a web app?
A website mostly shows information. A web app does work with the visitor: it takes input, keeps data, has accounts or roles, and returns a result. Many projects are a site with one app inside it, such as a quote builder or a fitment finder.
Can the app be installed on a phone?
Yes, as a progressive web app: it opens from the home screen and works like an app, without going through an app store. If you need a true native app in the stores, that is a different team.
Who owns the code and the data?
You do. The repository, the database, the hosting account and every login are handed over, and nothing stays locked on our side.
Can you connect it to our existing tools?
If the tool has a documented API, yes, and we test the connection before launch. If it does not, we will tell you what the options are before the scope is signed.
Can we start small?
That is how we prefer to work. The first stage does the core job for real users, and the next stages are decided by what people actually do with it.