Skip to main content

Web Application Development

Applications that run in a browser and replace the spreadsheet holding your business together. Where the cost sits, and what to decide before building.

What Usually Prompts This

A spreadsheet. Almost always a spreadsheet.

One that started as a convenience, became the way something is tracked, and now several people edit it, nobody is sure which copy is current, and the business would notice within an hour if it disappeared. That is the most common origin of a web application, and it is a good reason.

The second most common is a process running across three tools with manual work between them, where the manual work has quietly become somebody’s job.

What You Get That A Spreadsheet Cannot Give You

One version. Not a file with copies.

Permissions. People see what their role requires rather than everything.

Validation at entry, so the data stays usable instead of degrading.

A record of who changed what, which matters the first time somebody asks.

Concurrent use without overwriting each other.

Somewhere to attach logic, so rules are applied consistently rather than remembered.

That list is worth having in mind because it is the actual justification. “It looks more professional” is not one, and rebuilding a spreadsheet that works fine is a way to spend money on a lateral move.

Public Or Behind A Login

This decides the architecture and it is worth settling early.

Behind a login, used repeatedly by known people, wants a fast interactive interface. One heavier initial load followed by instant navigation is the right trade, and search visibility is irrelevant because the pages are private.

Public, where strangers arrive from a search result or an ad, wants content rendered on the server so it appears immediately and can be found. A visitor who has invested nothing will not wait.

Applying one approach to both is where the expensive mistakes happen, in either direction: a marketing site nobody can find, or an internal tool that reloads the whole page when somebody changes a filter.

What Moves The Price

Number of user roles, and how differently each sees the same data.

Whether it must work offline or on poor connections. A genuine step up if people use it on site or in vehicles.

Reporting depth. Showing current state is simple. Showing trends means storing history from day one, which has to be designed in.

Integrations, and the quality of the APIs at the other end.

Whether existing data comes across, and how messy it is.

Where These Projects Go Wrong

Rebuilding the spreadsheet exactly. Including the columns that exist because of a limitation you are removing. Redesign the process while you have the chance.

Everyone gets everything. Skipping the roles conversation produces a system where nobody can be given access safely, and retrofitting permissions is one of the more painful changes.

Launching complete. The version live at month nine is always wrong in ways the version live at month three would have shown you.

No thought about mobile. If people will use it away from a desk, that changes the design rather than being a later adjustment.

Questions To Ask Whoever Builds It

  • What are you not building in version one? There should be a list.
  • How do we get our data out? Answerable on day one, not eventually.
  • Which parts are public and which are behind a login? And does the technical approach match that split.
  • What happens on a phone?
  • Who else could maintain this? The answer depends more on the technology being mainstream than on quality.

A Brief You Can Send Anyone

What we track today: [and in what, including the spreadsheets]
Who touches it: [roles, and how many people]
What goes wrong now: [the specific failure]
What each role should see: [and what they should not]
Where it is used: [desk, phone, on site]
What it must connect to: [systems, and whether they have APIs]
Existing data: [how much, how clean]
The one thing that would make this a success: [in a sentence]

How We Build Them

Laravel and React on PostgreSQL, deliberately mainstream so hiring and handover are straightforward. Server-rendered where pages need to be found, application-style behind the login.

Smallest useful version first, live with real users early, then extended by what they actually do rather than what everyone predicted.

If the requirement is broader than a single application, custom software development covers the wider decision. Get in touch and bring the spreadsheet.

Portrait of Alexander De Sousa, founder of Digital Royalty
Founder-led
“I’ve put everything I know into how this company works — the standards, the method, the care on every project. It runs through the whole team, and I hold us all to it.”

Alexander De Sousa · Founder LinkedIn

Featured on BBC Radio Solent

Get started

Tell us what you need

A few quick questions, then a straight answer from a real person — usually within a few hours.

What happens next

  1. 1 We reply A real person reads your answers and gets back to you, usually within a few hours.
  2. 2 Questions or a short call If anything isn't clear, we ask by email or book a short call. Before any call we audit your website and make the quick fixes it finds, free.
  3. 3 Your fixed quote A clear, fixed price in writing, within 48 hours of any call. There is no obligation to go ahead.

Tell us what you're working on

Whether it's a new site, a platform, or a process that shouldn't be manual any more — we'll tell you honestly if we can help.