What this covers
Most web work we take on falls into one of these. If yours is somewhere between two of them, that is normal — say so and we will scope it properly.
- Customer portals where your clients check status, download documents, and raise requests without emailing anyone
- Internal dashboards that replace the spreadsheet three people are quietly maintaining by hand
- SaaS products with sign-up, subscription billing, usage limits, and role-based access built in from the start
- E-commerce and booking flows where a slow checkout costs you real money
- Rebuilds of applications that still work but have become too slow, too fragile, or too expensive to change
- Shared component libraries so your next three internal tools look consistent and take days rather than weeks
How we approach it
We start with the one workflow that matters most to your business and build that end to end — database through to interface — before touching anything else. You get something real to click on early, which is a far better way to find out we misunderstood a requirement than a document review.
Access control is designed in the first week, not retrofitted before launch. Every rule about who can see what is enforced on the server, so a determined visitor editing requests in their browser gets nowhere. Client-side checks exist purely to make the interface pleasant.
From there we ship in short increments to a staging environment you can reach whenever you like. Nothing merges without review, every deploy is automated, and the application is monitored from the day it goes live rather than the day something breaks.
Tools we use for this
The platforms we reach for on this kind of work. The right choice depends on what you already run, and we will tell you when your existing tooling is the better answer.
- Next.js
- React
- TypeScript
- Node.js
- Laravel
- Django
- PostgreSQL
- Supabase
- Redis
- Tailwind CSS
- Figma
- Vite
- Playwright
- ESLint
- Stripe
- Vercel
- Sentry
Common questions
How long does a web application take to build?
A focused first version — one core workflow, in production, with real users on it — is usually six to ten weeks. Larger platforms run longer, but we deliberately structure them so something useful is live early rather than everything arriving at once at the end.
Can you work with designs we already have?
Yes. Hand us Figma files and we will build to them. If you do not have designs, we can produce them, or work from your existing brand and keep the interface deliberately plain and functional — which is often the right answer for internal tools.
Can you take over an application someone else built?
Often, yes. We start with a short review of the codebase and infrastructure and tell you honestly whether it is worth continuing or worth replacing. We will tell you if the answer is replace, even though continuing would be the easier sale.
What happens after launch?
You choose. Some clients take the code and run it themselves — it is yours, documented, with no lock-in. Others keep us on a support arrangement for monitoring, updates, and new features. Both are fine; neither is assumed.
Talk to us about web applications
Tell us what you are trying to achieve and we will tell you honestly whether we are the right fit. We reply within 1 - 2 business days.
Start a conversation →