Start with one workflow
The one process that hurts – quotes, scheduling, intake, reporting – becomes a focused tool first.
Internal tools, customer portals, booking systems and dashboards: real software built with Python and Django, scoped as a first working version, replacing the spreadsheets and email chains your team has outgrown.
The one process that hurts – quotes, scheduling, intake, reporting – becomes a focused tool first.
Python and Django on PostgreSQL, hosted in Germany. Standard parts, not experiments.
A fixed price for a first working version and a roadmap for what comes after.
A web app is software that runs in the browser: your team logs in, works with data, and nothing needs installing. Custom software is the wider term – anything built for your process rather than bought off the shelf. In practice the two are the same project: a Django application, hosted on a server in Germany, that replaces a spreadsheet, an email chain or a tool that almost fits. If you can describe the workflow, we can build the tool for it.
Internal tools that replace Excel workflows – quote calculators, scheduling, order intake, stock lists that three people edit at once. Customer and partner portals where clients see their orders, documents or appointments. Booking and scheduling systems. Dashboards and reporting on data you already have in DATEV, Lexoffice, your ERP or a CSV. Admin back ends for existing websites and shops. The common thread: a process the business runs every day that software should carry instead of people.
What a first version costs depends on the scope of the workflow and the integrations – without a scope a starting price says nothing, with one we quote it as a fixed price. We scope a first working version around the one workflow that hurts most, quote it at a fixed price, and build it in eight to sixteen weeks – then grow it from real usage instead of a sixty-page specification. The website costs page puts that next to our other formats.
What makes custom software expensive is not the code; it is unclear requirements and integrations nobody checked. We check both in the scoping week, before you commit.
Python and Django on PostgreSQL, a clean HTML front end (HTMX where interactivity is needed, a JavaScript front end only when it really pays off), hosted on German or EU servers – Hetzner by default, or your own infrastructure. Authentication, roles, audit logs, exports, e-mail, REST APIs, integrations with DATEV, Lexoffice, HubSpot or Stripe: standard parts we have built before. The Django page explains why this stack, and what happens when you already have a Django app that needs rescuing.
Tests, documentation, a deployment you can run without us, and the code in your repository from day one. Whether you keep us on for ongoing development, bring in your own team later, or hand the project to another agency, the code base stays readable and yours. Maintenance is a monthly care plan or hourly, your choice – there is no licence and no lock-in. For local clients the Freiburg page describes how we run a project in person.