Web applications
Customer portals, dashboards, booking and ordering systems, internal tools. Fast, accessible, and built to be maintained by whoever comes after us.
- Kind
- Build
- Timeline
- 2 to 8 weeks

What this is
A web application is anything your customers or staff log into and use to get work done: a customer portal, an admin panel, a booking system, an ordering flow, a dashboard over your data. It is not a brochure site, and it is not a template with your logo on it.
You choose the technology, or fit it to what you already run. If you have no preference, we propose mainstream, well-documented tools that are cheap to host and easy for the next developer to pick up.
What you get
- A production application on your own domain and your own hosting account.
- A separate test address where every change lands first, so you can click through before it goes live.
- Authentication that fits your situation: email links, passwords with proper hashing, or single sign-on with the identity provider you already have.
- Role-based access, audit logs where money or personal data is involved, and plain-language error messages. Nobody should ever see a stack trace.
- A repository you own, with a README that a new developer can start from in an afternoon.
Typical scope
A first version is usually one clear job done well. Examples we would call one scope:
- A portal where customers see their orders, invoices and tickets, with login and a contact form that reaches the right person.
- An internal dashboard that replaces three spreadsheets, with imports from the systems the spreadsheets came from.
- A booking flow with calendar, payment and confirmation emails.
Anything bigger is two scopes, delivered in order, each one usable on its own.
Timeline
Two to eight weeks from kickoff for a first version, depending on how many screens and integrations the scope has. You see a working test address within the first week, every week after that.
Good fit if
- You can describe the one job the application must do.
- Someone on your side can test and answer questions within a day or two.
- You want to own the result, not rent it.
Not a fit if
- You need a marketing website. That is a smaller, different job, and we will say so.
- The requirement is "like X but for us" with nothing more. We will help you write the brief first, but we will not start building on that sentence.
Related
- Backend systems and APIs for when the web app is the visible part of a bigger system.
- Hosting on your accounts for how ownership works.
- Security practices for how we handle logins, data and secrets.