All services

Custom software for businesses

Custom web application development for processes that off-the-shelf software cannot handle

We build internal tools, operational platforms and SaaS products for companies whose processes do not fit into standard software. You speak directly with the two founders who design your application and write the code themselves. The code belongs to you, is documented and can be handed over to another team.

  • Built by the founders
  • You own the code
  • Internal tools to SaaS

Typical starting points

Where spreadsheets, inboxes and standard software hit their limits

Custom software is not an end in itself. It pays off where a core process carries your business and your current tools can only handle it through detours.

01

Your core process lives in Excel files

Quotes, schedules and approvals run through spreadsheets that circulate by email. Often only one person knows which version is current, and every report starts with copying data together.

02

Standard software is bent into shape

The tool you bought covers the standard case, and everything else is handled with custom fields, export lists and notes. Your team works around the software instead of with it, and new employees mostly learn the workarounds.

03

An existing application needs to keep growing

New requirements keep coming, and the existing application should be extended rather than replaced. For Deutsche Bahn, we support the ongoing development of a digital signage application whose Directus CMS and Next.js frontend are gaining new features.

04

A product idea needs to become a SaaS product

The domain concept is in place, but user accounts, billing and reliable operations are missing. For Prevision UG, we built Komplify as a bilingual SaaS platform with domain management, multi-level website scans and Stripe billing through subscriptions and credits.

What we build

Building blocks we develop for your business software

Every application is shaped differently, but certain building blocks appear in almost every project. We deliver them as working software, not as a concept document.

Operational workspaces for your team

You get forms, lists and status workflows for the process that currently lives in spreadsheets. At Agilico, teams create quotations with customer and agency contacts and schedule print and digital placements in calendars and exportable publication plans.

Dashboards and reporting

Key figures and trends appear where decisions are made, not only in a monthly export. In the Komplify dashboard, users follow their score over time, compare scans and export reports as PDF or CSV.

Roles, permissions and traceability

Who may view, change and approve what is defined in the system, not in an informal agreement. Where required, an audit trail records changes to critical data. The Agilico platform, for example, is role-based throughout.

SaaS foundations: accounts, subscriptions, tenants

We build sign-up, subscriptions, usage-based credits and separate data spaces for each customer. Komplify bills through Stripe subscriptions and scan credits, and at PinnDeals the database itself enforces the quotas of the five plans.

Documents in the format the next step needs

Your application produces files exactly the way a print shop, customer or public authority expects them. At Agilico, customers design their ads in public campaign shops and pay through Stripe, after which the server generates print-ready PDF/X-4 files with a color profile, bleed and embedded fonts.

Tests, deployment and handover

Every application comes with automated tests, reproducible Docker deployments through GitHub Actions and documentation that allows another team to continue the work. For Anita, we built a Playwright suite that checks every state of the development branch before it ships.

Approach

How your process becomes a web application

For operational applications, we work in four steps. What matters most is that your team works with real software early, not with clickable mockups.

  1. 01

    Map the current process with a real case

    We walk through an actual case with the people who handle it every day: which data is created, who decides and where spreadsheets or emails fill the gaps today. This produces a data model before the first screen is drawn.

  2. 02

    Define the smallest useful slice

    We choose the part of the process that delivers real value as a first version and deliberately postpone the rest. Depending on scope, your team typically works with a first version within 3 to 6 weeks.

  3. 03

    Build in iterations with realistic data

    You see progress regularly in a test environment with realistic data, not on slides. Feedback from the business team goes into the next iteration before wrong assumptions settle in.

  4. 04

    Data migration, go-live and operation

    We migrate existing data from spreadsheets or legacy systems, put the application into production and support the first weeks of daily use. After that, we continue development or hand the documented code over to your team.

Technology

Technology that stays maintainable and transferable

For web applications, we usually rely on React or Next.js with TypeScript in the frontend and Node.js with Express or Fastify in the backend. Data lives in PostgreSQL, accessed through Prisma and APIs validated with Zod. We run applications in Docker containers or on AWS and deliver them through GitHub Actions.

The choice follows your requirements and your operating environment. Where heavy computation or systems-level work calls for it, we add Python or C++. For Deutsche Bahn, by contrast, we work within the existing stack of Directus, Next.js and TypeScript. What matters is a stack that another team can take over without exotic specialist knowledge.

Typical stack

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Express
  • Fastify
  • PostgreSQL
  • Prisma
  • AWS
  • Docker

Frequently asked questions

Common questions before you commission a web application

Effort depends on scope, integrations, security requirements and existing systems, so we do not quote flat prices. In a free 30-minute call, we assess your project. You then receive a transparent proposal covering approach, milestones and billing.

Your team typically works with a first version within 3 to 6 weeks, depending on scope and the integrations required. That version covers a clearly defined part of the process and is then extended step by step. We only commit to a date once the scope is clear.

If an established standard product covers your process without major detours, we will recommend it. Custom software pays off when the process sets you apart from competitors or when adapting standard software creates more effort than it saves. A combination often makes sense: standard software for accounting or CRM, a custom application for the core process.

Yes. We start with a review of code, architecture and deployment, then tell you openly what can be extended and where rework is needed. For Deutsche Bahn, for example, we support the ongoing development of an existing digital signage application built on Directus and Next.js.

You do. You receive the complete, documented source code, and there is no artificial lock-in. Because we use widely adopted technologies, another team or your own IT department can continue the application at any time.