Clear agreements before work starts.
Every engagement receives a proposal or agreement with concrete scope, price, timing and responsibilities. These principles form the baseline; the project-specific agreement takes precedence.
Scope & changes
Deliverables, assumptions and acceptance are described upfront. New requirements or changed assumptions are discussed for price and schedule impact before becoming part of the engagement.
Pricing & payment
Rates, invoice milestones and payment terms are stated in the proposal. External hosting, model, data or licence costs are made visible upfront and passed on only as agreed.
Ownership & confidentiality
After payment, customer-specific code and documentation belong to the customer unless agreed otherwise. Existing generic components and open-source software retain their own rights. Confidential information is used only for the engagement.
Responsibility
Software is built carefully and professionally, but no system is risk-free. Liability, warranties, security responsibilities, operations and continuity are set proportionately in the engagement agreement.