We build web apps and SaaS products.
And we keep them running.
The software behind your login: web applications, internal tools and SaaS products, built by senior developers and kept running after launch.
Trusted by
Trusted by
The problem
You have something to build behind a login and the quotes come back starting at a number you were not planning to spend.
Anything behind a login gets quoted as a different and far more expensive category of work.
The proposals come back starting above what the build is actually worth to you.
Writing the code is one job. Running the thing afterwards is a different one, and it is the one people learn late.
Hiring a developer for a build that lasts a few months is a commitment that lasts a lot longer.
The build stops whenever the person doing it is busy with somebody else's work.
The Reality
Work like this is senior people-time, usually sold as a project wrapped around it. A month of build time, priced as a month, is easier to buy and easier to stop.
The Model
We shape the work. Then we build it.
We run Shape Up, the method 37signals published: work is shaped before it starts, given an appetite rather than an estimate, and built inside a fixed cycle. Ours is the month. The shaping happens inside that month, as part of the work, so there is no separate proposal phase to buy before anything gets built and no hours to track. You decide what gets built and in what order, and you see where it stands every week.
The reason these numbers work is how the building is done. AI does a lot of the typing, and there is a human in the loop: a person checks the work after every significant step and before anything ships. That is what keeps a build like this inside one person's reach, and it is the whole reason a product builder is affordable without an agency budget behind you.
How It Works
How a month runs
We get into your setup
Repositories, hosting, domains, the accounts and whatever exists already, including the prototype if you have one. Usually done inside the first week.
You get a board
One place where you put what you want built. You add to it whenever something comes up and you set the order. Nothing is estimated into a proposal first.
We build, month after month
Work moves across the board and you see each piece as it lands. A person reviews every significant step before it ships. If you stop, the running product, the code and the accounts are already yours and nothing about the setup depends on us.
What You Get
An application in production, the repository and every account in your name, and people who have run this stack in production for years. If you turn up with a prototype you built yourself, that is a good place to start and we like getting them.
Proof
Things we built and still run
Glasswise
Our own SaaS. Wineries selling into the EU have to publish ingredients and nutrition data under Regulation (EU) 2021/2117. Glasswise keeps one record per wine and publishes it as a branded multilingual e-label behind the QR code on the bottle. Next.js, Hasura and PostgreSQL on Nhost, with authentication, roles and subscription billing. We built it, we run it, and we answer the support mail. glasswise.eu
staticsites.eu
Also ours. Hand over a GitHub repository or a folder of built files and it goes live on your own domain with https handled. Every vendor in the stack is European, and the whole feature set is exposed over MCP, so a coding agent can deploy without opening a dashboard. staticsites.eu
SunRocks
An Austrian electronics insurance provider, running on a platform we have managed for years: a customer portal, a partner portal and a back office on Hasura and PostgreSQL, with queue workers for mail and document generation. The stack story is written up in our post on customer portals.
ThirtySix Degrees
A sustainability consultancy in Vienna. We built their internal tool for time tracking and invoicing, used by a team of consultants.
Pricing
You are paying for senior build time and for somebody who has taken a product all the way into production and kept it running.
The difference between the two numbers is how much of the month is yours.
Part of the month on your product. It fits an application that is already live or close to it: changes, fixes, a feature at a time, one integration after another, and somebody who knows the system when it breaks at an awkward hour.
Month to month, no long-term contract
Cancel or pause with 30 days notice
Part of the month on your product
Changes, fixes and features, one integration at a time
Repository, hosting and accounts in your name
The whole month on your build. This is the number for getting from nothing, or from the prototype you built yourself, to an application running in production, with several parts of the build moving at once.
The whole month on your build
Month to month, cancel or pause with 30 days notice
Frontend, backend, integrations and deployment
A person reviews every significant step before it ships
Repository, hosting and accounts in your name
All prices are net, excluding applicable VAT.
Who This Is For
Who this is for
A good fit if you
Have a web app, an internal tool or a SaaS product to build and one person who can make decisions
Want shaping and building in the same cycle instead of a proposal phase you pay for before anything gets built
Built a prototype yourself and want a production version of it
Need somebody to keep running it after launch, or want to be able to take it elsewhere
Not a fit if you
Are a marketing team moving off a legacy CMS. That is a Headless Migration
Want ongoing marketing engineering rather than product work. See Fractional Marketing Engineer
Are an agency that needs a website delivered under your own brand. See White-Label Web Development
Need a marketing website rather than an application. See Headless Website