EN

EthicalcHow we work

How we work

In stages, with acceptance criteria agreed before work starts. We build, we operate and, when you want, we hand over the whole system.

Terms of cooperation

We do not impose our own templates.

First and foremost, we accept the Client's terms or the terms of the request for quotation or tender. We offer the B-O-T model as an option, once both sides have agreed its details.

The B-O-T model

We build. We operate. We hand over.

We take on the cost and risk of the build. Your IT department does not get another project to run. Once the system works and has been proven, it passes into your control.

Bbuild

We build

We start from a description of the need in your own words. We reply with questions in writing, then with a specification: scope, acceptance criteria for every stage, schedule and price. The first working version on your data is ready in weeks. You pay for stages signed off in an acceptance report.

Ooperate

We operate

After acceptance we keep the system running day to day: monitoring, backups with a tested restore, updates and security fixes, support with a defined response time. Your team uses the system; we make sure it works.

Ttransfer

We hand over

On request we hand over everything: source code, infrastructure described as code, documentation, access credentials and administrator training. Your IT department or another contractor can take over the system. The handover is part of the contract from the start, not a negotiation at the end.

In every project

Core terms of cooperation

All of these are standard, not options on a price list.

  1. Acceptance with tests after every stageScenarios and measurable acceptance criteria are agreed before implementation. Every stage ends with a demonstration on your data and an acceptance report. Deployment is complete when the system runs on a real case, order or document.
  2. Documentation in your languageUser and administrator documentation, a description of the integrations, and instructions for building, installing, configuring, updating and restoring. Code and naming in English, as is standard in the industry.
  3. Maintenance and support after go-liveRequests in writing, accepted around the clock. Response to a critical incident within 4 business hours, to all others by the end of the next business day. Error classes and repair times are written into the contract.
  4. Warranty of 24 to 60 monthsCovers the system, configuration and the integrations delivered. Fixes are included in the price, including security fixes for the delivered software and its dependencies.
  5. Copyright and the full source code for the clientRights pass to you on acceptance of each stage, together with the right to have any contractor develop the system further. Open-source components are listed with their licences. The repository can be on your side from day one.
  6. Security and backups with a tested restoreEncryption in transit and at rest, two-factor login, roles and permissions, an event log, security testing at acceptance with a report. Backups in a second location, with a documented restore test and RPO/RTO parameters.
  7. Integration with your systemsERP, procurement platforms, workflow, reporting tools, devices. Through interfaces, files or logs, depending on what the system exposes. Every integration has its connections and their security rules documented.
  8. TrainingSeparately for users and for administrators, on-site or remote, with materials you can reuse for new staff.
  9. Digital accessibility to WCAG 2.1 AAKeyboard and screen-reader operation, contrast, image descriptions, clear error messages. Built in from the start, not bolted on at the end.
  10. On your premises or in an EU cloudClient infrastructure, a cloud region in the European Union or fully on-premises with no outside connections. We sign the data processing agreement before we start.

Information security

Rules we hold ourselves to.

  • We manage information security in line with ISO/IEC 27001: policy, risk assessment, procedures, review.
  • We sign the data processing agreement (DPA) before work begins. Test data is synthetic or anonymised.
  • Access to environments only through named accounts and keys, with an event log. Secrets are kept out of the repository.
  • Our own websites set no cookies, use no analytics and connect to no third-party servers. We apply this rule from our company site through to our clients' systems.

AI Act and EU regulation

Legal compliance.

  • AI Act, Regulation (EU) 2024/1689: risk-based classification of the system, transparency towards users, human oversight of decisions, documentation and an event log.
  • GDPR, Regulation (EU) 2016/679: data processing agreement, data protection impact assessment where required, data protection from the design stage.
  • NIS2, Directive (EU) 2022/2555, and national cybersecurity legislation: requirements for suppliers to essential and important entities.
  • DORA, Regulation (EU) 2022/2554: requirements for ICT service providers to the financial sector.

EU-funded projects

Requests for quotation and the competitive procedure.

We submit bids in procurement run under the competitive procedure required in EU-funded projects. We know their requirements and have ready what they usually ask for: a named team with documented experience, declarations, a schedule with stage acceptance, transfer of rights together with the source code, a warranty with a response time, and documentation in your language.

If you are preparing a request for quotation for a system, we will gladly answer questions in writing about feasibility and the order of magnitude of costs before the request is published.

First step

From a description of the need to a working version.

Step 1Describe the need

A few sentences in your own words: what should work, for whom, with what data. No technical knowledge needed.

Step 2Questions and specification

We reply within two business days. Then a specification with acceptance criteria, schedule and price. Free of charge.

Step 3First version

A working version on your data in weeks. You test it at work, not in a demo.

Step 4Acceptance and operation

Stages signed off in acceptance reports, then day-to-day maintenance or handover of the whole system to your team.

Tell us what you need