When a business needs an application
A website tells people about your business. A web application does a job for them. Four tests separate the two: does anyone log in, does it remember anything, does money move and does the visitor take something away. Pass one and you are building an application. The full guide walks through each test and the middle ground where most businesses land.
The middle ground matters. Most businesses need a website with one working part: a calculator, a map, a booking form, a page that rebuilds from data every month. That is still a website, and we build those too. This page is for the businesses that crossed the line.
What we build them with
Flask, PostgreSQL and Google Cloud. Flask is a Python framework that gets out of the way, so an application is only as large as its job. PostgreSQL is the database behind a good share of the internet, and it has been reliable for decades. Google Cloud Run runs the application on the infrastructure Google runs its own products on, and scales to whatever comes. Stripe handles the money, so we never touch a card number.
We chose these because they are boring in the best way. They are documented, staffed and still going to be here in 10 years. The view from 15,000 feet explains the stack for people who run businesses instead of servers.
How a build runs
You feel the application before it exists. A static mockup tells you how a screen looks and nothing about what a button does when you touch it. So we build a small, temporary version early and put it in your hands while it is still cheap to change. You click through the real thing, on your phone, and tell us what is wrong.
If you already have a prototype from a chatbot or a vibecoding tool, bring it. It is the best brief we can get. We keep what works, rebuild what does not and put a real database, real accounts and real billing underneath. The process is on how we work.
Then we test it the boring way: every path a user can take, every way a form can fail, every payment state Stripe can return. Everything ships tested and accountable.
Case in point: Pathway
Every listing page tries to answer the same question and almost none of them do. What is it like to live here? Pathway turns any address into a curated, interactive neighborhood map that embeds in a listing page with one line of code. Live travel times, Street View and per-pin analytics for the agent who owns the map.
It is a product, with accounts, plans and Stripe subscriptions, running on Flask, MapLibre GL, PostgreSQL and Google Cloud Run. It does one thing, and it does it completely. That is the standard for everything we build.
What it costs to run
An application has two prices, and we show you both before you decide. The build is a fixed quote after one conversation, driven by how much the application has to do. The running cost is monthly: hosting, the database, monitoring, backups, security updates and the small changes every live product needs. It is usually modest, and it is never a surprise.
See it built
Read more
Questions people ask
Can you turn my prototype into a real product?
Yes, and it is one of our favorite jobs. Bring the thing you built in a chatbot or a vibecoding tool. We keep what works, rebuild what does not and put a real database, accounts, billing and hosting underneath it.
Who owns the code?
You do. Everything we build ships into a repository you control, on infrastructure in your name. If you ever leave, you take the whole application with you.
Do you build mobile apps?
We build web applications that work on phones, which is what most businesses need. They install to a home screen, work offline where it matters and skip the app store entirely. If a job needs a native app, we say so.
What happens after launch?
We stay on. Hosting, monitoring, backups, security updates and small changes are part of a monthly arrangement you see up front. A web application is never finished the way a brochure is, and we price it that way.