Web application development

Custom web application development, built to last and easy to change

Customer portals, dashboards, booking and ordering systems, internal apps or a complete platform. We design and build web applications that load fast, work on every screen and stay easy to change when your business does. Three of our own run in production every day, so we build for the years after launch, not just for the demo.

  • One codebase for desktop, tablet and phone
  • Accounts, roles and permissions handled properly from the start
  • Hosting, monitoring and backups planned in, not added later
Twelve Lumens web app: a property with rooms grouped by type, each photo restyled in the Scandinavian style, with usage and actions in the sidebar
What we can build

What we build

From a fast marketing site to an application your whole business runs on. These are the kinds of web apps we build most.

Customer portals

A place where customers log in to follow orders or projects, download documents, update their details and help themselves, so your team answers fewer emails.

Dashboards and back offices

Screens that show what matters and let your team search, edit and act on data, designed around how they actually work.

Workflow and booking systems

Ordering, booking, planning and approval flows that replace email chains, spreadsheets and the one colleague who remembers how it all works.

Platforms and SaaS products

Applications for many customers at once, with teams, roles, subscriptions and usage limits, where every customer only sees their own data.

Live, responsive interfaces

Instant updates and live progress without a heavy JavaScript front end, so pages load fast and stay simple to maintain.

Fast marketing sites

Static or server-rendered sites with optimized images and a clean structure for search engines, like the site you're on now.

Proof, not promises

Web apps we designed, built and still run

Postcrest, Twelve Lumens and Salestreak are web applications we built and operate ourselves: an AI content and scheduling platform, an AI virtual staging app and a selling workspace with its own webshops. Between them they cover what most clients ask for: accounts and teams, payments, uploads, background processing, live progress and interfaces in several languages.

This site is a web build too: static pages served from Cloudflare's network, with every image converted to modern formats at build time.

  • Server-rendered interfaces with Hotwire: fast first loads and live updates without a separate front-end app
  • Reusable interface components, so new screens stay consistent and quick to build
  • Private files served through short-lived signed URLs
  • Two-factor login, rate limiting and automated security scans
  • Between 1,400 and 1,900 automated tests per product
Postcrest's post overview: scheduled Instagram carousels with captions, publish times, status and actions
A typical data screen in Postcrest: filters, status and actions per row (test account name blurred).
web apps of our own in production
3
interface languages in our newest apps
5
automated tests per product
1,400+
reusable UI components in one app
400+
Who it's for

Who we build web apps for

Teams running on spreadsheets

When a process lives in spreadsheets, inboxes and people's memory, a web app makes it reliable, visible and easy to hand over.

Businesses offering a customer portal

Let customers log in, follow their orders or projects and help themselves, so your service team can focus on the questions that need a person.

Startups building a product

From a first version to a growing platform, with accounts, billing and analytics in place early, so you don't have to rebuild later.

Teams stuck with a hard-to-change app

An outdated framework, no tests and one developer who knows how it works. We modernise it step by step, without a risky big-bang rewrite.

How it works

How we build your web application

We design around the work people do, then build and release in small steps you can follow.

  1. 1

    Understand the work

    Who uses it, what they do today and where it goes wrong. We map that before anyone designs a screen.

  2. 2

    Design the key flows

    Clickable designs of the screens that matter most, reviewed with the people who will use them.

  3. 3

    Build in short increments

    Working software early, on a test environment you can click through and give feedback on.

  4. 4

    Test and secure

    Automated tests, security scans and a check of every role and permission before go-live.

  5. 5

    Launch

    Existing data migrated, users invited, monitoring and error tracking switched on.

  6. 6

    Maintain and improve

    Updates, fixes and new features as your process changes, on a codebase that stays easy to change.

Technology we build with

Usually Ruby on Rails with Hotwire on PostgreSQL for applications, and Astro for fast marketing sites. Proven, well-documented tools that another team can pick up later.

  • Ruby on Rails
  • Hotwire
  • Stimulus
  • ViewComponent
  • Tailwind CSS
  • PostgreSQL
  • Solid Queue
  • Astro
  • Kamal
  • Cloudflare
  • Sentry
  • PostHog
Cost & timeline

What does a custom web application cost?

The number of screens matters less than you'd expect. These five factors move the estimate most:

Users and roles
One type of user is simple. Customers, staff and administrators with different rights need more design and more testing.
Workflows
The number of processes the app supports, and how many exceptions each of them has.
Integrations
Payments, accounting, CRM, email or external APIs each add authentication, error handling and maintenance.
Existing data
Moving data out of spreadsheets or an old system, cleanly and without losing history.
Design depth
A clean, standard interface, or a fully custom design system with its own components.
FAQ

Questions about web application development

How much does it cost to build a web application?

It depends on the number of user types, workflows and integrations, and on the data you need to bring over. After a free intro call you get a written scope and estimate, split into phases, so you know what the first version costs before we start.

How long does it take to build a web app?

That depends on the scope. We plan in phases with a clear first release and deliver in short increments, so you see working software early. The estimate after the intro call includes a timeline per phase.

What's the difference between a website and a web application?

A website mainly informs: people read pages. A web application does work: people log in, enter data, follow a process and get a result. Many projects are both, such as a marketing site with a customer portal behind it.

Will the web app work on phones?

Yes. We build responsive web apps that work in any modern browser on desktop, tablet and phone. For most business tools that's faster and simpler than separate iOS and Android apps.

Which technology do you use for web applications?

Usually Ruby on Rails with Hotwire and PostgreSQL. It's the stack behind our own products: quick to build with, reliable in production and easy for another team to maintain.

Can you take over or improve our existing web app?

Yes. We start with a review of the code, hosting and data, fix the urgent issues first and then modernise the rest step by step.

Who hosts the application?

We can host and maintain it on the same setup as our own products, with monitoring, error tracking and backups, or deploy it to your own cloud account.

Have a process that deserves its own app?

Tell us who will use it and what it should do. You'll get an honest view on scope, approach and the first version worth building.

martin@balk.dev

Typically a reply within one business day.

Useful to mention

  • What you want to build, in a few sentences
  • Who is going to use it
  • Any deadline or launch date
  • Tools and systems it should connect to