Not a step in the process. The promise behind the whole collaboration

Clear agreements from the start

You are covered from the very first conversation

The terms of business apply from the beginning. After that we add the agreements the task, the data processing and the operation call for.

We do not use more documents than necessary. But we make sure responsibility, rights and expectations are clear before the work begins.

1. Confidentiality before the sensitive details are shared

   NDA when needed

   When ideas, commercial matters or data call for it, we can sign a confidentiality agreement before the meeting or the pre-project.

2. The frame around the concrete task

   Project agreement

   Sets out purpose, scope, price, responsibility, deliverables and approvals for the project or the stage.

3. One shared frame for longer collaborations

   Framework agreement

   Makes it simpler to start new projects and stages without renegotiating the whole basis every time.

4. When we process personal data

   Data processing agreement

   Describes roles, instructions, security and responsibility when Coignite processes personal data on your behalf.

5. Clear terms once the solution is live

   Service agreement

   Describes support, maintenance, response times, responsibility and the ongoing handling of the solution.

We only use the agreements the task calls for. Not everything is relevant every time.

Ownership

You own your solution, and you are never tied to us

1. You own your solution

   When we build something specifically for you, you own the agreed solution, your data and the project-specific deliverables. Where we use existing open source components or our own reusable modules, we describe clearly what is yours, and what follows its own existing licence terms.

2. You can always move on without us

   You can take the solution further in house or together with another supplier. We want to keep you because the collaboration creates value, not because it is difficult to leave.

3. Documentation that can be handed on

   We document the solution, the important decisions and the necessary access, so others can understand, run and develop it further. The level of documentation is agreed according to the complexity and the need.

4. A proper ending

   If the collaboration is to end one day, we help with a controlled handover of the relevant code bases, data, access and documentation. We make sure your own people or a new supplier can move on properly.

In daily operation

What you can count on in everyday work

The concrete operation depends on the solution and the agreed service. When it is part of our responsibility, we make sure the basics are not overlooked.

1. Clear roles and named contacts

   You know who is responsible for what, and who to contact. The people you talk to know your solution and the history behind it.

2. Changes are agreed in advance

   We assess the consequences for functionality, time and price before a change is set in motion. You should not be surprised afterwards.

3. Backup and recovery

   When it is part of the operations agreement, relevant data and systems are backed up, and we have decided how the solution can be restored after an incident.

4. Requirements are considered early

   We help identify the relevant requirements for data, security and industry conditions, so they do not become expensive to fix later.

5. Decisions are written down

   Important technical and commercial decisions are written down, so you can later understand why the solution was built the way it was.

6. Ongoing risk assessment

   We point out technical debt, dependencies, security risks and coming needs before they grow into urgent problems.