Web applications built to be run.

We build web applications with sign-in, roles, billing and an audit trail from the first version, on a stack whose monthly cost you know before we start.

Stacked translucent layers of light seen at an angle, with one layer glowing

What it is

A website shows. An application does.

A web application is software your customers or your team sign in to: a portal, a dashboard, a booking system, a product with paid plans. Web application development services differ from building a website in one way that matters. People trust the application with their data and their money.

That changes what a first version must contain. Screens are the visible part. Who may see what, how a payment renews, and what was changed by whom are the parts that hurt when they are added later. We build those in from the start, and we run a product of our own on the same foundations.

What is inside

Six layers under every screen.

This is how an application is put together, from what people see down to what records it. Select a layer to see the rule it follows and how it exists in a product we built and run.

Screens

What it is

Customers and staff rarely need the same screens. A customer app and a staff back office are usually two applications over one set of data, so each can be simple.

The rule it follows
An application covered by the European Accessibility Act has had to meet its accessibility rules since 28 June 2025. E-commerce services are among those covered when you sell to consumers in the EU; the Act exempts micro-enterprises that provide services. This is general information, not legal advice.

European Commission, European Accessibility Act

In our own product

A customer app, a staff back office and a documentation site, kept in one codebase so they share the same data and components.

Rules quoted from each publisher’s own documentation, read on 15 November 2026. “Our own product” is a subscription service we built and operate.

Sources: European Commission, European Accessibility Act (opens in a new tab), NCSC, multi-factor authentication (opens in a new tab), PostgreSQL, row security policies (opens in a new tab), OWASP Top 10:2025 (opens in a new tab), Stripe, Strong Customer Authentication (opens in a new tab), Stripe, webhooks (opens in a new tab)

Build or buy

When to buy it instead.

Custom software is the expensive option. If a product that already exists does what you need, buy it. We would sooner tell you that than build something you could have rented.

Build it

  • The application is the product you sell.
  • Your process is the thing that sets you apart, and no tool fits it.
  • You have outgrown a tool and are paying for workarounds every month.
  • Customer data has to stay in accounts you own.

Buy it instead

  • It is something every business needs: invoicing, a CRM, a help desk.
  • An existing product covers most of it, and the rest is habit.
  • You are not yet sure the idea has customers.
  • Nobody in the business has time to own it after launch.

In detail

Roles, billing and data.

Sign-in and roles

Not everyone should see everything.

Most applications start with one kind of user and discover the second kind three months in: a manager, a support agent, an accountant. Adding roles afterwards means revisiting every screen.

We define the roles in the scope, even when version one uses only two of them, and every staff account signs in with a second step. The roles then decide what each screen shows and what each button may do.

  • Roles defined before the first screen
  • A second factor for staff
  • Customers and staff in separate applications

Billing and subscriptions

Getting paid is more than a checkout.

The first payment is the easy one. The work is in everything after it: a renewal the bank wants the customer to confirm, a failed card, a plan change in the middle of a month, a cancellation that should take effect at the end of the period.

We use Stripe for this and its hosted customer portal, where customers update their payment method, download invoices and cancel on their own. Your application listens for what Stripe reports and keeps its own records in step.

  • Plans, renewals and failed payments
  • A portal where customers help themselves
  • Your records kept in step with the payment provider

Data security

The rule lives in the database.

The usual way to protect data is to check in each screen whether the user may see it. One forgotten check and the data is out. We also write the rule into the database, where it applies to every query, whichever screen it came from.

Data protection law asks for this kind of thinking. The UK regulator’s guidance on data protection by design says you must put measures in place so that, by default, you only use the personal information necessary for your purpose. This is general information, not legal advice.

  • Access rules enforced in the database
  • Nothing is visible until a rule allows it
  • Only the data the application needs

Sources: Stripe, customer portal (opens in a new tab), Supabase, row level security (opens in a new tab), ICO, data protection by design and by default (opens in a new tab)

Version one

What a first version leaves out.

A first version ships when it is small. These are the things we advise cutting, and adding only when real users ask.

A separate mobile app

A web application that works well on a phone comes first. An app in the stores is a second project.

A setting for everything

Every option is a screen to build and a case to test. Pick the sensible default and move on.

Dashboards and reports

Start with an export. Build the report people actually open, once you know which one that is.

Every integration

Connect the one system the application cannot work without. The others can wait for demand.

More roles than you have people

Design for roles, build two. The third is added when someone needs it.

A second language

Built so it can be added, and added when there are users who need it.

Running cost

What it costs to keep running.

The build is paid once. These are the monthly bills of the stack we use, as its vendors publish them. When the accounts are in your name, you pay them directly.

Part
Database and sign-in (Supabase)
To try it
Free. A free project is paused after a week without activity.
In production
From $25 a month.
What that covers
The database, sign-in and file storage, with daily backups kept for 7 days.
Part
Hosting (Cloudflare Workers)
To try it
Free, up to 100,000 requests a day.
In production
$5 a month, with 10 million requests included.
What that covers
Running the application and its scheduled jobs.

Prices as shown on each vendor’s own pricing page on 15 November 2026, in US dollars. Usage above the included amounts is billed by the vendor, and a payment provider charges its own fee per payment. Maintenance of the application is separate.

Sources: Supabase pricing (opens in a new tab), Cloudflare Workers pricing (opens in a new tab)

How we work

Scope, ship, harden, run.

  1. 01 · Scope

    Decide what version one is

    The users, the roles, the one job the application must do well, and the list of what waits.

  2. 02 · Ship

    Get it in front of users

    A working first version with sign-in, roles and the core job, on real data.

  3. 03 · Harden

    Make it safe to rely on

    Data rules in the database, the audit trail, billing edge cases and the checks that run on every deploy.

  4. 04 · Run

    Hand over, or keep us on

    You get the documentation, and the code on full payment. Changes and upkeep are available as an optional monthly sprint.

Price

Quoted per application

We quote from the scope, fixed and agreed before we start, with the monthly running cost in the same quote. For UK clients we quote in pounds on request. See all pricing

FAQ

Questions about Web Applications

Reviewed by Chris de Gruijter,

Find out whether to build or buy.

Start with the free AI Scan, or tell us what the application should do and ask for a quote.