Skip to content

Web applications for businesses that have outgrown the spreadsheet

We build web applications for businesses that already have customers and a process that is starting to strain. The front end is React, Next.js or Vue; the back end is Django or FastAPI on PostgreSQL. The source is yours at the end.

First release in two to four weeks, typical.

What we get asked to build

Most requests are one of these. If yours is not, the first call will tell us both quickly.

SaaS platforms

Multi-tenant applications with subscriptions, authentication and role-based access. We take on the tenancy and billing plumbing so your team works on the product.

Online stores

Custom storefronts with inventory, payment processing and order fulfilment. Headless only where the catalogue is large enough to justify it.

Customer portals

Self-service accounts that take the repeat questions off your support line. Order tracking, documents and messages in one place the customer can log into.

Internal tools

The spreadsheet your operations team has outgrown, rebuilt as software. Purpose-built screens for the three tasks people actually do all day.

What the work covers

Frontend

Interfaces in React, Next.js and Vue, typed end to end and designed small screen first, that hold up on a mid-range Android phone on a shop counter.

Backend

Server-side work in Python on Django or FastAPI, with PostgreSQL as the system of record and background jobs that can be retried.

The stack, stated plainly

Boring on purpose. Everything here is something a future team can hire for.

The stack we build web applications on, by layer
LayerTools
FrontendReact, Next.js, Vue, TypeScript, Tailwind CSS
BackendPython: Django, FastAPI. PostgreSQL as the system of record
InfrastructureGoogle Cloud, AWS, Docker, GitHub Actions

The web application we run ourselves

Polaris is a Vue front end on Django and PostgreSQL, used at shop counters every trading day, with every action behind a permission and the reports read straight off the ledger.

See Polaris

How a first release runs

There is a demo at the end of every week. If a week slips, you hear it that week.

  1. Week 1

    Discovery and wireframes

    We sit with the people who will use the thing, write down what the software has to do, and put rough screens in front of you.

  2. Week 2

    Design and frontend shell

    The visual direction lands and the real screens go up against mock data. This is the week you can still change your mind cheaply.

  3. Week 3

    Backend and integrations

    Schema, APIs and the connections to whatever you already run. The demo at the end of this week works on real records.

  4. Week 4

    Testing and launch

    Load checks, accessibility pass, deploy pipeline and handover. Then we watch the first week of live traffic with you.

What you hold at handover

If we stopped working together the day after launch, this is what you would still have.

  • The full repository, with the commit history and no vendor lock on the code
  • Technical docs, API reference and a deployment guide someone else could follow
  • A performance budget agreed up front and checked on every build
  • Structured data, meta tags and Core Web Vitals measured on real devices

Questions we get asked

Tell us which spreadsheet your team has outgrown.

A 30 minute call. We look at what you run now and what it costs you in time, and sketch what a first release would cover.

Book a call
First reply
same working day
Hours
Set to your time zone
Built in
Lahore, Pakistan
WhatsApp+92 335-0706014