Waterford

Yes. Many projects combine a public website with a tool behind it. For a life-sciences manufacturer or supplier, that might be a change-request workflow in which every step is signed off and logged. A haulier or freight forwarder working with the port at Belview might need a status page where customers track consignments without phoning. Food producers often want traceability records from intake to dispatch, while start-ups at SETU Xcelerate usually need a first product version they can put in front of pilot customers. For heritage and tourism businesses in the Viking Triangle, the focus is online booking that works on any phone. Every website we build is fast, GDPR-compliant and designed in line with the WCAG accessibility guidelines.

Websites start at €3,000; custom software and web applications start at €15,000. How far above those figures a project ends up depends on factors we can name early: the number of page templates and languages, interfaces to systems such as an ERP or a laboratory database, user roles, data migration and how much content we write for you. Once we have discussed these points in an initial conversation, we put the scope in writing and quote a fixed price. It changes only if you change the scope, and any addition is priced before work on it begins. Invoices come from KRUPKA Concept GmbH in Germany, in euro; for VAT-registered Irish businesses, the EU reverse-charge mechanism applies.

It depends on scope, but most projects fall within predictable ranges. A company website with a clear structure typically takes four to eight weeks, and the pace is usually set by how quickly texts, images and approvals are ready. A defined software tool, such as an approval workflow or a customer portal, generally reaches its first working version in eight to twelve weeks; we then extend it in stages based on how your team uses it. In life-sciences settings, allow time for internal reviews, since your quality or IT team may want to assess a tool before staff rely on it. We agree milestones at the outset and show progress on a test environment throughout.

Either works, and you can switch later. If you want us to run it, a maintenance agreement covers hosting in EU data centres, security and framework updates, backups, monitoring and an agreed amount of time for small changes each month; response times for faults are set in writing. If your IT department or a local developer is to take over, we hand over the source code, deployment instructions and technical documentation, and brief the people who will maintain it. For tools used in regulated work, we keep a change log for every release, so your quality team can see what changed, when and why. In both cases, the code and the content belong to you.