Web Apps
Web apps your team actually uses
We build web apps, client portals and internal tools that run in the browser. You get a first working piece early and a new one every week, so you can see whether it fits before you commit more.
Sample view
Three problems we fix
- 01Data lives in mail and five toolsOne place for requests, tasks and files that your team opens every day.
- 02Everyone sees a different versionOne record, one status, visible to everyone who needs it.
- 03Clients call to ask for the statusClients check progress themselves in a portal with their own login.
What we deliver
MVP & SaaS
A narrow first release that proves the workflow, then more.
Client portals
Customers log in to see orders, files and status.
Roles & permissions
Everyone sees only what they should.
Integrations
Connected to the tools and data you already use.
What do you need?
Recommended scope
Pick one answer in each question and we suggest where to start.
Standard or custom?
| Your situation | Off-the-shelf SaaS tool | Custom web app |
|---|---|---|
| One standard process, few users | EnoughSubscribe and start today. | OverkillNot worth building what already exists. |
| Your process is how you win | LimitedYou adapt to the tool, not the other way round. | Pays offThe app follows your way of working. |
| Clients need their own login and view | LimitedClient access is rarely what the tool was built for. | Pays offA portal designed around what clients need to see. |
| Data is spread over several tools | FragileEvery connection is another workaround. | Pays offOne place, connected to your sources. |
| You want to test an idea quickly | OptionalA tool can prove demand first. | OptionalA narrow first release can do the same, and stays yours. |
One standard process, few users
Off-the-shelf SaaS toolEnoughSubscribe and start today.Custom web appOverkillNot worth building what already exists.
Your process is how you win
Off-the-shelf SaaS toolLimitedYou adapt to the tool, not the other way round.Custom web appPays offThe app follows your way of working.
Clients need their own login and view
Off-the-shelf SaaS toolLimitedClient access is rarely what the tool was built for.Custom web appPays offA portal designed around what clients need to see.
Data is spread over several tools
Off-the-shelf SaaS toolFragileEvery connection is another workaround.Custom web appPays offOne place, connected to your sources.
You want to test an idea quickly
Off-the-shelf SaaS toolOptionalA tool can prove demand first.Custom web appOptionalA narrow first release can do the same, and stays yours.
Typical projects
- 01Client portal with orders, files and status
- 02Internal tool that replaces mail and spreadsheets
- 03Dashboard that brings several data sources together
- 04MVP of a new product, built in small steps
- 05Individuelle DashboardsEin Bildschirm. Jede Zahl, die zählt.→
- 06Kunden- & MitarbeiterportaleGeben Sie jedem genau das, was er sehen soll.→
From the first call to launch
- What you getA short summary of what the first release must do.What we need from youYour goals, who will use it and who decides.
- What you getA clickable version on a test address, not a mockup.What we need from youA person who can answer questions about the workflow.
- What you getNew screens and features to review every week.What we need from youFeedback within the week.
- What you getGo-live, monitoring and updates after release.What we need from youAccess to your domain and existing systems.
What it costs
Every app is priced after the intro call. These three things move the price most.
- 01Number of roles and permissions
- 02Integrations with other systems
- 03Real-time, offline and admin features
Technology & quality
- Stack
- Next.js · NestJS · PostgreSQL
- Delivery
- A working piece to review every week
Common questions
Short answers. Anything else, write to us.
Eine Website präsentiert vor allem Informationen. Eine Webanwendung ermöglicht Anmeldung, die Arbeit mit Daten und das Erledigen von Aufgaben – zum Beispiel ein Kundenportal oder ein Reporting-Dashboard.
Ja. Schnittstellen zu APIs, Datenbanken, Tabellen, Anmeldung und Benachrichtigungen planen wir von Anfang an in der Architektur ein.
Ja. Wir empfehlen ein schlankes erstes Release, das den Ablauf belegt, und erweitern danach um Rollen, Berichte oder Automatisierung.
Ihnen. Quellcode und Projektmaterial übergeben wir Ihnen zu den im Vertrag vereinbarten Bedingungen.
Sie sehen früh ein erstes funktionierendes Stück und danach jede Woche ein neues. Was ins erste Release kommt, klären wir nach dem Erstgespräch danach, was Ihr Team am meisten braucht.
Wir erweitern die Anwendung in Schritten um Rollen, Berichte oder Anbindungen oder übergeben sie an Ihr Team. Support nach dem Livegang gehört zu unserem Angebot.