03 · Web
Web applications with a real database behind them
Free first conversation · No obligation · You own the code
You're likely in the right place if…
- 01Your spreadsheet has more rules than data.
- 02Many people edit the same data at the same time and conflicts are common.
- 03You need customers or partners to use the system, not just staff.
Sound familiar? Tell us which one on WhatsApp (opens in a new tab) and we'll suggest where to start.
What we build
- 01
Data model and backend
PostgreSQL schema, constraints and row-level security designed around your records.
- 02
Application interface
Responsive screens for each role, built for speed on real data volumes.
- 03
Integrations
Email, payments, messaging, storage and third-party APIs.
- 04
Deployment
Hosting, environments, backups and monitoring configured and documented.
How we build it
Data model first
Get the tables and relationships right and most of the application follows.
Migrate, don't restart
Existing spreadsheet data is imported and reconciled, so you launch with your history intact.
Typical stack
- Next.js
- TypeScript
- PostgreSQL
- Supabase
- Vercel
- Tailwind CSS
Questions about web applications
01What's the difference between a website and a web application?
A website mainly publishes information and collects enquiries. A web application lets signed-in users create and change data, such as orders, bookings, projects or accounts.
02Which technology do you use?
Usually Next.js and TypeScript with a PostgreSQL database (often through Supabase), hosted on Vercel. It's widely used, well documented and easy for other developers to maintain.
03Can it grow as we add users?
Yes. The database, hosting and permissions are set up to handle growth, and we explain the running costs at each stage.
04Can you work from our existing spreadsheet or prototype?
Yes. An existing sheet or prototype is often the best specification: it shows the real data and rules the application needs.
05How is the price decided?
After a short study of your process we send a written scope with fixed deliverables, timeline and price. Nothing is charged before you approve it; payment is typically 50% to start and 50% on delivery.
06Who owns the work when it's finished?
You do. Code, accounts and documentation are handed over in your name once the project is paid.
Often combined with
Next step
Ready to talk about web applications?
Share your current site or idea. We'll tell you what we'd keep, what we'd change and what the build would involve.
Free first conversation · No obligation · NDA on request