This page gets passed on — to the IT manager, the technical director, the works council. For them, it sets out who does what, who builds and who operates. Everything else, down to the permissions list, we clarify in a conversation with your IT.
What your IT does
Set up the accounts, review and approve the permissions concept and the Langdock roles, and from Step 4 a Microsoft Azure account — your company's cloud account with Microsoft. That is a few days in total, not a project role. Running and maintaining the knowledge is not your IT's job.
What Cassel does
Prepare and verify your knowledge, set up Langdock — permissions and rules —, have applications built and accept them, involve and train your people, and provide monthly support from Step 4 onwards.
Who builds
Concept, preparation, rules and introduction: Cord Cassel and Spencer Robens. Cord Cassel sets up Langdock, with a Langdock specialist where needed. From Step 4, a development partner builds to our specification; we choose which one together with you beforehand. Your contractual partner remains Cassel, including for the software; we accept everything before it reaches you. The rights to the software lie with Cassel: if a development partner drops out, another continues to the same specification. Operation and data sit in your Microsoft Azure account.
Who operates
For Steps 1 to 3 you only license Langdock, directly from the provider; from Step 4 your Microsoft Azure account is added. Both belong to you and stay yours. From Step 4, Cassel provides monthly support: operation, maintenance of the knowledge, a named contact — as a service provider with access you can withdraw at any time.
Rules and records
You decide what an agent may read, what may run without approval and who approves — we write it down before anything runs. The works council, the data protection officer and your IT receive a written statement of what is read and what is logged.
Your people and the works council
The goal is growth, not job cuts: the time gained is meant for new tasks. We recommend committing to this in writing before the start. The works council is involved from Step 1, before anything is set up. Nothing is ever measured per person.
Standard where possible. Tailored where it counts.
Every solution is tailored to what only your company has: your terms, your processes, your way of costing a quotation or tracking down a fault.
This is not a kit of separate tools, each bringing its own data. All applications work on the same knowledge base and under the same rules. What matters is that your process is mapped correctly — that is what Cord Cassel's thirty years in industry stand for.
Not a configurator: a configurator needs rules that someone sets in advance for every variant. The applications work with what your company has already built and written — comparable projects, verified knowledge, figures from the ERP — and your people approve.