WEB APPS

Web applications start at €15,000. A focused internal tool or customer portal with logins, user roles and one or two integrations is usually closer to that starting point; a multi-tenant SaaS platform with subscription billing, or an app connected to several systems such as ERP, CRM and accounting, costs correspondingly more. Before we quote, we hold an initial call and, for larger projects, a short scoping phase that pins down features, data and interfaces. You then receive a fixed price in euro for a clearly defined scope, broken down by module, so you can decide what belongs in the first release and what can wait. Ongoing costs for hosting and third-party services are listed separately.

A focused first release is typically ready in two to four months, and the project runs in four stages. In discovery, we map processes, roles and data and agree the scope. In the prototype stage, you click through the key screens before anything is built. Development follows in two-week sprints, each ending with a tested, working version in the staging environment. Launch covers data migration, user training and go-live, followed by a period of close support. Integrations with older systems and the speed of internal sign-offs have the biggest influence on the timeline. It often makes sense to start with a minimum viable product and add features once real users have worked with it.

The project runs in English – or in German, if that suits your team – through video calls, a shared ticket board and a staging environment you can open at any time. Germany is one hour ahead of Ireland all year round, so working hours overlap almost completely. MDEPARTMENT has no office in Ireland. Where an in-person workshop is worthwhile – at kick-off, for example, or for user training – we travel to you on request. Your contract is with KRUPKA Concept GmbH, based in Germany. For VAT-registered Irish businesses, we invoice in euro under the EU reverse-charge procedure: no German VAT is charged, and you self-account for Irish VAT in your VAT return.

Yes, provided the architecture sets clear data boundaries from the outset. Typical examples are an assistant that drafts replies or summaries, and a document search that answers questions from your manuals, contracts or policies, linking to the source passage – an approach known as retrieval-augmented generation. We choose providers and models that process data in the EU or under appropriate contractual safeguards, configure them so your inputs are not used for training, and keep personal data out of prompts wherever possible. Access follows the same user roles as the rest of the application. We also document how each feature works, which helps with your records of processing activities, any data protection impact assessment and the transparency obligations under the EU AI Act.