Web applications
From a customer portal to an internal operations dashboard, we design and build web applications that are fast, secure and easy to extend. We usually work with React and Next.js on the front end and Node.js or Python on the back end, deployed to infrastructure you control.
What is included
Customer platforms, dashboards and internal tools on a modern, well-supported stack.
- Product and UX design
- Wireframes and a clickable prototype before development, so you see the product before paying to build it.
- Front-end development
- Responsive interfaces that work on every screen size and meet accessibility basics.
- Back end and database
- APIs, sign-in, roles and permissions, and a data model designed for the next year, not just the next demo.
- Deployment and handover
- Automated deploys, staging and production environments, and documentation for whoever maintains it next.
How it works
From first call to launch.
Discovery
We map what the software must do, who uses it and what it connects to.
Scope and estimate
A written scope, milestones and cost, agreed before development starts.
Build in sprints
Two-week cycles, each ending with a working demo you can click through.
Launch and support
Deployment, monitoring, and either a clean handover or ongoing maintenance.
What a typical project looks like
A typical web application project is a customer portal, a marketplace or an internal operations tool for a seed-stage company. We usually start from a spreadsheet, a no-code prototype or a written process that has outgrown the tools behind it.
In the first two weeks we map users, roles and data, and produce a clickable prototype. The build then runs in two-week sprints: sign-in and permissions first, then the core workflow, then reporting and integrations. Most projects reach a production launch in eight to fourteen weeks, with staging, automated deploys and documentation handed over at the end.
Timeline
Typical timelines. You get a fixed written estimate after scoping, before any work starts.
- Small internal tool
- Four to six weeks.
- Customer-facing web app
- Eight to fourteen weeks.
- Ongoing development
- A monthly retainer for new features and maintenance, sized to your roadmap.
A good fit if
- You have a validated idea or an existing process that needs proper software.
- Your current setup is a patchwork of spreadsheets and no-code tools that has hit its limits.
- You need a team that owns delivery end to end, not one that waits for tickets.
Questions
Which tech stack do you use?
We default to widely used, well-documented tools such as React, Next.js, Node.js, Python and PostgreSQL. If you already have a stack, we work within it.
Do we own the code?
Yes. The repository, cloud accounts and domains sit in your name from day one, and we work inside them.
Can you take over an existing codebase?
Yes. We start with a short code review so you know what state it is in before we agree on a plan.
How much does a web application cost?
It depends on scope. The biggest drivers are the number of user roles, integrations and how complex the core workflow is. You get a fixed written estimate after scoping.
How long does it take to build a web app?
Eight to fourteen weeks for most first versions, with a working demo at the end of every two-week sprint.
Related services
Often paired with web applications.
Further reading
- Blog
How much does it cost to build an MVP?
What actually drives the cost of a startup MVP, how to estimate it before you talk to a development team, and where founders tend to overspend.
- Blog
No-code or custom build: when a prototype is enough
How to tell whether your startup should keep going on no-code tools or invest in a custom-built product.
- Guide
Web app or mobile app: which should your startup build first?
How to decide whether your startup should build a web app or a mobile app first, based on your users, your budget and what your first version has to prove.
Have something to build?
Tell us what you are working on. We will come back with questions, not a sales script.