Web apps.
Portals, registration and dashboards, built for the people who use them.
Some problems need more than pages: a place to sign in, a form people have to finish, a dashboard your staff checks every morning. We design the app around the people who use it, build it on Next.js and the systems you already run, and make it accessible from the first screen. The team that designs it builds it, then stays to look after it.
What you get
Portals
Members, students, patients or partners sign in and find what’s theirs.
Registration
Sign-ups, applications and bookings, short enough to finish on a phone.
Dashboards
The numbers your team checks every day, in one place, pulled from the systems that hold them.
Integrations
Connections to the CRM, payment, program and data systems you already run.
Go deeper
What goes into an app.
Each part has its own page. On a web app, they run together.
Modern frameworks, API development and the custom integrations that connect your systems.
Flows and interfaces prototyped and tested with the people who’ll use them, before anything is polished.
Built to WCAG and tested with assistive technology, so every person who has to use the app can.
Who it’s for
For the people who sign in every day.
We can connect registration and resident services to the systems you already run, like RecTrac.
We can build grant applications, member services and event registration.
Libraries, scholarships and universities: we can build the search, applications and accounts people sign in for.
Clear paths into patient portals like MyChart.
Age verification, memberships and storefronts.
Products and the tools behind them. We build our own, too.
How we work
Four phases, the same team.
Discovery
We watch how the work happens today — who signs in, what they need, where they get stuck — and map every system the app has to talk to.
Design
Flows and screens, prototyped and tested with the people who’ll use them before anything is polished.
Development
The team that designed it builds it, on Next.js and the systems you already run, with accessibility and security checked as we go.
Delivery
Documentation, training and monitoring, then support and improvements as the people using it ask for more.
How a project runs
It’s a loop,
not a line.
After launch we measure, learn and start again.
We don’t launch and disappear.
- Discovery
- Design
- Development
- Delivery
Launch is the start.
Related work
Louis Library.
We migrated Louis Library from WordPress to a modern Next.js environment hosted on Vercel, giving users a faster, more seamless way to discover their next great read.
Read the story →More app work
Built, shipped and still running.
Our own product: an alt text generator on Next.js and Supabase that writes descriptive alt text for every image.
A library of 297 responsive React and Tailwind blocks for P1, shipped as copy-paste components and Puck blocks with a live editor.
A cinematic Next.js launch site with age verification, the Story Society membership and a shareable storyteller hub.
Questions
If people only need to read and find things, a website. If they sign in, submit something or come back to see what’s theirs, an app. Plenty of projects are both, and one team can build both.
Usually, yes. Mapping those systems is part of discovery, and we’ll tell you early if one can’t be connected well.
We design and build to WCAG from the first screen and test with assistive technology before launch.
We do, if you want us to: hosting on SOC 2–compliant platforms, monitoring, support and improvements.
Tell us who has to use it.
Start with the people and the task. We’ll bring the questions.