Web applications and portals people actually like to use.
From customer portals to the internal tools your staff use every day, we design and build web applications that are fast, accessible and secure, and that your team can keep changing long after launch.
What we build
Most web projects fall into one or more of these. Many combine two or three.
-
Customer and member portals
Secure account areas where customers apply, pay, book, track orders, download documents and manage their details without calling you.
-
Partner and supplier portals
Shared workspaces for partners, suppliers and agents, with the right access for each organization and a clear record of what was exchanged.
-
Internal tools and back offices
Tools that replace spreadsheets, email chains and paper forms: approvals, case management, scheduling, inventory and reporting, built around how your team works.
-
Dashboards and reporting
Live views of the numbers that matter, with filters, exports and alerts, drawn from the systems you already run.
-
Online services and applications
Public-facing forms and services, such as applications, registrations and bookings, that work on any device and for people using assistive technology.
-
Marketplaces and booking platforms
Listings, search, availability, payments and messaging, between buyers and sellers or between your customers and your staff.
-
SaaS products
Multi-tenant platforms with sign-up, subscriptions, roles and an admin area, ready to grow from your first customers to many more.
-
Modernizing older web systems
We move ageing applications onto supported frameworks step by step, so your service keeps running while the work happens.
What goes into every web application we build
-
Accessible to everyone
Built to WCAG 2.2 AA, with real buttons, labels and keyboard support, and checked with automated tests and by hand.
-
Fast on any device
Pages that load quickly on phones and slow connections, with performance measured before every launch.
-
Secure by default
Careful sign-in and roles, protection against common web attacks, and code, dependency and container scanning on every release.
-
Sign-in that fits your users
Email and password, single sign-on with your identity provider, or two-factor authentication, depending on who your users are.
-
Easy to change
Clean, tested code and a library of reusable components, so new features do not break old ones.
-
Monitored from day one
Error tracking and uptime monitoring switched on at launch, so problems are found and fixed quickly.
Technology we use
We'll suggest the simplest set of tools that does the job, and that your own team can live with after we're done.
Front end
- React
- Next.js
- Vue.js
- TypeScript
Back end
- Node.js
- Python
- REST APIs and webhooks
Data
- PostgreSQL
Cloud
- AWS
- Azure
- Google Cloud
What you get
Everything your team needs to run it, change it and understand it.
- A working web application, released to your users
- Source code with automated tests that run on every change
- A library of reusable components for future features
- A delivery pipeline that builds, checks and releases each change
- Infrastructure defined as code, so environments can be rebuilt
- Documentation and a runbook for your team
How a project runs
Nothing starts without your sign-off, and you'll see working software every two weeks.
- 1
A free call
Thirty minutes to talk through what you need. If we're not the right fit, we'll say so.
- 2
Discovery
A few short workshops to agree goals, users, constraints and what success looks like.
- 3
Design
Screens you can click through and test with real users before we write any code.
- 4
Build
Two-week sprints. Each one ends with a demo of working software you can try and comment on.
- 5
Launch
Automated tests, security checks and a go-live plan with a way back if something goes wrong.
- 6
Looking after it
Your system moves onto a Managed Services retainer, supported by the people who built it.
What happens after launch?
You can keep us on to look after it. The people who wrote the code are the ones who keep it running, so nothing gets lost in a handover.
Common questions
- Can you improve the web application we already have?
- Yes. We start with a short review of the code, the hosting and how people use it today, then suggest whether to improve what you have or rebuild parts of it.
- Will it work on phones and tablets?
- Yes. Everything we build works on phones, tablets and desktops, and we test at each size before launch.
- Can our own developers work on it later?
- Yes. We use widely supported tools, write tests and documentation, and hand over cleanly, so your own team can take it on.
- How do you charge?
- Build work is billed by the hour against an estimate we agree before we start, and you see hours and progress every sprint. Looking after a live system is a monthly or yearly retainer.
- Where do we start?
- With a free 30-minute call. If we're not the right fit, we'll tell you. If we are, we agree goals and an estimate before any work begins.
Tell us what you're working on
The first call is free and there's no sales pitch. We reply within 24 hours.